<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>INDI-Library | 星空の風景, 日々の風景</title>
	<atom:link href="https://globe3.ddns.net/wp/category/starry-sky/indi-library/feed/" rel="self" type="application/rss+xml" />
	<link>https://globe3.ddns.net/wp</link>
	<description>星空のこと. 日々に想うこと.</description>
	<lastBuildDate>Thu, 29 Oct 2026 00:08:15 +0000</lastBuildDate>
	<language>ja</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>KStars Flatpak を追う</title>
		<link>https://globe3.ddns.net/wp/configuring-flatpak-version-kstars/</link>
					<comments>https://globe3.ddns.net/wp/configuring-flatpak-version-kstars/#respond</comments>
		
		<dc:creator><![CDATA[minmin]]></dc:creator>
		<pubDate>Mon, 19 Oct 2026 01:48:21 +0000</pubDate>
				<category><![CDATA[INDI-Library]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<guid isPermaLink="false">https://globe3.ddns.net/wp/?p=6555</guid>

					<description><![CDATA[Flatpak版 KStarsを使うと、自動に更新されたらしい。その為に、安定して動いていた、コミットが更新されたらしく、不具合を追うようになりました。 ここには、その作業を記載しています。 KStars / Ekos  [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Flatpak版 KStarsを使うと、自動に更新されたらしい。<br>その為に、安定して動いていた、コミットが更新されたらしく、不具合を追うようになりました。</p>



<p class="wp-block-paragraph">ここには、その作業を記載しています。</p>



<p class="wp-block-paragraph">KStars / Ekos , Flatpak版、こちらの環境では、Local Astrometryが使えていません。<br>プレートソルブにて特定の動作で、KStars / Ekos , Flatpak版がダウンしています。<br>2026年10月21日現在、Local Astrometry動作とプレートソルブ動作不具合は確認していません。</p>



<h2 class="wp-block-heading">Flatpak の”今”を調べる</h2>



<h3 class="wp-block-heading">現在のコミットを表示</h3>



<pre class="wp-block-code"><code>$ flatpak info --user org.kde.kstars

KStars - Desktop Planetarium

          ID: org.kde.kstars
         Ref: app/org.kde.kstars/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 3.8.5
     License: GPL-2.0+
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 957.5&nbsp;MB
     Runtime: org.kde.Platform/x86_64/6.10
         Sdk: org.kde.Sdk/x86_64/6.10

      Commit: 110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136
      Parent: 5f8c05ec2b8c95a0a1578239c1ef88e2ca15607033426b0b73ec717ffca1501a
     Subject: Merge pull request #160 from knro/fix-focus-settle-crash (a919fa71c20c)
        Date: 2026-10-03 05:53:00 +0000</code></pre>



<h3 class="wp-block-heading">KStars の更新をブロックしているか確認します</h3>



<pre class="wp-block-code"><code>$ flatpak mask --user
Masked patterns:
  org.kde.kstars</code></pre>



<h3 class="wp-block-heading">KStars に更新があるか確認します</h3>



<pre class="wp-block-code"><code>$ flatpak remote-info --log flathub org.kde.kstars
Remote ‘flathub’ found in multiple installations:

   1) system
   2) user

Which do you want to use (0 to abort)? &#91;0-2]: 2

KStars - Desktop Planetarium

        ID: org.kde.kstars
       Ref: app/org.kde.kstars/x86_64/stable
      Arch: x86_64
    Branch: stable
   Version: 3.8.5
   License: GPL-2.0+
Collection: org.flathub.Stable
  Download: 480.1&nbsp;MB
 Installed: 957.5&nbsp;MB
   Runtime: org.kde.Platform/x86_64/6.10
       Sdk: org.kde.Sdk/x86_64/6.10

    Commit: e44f942857288863d34a9b37efdea4c35cef7c3d9c25738a28344d27449fbdf4
    Parent: 110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136
   Subject: Merge pull request #161 from knro/update-3.8.5-patch (e464afcc596a)
      Date: 2026-10-10 11:13:13 +0000
   History: 

    Commit: 110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136
   Subject: Merge pull request #160 from knro/fix-focus-settle-crash (a919fa71c20c)
      Date: 2026-10-03 05:53:00 +0000

    Commit: 5f8c05ec2b8c95a0a1578239c1ef88e2ca15607033426b0b73ec717ffca1501a
   Subject: Merge pull request #157 from s-pouya-sh/patch-18 (a8ca8995e0f7)
      Date: 2026-08-16 11:09:54 +0000

    Commit: 98a725b70de65599ea7f4e479efe6d891506d4fa9e7df620a9ed54e818d72584
   Subject: Merge pull request #155 from s-pouya-sh/patch-17 (a3981b62f214)
      Date: 2026-08-09 16:46:49 +0000

    Commit: 435860949507c59cdc7adb389e014b6c10a23a8d5add5b15fdd658d2bc66d1c0
   Subject: Merge pull request #154 from s-pouya-sh/patch-17 (7ea6cc80236d)
      Date: 2026-08-09 14:15:48 +0000</code></pre>



<p class="wp-block-paragraph">この現時点でのコミットは、</p>



<pre class="wp-block-code"><code>Commit: e44f942857288863d34a9b37efdea4c35cef7c3d9c25738a28344d27449fbdf4
   Date: 2026-10-10 11:13:13 +0000</code></pre>



<p class="wp-block-paragraph">その親コミットは次のとおりです。</p>



<pre class="wp-block-code"><code>Commit: 110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136
   Date: 2026-10-03 05:53:00 +0000</code></pre>



<h3 class="wp-block-heading">Flatpak の更新履歴を確認</h3>



<pre class="wp-block-code"><code>$ flatpak history --user
Time             Change        Application                           Branch      Installation Remote
10月 12 16:23:35 pull          org.kde.kstars                        stable      user         flathub
10月 12 16:23:36 deploy update org.kde.kstars                        stable      user         flathub
10月 14 18:34:19 pull          org.freedesktop.Platform.GL.default   25.08       user         flathub
10月 14 18:34:20 deploy update org.freedesktop.Platform.GL.default   25.08       user         flathub
10月 14 18:34:22 pull          org.freedesktop.Platform.GL.default   25.08-extra user         flathub
10月 14 18:34:22 deploy update org.freedesktop.Platform.GL.default   25.08-extra user         flathub
10月 14 18:34:24 pull          org.freedesktop.Platform.VAAPI.Intel  25.08       user         flathub
10月 14 18:34:24 deploy update org.freedesktop.Platform.VAAPI.Intel  25.08       user         flathub
10月 14 18:34:24 pull          org.freedesktop.Platform.codecs-extra 25.08-extra user         flathub
10月 14 18:34:24 deploy update org.freedesktop.Platform.codecs-extra 25.08-extra user         flathub</code></pre>



<pre class="wp-block-code"><code>10月 12 16:23:35 pull          org.kde.kstars
10月 12 16:23:36 deploy update org.kde.kstars</code></pre>



<p class="wp-block-paragraph">2026年10月12日に KStars の更新が行われたことが分かります。</p>



<h2 class="wp-block-heading">KStars の自動更新を止める</h2>



<pre class="wp-block-code"><code>$ flatpak mask --user org.kde.kstars</code></pre>



<p class="wp-block-paragraph">確認します。</p>



<pre class="wp-block-code"><code>$ flatpak mask --user
Masked patterns:
  org.kde.kstars</code></pre>



<p class="wp-block-paragraph">KStars の更新をブロックしているか確認</p>



<h3 class="wp-block-heading">自動更新の仕組みをさらに調べる</h3>



<p class="wp-block-paragraph">ユーザー単位のタイマー</p>



<pre class="wp-block-code"><code>$ systemctl --user list-timers --all | grep -Ei 'flatpak|update'
Sun 2026-10-18 18:00:00 JST 3min 57s -                                      - snap.firmware-updater.firmware-notifier.timer snap.firmware-updater.firmware-notifier.service</code></pre>



<p class="wp-block-paragraph">システム全体のタイマー</p>



<pre class="wp-block-code"><code>$ systemctl list-timers --all | grep -Ei 'flatpak|update'
Mon 2026-10-19 00:50:03 JST       6h Sun 2026-10-18 01:25:22 JST            - plocate-updatedb.timer         plocate-updatedb.service
Mon 2026-10-19 16:10:41 JST      22h Sun 2026-10-18 16:10:41 JST 1h 46min ago update-notifier-download.timer update-notifier-download.service
Sun 2026-10-25 01:27:18 JST   6 days Thu 2026-10-15 09:41:01 JST            - update-notifier-motd.timer     update-notifier-motd.service</code></pre>



<p class="wp-block-paragraph">systemd のタイマー一覧には、Flatpak の自動更新を直接実行するタイマーは、なさそうです。</p>



<p class="wp-block-paragraph">GNOME Software の自動更新設定を確認します。</p>



<pre class="wp-block-code"><code>$ gsettings list-recursively org.gnome.software | grep -Ei 'download-updates|download-updates-notify|install-updates|update'
org.gnome.software allow-updates true
org.gnome.software download-updates true
org.gnome.software download-updates-notify true
org.gnome.software packagekit-historical-updates-timestamp uint64 0
org.gnome.software update-notification-timestamp int64 0</code></pre>



<p class="wp-block-paragraph">GNOME Software では、更新に関する設定が有効になっています。<br>この前に、flatpak mask &#8211;user org.kde.kstars を行ったので、Flatpak 更新では KStars が通常の更新対象から除外されます。<br></p>



<h2 class="wp-block-heading">直前のバージョンに戻す。ダウングレード</h2>



<p class="wp-block-paragraph">今回は、10月 12 16:23:36 deploy update org.kde.kstars<br>この時点で不具合が生じたので、その直前の状態に戻します。</p>



<p class="wp-block-paragraph">確認した履歴では、現在のコミットの親が次のコミットです。</p>



<pre class="wp-block-code"><code>現在：e44f942857288863d34a9b37efdea4c35cef7c3d9c25738a28344d27449fbdf4
直前：110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136</code></pre>



<pre class="wp-block-code"><code>$ flatpak update --user --commit=110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136 org.kde.kstars
Looking for updates…

Nothing to do.</code></pre>



<p class="wp-block-paragraph">指定したコミットへの切り替えが実行されなかったようです。先に設定した flatpak maskを一時外します。</p>



<pre class="wp-block-code"><code>$ flatpak mask --user --remove org.kde.kstars</code></pre>



<pre class="wp-block-code"><code>$ flatpak update --user --commit=110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136 org.kde.kstars
Looking for updates…


        ID                     Branch         Op         Remote         Download
 1.     org.kde.kstars         stable         u          flathub        &lt; 480.1&nbsp;MB

Proceed with these changes to the user installation? &#91;Y/n]:Y

        ID                     Branch         Op         Remote         Download
 1. &#91;✓] org.kde.kstars         stable         u          flathub        18.9&nbsp;MB / 480.1&nbsp;MB

Updates complete.</code></pre>



<p class="wp-block-paragraph">Commit を確認します。</p>



<pre class="wp-block-code"><code>$ flatpak info --user org.kde.kstars

KStars - Desktop Planetarium

          ID: org.kde.kstars
         Ref: app/org.kde.kstars/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 3.8.5
     License: GPL-2.0+
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 957.5&nbsp;MB
     Runtime: org.kde.Platform/x86_64/6.10
         Sdk: org.kde.Sdk/x86_64/6.10

      Commit: 110b41247bf4b838e944905495f2537ad1b347cc528cdf32316875ee5e0db136
      Parent: 5f8c05ec2b8c95a0a1578239c1ef88e2ca15607033426b0b73ec717ffca1501a
     Subject: Merge pull request #160 from knro/fix-focus-settle-crash (a919fa71c20c)
        Date: 2026-10-03 05:53:00 +0000</code></pre>



<p class="wp-block-paragraph">更新ブロックを再設定します。</p>



<pre class="wp-block-code"><code>$ flatpak mask --user org.kde.kstars
$ flatpak mask --user
Masked patterns:
  org.kde.kstars</code></pre>



<p class="wp-block-paragraph">KStarsを起動させます。</p>



<pre class="wp-block-code"><code>$ flatpak run org.kde.kstars</code></pre>



<h3 class="wp-block-heading">さらに、前のコミットに戻すには</h3>



<p class="wp-block-paragraph">更新ブロックを一時解除します。</p>



<pre class="wp-block-code"><code>$ flatpak mask --user --remove org.kde.kstars</code></pre>



<p class="wp-block-paragraph">さらに前のコミットにもどします。</p>



<pre class="wp-block-code"><code>$ flatpak update --user --commit=5f8c05ec2b8c95a0a1578239c1ef88e2ca15607033426b0b73ec717ffca1501a org.kde.kstars</code></pre>



<p class="wp-block-paragraph">コミットを確認します。</p>



<pre class="wp-block-code"><code>$ flatpak info --user org.kde.kstars</code></pre>



<p class="wp-block-paragraph">更新ブロックを再設定します。</p>



<pre class="wp-block-code"><code>$ flatpak mask --user org.kde.kstars</code></pre>



<p class="wp-block-paragraph">KStars を起動して動作確認します。</p>



<pre class="wp-block-code"><code>$ flatpak run org.kde.kstars</code></pre>



<h2 class="wp-block-heading">KStars ログを録る</h2>



<p class="wp-block-paragraph">エラーをログに記録します。</p>



<ul class="wp-block-list">
<li>Ekos画面 → Setup → Logs&#8230; →
<ul class="wp-block-list">
<li>Logging: Verbosity: Verbose</li>



<li>出力：File</li>



<li>Ekos: Alignment</li>
</ul>
</li>



<li>Flatpak 版 KStars を端末から起動し、標準出力・標準エラーに出力された情報も記録させます。</li>



<li>KStars を終了します。</li>



<li>コマンドでKStarsを起動し、ログを指定します。</li>
</ul>



<pre class="wp-block-code"><code>$ flatpak run org.kde.kstars 2&gt;&amp;1 | tee ~/kstars-debug.log</code></pre>



<ul class="wp-block-list">
<li>KStars：  Ekos → Align</li>



<li>Local Astrometry を選択し、プレートソルブを実行します。</li>



<li>エラーが発生したら KStars を終了します。</li>
</ul>



<p class="wp-block-paragraph">ログを確認します。</p>



<pre class="wp-block-code"><code>grep -inE 'astrometry|solve-field|index|error|failed|solver'
~/kstars-debug.log | tail -n 100</code></pre>



<h2 class="wp-block-heading">安定版と開発版を並行して使う</h2>



<p class="wp-block-paragraph"><br><a rel="noopener" target="_blank" href="https://ivanalejandro0.com/blog/flatpak-custom-data-folder/">https://ivanalejandro0.com/blog/flatpak-custom-data-folder/</a></p>



<p class="wp-block-paragraph">KStars 開発版 と安定版を使います。<br>設定ファイルは別に用意し、設定ファイルやデータやディレクトリが影響しない編成にします。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">安定版（Stable）の保存先：   ~/.var/app/org.kde.kstars<br>開発版（Nightly）の保存先： ~/.var/app/org.kde.kstars-nightly</p>
</div>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">Astrometry.net を使う</h2>



<div class="wp-block-cocoon-blocks-tab-box-1 blank-box bb-tab bb-check block-box">
<p class="wp-block-paragraph">後に記述した様に、KStars のユーザー単位に Flatpak 権限を変更させても、動作しませんでした。</p>



<pre class="wp-block-code"><code>flatpak override --user \
  --talk-name=org.freedesktop.Flatpak \</code></pre>



<div class="wp-block-cocoon-blocks-info-box block-box primary-box">
<p class="wp-block-paragraph">flatpak override ：アプリの Flatpak 権限設定を変更する<br>&#8211;user ：現在のユーザーにだけ適用する<br>&#8211;talk-name=org.freedesktop.Flatpak ：org.freedesktop.Flatpak という D-Bus サービスとの通信を許可する<br>org.kde.kstars ：設定変更の対象を KStars に限定する</p>
</div>



<p class="wp-block-paragraph">ラッパースクリプト経由でFlatpak版KStars/Ekosから、プレートソルブを行わせます。</p>
</div>



<h3 class="wp-block-heading">インストール、設定</h3>



<pre class="wp-block-code"><code>sudo apt update
sudo apt install astrometry.net</code></pre>



<pre class="wp-block-code"><code>sudo cp /etc/astrometry.cfg /etc/astrometry.cfg.bak</code></pre>



<p class="wp-block-paragraph">パスを追加</p>



<pre class="wp-block-code"><code>sudo emacs -nw /etc/astrometry.cfg</code></pre>



<p class="wp-block-paragraph">USERNAMEは、実際のユーザーアカウント名</p>



<pre class="wp-block-code"><code>### 次の行に追加
### add_path /usr/share/astrometry
add_path /home/USERNAME/.var/app/org.kde.kstars/data/kstars/astrometry</code></pre>



<p class="wp-block-paragraph">変更箇所を確認します。</p>



<pre class="wp-block-code"><code>$ grep -E '^&#91;&#91;:space:]]*(add_path|autoindex|index)' /etc/astrometry.cfg</code></pre>



<h3 class="wp-block-heading">flatpak-spawnを使う</h3>



<p class="wp-block-paragraph">Flatpakからホスト側の solve-field を呼び出すラッパースクリプトを用います。</p>



<p class="wp-block-paragraph">flatpak-spawn は、Flatpakアプリのサンドボックス内から、Ubuntu側のプログラムを実行するためのコマンドです。</p>



<p class="wp-block-paragraph">Flatpakの設定を確認します。<br>何も表示されない状態なら、ユーザー単位のオーバーライドは解除されています。</p>



<pre class="wp-block-code"><code>flatpak override --user --show org.kde.kstars</code></pre>



<p class="wp-block-paragraph">flatpak-spawn が使えるか確認します。</p>



<pre class="wp-block-code"><code>flatpak run --command=sh org.kde.kstars -c 'command -v flatpak-spawn'
/usr/bin/flatpak-spawn</code></pre>



<p class="wp-block-paragraph">Flatpak版 KStars にホストコマンドの実行権限を与えます。<br>KStarsに org.freedesktop.Flatpak のD-Busインターフェースへのアクセスを許可します。</p>



<pre class="wp-block-code"><code>flatpak override --user \
  --talk-name=org.freedesktop.Flatpak \
  org.kde.kstars</code></pre>



<p class="wp-block-paragraph">Ubuntuのソルバーが動作することを確認します。</p>



<pre class="wp-block-code"><code>/usr/bin/solve-field --version</code></pre>



<h4 class="wp-block-heading">ラッパースクリプトを作成します。</h4>



<pre class="wp-block-code"><code>mkdir -p ~/.var/app/org.kde.kstars/data/wrapper</code></pre>



<pre class="wp-block-code"><code>cat &gt; ~/.var/app/org.kde.kstars/data/wrapper/solve-field &lt;&lt;'EOF'
#!/bin/sh
exec flatpak-spawn --host /usr/bin/solve-field "$@"
EOF</code></pre>



<pre class="wp-block-code"><code>cat &gt; ~/.var/app/org.kde.kstars/data/wrapper/solve-field &lt;&lt;'EOF'
#!/bin/sh

LOG="/var/data/wrapper/solve-field.log"

{
    echo
    echo "===== $(date) ====="
    printf 'ARG: &lt;%s&gt;\n' "$@"
} &gt;&gt; "$LOG"

exec /usr/bin/flatpak-spawn --host /usr/bin/solve-field "$@"
EOF</code></pre>



<p class="wp-block-paragraph">ラッパースクリプトに実行権限を付けます。</p>



<pre class="wp-block-code"><code>chmod +x ~/.var/app/org.kde.kstars/data/wrapper/solve-field</code></pre>



<p class="wp-block-paragraph">ラッパーの動作を確認します。ホスト側のAstrometry.netを呼び出せるかも確認します。</p>



<pre class="wp-block-code"><code>flatpak run --command=sh org.kde.kstars -c \
'"$HOME/.var/app/org.kde.kstars/data/wrapper/solve-field" --version'</code></pre>



<p class="wp-block-paragraph">また、<br>Flatpak環境では、アプリ専用のデータディレクトリは通常 /var/data に対応しています。</p>



<pre class="wp-block-code"><code>flatpak run --command=sh org.kde.kstars -c \
    '/var/data/wrapper/solve-field --version'</code></pre>



<h4 class="wp-block-heading">FlatpakとUbuntuの一時ファイルの受け渡しを修正</h4>



<h3 class="wp-block-heading">Ekosを設定</h3>



<p class="wp-block-paragraph">Alignモジュールに次があります。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">solver binary: /app/bin/solve-field<br>wcsinfo: /app/bin/wcsinfo<br>config: /app/etc/astrometry.cfg</p>
</div>



<p class="wp-block-paragraph">もしくは</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">solver binary: /usr/bin/solve-field<br>wcsinfo: /usr/bin/wcsinfo<br>config: /etc/astrometry.cfg</p>
</div>



<p class="wp-block-paragraph">Ekosを設定します。/usr/bin/solve-field　を変更します。<br>指定できる場合は、パスを用います。もしくはUSERNAMEは実際のユーザー名にします。</p>



<p class="wp-block-paragraph">solver binary: /var/data/wrapper/solve-field</p>



<p class="wp-block-paragraph">solver binary: /home/USERNAME/.var/app/org.kde.kstars/data/wrapper/solve-field</p>



<h3 class="wp-block-heading">INDI control panel</h3>



<p class="wp-block-paragraph">/usr/bin/solve-field<br>↓<br>/var/data/wrapper/solve-field</p>



<h4 class="wp-block-heading">サンドボックス（隔離空間）からシステムファイルへのアクセスについて</h4>



<p class="wp-block-paragraph">サンドボックス（隔離空間）からシステムファイルへのアクセスを可能にします。<br>Flatpak版 KStars にフォルダのアクセス権限を与えます。</p>



<pre class="wp-block-code"><code>flatpak override --user --filesystem=/usr/bin/solve-field org.kde.kstars</code></pre>



<pre class="wp-block-code"><code>flatpak override --user --filesystem=/usr/share/astrometry org.kde.kstars
flatpak override --user --filesystem=/var/lib/astrometry org.kde.kstars

アクセス権限を削除
flatpak override --user --nofilesystem=/usr/bin/solve-field org.kde.kstars
flatpak override --user --nofilesystem=host org.kde.kstars</code></pre>



<pre class="wp-block-code"><code>既存の /etc 全体へのアクセス権限
flatpak override --user --filesystem=/etc:ro org.kde.kstars
既存の /etc 全体へのアクセス権限を削除（リセット）
flatpak override --user --nofilesystem=/etc org.kde.kstars

KStarsのユーザーオーバーライドをリセットする
flatpak override --user --reset org.kde.kstars</code></pre>



<h3 class="wp-block-heading">シミュレーターで動作確認</h3>



<p class="wp-block-paragraph">先ずシミュレーターで動作確認します。<br>(IMX533では、Low (最小): 18.305deg、High (最大): <code>22.882</code> deg)</p>



<h3 class="wp-block-heading">Astrometry.net　を使ってプレートソルブ</h3>



<p class="wp-block-paragraph">動作テストします。</p>



<pre class="wp-block-code"><code>$ solve-field \
    --config /etc/astrometry.cfg \
    --overwrite \
    test.fits</code></pre>



<pre class="wp-block-code"><code>Found an existing WCS header, will try to verify it.
Extracting sources...
simplexy: found 489 sources.
Solving...
途中省略
  log-odds ratio 367.262 (3.15998e+159), 59 match, 0 conflict, 409 distractors, 64 index.
  RA,Dec = (25.7612,13.6752), pixel scale 0.777888 arcsec/pix.
  Hit/miss:   Hit/miss: --+-+---+--+---+-+---+++--+-++---+----+---+------+-----+----------+-++--+----------+------+-+++-----
Field 1: solved with index index-5206-18.fits.
Field 1 solved: writing to file /home/USERNAME/Astronomy-images/2026_10-17/Light/NGC_660/NGC_660_Light_HEUIB-II_180_secs_2026-10-18T04-14-57_080.solved to indicate this.
Field: /home/USERNAME/Astronomy-images/2026_10-17/Light/NGC_660/NGC_660_Light_HEUIB-II_180_secs_2026-10-18T04-14-57_080.fits
Field center: (RA,Dec) = (25.760992, 13.675102) deg.
Field center: (RA H:M:S, Dec D:M:S) = (01:43:02.638, +13:40:30.368).
Field size: 38.9551 x 38.9448 arcminutes
Field rotation angle: up is 179.813 degrees E of N
Field parity: neg
Creating new FITS file "/home/USERNAME/Astronomy-images/2026_10-17/Light/NGC_660/NGC_660_Light_HEUIB-II_180_secs_2026-10-18T04-14-57_080.new"...
Creating index object overlay plot...
Creating annotation plot...
Your field contains:
  IC 148
  NGC 660</code></pre>



<p class="wp-block-paragraph">画像から489個の星を検出しています。<br>index-5206-18.fits を使ってプレートソルブに成功しています。<br>　16&#8242; &#8211; 22&#8242;, Tycho2/Gaia Catalogを使っています。<br>赤経・赤緯と画像の視野を計算できています。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">Tycho2/Gaia Catalog　を用いて、<br>simplexy: found 489 sources： 489個の星などの光源を検出<br>Field 1: solved with index index-5206-18.fits： インデックスを使った位置解析<br>RA,Dec = (25.7612,13.6752)： 天球上の座標を計算<br>Field size: 38.9551 x 38.9448 arcminutes： 画像の視野を計算<br>Field parity: neg： 画像の座標変換における反転方向を示す情報<br>Your field contains: IC 148, NGC 660 と表示、画像内の天体を特定</p>
</div>



<h3 class="wp-block-heading">KStarsから、/usr/bin/solve-field　が見られるかを確認</h3>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
echo "=== solve-field ==="
command -v solve-field
echo "=== executable ==="
ls -l /usr/bin/solve-field
'
=== solve-field ===
=== executable ===
ls: '/usr/bin/solve-field' にアクセスできません: そのようなファイルやディレクトリはありません</code></pre>



<p class="wp-block-paragraph">/usr/bin/solve-field を KStarsからは<strong>見えていない</strong>。</p>



<p class="wp-block-paragraph">さらに確認します。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
echo "=== flatpak-spawn ==="
command -v flatpak-spawn
echo "=== host solve-field ==="
flatpak-spawn --host /usr/bin/solve-field --version
'
=== flatpak-spawn ===
/usr/bin/flatpak-spawn
=== host solve-field ===
Portal call failed: org.freedesktop.DBus.Error.ServiceUnknown
Hint: --host only works when the Flatpak is allowed to talk to org.freedesktop.Flatpak</code></pre>



<p class="wp-block-paragraph">Flatpak 内から設定ファイルとインデックスディレクトリが見えるかを確認します</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
echo "=== astrometry.cfg ==="
ls -l /etc/astrometry.cfg
echo "=== index directory ==="
ls -ld "$HOME/.var/app/org.kde.kstars/data/kstars/astrometry"
'
=== astrometry.cfg ===
ls: '/etc/astrometry.cfg' にアクセスできません: そのようなファイルやディレクトリはありません
=== index directory ===
drwxr-xr-x 2 USERNAME USERNAME 4096 10月 19 03:41 /home/USERNAME/.var/app/org.kde.kstars/data/kstars/astrometry</code></pre>



<h3 class="wp-block-heading">KStars に solve-fieldに対して実行権限をつけます</h3>



<p class="wp-block-paragraph">KStarsを終了させ、次を行います。</p>



<p class="wp-block-paragraph">KStars のユーザー単位に Flatpak 権限を変更します。</p>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">この権限を与えると、KStars からホスト側の任意のコマンドを実行できる可能性があります。Flatpak の隔離を弱める変更になります。</p>
</div>



<p class="wp-block-paragraph">コマンド内容は、以下です。<br></p>



<div class="wp-block-cocoon-blocks-info-box block-box primary-box">
<p class="wp-block-paragraph">flatpak override ：アプリの Flatpak 権限設定を変更する<br>&#8211;user ：現在のユーザーにだけ適用する<br>&#8211;talk-name=org.freedesktop.Flatpak ：org.freedesktop.Flatpak という D-Bus サービスとの通信を許可する<br>org.kde.kstars ：設定変更の対象を KStars に限定する</p>
</div>



<pre class="wp-block-code"><code>flatpak override --user \
  --talk-name=org.freedesktop.Flatpak \
  org.kde.kstars</code></pre>



<p class="wp-block-paragraph">solve-fieldを呼び出せるか確認します。</p>



<pre class="wp-block-code"><code>flatpak run --command=sh org.kde.kstars -c '
echo "=== host solve-field ==="
flatpak-spawn --host /usr/bin/solve-field --version
'</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">flatpak run ：Flatpak アプリを実行する<br>&#8211;command=sh ：KStars 本体ではなく、Flatpak 内のシェル sh を起動する<br>org.kde.kstars ：対象の Flatpak アプリを指定する<br>-c &#8216;&#8230;&#8217; ：引用符内のコマンドをシェルで実行する<br>echo &#8220;=== host solve-field ===&#8221; ：テスト内容を画面に表示する<br>flatpak-spawn &#8211;host ：Flatpak の外側にある Ubuntu ホスト環境でコマンドを実行する<br>/usr/bin/solve-field ：実行するプログラムを指定する<br>&#8211;version ：バージョンを表示するだけで終了する</p>
</div>



<pre class="wp-block-code"><code>=== host solve-field ===
0.93</code></pre>



<p class="wp-block-paragraph">Flatpak 版 KStars の内部で flatpak-spawn の使い方を表示させます。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c 'flatpak-spawn --help'
用法:
  flatpak-spawn &#91;オプション…] COMMAND &#91;ARGUMENT…]

Run a command in a sandbox

ヘルプのオプション:
  -h, --help                            ヘルプのオプションを表示する

アプリケーションのオプション:
  -v, --verbose                         Enable debug output
  --forward-fd=FD                       Forward file descriptor
  --clear-env                           Run with clean environment
  --watch-bus                           Make the spawned command exit if we do
  --expose-pids                         Expose sandbox pid in calling sandbox
  --share-pids                          Use same pid namespace as calling sandbox
  --env=VAR=VALUE                       Set environment variable
  --unset-env=VAR=VALUE                 Unset environment variable
  --env-fd=FD                           Read environment variables in env -0 format from FD
  --latest-version                      Run latest version
  --sandbox                             Run sandboxed
  --no-network                          Run without network access
  --sandbox-expose=NAME                 Expose access to named file
  --sandbox-expose-ro=NAME              Expose readonly access to named file
  --sandbox-expose-path=PATH            Expose access to path
  --sandbox-expose-path-ro=PATH         Expose readonly access to path
  --sandbox-expose-path-try=PATH        Expose access to path if it exists
  --sandbox-expose-path-ro-try=PATH     Expose readonly access to path if it exists
  --sandbox-flag=FLAG                   Enable sandbox flag
  --sandbox-a11y-own-name=DBUS_NAME     Allow owning the name on the a11y bus
  --host                                Start the command on the host
  --directory=DIR                       Working directory in which to run the command
  --app-path=DIR|""                     Replace runtime's /app with DIR or empty
  --usr-path=DIR                        Replace runtime's /usr with DIR</code></pre>



<h2 class="wp-block-heading">solve-field, astrometry.cfg が、KStarsから見られない。。。</h2>



<p class="wp-block-paragraph">Flatpak 版 KStars がホスト側の astrometry.net を直接利用できていないようです。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
ls -l /usr/bin/solve-field 2&gt;&amp;1
ls -l /etc/astrometry.cfg 2&gt;&amp;1
'
ls: '/usr/bin/solve-field' にアクセスできません: そのようなファイルやディレクトリはありません
ls: '/etc/astrometry.cfg' にアクセスできません: そのようなファイルやディレクトリはありません</code></pre>



<p class="wp-block-paragraph">Flatpak 版 KStars のアクセス権を確認します。</p>



<pre class="wp-block-code"><code>$ flatpak info --show-permissions org.kde.kstars
&#91;Context]
shared=network;ipc;
sockets=wayland;pulseaudio;fallback-x11;
devices=all;
features=devel;
filesystems=xdg-documents;xdg-pictures;xdg-videos;xdg-config/kdeglobals:ro;~/.cache/sentry;~/.indi;host;

&#91;Session Bus Policy]
com.canonical.AppMenu.Registrar=talk
org.kde.kconfig.notify=talk
org.kde.KGlobalSettings=talk
org.freedesktop.Flatpak=talk
org.freedesktop.secrets=talk
org.kde.kwalletd6=talk

&#91;Environment]
GSCDAT=/app/share/GSC</code></pre>



<p class="wp-block-paragraph">filesystems=&#8230;;host;<br>host が指定されているため、Flatpak 版 KStars にはホスト側のファイルシステムへのアクセス許可が設定されていることが確認できます。</p>



<p class="wp-block-paragraph">/run/host 経由でホスト側のファイルを調べます。<br>/run/host/usr/bin/　を用います。</p>



<p class="wp-block-paragraph">/run/host/usr/bin/ は、Flatpak アプリから Ubuntu 本体の /usr/bin/ を参照するためのパスです。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
ls -l /run/host/usr/bin/solve-field 2&gt;&amp;1
ls -l /run/host/etc/astrometry.cfg 2&gt;&amp;1
'
-rwxr-xr-x 1 nfsnobody nfsnobody 96584  4月  9  2024 /run/host/usr/bin/solve-field
-rw-r--r-- 1 nfsnobody nfsnobody 2589 10月 19 02:52 /run/host/etc/astrometry.cfg
</code></pre>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c \
'/run/host/usr/bin/solve-field --version'
/run/host/usr/bin/solve-field: error while loading shared libraries: libastrometry.so.0: cannot open shared object file: No such file or directory

$ /usr/bin/solve-field --version
0.93</code></pre>



<p class="wp-block-paragraph">solve-field 自体は見つかったものの、起動に必要な共有ライブラリ libastrometry.so.0 を Flatpak の実行環境から読み込めなかったことを示しています。<br>実行環境が読み込めないのが、不具合の原因か？</p>



<p class="wp-block-paragraph">ライブラリ情報は？</p>



<pre class="wp-block-code"><code>$ ldconfig -p | grep libastrometry
	libastrometry.so.0 (libc6,x86-64) =&gt; /lib/x86_64-linux-gnu/libastrometry.so.0</code></pre>



<p class="wp-block-paragraph">Flatpak 内から同じライブラリが見えるか、調べます。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
ls -l /run/host/lib/x86_64-linux-gnu/libastrometry.so.0 2&gt;&amp;1
ls -l /run/host/usr/lib/x86_64-linux-gnu/libastrometry.so.0 2&gt;&amp;1
'
-rw-r--r-- 1 nfsnobody nfsnobody 2143432  4月  9  2024 /run/host/lib/x86_64-linux-gnu/libastrometry.so.0
-rw-r--r-- 1 nfsnobody nfsnobody 2143432  4月  9  2024 /run/host/usr/lib/x86_64-linux-gnu/libastrometry.so.0</code></pre>



<p class="wp-block-paragraph">Flatpak 内からそのライブラリを読み込めるか、確認します。</p>



<pre class="wp-block-code"><code>$ ldd /usr/bin/solve-field | grep -E 'astrometry'
	libastrometry.so.0 =&gt; /lib/x86_64-linux-gnu/libastrometry.so.0 (0x0000708a13000000)</code></pre>



<p class="wp-block-paragraph">Flatpak 内でホスト側の共有ライブラリを読み込めるか、確認します。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
LD_LIBRARY_PATH=/run/host/lib/x86_64-linux-gnu:/run/host/usr/lib/x86_64-linux-gnu \
/run/host/usr/bin/solve-field --version
'
/run/host/usr/bin/solve-field: symbol lookup error: /run/host/lib/x86_64-linux-gnu/libc.so.6: undefined symbol: __nptl_change_stack_perm, version GLIBC_PRIVATE</code></pre>



<p class="wp-block-paragraph">Ubuntu 側の solve-field を Flatpak 内から直接実行する方法は、ライブラリの互換性の問題により、そのままでは使えないようです。</p>



<p class="wp-block-paragraph">Use Position と Use Scale を、Ekos の Scale &amp; Position から外してプレートソルブを行います。</p>



<p class="wp-block-paragraph">望遠鏡の座標や推定画角の誤差がソルブを妨げていないか確認します。<br>KStarsのログ</p>



<pre class="wp-block-code"><code>2026-10-19T15:36:50 Solver aborted.
2026-10-19T15:36:50 Slewing failed.
2026-10-19T15:36:50 Slewing to target coordinates: RA (01h 44m 31s) DEC ( 13° 48' 48").
2026-10-19T15:36:50 Slewing failed.
2026-10-19T15:36:50 Slewing to target coordinates: RA (01h 44m 31s) DEC ( 13° 48' 48").
2026-10-19T15:36:50 Slewing failed.
2026-10-19T15:36:45 Slewing to target coordinates: RA (01h 44m 31s) DEC ( 13° 48' 48").
2026-10-19T15:36:45 Solution coordinates: RA (01h 44m 31s) DEC ( 13° 48' 48") Telescope Coordinates: RA (22h 15m 56s) DEC ( 14° 50' 19") Target Coordinates: RA (23h 56m 00s) DEC ( 180° 00' 00")
2026-10-19T15:36:45 WCS information updated. Images captured from this point forward shall have valid WCS.
2026-10-19T15:36:45 Solver RA (25.76083) DEC (13.67526) Orientation (179.84074) Pixel Scale (0.77730) Parity (neg) PA (-0.15926)
2026-10-19T15:36:45 Solver completed after 1.03 seconds.
2026-10-19T15:36:44 Loaded image was taken on pierside EAST
2026-10-19T15:29:12 World Coordinate System (WCS) is enabled.</code></pre>



<p class="wp-block-paragraph">Flatpak 内で使えるソルバーを調べます。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
echo "=== /app/bin ==="
ls -l /app/bin/solve-field 2&gt;&amp;1

echo "=== Flatpak内のPATH ==="
echo "$PATH"

echo "=== solve-fieldを検索 ==="
find /app -type f -name solve-field 2&gt;/dev/null
'
=== /app/bin ===
ls: '/app/bin/solve-field' にアクセスできません: そのようなファイルやディレクトリはありません
=== Flatpak内のPATH ===
/app/bin:/usr/bin
=== solve-fieldを検索 ===</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">Flatpak 内の /app/bin/solve-field：存在しない<br>Flatpak 内の PATH：/app/bin:/usr/bin<br>/app 内を検索しても solve-field は見つからない<br>Ubuntu 本体には /usr/bin/solve-field が存在する<br>ホスト側の solve-field を Flatpak 内から直接実行すると、GLIBC の互換性エラーが発生する</p>



<p class="wp-block-paragraph">Flatpak 版 KStars の環境には、外部の Astrometry.net 実行ファイルが同梱されていません。</p>
</div>



<p class="wp-block-paragraph">Flatpak 内から wcsinfo を実行します。</p>



<pre class="wp-block-code"><code>$ flatpak run --command=sh org.kde.kstars -c '
/run/host/usr/bin/wcsinfo 2&gt;&amp;1 | head -20
'
/run/host/usr/bin/wcsinfo: error while loading shared libraries: libgsl.so.27: cannot open shared object file: No such file or directory</code></pre>



<h2 class="wp-block-heading">プレートソルブ / 不具合を追う</h2>



<p class="wp-block-paragraph">KStars　バージョン 3.8.5 Stable</p>



<p class="wp-block-paragraph">プレートソルブ途中で、クラッシュが多発するようになった。</p>



<pre class="wp-block-code"><code>$ ls -lht /var/crash/
合計 40K
-rw-r--r-- 1 root whoopsie   0 10月 18 22:31 _usr_share_apport_apport.0.upload
-rw-r----- 1 root whoopsie 39K 10月 18 22:31 _usr_share_apport_apport.0.crash</code></pre>



<pre class="wp-block-code"><code>$ coredumpctl list
TIME                         PID  UID  GID SIG     COREFILE EXE               SIZE
Sun 2026-10-18 22:30:57 JST 3958 1000 1000 SIGSEGV present  /app/bin/kstars 223.6M</code></pre>



<pre class="wp-block-code"><code>$ coredumpctl info kstars
           PID: 3958 (kstars)
           UID: 1000 (USERNAME)
           GID: 1000 (USERNAME)
        Signal: 11 (SEGV)
     Timestamp: Sun 2026-10-18 22:30:49 JST (9min ago)
  Command Line: kstars
    Executable: /app/bin/kstars
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.kstars-3947.scope
          Unit: user@1000.service
     User Unit: app-flatpak-org.kde.kstars-3947.scope
         Slice: user-1000.slice
     Owner UID: 1000 (USERNAME)
       Boot ID: fc59a2c2dc594283b13a5c649180493c
    Machine ID: 74e8e02918d240c7a288b206ca440774
      Hostname: ah53s
       Storage: /var/lib/systemd/coredump/core.kstars.1000.fc59a2c2dc594283b13a5c649180493c.3958.1792330249000000.zst (present)
  Size on Disk: 223.6M
       Message: Process 3958 (kstars) of user 1000 dumped core.
                
                Stack trace of thread 83:
                #0  0x000073f8c82f2a80 n/a (/app/lib/libstellarsolver6.so.2.8 + 0xcca80)
                #1  0x000073f8c82a4a8e n/a (/app/lib/libstellarsolver6.so.2.8 + 0x7ea8e)
                #2  0x000073f8c829a527 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74527)
                #3  0x000073f8c829a063 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74063)
                #4  0x000073f8c829aa87 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74a87)
                #5  0x000073f8c829adf2 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74df2)
                #6  0x000073f8c829af19 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74f19)
                #7  0x000073f8c829c278 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x76278)
                #8  0x000073f8c8297042 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x71042)
                #9  0x000073f8c82986b7 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x726b7)
                #10 0x000073f8c829684a n/a (/app/lib/libstellarsolver6.so.2.8 + 0x7084a)
                #11 0x000073f8c8253be8 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x2dbe8)
                #12 0x000073f8c8258218 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x32218)
                #13 0x000073f8c658c3d4 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.10.3 + 0x38c3d4)
                #14 0x000073f8c409b56a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9a56a)
                #15 0x000073f8c411ee94 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x11de94)
                ELF object binary architecture: AMD x86-64</code></pre>



<pre class="wp-block-code"><code>$ coredumpctl debug 3958
           PID: 3958 (kstars)
           UID: 1000 (USERNAME)
           GID: 1000 (USERNAME)
        Signal: 11 (SEGV)
     Timestamp: Sun 2026-10-18 22:30:49 JST (9min ago)
  Command Line: kstars
    Executable: /app/bin/kstars
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.kstars-3947.scope
          Unit: user@1000.service
     User Unit: app-flatpak-org.kde.kstars-3947.scope
         Slice: user-1000.slice
     Owner UID: 1000 (USERNAME)
       Boot ID: fc59a2c2dc594283b13a5c649180493c
    Machine ID: 74e8e02918d240c7a288b206ca440774
      Hostname: ah53s
       Storage: /var/lib/systemd/coredump/core.kstars.1000.fc59a2c2dc594283b13a5c649180493c.3958.1792330249000000.zst (present)
  Size on Disk: 223.6M
       Message: Process 3958 (kstars) of user 1000 dumped core.
                
                Stack trace of thread 83:
                #0  0x000073f8c82f2a80 n/a (/app/lib/libstellarsolver6.so.2.8 + 0xcca80)
                #1  0x000073f8c82a4a8e n/a (/app/lib/libstellarsolver6.so.2.8 + 0x7ea8e)
                #2  0x000073f8c829a527 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74527)
                #3  0x000073f8c829a063 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74063)
                #4  0x000073f8c829aa87 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74a87)
                #5  0x000073f8c829adf2 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74df2)
                #6  0x000073f8c829af19 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x74f19)
                #7  0x000073f8c829c278 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x76278)
                #8  0x000073f8c8297042 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x71042)
                #9  0x000073f8c82986b7 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x726b7)
                #10 0x000073f8c829684a n/a (/app/lib/libstellarsolver6.so.2.8 + 0x7084a)
                #11 0x000073f8c8253be8 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x2dbe8)
                #12 0x000073f8c8258218 n/a (/app/lib/libstellarsolver6.so.2.8 + 0x32218)
                #13 0x000073f8c658c3d4 n/a (/usr/lib/x86_64-linux-gnu/libQt6Core.so.6.10.3 + 0x38c3d4)
                #14 0x000073f8c409b56a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x9a56a)
                #15 0x000073f8c411ee94 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x11de94)
                ELF object binary architecture: AMD x86-64

GNU gdb (Ubuntu 15.1-1ubuntu1~24.04.1) 15.1
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later &lt;http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
&lt;https://www.gnu.org/software/gdb/bugs/&gt;.
Find the GDB manual and other documentation resources online at:
    &lt;http://www.gnu.org/software/gdb/documentation/&gt;.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
/app/bin/kstars: そのようなファイルやディレクトリはありません.

This GDB supports auto-downloading debuginfo from the following URLs:
  &lt;https://debuginfod.ubuntu.com&gt;
Enable debuginfod for this session? (y or &#91;n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading executable for /app/bin/kstars
Download failed: タイマが破棄されました.  Continuing without executable for /app/bin/kstars.                                      

warning: Can't open file /app/bin/kstars during file-backed mapping note processing

warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing
--Type &lt;RET&gt; for more, q to quit, c to continue without paging--q
Quit
(gdb) set pagination off
(gdb) thread apply all bt
(gdb) q</code></pre>



<p class="wp-block-paragraph">Signal: 11 (SEGV)<br>KStars のプロセスが SIGSEGV（セグメンテーション違反） というシグナルを受けて終了した。</p>



<p class="wp-block-paragraph">Stack trace of thread 83:<br>#0 から #12 まで、すべて libstellarsolver6.so.2.8 内のアドレスを指しています。</p>



<h2 class="wp-block-heading">ASTAPを使う</h2>



<p class="wp-block-paragraph">KStarsのプレートソルブには次の設定があります。</p>



<p class="wp-block-paragraph">Source Extraction Method: Internal SEP<br>Solving Method: Internal Solver</p>



<p class="wp-block-paragraph">Internal SEP は、画像から星を検出する方法です。<br>Internal Solver は、検出された星の情報を使ってプレートソルブを行う方法です。</p>



<p class="wp-block-paragraph">他の方法には、次があります。</p>



<p class="wp-block-paragraph">StellarSolver<br>ASTAP<br>Astrometry.net</p>



<p class="wp-block-paragraph">ASTAPを使ってみます。<br>Internal SEP と Internal Solver を用い、クラッシュが多発するようになった場合の回避策として。</p>



<h3 class="wp-block-heading">KStarsを最新版に更新する</h3>



<h4 class="wp-block-heading">更新マスクを解除とその確認</h4>



<pre class="wp-block-code"><code>$ flatpak mask --user --remove org.kde.kstars

$ flatpak mask --user
No masked patterns</code></pre>



<h4 class="wp-block-heading">KStarsを最新版に更新する</h4>



<pre class="wp-block-code"><code>$ flatpak update --user org.kde.kstars
Looking for updates…

        ID                     Branch         Op         Remote         Download
 1.     org.kde.kstars         stable         u          flathub        &lt; 480.1&nbsp;MB

Proceed with these changes to the user installation? &#91;Y/n]:Y

ID                     Branch         Op         Remote         Download
 1. &#91;✓] org.kde.kstars         stable         u          flathub        180.2&nbsp;MB / 480.1&nbsp;MB

Updates complete.</code></pre>



<h4 class="wp-block-heading">Linux用のASTAP</h4>



<p class="wp-block-paragraph">ASTAP本体と星データベースが配布されています。<br><a rel="noopener" target="_blank" href="https://www.hnsky.org/astap.htm">https://www.hnsky.org/astap.htm</a></p>


<a rel="noopener" target="_blank" href="https://www.hnsky.org/astap.htm" title="ASTAP, Astrometric Stacking Program" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img fetchpriority="high" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fwww.hnsky.org%2Fastap.htm?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">ASTAP, Astrometric Stacking Program</div><div class="blogcard-snippet external-blogcard-snippet">ASTAP, ASTrometric Stacking Program, astrometric solver, stacking of images, photometry and FITS viewer.</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img decoding="async" src="https://www.google.com/s2/favicons?domain=https://www.hnsky.org/astap.htm" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">www.hnsky.org</div></div></div></div></a>


<p class="wp-block-paragraph">今回はUbuntu 24.04のFlatpak版KStarsを使用しているため、Linux用のASTAPを選びます。</p>



<h4 class="wp-block-heading">APTで利用できるASTAPの情報を確認</h4>



<pre class="wp-block-code"><code>$ apt policy astap
astap:
  インストールされているバージョン: (なし)
  候補:               2024.01.16-1
  バージョンテーブル:
     2024.01.16-1 500
        500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages</code></pre>



<p class="wp-block-paragraph">ASTAP をインストールします。</p>



<pre class="wp-block-code"><code>sudo apt update
sudo apt install astap
apt show astap</code></pre>



<h4 class="wp-block-heading">StellarSolver Options</h4>



<p class="wp-block-paragraph">KStars、StellarSolver Optionsにある、Solving Methodを &#8220;Local ASTAP&#8221;に指定します。</p>



<h4 class="wp-block-heading">アライメントログの有効化（原因の特定）</h4>



<p class="wp-block-paragraph">Ekos画面上、左端の「ドライバーとスパナアイコン」、[Setup] タブ <br>[Setup] タブ → [Logs] で「Alignment Logging」を有効にしてください。</p>



<h4 class="wp-block-heading">星図データを導入</h4>



<p class="wp-block-paragraph"><a rel="noopener" target="_blank" href="https://www.hnsky.org/astap.htm">https://www.hnsky.org/astap.htm</a><br>こちらから、D50 (debian)<br>d50_star_database.deb　をダウンロードします。</p>



<pre class="wp-block-code"><code>$ sudo apt install ./d50_star_database.deb</code></pre>



<p class="wp-block-paragraph">インストールを確認します。</p>



<pre class="wp-block-code"><code>$ ls -lh /opt/astap
合計 911M
-rw------- 1 root root  34K  9月 29  2023 'acknowledgement of databases.txt'
-rw-r--r-- 1 root root 510K  3月 15  2023  d50_0101.1476</code></pre>



<h4 class="wp-block-heading">ASTAPを指定</h4>



<pre class="wp-block-code"><code>KStars 設定、External &amp; Online Programs
ASTAP: ASTAP Binary: 
/usr/bin/astap を指定します。</code></pre>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://globe3.ddns.net/wp/configuring-flatpak-version-kstars/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PI.N.S.を、x86_64 GUN/Linux で使うには</title>
		<link>https://globe3.ddns.net/wp/porting-pins-to-x86_64-gun-linux/</link>
					<comments>https://globe3.ddns.net/wp/porting-pins-to-x86_64-gun-linux/#respond</comments>
		
		<dc:creator><![CDATA[minmin]]></dc:creator>
		<pubDate>Fri, 04 Sep 2026 04:15:34 +0000</pubDate>
				<category><![CDATA[INDI-Library]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<guid isPermaLink="false">https://globe3.ddns.net/wp/?p=5370</guid>

					<description><![CDATA[頼りになる星仲間に紹介されたので、使ってみよう。https://touch-n-stars.eu/ NINAワークフローを基盤とした2つのオープンソースプロジェクト：スマートフォンやタブレット向けの「タッチファースト」対 [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">頼りになる星仲間に紹介されたので、使ってみよう。<br><a rel="noopener" target="_blank" href="https://touch-n-stars.eu/">https://touch-n-stars.eu/</a></p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">NINAワークフローを基盤とした2つのオープンソースプロジェクト：スマートフォンやタブレット向けの「タッチファースト」対応コンパニオンアプリと、より小型のRaspberry Piイメージングコンピュータを実現するためのLinuxに特化したアプローチです。<br><a rel="noopener" target="_blank" href="https://touch-n-stars.eu/">https://touch-n-stars.eu/</a></p>
</blockquote>



<p class="wp-block-paragraph">こちらには、2つのプロジェクトがあり、その一つが<br>『Raspberry Piをはじめとするコンパクトなシステムでの画像取得を目的とした、Linuxに特化したN.I.N.A.のフォーク版です。PINSは、より携帯性に優れ、低消費電力のフィールドコンピュータを試してみたいユーザー向けのものです。』</p>



<p class="wp-block-paragraph">Raspberry PiやミニPCを天体画像撮影に使う選択肢に、N.I.N.Aを挙げています。</p>



<p class="has-text-align-right wp-block-paragraph">「あら、raspberry piが手元に無い。。。」</p>



<p class="wp-block-paragraph">では、GUN/Linux, Ubuntu PCの画面上に、N.I.N.Aを表示させてみましょう。<br>ついでに、raspberry pi固有の機能などは全て無視して、最低限の動作が行えるか、試してみます。</p>



<p class="wp-block-paragraph">「それって、N.I.N.Aの選択幅を広げられるってこと？」</p>



<p class="has-text-align-right wp-block-paragraph">『ん〜〜、迷いを広げるってことにならないかい&#8230;』</p>



<p class="wp-block-paragraph">Ubuntu 26.04 / x86_64 Linux上でビルドを試します。頓挫もおおいにありえる。</p>



<p class="wp-block-paragraph">PINS GitHub<br><a rel="noopener" target="_blank" href="https://github.com/nitr57/pins">https://github.com/nitr57/pins</a></p>



<p class="wp-block-paragraph">開発版を使うのではなく、<br>x86_64 LinuxでPINSを最小構成でビルドできるか確認したいので、<br>develop ブランチを取得します。x86_64 Linux 対応の実装が develop にあるようです。</p>



<p class="wp-block-paragraph">Package pinsdaemon ASTAP data-link helper<br>build-and-install-pins-x64.sh<br><a rel="noopener" target="_blank" href="https://github.com/nitr57/pins/blob/develop/build-and-install-pins-x64.sh">https://github.com/nitr57/pins/blob/develop/build-and-install-pins-x64.sh</a><br>有り難いことに、ビルドスクリプトが用意されています。</p>



<p class="wp-block-paragraph">PI.N.S. (PI &#8216;N&#8217; Stars)の案内があります。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">PI.N.S. (PI 『N』 Stars)<br>このリポジトリには、オリジナルの N.I.N.A. &#8211; Nighttime Imaging 『N』 Astronomy イメージングソフトウェアの Linux 向け移植版およびフォークである PI.N.S. (PI 『N』 Stars) のソースコードが含まれています。<br><a rel="noopener" target="_blank" href="https://github.com/nitr57/pins/tree/develop">https://github.com/nitr57/pins/tree/develop</a></p>
</blockquote>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">PI.N.S.は、N.I.N.A.の強力な機能をLinuxユーザーに提供することを目的としています。</p>
</blockquote>



<p class="wp-block-paragraph">とても有り難いコメントです。</p>



<p class="wp-block-paragraph">などと、順調な書き出しですが、それぞれのソースに、私の意識がロックオンされて、<br>build-and-install-pins-x64.sh が用意されている事に、丸々一日、気が付かないとの落ちが。。。</p>



<p class="wp-block-paragraph">これはそんな者の、PI.N.Sビルド、インストール録です。</p>



<p class="has-text-align-right wp-block-paragraph">「思い込みって意識が狭くなりますね」</p>



<h2 class="wp-block-heading">PINSをclone</h2>



<pre class="wp-block-code"><code>git clone --branch develop --recurse-submodules https://github.com/nitr57/pins.git

Submodule path 'NINA.Plugins/PolarAlignment/NINA.Plugins.PolarAlignment.Test/External': checked out 'c43065ee856ad8a5f1edbd9e043c520872570e33'
Submodule path 'NINA.Plugins/Touch-N-Stars': checked out '23f08d5fc14421e9f42cf2d9e27981e49fc4bb8e'
Submodule path 'NINA.Plugins/joko.nina.plugins': checked out '8f40cc9c31c406f77b314b1a43b2746b85780142'
Submodule path 'NINA.Plugins/nina.plugin.orbuculum': checked out 'b0fa902093943577cb38fc706faa5dc0f593b368'
Submodule path 'NINA.Plugins/nina.plugin.phd2tools': checked out '7ab92e2daf7f240f6e9e01a46468f5f26e1df0e8'
Submodule path 'NINA.Plugins/ninaAPI': checked out 'd96ada2b67f4c979e4708046ba0803c0ae22b158'
Submodule path 'Touch-N-Stars': checked out 'd43bceb6d24956beb35097267b7c28712d8ccdcc'</code></pre>



<p class="wp-block-paragraph">develop ブランチのPINS本体 + ブランチが指定しているsubmoduleも取得します。</p>



<pre class="wp-block-code"><code>### https://github.com/nitr57/pins.git

### git clone --branch develop https://github.com/nitr57/pins.git
cd pins

git branch --show-current
develop

作業ツリーとsubmoduleの状態を確認
git status
ブランチ develop
Your branch is up to date with 'origin/develop'.
nothing to commit, working tree clean

git submodule status
 6c3c07d9a5607cf8a24d478f70161d1a52e4ddf9 NINA.Plugins/LiveStack (6c3c07d)
 518edfe4b7b72ba149ac728fd90ebd3167895e6a NINA.Plugins/NINA.Joko.Plugin.TenMicron (518edfe)
 be1cf505272a5520e4938187631182777d9388c2 NINA.Plugins/PolarAlignment (be1cf50)
 23f08d5fc14421e9f42cf2d9e27981e49fc4bb8e NINA.Plugins/Touch-N-Stars (23f08d5)
 8f40cc9c31c406f77b314b1a43b2746b85780142 NINA.Plugins/joko.nina.plugins (8f40cc9)
 b0fa902093943577cb38fc706faa5dc0f593b368 NINA.Plugins/nina.plugin.orbuculum (b0fa902)
 7ab92e2daf7f240f6e9e01a46468f5f26e1df0e8 NINA.Plugins/nina.plugin.phd2tools (7ab92e2)
 d96ada2b67f4c979e4708046ba0803c0ae22b158 NINA.Plugins/ninaAPI (remotes/origin/fix/single-29-gd96ada2)
fatal: no submodule mapping found in .gitmodules for path 'NINA.Plugins/pins.plugin'</code></pre>



<p class="wp-block-paragraph">fatal: no submodule mapping found in .gitmodules for path &#8216;NINA.Plugins/pins.plugin&#8217;</p>



<pre class="wp-block-code"><code>### 現在のリポジトリで管理対象として認識しているファイルを表示させます
git ls-files --stage NINA.Plugins/pins.plugin
160000 526db72c0aaf5850920188f44a8be2289aec38aa 0	NINA.Plugins/pins.plugin

ls -ld NINA.Plugins/pins.plugin
drwxrwxr-x 2 USER USER 4096 Sep  7 09:07 NINA.Plugins/pins.plugin

git config --file .gitmodules --get-regexp '^submodule\.'
submodule.Touch-N-Stars.path Touch-N-Stars
submodule.Touch-N-Stars.url https://github.com/Touch-N-Stars/Touch-N-Stars.git
submodule.Touch-N-Stars.branch pins
submodule.NINA.Plugins/ninaAPI.path NINA.Plugins/ninaAPI
submodule.NINA.Plugins/ninaAPI.url https://github.com/nitr57/ninaAPI.git
submodule.NINA.Plugins/ninaAPI.branch dev
submodule.NINA.Plugins/Touch-N-Stars.path NINA.Plugins/Touch-N-Stars
submodule.NINA.Plugins/Touch-N-Stars.url https://github.com/nitr57/N.I.N.A-Plugin-for-Touch-N-Stars.git
submodule.NINA.Plugins/Touch-N-Stars.branch main
submodule.NINA.Plugins/LiveStack.path NINA.Plugins/LiveStack
submodule.NINA.Plugins/LiveStack.url https://github.com/nitr57/nina.plugin.livestack
submodule.NINA.Plugins/LiveStack.branch main
submodule.NINA.Plugins/PolarAlignment.path NINA.Plugins/PolarAlignment
submodule.NINA.Plugins/PolarAlignment.url https://github.com/nitr57/nina.plugin.polaralignment.git
submodule.NINA.Plugins/PolarAlignment.branch master
submodule.NINA.Plugins/joko.nina.plugins.path NINA.Plugins/joko.nina.plugins
submodule.NINA.Plugins/joko.nina.plugins.url https://github.com/nitr57/joko.nina.plugins.git
submodule.NINA.Plugins/joko.nina.plugins.branch develop
submodule.NINA.Plugins/NINA.Joko.Plugin.TenMicron.path NINA.Plugins/NINA.Joko.Plugin.TenMicron
submodule.NINA.Plugins/NINA.Joko.Plugin.TenMicron.url https://github.com/nitr57/NINA.Joko.Plugin.TenMicron.git
submodule.NINA.Plugins/NINA.Joko.Plugin.TenMicron.branch develop
submodule.NINA.Plugins/nina.plugin.orbuculum.path NINA.Plugins/nina.plugin.orbuculum
submodule.NINA.Plugins/nina.plugin.orbuculum.url https://github.com/nitr57/nina.plugin.orbuculum.git
submodule.NINA.Plugins/nina.plugin.orbuculum.branch master
submodule.NINA.Plugins/nina.plugin.phd2tools.path NINA.Plugins/nina.plugin.phd2tools
submodule.NINA.Plugins/nina.plugin.phd2tools.url https://github.com/nitr57/nina.plugin.phd2tools.git</code></pre>



<p class="wp-block-paragraph">Gitのgitlink（submodule）として記録されているのに、.gitmodules にその定義が存在しない状態になってる。</p>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh では、&#8221;pins.plugin&#8221;は何してるかな？</p>



<pre class="wp-block-code"><code>grep -n "pins.plugin" build-and-install-pins-x64.sh

225:    "pins-plugin|https://github.com/nitr57/pins.plugin|"
935:  clone_repo_fresh "https://github.com/nitr57/pins.plugin" "NINA.Plugins/pins.plugin"
</code></pre>



<p class="wp-block-paragraph">935行目には、ビルドスクリプトから別途cloneする設計らしいです。<br>pins.plugin を、.gitmodules に登録されたsubmoduleとして取得するのではない。</p>



<h2 class="wp-block-heading">build-and-install-pins-x64.sh を見る</h2>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh を見てみると、</p>



<pre class="wp-block-code"><code>### Ubuntu/Debian x86_64パッケージアーキテクチャamd64向き
TARGET_RUNTIME="${TARGET_RUNTIME:-linux-x64}"

### .NETは net10.0, SDK 10.0.400?
PLUGIN_TARGET_FRAMEWORK="${PLUGIN_TARGET_FRAMEWORK:-net10.0}"

### スクリプト自身がPINSをcloneする
PINS_REPO_URL="${PINS_REPO_URL:-https://github.com/acocalypso/pins.git}"
PINS_REPO_BRANCH="${PINS_REPO_BRANCH:-develop}"
PINS_WORKDIR="${PINS_WORKDIR:-$TARGET_HOME/pins-build-src}"
AUTO_CLONE_PINS_REPO="${AUTO_CLONE_PINS_REPO:-true}"

### INDIも（xisf）ビルドする
INDI_VERSION="${INDI_VERSION:-2.1.9}"
INDI_ENABLE_XISF="${INDI_ENABLE_XISF:-true}"</code></pre>



<p class="wp-block-paragraph">CMake、Ninja、Make、automake、curl、wgetなどもスクリプトで取得するようだ。</p>



<pre class="wp-block-code"><code>sed -n '300,470p' build-and-install-pins-x64.sh

install_build_prerequisites() {
  log "Installing system build prerequisites"

  run_as_root apt-get update
  run_as_root apt-get install -y --no-install-recommends \
    apt-transport-https \
    autoconf \
    autoconf-archive \
    automake \
    build-essential \
    ca-certificates \
    cdbs \
    cmake \
    curl \
    debhelper \
    devscripts \
    default-jre-headless \
    dkms \
    dpkg-dev \
    equivs \
    fakeroot \
    fxload \
    gettext \
    git \
    git-lfs \
    gnupg \
    libavdevice-dev \
    libboost-regex-dev \
    libboost-all-dev \
    libcfitsio-dev \
    libczmq-dev \
    libcurl4-gnutls-dev \
    libdc1394-dev \
    libeigen3-dev \
    libev-dev \
    libfftw3-dev \
    libftdi1-dev \
    libftdi-dev \
    libgphoto2-dev \
    libgps-dev \
    libgsl-dev \
    libgtest-dev \
    libgmock-dev \
    libhidapi-dev \
    libicu-dev \
    libjpeg-dev \
    libjsoncpp-dev \
    libkrb5-dev \
    liblimesuite-dev \
    libnova-dev \
    libopencv-dev \
    libpng-dev \
    libraw-dev \
    librtlsdr-dev \
    libssl-dev \
    libtesseract-dev \
    libtheora-dev \
    libtiff-dev \
    libtool \
    libudev-dev \
    libusb-1.0-0-dev \
    libusb-dev \
    libv4l-dev \
    libwxgtk3.2-dev \
    libx11-dev \
    libxisf-dev \
    libzstd-dev \
    libzmq3-dev \
    libwebp-dev \
    ninja-build \
    nlohmann-json3-dev \
    pkg-config \
    rsync \
    unzip \
    wget \
    wx-common \
    wx3.2-i18n \
    zip \
    zlib1g-dev
}</code></pre>



<p class="wp-block-paragraph">linux-x64<br>├── INDI 2.1.9<br>├── PHD2<br>├── OpenCV 4.11.0<br>├── OpenCvSharp<br>├── ASTAP<br>└── 各種NINA plugin<br>それぞれを、build-and-install-pins-x64.shからビルドしているらしい。</p>



<pre class="wp-block-code"><code>sed -n '800,880p' build-and-install-pins-x64.sh
  fi

  &#91;&#91; -f "$package_so" ]] || fail "OpenCvSharp runtime library not found: $package_so"

  local stage_dir="NINA/External/$TARGET_RUNTIME"
  mkdir -p "$stage_dir"
  cp -f "$package_so" "$stage_dir/libOpenCvSharpExtern.so"
  chmod 755 "$stage_dir/libOpenCvSharpExtern.so"

  log "Staged OpenCvSharp runtime library at: $stage_dir/libOpenCvSharpExtern.so"
}

install_dotnet_10() {
  local dotnet_ok="false"

  if command -v dotnet &gt;/dev/null 2&gt;&amp;1; then
    if dotnet --list-sdks | grep -q '^10\.'; then
      dotnet_ok="true"
    fi
  fi

  if &#91;&#91; "$dotnet_ok" == "true" ]]; then
    log ".NET 10 SDK already available"
    return
  fi

  log "Installing .NET 10 SDK"
  source /etc/os-release
  local ms_repo_deb
  ms_repo_deb="$(mktemp)"

  if ! wget -q "https://packages.microsoft.com/config/ubuntu/${VERSION_ID}/packages-microsoft-prod.deb" -O "$ms_repo_deb"; then
    fail "Failed to download Microsoft package feed for Ubuntu ${VERSION_ID}"
  fi

  run_as_root dpkg -i "$ms_repo_deb"
  rm -f "$ms_repo_deb"

  run_as_root apt-get update
  run_as_root apt-get install -y dotnet-sdk-10.0
}

install_node_22() {
  local node_ok="false"

  if command -v node &gt;/dev/null 2&gt;&amp;1; then
    local node_major
    node_major="$(node -p 'process.versions.node.split(".")&#91;0]')"
    if &#91;&#91; "$node_major" == "22" ]]; then
      node_ok="true"
    fi
  fi

  if &#91;&#91; "$node_ok" == "true" ]]; then
    log "Node.js 22 already available"
    return
  fi

  log "Installing Node.js 22"
  local nodesource_script
  nodesource_script="$(mktemp)"
  curl -fsSL https://deb.nodesource.com/setup_22.x -o "$nodesource_script"
  run_as_root bash "$nodesource_script"
  rm -f "$nodesource_script"

  run_as_root apt-get install -y nodejs
}

print_tool_versions() {
  log "Toolchain versions"
  dotnet --info
  node --version
  npm --version
}

update_submodules_except_external() {
  log "Updating git submodules (excluding NINA/External)"

  git lfs install

  local excluded_path="NINA/External"</code></pre>



<p class="wp-block-paragraph">.NET SDK、Node.js 22もスクリプトが導入するようです。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">build-and-install-pins-x64.shのみ単体でダウンロードして実行すると、PINS環境構築ができそうです。ただし、一箇所の変更が必要かもしれません。<br>変更前：<br>PINS_REPO_URL=&#8221;${PINS_REPO_URL:-https://github.com/acocalypso/pins.git}&#8221;</p>



<p class="wp-block-paragraph">変更後：<br>PINS_REPO_URL=&#8221;${PINS_REPO_URL:-https://github.com/nitr57/pins.git}&#8221;</p>
</div>



<p class="wp-block-paragraph">スクリプトが行う、処理順を全体像として確認します。</p>



<pre class="wp-block-code"><code>grep -nE '^&#91;a-zA-Z_]&#91;a-zA-Z0-9_]*\(\)' build-and-install-pins-x64.sh

13:log() {
17:warn() {
21:fail() {
26:is_truthy() {
33:run_as_root() {
43:require_file() {
48:has_required_repo_layout() {
57:check_required_repo_layout() {
159:record_built_deb() {
174:get_remote_sha() {
191:compute_source_fingerprint() {
255:load_previous_build_state() {
270:try_reuse_successful_build() {
309:save_successful_build_state() {
325:install_bootstrap_tools_if_needed() {
346:ensure_repo_root() {
379:install_build_prerequisites() {
460:get_opencv_version() {
499:get_local_opencv_pkgconfig_version() {
522:opencv_matches_required_version() {
532:activate_opencv_environment() {
565:build_and_install_opencv_required_version() {
600:ensure_opencv_required_version() {
650:activate_local_libxisf_environment() {
703:get_libxisf_header_candidate() {
718:libxisf_supports_required_api() {
727:build_and_install_libxisf() {
748:ensure_modern_libxisf_if_enabled() {
778:stage_opencvsharp_runtime_from_nuget() {
812:install_dotnet_10() {
842:install_node_22() {
868:print_tool_versions() {
875:update_submodules_except_external() {
909:clone_repo_fresh() {
922:clone_workflow_plugin_repositories() {
938:build_and_install_libgpiod() {
958:populate_external_bundle() {
1014:determine_versions() {
1028:build_core_pins_package() {
1146:build_pinsdaemon_package() {
1202:build_wandereretasdk_package() {
1251:find_assembly_info() {
1266:build_plugin_deb() {
1370:prepare_touch_n_stars_frontend() {
1388:prepare_pins_plugin_sdks() {
1425:build_plugins() {
1484:build_indi_debian_packages() {
1733:configure_phd2_service_file() {
1762:build_phd2_package() {
1908:create_firmware_bundle() {
1930:install_built_packages() {
1978:setup_framingassistant_cache() {
2011:setup_astap() {
2048:setup_runtime_prerequisites() {
2083:print_summary() {
2096:main() {</code></pre>



<p class="wp-block-paragraph">基本処理 (x86_64 / amd64確認) → PINSソース確認 →  <code>ビルド状態確認</code>(前回成功ビルドの再利用判定) → ビルド環境構築( build-essential, cmake, ninja, 各種lib*-dev) → OpenCVビルド、libXISFビルド、OpenCvSharp取得 / .NET導入 / Node.js導入 → PINS関連コンポーネント → N.I.N.A. Pluginビルド → INDI 2.1.9ビルド → PHD2ビルド → ビルドされた.debをインストール → ASTAP / Framing Assistant等の実行環境設定<br>との流れで処理するようです。</p>



<p class="wp-block-paragraph">PINSソースを確認 → ビルド環境を構築 → ネイティブ依存関係を整備 → .NET/Node環境を整備 → submodule/Pluginを取得 → PINS/N.I.N.A./INDI/PHD2等をビルド → インストール</p>



<h2 class="wp-block-heading">build-and-install-pins-x64.sh を使う</h2>



<p class="wp-block-paragraph">だいぶ行き届いたお膳立てが、このスクリプトは成されています。</p>



<pre class="wp-block-code"><code>git status
ブランチ develop
Your branch is up to date with 'origin/develop'.
nothing to commit, working tree clean</code></pre>



<p class="wp-block-paragraph">インストールスクリプトを使います。</p>



<pre class="wp-block-code"><code>### 実行権限を付ける
chmod +x build-and-install-pins-x64.sh
### スクリプトを動かす
./build-and-install-pins-x64.sh</code></pre>



<p class="wp-block-paragraph">インストールログ</p>



<p class="wp-block-paragraph">Ubuntu 26.04クリーンインストール直後</p>



<pre class="wp-block-code"><code>以下のパッケージが新たにインストールされます:
  apt-transport-https autoconf autoconf-archive automake autopoint autotools-dev build-essential bzip2 ca-certificates-java cdbs cfortran cmake cmake-data comerr-dev cpp-16 cpp-16-x86-64-linux-gnu curl debhelper debugedit
  default-jre-headless devscripts dh-autoreconf dh-strip-nondeterminism dkms dpkg-dev dwz equivs fakeroot fxload g++ g++-15 g++-15-x86-64-linux-gnu g++-x86-64-linux-gnu gcc gcc-15 gcc-15-x86-64-linux-gnu gcc-16 gcc-16-x86-64-linux-gnu
  gcc-x86-64-linux-gnu gdal-data gdal-plugins gettext gfortran-16 gfortran-16-x86-64-linux-gnu git-lfs googletest icu-devtools intltool-debian java-common krb5-multidev libacl1-dev libadios2-mpi-auxiliary-2.11 libadios2-mpi-c++-2.11
  libadios2-mpi-c-2.11 libadios2-mpi-core-2.11 libadios2-mpi-plugins libaec0 libamd-comgr3 libamdhip64-7 libarchive-dev libarchive-zip-perl libarmadillo15 libarpack2t64 libattr1-dev libavcodec-dev libavdevice-dev libavdevice62
  libavfilter-dev libavformat-dev libavif16 libavutil-dev libb-hooks-op-check-perl libblas3 libblosc1 libblosc2-7 libboost-all-dev libboost-atomic-dev libboost-atomic1.90-dev libboost-atomic1.90.0 libboost-charconv1.90-dev
  libboost-charconv1.90.0 libboost-chrono-dev libboost-chrono1.90-dev libboost-chrono1.90.0 libboost-container-dev libboost-container1.90-dev libboost-container1.90.0 libboost-context-dev libboost-context1.90-dev libboost-context1.90.0
  libboost-coroutine-dev libboost-coroutine1.90-dev libboost-coroutine1.90.0 libboost-date-time-dev libboost-date-time1.90-dev libboost-date-time1.90.0 libboost-dev libboost-exception-dev libboost-exception1.90-dev libboost-fiber-dev
  libboost-fiber1.90-dev libboost-fiber1.90.0 libboost-filesystem-dev libboost-filesystem1.90-dev libboost-filesystem1.90.0 libboost-graph-dev libboost-graph-parallel-dev libboost-graph-parallel1.90-dev libboost-graph-parallel1.90.0
  libboost-graph1.90-dev libboost-graph1.90.0 libboost-iostreams-dev libboost-iostreams1.90-dev libboost-iostreams1.90.0 libboost-json-dev libboost-json1.90-dev libboost-json1.90.0 libboost-locale-dev libboost-locale1.90-dev
  libboost-locale1.90.0 libboost-log-dev libboost-log1.90-dev libboost-log1.90.0 libboost-math-dev libboost-math1.90-dev libboost-math1.90.0 libboost-mpi-dev libboost-mpi-python-dev libboost-mpi-python1.90-dev libboost-mpi-python1.90.0
  libboost-mpi1.90-dev libboost-mpi1.90.0 libboost-nowide-dev libboost-nowide1.90-dev libboost-nowide1.90.0 libboost-numpy-dev libboost-numpy1.90-dev libboost-numpy1.90.0 libboost-process-dev libboost-process1.90-dev
  libboost-process1.90.0 libboost-program-options-dev libboost-program-options1.90-dev libboost-program-options1.90.0 libboost-python-dev libboost-python1.90-dev libboost-python1.90.0 libboost-random-dev libboost-random1.90-dev
  libboost-random1.90.0 libboost-regex-dev libboost-regex1.90-dev libboost-regex1.90.0 libboost-serialization-dev libboost-serialization1.90-dev libboost-serialization1.90.0 libboost-stacktrace-dev libboost-stacktrace1.90-dev
  libboost-stacktrace1.90.0 libboost-test-dev libboost-test1.90-dev libboost-test1.90.0 libboost-thread-dev libboost-thread1.90-dev libboost-thread1.90.0 libboost-timer-dev libboost-timer1.90-dev libboost-timer1.90.0 libboost-tools-dev
  libboost-type-erasure-dev libboost-type-erasure1.90-dev libboost-type-erasure1.90.0 libboost-url-dev libboost-url1.90-dev libboost-url1.90.0 libboost-wave-dev libboost-wave1.90-dev libboost-wave1.90.0 libboost1.90-dev
  libboost1.90-tools-dev libbrotli-dev libbsd-dev libbz2-dev libcc1-0 libcfitsio-dev libcfitsio10t64 libcharls2 libclass-method-modifiers-perl libclass-xsaccessor-perl libconfig-inifiles-perl libcrypt-dev libcurl4-gnutls-dev libczmq-dev
  libczmq4 libdc1394-dev libdebhelper-perl libdeflate-dev libdevel-callchecker-perl libdpkg-perl libdynaloader-functions-perl libeigen3-dev libev-dev libev4t64 libevent-2.1-7t64 libevent-core-2.1-7t64 libevent-dev
  libevent-extra-2.1-7t64 libevent-openssl-2.1-7t64 libevent-pthreads-2.1-7t64 libexif-dev libexpat1-dev libext2fs-dev libfabric1 libfakeroot libfftw3-bin libfftw3-dev libfftw3-long3 libfftw3-quad3 libfile-dirlist-perl
  libfile-homedir-perl libfile-stripnondeterminism-perl libfile-touch-perl libfile-which-perl libfreexl1 libftdi-dev libftdi1 libftdi1-dev libfyba0t64 libgav1-2 libgcc-15-dev libgcc-16-dev libgdal38 libgdcm-dev libgdcm3.0t64
  libgeos-c1t64 libgeos3.14.1 libgeotiff5 libgfortran-16-dev libgfortran5 libgl-dev libgl2ps1.4 libglu1-mesa libglu1-mesa-dev libglx-dev libgmock-dev libgmp-dev libgmpxx4ldbl libgnutls-dane0t64 libgnutls-openssl27t64 libgnutls28-dev
  libgphoto2-dev libgps-dev libgps32 libgsl-dev libgsl28 libgslcblas0 libgssrpc4t64 libgtest-dev libhdf4-0 libhdf5-310 libhdf5-hl-310 libhdf5-openmpi-310 libhidapi-dev libhidapi-hidraw0 libhidapi-libusb0 libhsa-runtime64-1 libhsakmt1
  libhwloc-dev libhwloc-plugins libhwloc15 libibmad5 libibumad3 libibverbs-dev libicu-dev libidn2-dev libimath-dev libimport-into-perl libio-string-perl libjbig-dev libjpeg-dev libjpeg-turbo8-dev libjpeg8-dev libjs-jquery
  libjs-jquery-ui libjsoncpp-dev libjsoncpp26 libkadm5clnt-mit12 libkadm5srv-mit12 libkdb5-10t64 libkmlbase1t64 libkmldom1t64 libkmlengine1t64 libkrb5-dev liblapack3 liblcms2-dev libldap-dev libleptonica-dev libleptonica6 liblerc-dev
  liblimesuite-dev liblimesuite23.11-1 libltdl-dev liblz4-dev liblzma-dev libmd-dev libminizip1t64 libmodule-runtime-perl libmoo-perl libmunge2 libmuparser2v5 libnetcdf22 libnghttp2-dev libnl-3-dev libnl-route-3-dev libnorm-dev
  libnova-0.16-0t64 libnova-dev libnova-dev-bin libnspr4-dev libnss3-dev libnuma-dev libodbc2 libodbcinst2 libogg-dev libopenblas0 libopenblas0-pthread libopencv-calib3d-dev libopencv-calib3d410 libopencv-contrib-dev
  libopencv-contrib410 libopencv-core-dev libopencv-core410 libopencv-dev libopencv-dnn-dev libopencv-dnn410 libopencv-features2d-dev libopencv-features2d410 libopencv-flann-dev libopencv-flann410 libopencv-highgui-dev
  libopencv-highgui410 libopencv-imgcodecs-dev libopencv-imgcodecs410 libopencv-imgproc-dev libopencv-imgproc410 libopencv-ml-dev libopencv-ml410 libopencv-objdetect-dev libopencv-objdetect410 libopencv-photo-dev libopencv-photo410
  libopencv-shape-dev libopencv-shape410 libopencv-stitching-dev libopencv-stitching410 libopencv-superres-dev libopencv-superres410 libopencv-video-dev libopencv-video410 libopencv-videoio-dev libopencv-videoio410
  libopencv-videostab-dev libopencv-videostab410 libopencv-viz-dev libopencv-viz410 libopenexr-dev libopengl-dev libopengl0 libopenmpi-dev libopenmpi40 libp11-kit-dev libparams-classify-perl libpgm-dev libpmix2t64 libpng-dev libproj25
  libprrte-bin libprrte-dev libprrte3 libpsl-dev libpsm2-2 libpugixml1v5 libpython3-dev libpython3.14-dev libqhull-r8.0 libqt5opengl5t64 libqt5test5t64 libraw-dev libraw1394-dev librdmacm1t64 librhash1 librole-tiny-perl librtlsdr-dev
  librtlsdr0 librtmp-dev librttopo1 libsdl2-2.0-0 libsdl2-classic libsharpyuv-dev libsocket++1 libsodium-dev libspatialite8t64 libssh2-1-dev libssl-dev libstdc++-15-dev libsub-quote-perl libsuperlu7 libswresample-dev libswscale-dev
  libsystemd-dev libsz2 libtasn1-6-dev libtbb-dev libtbb12 libtbbbind-2-5 libtbbmalloc2 libtesseract-dev libtesseract5 libtheora-dev libtiff-dev libtiffxx6 libtool libucc1 libucx0 libudev-dev libunbound8 liburiparser1 libusb-0.1-4
  libusb-1.0-0-dev libusb-dev libv4l-dev libv4l2rds0t64 libvtk9.5 libwebp-dev libwxbase3.2-1t64 libwxgtk-gl3.2-1t64 libwxgtk3.2-1t64 libwxgtk3.2-dev libx11-dev libxau-dev libxcb1-dev libxdmcp-dev libxerces-c3.2t64 libxisf-dev libxisf0
  libxml2-dev libxxhash-dev libyaml-cpp0.8 libyaml-libyaml-perl libyuv0 libze1 libzfp1t64 libzmq3-dev libzstd-dev lto-disabled-list m4 make mpi-default-bin mpi-default-dev nettle-dev ninja-build nlohmann-json3-dev
  openjdk-25-jre-headless openmpi-bin openmpi-common patchutils po-debconf proj-data python3-dev python3.14-dev unixodbc-common uuid-dev wdiff wx-common wx3.2-headers wx3.2-i18n x11proto-dev xorg-sgml-doctools xtrans-dev zlib1g-dev
アップグレード: 0 個、新規インストール: 480 個、削除: 0 個、保留: 5 個。
693 MB のアーカイブを取得する必要があります。
この操作後に追加で 2,848 MB のディスク容量が消費されます。</code></pre>



<p class="wp-block-paragraph">Ubuntu 26.04、CUDA環境整備後</p>



<pre class="wp-block-code"><code>以下の追加パッケージがインストールされます: 
  autopoint ca-certificates-java debugedit dh-autoreconf dh-strip-nondeterminism dwz googletest intltool-debian java-common libacl1-dev libarchive-dev libarchive-zip-perl libattr1-dev libavdevice62 libavfilter-dev
  libb-hooks-op-check-perl libboost-atomic-dev libboost-atomic1.90-dev libboost-atomic1.90.0 libboost-charconv1.90-dev libboost-charconv1.90.0 libboost-chrono-dev libboost-chrono1.90-dev libboost-chrono1.90.0
  libboost-container-dev libboost-container1.90-dev libboost-container1.90.0 libboost-context-dev libboost-context1.90-dev libboost-context1.90.0 libboost-coroutine-dev libboost-coroutine1.90-dev libboost-coroutine1.90.0
  libboost-date-time-dev libboost-date-time1.90-dev libboost-date-time1.90.0 libboost-dev libboost-exception-dev libboost-exception1.90-dev libboost-fiber-dev libboost-fiber1.90-dev libboost-fiber1.90.0
  libboost-filesystem-dev libboost-filesystem1.90-dev libboost-filesystem1.90.0 libboost-graph-dev libboost-graph-parallel-dev libboost-graph-parallel1.90-dev libboost-graph-parallel1.90.0 libboost-graph1.90-dev
  libboost-graph1.90.0 libboost-iostreams-dev libboost-iostreams1.90-dev libboost-iostreams1.90.0 libboost-json-dev libboost-json1.90-dev libboost-json1.90.0 libboost-locale-dev libboost-locale1.90-dev
  libboost-locale1.90.0 libboost-log-dev libboost-log1.90-dev libboost-log1.90.0 libboost-math-dev libboost-math1.90-dev libboost-math1.90.0 libboost-mpi-dev libboost-mpi-python-dev libboost-mpi-python1.90-dev
  libboost-mpi-python1.90.0 libboost-mpi1.90-dev libboost-mpi1.90.0 libboost-nowide-dev libboost-nowide1.90-dev libboost-nowide1.90.0 libboost-numpy-dev libboost-numpy1.90-dev libboost-numpy1.90.0 libboost-process-dev
  libboost-process1.90-dev libboost-process1.90.0 libboost-program-options-dev libboost-program-options1.90-dev libboost-program-options1.90.0 libboost-python-dev libboost-python1.90-dev libboost-python1.90.0
  libboost-random-dev libboost-random1.90-dev libboost-random1.90.0 libboost-regex1.90-dev libboost-regex1.90.0 libboost-serialization-dev libboost-serialization1.90-dev libboost-serialization1.90.0
  libboost-stacktrace-dev libboost-stacktrace1.90-dev libboost-stacktrace1.90.0 libboost-test-dev libboost-test1.90-dev libboost-test1.90.0 libboost-thread-dev libboost-thread1.90-dev libboost-thread1.90.0
  libboost-timer-dev libboost-timer1.90-dev libboost-timer1.90.0 libboost-tools-dev libboost-type-erasure-dev libboost-type-erasure1.90-dev libboost-type-erasure1.90.0 libboost-url-dev libboost-url1.90-dev
  libboost-url1.90.0 libboost-wave-dev libboost-wave1.90-dev libboost-wave1.90.0 libboost1.90-dev libboost1.90-tools-dev libbsd-dev libclass-method-modifiers-perl libclass-xsaccessor-perl libconfig-inifiles-perl libczmq4
  libdebhelper-perl libdevel-callchecker-perl libdynaloader-functions-perl libev4t64 libevent-dev libevent-extra-2.1-7t64 libevent-openssl-2.1-7t64 libext2fs-dev libfile-dirlist-perl libfile-homedir-perl
  libfile-stripnondeterminism-perl libfile-touch-perl libfile-which-perl libftdi1 libglu1-mesa libglu1-mesa-dev libgps32 libhidapi-hidraw0 libhidapi-libusb0 libhwloc-dev libibverbs-dev libimport-into-perl
  libio-string-perl libjack-jackd2-0 libjs-jquery libjs-jquery-ui libleptonica-dev liblimesuite23.11-1 libmd-dev libmodule-runtime-perl libmoo-perl libnl-3-dev libnl-route-3-dev libnorm-dev libnova-0.16-0t64
  libnova-dev-bin libnspr4-dev libnss3-dev libnuma-dev libogg-dev libopenal-data libopenal1 libopenmpi-dev libparams-classify-perl libpgm-dev libprrte-bin libprrte-dev libprrte3 libpython3-dev libpython3.14-dev
  librole-tiny-perl librtlsdr0 libsodium-dev libsub-quote-perl libusb-0.1-4 libv4l2rds0t64 libwxbase3.2-1t64 libwxgtk-gl3.2-1t64 libwxgtk3.2-1t64 libyaml-libyaml-perl mpi-default-bin mpi-default-dev
  openjdk-25-jre-headless openmpi-bin openmpi-common patchutils po-debconf python3-dev python3.14-dev wdiff wx3.2-headers
提案パッケージ:
  dh-make default-jre adequate at autopkgtest bls-standalone check-all-the-things diffoscope disorderfs docker.io dose-extra duck elpa-devscripts faketime gnuplot how-can-i-help libdbd-pg-perl libgitlab-api-v4-perl
  libterm-size-perl mmdebstrap mutt piuparts postgresql-client pristine-lfs python3-debianbts python3-pycurl quilt ratt reprotest svn-buildpackage w3m debian-keyring debian-tag2upload-keyring git-debpush
  libmetacpan-client-perl libsoap-lite-perl pristine-tar gettext-doc libasprintf-dev libgettextpo-dev gnulib-l10n libboost-doc libboost1.90-doc libboost-contract1.90-dev libmpfrc++-dev libntl-dev xsltproc doxygen
  docbook-xsl default-jdk fop libeigen3-doc doc-base gpsd jackd2 libjs-jquery-ui-docs liblimesuite-doc libnorm-doc libportaudio2 openmpi-doc libscalar-number-perl libxstring-perl wx3.2-doc fonts-dejavu-extra
  fonts-ipafont-gothic fonts-ipafont-mincho fonts-wqy-microhei | fonts-wqy-zenhei fonts-indic libmail-box-perl wdiff-doc
推奨パッケージ:
  dctrl-tools dput | dupload libdistro-info-perl libjson-perl libstring-shellquote-perl licensecheck lintian lzip python3-magic python3-unidiff libarchive-cpio-perl libftdi1-doc javascript-common limesuite-udev
  libnamespace-clean-perl libcoarrays-openmpi-dev libpmix-dev libusb-1.0-doc cppzmq-dev libmail-sendmail-perl
以下のパッケージが新たにインストールされます:
  apt-transport-https autoconf-archive autopoint ca-certificates-java cdbs debhelper debugedit default-jre-headless devscripts dh-autoreconf dh-strip-nondeterminism dwz equivs fxload gettext googletest intltool-debian
  java-common libacl1-dev libarchive-dev libarchive-zip-perl libattr1-dev libavdevice-dev libavdevice62 libavfilter-dev libb-hooks-op-check-perl libboost-all-dev libboost-atomic-dev libboost-atomic1.90-dev
  libboost-atomic1.90.0 libboost-charconv1.90-dev libboost-charconv1.90.0 libboost-chrono-dev libboost-chrono1.90-dev libboost-chrono1.90.0 libboost-container-dev libboost-container1.90-dev libboost-container1.90.0
  libboost-context-dev libboost-context1.90-dev libboost-context1.90.0 libboost-coroutine-dev libboost-coroutine1.90-dev libboost-coroutine1.90.0 libboost-date-time-dev libboost-date-time1.90-dev libboost-date-time1.90.0
  libboost-dev libboost-exception-dev libboost-exception1.90-dev libboost-fiber-dev libboost-fiber1.90-dev libboost-fiber1.90.0 libboost-filesystem-dev libboost-filesystem1.90-dev libboost-filesystem1.90.0
  libboost-graph-dev libboost-graph-parallel-dev libboost-graph-parallel1.90-dev libboost-graph-parallel1.90.0 libboost-graph1.90-dev libboost-graph1.90.0 libboost-iostreams-dev libboost-iostreams1.90-dev
  libboost-iostreams1.90.0 libboost-json-dev libboost-json1.90-dev libboost-json1.90.0 libboost-locale-dev libboost-locale1.90-dev libboost-locale1.90.0 libboost-log-dev libboost-log1.90-dev libboost-log1.90.0
  libboost-math-dev libboost-math1.90-dev libboost-math1.90.0 libboost-mpi-dev libboost-mpi-python-dev libboost-mpi-python1.90-dev libboost-mpi-python1.90.0 libboost-mpi1.90-dev libboost-mpi1.90.0 libboost-nowide-dev
  libboost-nowide1.90-dev libboost-nowide1.90.0 libboost-numpy-dev libboost-numpy1.90-dev libboost-numpy1.90.0 libboost-process-dev libboost-process1.90-dev libboost-process1.90.0 libboost-program-options-dev
  libboost-program-options1.90-dev libboost-program-options1.90.0 libboost-python-dev libboost-python1.90-dev libboost-python1.90.0 libboost-random-dev libboost-random1.90-dev libboost-random1.90.0 libboost-regex-dev
  libboost-regex1.90-dev libboost-regex1.90.0 libboost-serialization-dev libboost-serialization1.90-dev libboost-serialization1.90.0 libboost-stacktrace-dev libboost-stacktrace1.90-dev libboost-stacktrace1.90.0
  libboost-test-dev libboost-test1.90-dev libboost-test1.90.0 libboost-thread-dev libboost-thread1.90-dev libboost-thread1.90.0 libboost-timer-dev libboost-timer1.90-dev libboost-timer1.90.0 libboost-tools-dev
  libboost-type-erasure-dev libboost-type-erasure1.90-dev libboost-type-erasure1.90.0 libboost-url-dev libboost-url1.90-dev libboost-url1.90.0 libboost-wave-dev libboost-wave1.90-dev libboost-wave1.90.0 libboost1.90-dev
  libboost1.90-tools-dev libbsd-dev libclass-method-modifiers-perl libclass-xsaccessor-perl libconfig-inifiles-perl libczmq-dev libczmq4 libdebhelper-perl libdevel-callchecker-perl libdynaloader-functions-perl
  libeigen3-dev libev-dev libev4t64 libevent-dev libevent-extra-2.1-7t64 libevent-openssl-2.1-7t64 libext2fs-dev libfile-dirlist-perl libfile-homedir-perl libfile-stripnondeterminism-perl libfile-touch-perl
  libfile-which-perl libftdi-dev libftdi1 libftdi1-dev libglu1-mesa libglu1-mesa-dev libgmock-dev libgps-dev libgps32 libgtest-dev libhidapi-dev libhidapi-hidraw0 libhidapi-libusb0 libhwloc-dev libibverbs-dev
  libimport-into-perl libio-string-perl libjack-jackd2-0 libjs-jquery libjs-jquery-ui libjsoncpp-dev libleptonica-dev liblimesuite-dev liblimesuite23.11-1 libmd-dev libmodule-runtime-perl libmoo-perl libnl-3-dev
  libnl-route-3-dev libnorm-dev libnova-0.16-0t64 libnova-dev libnova-dev-bin libnspr4-dev libnss3-dev libnuma-dev libogg-dev libopenal-data libopenal1 libopenmpi-dev libparams-classify-perl libpgm-dev libprrte-bin
  libprrte-dev libprrte3 libpython3-dev libpython3.14-dev librole-tiny-perl librtlsdr-dev librtlsdr0 libsodium-dev libsub-quote-perl libtesseract-dev libtheora-dev libudev-dev libusb-0.1-4 libusb-1.0-0-dev libusb-dev
  libv4l-dev libv4l2rds0t64 libwxbase3.2-1t64 libwxgtk-gl3.2-1t64 libwxgtk3.2-1t64 libwxgtk3.2-dev libyaml-libyaml-perl libzmq3-dev mpi-default-bin mpi-default-dev nlohmann-json3-dev openjdk-25-jre-headless openmpi-bin
  openmpi-common patchutils po-debconf python3-dev python3.14-dev wdiff wx-common wx3.2-headers wx3.2-i18n
アップグレード: 0 個、新規インストール: 231 個、削除: 0 個、保留: 8 個。
138 MB のアーカイブを取得する必要があります。
この操作後に追加で 788 MB のディスク容量が消費されます。</code></pre>



<h2 class="wp-block-heading">build-and-install-pins-x64.sh エラーを取り除く。。。</h2>



<p class="wp-block-paragraph">この後、エラーで何度も止まります。<br>この段階で、方針を決めます。</p>



<div class="wp-block-cocoon-blocks-sticky-box blank-box block-box sticky">
<p class="wp-block-paragraph">既存の build-and-install-pins-x64.sh を最大限そのまま使う<br>問題が確認された部分だけ修正する<br>手作業で大量の依存ソフトを個別導入しない<br>システムに変更を加えない<br><br>PINS専用のものは、可能なら専用ディレクトリへ分離する<br>ビルドして初めて分かる問題は、事前に推測して大量修正しない</p>



<p class="wp-block-paragraph">この原則で行います。先は長そうです。</p>
</div>



<h3 class="wp-block-heading">opencv-4.11.0.zip エラー</h3>



<p class="wp-block-paragraph">何度も、OpenCVビルドでつまずくので、後では、個別にビルドして、インストールしています。</p>



<p class="wp-block-paragraph">artifacts/src/opencv/opencv-4.11.0.zip</p>



<pre class="wp-block-code"><code>CMake Error at /home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake:113 (cmake_minimum_required):
  Compatibility with CMake &lt; 3.5 has been removed from CMake.

  Update the VERSION argument &lt;min&gt; value.  Or, use the &lt;min&gt;...&lt;max&gt; syntax
  to tell CMake that the project requires at least &lt;min&gt; but has been updated
  to work with policies introduced by &lt;max&gt; or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.</code></pre>



<p class="wp-block-paragraph">OpenCV 4.11.0のビルド処理が、Ubuntu 26.04に入っているCMakeと互換性がないようです。<br>-DCMAKE_POLICY_VERSION_MINIMUM=3.5　オプションを提案してます。</p>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh の opencv、cmake を見てみます。</p>



<pre class="wp-block-code"><code>### Ubuntu 26.04のCmake
cmake --version
cmake version 4.2.3</code></pre>



<pre class="wp-block-code"><code>grep -n -C 5 "opencv\|cmake" build-and-install-pins-x64.sh</code></pre>



<p class="wp-block-paragraph">これは自分が読み込めない。。。</p>



<pre class="wp-block-code"><code>### PINSスクリプトではOpenCV 4.11.0をソースからビルドしています。

local cmake_args=(
  -DCMAKE_BUILD_TYPE=Release
  -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
  -DOPENCV_GENERATE_PKGCONFIG=ON
)</code></pre>



<p class="wp-block-paragraph">Ubuntu 26.04のCMakeとOpenCV 4.11.0の組み合わせによる問題らしい。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Compatibility with versions of CMake older than 3.5 has been removed.<br>CMake 4.0 Release Notes<br><a rel="noopener" target="_blank" href="https://cmake.org/cmake/help/v4.2/release/4.0.html?utm_source=chatgpt.com#deprecated-and-removed-features">https://cmake.org/cmake/help/v4.2/release/4.0.html?utm_source=chatgpt.com#deprecated-and-removed-features</a></p>
</blockquote>



<p class="wp-block-paragraph">先の、-DCMAKE_POLICY_VERSION_MINIMUM=3.5 についても説明があります。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">CMAKE_POLICY_VERSION_MINIMUM<br>CMake を使用しているユーザーは、キャッシュ内でこの変数を設定（例：-DCMAKE_POLICY_VERSION_MINIMUM=3.5）することで、そのポリシーバージョン以上に更新されていないプロジェクトの構成を試みることができます。<br><a rel="noopener" target="_blank" href="https://cmake.org/cmake/help/latest/variable/CMAKE_POLICY_VERSION_MINIMUM.html?utm_source=chatgpt.com">https://cmake.org/cmake/help/latest/variable/CMAKE_POLICY_VERSION_MINIMUM.html?utm_source=chatgpt.com</a></p>
</blockquote>



<p class="wp-block-paragraph">ん〜〜。。。面倒だ。提案されたオプションを試します。</p>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh のOpenCVビルド部分に、-DCMAKE_POLICY_VERSION_MINIMUM=3.5 を追加します。</p>



<p class="wp-block-paragraph">~/pins/build-and-install-pins-x64.sh の 581行付近が、OpenCVビルド箇所です。</p>



<pre class="wp-block-code"><code>  local cmake_args=(
    -DCMAKE_BUILD_TYPE=Release
    -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
    -DOPENCV_GENERATE_PKGCONFIG=ON
  )</code></pre>



<p class="wp-block-paragraph">-DCMAKE_POLICY_VERSION_MINIMUM=3.5 を追加します。</p>



<pre class="wp-block-code"><code>local cmake_args=(
  -DCMAKE_BUILD_TYPE=Release
  -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
  -DOPENCV_GENERATE_PKGCONFIG=ON
  -DCMAKE_POLICY_VERSION_MINIMUM=3.5
)</code></pre>



<p class="wp-block-paragraph">変更部分を確認します。</p>



<pre class="wp-block-code"><code>grep -n -A5 "local cmake_args=" build-and-install-pins-x64.sh
581:  local cmake_args=(
582-    -DCMAKE_BUILD_TYPE=Release
583-    -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
584-    -DOPENCV_GENERATE_PKGCONFIG=ON
585-    -DCMAKE_POLICY_VERSION_MINIMUM=3.5
586-  )</code></pre>



<pre class="wp-block-code"><code>### スクリプトを動かす
./build-and-install-pins-x64.sh</code></pre>



<p class="wp-block-paragraph">同じ箇所で止まった。。。</p>



<pre class="wp-block-code"><code>CMake Error at /home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake:113 (cmake_minimum_required):
  Compatibility with CMake &lt; 3.5 has been removed from CMake.

  Update the VERSION argument &lt;min&gt; value.  Or, use the &lt;min&gt;...&lt;max&gt; syntax
  to tell CMake that the project requires at least &lt;min&gt; but has been updated
  to work with policies introduced by &lt;max&gt; or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.</code></pre>



<p class="wp-block-paragraph">PINSが要求しているOpenCV 4.11.0を維持し、CMake 4との非互換部分だけ修正します。</p>



<pre class="wp-block-code"><code>sed -n '105,118p' artifacts/src/opencv/opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake

if((UNIX AND NOT ANDROID) OR MINGW)
  install(FILES ${CMAKE_BINARY_DIR}/unix-install/${OPENCV_PC_FILE_NAME} DESTINATION ${OPENCV_LIB_INSTALL_PATH}/pkgconfig COMPONENT dev)
endif()

# =============================================================================
else() # DEFINED CMAKE_HELPER_SCRIPT

cmake_minimum_required(VERSION 2.8.12.2)
cmake_policy(SET CMP0012 NEW)
include("${CMAKE_HELPER_SCRIPT}")
include("${OpenCV_SOURCE_DIR}/cmake/OpenCVUtils.cmake")

fix_prefix(_modules 1)</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">現在：<br>cmake_minimum_required(VERSION 2.8.12.2)<br><br>変更：<br>cmake_minimum_required(VERSION 3.5)</p>
</div>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph"><br>CMAKE_POLICY_VERSION_MINIMUM=3.5 をCMake configureに指定<br>OpenCVGenPkgconfig.cmake の古い 2.8.12.2 を 3.5 に修正</p>
</div>



<p class="wp-block-paragraph">サイトを漁ると次がありました。113行で止まるのは</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">cmake-4.patch<br><a rel="noopener" target="_blank" href="https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/cmake-4.patch?utm_source=chatgpt.com">https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/cmake-4.patch?utm_source=chatgpt.com</a></p>
</blockquote>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">こちらでも論じられています<br><a rel="noopener" target="_blank" href="https://github.com/opencv/opencv/issues/27122">https://github.com/opencv/opencv/issues/27122</a></p>
</blockquote>



<p class="wp-block-paragraph">~/pins/build-and-install-pins-x64.sh　を変更します。<br>build_and_install_opencv_required_version( を変更します。</p>



<pre class="wp-block-code"><code>### 変更前
wget -O "$opencv_zip" "https://github.com/opencv/opencv/archive/refs/tags/${OPENCV_REQUIRED_VERSION}.zip"
unzip -q "$opencv_zip" -d "$opencv_src_root"

local cmake_args=(
  -DCMAKE_BUILD_TYPE=Release
  -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
  -DOPENCV_GENERATE_PKGCONFIG=ON
  -DCMAKE_POLICY_VERSION_MINIMUM=3.5
)</code></pre>



<pre class="wp-block-code"><code>### 変更後
wget -O "$opencv_zip" "https://github.com/opencv/opencv/archive/refs/tags/${OPENCV_REQUIRED_VERSION}.zip"
unzip -q "$opencv_zip" -d "$opencv_src_root"

sed -i \
  's/cmake_minimum_required(VERSION 2.8.12.2)/cmake_minimum_required(VERSION 3.5)/' \
  "$opencv_src_dir/cmake/OpenCVGenPkgconfig.cmake"

local cmake_args=(
  -DCMAKE_BUILD_TYPE=Release
  -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
  -DOPENCV_GENERATE_PKGCONFIG=ON
  -DCMAKE_POLICY_VERSION_MINIMUM=3.5</code></pre>



<p class="wp-block-paragraph">挟み込んだ、sed -i 部分は、<br>OpenCVを展開した直後に、OpenCVGenPkgconfig.cmake の古いCMakeバージョン指定を書き換えるコマンドです。<br>sed：テキストファイルの内容を検索・置換するLinuxのコマンド、-i は ファイルを直接書き換える。<br><code>s/.../.../</code>　は、s/変更前/変更後/<br>変更前：cmake_minimum_required(VERSION 2.8.12.2)<br>変更後：cmake_minimum_required(VERSION 3.5)<br>&#8220;$&#8221;　対象ファイルを示す。</p>



<p class="wp-block-paragraph">構文チェックをします。スクリプトを実行します。</p>



<pre class="wp-block-code"><code>bash -n ~/pins/build-and-install-pins-x64.sh
./build-and-install-pins-x64.sh</code></pre>



<h3 class="wp-block-heading">FFmpg互換性</h3>



<p class="wp-block-paragraph">同じ箇所で止まります。</p>



<p class="wp-block-paragraph">Ubuntu 26.04 のFFmpeg開発ライブラリ（FFmpeg 8系）<br>OpenCV 4.11.0 のFFmpeg連携コード</p>



<p class="wp-block-paragraph">FFmpegのAPI互換性問題</p>



<pre class="wp-block-code"><code>&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/concat_layer.cpp.o
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/const_layer.cpp.o
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/convolution_layer.cpp.o
&#91; 24%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_obsensor_capture.cpp.o
&#91; 24%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_obsensor/obsensor_uvc_stream_channel.cpp.o
In file included from /home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg.cpp:50:
/home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp: In member function ‘void CvCapture_FFMPEG::close()’:
/home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp:688:9: error: ‘avcodec_close’ was not declared in this scope; did you mean ‘avio_close’?
  688 |         avcodec_close( context );
      |         ^~~~~~~~~~~~~
      |         avio_close
&#91; 24%] Building CXX object modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_obsensor/obsensor_stream_channel_v4l2.cpp.o
/home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp: In member function ‘void CvCapture_FFMPEG::get_rotation_angle()’:
/home/USERNAME/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp:2008:12: error: ‘av_stream_get_side_data’ was not declared in this scope; did you mean ‘av_frame_get_side_data’?
 2008 |     data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
      |            ^~~~~~~~~~~~~~~~~~~~~~~
      |            av_frame_get_side_data
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/correlation_layer.cpp.o
gmake&#91;2]: *** &#91;modules/videoio/CMakeFiles/opencv_videoio.dir/build.make:219: modules/videoio/CMakeFiles/opencv_videoio.dir/src/cap_ffmpeg.cpp.o] エラー 1
gmake&#91;2]: *** 未完了のジョブを待っています....
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/cpu_kernels/conv_depthwise.cpp.o
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/cpu_kernels/conv_winograd_f63.cpp.o
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/cpu_kernels/conv_winograd_f63.dispatch.cpp.o
&#91; 24%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/cpu_kernels/convolution.cpp.o

&#91; 25%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/detection_output_layer.cpp.o
&#91; 25%] Built target opencv_photo
&#91; 25%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/einsum_layer.cpp.o

&#91; 25%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/flow_warp_layer.cpp.o
gmake&#91;1]: *** &#91;CMakeFiles/Makefile2:6891: modules/videoio/CMakeFiles/opencv_videoio.dir/all] エラー 2
gmake&#91;1]: *** 未完了のジョブを待っています....
&#91; 25%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/layers/fully_connected_layer.cpp.o
&#91; 29%] Linking CXX shared library ../../lib/libopencv_xphoto.so
&#91; 29%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/op_timvx.cpp.o
&#91; 29%] Built target opencv_xphoto
&#91; 29%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/op_vkcom.cpp.o
&#91; 29%] Building CXX object modules/dnn/CMakeFiles/opencv_dnn.dir/src/op_webnn.cpp.o


&#91; 31%] Linking CXX shared library ../../lib/libopencv_dnn.so
&#91; 31%] Built target opencv_dnn
&#91; 31%] Linking CXX shared library ../../lib/libopencv_features2d.so
&#91; 31%] Built target opencv_features2d
gmake: *** &#91;Makefile:166: all] エラー 2
</code></pre>



<p class="wp-block-paragraph">avcodec_close was not declared<br>av_stream_get_side_data was not declared</p>



<p class="wp-block-paragraph">avcodecは、FFmpegの一部なので、OpenCV 4.11.0 の FFmpeg 部分と、Ubuntu 26.04 側の FFmpeg APの不整合らしい。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">ffmpeg-8.0-compat-1.patch<br><a rel="noopener" target="_blank" href="https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-1.patch">https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-1.patch</a><br><br>Adding ffmpeg-8.0 support<br><a rel="noopener" target="_blank" href="https://github.com/opencv/opencv/issues/27688?utm_source=chatgpt.com">https://github.com/opencv/opencv/issues/27688?utm_source=chatgpt.com</a></p>
</blockquote>



<p class="wp-block-paragraph">OpenCVのビルドに必要なFFmpeg開発ライブラリを確認します。</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E 'libav(codec|format|util|device|filter|swscale|swresample)'
ii  libavcodec-dev:amd64                            7:8.0.1-3ubuntu2                           amd64        FFmpeg library with de/encoders for audio/video codecs - development files
ii  libavcodec62:amd64                              7:8.0.1-3ubuntu2                           amd64        FFmpeg library with de/encoders for audio/video codecs - runtime files
ii  libavdevice-dev:amd64                           7:8.0.1-3ubuntu2                           amd64        FFmpeg library for handling input and output devices - development files
ii  libavdevice62:amd64                             7:8.0.1-3ubuntu2                           amd64        FFmpeg library for handling input and output devices - runtime files
ii  libavfilter-dev:amd64                           7:8.0.1-3ubuntu2                           amd64        FFmpeg library containing media filters - development files
ii  libavfilter11:amd64                             7:8.0.1-3ubuntu2                           amd64        FFmpeg library containing media filters - runtime files
ii  libavformat-dev:amd64                           7:8.0.1-3ubuntu2                           amd64        FFmpeg library with (de)muxers for multimedia containers - development files
ii  libavformat62:amd64                             7:8.0.1-3ubuntu2                           amd64        FFmpeg library with (de)muxers for multimedia containers - runtime files
ii  libavutil-dev:amd64                             7:8.0.1-3ubuntu2                           amd64        FFmpeg library with functions for simplifying programming - development files
ii  libavutil60:amd64                               7:8.0.1-3ubuntu2                           amd64        FFmpeg library with functions for simplifying programming - runtime files</code></pre>



<pre class="wp-block-code"><code>pkg-config --modversion libavcodec
62.11.100</code></pre>



<pre class="wp-block-code"><code>sed -n '660,710p' artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp
    extraDataIdx = 1;
}


void CvCapture_FFMPEG::close()
{
    if( img_convert_ctx )
    {
        sws_freeContext(img_convert_ctx);
        img_convert_ctx = 0;
    }

    if( picture )
    {
#if LIBAVCODEC_BUILD &gt;= (LIBAVCODEC_VERSION_MICRO &gt;= 100 \
    ? CALC_FFMPEG_VERSION(55, 45, 101) : CALC_FFMPEG_VERSION(55, 28, 1))
        av_frame_free(&amp;picture);
#elif LIBAVCODEC_BUILD &gt;= (LIBAVCODEC_VERSION_MICRO &gt;= 100 \
    ? CALC_FFMPEG_VERSION(54, 59, 100) : CALC_FFMPEG_VERSION(54, 28, 0))
        avcodec_free_frame(&amp;picture);
#else
        av_free(picture);
#endif
    }

    if( video_st )
    {
#ifdef CV_FFMPEG_CODECPAR
        avcodec_close( context );
#endif
        video_st = NULL;
    }

    if (context)
    {
#ifdef CV_FFMPEG_CODECPAR
        avcodec_free_context(&amp;context);
#endif
    }

    if( ic )
    {
        avformat_close_input(&amp;ic);
        ic = NULL;
    }

#if USE_AV_FRAME_GET_BUFFER
    av_frame_unref(&amp;rgb_picture);
#else
    if( rgb_picture.data&#91;0] )
    {</code></pre>



<pre class="wp-block-code"><code>sed -n '1990,2020p' artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp

int64_t CvCapture_FFMPEG::dts_to_frame_number(int64_t dts)
{
    double sec = dts_to_sec(dts);
    return (int64_t)(get_fps() * sec + 0.5);
}

double CvCapture_FFMPEG::dts_to_sec(int64_t dts) const
{
    return (double)(dts - ic-&gt;streams&#91;video_stream]-&gt;start_time) *
        r2d(ic-&gt;streams&#91;video_stream]-&gt;time_base);
}

void CvCapture_FFMPEG::get_rotation_angle()
{
    rotation_angle = 0;
#if LIBAVFORMAT_BUILD &gt;= CALC_FFMPEG_VERSION(57, 68, 100)
    const uint8_t *data = 0;
    data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
    if (data)
    {
        rotation_angle = -cvRound(av_display_rotation_get((const int32_t*)data));
        if (rotation_angle &lt; 0)
            rotation_angle += 360;
    }
#elif LIBAVUTIL_BUILD &gt;= CALC_FFMPEG_VERSION(52, 94, 100)
    AVDictionaryEntry *rotate_tag = av_dict_get(video_st-&gt;metadata, "rotate", NULL, 0);
    if (rotate_tag != NULL)
        rotation_angle = atoi(rotate_tag-&gt;value);
#endif
}</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">エラーは：error: ‘avcodec_close’ was not declared in this scope<br>avcodec_close(context); ← 古いAPI<br>↓<br>avcodec_free_context(&amp;context); ← 現在使われている解放処理<br><br>エラーは：error: ‘av_stream_get_side_data’ was not declared in this scope<br>AV_PKT_DATA_DISPLAYMATRIXを指定しています。これは動画の回転情報を取得</p>
</div>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">ffmpeg-8.0-compat-1.patch<br><a rel="noopener" target="_blank" href="https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-1.patch">https://sources.debian.org/src/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-1.patch</a><br><br>Adding ffmpeg-8.0 support<br><a rel="noopener" target="_blank" href="https://github.com/opencv/opencv/issues/27688?utm_source=chatgpt.com">https://github.com/opencv/opencv/issues/27688?utm_source=chatgpt.com</a></p>
</blockquote>



<p class="wp-block-paragraph">ffmpeg-8.0-compat-1.patchの修正では、<br>#if (LIBAVCODEC_BUILD &lt; CALC_FFMPEG_VERSION(62, 11, 100))<br>　avcodec_close( context );<br># endif<br>として、FFmpeg 8未満の場合だけ実行します<br><br>ffmpeg-8.0-compat-1.patchのOpenCV修正では、FFmpeg 8の場合は以下の修正らしいです。</p>



<pre class="wp-block-code"><code>AVPacketSideData* sd = video_st-&gt;codecpar-&gt;coded_side_data;
int nb_sd = video_st-&gt;codecpar-&gt;nb_coded_side_data;

if (sd &amp;&amp; nb_sd &gt; 0)
{
    const AVPacketSideData* mtx =
        av_packet_side_data_get(
            sd,
            nb_sd,
            AV_PKT_DATA_DISPLAYMATRIX);

    data = mtx-&gt;data;
}</code></pre>



<h2 class="wp-block-heading">opencv-4.11.0は別にビルド</h2>



<p class="wp-block-paragraph">opencvビルドをbuild-and-install-pins-x64.shスクリプトで行うと、まだまだ、沢山のエラーが出そうなので方針を替えます。</p>



<p class="wp-block-paragraph">OpenCVをPINSのビルドとは分離してビルド、インストールし、PINSのスクリプトには「既にOpenCVが存在する」と指定します。</p>



<p class="wp-block-paragraph">OpenCV 4.11.0ビルド・インストール<br>/home/USERNAME/opencv-build/install/<br>├── include/<br>├── lib/<br>└── lib/cmake/opencv4/OpenCVConfig.cmake</p>



<p class="wp-block-paragraph"><br>build-and-install-pins-x64.shには、<br>「既に OpenCV 4.11.0 がある。それを使用する」と指定します。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">環境変数を用いて<br>OPENCV_INSTALL_PREFIX=&#8221;${OPENCV_INSTALL_PREFIX:-$HOME/opencv-build/install}&#8221;<br><br>OpenCV_DIR=&#8221;$OPENCV_INSTALL_PREFIX/lib/cmake/opencv4&#8243;<br>をPINSビルドで使わせます。</p>
</div>



<p class="wp-block-paragraph">opencvをビルドします。</p>



<pre class="wp-block-code"><code>cd ~
mkdir -p opencv-build
cd opencv-build</code></pre>



<pre class="wp-block-code"><code>### OpenCV 本体のダウンロード
wget -O opencv-4.11.0.zip https://github.com/opencv/opencv/archive/refs/tags/4.11.0.zip

### opencv_contrib（拡張モジュール）のダウンロード
wget -O opencv_contrib-4.11.0.zip https://github.com/opencv/opencv_contrib/archive/refs/tags/4.11.0.zip

### 展開
unzip -q opencv-4.11.0.zip
unzip -q opencv_contrib-4.11.0.zip</code></pre>



<p class="wp-block-paragraph">~/opencv-build のOpenCV 4.11.0にFFmpeg 8.0パッチを適用します。</p>



<p class="wp-block-paragraph">公式のFFmpeg 8.0互換パッチをそのまま適用します。</p>



<pre class="wp-block-code"><code>### パッチを取得します。

wget -O /tmp/ffmpeg-8.0-compat.patch \
  'https://sources.debian.org/data/main/o/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-1.patch'
‘/tmp/ffmpeg-8.0-compat.patch’ へ保存完了 &#91;1303/1303]</code></pre>



<p class="wp-block-paragraph">パッチの内容を確認します。</p>



<pre class="wp-block-code"><code>grep -nE 'avcodec_close|av_stream_get_side_data|av_packet_side_data_get' \
  /tmp/ffmpeg-8.0-compat.patch

199:&lt;/span&gt;&lt;span id="line11" class="codeline "&gt;+// avcodec_close removed in FFmpeg release 8.0
201:&lt;/span&gt;&lt;span id="line13" class="codeline "&gt;         avcodec_close( context );
210:&lt;/span&gt;&lt;span id="line22" class="codeline "&gt;+    // av_stream_get_side_data removed in FFmpeg release 8.0
212:&lt;/span&gt;&lt;span id="line24" class="codeline "&gt;     data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
218:&lt;/span&gt;&lt;span id="line30" class="codeline "&gt;+        const AVPacketSideData* mtx = av_packet_side_data_get(sd,  nb_sd, AV_PKT_DATA_DISPLAYMATRIX);
~/pins$ sed -n '185,225p' /tmp/ffmpeg-8.0-compat.patch
    &lt;td&gt;
      &lt;pre id="sourceslinenumbers"&gt;&lt;a id="L1" href="#L1"&gt;1&lt;/a&gt;&lt;br /&gt;&lt;a id="L2" href="#L2"&gt;2&lt;/a&gt;&lt;br /&gt;&lt;a id="L3" href="#L3"&gt;3&lt;/a&gt;&lt;br /&gt;&lt;a id="L4" href="#L4"&gt;4&lt;/a&gt;&lt;br /&gt;&lt;a id="L5" href="#L5"&gt;5&lt;/a&gt;&lt;br /&gt;&lt;a id="L6" href="#L6"&gt;6&lt;/a&gt;&lt;br /&gt;&lt;a id="L7" href="#L7"&gt;7&lt;/a&gt;&lt;br /&gt;&lt;a id="L8" href="#L8"&gt;8&lt;/a&gt;&lt;br /&gt;&lt;a id="L9" href="#L9"&gt;9&lt;/a&gt;&lt;br /&gt;&lt;a id="L10" href="#L10"&gt;10&lt;/a&gt;&lt;br /&gt;&lt;a id="L11" href="#L11"&gt;11&lt;/a&gt;&lt;br /&gt;&lt;a id="L12" href="#L12"&gt;12&lt;/a&gt;&lt;br /&gt;&lt;a id="L13" href="#L13"&gt;13&lt;/a&gt;&lt;br /&gt;&lt;a id="L14" href="#L14"&gt;14&lt;/a&gt;&lt;br /&gt;&lt;a id="L15" href="#L15"&gt;15&lt;/a&gt;&lt;br /&gt;&lt;a id="L16" href="#L16"&gt;16&lt;/a&gt;&lt;br /&gt;&lt;a id="L17" href="#L17"&gt;17&lt;/a&gt;&lt;br /&gt;&lt;a id="L18" href="#L18"&gt;18&lt;/a&gt;&lt;br /&gt;&lt;a id="L19" href="#L19"&gt;19&lt;/a&gt;&lt;br /&gt;&lt;a id="L20" href="#L20"&gt;20&lt;/a&gt;&lt;br /&gt;&lt;a id="L21" href="#L21"&gt;21&lt;/a&gt;&lt;br /&gt;&lt;a id="L22" href="#L22"&gt;22&lt;/a&gt;&lt;br /&gt;&lt;a id="L23" href="#L23"&gt;23&lt;/a&gt;&lt;br /&gt;&lt;a id="L24" href="#L24"&gt;24&lt;/a&gt;&lt;br /&gt;&lt;a id="L25" href="#L25"&gt;25&lt;/a&gt;&lt;br /&gt;&lt;a id="L26" href="#L26"&gt;26&lt;/a&gt;&lt;br /&gt;&lt;a id="L27" href="#L27"&gt;27&lt;/a&gt;&lt;br /&gt;&lt;a id="L28" href="#L28"&gt;28&lt;/a&gt;&lt;br /&gt;&lt;a id="L29" href="#L29"&gt;29&lt;/a&gt;&lt;br /&gt;&lt;a id="L30" href="#L30"&gt;30&lt;/a&gt;&lt;br /&gt;&lt;a id="L31" href="#L31"&gt;31&lt;/a&gt;&lt;br /&gt;&lt;a id="L32" href="#L32"&gt;32&lt;/a&gt;&lt;br /&gt;&lt;a id="L33" href="#L33"&gt;33&lt;/a&gt;&lt;br /&gt;&lt;a id="L34" href="#L34"&gt;34&lt;/a&gt;&lt;br /&gt;&lt;a id="L35" href="#L35"&gt;35&lt;/a&gt;&lt;br /&gt;&lt;a id="L36" href="#L36"&gt;36&lt;/a&gt;&lt;br /&gt;&lt;/pre&gt;
    &lt;/td&gt;
    &lt;td&gt;
      &lt;pre&gt;&lt;code id="sourcecode" class="diff"&gt;&lt;span id="line1" class="codeline "&gt;From: Alexander Smorkalov &amp;lt;alexander.smorkalov@opencv.ai&amp;gt;
&lt;/span&gt;&lt;span id="line2" class="codeline "&gt;Subject: FFmpeg 8.0 support 1/2
&lt;/span&gt;&lt;span id="line3" class="codeline "&gt;Origin: upstream, https://github.com/opencv/opencv/commit/90c444abd387ffa70b2e72a34922903a2f0f4f5a</code></pre>



<p class="wp-block-paragraph">パッチを適応します。</p>



<pre class="wp-block-code"><code>cd ~/opencv-build/opencv-4.11.0
patch --dry-run -p1 &lt; /tmp/ffmpeg-8.0-compat.patch

### 適応させます
patch -p1 &lt; /tmp/ffmpeg-8.0-compat.patch
patching file modules/videoio/src/cap_ffmpeg_impl.hpp
Hunk #1 succeeded at 685 (offset 5 lines).
Hunk #2 succeeded at 2008 (offset 66 lines).</code></pre>



<pre class="wp-block-code"><code>### 後続のパッチを取得します。
wget -O /tmp/ffmpeg-8.0-compat-2.patch \
  'https://sources.debian.org/data/main/o/opencv/4.10.0%2Bdfsg-8/debian/patches/ffmpeg-8.0-compat-2.patch'</code></pre>



<p class="wp-block-paragraph">パッチを確認します。</p>



<pre class="wp-block-code"><code>head -5 /tmp/ffmpeg-8.0-compat-2.patch
From: Dmitry Kurtaev &lt;dmitry.kurtaev@gmail.com&gt;
Subject: FFmpeg 8.0 support 2/2
Origin: upstream, https://github.com/opencv/opencv/commit/443d0ae63fad6dfd8c485d609203db16c8bd0ec3

--- a/modules/videoio/src/cap_ffmpeg_impl.hpp
</code></pre>



<pre class="wp-block-code"><code>grep -nE 'av_packet_side_data_get|mtx|NULL' \
  /tmp/ffmpeg-8.0-compat-2.patch

198:&lt;/span&gt;&lt;span id="line10" class="codeline "&gt;         const AVPacketSideData* mtx = av_packet_side_data_get(sd,  nb_sd, AV_PKT_DATA_DISPLAYMATRIX);
199:&lt;/span&gt;&lt;span id="line11" class="codeline "&gt;-        data = mtx-&amp;gt;data;
200:&lt;/span&gt;&lt;span id="line12" class="codeline "&gt;+        if (mtx)
202:&lt;/span&gt;&lt;span id="line14" class="codeline "&gt;+            data = mtx-&amp;gt;data;</code></pre>



<p class="wp-block-paragraph">後続のパッチを適応します。</p>



<pre class="wp-block-code"><code>patch -p1 &lt; /tmp/ffmpeg-8.0-compat-2.patch</code></pre>



<p class="wp-block-paragraph">パッチを確認します。</p>



<pre class="wp-block-code"><code>grep -n -A8 -B3 "avcodec_close( context )" \
  modules/videoio/src/cap_ffmpeg_impl.hpp
687-#ifdef CV_FFMPEG_CODECPAR
688-// avcodec_close removed in FFmpeg release 8.0
689-# if (LIBAVCODEC_BUILD &lt; CALC_FFMPEG_VERSION(62, 11, 100))
690:        avcodec_close( context );
691-# endif
692-#endif
693-        video_st = NULL;
694-    }
695-
696-    if (context)
697-    {
698-#ifdef CV_FFMPEG_CODECPAR</code></pre>



<pre class="wp-block-code"><code>grep -n -A20 -B3 "av_stream_get_side_data" \
  modules/videoio/src/cap_ffmpeg_impl.hpp
2008-    rotation_angle = 0;
2009-#if LIBAVFORMAT_BUILD &gt;= CALC_FFMPEG_VERSION(57, 68, 100)
2010-    const uint8_t *data = 0;
2011:    // av_stream_get_side_data removed in FFmpeg release 8.0
2012-# if (LIBAVCODEC_BUILD &lt; CALC_FFMPEG_VERSION(62, 11, 100))
2013:    data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
2014-# else
2015-    AVPacketSideData* sd = video_st-&gt;codecpar-&gt;coded_side_data;
2016-    int nb_sd = video_st-&gt;codecpar-&gt;nb_coded_side_data;
2017-    if (sd &amp;&amp; nb_sd &gt; 0)
2018-    {
2019-        const AVPacketSideData* mtx = av_packet_side_data_get(sd,  nb_sd, AV_PKT_DATA_DISPLAYMATRIX);
2020-        if (mtx)
2021-        {
2022-            data = mtx-&gt;data;
2023-        }
2024-    }
2025-# endif
2026-    if (data)
2027-    {
2028-        rotation_angle = -cvRound(av_display_rotation_get((const int32_t*)data));
2029-        if (rotation_angle &lt; 0)
2030-            rotation_angle += 360;
2031-    }
2032-#elif LIBAVUTIL_BUILD &gt;= CALC_FFMPEG_VERSION(52, 94, 100)
2033-    AVDictionaryEntry *rotate_tag = av_dict_get(video_st-&gt;metadata, "rotate", NULL, 0);</code></pre>



<p class="wp-block-paragraph">CMake 4対応<br>OpenCV 4.11.0 のソースコード内にあるCMake設定を、CMake 4.2.3でも受け付けられるように1箇所だけ書き換えます。</p>



<p class="wp-block-paragraph">ここでは、OpenCV 4.11.0の<br>opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake<br>の113行目にある</p>



<p class="wp-block-paragraph">cmake_minimum_required(VERSION 2.8.12.2)<br>を、<br>cmake_minimum_required(VERSION 3.5)</p>



<p class="wp-block-paragraph">に変更します。</p>



<pre class="wp-block-code"><code>cd opencv-build

sed -i \
  's/cmake_minimum_required(VERSION 2\.8\.12\.2)/cmake_minimum_required(VERSION 3.5)/' \
  opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake</code></pre>



<p class="wp-block-paragraph">sed：テキストファイルを編集するコマンド<br>-i：ファイルそのものを書き換える<br>s/変更前/変更後/：「変更前」を「変更後」に置換する<br>opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake：変更対象のファイル</p>



<p class="wp-block-paragraph">変更を確認します。</p>



<pre class="wp-block-code"><code>grep -n "cmake_minimum_required" \
  opencv-4.11.0/cmake/OpenCVGenPkgconfig.cmake

113:cmake_minimum_required(VERSION 3.5)</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">変更前：cmake_minimum_required(VERSION 2.8.12.2) </p>



<p class="wp-block-paragraph">変更後：cmake_minimum_required(VERSION 3.5)</p>
</div>



<p class="wp-block-paragraph">CMake設定を行います。上記で変更させた部分を反映させます。</p>



<pre class="wp-block-code"><code>cd ~/opencv-build
mkdir -p build

cmake -S ~/opencv-build/opencv-4.11.0 \
      -B ~/opencv-build/build \
      -DCMAKE_BUILD_TYPE=Release \
      -DCMAKE_INSTALL_PREFIX=/usr/local \
      -DOPENCV_GENERATE_PKGCONFIG=ON \
      -DOPENCV_EXTRA_MODULES_PATH=~/opencv-build/opencv_contrib-4.11.0/modules \
      -DCMAKE_POLICY_VERSION_MINIMUM=3.5</code></pre>



<p class="wp-block-paragraph">コンパイルを行います。（ここまでで既に困憊る）</p>



<pre class="wp-block-code"><code>cmake --build ~/opencv-build/build --parallel "$(nproc)"</code></pre>



<p class="wp-block-paragraph">&#8211;parallel &#8220;$(nproc)&#8221;は、処理するコア数<br>&#8211;parallel &#8220;$(nproc)&#8221;は、&#8211;parallel 16：最大16個のジョブを並列にコンパイル<br>CPU負荷を抑える → &#8211;parallel 4 や 8</p>



<p class="wp-block-paragraph">インストール先はどこかな？</p>



<pre class="wp-block-code"><code>grep CMAKE_INSTALL_PREFIX ~/opencv-build/build/CMakeCache.txt
CMAKE_INSTALL_PREFIX:PATH=/usr/local
//CMAKE_INSTALL_PREFIX during last run
_GNUInstallDirs_LAST_CMAKE_INSTALL_PREFIX:INTERNAL=/usr/local</code></pre>



<p class="wp-block-paragraph">OpenCV 4.11.0を <code>/usr/local</code> にインストールします。</p>



<pre class="wp-block-code"><code>sudo cmake --install ~/opencv-build/build
sudo ldconfig
pkg-config --modversion opencv4
4.11.0</code></pre>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh を見てみます。</p>



<pre class="wp-block-code"><code>installed="$(get_opencv_version)"
local_pkg_version="$(get_local_opencv_pkgconfig_version)"

if opencv_matches_required_version "$installed" &amp;&amp; &#91;&#91; "$local_pkg_ok" == "true" ]]; then
  log "OpenCV version $installed already available"
  activate_opencv_environment
  return
fi</code></pre>



<p class="wp-block-paragraph">インストールされたopencvが判別できれば、build_and_install_opencv_required_version() は呼ばれません。</p>



<pre class="wp-block-code"><code>grep -n -E \
  "OPENCV_INSTALL_PREFIX|OPENCV_REQUIRE_LOCAL_PKGCONFIG|get_opencv_version|get_local_opencv_pkgconfig_version|activate_opencv_environment" \
  build-and-install-pins-x64.sh
113:OPENCV_INSTALL_PREFIX="${OPENCV_INSTALL_PREFIX:-/usr/local}"
115:OPENCV_REQUIRE_LOCAL_PKGCONFIG="${OPENCV_REQUIRE_LOCAL_PKGCONFIG:-true}"
460:get_opencv_version() {
463:  if &#91;&#91; -x "$OPENCV_INSTALL_PREFIX/bin/opencv_version" ]]; then
464:    version="$($OPENCV_INSTALL_PREFIX/bin/opencv_version 2&gt;/dev/null || true)"
472:    local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/pkgconfig")
473:    local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib64/pkgconfig")
475:      local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/$multiarch/pkgconfig")
499:get_local_opencv_pkgconfig_version() {
508:  local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/pkgconfig")
509:  local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib64/pkgconfig")
511:    local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/$multiarch/pkgconfig")
532:activate_opencv_environment() {
537:  local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/pkgconfig")
538:  local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib64/pkgconfig")
540:    local_pkg_paths+=("$OPENCV_INSTALL_PREFIX/lib/$multiarch/pkgconfig")
555:  local opencv_cmake_dir="$OPENCV_INSTALL_PREFIX/lib/cmake/opencv4"
558:    export CMAKE_PREFIX_PATH="$OPENCV_INSTALL_PREFIX:${CMAKE_PREFIX_PATH:-}"
561:  export PATH="$OPENCV_INSTALL_PREFIX/bin:${PATH:-}"
562:  export LD_LIBRARY_PATH="$OPENCV_INSTALL_PREFIX/lib:${LD_LIBRARY_PATH:-}"
587:    -DCMAKE_INSTALL_PREFIX="$OPENCV_INSTALL_PREFIX"
607:  installed="$(get_opencv_version)"
609:  local_pkg_version="$(get_local_opencv_pkgconfig_version)"
612:  if is_truthy "$OPENCV_REQUIRE_LOCAL_PKGCONFIG"; then
620:    activate_opencv_environment
630:  if is_truthy "$OPENCV_REQUIRE_LOCAL_PKGCONFIG"; then
634:      warn "Local pkg-config metadata for opencv4 not found under $OPENCV_INSTALL_PREFIX"
640:  activate_opencv_environment
643:  final_version="$(get_opencv_version)"
646:  if is_truthy "$OPENCV_REQUIRE_LOCAL_PKGCONFIG"; then
648:    final_local_pkg_version="$(get_local_opencv_pkgconfig_version)"
1888:    export PKG_CONFIG_PATH="$OPENCV_INSTALL_PREFIX/lib/pkgconfig:${PKG_CONFIG_PATH:-}"
1889:    export LD_LIBRARY_PATH="$OPENCV_INSTALL_PREFIX/lib:${LD_LIBRARY_PATH:-}"
1890:    export CMAKE_PREFIX_PATH="$OPENCV_INSTALL_PREFIX:${CMAKE_PREFIX_PATH:-}"
1891:    export OpenCV_DIR="$OPENCV_INSTALL_PREFIX/lib/cmake/opencv4"</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph"><code>OPENCV_INSTALL_PREFIX</code></p>



<ul class="wp-block-list">
<li>OpenCVのインストール先</li>



<li>今回は <code>/usr/local</code> になっているか確認したい</li>
</ul>



<p class="wp-block-paragraph"><code>OPENCV_REQUIRE_LOCAL_PKGCONFIG</code></p>



<ul class="wp-block-list">
<li><code>pkg-config</code> のOpenCV情報を必須にする設定</li>
</ul>



<p class="wp-block-paragraph"><code>get_opencv_version</code></p>



<ul class="wp-block-list">
<li>システムにインストールされているOpenCVのバージョンを取得する関数</li>
</ul>



<p class="wp-block-paragraph"><code>get_local_opencv_pkgconfig_version</code></p>



<ul class="wp-block-list">
<li><code>pkg-config</code> からOpenCVのバージョンを取得する関数</li>
</ul>



<p class="wp-block-paragraph"><code>activate_opencv_environment</code></p>



<ul class="wp-block-list">
<li>検出したOpenCVをPINSのビルド環境で使えるようにする関数</li>
</ul>
</div>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">opencv-4.11.0を別途で、コンパイル、インストールします。<br>その後、build-and-install-pins-x64.shへの変更は不要です。</p>
</div>



<pre class="wp-block-code"><code>./build-and-install-pins-x64.sh
&#91;INFO] OpenCV version 4.11.0 already available
&#91;INFO] LibXISF API is compatible: /usr/include/libxisf.h
&#91;INFO] Installing .NET 10 SDK
以前に未選択のパッケージ packages-microsoft-prod を選択しています。

以下の追加パッケージがインストールされます:
  aspnetcore-runtime-10.0 aspnetcore-targeting-pack-10.0 dotnet-apphost-pack-10.0 dotnet-host-10.0 dotnet-hostfxr-10.0 dotnet-runtime-10.0 dotnet-sdk-aot-10.0 dotnet-targeting-pack-10.0 dotnet-templates-10.0 liblttng-ust-common1t64
  liblttng-ust-ctl6 liblttng-ust1t64
提案パッケージ:
  aspnetcore-runtime-dbg-10.0 dotnet-runtime-dbg-10.0 dotnet-sdk-dbg-10.0
以下のパッケージが新たにインストールされます:
  aspnetcore-runtime-10.0 aspnetcore-targeting-pack-10.0 dotnet-apphost-pack-10.0 dotnet-host-10.0 dotnet-hostfxr-10.0 dotnet-runtime-10.0 dotnet-sdk-10.0 dotnet-sdk-aot-10.0 dotnet-targeting-pack-10.0 dotnet-templates-10.0
  liblttng-ust-common1t64 liblttng-ust-ctl6 liblttng-ust1t64
アップグレード: 0 個、新規インストール: 13 個、削除: 0 個、保留: 5 個。

&#91;INFO] Toolchain versions

Host:
  Version:      10.0.11
  Architecture: x64
  Commit:       e2f47b0110
  RID:          ubuntu.26.04-x64

.NET SDKs installed:
  10.0.111 &#91;/usr/lib/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.11 &#91;/usr/lib/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.11 &#91;/usr/lib/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  /home/USERNAME/pins/global.json

Learn more:
  https:&#47;&#47;aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download
v22.23.2
10.9.8

fatal: Unable to find refs/remotes/origin/pins revision in submodule path 'Touch-N-Stars'
&#91;WARN] Remote update failed for Touch-N-Stars; falling back to pinned commit
&#91;INFO] Updating submodule NINA.Plugins/ninaAPI

&#91;INFO] Updating submodule NINA.Plugins/LiveStack
Submodule path 'NINA.Plugins/LiveStack': checked out '1c0d473a57eb60d1e07068ec55c7330eebbaec7f'
Submodule 'nina.plugin.livestack.benchmark/External' (https://github.com/isbeorn/nina.external.git) registered for path 'NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External'
Submodule 'nina.plugin.livestack.test/External' (https://github.com/isbeorn/nina.external.git) registered for path 'NINA.Plugins/LiveStack/nina.plugin.livestack.test/External'
Cloning into '/home/USERNAME/pins/NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External'...
Cloning into '/home/USERNAME/pins/NINA.Plugins/LiveStack/nina.plugin.livestack.test/External'...
Submodule path 'NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External': checked out 'de19c6cf64128e93ed78944ddc057ba65fb12c49'
Submodule path 'NINA.Plugins/LiveStack/nina.plugin.livestack.test/External': checked out 'de19c6cf64128e93ed78944ddc057ba65fb12c49'
&#91;INFO] Updating submodule NINA.Plugins/PolarAlignment
Submodule path 'NINA.Plugins/PolarAlignment': checked out 'bafe381399b2d59dd2189d5d75a48da8f13b06d5'
Submodule path 'NINA.Plugins/PolarAlignment/NINA.Plugins.PolarAlignment.Test/External': checked out 'ee668b326e9106d55c12cae035bdc9db879d7b12'
&#91;INFO] Updating submodule NINA.Plugins/joko.nina.plugins

</code></pre>



<p class="wp-block-paragraph">先にビルド、インストールしたopencv4が認識され、PINSのビルドが進みました。</p>



<h2 class="wp-block-heading">Naval Observatory Vector Astrometry Software (NOVAS)</h2>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">海軍天文台ベクトル天体測位ソフトウェア（NOVAS）<br>バージョン 3.1 Fortran、C、および Python 版NOVAS は現在、Astrophysics Source Code Library で入手可能です。</p>



<p class="wp-block-paragraph">NOVASは、位置天文学において一般的に必要とされる様々な量を計算するためのルーチンを統合したパッケージです。このパッケージを使用すると、1回または2回のサブルーチンまたは関数の呼び出しで、あらゆる恒星や惑星の瞬間座標を、様々な座標系で算出することができます。<br><a rel="noopener" target="_blank" href="https://aa.usno.navy.mil/software/novas_info">https://aa.usno.navy.mil/software/novas_info</a></p>
</blockquote>



<p class="wp-block-paragraph">NOVASビルドで止まりました。</p>



<pre class="wp-block-code"><code>du -sh ~/pins/NOVAS31/* 2&gt;/dev/null | sort -h
405G	/home/USERNAME/pins/NOVAS31/cio_ra.bin</code></pre>



<p class="wp-block-paragraph">cio_ra.binが、405GBは異常に大きなファイルになっています。<br>異常なcio_ra.binは削除します。</p>



<pre class="wp-block-code"><code>rm -f ~/pins/NOVAS31/cio_ra.bin
df -h ~
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2       457G   29G  405G   7% /</code></pre>



<p class="wp-block-paragraph">NOVASの生成処理がなぜ異常に大きくなったのか、見ていきます。</p>



<pre class="wp-block-code"><code>cd ~/pins/NOVAS31
sed -n '35,50p' Makefile

# Build the CIO file utility and run it to generate cio_ra.bin
cio_ra.bin: $(SRCDIR)/cio_file.c $(SRCDIR)/CIO_RA.TXT | $(BUILDDIR)
	@echo "Building cio_file utility..."
	$(CC) $(CFLAGS) -o $(BUILDDIR)/cio_file $(SRCDIR)/cio_file.c $(LDLIBS)
	@echo "Generating cio_ra.bin from CIO_RA.TXT..."
	@if &#91; -f cio_ra.bin ]; then rm cio_ra.bin; fi
	@cp $(SRCDIR)/CIO_RA.TXT .
	@./$(BUILDDIR)/cio_file &gt; /dev/null
	@rm -f CIO_RA.TXT
	@if &#91; -f cio_ra.bin ]; then \
		echo "Created cio_ra.bin"; \
	else \
		echo "ERROR: Failed to create cio_ra.bin"; \
		exit 1; \
	fi</code></pre>



<pre class="wp-block-code"><code>CIO_RA.TXT
   ↓
cio_file
   ↓
cio_ra.bin</code></pre>



<p class="wp-block-paragraph">CIO_RA.TXT のサイズを確認します。そのサイズは、132バイト。</p>



<pre class="wp-block-code"><code>cd ~/pins/NOVAS31

ls -lh CIO_RA.TXT
-rw-rw-r-- 1 USERNAME 132 Sep  7 19:06 CIO_RA.TXT
ls -lh NOVAS31/CIO_RA.TXT
-rw-rw-r-- 1 USERNAME 132 Sep  7 09:07 NOVAS31/CIO_RA.TXT</code></pre>



<p class="wp-block-paragraph"><code>CIO_RA.TXT</code> が 132 bytes</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">User’s Guide to NOVAS Version C3.1<br>Naval Observatory Vector Astrometry Software<br><a rel="noopener" target="_blank" href="https://aa.usno.navy.mil/downloads/novas/NOVAS_C3.1_Guide.pdf?utm_source=chatgpt.com">https://aa.usno.navy.mil/downloads/novas/NOVAS_C3.1_Guide.pdf?utm_source=chatgpt.com</a></p>
</blockquote>



<p class="wp-block-paragraph">このガイドによると、CIO_RA.TXT は、<br>cio_ra * basic Computes true right ascension of the CIO, given TT Julian date<br>1700～2300年のデータを含み、約7.5 MB あります。そして cio_file が生成する cio_ra.bin は 約2.9 MB になるのが正常らしいです。<br>こちらのPCにあるデータ量と明らかに違う。。。</p>



<p class="wp-block-paragraph">CIO_RA.TXTを見てみます。</p>



<pre class="wp-block-code"><code>cd ~/pins/NOVAS31
cat -A CIO_RA.TXT
version https://git-lfs.github.com/spec/v1$
oid sha256:94af0088304f458dbb486b1c072c67bdc506edd8da1d3db722e4ae1dcc4b202d$
size 7671616$</code></pre>



<p class="wp-block-paragraph">これは NOVASのCIOデータではないようです。<br>本来のデータ量は、size 7671616、約7MB。<br>Gitで大きなファイルを扱うための仕組みらしい。ポインタみたいな物かな。。。</p>



<p class="wp-block-paragraph">LFS 、Git Large File Storage（Git LFS）を見てみます。</p>



<p class="wp-block-paragraph">git lfs pull を使い、<br>Git LFSの「ポインタファイル」を見て、対応する本物の大きなファイルをダウンロードし、作業ディレクトリに展開するさせます。</p>



<p class="wp-block-paragraph">次で、実体を取得できる。</p>



<pre class="wp-block-code"><code>cd ~/pins　###Git LFSはGitリポジトリ単位で動作する
git lfs pull

ects: 100% (2/2), 8.2 MB | 1.7 MB/s
</code></pre>



<p class="wp-block-paragraph">データが取得されたようです。<br>CIO_RA.TXTを確認します。</p>



<pre class="wp-block-code"><code>wc -c ~/pins/NOVAS31/CIO_RA.TXT
132 /home/USERNAME/pins/NOVAS31/CIO_RA.TXT</code></pre>



<p class="wp-block-paragraph">少ない。こちらは取得されていないようです。</p>



<pre class="wp-block-code"><code>cd ~/pins
git lfs status
On branch develop
Objects to be pushed to origin/develop:

Objects to be committed:

Objects not staged for commit:

	NINA.Plugins/LiveStack (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/NINA.Joko.Plugin.TenMicron (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/PolarAlignment (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/Touch-N-Stars (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/joko.nina.plugins (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/nina.plugin.orbuculum (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/nina.plugin.phd2tools (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/ninaAPI (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/pins.plugin (?: &lt;missing&gt; -&gt; File: deleted)
	NINA/External (?: &lt;missing&gt; -&gt; ?: &lt;missing&gt;)
	build-and-install-pins-x64.sh (Git: 8f458de -&gt; File: b52399e)

git lfs ls-files
4338325ad1 * NINA.Test/Autofocus/TestImage_Jelly.xisf
94af008830 * NOVAS31/NOVAS31/CIO_RA.TXT</code></pre>



<pre class="wp-block-preformatted">94af008830 * NOVAS31/NOVAS31/CIO_RA.TXT</pre>



<p class="wp-block-paragraph">NOVAS31/NOVAS31/CIO_RA.TXT なのでディレクトリが一層下だ。</p>



<pre class="wp-block-code"><code>cd ~/pins/NOVAS31
wc -c NOVAS31/CIO_RA.TXT
7671616 NOVAS31/CIO_RA.TXT</code></pre>



<p class="wp-block-paragraph">以前のビルド生成物を削除します</p>



<pre class="wp-block-code"><code>make clean
rm -rf build libnovas_c.so cio_ra.bin</code></pre>



<p class="wp-block-paragraph">再ビルドします。</p>



<pre class="wp-block-code"><code>make
log後半
gcc -fPIC -O2 -Wall -std=c99 -c -o build/solsys1.o NOVAS31/solsys1.c
gcc -fPIC -O2 -Wall -std=c99 -c -fPIC -o build/solsys1.pic.o NOVAS31/solsys1.c
gcc -shared -o libnovas_c.so build/cio_file.pic.o build/eph_manager.pic.o build/novas.pic.o build/novascon.pic.o build/nutation.pic.o build/readeph0.pic.o build/solsys1.pic.o -lm
Building cio_file utility...
gcc -fPIC -O2 -Wall -std=c99 -o build/cio_file NOVAS31/cio_file.c -lm
NOVAS31/cio_file.c: In function ‘main’:
NOVAS31/cio_file.c:74:4: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
   74 |    fgets (identifier, sizeof(identifier), in_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:88:7: warning: ignoring return value of ‘fscanf’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
   88 |       fscanf (in_file, " %lf %lf ", &amp;jd_tdb, &amp;ra_cio);
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:159:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  159 |    fread (&amp;jd_beg, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:160:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  160 |    fread (&amp;jd_end, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:161:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  161 |    fread (&amp;t_int, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:162:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  162 |    fread (&amp;n_recs, long_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:164:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  164 |    fread (&amp;jd_1, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:165:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  165 |    fread (&amp;ra_1, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:167:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  167 |    fread (&amp;jd_n, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOVAS31/cio_file.c:168:4: warning: ignoring return value of ‘fread’ declared with attribute ‘warn_unused_result’ &#91;-Wunused-result]
  168 |    fread (&amp;ra_n, double_size, (size_t) 1, out_file);
      |    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Generating cio_ra.bin from CIO_RA.TXT...
Created cio_ra.bin
Built libnovas_c.so
rm build/novas.o build/readeph0.o build/solsys1.o build/novascon.o build/cio_file.o build/nutation.o build/eph_manager.o</code></pre>



<pre class="wp-block-code"><code>ls -lh ~/pins/NOVAS31/cio_ra.bin
-rw-rw-r-- 1 USERNAME USERNAME 2.8M Sep  8 12:42 /home/USERNAME/pins/NOVAS31/cio_ra.bin
ls -lh ~/pins/NOVAS31/libnovas_c.so
-rwxrwxr-x 1 USERNAME USERNAME 201K Sep  8 12:42 /home/USERNAME/pins/NOVAS31/libnovas_c.so</code></pre>



<p class="wp-block-paragraph">Git LFSで管理されている CIO_RA.TXT の実体が取得されておらず、132バイトのポインタファイルになっていたことが、解決しました。</p>



<p class="wp-block-paragraph">ここまででの、git状態を見ます。</p>



<pre class="wp-block-code"><code>cd ~/pins
git status --short
 M NINA.Plugins/LiveStack
 M NINA.Plugins/NINA.Joko.Plugin.TenMicron
 M NINA.Plugins/PolarAlignment
 M NINA.Plugins/Touch-N-Stars
 M NINA.Plugins/joko.nina.plugins
 M NINA.Plugins/nina.plugin.orbuculum
 M NINA.Plugins/nina.plugin.phd2tools
 M NINA.Plugins/ninaAPI
 M NINA.Plugins/pins.plugin
 m NINA/External
 M build-and-install-pins-x64.sh
?? NOVAS31/build/
?? NOVAS31/cio_ra.bin
?? NOVAS31/libnovas_c.so
?? artifacts/
?? build-and-install-pins-x64.sh.org

git lfs status
On branch develop
Objects to be pushed to origin/develop:


Objects to be committed:


Objects not staged for commit:

	NINA.Plugins/LiveStack (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/NINA.Joko.Plugin.TenMicron (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/PolarAlignment (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/Touch-N-Stars (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/joko.nina.plugins (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/nina.plugin.orbuculum (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/nina.plugin.phd2tools (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/ninaAPI (?: &lt;missing&gt; -&gt; File: deleted)
	NINA.Plugins/pins.plugin (?: &lt;missing&gt; -&gt; File: deleted)
	NINA/External (?: &lt;missing&gt; -&gt; ?: &lt;missing&gt;)
	build-and-install-pins-x64.sh (Git: 8f458de -&gt; File: b52399e)</code></pre>



<p class="wp-block-paragraph">LFS実体が取得済み / 再ビルドは行えました。そして次のエラーが。。。</p>



<h2 class="wp-block-heading">SDK version: 10.0.400 をインストール</h2>



<h3 class="wp-block-heading">Requested SDK version: 10.0.400</h3>



<pre class="wp-block-code"><code>log
Installing libsofa_c.so to ../../../NINA/External/linux-x64/SOFA/
Installed: ../../../NINA/External/linux-x64/SOFA//libsofa_c.so

*** Now type 'make test'  to install the library and run tests ***

&#91;INFO] External bundle populated from repository clone into NINA/External
&#91;INFO] Staging OpenCvSharp Linux runtime from NuGet
The command could not be loaded, possibly because:
  * You intended to execute a .NET application:
      The application 'nuget' does not exist or is not a managed .dll or .exe.
  * You intended to execute a .NET SDK command:
      A compatible .NET SDK was not found.

Requested SDK version: 10.0.400
global.json file: /home/USERNAME/pins/global.json

Installed SDKs:

Install the &#91;10.0.400] .NET SDK or update &#91;/home/USERNAME/pins/global.json] to match an installed SDK.

Learn about SDK resolution:
https:&#47;&#47;aka.ms/dotnet/sdk-not-found</code></pre>



<p class="wp-block-paragraph">build-and-install-pins-x64.shにある、&#8221;dotnet_10&#8243;をインストールしてる部分を確認します。</p>



<pre class="wp-block-code"><code>grep -n -i -E 'dotnet|sdk|10\.0' ~/pins/build-and-install-pins-x64.sh
68:PLUGIN_TARGET_FRAMEWORK="${PLUGIN_TARGET_FRAMEWORK:-net10.0}"
227:    "wandereretasdk|https://github.com/nitr57/WandererETASDK|"
796:  nuget_global_packages="$(dotnet nuget locals global-packages --list | sed -n 's/^global-packages: //p' | head -n 1)"
804:    dotnet restore NINA/NINA.csproj -r "$TARGET_RUNTIME"
817:install_dotnet_10() {
818:  local dotnet_ok="false"
820:  if command -v dotnet &gt;/dev/null 2&gt;&amp;1; then
821:    if dotnet --list-sdks | grep -q '^10\.'; then
822:      dotnet_ok="true"
826:  if &#91;&#91; "$dotnet_ok" == "true" ]]; then
827:    log ".NET 10 SDK already available"
831:  log "Installing .NET 10 SDK"
844:  run_as_root apt-get install -y dotnet-sdk-10.0
875:  dotnet --info</code></pre>



<p class="wp-block-paragraph">817:install_dotnet_10() {<br>818: local dotnet_ok=&#8221;false&#8221;<br>820: if command -v dotnet &gt;/dev/null 2&gt;&amp;1; then<br>821: if dotnet &#8211;list-sdks | grep -q &#8216;^10.&#8217;; then<br>822: dotnet_ok=&#8221;true&#8221;<br>826: if [[ &#8220;$dotnet_ok&#8221; == &#8220;true&#8221; ]]; then</p>



<p class="wp-block-paragraph">.NET 10.x SDKが何か1つ入っていれば&#8221;OK&#8221;良、入っていないならば、<br>apt-get install -y dotnet-sdk-10.0<br>これでUbuntu 26.04が用意（リポジトリ）しているSDKがインストールされました。<br></p>



<p class="wp-block-paragraph">でも、~/pins/global.jsonは、&#8221;10.0.400&#8243;を要求します。</p>



<pre class="wp-block-code"><code>cat global.json
{
  "sdk": {
    "version": "10.0.400",
    "rollForward": "latestPatch"
  }
}</code></pre>



<h3 class="wp-block-heading">SDK 10.0.400インストール スクリプトを使用</h3>



<p class="wp-block-paragraph">インストール スクリプトを使用するか、バイナリを抽出して linux に.NETをインストールする<br><a rel="noopener" target="_blank" href="https://learn.microsoft.com/ja-jp/dotnet/core/install/linux-scripted-manual">https://learn.microsoft.com/ja-jp/dotnet/core/install/linux-scripted-manual</a><br><a rel="noopener" target="_blank" href="https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual?utm_source=chatgpt.com">https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual?utm_source=chatgpt.com</a></p>



<p class="wp-block-paragraph">公式のインストールスクリプトを取得します。</p>



<pre class="wp-block-code"><code>cd /tmp
wget https://dot.net/v1/dotnet-install.sh -O dotnet-install.sh
chmod +x ./dotnet-install.sh
</code></pre>



<p class="wp-block-paragraph">dotnet-install スクリプト リファレンス<br><a rel="noopener" target="_blank" href="https://learn.microsoft.com/ja-jp/dotnet/core/tools/dotnet-install-script">https://learn.microsoft.com/ja-jp/dotnet/core/tools/dotnet-install-script</a><br>バージョンとインストール先の指定は、こちらに案内されています。</p>



<p class="wp-block-paragraph">10.0.400を指定します。</p>



<pre class="wp-block-code"><code>/tmp/dotnet-install.sh --version 10.0.400 --install-dir "$HOME/.dotnet"</code></pre>



<pre class="wp-block-code"><code>/tmp/dotnet-install.sh --version 10.0.400 --install-dir "$HOME/.dotnet"
dotnet-install: Attempting to download using primary link https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.400/dotnet-sdk-10.0.400-linux-x64.tar.gz
dotnet-install: Remote file https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.400/dotnet-sdk-10.0.400-linux-x64.tar.gz size is 240133692 bytes.
dotnet-install: Extracting archive from https://builds.dotnet.microsoft.com/dotnet/Sdk/10.0.400/dotnet-sdk-10.0.400-linux-x64.tar.gz
dotnet-install: Downloaded file size is 240133692 bytes.
dotnet-install: The remote and local file sizes are equal.
dotnet-install: Installed version is 10.0.400
dotnet-install: Adding to current process PATH: `/home/USERNAME/.dotnet`. Note: This change will be visible only when sourcing script.
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://learn.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
</code></pre>



<p class="wp-block-paragraph">インストール後に次を行います。</p>



<pre class="wp-block-code"><code>$HOME/.dotnet/dotnet --list-sdks
10.0.400 &#91;/home/USERNAME/.dotnet/sdk/10.0.400]</code></pre>



<p class="wp-block-paragraph">パスを通します。<br>PINSスクリプト内の dotnet コマンドにも10.0.400を使わせるため、シェルでPATHを変更します。</p>



<pre class="wp-block-code"><code>export PATH="$HOME/.dotnet:$PATH"</code></pre>



<pre class="wp-block-code"><code>export PATH="$HOME/.dotnet:$PATH"
 which dotnet
/home/USERNAME/.dotnet/dotnet
dotnet --version
10.0.400</code></pre>



<h3 class="wp-block-heading">PINSビルド再開</h3>



<p class="wp-block-paragraph">上記パスを通したシェルで行います。</p>



<pre class="wp-block-code"><code>cd ~/pins
./build-and-install-pins-x64.sh</code></pre>



<pre class="wp-block-code"><code>&#91;INFO] OpenCV version 4.11.0 already available
&#91;INFO] LibXISF API is compatible: /usr/include/libxisf.h
&#91;INFO] .NET 10 SDK already available
&#91;INFO] Node.js 22 already available
&#91;INFO] Toolchain versions
.NET SDK:
 Version:           10.0.400
 Commit:            14fbf8d527
 Workload version:  10.0.400-manifests.330ea142
 MSBuild version:   18.9.6+14fbf8d52

.NET SDKs installed:
  10.0.400 &#91;/home/USERNAME/.dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 10.0.11 &#91;/home/USERNAME/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 10.0.11 &#91;/home/USERNAME/.dotnet/shared/Microsoft.NETCore.App]

&#91;WARN] Remote update failed for Touch-N-Stars; falling back to pinned commit
&#91;INFO] Updating submodule NINA.Plugins/ninaAPI
&#91;INFO] Updating submodule NINA.Plugins/Touch-N-Stars
fatal: Unable to find refs/remotes/origin/main revision in submodule path 'NINA.Plugins/Touch-N-Stars'
&#91;WARN] Remote update failed for NINA.Plugins/Touch-N-Stars; falling back to pinned commit
Submodule path 'NINA.Plugins/Touch-N-Stars': checked out '23f08d5fc14421e9f42cf2d9e27981e49fc4bb8e'
&#91;INFO] Updating submodule NINA.Plugins/LiveStack
Submodule 'nina.plugin.livestack.benchmark/External' (https://github.com/isbeorn/nina.external.git) registered for path 'NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External'
Submodule 'nina.plugin.livestack.test/External' (https://github.com/isbeorn/nina.external.git) registered for path 'NINA.Plugins/LiveStack/nina.plugin.livestack.test/External'
Cloning into '/home/USERNAME/pins/NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External'...
Cloning into '/home/USERNAME/pins/NINA.Plugins/LiveStack/nina.plugin.livestack.test/External'...
Submodule path 'NINA.Plugins/LiveStack/nina.plugin.livestack.benchmark/External': checked out 'de19c6cf64128e93ed78944ddc057ba65fb12c49'
Submodule path 'NINA.Plugins/LiveStack/nina.plugin.livestack.test/External': checked out 'de19c6cf64128e93ed78944ddc057ba65fb12c49'
&#91;INFO] Updating submodule NINA.Plugins/PolarAlignment
Submodule 'NINA.Plugins.PolarAlignment.Test/External' (https://bitbucket.org/Isbeorn/nina.external.git) registered for path 'NINA.Plugins/PolarAlignment/NINA.Plugins.PolarAlignment.Test/External'
Cloning into '/home/USERNAME/pins/NINA.Plugins/PolarAlignment/NINA.Plugins.PolarAlignment.Test/External'...</code></pre>



<p class="wp-block-paragraph">.NET SDKs installed:<br>10.0.400 [/home/USERNAME/.dotnet/sdk]<br>ここで認識されています。</p>



<h3 class="wp-block-heading">pinsdaemon エラー</h3>



<p class="wp-block-paragraph">pinsdaemon は、PINS本体とは別のバックグラウンドサービス（daemon）です。<br>ログを見る限り、主に PINSのシステム管理・アップデート関連を担当するコンポーネントのようです。</p>



<pre class="wp-block-code"><code>以下のパッケージは「削除」されます:
  pinsdaemon
アップグレード: 0 個、新規インストール: 0 個、削除: 1 個、保留: 21 個。
1 個のパッケージが完全にインストールまたは削除されていません。
この操作後に追加で 0 B のディスク容量が消費されます。
(データベースを読み込んでいます ... 現在 229731 個のファイルとディレクトリがインストールされています。)
pinsdaemon (1.0.6-1788846944) を削除しています ...
dpkg: 警告: pinsdaemon の削除中、ディレクトリ '/usr/local/bin' が空でないため削除できませんでした
(データベースを読み込んでいます ... 現在 229706 個のファイルとディレクトリがインストールされています。)
.../pins_3.3.0.1057-nightly+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins (3.3.0.1057-nightly+1788846944) で (3.3.0.1057-nightly+1788846944 に) 上書き展開しています ...
以前に未選択のパッケージ pinsdaemon を選択しています。
.../pinsdaemon_1.0.6-1788846944_amd64.deb を展開する準備をしています ...
pinsdaemon (1.0.6-1788846944) を展開しています...
.../pins-wandereretasdk_3.3.0.1057-nightly+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-wandereretasdk (3.3.0.1057-nightly+1788846944) で (3.3.0.1057-nightly+1788846944 に) 上書き展開しています ...
.../pins-plugin-joko_4.0.0.17+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-joko (4.0.0.17+1788846944) で (4.0.0.17+1788846944 に) 上書き展開しています ...
.../pins-plugin-tenmicron_3.0.0.13+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-tenmicron (3.0.0.13+1788846944) で (3.0.0.13+1788846944 に) 上書き展開しています ...
.../pins-plugin-livestack_1.0.1.2+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-livestack (1.0.1.2+1788846944) で (1.0.1.2+1788846944 に) 上書き展開しています ...
.../pins-plugin-ninaapi_2.2.15.2+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-ninaapi (2.2.15.2+1788846944) で (2.2.15.2+1788846944 に) 上書き展開しています ...
.../pins-plugin-orbuculum_2.0.0.2+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-orbuculum (2.0.0.2+1788846944) で (2.0.0.2+1788846944 に) 上書き展開しています ...
.../pins-plugin-phd2tools_1.0.5.3+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-phd2tools (1.0.5.3+1788846944) で (1.0.5.3+1788846944 に) 上書き展開しています ...
.../pins-plugin-polaralignment_2.2.3.4+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-polaralignment (2.2.3.4+1788846944) で (2.2.3.4+1788846944 に) 上書き展開しています ...
.../pins-plugin-touch-n-stars_1.4.0.1+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-touch-n-stars (1.4.0.1+1788846944) で (1.4.0.1+1788846944 に) 上書き展開しています ...
.../pins-plugin-pins_1.0.3.0+1788846944_amd64_08092026.deb を展開する準備をしています ...
pins-plugin-pins (1.0.3.0+1788846944) で (1.0.3.0+1788846944 に) 上書き展開しています ...
.../indi-bin_2.1.9+1788846944_amd64_08092026.deb を展開する準備をしています ...
indi-bin (2.1.9+1788846944) で (2.1.9+1788846944 に) 上書き展開しています ...
.../libindi1_2.1.9+1788846944_amd64_08092026.deb を展開する準備をしています ...
libindi1 (2.1.9+1788846944) で (2.1.9+1788846944 に) 上書き展開しています ...
.../libindi-data_2.1.9+1788846944_amd64_08092026.deb を展開する準備をしています ...
libindi-data (2.1.9+1788846944) で (2.1.9+1788846944 に) 上書き展開しています ...
.../libindi-dev_2.1.9+1788846944_amd64_08092026.deb を展開する準備をしています ...
libindi-dev (2.1.9+1788846944) で (2.1.9+1788846944 に) 上書き展開しています ...
.../phd2_2.6.14-1788846974_amd64.deb を展開する準備をしています ...
phd2 (2.6.14-1788846974) で (2.6.14-1788846974 に) 上書き展開しています ...

dpkg: 依存関係の問題により pinsdaemon の設定ができません:
 pinsdaemon は以下に依存 (depends) します: python3-venv ...しかし:
  パッケージ python3-venv はまだインストールされていません。
 pinsdaemon は以下に依存 (depends) します: wireless-tools ...しかし:
  パッケージ wireless-tools はまだインストールされていません。
 pinsdaemon は以下に依存 (depends) します: raspi-config ...しかし:
  パッケージ raspi-config はまだインストールされていません。

dpkg: パッケージ pinsdaemon の処理中にエラーが発生しました (--install):
 依存関係の問題 - 設定を見送ります
pins-wandereretasdk (3.3.0.1057-nightly+1788846944) を設定しています ...
pins-plugin-joko (4.0.0.17+1788846944) を設定しています ...
pins-plugin-tenmicron (3.0.0.13+1788846944) を設定しています ...
pins-plugin-livestack (1.0.1.2+1788846944) を設定しています ...
pins-plugin-ninaapi (2.2.15.2+1788846944) を設定しています ...
pins-plugin-orbuculum (2.0.0.2+1788846944) を設定しています ...
pins-plugin-phd2tools (1.0.5.3+1788846944) を設定しています ...
pins-plugin-polaralignment (2.2.3.4+1788846944) を設定しています ...
pins-plugin-touch-n-stars (1.4.0.1+1788846944) を設定しています ...
pins-plugin-pins (1.0.3.0+1788846944) を設定しています ...
libindi1 (2.1.9+1788846944) を設定しています ...
libindi-data (2.1.9+1788846944) を設定しています ...
libindi-dev (2.1.9+1788846944) を設定しています ...
phd2 (2.6.14-1788846974) を設定しています ...
indi-bin (2.1.9+1788846944) を設定しています ...
libc-bin (2.43-2ubuntu2.3) のトリガを処理しています ...
gnome-menus (3.38.1-1ubuntu1) のトリガを処理しています ...
desktop-file-utils (0.28-1build1) のトリガを処理しています ...
処理中にエラーが発生しました:
 pinsdaemon</code></pre>



<p class="wp-block-paragraph">pinsdaemon は以下に依存:<br>python3-venv<br>wireless-tools<br>raspi-config<br>特に raspi-config が依存に入っているため、Raspberry Pi環境を想定した機能を含んでいることが分かります。</p>



<p class="wp-block-paragraph">次のパッケージは入っています。<br>pins<br>pins-wandereretasdk<br>pins-plugin-joko<br>pins-plugin-tenmicron<br>pins-plugin-livestack<br>pins-plugin-ninaapi<br>pins-plugin-orbuculum<br>pins-plugin-phd2tools<br>pins-plugin-polaralignment<br>pins-plugin-touch-n-stars<br>pins-plugin-pins<br>indi-bin<br>libindi1<br>libindi-data<br>libindi-dev<br>phd2</p>



<p class="wp-block-paragraph">build-and-install-pins-x64.sh の pinsdaemon を作っている箇所を見てみる。</p>



<pre class="wp-block-code"><code>grep -n -i -C 5 'pinsdaemon' ~/pins/build-and-install-pins-x64.sh
221-    "orbuculum|https://github.com/nitr57/nina.plugin.orbuculum|"
222-    "polaralignment|https://github.com/nitr57/nina.plugin.polaralignment|"
223-    "livestack|https://github.com/nitr57/nina.plugin.livestack|"
224-    "tenmicron|https://github.com/nitr57/NINA.Joko.Plugin.TenMicron|"
225-    "pins-plugin|https://github.com/nitr57/pins.plugin|"
226:    "pinsdaemon|https://github.com/Touch-N-Stars/pinsdaemon|"
227-    "wandereretasdk|https://github.com/nitr57/WandererETASDK|"
228-    "touch-frontend|https://github.com/Touch-N-Stars/Touch-N-Stars|develop"
229-  )
230-
231-  local item
--
1146-  ) &gt; "$CORE_EXCLUDES_FILE"
1147-
1148-  log "Built core package: $deb_path"
1149-}
1150-
1151:build_pinsdaemon_package() {
1152:  log "Building pinsdaemon package"
1153-
1154:  rm -rf pinsdaemon
1155:  git clone https://github.com/Touch-N-Stars/pinsdaemon pinsdaemon
1156-
1157:  pushd pinsdaemon &gt;/dev/null
1158:  mkdir -p build/opt/pinsdaemon
1159-  mkdir -p build/usr/local/bin
1160-  mkdir -p build/etc/systemd/system
1161-  mkdir -p build/etc/sudoers.d
1162-  mkdir -p build/home/$TARGET_USER/pins-scripts
1163-  mkdir -p build/lib/udev/rules.d
1164-  mkdir -p build/DEBIAN
1165-
1166:  cp -r app build/opt/pinsdaemon/
1167:  cp requirements.txt build/opt/pinsdaemon/
1168:  cp README.md build/opt/pinsdaemon/
1169-
1170-  cp scripts/system-upgrade.sh build/usr/local/bin/
1171-  cp scripts/manage-samba.sh build/usr/local/bin/
1172-  cp scripts/wifi-connect.sh build/usr/local/bin/
1173-  cp scripts/wifi-automanage.py build/usr/local/bin/
--
1186-  chmod 755 build/DEBIAN/postinst
1187-  chmod 755 build/DEBIAN/prerm
1188-
1189-  local base_version
1190-  base_version="$(grep '^Version:' packaging/DEBIAN/control | awk '{print $2}')"
1191:  &#91;&#91; -n "$base_version" ]] || fail "Unable to parse pinsdaemon base version"
1192-
1193-  local full_version="${base_version}-${BUILD_NUMBER}"
1194-  sed -i -E "s/^Version:.*/Version: ${full_version}/" build/DEBIAN/control
1195-  sed -i -E "s/^Architecture:.*/Architecture: ${DEB_ARCH}/" build/DEBIAN/control
1196-
1197:  local deb_path="../artifacts/pinsdaemon_${full_version}_${DEB_ARCH}.deb"
1198-  dpkg-deb --root-owner-group --build build "$deb_path"
1199-  sha256sum "$deb_path" &gt; "$deb_path.sha256"
1200-  record_built_deb "$deb_path"
1201-
1202-  popd &gt;/dev/null
1203-
1204:  log "Built pinsdaemon package"
1205-}
1206-
1207-build_wandereretasdk_package() {
1208-  log "Building WandererETASDK package"
1209-
--
2132-  populate_external_bundle
2133-  stage_opencvsharp_runtime_from_nuget
2134-
2135-  determine_versions
2136-  build_core_pins_package
2137:  build_pinsdaemon_package
2138-  build_wandereretasdk_package
2139-  build_plugins
2140-  build_indi_debian_packages
2141-  build_phd2_package
2142-  if is_truthy "$CREATE_FIRMWARE_BUNDLE"; then</code></pre>



<p class="wp-block-paragraph">&#8220;pinsdaemon|https://github.com/Touch-N-Stars/pinsdaemon|&#8221;<br>ここでGitHubから取得しています。<br>build_pinsdaemon_package() {<br>で .deb を作っています。</p>



<p class="wp-block-paragraph">pinsdaemon の DEBIAN/control を見て、どの依存関係を要求しているのかを確認します。</p>



<pre class="wp-block-code"><code>grep -n -E '^(Package|Version|Architecture|Depends|Recommends):' \
  ~/pins/pinsdaemon/packaging/DEBIAN/control
1:Package: pinsdaemon
2:Version: 1.0.6
5:Architecture: arm64
7:Depends: python3, python3-venv, sudo, bash, util-linux, network-manager, wireless-tools, unzip, usbutils, rfkill, iw, iputils-ping, avahi-daemon, raspi-config, locales, keyboard-configuration</code></pre>



<p class="wp-block-paragraph">raspi-config はRaspberry Pi用の設定ツールで、公式リポジトリの実装にもPiのアーキテクチャ・ボード判定が入っています。</p>



<p class="wp-block-paragraph">公式リポジトリ<br><a rel="noopener" target="_blank" href="https://github.com/RPi-Distro/raspi-config/blob/trixie/raspi-config?utm_source=chatgpt.com">https://github.com/RPi-Distro/raspi-config/blob/trixie/raspi-config?utm_source=chatgpt.com</a></p>



<p class="wp-block-paragraph">Raspberry Pi固有の機能は不要なので、今回はpinsdaemonの機能は除外します。</p>



<h3 class="wp-block-heading">build_pinsdaemon_package の呼び出しをスキップさせる</h3>



<p class="wp-block-paragraph">pinsdaemonの機能は除外します。</p>



<p class="wp-block-paragraph">build_pinsdaemon_package の呼び出しだけを、x86_64ではスキップさせます。</p>



<pre class="wp-block-code"><code>  determine_versions
  build_core_pins_package
  # pinsdaemon is Raspberry Pi/ARM64-specific; skip on x86_64
  if &#91;&#91; "$DEB_ARCH" == "arm64" ]]; then
    build_pinsdaemon_package
  fi
  build_wandereretasdk_package
  build_plugins
  build_indi_debian_packages
  build_phd2_package
  if is_truthy "$CREATE_FIRMWARE_BUNDLE"; then
    create_firmware_bundle
  else
    log "Skipping firmware bundle zip creation"
  fi
  install_built_packages
  setup_runtime_prerequisites
  save_successful_build_state

  print_summary
}
</code></pre>



<pre class="wp-block-code"><code>nano build-and-install-pins-x64.sh</code></pre>



<p class="wp-block-paragraph">変更前：</p>



<pre class="wp-block-code"><code>build_core_pins_package
build_pinsdaemon_package
build_wandereretasdk_package</code></pre>



<p class="wp-block-paragraph">変更後：</p>



<pre class="wp-block-code"><code>build_core_pins_package
# pinsdaemon is Raspberry Pi/ARM64-specific; skip on x86_64
if &#91;&#91; "$DEB_ARCH" == "arm64" ]]; then
  build_pinsdaemon_package
fi
build_wandereretasdk_package</code></pre>



<p class="wp-block-paragraph">スクリプトが「作成済み .deb を全部インストール」する仕組みなので、<br>以前作った、artifacts/pinsdaemon_1.0.6-&#8230;.debパッケージをインストールするかもしれません。<br>そこで、今回生成された pinsdaemon のdebだけを削除します。</p>



<pre class="wp-block-code"><code>rm -f artifacts/pinsdaemon_*.deb
rm -f artifacts/pinsdaemon_*.deb.sha256</code></pre>



<p class="wp-block-paragraph">ビルドを再実行</p>



<pre class="wp-block-code"><code>パッケージリストを読み込んでいます... 完了
依存関係ツリーを作成しています... 完了        
状態情報を読み取っています... 完了

これらを直すためには 'apt --fix-broken install' を実行する必要があるかもしれません。
以下のパッケージには満たせない依存関係があります:
 pinsdaemon : 依存: python3-venv しかし、インストールされようとしていません
              依存: wireless-tools しかし、インストールすることができません
              依存: raspi-config しかし、インストールされようとしていません
E: 未解決の依存関係です。'apt --fix-broken install' を実行してみてください (または解法を明示してください)。</code></pre>



<pre class="wp-block-code"><code>dpkg -l pinsdaemon
+-- Desired=Unknown/Install/Remove/Purge/Hold
|+- Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
||+ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||| 名前           バージョン       アーキテクチ 説明
+++-==============-================-============-=================================
iU  pinsdaemon     1.0.6-1788846944 amd64        System Upgrade API Daemon</code></pre>



<p class="wp-block-paragraph">pinsdaemon を使わないので、削除します。pinsdaemon を先に除去します。</p>



<pre class="wp-block-code"><code>sudo dpkg --remove --force-remove-reinstreq pinsdaemon
sudo dpkg --configure -a
sudo apt --fix-broken install</code></pre>



<p class="wp-block-paragraph">sudo dpkg &#8211;configure -a ：システム内で未完了となっている全ての設定を自動で片付ける。ソフトウェアのアップデート中にエラーが起きたときの修復手順です。</p>



<pre class="wp-block-code"><code>dpkg -l pinsdaemon
dpkg-query: pinsdaemon に一致するパッケージが見つかりません</code></pre>



<p class="wp-block-paragraph">./build-and-install-pins-x64.sh　を行います。</p>



<h2 class="wp-block-heading">PHD2エラー</h2>



<p class="wp-block-paragraph">phd2をビルド時に、libindiが見つからないと言ってます。</p>



<pre class="wp-block-code"><code>-- Using system's libindi
-- Checking for module 'libindi'
--   Package 'libindi' not found
CMake Error at cmake_modules/FindINDI.cmake:136 (message):
  INDI not found.  Please install INDI and try again.
Call Stack (most recent call first):
  thirdparty/thirdparty.cmake:487 (find_package)
  CMakeLists.txt:125 (include)

==&gt; CMakeCache.txt &lt;==
# This is the CMakeCache file.
# For build in directory: /home/USERNAME/pins-build-src/artifacts/src/phd2/obj-x86_64-linux-gnu
# It was generated by CMake: /usr/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:</code></pre>



<pre class="wp-block-code"><code>dpkg -l | grep -E 'libindi|indi-bin'
ii  indi-bin                                        2.1.9+1788846944                           amd64        INDI core library, server, and drivers built from upstream v2.1.9
ii  libindi-data                                    2.1.9+1788846944                           amd64        INDI shared data files built from upstream v2.1.9
ii  libindi-dev                                     2.1.9                                      all          Dummy libindi-dev package (local build)
ii  libindi1                                        2.1.9+1788846944                           amd64        INDI runtime shared libraries built from upstream v2.1.9</code></pre>



<p class="wp-block-paragraph">ii libindi-dev 2.1.9 all Dummy libindi-dev package (local build)<br>ダミーバージョンになってます。（なんでやねん）</p>



<p class="wp-block-paragraph">なぜダミーを作るのか、見てみます。</p>



<pre class="wp-block-code"><code>grep -Rni "libindi-dev" ~/pins/build-and-install-pins-x64.sh
1698:    echo "Package: libindi-dev"
1705:    echo "Replaces: libindi-dev (&lt;&lt; $INDI_VERSION)"
1717:  local dev_output="artifacts/libindi-dev_${package_version}_${DEB_ARCH}_${RELEASE_DATE}.deb"
1814:  local equivs_dir="/tmp/libindi-dev-equivs"
1822:Package: libindi-dev
1826:Description: Dummy libindi-dev package (local build)
1833:  run_as_root dpkg -i "$equivs_dir/libindi-dev_${PHD2_INDI_VERSION}_all.deb"

grep -Rni "Dummy libindi-dev" ~/pins ~/pins-build-src 2&gt;/dev/null
/home/USERNAME/pins/artifacts/src/phd2/.github/workflows/build-arm64-deb.yml:84:          Description: Dummy libindi-dev package (CI)
/home/USERNAME/pins/build-and-install-pins-x64.sh.bak:1826:Description: Dummy libindi-dev package (local build)
/home/USERNAME/pins/build-and-install-pins-x64.sh.org:1821:Description: Dummy libindi-dev package (local build)
/home/USERNAME/pins/build-and-install-pins-x64.sh:1826:Description: Dummy libindi-dev package (local build)
/home/USERNAME/pins-build-src/artifacts/src/phd2/.github/workflows/build-arm64-deb.yml:84:          Description: Dummy libindi-dev package (CI)
/home/USERNAME/pins-build-src/build-and-install-pins-x64.sh:1821:Description: Dummy libindi-dev package (local build)</code></pre>



<p class="wp-block-paragraph">1826行目にあります。</p>



<p class="wp-block-paragraph">PHD2 のビルド<br>↓<br>「libindi-dev が必要」と言われる<br>↓<br>equivs でダミー libindi-dev を作る<br>↓<br>依存関係だけ満たす</p>



<p class="wp-block-paragraph">しかし、既にスクリプト自身が、<br>artifacts/libindi-dev_2.1.9+1788846944_amd64.deb<br>という本物の開発パッケージを生成しています。</p>



<p class="wp-block-paragraph">ダミーを作る部分を訂正します。</p>



<pre class="wp-block-code"><code>sed -n '1790,1840p' ~/pins/build-and-install-pins-x64.sh

    if &#91; -f /etc/apt/sources.list.d/ubuntu.sources ]; then \
      sed -i 's/^Types: deb$/Types: deb deb-src/' /etc/apt/sources.list.d/ubuntu.sources; \
    elif &#91; -f /etc/apt/sources.list.d/debian.sources ]; then \
      sed -i 's/^Types: deb$/Types: deb deb-src/' /etc/apt/sources.list.d/debian.sources; \
    elif &#91; -f /etc/apt/sources.list ]; then \
      sed -i '/^deb /p; s/^deb /deb-src /' /etc/apt/sources.list; \
    fi"
  run_as_root apt-get update

  local projects_home
  projects_home="${HOME}/Projects"
  mkdir -p "$projects_home" "$projects_home/build"

  local indi_core_src="$projects_home/indi-core"
  local indi_core_build="$projects_home/build/indi-core"
  rm -rf "$indi_core_src" "$indi_core_build"
  git clone --depth 1 --branch "v$PHD2_INDI_VERSION" https://github.com/indilib/indi.git "$indi_core_src"
  cmake -S "$indi_core_src" -B "$indi_core_build" \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DCMAKE_BUILD_TYPE=Release
  cmake --build "$indi_core_build" --parallel "$(nproc)"
  run_as_root cmake --install "$indi_core_build"
  run_as_root ldconfig

  local equivs_dir="/tmp/libindi-dev-equivs"
  rm -rf "$equivs_dir"
  mkdir -p "$equivs_dir"
  cat &gt; "$equivs_dir/control" &lt;&lt;EOF
Section: misc
Priority: optional
Standards-Version: 4.7.0

Package: libindi-dev
Version: ${PHD2_INDI_VERSION}
Maintainer: Local Builder &lt;builder@local&gt;
Architecture: all
Description: Dummy libindi-dev package (local build)
 Dummy package to satisfy Build-Depends when INDI is built from source.
EOF
  (
    cd "$equivs_dir"
    equivs-build control
  )
  run_as_root dpkg -i "$equivs_dir/libindi-dev_${PHD2_INDI_VERSION}_all.deb"

  (
    cd "$phd2_src"
    run_as_root mk-build-deps --install --remove \
      --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y" \
      debian/control
  )</code></pre>



<pre class="wp-block-code"><code>  local equivs_dir="/tmp/libindi-dev-equivs"
  rm -rf "$equivs_dir"
  mkdir -p "$equivs_dir"
  cat &gt; "$equivs_dir/control" &lt;&lt;EOF
Section: misc
Priority: optional
Standards-Version: 4.7.0

Package: libindi-dev
Version: ${PHD2_INDI_VERSION}
Maintainer: Local Builder &lt;builder@local&gt;
Architecture: all
Description: Dummy libindi-dev package (local build)
 Dummy package to satisfy Build-Depends when INDI is built from source.
EOF</code></pre>



<p class="wp-block-paragraph">この部分で、PHD2 のビルド依存を満たすために、わざとダミーの libindi-dev を作っています。<br>そして、ダミーをインストールしています。</p>



<pre class="wp-block-code"><code>  run_as_root dpkg -i "$equivs_dir/libindi-dev_${PHD2_INDI_VERSION}_all.deb"</code></pre>



<p class="wp-block-paragraph">ダミーではなく、<br>artifacts/libindi-dev_2.1.9+1788846944_amd64.deb<br>をインストールするように変更するべきです。</p>



<p class="wp-block-paragraph">./build-and-install-pins-x64.shを変更します。</p>



<p class="wp-block-paragraph">変更前：</p>



<pre class="wp-block-code"><code>  cmake --build "$indi_core_build" --parallel "$(nproc)"
  run_as_root cmake --install "$indi_core_build"
  run_as_root ldconfig

  local equivs_dir="/tmp/libindi-dev-equivs"
  rm -rf "$equivs_dir"
  mkdir -p "$equivs_dir"
  cat &gt; "$equivs_dir/control" &lt;&lt;EOF
Section: misc
Priority: optional
Standards-Version: 4.7.0

Package: libindi-dev
Version: ${PHD2_INDI_VERSION}
Maintainer: Local Builder &lt;builder@local&gt;
Architecture: all
Description: Dummy libindi-dev package (local build)
 Dummy package to satisfy Build-Depends when INDI is built from source.
EOF
  (
    cd "$equivs_dir"
    equivs-build control
  )
  run_as_root dpkg -i "$equivs_dir/libindi-dev_${PHD2_INDI_VERSION}_all.deb"

  (
    cd "$phd2_src"
    run_as_root mk-build-deps --install --remove \
      --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y" \
      debian/control
  )</code></pre>



<p class="wp-block-paragraph">変更後：上記ブロック以下に変更します。</p>



<pre class="wp-block-code"><code>  cmake --build "$indi_core_build" --parallel "$(nproc)"
  run_as_root cmake --install "$indi_core_build"
  run_as_root ldconfig

  local libindi_dev_deb
  libindi_dev_deb="$(find artifacts -maxdepth 1 -type f -name "libindi-dev_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
  &#91;&#91; -n "$libindi_dev_deb" ]] || fail "libindi-dev package not found"

  run_as_root dpkg -i "$libindi_dev_deb"

  (
    cd "$phd2_src"
    run_as_root mk-build-deps --install --remove \
      --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y" \
      debian/control
  )</code></pre>



<p class="wp-block-paragraph">PHD2 のビルド部分には、<br>必要な依存パッケージを揃える処理を加えます。</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">mk-build-deps<br>↓<br>PHD2 の debian/control を読む<br>↓<br>必要なビルド依存パッケージを解析<br>↓<br>一時的な依存パッケージを生成<br>↓<br>apt-get で依存パッケージをインストール<br>↓<br>&#8211;remove により一時メタパッケージを削除</p>
</div>



<p class="wp-block-paragraph"></p>



<pre class="wp-block-code"><code>sudo dpkg --remove libindi-dev
dpkg: 依存関係の問題により、libindi-dev の削除ができません:
 phd2-build-deps は以下に依存 (depends) します: libindi-dev (&gt;= 2.0).

dpkg: パッケージ libindi-dev の処理中にエラーが発生しました (--remove):
 依存関係の問題 - 削除しません
処理中にエラーが発生しました:
 libindi-dev</code></pre>



<pre class="wp-block-code"><code>sudo dpkg --remove phd2-build-deps
sudo dpkg --remove libindi-dev</code></pre>



<p class="wp-block-paragraph">確認します。</p>



<pre class="wp-block-code"><code>dpkg -l libindi-dev
dpkg-query: libindi-dev に一致するパッケージが見つかりません</code></pre>



<p class="wp-block-paragraph">./build-and-install-pins-x64.sh再実行</p>



<h2 class="wp-block-heading">libindi-dev のバージョンが libindi1 と一致しない</h2>



<pre class="wp-block-code"><code>以前に未選択のパッケージ libindi-dev を選択しています。
(データベースを読み込んでいます ... 現在 229568 個のファイルとディレクトリがインストールされています。)
.../libindi-dev_2.1.9+1788858200_amd64_08092026.deb を展開する準備をしています ...
libindi-dev (2.1.9+1788858200) を展開しています...
dpkg: 依存関係の問題により libindi-dev の設定ができません:
 libindi-dev は以下に依存 (depends) します: libindi1 (= 2.1.9+1788858200) ...しかし:
  システム上の libindi1 のバージョンは 2.1.9+1788846944 です。

dpkg: パッケージ libindi-dev の処理中にエラーが発生しました (--install):
 依存関係の問題 - 設定を見送ります
処理中にエラーが発生しました:
 libindi-dev</code></pre>



<p class="wp-block-paragraph">libindi-dev のバージョンが libindi1 と一致していません。<br>build_indi_debian_packages<br>↓<br>libindi1 = 2.1.9+1788846944<br>libindi-dev = 2.1.9+1788858200libindi1 が古い</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E '^ii  (libindi1|libindi-dev|indi-bin|libindi-data)'
ii  indi-bin                                        2.1.9+1788846944                           amd64        INDI core library, server, and drivers built from upstream v2.1.9
ii  libindi-data                                    2.1.9+1788846944                           amd64        INDI shared data files built from upstream v2.1.9
ii  libindi1                                        2.1.9+1788846944                           amd64        INDI runtime shared libraries built from upstream v2.1.9</code></pre>



<p class="wp-block-paragraph">あら、そろってる。。。でも、</p>



<div class="wp-block-cocoon-blocks-info-box block-box primary-box">
<p class="wp-block-paragraph">libindi-dev 未インストール<br>今回スクリプトがインストールしようとした libindi-dev は、<br>2.1.9+1788858200</p>
</div>



<pre class="wp-block-code"><code>ls -l artifacts/indi-bin_*.deb
ls -l artifacts/libindi1_*.deb
ls -l artifacts/libindi-data_*.deb
ls -l artifacts/libindi-dev_*.deb</code></pre>



<pre class="wp-block-code"><code>artifacts/indi-bin_2.1.9+1788846944_amd64_08092026.deb
artifacts/libindi1_2.1.9+1788846944_amd64_08092026.deb
artifacts/libindi-data_2.1.9+1788846944_amd64_08092026.deb
artifacts/libindi-dev_2.1.9+1788846944_amd64_08092026.deb</code></pre>



<p class="wp-block-paragraph">古い libindi-dev が残っていたのではなく、build_phd2_package が別の libindi-dev を拾っています。</p>



<pre class="wp-block-code"><code>dpkg -l libindi-dev
+-- Desired=Unknown/Install/Remove/Purge/Hold
|+- Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
||+ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||| 名前           バージョン       アーキテクチ 説明
+++-==============-================-============-======================================================================
iU  libindi-dev    2.1.9+1788858200 amd64        INDI development headers and build metadata built from upstream v2.1.9</code></pre>



<p class="wp-block-paragraph"> iU の意味は、<br>i = インストールする。<br>U = Unpacked（展開済み）だが、設定（configure）されていない。</p>



<p class="wp-block-paragraph">古い iU を削除します。<br>依存関係で phd2-build-deps が残っていると削除できないので、</p>



<pre class="wp-block-code"><code>sudo dpkg --remove phd2-build-deps
sudo dpkg --remove libindi-dev</code></pre>



<p class="wp-block-paragraph">古い3パッケージを、新しいビルドでまとめて置き換えます。<br>再実行前にやること：</p>



<pre class="wp-block-code"><code>sudo dpkg --remove phd2-build-deps 2&gt;/dev/null || true
sudo dpkg --remove libindi-dev 2&gt;/dev/null || true</code></pre>



<p class="wp-block-paragraph">既存の古い INDI パッケージも削除します。</p>



<pre class="wp-block-code"><code>sudo dpkg --remove indi-bin libindi1 libindi-data</code></pre>



<p class="wp-block-paragraph">削除を確認します。</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E '^ii  (indi-bin|libindi1|libindi-data|libindi-dev)'
何も表示がなければ、削除できている。</code></pre>



<p class="wp-block-paragraph">スクリプトを再実行</p>



<pre class="wp-block-code"><code>./build-and-install-pins-x64.sh</code></pre>



<h3 class="wp-block-heading">build_phd2_package() を修正</h3>



<pre class="wp-block-code"><code>dpkg: 依存関係の問題により libindi-dev の設定ができません:
 libindi-dev は以下に依存 (depends) します: libindi1 (= 2.1.9+1788864166) ...しかし:
  パッケージ libindi1 はまだインストールされていません。</code></pre>



<p class="wp-block-paragraph">libindi1を入れてから、libindi-devをインストールするはずが、逆になっています。</p>



<p class="wp-block-paragraph">build-and-install-pins-x64.shにある1814行付近、 <br><code>local libindi1_deb</code><br>run_as_root dpkg -i &#8220;$libindi1_deb&#8221;<br>追加します。</p>



<pre class="wp-block-code"><code>  cmake --build "$indi_core_build" --parallel "$(nproc)"
  run_as_root cmake --install "$indi_core_build"
  run_as_root ldconfig

  local libindi1_deb
  libindi1_deb="$(find artifacts -maxdepth 1 -type f -name "libindi1_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
  &#91;&#91; -n "$libindi1_deb" ]] || fail "libindi1 package not found"
  
  local libindi_dev_deb
  libindi_dev_deb="$(find artifacts -maxdepth 1 -type f -name "libindi-dev_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
  &#91;&#91; -n "$libindi_dev_deb" ]] || fail "libindi-dev package not found"

  run_as_root dpkg -i "$libindi1_deb"
  run_as_root dpkg -i "$libindi_dev_deb"

  (
    cd "$phd2_src"
    run_as_root mk-build-deps --install --remove \
      --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y" \
      debian/control
  )
</code></pre>



<pre class="wp-block-code"><code>エラー
zip はすでに最新バージョン (3.0-15ubuntu3) です。
zlib1g-dev はすでに最新バージョン (1:1.3.dfsg+really1.3.1-1ubuntu3.1) です。
これらを直すためには 'apt --fix-broken install' を実行する必要があるかもしれません。
以下のパッケージには満たせない依存関係があります:
 libindi-dev : 依存: libindi1 (= 2.1.9+1788864166) しかし、インストールすることができません
E: 未解決の依存関係です。'apt --fix-broken install' を実行してみてください (または解法を明示してください)。</code></pre>



<pre class="wp-block-code"><code>grep -n -A20 -B5 'local libindi1_deb' ~/pins/build-and-install-pins-x64.sh
1809-    -DCMAKE_BUILD_TYPE=Release
1810-  cmake --build "$indi_core_build" --parallel "$(nproc)"
1811-  run_as_root cmake --install "$indi_core_build"
1812-  run_as_root ldconfig
1813-
1814:  local libindi1_deb
1815-  libindi1_deb="$(find artifacts -maxdepth 1 -type f -name "libindi1_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
1816-  &#91;&#91; -n "$libindi1_deb" ]] || fail "libindi1 package not found"
1817-  
1818-  local libindi_dev_deb
1819-  libindi_dev_deb="$(find artifacts -maxdepth 1 -type f -name "libindi-dev_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
1820-  &#91;&#91; -n "$libindi_dev_deb" ]] || fail "libindi-dev package not found"
1821-
1822-  run_as_root dpkg -i "$libindi1_deb"
1823-  run_as_root dpkg -i "$libindi_dev_deb"
1824-
1825-  (
1826-    cd "$phd2_src"
1827-    run_as_root mk-build-deps --install --remove \
1828-      --tool "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y" \
1829-      debian/control
1830-  )
1831-
1832-  ensure_opencv_required_version
1833-
1834-  if is_truthy "$PHD2_BUILD_INDI_3RDPARTY"; then</code></pre>



<p class="wp-block-paragraph">この2行が変更対象です。<br>libindi1_deb=&#8221;$(find artifacts -maxdepth 1 -type f -name &#8220;libindi1_*_${DEB_ARCH}_*.deb&#8221; | sort -V | tail -1)&#8221;</p>



<p class="wp-block-paragraph">libindi_dev_deb=&#8221;$(find artifacts -maxdepth 1 -type f -name &#8220;libindi-dev_*_${DEB_ARCH}_*.deb&#8221; | sort -V | tail -1)&#8221;</p>



<p class="wp-block-paragraph">*でバージョンを指定しているため、artifacts に古い .deb が残っていると、それを拾う可能性があります。</p>



<p class="wp-block-paragraph">1814〜1823行を置き換え</p>



<p class="wp-block-paragraph">変更前：</p>



<pre class="wp-block-code"><code>  local libindi1_deb
  libindi1_deb="$(find artifacts -maxdepth 1 -type f -name "libindi1_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
  &#91;&#91; -n "$libindi1_deb" ]] || fail "libindi1 package not found"
  
  local libindi_dev_deb
  libindi_dev_deb="$(find artifacts -maxdepth 1 -type f -name "libindi-dev_*_${DEB_ARCH}_*.deb" | sort -V | tail -1)"
  &#91;&#91; -n "$libindi_dev_deb" ]] || fail "libindi-dev package not found"

  run_as_root dpkg -i "$libindi1_deb"
  run_as_root dpkg -i "$libindi_dev_deb"</code></pre>



<p class="wp-block-paragraph">変更後：</p>



<pre class="wp-block-code"><code>  local libindi_package_version="${INDI_VERSION}+${BUILD_NUMBER}"

  local libindi1_deb
  libindi1_deb="$(find artifacts -maxdepth 1 -type f \
    -name "libindi1_${libindi_package_version}_${DEB_ARCH}_*.deb" \
    | head -1)"
  &#91;&#91; -n "$libindi1_deb" ]] || fail "libindi1 package not found: version=$libindi_package_version"

  local libindi_dev_deb
  libindi_dev_deb="$(find artifacts -maxdepth 1 -type f \
    -name "libindi-dev_${libindi_package_version}_${DEB_ARCH}_*.deb" \
    | head -1)"
  &#91;&#91; -n "$libindi_dev_deb" ]] || fail "libindi-dev package not found: version=$libindi_package_version"

  run_as_root dpkg -i "$libindi1_deb"
  run_as_root dpkg -i "$libindi_dev_deb"
</code></pre>



<p class="wp-block-paragraph">一度クリーンにして再実行します。</p>



<pre class="wp-block-code"><code>sudo dpkg --remove libindi-dev</code></pre>



<p class="wp-block-paragraph">古いindi debを削除します。</p>



<pre class="wp-block-code"><code>rm -f artifacts/indi-bin_*.deb
rm -f artifacts/libindi1_*.deb
rm -f artifacts/libindi-data_*.deb
rm -f artifacts/libindi-dev_*.deb</code></pre>



<p class="wp-block-paragraph">削除確認</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E '^ii  (libindi1|libindi-dev|indi-bin|libindi-data)'</code></pre>



<p class="wp-block-paragraph">PINSビルドインストール、再開</p>



<pre class="wp-block-code"><code>./build-and-install-pins-x64.sh</code></pre>



<pre class="wp-block-code"><code>&#91;INFO] PHD2 service auto-start disabled (set PHD2_AUTOSTART_SERVICE=true to enable)
&#91;INFO] Installed 16 package(s)
&#91;INFO] Applying runtime prerequisites from BUILD_PINS.md
&#91;INFO] Setting up Offline Sky Map Cache (FramingAssistantCache)
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
  0  3.28G   0  5.75M   0      0 223.6k      0 4:16:39   00:26 4:16:13 376.2k</code></pre>



<p class="wp-block-paragraph">3.28 GB の Offline Sky Map Cache をダウンロード中なので、中座します。<br>4時間くらいかかるかな。Zzz&#8230;&#8230;&#8230;</p>



<p class="wp-block-paragraph">インストールログ。パスワード入力を求められていたようだ。</p>



<pre class="wp-block-code"><code>&#91;INFO] PHD2 service auto-start disabled (set PHD2_AUTOSTART_SERVICE=true to enable)
&#91;INFO] Installed 16 package(s)
&#91;INFO] Applying runtime prerequisites from BUILD_PINS.md
&#91;INFO] Setting up Offline Sky Map Cache (FramingAssistantCache)
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
100  3.28G 100  3.28G   0      0 471.4k      0 2:01:45 2:01:45         434.7k
&#91;sudo: authenticate] パスワード: 
sudo: timed out
&#91;INFO] FramingAssistant cache installed at: /home/USERNAME/.local/share/NINA/FramingAssistantCache
&#91;INFO] Setting up ASTAP
&#91;sudo: authenticate] パスワード: 
sudo: timed out
&#91;sudo: authenticate] パスワード: 
sudo: timed out
&#91;WARN] ASTAP not found in apt and ASTAP_CLI_SOURCE is not set
&#91;WARN] Set ASTAP_CLI_SOURCE to a local astap_cli binary to install manually
&#91;WARN] Failed to set up ASTAP
&#91;WARN] Runtime setup completed with 1 warning(s)
&#91;INFO] Build and install completed

Release: v08092026-1788872749
Artifacts:
  - /home/USERNAME/pins-build-src/artifacts/indi-bin_2.1.9+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi1_2.1.9+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi-data_2.1.9+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi-dev_2.1.9+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/phd2_2.6.14-1788872779_amd64.deb
  - /home/USERNAME/pins-build-src/artifacts/pins_3.3.0.1057-nightly+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/pins-wandereretasdk_3.3.0.1057-nightly+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-joko_4.0.0.17+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-livestack_1.0.1.2+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-ninaapi_2.2.15.2+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-orbuculum_2.0.0.2+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-phd2tools_1.0.5.3+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-pins_1.0.3.0+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-polaralignment_2.2.3.4+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-tenmicron_3.0.0.13+1788872749_amd64_08092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-touch-n-stars_1.4.0.1+1788872749_amd64_08092026.deb</code></pre>



<p class="wp-block-paragraph">indi関連を確認します。</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E '^ii  (libindi1|libindi-dev|indi-bin|libindi-data)'
ii  indi-bin      2.1.9+1788872749  amd64    INDI core library, server, and drivers built from upstream v2.1.9
ii  libindi-data  2.1.9+1788872749  amd64    INDI shared data files built from upstream v2.1.9
ii  libindi-dev   2.1.9+1788872749  amd64    INDI development headers and build metadata built from upstream v2.1.9
ii  libindi1      2.1.9+1788872749  amd64    INDI runtime shared libraries built from upstream v2.1.9</code></pre>



<pre class="wp-block-code"><code>pkg-config --modversion libindi
2.1.9</code></pre>



<p class="wp-block-paragraph">INDI liblary 関連はインストールできました。</p>



<h3 class="wp-block-heading">ASTAP 落ち穂ひろい</h3>



<p class="wp-block-paragraph">次は、寝ていた間にパスワードを入力できずに、時間切れになってしまった、ASTAPをインストールし直します。</p>



<pre class="wp-block-code"><code>&#91;WARN] ASTAP not found in apt and ASTAP_CLI_SOURCE is not set
&#91;WARN] Set ASTAP_CLI_SOURCE to a local astap_cli binary to install manually
&#91;WARN] Failed to set up ASTAP
&#91;WARN] Runtime setup completed with 1 warning(s)
&#91;INFO] Build and install completed</code></pre>



<p class="wp-block-paragraph">ASTAP は、天体画像のプレートソルビング（Plate Solving）を行うソフトウェアです。<br>ASTAP は、N.I.N.Aでのプレートソルビングを行います。天体の導入と、修正を行います。</p>



<pre class="wp-block-code"><code>sudo -v</code></pre>



<p class="wp-block-paragraph">vオプション：-v(validate) 保存された認証情報（タイムスタンプ）を更新します。<br>パスワードを入力しておきます。sudoがパスワード入力を一定時間、持っているらしいです。</p>



<p class="wp-block-paragraph">ビルドインストールスクリプトを再開</p>



<pre class="wp-block-code"><code>./build-and-install-pins-x64.sh</code></pre>



<p class="wp-block-paragraph">1時間経つと無効になるらしく、パスワード入力を行いました。</p>



<p class="wp-block-paragraph">ダウンロードにかかる時間を見計らって、ダウンロード状況を見ました。なんともアナログな対応</p>



<pre class="wp-block-code"><code>&#91;INFO] PHD2 service auto-start disabled (set PHD2_AUTOSTART_SERVICE=true to enable)
&#91;INFO] Installed 16 package(s)
&#91;INFO] Applying runtime prerequisites from BUILD_PINS.md
&#91;INFO] Setting up Offline Sky Map Cache (FramingAssistantCache)
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
100  3.28G 100  3.28G   0      0 652.5k      0 1:27:58 1:27:58         602.5k
&#91;sudo: authenticate] パスワード:          
&#91;INFO] FramingAssistant cache installed at: /home/USERNAME/.local/share/NINA/FramingAssistantCache
&#91;INFO] Setting up ASTAP
ヒット:1 https://deb.nodesource.com/node_22.x nodistro InRelease
ヒット:2 http://jp.archive.ubuntu.com/ubuntu resolute InRelease                                                                                                             
ヒット:3 http://security.ubuntu.com/ubuntu resolute-security InRelease                                                                                                      
取得:4 http://jp.archive.ubuntu.com/ubuntu resolute-updates InRelease &#91;137 kB]
取得:5 https://packages.microsoft.com/ubuntu/26.04/prod resolute InRelease &#91;3,964 B]
取得:6 https://packages.microsoft.com/ubuntu/26.04/prod resolute/main amd64 Packages &#91;54.4 kB]
取得:7 https://packages.microsoft.com/ubuntu/26.04/prod resolute/main arm64 Packages &#91;47.3 kB]
ヒット:8 http://jp.archive.ubuntu.com/ubuntu resolute-backports InRelease
取得:9 http://jp.archive.ubuntu.com/ubuntu resolute-updates/main Sources &#91;298 kB]
取得:10 http://jp.archive.ubuntu.com/ubuntu resolute-updates/main amd64 Packages &#91;601 kB]
取得:11 http://jp.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 Packages &#91;268 kB]
1,410 kB を 3秒 で取得しました (464 kB/s)                   
パッケージリストを読み込んでいます... 完了
パッケージリストを読み込んでいます... 完了
依存関係ツリーを作成しています... 完了        
状態情報を読み取っています... 完了        
Solving dependencies... 完了
以下の追加パッケージがインストールされます:
  libqt5pas1 libqt5printsupport5t64 libqt5x11extras5 libraw-bin
以下のパッケージが新たにインストールされます:
  astap libqt5pas1 libqt5printsupport5t64 libqt5x11extras5 libraw-bin
アップグレード: 0 個、新規インストール: 5 個、削除: 0 個、保留: 53 個。
4,390 kB のアーカイブを取得する必要があります。
この操作後に追加で 14.4 MB のディスク容量が消費されます。
取得:1 http://jp.archive.ubuntu.com/ubuntu resolute/universe amd64 libqt5printsupport5t64 amd64 5.15.18+dfsg-1ubuntu1 &#91;209 kB]
取得:2 http://jp.archive.ubuntu.com/ubuntu resolute/universe amd64 libqt5x11extras5 amd64 5.15.18-1 &#91;11.0 kB]
取得:3 http://jp.archive.ubuntu.com/ubuntu resolute/universe amd64 libqt5pas1 amd64 4.4+dfsg-1 &#91;521 kB]
取得:4 http://jp.archive.ubuntu.com/ubuntu resolute-updates/universe amd64 libraw-bin amd64 0.21.5b-1ubuntu1.1 &#91;50.2 kB]
取得:5 http://jp.archive.ubuntu.com/ubuntu resolute/universe amd64 astap amd64 2024.11.13-1 &#91;3,599 kB]
4,390 kB を 3秒 で取得しました (1,415 kB/s)
以前に未選択のパッケージ libqt5printsupport5t64:amd64 を選択しています。
(データベースを読み込んでいます ... 現在 229706 個のファイルとディレクトリがインストールされています。)
.../libqt5printsupport5t64_5.15.18+dfsg-1ubuntu1_amd64.deb を展開する準備をしています ...
libqt5printsupport5t64:amd64 (5.15.18+dfsg-1ubuntu1) を展開しています...
以前に未選択のパッケージ libqt5x11extras5:amd64 を選択しています。
.../libqt5x11extras5_5.15.18-1_amd64.deb を展開する準備をしています ...
libqt5x11extras5:amd64 (5.15.18-1) を展開しています...
以前に未選択のパッケージ libqt5pas1:amd64 を選択しています。
.../libqt5pas1_4.4+dfsg-1_amd64.deb を展開する準備をしています ...
libqt5pas1:amd64 (4.4+dfsg-1) を展開しています...
以前に未選択のパッケージ libraw-bin を選択しています。
.../libraw-bin_0.21.5b-1ubuntu1.1_amd64.deb を展開する準備をしています ...
libraw-bin (0.21.5b-1ubuntu1.1) を展開しています...
以前に未選択のパッケージ astap を選択しています。
.../astap_2024.11.13-1_amd64.deb を展開する準備をしています ...
astap (2024.11.13-1) を展開しています...
libraw-bin (0.21.5b-1ubuntu1.1) を設定しています ...
libqt5x11extras5:amd64 (5.15.18-1) を設定しています ...
libqt5printsupport5t64:amd64 (5.15.18+dfsg-1ubuntu1) を設定しています ...
libqt5pas1:amd64 (4.4+dfsg-1) を設定しています ...
astap (2024.11.13-1) を設定しています ...
libc-bin (2.43-2ubuntu2.3) のトリガを処理しています ...
&#91;INFO] ASTAP available at: /usr/bin/astap
&#91;WARN] ASTAP star database files are still required and must be installed separately
&#91;INFO] Runtime prerequisites setup completed
&#91;INFO] Build and install completed

Release: v09092026-1788910328
Artifacts:
  - /home/USERNAME/pins-build-src/artifacts/indi-bin_2.1.9+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi1_2.1.9+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi-data_2.1.9+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/libindi-dev_2.1.9+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/phd2_2.6.14-1788910358_amd64.deb
  - /home/USERNAME/pins-build-src/artifacts/pins_3.3.0.1057-nightly+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/pins-wandereretasdk_3.3.0.1057-nightly+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-joko_4.0.0.17+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-livestack_1.0.1.2+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-ninaapi_2.2.15.2+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-orbuculum_2.0.0.2+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-phd2tools_1.0.5.3+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-pins_1.0.3.0+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-polaralignment_2.2.3.4+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-tenmicron_3.0.0.13+1788910328_amd64_09092026.deb
  - /home/USERNAME/pins-build-src/artifacts/plugins/pins-plugin-touch-n-stars_1.4.0.1+1788910328_amd64_09092026.deb</code></pre>



<p class="wp-block-paragraph">インストール完了！！　ようやく。。。</p>



<h2 class="wp-block-heading">使い方は？</h2>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">PINSを入れたPCのブラウザから、<br>http://127.0.0.1:5000<br><br>若しくは、他のPCから<br>http://NINA PC アドレス:5000</p>



<p class="wp-block-paragraph">PINS設定画面になります。</p>
</div>



<p class="wp-block-paragraph">PCのブラウザから、</p>



<pre class="wp-block-code"><code>http:&#47;&#47;127.0.0.1:5000</code></pre>



<pre class="wp-block-code"><code>http://NINA PC アドレス:5000</code></pre>



<p class="wp-block-paragraph">これで各種設定が行えるようです。</p>



<p class="wp-block-paragraph">NINA/PINS にどう接続して使うかを確認します。ポートを見ます。<br>この作業を初めたら、「N.I.N.Aをコマンドで単独に起動できる」と思い込んでしまった。</p>



<pre class="wp-block-code"><code>systemctl list-units --type=service | grep -Ei 'pins|nina|touch|stars'
  pins.service   loaded active running NINA Service

ps aux | grep -Ei 'pins|nina|touch' | grep -v grep
USERNAME    434153  2.3  1.1 69040056 349192 ?     Ssl  08:55   2:16 /home/USERNAME/pins/NINA</code></pre>



<p class="wp-block-paragraph">ポート番号が、サイトの一番下にある。。。<br><a rel="noopener" target="_blank" href="https://touch-n-stars.eu/">https://touch-n-stars.eu/</a><br>5000辺りを使うのかな、見てみます。NINA APIなどはネット検索しました。</p>



<pre class="wp-block-code"><code>sudo ss -lntp | grep -E 'NINA|pins|dotnet|1888|5000'
LISTEN 0      512          0.0.0.0:4782      0.0.0.0:*    users:(("NINA",pid=434153,fd=382))        
LISTEN 0      500                *:5000            *:*    users:(("NINA",pid=434153,fd=452))        
LISTEN 0      500                *:1889            *:*    users:(("NINA",pid=434153,fd=499))        
LISTEN 0      500                *:1888            *:*    users:(("NINA",pid=434153,fd=421))</code></pre>



<p class="wp-block-paragraph">NINA（PID 434153）は、4つのポートで待ち受け中です。<br>ポート ：状態 　　：用途<br>4782 ：LISTEN  ：NINA内部/デバイス通信など<br>5000 ：LISTEN  ：Webインターフェース<br>1888 ：LISTEN  ：NINA API<br>1889 ：LISTEN  ：API関連の別エンドポイント等</p>



<p class="wp-block-paragraph">PCのブラウザから、</p>



<pre class="wp-block-code"><code>http:&#47;&#47;127.0.0.1:5000</code></pre>



<pre class="wp-block-code"><code>http://NINA PC アドレス:5000</code></pre>



<p class="wp-block-paragraph">Setup Assistant が表示されました。</p>



<p class="wp-block-paragraph">5000番でWebサービスが正常に動いていることを確認します。</p>



<pre class="wp-block-code"><code>curl -I http://127.0.0.1:5000
HTTP/1.1 200 OK
Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Headers: Content-Type, Authorization, X-Suppress-Toast-404, X-Requested-With, X-Bahtinov-Metadata
Access-Control-Allow-Origin: *
Vary: Accept-Encoding
Content-Encoding: identity
ETag: "ACp3sQIO3wgPA4AAAAAAAA"
Last-Modified: Tue, 08 Sep 2026 23:41:24 GMT
Cache-Control: max-age=0, must-revalidate
Accept-Ranges: bytes
Content-Type: text/html; charset=utf-8
Server: EmbedIO/3.5.2
Date: Wed, 09 Sep 2026 03:02:59 GMT
Content-Length: 0
Connection: keep-alive
Keep-Alive: timeout=15,max=100</code></pre>



<p class="wp-block-paragraph">NINAプロセスにGUIがある構成なのか、Web版として動かしている構成なのかを確認します。</p>



<pre class="wp-block-code"><code>file /home/USERNAME/pins/NINA
/home/USERNAME/pins/NINA: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID&#91;sha1]=93c65abf3ff66427178d065d36972e8969f06f4e, stripped</code></pre>



<p class="wp-block-paragraph">インストールされているパッケージを確認</p>



<pre class="wp-block-code"><code>dpkg -l | grep -E '^ii.*pins'
ii  pins                                            3.3.0.1057-nightly+1788910328              amd64        Pins build for Ubuntu x64
ii  pins-plugin-joko                                4.0.0.17+1788910328                        amd64        NINA plugin package for joko.nina.plugins
ii  pins-plugin-livestack                           1.0.1.2+1788910328                         amd64        NINA plugin package for LiveStack
ii  pins-plugin-ninaapi                             2.2.15.2+1788910328                        amd64        NINA plugin package for ninaAPI
ii  pins-plugin-orbuculum                           2.0.0.2+1788910328                         amd64        NINA plugin package for Orbuculum
ii  pins-plugin-phd2tools                           1.0.5.3+1788910328                         amd64        NINA plugin package for Phd2 Tools
ii  pins-plugin-pins                                1.0.3.0+1788910328                         amd64        NINA plugin package for pins.plugin
ii  pins-plugin-polaralignment                      2.2.3.4+1788910328                         amd64        NINA plugin package for PolarAlignment
ii  pins-plugin-tenmicron                           3.0.0.13+1788910328                        amd64        NINA plugin package for NINA.Joko.Plugin.TenMicron
ii  pins-plugin-touch-n-stars                       1.4.0.1+1788910328                         amd64        NINA plugin package for Touch-N-Stars
ii  pins-wandereretasdk                             3.3.0.1057-nightly+1788910328              amd64        WandererETA SDK shared library package

pkg -L pins 2&gt;/dev/null | head -100
/.
/etc
/etc/systemd
/etc/systemd/system
/etc/systemd/system/pins.service
/home
/home/USERNAME
/home/USERNAME/pins
/home/USERNAME/pins/.install_path
/home/USERNAME/pins/ASCOM.Alpaca.Device.dll
/home/USERNAME/pins/ASCOM.Alpaca.dll
/home/USERNAME/pins/ASCOM.Com.dll
/home/USERNAME/pins/ASCOM.Common.dll
/home/USERNAME/pins/ASCOM.Exceptions.dll
/home/USERNAME/pins/ASCOM.Tools.dll
/home/USERNAME/pins/Accord.Math.Core.dll
/home/USERNAME/pins/Accord.Math.dll
/home/USERNAME/pins/Accord.Statistics.dll
/home/USERNAME/pins/Accord.dll
/home/USERNAME/pins/Accord.dll.config
/home/USERNAME/pins/AsyncEnumerable.dll
/home/USERNAME/pins/Castle.Core.AsyncInterceptor.dll
/home/USERNAME/pins/Castle.Core.dll
/home/USERNAME/pins/CommandLine.dll
/home/USERNAME/pins/CommunityToolkit.Mvvm.dll
/home/USERNAME/pins/CsvHelper.dll
/home/USERNAME/pins/Database
/home/USERNAME/pins/Database/Initial
/home/USERNAME/pins/Database/Initial/initial_data.sql
/home/USERNAME/pins/Database/Initial/initial_schema.sql
/home/USERNAME/pins/Database/Migration
/home/USERNAME/pins/Database/Migration/1.sql
/home/USERNAME/pins/Database/Migration/10.sql
/home/USERNAME/pins/Database/Migration/11.sql
/home/USERNAME/pins/Database/Migration/12.sql
/home/USERNAME/pins/Database/Migration/13.sql
/home/USERNAME/pins/Database/Migration/14.sql
/home/USERNAME/pins/Database/Migration/15.sql
/home/USERNAME/pins/Database/Migration/16.sql
/home/USERNAME/pins/Database/Migration/2.sql
/home/USERNAME/pins/Database/Migration/3.sql
/home/USERNAME/pins/Database/Migration/5.sql
/home/USERNAME/pins/Database/Migration/6.sql
/home/USERNAME/pins/Database/Migration/7.sql
/home/USERNAME/pins/Database/Migration/8.sql
/home/USERNAME/pins/Database/Migration/9.sql
/home/USERNAME/pins/EntityFramework.SqlServer.dll
/home/USERNAME/pins/EntityFramework.dll
/home/USERNAME/pins/ExtendedNumerics.BigDecimal.dll
/home/USERNAME/pins/External
/home/USERNAME/pins/External/.git
/home/USERNAME/pins/External/.git/HEAD
/home/USERNAME/pins/External/.git/config
/home/USERNAME/pins/External/.git/description
/home/USERNAME/pins/External/.git/hooks
/home/USERNAME/pins/External/.git/hooks/applypatch-msg.sample
/home/USERNAME/pins/External/.git/hooks/commit-msg.sample
/home/USERNAME/pins/External/.git/hooks/fsmonitor-watchman.sample
/home/USERNAME/pins/External/.git/hooks/post-checkout
/home/USERNAME/pins/External/.git/hooks/post-commit
/home/USERNAME/pins/External/.git/hooks/post-merge
/home/USERNAME/pins/External/.git/hooks/post-update.sample
/home/USERNAME/pins/External/.git/hooks/pre-applypatch.sample
/home/USERNAME/pins/External/.git/hooks/pre-commit.sample
/home/USERNAME/pins/External/.git/hooks/pre-merge-commit.sample
/home/USERNAME/pins/External/.git/hooks/pre-push
/home/USERNAME/pins/External/.git/hooks/pre-push.sample
/home/USERNAME/pins/External/.git/hooks/pre-rebase.sample
/home/USERNAME/pins/External/.git/hooks/pre-receive.sample
/home/USERNAME/pins/External/.git/hooks/prepare-commit-msg.sample
/home/USERNAME/pins/External/.git/hooks/push-to-checkout.sample
/home/USERNAME/pins/External/.git/hooks/sendemail-validate.sample
/home/USERNAME/pins/External/.git/hooks/update.sample
/home/USERNAME/pins/External/.git/index
/home/USERNAME/pins/External/.git/info
/home/USERNAME/pins/External/.git/info/exclude
/home/USERNAME/pins/External/.git/lfs
/home/USERNAME/pins/External/.git/lfs/incomplete
/home/USERNAME/pins/External/.git/lfs/objects
/home/USERNAME/pins/External/.git/lfs/objects/06
/home/USERNAME/pins/External/.git/lfs/objects/06/f9
/home/USERNAME/pins/External/.git/lfs/objects/06/f9/06f9da829af05e280a01c9566677883bb9af42385b7af82acc018b8ccd347765
/home/USERNAME/pins/External/.git/lfs/objects/18
/home/USERNAME/pins/External/.git/lfs/objects/18/19
/home/USERNAME/pins/External/.git/lfs/objects/18/19/18191689141077cd31f58a294838bb9650908a02cb423eff60a81cbda0b18efc
/home/USERNAME/pins/External/.git/lfs/objects/1d
/home/USERNAME/pins/External/.git/lfs/objects/1d/b4
/home/USERNAME/pins/External/.git/lfs/objects/1d/b4/1db4dac54f2a2dd4588c6f2f6ce75d41bbfeb6bf58034e317253911c628c1e6c
/home/USERNAME/pins/External/.git/lfs/objects/29
/home/USERNAME/pins/External/.git/lfs/objects/29/6b
/home/USERNAME/pins/External/.git/lfs/objects/29/6b/296b1a044cdfbc1a7f82f08c28aefd60f25761aa188916e26eab46281c02595a
/home/USERNAME/pins/External/.git/lfs/objects/2b
/home/USERNAME/pins/External/.git/lfs/objects/2b/de
/home/USERNAME/pins/External/.git/lfs/objects/2b/de/2bde7d5e84caac944356543ff5cf6755564664bf07834418ede708d1de243172
/home/USERNAME/pins/External/.git/lfs/objects/32
/home/USERNAME/pins/External/.git/lfs/objects/32/ff
/home/USERNAME/pins/External/.git/lfs/objects/32/ff/32ff8f1e702b93ee2a7537e5399f1a2a26a9e51f0752d11f914de8293ae66a0b
/home/USERNAME/pins/External/.git/lfs/objects/3c
/home/USERNAME/pins/External/.git/lfs/objects/3c/b5
/home/USERNAME/pins/External/.git/lfs/objects/3c/b5/3cb59e2d6cb7dbefb2d87c3b5b25654207ceee18b285f52d4e8edaeb2ffb6548</code></pre>



<p class="wp-block-paragraph">PINSの実行ファイルを探します。</p>



<pre class="wp-block-code"><code>find /home/USERNAME/pins -maxdepth 2 -type f -executable -printf '%p\n'
/home/USERNAME/pins/System.AppContext.dll
/home/USERNAME/pins/System.Security.Cryptography.OpenSsl.dll
/home/USERNAME/pins/System.Runtime.InteropServices.dll
/home/USERNAME/pins/System.Xml.XPath.XDocument.dll
/home/USERNAME/pins/System.Data.SQLite.dll
/home/USERNAME/pins/System.Configuration.ConfigurationManager.dll
/home/USERNAME/pins/System.Linq.Queryable.dll
/home/USERNAME/pins/Accord.Math.Core.dll
/home/USERNAME/pins/System.Formats.Cbor.dll
/home/USERNAME/pins/System.Net.Security.dll
/home/USERNAME/pins/System.Runtime.Serialization.Xml.dll
/home/USERNAME/pins/System.ValueTuple.dll
/home/USERNAME/pins/Microsoft.Extensions.Configuration.Json.dll
/home/USERNAME/pins/Microsoft.Win32.Registry.dll
/home/USERNAME/pins/System.Data.DataSetExtensions.dll
/home/USERNAME/pins/System.Memory.dll
/home/USERNAME/pins/zh-Hans/Microsoft.CodeAnalysis.CSharp.resources.dll
/home/USERNAME/pins/zh-Hans/Microsoft.CodeAnalysis.resources.dll
/home/USERNAME/pins/System.Core.dll
/home/USERNAME/pins/System.Reflection.Emit.Lightweight.dll
/home/USERNAME/pins/ASCOM.Exceptions.dll
/home/USERNAME/pins/System.Threading.Timer.dll
/home/USERNAME/pins/System.Web.dll
/home/USERNAME/pins/System.Private.Xml.dll
/home/USERNAME/pins/System.Diagnostics.Process.dll
/home/USERNAME/pins/System.Net.WebSockets.WebSocketProtocol.dll
/home/USERNAME/pins/System.Net.Requests.dll
/home/USERNAME/pins/Nito.AsyncEx.Tasks.dll
/home/USERNAME/pins/Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.dll
/home/USERNAME/pins/Microsoft.AspNetCore.Razor.dll
/home/USERNAME/pins/System.Net.Ping.dll
/home/USERNAME/pins/Nito.Cancellation.dll
/home/USERNAME/pins/de/Microsoft.CodeAnalysis.CSharp.resources.dll
/home/USERNAME/pins/de/Microsoft.CodeAnalysis.resources.dll
/home/USERNAME/pins/System.Collections.dll
/home/USERNAME/pins/Parlot.dll
/home/USERNAME/pins/System.Threading.Overlapped.dll
/home/USERNAME/pins/Microsoft.AspNetCore.SignalR.Common.dll
/home/USERNAME/pins/System.Resources.ResourceManager.dll
/home/USERNAME/pins/build-and-install-pins-x64.sh.after-phd2
/home/USERNAME/pins/System.ObjectModel.dll
/home/USERNAME/pins/Microsoft.Extensions.FileProviders.Abstractions.dll
/home/USERNAME/pins/Microsoft.Extensions.Caching.Memory.dll
/home/USERNAME/pins/Microsoft.AspNetCore.Hosting.Server.Abstractions.dll
/home/USERNAME/pins/Microsoft.AspNetCore.Razor.Runtime.dll
/home/USERNAME/pins/System.ComponentModel.Primitives.dll
/home/USERNAME/pins/Microsoft.AspNetCore.SignalR.dll
/home/USERNAME/pins/Swashbuckle.AspNetCore.Swagger.dll
/home/USERNAME/pins/ru/Microsoft.CodeAnalysis.CSharp.resources.dll
/home/USERNAME/pins/ru/Microsoft.CodeAnalysis.resources.dll
/home/USERNAME/pins/System.Diagnostics.FileVersionInfo.dll
/home/USERNAME/pins/System.Security.Cryptography.Xml.dll
/home/USERNAME/pins/Microsoft.Extensions.Diagnostics.dll
/home/USERNAME/pins/System.Runtime.Loader.dll
/home/USERNAME/pins/Microsoft.Extensions.FileSystemGlobbing.dll
/home/USERNAME/pins/AsyncEnumerable.dll
/home/USERNAME/pins/System.Net.NameResolution.dll
/home/USERNAME/pins/Microsoft.CodeAnalysis.CSharp.dll
/home/USERNAME/pins/System.Security.Cryptography.Pkcs.dll
/home/USERNAME/pins/System.Diagnostics.Tracing.dll
/home/USERNAME/pins/libSystem.IO.Ports.Native.so
/home/USERNAME/pins/Microsoft.AspNetCore.Mvc.Localization.dll
/home/USERNAME/pins/NINA</code></pre>



<p class="wp-block-paragraph">単純に、/home/USERNAME/pins/NINA　でした。</p>



<pre class="wp-block-code"><code>~/pins$ ./NINA

コアダンプします

2026-09-09T12:29:09.8032|INFO|Program.cs|&lt;Main&gt;$|78|Launched with command line arguments: /home/USERNAME/pins/NINA.dll
2026-09-09T12:29:09.9222|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libudev.so.1
2026-09-09T12:29:09.9239|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libhidapi-hidraw.so
2026-09-09T12:29:09.9241|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libusb-1.0.so.0
2026-09-09T12:29:09.9604|INFO|INDIClient.cs|KillExistingServer|1501|Killed existing indiserver processes
2026-09-09T12:29:09.9611|INFO|INDIClient.cs|CreateFifo|1424|FIFO already exists: /tmp/indiFIFO
2026-09-09T12:29:09.9619|INFO|INDIClient.cs|StartServerInFifoMode|1368|INDI server started in FIFO mode with PID 445854, port: 7624, using FIFO: /tmp/indiFIFO
2026-09-09T12:29:09.9677|INFO|DllLoader.cs|LoadDll|61|DllLoader: Loading bundled library: /home/USERNAME/pins/External/linux-x64/SOFA/libsofa_c.so
2026-09-09T12:29:10.0758|INFO|INDIClient.cs|Connect|153|Connected to INDI server
2026-09-09T12:29:10.0760|INFO|INDIClient.cs|StartServerInFifoMode|1399|Connected to INDI server on attempt 1
2026-09-09T12:29:10.5237|INFO|DllLoader.cs|LoadDll|61|DllLoader: Loading bundled library: /home/USERNAME/pins/External/linux-x64/NOVAS/libnovas_c.so
2026-09-09T12:29:10.5493|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libatikcameras.so
2026-09-09T12:29:10.5558|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libASICamera2.so
2026-09-09T12:29:10.5596|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libNitecrawlerSDK.so
2026-09-09T12:29:10.5599|ERROR|DllLoader.cs|LoadDllFromAbsolutePath|137|DllLoader failed to load library libNitecrawlerSDK.so: Unknown error
2026-09-09T12:29:10.5610|ERROR|RotatorChooserVM.cs|GetEquipment|56
System.DllNotFoundException: Unable to load shared library 'libNitecrawlerSDK.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
/home/USERNAME/pins/libNitecrawlerSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibNitecrawlerSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/libNitecrawlerSDK.so.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibNitecrawlerSDK.so.so: cannot open shared object file: No such file or directory

   at Nitecrawler.NitecrawlerSDK.NCRotatorScan(Int32&amp; number, Int32&#91;] ids)
   at Nitecrawler.NitecrawlerSDK.ScanRotators(Int32&amp; number, Int32&#91;] ids) in /home/USRNAME/pins-build-src/NINA.Equipment/SDK/RotatorSDKs/NitecrawlerSDK/NitecrawlerSDK.cs:line 294
   at NINA.WPF.Base.ViewModel.Equipment.Rotator.RotatorChooserVM.GetEquipment() in /home/USRNAME/pins-build-src/NINA.WPF.Base/ViewModel/Equipment/Rotator/RotatorChooserVM.cs:line 47
2026-09-09T12:29:10.5643|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libWandererRotatorSDK.so
2026-09-09T12:29:10.5644|ERROR|DllLoader.cs|LoadDllFromAbsolutePath|137|DllLoader failed to load library libWandererRotatorSDK.so: libWandererRotatorSDK.so: cannot open shared object file: No such file or directory
2026-09-09T12:29:10.5645|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libWandererCoverSDK.so
2026-09-09T12:29:10.5646|ERROR|DllLoader.cs|LoadDllFromAbsolutePath|137|DllLoader failed to load library libWandererCoverSDK.so: libWandererCoverSDK.so: cannot open shared object file: No such file or directory
2026-09-09T12:29:10.5649|ERROR|RotatorChooserVM.cs|GetEquipment|78|Failed to scan for WandererRotators: System.DllNotFoundException: Unable to load shared library 'libWandererRotatorSDK.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
/home/USRNAME/pins/libWandererRotatorSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibWandererRotatorSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/libWandererRotatorSDK.so.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibWandererRotatorSDK.so.so: cannot open shared object file: No such file or directory

   at Wanderer.WandererRotatorSDK.WRRotatorScan(Int32&amp; number, Int32&#91;] ids)
   at Wanderer.WandererRotatorSDK.RotatorScan(Int32&amp; number, Int32&#91;] ids) in /home/USRNAME/pins-build-src/NINA.Equipment/SDK/RotatorSDKs/WandererRotatorSDK/WandererRotatorSDK.cs:line 139
   at NINA.WPF.Base.ViewModel.Equipment.Rotator.RotatorChooserVM.GetEquipment() in /home/USRNAME/pins-build-src/NINA.WPF.Base/ViewModel/Equipment/Rotator/RotatorChooserVM.cs:line 64
2026-09-09T12:29:10.5656|ERROR|FlatDeviceChooserVM.cs|GetEquipment|60|Failed to scan for WandererCovers: System.DllNotFoundException: Unable to load shared library 'libWandererCoverSDK.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
/home/USRNAME/pins/libWandererCoverSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibWandererCoverSDK.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/libWandererCoverSDK.so.so: cannot open shared object file: No such file or directory
/home/USRNAME/pins/liblibWandererCoverSDK.so.so: cannot open shared object file: No such file or directory

   at Wanderer.WandererCoverSDK.WCCoverScan(Int32&amp; number, Int32&#91;] ids)
   at Wanderer.WandererCoverSDK.CoverScan(Int32&amp; number, Int32&#91;] ids) in /home/USRNAME/pins-build-src/NINA.Equipment/SDK/FlatDeviceSDKs/WandererCoverSDK/WandererCoverSDK.cs:line 129
   at NINA.WPF.Base.ViewModel.Equipment.FlatDevice.FlatDeviceChooserVM.GetEquipment() in /home/USRNAME/pins-build-src/NINA.WPF.Base/ViewModel/Equipment/FlatDevice/FlatDeviceChooserVM.cs:line 46
2026-09-09T12:29:10.5737|INFO|CameraChooserVM.cs|GetEquipment|61|Found 0 ASI Cameras
2026-09-09T12:29:10.5741|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libaltaircam.so
2026-09-09T12:29:10.5841|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libqhyccd.so
2026-09-09T12:29:10.5949|INFO|CameraChooserVM.cs|GetEquipment|76|Found 0 Altair Cameras
2026-09-09T12:29:10.5950|INFO|CameraChooserVM.cs|GetEquipment|91|Found 0 Atik Cameras
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
2026-09-09T12:29:10.5999|INFO|Program.cs|&lt;Main&gt;$|131|Server fully initialized and running.
QHYCCD|QHYCCD.CPP|libusb_version 1.0.29.11953
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path  26.2.1.12 svn: 1  ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/USRNAME/pins  fileName = qhyccd.ini
2026-09-09T12:29:10.6190|INFO|UsbDeviceWatcher.cs|Stop|42|USB Device Watcher stopped
Unhandled exception. System.IO.IOException: Failed to bind to address http://0.0.0.0:4782: address already in use.
 ---&gt; Microsoft.AspNetCore.Connections.AddressInUseException: Address already in use
 ---&gt; System.Net.Sockets.SocketException (98): Address already in use
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportOptions.CreateDefaultBoundListenSocket(EndPoint endpoint)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketConnectionListener.Bind()
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.SocketTransportFactory.BindAsync(EndPoint endpoint, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Infrastructure.TransportManager.BindAsync(EndPoint endPoint, ConnectionDelegate connectionDelegate, EndpointConfig endpointConfig, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.&lt;&gt;c__DisplayClass28_0`1.&lt;&lt;StartAsync&gt;g__OnBind|0&gt;d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindEndpointAsync(ListenOptions endpoint, AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync&#91;TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
   at Microsoft.Extensions.Hosting.Internal.Host.&lt;StartAsync&gt;b__14_1(IHostedService service, CancellationToken token)
   at Microsoft.Extensions.Hosting.Internal.Host.ForeachService&#91;T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
   at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)
   at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.Run(IHost host)
   at Program.&lt;Main&gt;$(String&#91;] args) in /home/USRNAME/pins-build-src/NINA/Program.cs:line 154
中止                     (コアダンプ) ./NINA</code></pre>



<pre class="wp-block-code"><code>System.IO.IOException: Failed to bind to address http://0.0.0.0:4782: address already in use.
...
SocketException (98): Address already in use</code></pre>



<p class="wp-block-paragraph">既に何かのプロセスが、ポート4782を使ってるようです。調べます。</p>



<pre class="wp-block-code"><code>sudo ss -ltnp 'sport = :4782'
&#91;sudo: authenticate] パスワード:          
State   Recv-Q   Send-Q   Local Address:Port   Peer Address:Port       Process
LISTEN    　 0      512         0.0.0.0:4782          0.0.0.0:*        users:

(("NINA",pid=434153,fd=382))</code></pre>



<p class="wp-block-paragraph">NINAがすでに使っている模様です。ブラウザに表示させているプロセスかな？</p>



<pre class="wp-block-code"><code>ps aux | grep -i '&#91;N]INA'
USERNAME   434153  2.2  1.3 69173980 415112 ?    Ssl  08:55   5:00 /home/USRNAME/pins/NINA</code></pre>



<p class="wp-block-paragraph">止めます。</p>



<pre class="wp-block-code"><code>kill 434153</code></pre>



<pre class="wp-block-code"><code>~/pins$ ./NINA</code></pre>



<p class="wp-block-paragraph">コアダンプするので、調べます。</p>



<pre class="wp-block-code"><code>sudo ss -ltnp 'sport = :4782'
State　　 Recv-   Send-Q    Local Address:Port   Peer Address:Port     Process
LISTEN       0       512          0.0.0.0:4782            0.0.0.0:*                    users:(("NINA",pid=446716,fd=375))</code></pre>



<p class="wp-block-paragraph">PID 446716 の NINA が4782を使っている。</p>



<p class="wp-block-paragraph">PID 446716は何かな？</p>



<pre class="wp-block-code"><code>ps -fp 446716
UID          PID    PPID  C STIME TTY          TIME CMD
USERNAME    446716       1  3 12:42 ?        00:00:15 /home/USERNAME/pins/NINA

readlink -f /proc/446716/exe
/home/USERNAME/pins/NINA

pgrep -a -f 'NINA|NINA.dll'
446716 /home/USERNAME/pins/NINA</code></pre>



<p class="wp-block-paragraph">NINAが起動途中ですでに4782を開いているが、別の処理でもう一度4782を開こうとしているらしい。</p>



<p class="wp-block-paragraph">NINAを終了し、4782ポートを見てます</p>



<pre class="wp-block-code"><code>kill 446716
sudo ss -ltnp 'sport = :4782'
State   Recv-Q  Send-Q    Local Address:Port   Peer Address:Port    Process
LISTEN  　   0     512          0.0.0.0:4782           0.0.0.0:*    users:(("NINA",pid=447228,fd=377))</code></pre>



<p class="wp-block-paragraph">NINAは別のプロセスに監視されていて、終了すると自動再起動されています。</p>



<p class="wp-block-paragraph">systemd登録されているかもしれません。見てみます。</p>



<pre class="wp-block-code"><code>systemctl list-units --type=service --all | grep -i nina
  pins.service        loaded    active   running NINA Service</code></pre>



<p class="wp-block-paragraph">pins.service が NINAをsystemdサービスとして常駐、自動再起動させています。</p>



<pre class="wp-block-code"><code>sudo systemctl status pins.service
&#91;sudo: authenticate] パスワード:          
● pins.service - NINA Service
     Loaded: loaded (/etc/systemd/system/pins.service; enabled; preset: enabled)
     Active: active (running) since Wed 2026-09-09 12:53:12 JST; 18min ago
 Invocation: 5f43ce878bb14399981177d51f6f1149
   Main PID: 447228 (NINA)
      Tasks: 35 (limit: 36763)
     Memory: 189.5M (peak: 191M)
        CPU: 31.537s
     CGroup: /system.slice/pins.service
             ├─447228 /home/USRNAME/pins/NINA
             └─447243 indiserver -v -p 7624 -m 1000 -f /tmp/indiFIFO

 9月 09 12:53:19 a7g NINA&#91;447228]: 2026-09-09T12:53:19.4883|INFO|SafetyMonitorChooserVM.cs|GetEquipment|74|Found 0 INDI Safety Monitors
 9月 09 12:53:19 a7g NINA&#91;447228]: 2026-09-09T12:53:19.4901|INFO|FilterWheelChooserVM.cs|GetEquipment|279|Found 1 Alpaca Filter Wheels
 9月 09 12:53:19 a7g NINA&#91;447228]: 2026-09-09T12:53:19.9883|INFO|DomeChooserVM.cs|GetEquipment|70|Found 0 INDI Domes
 9月 09 12:53:19 a7g NINA&#91;447228]: 2026-09-09T12:53:19.9894|INFO|FocuserChooserVM.cs|GetEquipment|137|Found 1 Alpaca Focusers
 9月 09 12:53:20 a7g NINA&#91;447228]: 2026-09-09T12:53:20.4889|INFO|SwitchChooserVM.cs|GetEquipment|75|Found 0 INDI Switch Hubs
 9月 09 12:53:20 a7g NINA&#91;447228]: 2026-09-09T12:53:20.4902|INFO|WeatherDataChooserVM.cs|GetEquipment|70|Found 1 Alpaca Observing Conditions
 9月 09 12:53:20 a7g NINA&#91;447228]: 2026-09-09T12:53:20.9917|INFO|CameraChooserVM.cs|GetEquipment|259|Found 1 Alpaca Cameras
 9月 09 12:53:20 a7g NINA&#91;447228]: 2026-09-09T12:53:20.9942|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libgphoto2.so
 9月 09 12:53:20 a7g NINA&#91;447228]: 2026-09-09T12:53:20.9947|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libgphoto2_port.so
 9月 09 12:53:21 a7g NINA&#91;447228]: 2026-09-09T12:53:21.0380|INFO|CameraChooserVM.cs|GetEquipment|267|Found 0 libgphoto2 Cameras</code></pre>



<p class="wp-block-paragraph">pins.serviceの内容を見てみます。</p>



<pre class="wp-block-code"><code>sudo systemctl cat pins.service
&#91;sudo: authenticate] パスワード:          
# /etc/systemd/system/pins.service
&#91;Unit]
Description=NINA Service
After=network.target

&#91;Service]
Type=simple
Environment="LD_LIBRARY_PATH=/opt/opencvsharp/lib:/usr/lib/x86_64-linux-gnu"
ExecStart=/home/USERNAME/pins/NINA
WorkingDirectory=/home/USERNAME/pins/
User=USERNAME
Group=USERNAME
Restart=always
RestartSec=5

&#91;Install]
WantedBy=multi-user.target</code></pre>



<p class="wp-block-paragraph">Restart=always<br>この行があるので、killしてもNINA Serviceが再起動されます。</p>



<p class="wp-block-paragraph">いったんsystemd版を止めて、ポート4782が空いたことを確認し、~/pins$ ./NINA を用い、<br>NINAを表示させます。</p>



<pre class="wp-block-code"><code>sudo systemctl stop pins.service
sudo ss -ltnp 'sport = :4782'
~/pins$ ./NINA</code></pre>



<pre class="wp-block-code"><code>2026-09-09T14:11:09.7789|ERROR|FocuserChooserVM.cs|GetEquipment|117
System.DllNotFoundException: Unable to load shared library 'libNitecrawlerSDK.so' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: 
/home/USERNAME/pins/libNitecrawlerSDK.so: cannot open shared object file: No such file or directory
/home/USERNAME/pins/liblibNitecrawlerSDK.so: cannot open shared object file: No such file or directory
/home/USERNAME/pins/libNitecrawlerSDK.so.so: cannot open shared object file: No such file or directory
/home/USERNAME/pins/liblibNitecrawlerSDK.so.so: cannot open shared object file: No such file or directory

   at Nitecrawler.NitecrawlerSDK.NCFocuserScan(Int32&amp; number, Int32&#91;] ids)
   at Nitecrawler.NitecrawlerSDK.ScanFocusers(Int32&amp; number, Int32&#91;] ids) in /home/USERNAME/pins-build-src/NINA.Equipment/SDK/RotatorSDKs/NitecrawlerSDK/NitecrawlerSDK.cs:line 268
   at NINA.WPF.Base.ViewModel.Equipment.Focuser.FocuserChooserVM.GetEquipment() in /home/USERNAME/pins-build-src/NINA.WPF.Base/ViewModel/Equipment/Focuser/FocuserChooserVM.cs:line 108
2026-09-09T14:11:09.7796|INFO|CameraChooserVM.cs|GetEquipment|235|Found 1 Hocus Focus Cameras
2026-09-09T14:11:09.7799|INFO|CameraChooserVM.cs|GetEquipment|235|Found 1 Hocus Focus Cameras
2026-09-09T14:11:09.7831|INFO|SwitchChooserVM.cs|GetEquipment|48|Found 0 PINS.PowerBox Switch Hubs
2026-09-09T14:11:09.7857|INFO|WeatherDataChooserVM.cs|GetEquipment|46|Found 0 PINS.MeteoStation Weather Data
2026-09-09T14:11:09.7940|INFO|SwitchChooserVM.cs|GetEquipment|48|Found 0 PINS.PowerBox Switch Hubs
2026-09-09T14:11:09.7962|INFO|WeatherDataChooserVM.cs|GetEquipment|46|Found 0 PINS.MeteoStation Weather Data
2026-09-09T14:11:10.2695|INFO|TelescopeChooserVM.cs|GetEquipment|58|Found 0 INDI Telescopes
2026-09-09T14:11:10.7711|INFO|FlatDeviceChooserVM.cs|GetEquipment|82|Found 0 INDI FlatDevices
2026-09-09T14:11:11.2711|INFO|RotatorChooserVM.cs|GetEquipment|100|Found 0 INDI Rotators
2026-09-09T14:11:11.7710|INFO|FilterWheelChooserVM.cs|GetEquipment|267|Found 0 INDI Filter Wheels
2026-09-09T14:11:11.7735|INFO|SafetyMonitorChooserVM.cs|GetEquipment|62|Found 1 Alpaca Safety Monitors
2026-09-09T14:11:11.7735|INFO|DomeChooserVM.cs|GetEquipment|58|Found 1 Alpaca Domes
2026-09-09T14:11:11.7960|INFO|SwitchChooserVM.cs|GetEquipment|62|Found 1 Alpaca Switch Hubs
2026-09-09T14:11:12.2713|INFO|CameraChooserVM.cs|GetEquipment|247|Found 0 INDI Cameras
2026-09-09T14:11:12.2715|INFO|TelescopeChooserVM.cs|GetEquipment|81|Found 1 Alpaca Telescopes
2026-09-09T14:11:12.7710|INFO|FocuserChooserVM.cs|GetEquipment|125|Found 0 INDI Focusers
2026-09-09T14:11:12.7731|INFO|FlatDeviceChooserVM.cs|GetEquipment|94|Found 1 Alpaca Cover Calibrators
2026-09-09T14:11:13.2715|INFO|WeatherDataChooserVM.cs|GetEquipment|58|Found 0 INDI Weather Data
2026-09-09T14:11:13.2741|INFO|RotatorChooserVM.cs|GetEquipment|112|Found 1 Alpaca Rotators
2026-09-09T14:11:13.7719|INFO|SafetyMonitorChooserVM.cs|GetEquipment|74|Found 0 INDI Safety Monitors
2026-09-09T14:11:13.7728|INFO|FilterWheelChooserVM.cs|GetEquipment|279|Found 1 Alpaca Filter Wheels
2026-09-09T14:11:14.2723|INFO|DomeChooserVM.cs|GetEquipment|70|Found 0 INDI Domes
2026-09-09T14:11:14.2740|INFO|CameraChooserVM.cs|GetEquipment|259|Found 1 Alpaca Cameras
2026-09-09T14:11:14.2766|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libgphoto2.so
2026-09-09T14:11:14.2771|INFO|DllLoader.cs|LoadDll|76|DllLoader: Trying system library via LD_LIBRARY_PATH: libgphoto2_port.so
2026-09-09T14:11:14.3224|INFO|CameraChooserVM.cs|GetEquipment|267|Found 0 libgphoto2 Cameras
2026-09-09T14:11:14.3258|INFO|PluginFetcher.cs|RequestAll|57|Found 96 valid plugins at https://nighttime-imaging.eu/wp-json/nina/v1/plugins/manifests
2026-09-09T14:11:14.7716|INFO|SwitchChooserVM.cs|GetEquipment|75|Found 0 INDI Switch Hubs
2026-09-09T14:11:14.7732|INFO|FocuserChooserVM.cs|GetEquipment|137|Found 1 Alpaca Focusers
2026-09-09T14:11:15.2749|INFO|WeatherDataChooserVM.cs|GetEquipment|70|Found 1 Alpaca Observing Conditions</code></pre>



<p class="wp-block-paragraph">Found 1 Alpaca Observing Conditions<br>ここで、処理が止まっている。機器スキャンで止まっている。</p>



<p class="wp-block-paragraph">状態を見ます。</p>



<pre class="wp-block-code"><code>ps -o pid,ppid,stat,%cpu,%mem,etime,cmd -C NINA
    PID    PPID STAT %CPU %MEM     ELAPSED CMD
 450039    9160 Sl+   3.1  1.2       13:17 ./NINA

sudo ss -tnp | grep 450039
&#91;sudo: authenticate] パスワード:          
ESTAB 0      0                        &#91;::ffff:127.0.0.1]:40670               &#91;::ffff:127.0.0.1]:7624  users:(("NINA",pid=450039,fd=311))</code></pre>



<p class="wp-block-paragraph">sudo ss -uap は、現在PC上で開かれているUDPソケットと、それを使っているプロセスを表示するコマンドです。</p>



<pre class="wp-block-code"><code>sudo ss -uap
State             Recv-Q            Send-Q                                          Local Address:Port                                Peer Address:Port             Process                                              
UNCONN            0                 0                                                192.168.0.13:3702                                     0.0.0.0:*                 users:(("python3",pid=162082,fd=10))                
UNCONN            0                 0                                             239.255.255.250:3702                                     0.0.0.0:*                 users:(("python3",pid=162082,fd=8))                 
UNCONN            0                 0                                                     0.0.0.0:37426                                    0.0.0.0:*                 users:(("python3",pid=162082,fd=9))                 
UNCONN            0                 0                                                192.168.0.13:mdns                                     0.0.0.0:*                 users:(("NINA",pid=450039,fd=491))                  
UNCONN            0                 0                                                     0.0.0.0:mdns                                     0.0.0.0:*                 users:(("NINA",pid=450039,fd=489))                  
UNCONN            0                 0                                                192.168.0.13:mdns                                     0.0.0.0:*                 users:(("NINA",pid=450039,fd=467))                  
UNCONN            0                 0                                                     0.0.0.0:mdns                                     0.0.0.0:*                 users:(("NINA",pid=450039,fd=465))                  
UNCONN            0                 0                                                     0.0.0.0:mdns                                     0.0.0.0:*                 users:(("avahi-daemon",pid=1613,fd=12))             
UNCONN            0                 0                                                  127.0.0.54:domain                                   0.0.0.0:*                 users:(("systemd-resolve",pid=564,fd=18))           
UNCONN            0                 0                                               127.0.0.53%lo:domain                                   0.0.0.0:*                 users:(("systemd-resolve",pid=564,fd=16))           
ESTAB             0                 0                                           192.168.0.13%eno1:bootpc                               192.168.0.2:bootps            users:(("NetworkManager",pid=2067,fd=26))           
UNCONN            0                 0                                                   127.0.0.1:323                                      0.0.0.0:*                 users:(("chronyd",pid=1813,fd=4))                   
UNCONN            0                 0                                                           *:35462                                          *:*                 users:(("python3",pid=162082,fd=12))                
UNCONN            0                 0                            &#91;fe80::b225:aaff:fe9f:a2b9]%eno1:3702                                        &#91;::]:*                 users:(("python3",pid=162082,fd=13))                
UNCONN            0                 0                                              &#91;ff02::c]%eno1:3702                                        &#91;::]:*                 users:(("python3",pid=162082,fd=11))                
UNCONN            0                 0                                                        &#91;::]:mdns                                        &#91;::]:*                 users:(("avahi-daemon",pid=1613,fd=13))             
UNCONN            0                 0                                                        &#91;::]:mdns                                        &#91;::]:*                 users:(("NINA",pid=450039,fd=466))                  
UNCONN            0                 0                            &#91;fe80::b225:aaff:fe9f:a2b9]%eno1:mdns                                        &#91;::]:*                 users:(("NINA",pid=450039,fd=468))                  
UNCONN            0                 0                                                        &#91;::]:mdns                                        &#91;::]:*                 users:(("NINA",pid=450039,fd=490))                  
UNCONN            0                 0                            &#91;fe80::b225:aaff:fe9f:a2b9]%eno1:mdns                                        &#91;::]:*                 users:(("NINA",pid=450039,fd=492))                  
UNCONN            0                 0                                                           *:39160                                          *:*                 users:(("firefox",pid=4884,fd=163))                 
UNCONN            0                 0                                                           *:46782                                          *:*                 users:(("firefox",pid=4884,fd=139))                 
UNCONN            0                 0                                                       &#91;::1]:323                                         &#91;::]:*                 users:(("chronyd",pid=1813,fd=5))                   
UNCONN            0                 0                            &#91;fe80::b225:aaff:fe9f:a2b9]%eno1:dhcpv6-client                               &#91;::]:*                 users:(("NetworkManager",pid=2067,fd=28))</code></pre>



<p class="wp-block-paragraph">NINA pid=450039<br>192.168.0.13:mdns<br>0.0.0.0:mdns<br>[::]:mdns<br>これは、Alpacaデバイスなどのネットワーク探索で使われる模様です。</p>



<p class="wp-block-paragraph">python3 pid=162082<br>192.168.0.13:3702<br>239.255.255.250:3702<br>0.0.0.0:37426<br>*:35462<br>239.255.255.250:3702 は WS-Discovery で使われるマルチキャストアドレス/ポートです。<br>Alpaca/ASCOMデバイス探索と関係するネットワーク探索を行っているかもしれません。</p>



<p class="wp-block-paragraph">この段階で、PCには何も機器を接続していません。</p>



<p class="wp-block-paragraph"><em>:35462 : users:((&#8220;python3&#8221;,pid=162082,fd=12))<br>UNCONN 0 0 [fe80::b225:aaff:fe9f:a2b9]%eno1:3702 [::]:</em> users:((&#8220;python3&#8221;,pid=162082,fd=13))<br>UNCONN 0 0 [ff02::c]%eno1:3702 [::]:* users:((&#8220;python3&#8221;,pid=162082,fd=11))<br>これを調べます。</p>



<pre class="wp-block-code"><code>ps -fp 162082
UID          PID    PPID  C STIME TTY          TIME CMD
USERNAME    162082  162077  0  9月08 ?      00:00:02 python3 /usr/bin/wsdd --no-host --discovery --listen /run/user/1000/gvfsd/wsdd</code></pre>



<p class="wp-block-paragraph">現在動いているNINA（PID 450039）が、ネットワーク通信で何をしているかをリアルタイムで見てみます。</p>



<pre class="wp-block-code"><code>sudo strace -p 450039 -f -e trace=network -tt
strace: Process 450039 attached with 34 threads
strace: Process 451155 attached
&#91;pid 451155] 14:37:41.931321 +++ exited with 0 +++
strace: Process 451187 attached
&#91;pid 451187] 14:38:13.247452 +++ exited with 0 +++</code></pre>



<p class="wp-block-paragraph">NINAがだんまりを決め込んでるように見えてますが、そうではないらしい。</p>



<p class="wp-block-paragraph">クラッシュしていない、CPUを多少使用している、INDI接続は存在、ネットワークエラーも発生していない。</p>



<p class="wp-block-paragraph">NINAの各スレッド、CPU使用率、wchan（カーネル内で何を待っているか）を表示します。</p>



<pre class="wp-block-code"><code>ps -L -p 450039 -o pid,tid,stat,pcpu,wchan:32,comm --sort=-pcpu</code></pre>



<p class="wp-block-paragraph">待機中です。</p>



<p class="wp-block-paragraph">全スレッドを対象に、どこで待っているかを見てみます。</p>



<pre class="wp-block-code"><code>ps -T -p 450039 -o pid,tid,stat,pcpu,wchan:32,comm</code></pre>



<p class="wp-block-paragraph">ん〜</p>



<pre class="wp-block-code"><code>ps -T -p 450039 -o pid,tid,stat,pcpu,wchan:32,comm
    PID     TID STAT %CPU WCHAN                            COMMAND
 450039  450039 Sl+   0.0 futex_do_wait                    NINA
 450039  450040 Sl+   0.0 poll_schedule_timeout.constprop. .NET SynchManag
 450039  450041 Sl+   0.0 poll_schedule_timeout.constprop. .NET EventPipe
 450039  450042 Sl+   0.0 wait_for_partner                 .NET DebugPipe
 450039  450043 Sl+   0.0 futex_do_wait                    .NET Debugger
 450039  450044 Sl+   0.0 futex_do_wait                    .NET Finalizer
 450039  450047 Sl+   0.5 futex_do_wait                    .NET Timer
 450039  450049 Sl+   0.0 futex_do_wait                    .NET TP Gate
 450039  450051 Sl+   0.0 anon_pipe_read                   .NET SigHandler
 450039  450058 Sl+   0.0 ep_poll                          .NET Sockets
 450039  450060 Sl+   0.0 poll_schedule_timeout.constprop. .NET TP Worker
 450039  450061 Sl+   0.0 hrtimer_nanosleep                .NET TP Worker
 450039  450062 Sl+   0.0 poll_schedule_timeout.constprop. libusb_event
 450039  450067 Sl+   0.0 poll_schedule_timeout.constprop. .NET TP Worker
 450039  450068 Sl+   0.0 futex_do_wait                    Kestrel Timer
 450039  450071 Sl+   0.0 futex_do_wait                    API Thread
 450039  450072 Sl+   0.0 futex_do_wait                    Log watcher thr
 450039  450073 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450074 Sl+   0.0 futex_do_wait                    Touch-N-Stars A
 450039  450075 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450076 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450077 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450078 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450087 Sl+   0.0 futex_do_wait                    API Thread
 450039  450088 Sl+   0.0 futex_do_wait                    Log watcher thr
 450039  450089 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450098 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450099 Sl+   0.0 wait_woken                       .NET File Watch
 450039  450100 Sl+   0.2 poll_schedule_timeout.constprop. .NET TP Worker
 450039  451049 Sl+   0.6 futex_do_wait                    .NET TP Worker
 450039  451093 Sl+   0.4 futex_do_wait                    .NET TP Worker
 450039  451837 Sl+   0.3 futex_do_wait                    .NET TP Worker
 450039  451922 Sl+   0.3 futex_do_wait                    .NET TP Worker
 450039  451945 Sl+   0.3 futex_do_wait                    .NET TP Worker</code></pre>



<p class="wp-block-paragraph">全て、待機状態だ。ループやデッドロックで固まってないようです。<br>ん〜〜。。。NINAのGUI初期化中に何かの非同期処理を待っているように感じる。。。</p>



<p class="wp-block-paragraph">PCのブラウザから、</p>



<pre class="wp-block-code"><code>http:&#47;&#47;127.0.0.1:5000</code></pre>



<p class="wp-block-paragraph">ここで全て行うのか？<br>NINAが実際にどのポートをLISTENしているか見てみます。</p>



<pre class="wp-block-code"><code>sudo ss -ltnp | grep NINA
LISTEN 0      512          0.0.0.0:4782      0.0.0.0:*    users:(("NINA",pid=450039,fd=385))        
LISTEN 0      500                *:5000            *:*    users:(("NINA",pid=450039,fd=452))        
LISTEN 0      500                *:1889            *:*    users:(("NINA",pid=450039,fd=499))        
LISTEN 0      500                *:1888            *:*    users:(("NINA",pid=450039,fd=422))</code></pre>



<p class="wp-block-paragraph">NINAは以下のポートをLISTENしています。<br>4782 → NINA<br>5000 → NINA<br>1889 → NINA<br>1888 → NINA</p>



<p class="wp-block-paragraph">初めに分かっていたのに、スルーしちゃった。</p>



<pre class="wp-block-code"><code>http:&#47;&#47;127.0.0.1:5000</code></pre>



<p class="has-text-align-right wp-block-paragraph">「なーんだ、ブラウザでひとまず全てができるかな&#8230;」</p>



<p class="wp-block-paragraph">機器を接続した際には、まず</p>



<pre class="wp-block-code"><code>lsusb</code></pre>



<p class="wp-block-paragraph">Althiba3をUSB接続すると、下記のデバイス表示になりました。</p>



<pre class="wp-block-code"><code>Bus 003 Device 004: ID 04b4:6572 Cypress Semiconductor Corp. Unprogrammed CY7C65642 hub
Bus 003 Device 005: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial</code></pre>



<p class="wp-block-paragraph">Cypress Semiconductor<br>CY7C65642: HX2VL &#8211; 超低消費電力USB 2.0 TetraHub™ コントローラー</p>



<p class="wp-block-paragraph">Vendor ID (ベンダーID): 16C0 (Van Ooijen Technische Informatica)<br>Device ID (デバイスID): 0483 (Teensyduino Serial)</p>



<p class="wp-block-paragraph">ModemManager がデバイスを制御を行うので、これを削除します。</p>



<pre class="wp-block-code"><code>sudo apt remove modemmanager</code></pre>



<p class="wp-block-paragraph">PI.N.S.のログにもあるように、ユーザーアカウントをdialoutグループに加えます。</p>



<pre class="wp-block-code"><code>sudo adduser ${USER} dialout</code></pre>



<p class="wp-block-paragraph">これで、Althiba3、Teensyduino Serialが制御できます。</p>



<p class="wp-block-paragraph">ガイドカメラとphd2の設定は、PI.N.S.からではなく、phd2から設定を行います。</p>



<p class="wp-block-paragraph">http://127.0.0.1:5000/equipment<br>一括切断<br>PHD2設定画面で、機器と接続、カメラとマウントをそれぞれ、<br>ZWO ASI462MC<br>INDI Mount [LX200 TeenAsto]を指定し、「全て接続」<br>http://127.0.0.1:5000/equipment<br>一括接続</p>



<p class="wp-block-paragraph">その後、PI.N.S.機器制御から指定できます。</p>



<figure class="wp-block-image size-full"><img decoding="async" width="800" height="673" src="https://globe3.ddns.net/wp/wp-content/uploads/2026/09/INDI_setup.jpg" alt="" class="wp-image-5982" srcset="https://globe3.ddns.net/wp/wp-content/uploads/2026/09/INDI_setup.jpg 800w, https://globe3.ddns.net/wp/wp-content/uploads/2026/09/INDI_setup-300x252.jpg 300w, https://globe3.ddns.net/wp/wp-content/uploads/2026/09/INDI_setup-150x126.jpg 150w, https://globe3.ddns.net/wp/wp-content/uploads/2026/09/INDI_setup-768x646.jpg 768w" sizes="(max-width: 800px) 100vw, 800px" /></figure>



<h2 class="wp-block-heading">試行錯誤の跡</h2>



<div class="wp-block-cocoon-blocks-sticky-box blank-box block-box sticky">
<p class="wp-block-paragraph">上記でPI.N.S. 及び、N.I.N.Aが動いたので、ここより、以下は未実施</p>
</div>



<p class="wp-block-paragraph">ビルド時のAPI／互換性問題を解決します。</p>



<p class="wp-block-paragraph">CMake 4.2.3対応：VERSION 2.8.12.2 → VERSION 3.5<br>FFmpeg 8対応：avcodec_close()　をFFmpeg 8未満の場合だけ実行<br>FFmpeg 8対応：av_stream_get_side_data()</p>



<p class="wp-block-paragraph">OpenCV 4.11.0の cap_ffmpeg_impl.hpp を修正します。</p>



<p class="wp-block-paragraph">現在の状態をバックアップします。</p>



<pre class="wp-block-code"><code>cd ~/pins/artifacts/src/opencv/opencv-4.11.0

cp modules/videoio/src/cap_ffmpeg_impl.hpp \
   /tmp/cap_ffmpeg_impl.hpp.org</code></pre>



<p class="wp-block-paragraph">avcodec_close() を修正します。</p>



<pre class="wp-block-code"><code>cd ~/pins/artifacts/src/opencv/opencv-4.11.0
sed -n '682,700p' modules/videoio/src/cap_ffmpeg_impl.hpp

#endif
    }

    if( video_st )
    {
#ifdef CV_FFMPEG_CODECPAR
        avcodec_close( context );
#endif
        video_st = NULL;
    }

    if (context)
    {
#ifdef CV_FFMPEG_CODECPAR
        avcodec_free_context(&amp;context);
#endif
    }

    if( ic )
</code></pre>



<pre class="wp-block-code"><code>#ifdef CV_FFMPEG_CODECPAR
        avcodec_close( context );
#endif</code></pre>



<p class="wp-block-paragraph">元のOpenCVコードをFFmpeg 8.0に合わせて変更します。<br>cap_ffmpeg_impl.hpp 682行以降です。</p>



<pre class="wp-block-code"><code>nano ~/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp</code></pre>



<pre class="wp-block-code"><code>### 変更前
#ifdef CV_FFMPEG_CODECPAR
        avcodec_close( context );
#endif</code></pre>



<pre class="wp-block-code"><code>### 変更後
#ifdef CV_FFMPEG_CODECPAR
// avcodec_close removed in FFmpeg release 8.0
# if (LIBAVCODEC_BUILD &lt; CALC_FFMPEG_VERSION(62, 11, 100))
        avcodec_close( context );
# endif
#endif</code></pre>



<p class="wp-block-paragraph">CV_FFMPEG_CODECPAR が有効<br>↓<br>FFmpegのバージョンを確認<br>↓<br>62.11.100 より古い<br>├─ Yes → avcodec_close() を使う<br>└─ No → avcodec_close() を使わない</p>



<p class="wp-block-paragraph">続けて、av_stream_get_side_data()　を修正します。</p>



<pre class="wp-block-code"><code>nano ~/pins/artifacts/src/opencv/opencv-4.11.0/modules/videoio/src/cap_ffmpeg_impl.hpp</code></pre>



<p class="wp-block-paragraph">2000行以降です。</p>



<pre class="wp-block-code"><code>### 変更前
#if LIBAVFORMAT_BUILD &gt;= CALC_FFMPEG_VERSION(57, 68, 100)
    const uint8_t *data = 0;
    data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
    if (data)</code></pre>



<pre class="wp-block-code"><code>### 変更後
#if LIBAVFORMAT_BUILD &gt;= CALC_FFMPEG_VERSION(57, 68, 100)
    const uint8_t *data = 0;
// av_stream_get_side_data removed in FFmpeg release 8.0
# if (LIBAVCODEC_BUILD &lt; CALC_FFMPEG_VERSION(62, 11, 100))
    data = av_stream_get_side_data(video_st, AV_PKT_DATA_DISPLAYMATRIX, NULL);
# else
    AVPacketSideData* sd = video_st-&gt;codecpar-&gt;coded_side_data;
    int nb_sd = video_st-&gt;codecpar-&gt;nb_coded_side_data;
    if (sd &amp;&amp; nb_sd &gt; 0)
    {
        const AVPacketSideData* mtx =
            av_packet_side_data_get(sd, nb_sd, AV_PKT_DATA_DISPLAYMATRIX);
        if (mtx)
            data = mtx-&gt;data;
    }
# endif
    if (data)</code></pre>



<p class="wp-block-paragraph">OpenCVソースに対する変更を確認を行います。</p>



<pre class="wp-block-code"><code>cd ~/pins
git status --short</code></pre>



<p class="wp-block-paragraph">再度、スクリプトを実行します。</p>



<pre class="wp-block-code"><code>./build-and-install-pins-x64.sh</code></pre>



<pre class="wp-block-code"><code>grep -n -E \
  "OPENCV_INSTALL_PREFIX|OPENCV_REQUIRE_LOCAL_PKGCONFIG|get_opencv_version|get_local_opencv_pkgconfig_version|activate_opencv_environment" \
  build-and-install-pins-x64.sh
113:OPENCV_INSTALL_PREFIX="${OPENCV_INSTALL_PREFIX:-/usr/local}"
115:OPENCV_REQUIRE_LOCAL_PKGCONFIG="${OPENCV_REQUIRE_LOCAL_PKGCONFIG:-true}"
460:get_opencv_version() {</code></pre>



<p class="wp-block-paragraph">113行目で、opencv4をインストールした、/usr/local　を見に行っています。</p>



<pre class="wp-block-code"><code>OPENCV_INSTALL_PREFIX="${OPENCV_INSTALL_PREFIX:-/usr/local}"
↓
OPENCV_INSTALL_PREFIX=/usr/local
↓
要求バージョンと一致
↓
activate_opencv_environment
↓
以降のPINSビルドでそのOpenCVを使用</code></pre>



<h3 class="wp-block-heading">Node.js 22をインストール</h3>



<p class="wp-block-paragraph">Node.js 22をインストール<br>　JavaScriptをPC上で実行するための実行環境です</p>



<p class="wp-block-paragraph">Node.js 22は、<br><a rel="noopener" target="_blank" href="https://github.com/nitr57/pins/blob/develop/build-and-install-pins-x64.sh">https://github.com/nitr57/pins/blob/develop/build-and-install-pins-x64.sh</a><br>ここで指定されています。</p>



<pre class="wp-block-code"><code>install_node_22() {
local node_ok="false"

if command -v node &gt;/dev/null 2&gt;&amp;1; then
local node_major
node_major="$(node -p 'process.versions.node.split(".")&#91;0]')"
if &#91;&#91; "$node_major" == "22" ]]; then
node_ok="true"
fi</code></pre>



<p class="wp-block-paragraph">ここに案内があります。<br><a rel="noopener" target="_blank" href="https://nodejs.org/ja/download">https://nodejs.org/ja/download</a><br>「全ての過去のリリース」にリンクがあり、v22.23.2 (Jod) を選べます。<br><a rel="noopener" target="_blank" href="https://nodejs.org/dist/v22.23.2/node-v22.23.2-linux-x64.tar.xz">node-v22.23.2-linux-x64.tar.xz</a> を用います。</p>



<p class="wp-block-paragraph">バージョン確認</p>



<pre class="wp-block-code"><code>~/Downloads/node-v22.23.2-linux-x64/bin/node --version
v22.23.2</code></pre>



<pre class="wp-block-code"><code>### 一時的にPATHを設定
export PATH="$HOME/Downloads/node-v22.23.2-linux-x64/bin:$PATH"
npm --version
10.9.8</code></pre>



<h3 class="wp-block-heading">.NET SDK Linux x64をインストール</h3>



<p class="wp-block-paragraph">.NET SDK Linux x64をインストール<br>　PINS develop が指定するバージョンを確認します。</p>



<pre class="wp-block-code"><code>~/pins$ less global.json
{
  "sdk": {
    "version": "10.0.400",
    "rollForward": "latestPatch"
  }
}</code></pre>



<p class="wp-block-paragraph">PINS develop は .NET SDK 10.0.400 を指定しています。</p>



<p class="wp-block-paragraph">PINSをclone</p>



<h3 class="wp-block-heading">SDKバージョン</h3>



<p class="wp-block-paragraph">global.json を10.0.302に変更</p>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">NINA.Sequencer.Generators を新しい Roslyn 5.6 でビルドした DLL を、古い Roslyn 5.0 相当の SDK 10.0.111 でアナライザーとして実行していることが原因なので、</p>



<p class="wp-block-paragraph"><br>PINSビルドには、SDK 10.0.302 / Linux x64を入れる。</p>
</div>



<p class="wp-block-paragraph">.NET SDK 10.0.302 をインストール</p>



<p class="wp-block-paragraph">Microsoft の公式 .NET SDK ダウンロードページから SDK 10.0.302 / Linux x64 を入れます。<br>Microsoft が提供している .NET SDK 10.0.302 のバイナリ/パッケージを直接入れるます。</p>



<p class="wp-block-paragraph">.NET SDK 10.0.302<br>10.0.10にSDK 10.0.302の案内があります。<br><a rel="noopener" target="_blank" href="https://dotnet.microsoft.com/ja-jp/download/dotnet/10.0">https://dotnet.microsoft.com/ja-jp/download/dotnet/10.0</a></p>



<p class="wp-block-paragraph">手動インストール<br><a rel="noopener" target="_blank" href="https://learn.microsoft.com/ja-jp/dotnet/core/install/linux-scripted-manual">https://learn.microsoft.com/ja-jp/dotnet/core/install/linux-scripted-manual</a></p>



<p class="wp-block-paragraph">.NET 10.0 SDK (v10.0.302) &#8211; Linux x64 Binariesをインストールします。<br>apt版とは別に共存できるようです。</p>



<p class="wp-block-paragraph">Microsoft の公式手順ではホームディレクトリに：<br>$HOME/dotnet/<br>として展開します。公式手順も mkdir -p $HOME/dotnet → tar 展開 → DOTNET_ROOT と PATH を設定、という方式です。</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">mkdir -p $HOME/dotnet &amp;&amp; tar zxf dotnet-sdk-10.0.302-linux-x64.tar.gz -C $HOME/dotnet<br>export DOTNET_ROOT=$HOME/dotnet<br>export PATH=$PATH:$HOME/dotnet<br><br><a rel="noopener" target="_blank" href="https://dotnet.microsoft.com/ja-jp/download/dotnet/thank-you/sdk-10.0.302-linux-x64-binaries-targz">https://dotnet.microsoft.com/ja-jp/download/dotnet/thank-you/sdk-10.0.302-linux-x64-binaries-targz</a></p>
</blockquote>



<pre class="wp-block-code"><code>pwd /home/USERNAME/
mkdir -p "$HOME/.dotnet"</code></pre>



<p class="wp-block-paragraph">既にディレクトがある場合は、そのまま使います。</p>



<pre class="wp-block-code"><code>cd .dotnet/
~/.dotnet$ ll
total 16

0 Sep  4 16:28 .workloadAdvertisingManifestSentinel10.0.100
0 Sep  4 16:21 10.0.111.aspNetCertificateSentinel
0 Sep  4 16:21 10.0.111.dotnetFirstUseSentinel
0 Sep  4 16:21 10.0.111.toolpath.sentinel
4096 Sep  4 16:21 corefx/
4096 Sep  4 16:28 sdk-advertising/</code></pre>



<p class="wp-block-paragraph">SDK本体はこのディレクトリにはありません。<br>SDK 10.0.111 本体は /usr/lib/dotnet にあります。</p>



<p class="wp-block-paragraph">dotnet-sdk-10.0.302-linux-x64.tar.gz を、 ~/.dotnetへ展開します。</p>



<pre class="wp-block-code"><code>tar -xzf ~/Downloads/dotnet-sdk-10.0.302-linux-x64.tar.gz -C ~/.dotnet</code></pre>



<p class="wp-block-paragraph">PINS GitHub　&lt;&gt;codeの案内に沿って、PINSコードを~/pins へ収めます。</p>



<pre class="wp-block-code"><code>### https://github.com/nitr57/pins.git

git clone --branch develop https://github.com/nitr57/pins.git
cd pins

git branch --show-current
develop</code></pre>



<p class="wp-block-paragraph">clone 直後の状態を確認します。</p>



<pre class="wp-block-code"><code>cd ~/pins/NINA
git status
git status
ブランチ develop
Your branch is up to date with 'origin/develop'.
nothing to commit, working tree clean

git branch --show-current
develop

git rev-parse HEAD
d9acaf5488bbf8b07cf1e8f4ea0c52edb1fa1ff7</code></pre>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">~/pins/NINA<br>ブランチ: develop<br>HEAD: d9acaf5488bbf8b07cf1e8f4ea0c52edb1fa1ff7<br>working tree: clean</p>
</div>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://globe3.ddns.net/wp/porting-pins-to-x86_64-gun-linux/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Ubuntu KStars 3.8.2 Flatpak版へ行こう</title>
		<link>https://globe3.ddns.net/wp/flatpak-version-kstars-ubuntu24-04-migrate-my-data/</link>
					<comments>https://globe3.ddns.net/wp/flatpak-version-kstars-ubuntu24-04-migrate-my-data/#respond</comments>
		
		<dc:creator><![CDATA[minmin]]></dc:creator>
		<pubDate>Mon, 18 May 2026 00:31:48 +0000</pubDate>
				<category><![CDATA[INDI-Library]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<guid isPermaLink="false">https://globe3.ddns.net/wp/?p=3263</guid>

					<description><![CDATA[Ubuntu 24.04 に Flatpak版 KStarsを用います。これまでのデータも移行します。 KStars 3.8.1 を使って、極軸修正を行うと、とんでもない修正値が表示されました。「いやいや、沖縄くらいの緯 [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Ubuntu 24.04 に Flatpak版 KStarsを用います。これまでのデータも移行します。</p>



<p class="wp-block-paragraph">KStars 3.8.1 を使って、極軸修正を行うと、とんでもない修正値が表示されました。<br>「いやいや、沖縄くらいの緯度には居ないって」</p>



<h2 class="wp-block-heading">KStars 3.8.1 と Apt installed KStars は、Polar Alignment に不備</h2>



<p class="wp-block-paragraph">KStars 3.8.1には、 Polar Alignment に不備があります。<br>Ubuntuシステムから、aptなどでインストールされた、KStars 3.8.2はこの不備が未修正です。</p>


<a rel="noopener" target="_blank" href="https://knro.blogspot.com/2026/04/kstars-382-released.html" title="KStars 3.8.2 Released" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/c4dfe581a5fa0e2f86caad917790c83c.jpg" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">KStars 3.8.2 Released</div><div class="blogcard-snippet external-blogcard-snippet">KStars v3.8.2 is released on 2026.04.08 for Windows, Linux, and MacOS . For Linux users, it&#039;s highly recommended to use &#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=http://knro.blogspot.com/2026/04/kstars-382-released.html" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">knro.blogspot.com</div></div></div></div></a>


<p class="wp-block-paragraph">KStars 3.8.2に案内がありました。「Linux使いは、Flatpak版を強くお勧めしますよ」<br>極軸修正についての案内もありました。<br></p>



<h2 class="wp-block-heading">Flatpak を Ubuntuにインストール</h2>


<a rel="noopener" target="_blank" href="https://flatpak.org/setup/Ubuntu" title="Flatpak—the future of application distribution" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fflatpak.org%2Fsetup%2FUbuntu?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Flatpak—the future of application distribution</div><div class="blogcard-snippet external-blogcard-snippet"></div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://flatpak.org/setup/Ubuntu" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">flatpak.org</div></div></div></div></a>


<p class="wp-block-paragraph">Flatpak の Ubuntuに設定する案内に沿って、インストールします。</p>



<pre class="wp-block-code"><code>$ sudo apt install flatpak
$ sudo apt install gnome-software-plugin-flatpak  # GUIを使わないならば不要
$ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
$ sudo reboot</code></pre>



<h2 class="wp-block-heading">Flatpak版、KStarsをUbuntuへインストール</h2>



<p class="wp-block-paragraph">再起動後に、「はて、KStars Flatpak版はどうやってインストールするのかな？」<br>kstars.kde.orgに案内があるので、これに沿ってインストールしていきます。</p>


<a rel="noopener" target="_blank" href="https://kstars.kde.org/download/linux" title="KStars for Linux" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/a50d54f03471389105226615179d9385.png" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">KStars for Linux</div><div class="blogcard-snippet external-blogcard-snippet">What is Flatpak? Flatpak is a modern packaging and distribution system for Linux applications. It allows developers to b&#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://kstars.kde.org/download/linux/" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">kstars.kde.org</div></div></div></div></a>


<pre class="wp-block-code"><code>インストールスクリプトをダウンロードする
$ wget https://raw.githubusercontent.com/ikarustechnologies/indi-firmware/main/kstars.sh

安定版の場合(ほとんどの皆さんに推奨されています):
$ bash kstars.sh

自動更新
$ bash kstars.sh

手動にて直接更新
flatpak update org.kde.kstars</code></pre>



<pre class="wp-block-code"><code>開発版ならば、
$ bash kstars.sh nightly

1. &#91;✓] org.freedesktop.Platform.GL.default                        25.08                   i              flathub             146.9 MB / 147.9 MB
 2. &#91;✓] org.freedesktop.Platform.GL.default                        25.08-extra             i              flathub              28.2 MB / 148.0 MB
 3. &#91;✓] org.freedesktop.Platform.GL.nvidia-580-178-04              1.4                     i              flathub             331.7 MB / 332.1 MB
 4. &#91;✓] org.freedesktop.Platform.VAAPI.nvidia                      25.08                   i              flathub              68.2 kB / 75.8 kB
 5. &#91;✓] org.freedesktop.Platform.codecs-extra                      25.08-extra             i              flathub              14.4 MB / 14.6 MB
 6. &#91;✓] org.gtk.Gtk3theme.Yaru-dark                                3.22                    i              flathub             134.3 kB / 196.5 kB
 7. &#91;✓] org.kde.Platform.Locale                                    6.10                    i              flathub               1.9 MB / 401.9 MB
 8. &#91;✓] org.kde.Platform                                           6.10                    i              flathub             319.3 MB / 392.1 MB

 1. &#91;✓] org.kde.Sdk.Locale          6.10           i          flathub         274.6 kB / 417.8 MB
 2. &#91;✓] org.kde.Sdk                 6.10           i          flathub         830.6 MB / 1.1 GB

org.kde.kstars permissions:
    ipc      network      fallback-x11      pulseaudio      wayland      devices      devel      file access &#91;1]     dbus access &#91;2]     tags &#91;3]

    &#91;1] xdg-config/kdeglobals:ro, xdg-documents, xdg-pictures, xdg-videos, ~/.cache/sentry, ~/.indi
    &#91;2] com.canonical.AppMenu.Registrar, org.kde.KGlobalSettings, org.kde.kconfig.notify
    &#91;3] nightly


        ID                              Branch           Op          Remote                  Download
 1. &#91;✓] org.kde.kstars.Locale           master           i           kstars-nightly          202.2 kB / 14.7 MB
 2. &#91;✓] org.kde.kstars                  master           i           kstars-nightly          413.2 MB / 469.9 MB

Installation complete.
Looking for updates…

Nothing to do.
KStars Flatpak version nightly installed.
Script finished.
 
================================================================
================================================================
                   Installation completed 
                For running the Kstars, run: 
       flatpak run --user org.kde.kstars//master 
================================================================
================================================================</code></pre>



<p class="wp-block-paragraph">インストール後のコンソールに、以下が表示されました。</p>



<pre class="wp-block-code"><code>安定版

================================================================
================================================================
                   Installation completed 
                For running the Kstars, run: 
       flatpak run --user org.kde.kstars//stable  
================================================================
================================================================</code></pre>



<p class="wp-block-paragraph">Flatpak版 KStarsを使うには次のコマンです。</p>



<pre class="wp-block-code"><code>$ flatpak run --user org.kde.kstars//stable</code></pre>



<p class="wp-block-paragraph">KStarsを起動すると、以下の表示があり、KStarsが使うデータのディレクトリが分ります。</p>



<pre class="wp-block-code"><code>org.kde.kstars: Loaded DSO catalog file:  "unnamedstars.dat"
org.kde.kstars: "星 HD20,794 が見つかりません。"
org.kde.kstars: "星 HD98,230 が見つかりません。"
org.kde.kstars: Loaded DSO catalogs.
org.kde.kstars: Loading asteroids
org.kde.kstars: Loading asteroid objects failed.
org.kde.kstars: " -&gt; was trying to read /home/USERNAME/.var/app/org.kde.kstars/data/kstars/asteroids.dat"
org.kde.kstars: Loading comets
</code></pre>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">KStars インストールやデータ移行</h2>



<p class="wp-block-paragraph">これまで使っていたリポジトリインストール版からのデータ移行もします。</p>


<a rel="noopener" target="_blank" href="https://kstars.kde.org/download/linux" title="KStars for Linux" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/a50d54f03471389105226615179d9385.png" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">KStars for Linux</div><div class="blogcard-snippet external-blogcard-snippet">What is Flatpak? Flatpak is a modern packaging and distribution system for Linux applications. It allows developers to b&#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://kstars.kde.org/download/linux/" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">kstars.kde.org</div></div></div></div></a>


<p class="wp-block-paragraph">kstars.kde.orgにインストールやデータ移行の案内があります。</p>



<p class="wp-block-paragraph">/home/USERNAME/.config/kstarsrc<br>このディレクトリに構成や設定データがあります。(自分のubuntu環境ではありませんでした)</p>



<p class="wp-block-paragraph">/home/USERNAME/.local/share/kstars<br>Gaiaや天体位置測定、星図にあるフラグデータ(userdb.sqlite)などがあります。<br>これを KStars Flatpak版 が使えるように移行させます。</p>



<pre class="wp-block-code"><code>kstars.kde.org の案内は以下です
cp -r ~/.config/kstarsrc ~/.var/app/org.kde.kstars/config/
cp -r ~/.local/share/kstars ~/.var/app/org.kde.kstars/data/</code></pre>



<pre class="wp-block-code"><code>KStarsの構成や設定データを移行する
cp -r ~/.config/kstarsrc ~/.var/app/org.kde.kstars/config/

KStars各種データを移行する。こちらのUbuntu環境では次でした。
cp -p -r ~/.local/share/kstars ~/.var/app/org.kde.kstars/data/</code></pre>



<h2 class="wp-block-heading">KStars 設定</h2>



<p class="wp-block-paragraph">&#8220;INDI Control Panel&#8221; &#8220;Ekos&#8221; &#8220;KStars&#8221;などの画面が分離して表示させる。<br>independent window　をチェック</p>



<p class="wp-block-paragraph">File Settings<br>撮影画像ディレクトリ、及び名前形式を決めます。<br>Format: /%T/%t/%t_%T_%F_%e_%D<br><br>撮影画像名は、指定されたディレクトリに、次のファイル名になります。<br>/Light/M1/M1_Light_HEUIB-II_180_secs_2025-09-15T23-51-16_001.fits</p>



<ul class="wp-block-list">
<li>%f (ファイル名): 拡張子を除いた .esq ファイルの名前</li>



<li>%D (日付/時刻): ファイルが保存された時刻と日付</li>



<li>%T (タイプ): フレームのタイプ (例: “Light”、”Dark “など)</li>



<li>%e (露出): 露光時間（秒）</li>



<li>%F (フィルター): 使用するフィルター名</li>



<li>%t (ターゲット): ターゲット名</li>



<li>%s (シーケンス): イメージ シーケンスの識別子。* は使用される桁数 (1 ～ 9) です。 このタグは必須であり、形式の最後の要素である必要があります。</li>



<li>サフィックス: ファイル名にシーケンス番号を追加するために使用される桁数</li>
</ul>



<p class="wp-block-paragraph">マウスポインターの形を変えるには、<br>KStars画面 → 設定 → KStarsを設定 → 詳細 → Look and Feel<br></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph">Flatpak版 KStarsインストール中のコンソール表示は、</p>



<pre class="wp-block-code"><code>$ wget https://raw.githubusercontent.com/ikarustechnologies/indi-firmware/main/kstars.sh
$ bash kstars.sh
Checking for and installing flatpak...
Flatpak is already installed.
Checking for and installing fxload (required for QHYCCD firmware)...
Detected Debian/Ubuntu. Installing fxload using apt...

以下のパッケージが新たにインストールされます:
  fxload

Cloning repository 'https://github.com/ikarustechnologies/indi-firmware.git'...
Cloning into '/home/USERNAME/.indi-firmware'...
remote: Enumerating objects: 447, done.
remote: Counting objects: 100% (82/82), done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 447 (delta 35), reused 54 (delta 19), pack-reused 365 (from 1)
Receiving objects: 100% (447/447), 1.78 MiB | 3.33 MiB/s, done.
Resolving deltas: 100% (192/192), done.
Creating destination directories: /lib/udev/rules.d, /lib/firmware/qhy...
Destination directories created.
Copying udev rules files to /lib/udev/rules.d...
'/home/USERNAME/.indi-firmware/indi/drivers/auxiliary/99-indi_auxiliary.rules' -&gt; '/lib/udev/rules.d/99-indi_auxiliary.rules'
'/home/USERNAME/.indi-firmware/indi/drivers/video/80-dbk21-camera.rules' -&gt; '/lib/udev/rules.d/80-dbk21-camera.rules'
'/home/USERNAME/.indi-firmware/indi-3rdparty/indi-ffmv/99-fireflymv.rules' -&gt; '/lib/udev/rules.d/99-fireflymv.rules'
'/home/USERNAME/.indi-firmware/indi-3rdparty/indi-nightscape/99-nightscape.rules' -&gt; '/lib/udev/rules.d/99-nightscape.rules'
'/homeUSERNAME/.indi-firmware/indi-3rdparty/indi-armadillo-platypus/99-armadilloplatypus.rules' -&gt; '/lib/udev/rules.d/99-armadilloplatypus.rules'

Udev rules files copied.
Installing fxload helper script to /usr/local/sbin/indi-fxload...

Copying individual firmware files to /lib/firmware...
'/home/USERNAME/.indi-firmware/indi-3rdparty/libfishcamp/gdr_usb.hex' -&gt; '/lib/firmware/gdr_usb.hex'

Individual firmware files copied.

Copying QHY firmware files to /lib/firmware/qhy...
'/home/USERNAME/.indi-firmware/indi-3rdparty/libqhy/firmware/IC16200A.HEX' -&gt; '/lib/firmware/qhy/IC16200A.HEX'

QHY firmware files copied.
Reloading udev rules...
Udev rules reloaded.
Adding Flathub remote if it doesn't exist...
Flathub remote added.
Adding kstars-nightly hub remote if it doesn't exist...
kstars-nightly remote added.
Installing KDE Platform and SDK runtimes...
Looking for matches…

        ID                                           Branch             Op        Remote         Download
 1. &#91;✓] org.freedesktop.Platform.GL.default          25.08              i         flathub        141.4&nbsp;MB / 142.4&nbsp;MB
 2. &#91;✓] org.freedesktop.Platform.GL.default          25.08-extra        i         flathub         25.6&nbsp;MB / 142.4&nbsp;MB
 3. &#91;✓] org.freedesktop.Platform.VAAPI.Intel         25.08              i         flathub         13.6&nbsp;MB / 13.7&nbsp;MB
 4. &#91;✓] org.freedesktop.Platform.codecs-extra        25.08-extra        i         flathub         14.2&nbsp;MB / 14.4&nbsp;MB
 5. &#91;✓] org.gtk.Gtk3theme.Yaru                       3.22               i         flathub        139.3&nbsp;kB / 191.5&nbsp;kB
 6. &#91;✓] org.kde.Platform.Locale                      6.10               i         flathub          1.9&nbsp;MB / 400.7&nbsp;MB
 7. &#91;✓] org.kde.Platform                             6.10               i         flathub        315.8&nbsp;MB / 387.1&nbsp;MB

Installation complete.
Looking for matches…

        ID                          Branch         Op         Remote          Download
 1. &#91;✓] org.kde.Sdk.Locale          6.10           i          flathub         274.6&nbsp;kB / 416.4&nbsp;MB
 2. &#91;✓] org.kde.Sdk                 6.10           i          flathub         821.8&nbsp;MB / 1.1&nbsp;GB

Installation complete.
KDE Platform and SDK runtimes installed.
Installing KStars Flatpak package version stable...
Looking for matches…

org.kde.kstars permissions:
    ipc           network      fallback-x11         pulseaudio           wayland      x11
    devices       devel        file access &#91;1]      dbus access &#91;2]

    &#91;1] xdg-config/kdeglobals:ro, xdg-documents, xdg-pictures, xdg-videos, ~/.cache/sentry, ~/.indi
    &#91;2] com.canonical.AppMenu.Registrar, org.kde.KGlobalSettings, org.kde.kconfig.notify


        ID                     Branch         Op         Remote         Download
 1. &#91;✓] org.kde.kstars         stable         i          flathub        423.7&nbsp;MB / 473.1&nbsp;MB

Installation complete.
Looking for updates…

Nothing to do.
KStars Flatpak version stable installed.
Script finished.

================================================================ 
                   Installation completed 
                For running the Kstars, run: 
       flatpak run --user org.kde.kstars//stable  
================================================================

</code></pre>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
					<wfw:commentRss>https://globe3.ddns.net/wp/flatpak-version-kstars-ubuntu24-04-migrate-my-data/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Ubuntu PC 天文セットアップ</title>
		<link>https://globe3.ddns.net/wp/astronomy-ubuntu-pc-setup/</link>
					<comments>https://globe3.ddns.net/wp/astronomy-ubuntu-pc-setup/#respond</comments>
		
		<dc:creator><![CDATA[minmin]]></dc:creator>
		<pubDate>Fri, 05 Sep 2025 05:11:58 +0000</pubDate>
				<category><![CDATA[INDI-Library]]></category>
		<category><![CDATA[Siril]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[天文]]></category>
		<guid isPermaLink="false">https://globe3.ddns.net/wp/?p=1874</guid>

					<description><![CDATA[ノートPCを天文趣味PCにします。インストールをメモします。 OSは、星の数ほどあるディストリビューションの一つ、GNU/Linux, Ubuntu機器制御、撮影には INDI Library + PHD2画像処理には  [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">ノートPCを天文趣味PCにします。インストールをメモします。<br><br>OSは、星の数ほどあるディストリビューションの一つ、GNU/Linux, Ubuntu<br>機器制御、撮影には INDI Library + PHD2<br>画像処理には Siril &amp; Python</p>



<h2 class="wp-block-heading">Ubuntu インストールメディアを用意</h2>



<p class="wp-block-paragraph">Ubuntu ミラーサイト<br><a rel="noopener" target="_blank" href="https://launchpad.net/ubuntu/+cdmirrors">https://launchpad.net/ubuntu/+cdmirrors</a></p>



<p class="wp-block-paragraph">Ubuntu リリースサイト<br><a rel="noopener" target="_blank" href="https://releases.ubuntu.com/">https://releases.ubuntu.com/</a></p>



<p class="wp-block-paragraph">ブータブルUSBの作成<br>Ubuntu : BalenaEtcher <a rel="noopener" target="_blank" href="https://github.com/balena-io/etcher/releases/">https://github.com/balena-io/etcher/releases/</a><br>Windows : <a rel="noopener" target="_blank" href="https://rufus.ie/ja/">https://rufus.ie/ja/</a></p>



<h2 class="wp-block-heading">インストール後の設定</h2>


<a rel="noopener" target="_blank" href="https://www.server-world.info/query?os=Ubuntu_24.04" title="Ubuntu 24.04 &#12452;&#12531;&#12473;&#12488;&#12540;&#12523;&#12392;&#35373;&#23450; : Server World" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fwww.server-world.info%2Fquery%3Fos%3DUbuntu_24.04?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Ubuntu 24.04 &#12452;&#12531;&#12473;&#12488;&#12540;&#12523;&#12392;&#35373;&#23450; : Server World</div><div class="blogcard-snippet external-blogcard-snippet">Ubuntu 24.04 における各種アプリケーションのインストール方法や設定方法についてまとめています。</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://www.server-world.info/query?os=Ubuntu_24.04" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">www.server-world.info</div></div></div></div></a>


<p class="wp-block-paragraph">こちらを参照しています。有り難うございます。</p>



<h3 class="wp-block-heading">ssh server を追加します。</h3>



<pre class="wp-block-code"><code>$ sudo apt install openssh-server</code></pre>



<h3 class="wp-block-heading">ホームディレクトリを英語に変更します。</h3>



<pre class="wp-block-code"><code>LANG=C xdg-user-dirs-gtk-update
若しくは
LANG=C LC_ALL=C xdg-user-dirs-gtk-update</code></pre>



<h3 class="wp-block-heading">Caps Lock と Ctrl を入れ替え。マウスホイールクリック：<br>GUIでの操作では、Tweaksを使います。</h3>



<pre class="wp-block-code"><code>$ sudo apt install gnome-tweaks</code></pre>



<p class="wp-block-paragraph">&#8220;キーボード&#8221; → &#8220;追加のレイアウトオプション&#8221; → &#8220;Ctrl posision&#8221; → &#8220;CtrlとCaps Lock を入れ替える&#8221;<br>&#8220;マウスとタッチパッド&#8221; → &#8220;中クリックによる貼付け&#8221;</p>



<h3 class="wp-block-heading">バックアップから&#8221;.ファイル&#8221;をダウンロード</h3>



<p class="wp-block-paragraph">Sirilは初期状態に戻したいので、Siril関連は外します。<br>変更や改変したスクリプトは、別に読み込ませます。</p>



<h3 class="wp-block-heading">リモートデスクトップのパスワード設定</h3>



<p class="wp-block-paragraph">リモートデスクトップパスワードを固定にします。</p>



<ul class="wp-block-list">
<li>設定→共有→リモートデスクトップ : Ubuntu 24<br>設定→システム→リモートデスクトップ : Ubuntu 26 <br>&#8220;リモートデスクトップ&#8221; を有効にし、何でも良いので、パスワードを入れ、設定画面を閉じます。</li>



<li>画面左上をクリックし、検索ワードを入力に&#8221;Seahorse&#8221;を入れる。途中まででも良い。</li>



<li>&#8220;パスワードと鍵&#8221;が表示される。</li>



<li>&#8220;Seahorse&#8221;または&#8221;パスワードと鍵&#8221;にある、&#8221;パスワード&#8221;→&#8221;Login（ログイン）&#8221;→&#8221;GNOME Remote Desktop RDP credentials&#8221;項目があることを確認し、これを削除します。</li>



<li>ダミーのパスワードキーリングを作ります。
<ul class="wp-block-list">
<li>&#8220;パスワードと鍵&#8221; 左上の &#8220;+&#8221; → &#8220;パスワードキーリング&#8221; → &#8220;パスワードキーリングを追加&#8221;<br>(keyring-RDP) 例えば、[dummy] → &#8220;追加&#8221;</li>



<li>&#8220;enterキー&#8221;で空パスワードを入れます。[続行をenter] → 暗号化していないパスワードを保存</li>



<li>&#8220;パスワードと鍵&#8221; (Seahorse) に先ほど追加したパスワード項目があります。<br>これを右クリックで&#8221;デフォルト&#8221;指定し、設定画面を閉じます。</li>
</ul>
</li>



<li>リモートデスクトップ設定を開き、使いたいユーザー名とパスワードを入力し、設定画面を閉じます。</li>



<li>&#8220;パスワードと鍵&#8221; (Seahorse)を再度開き、&#8221;パスワード&#8221;→&#8221;dummy&#8221;→ 先ほど追加した項目に&#8221;GNOME Remote Desktop RDP credentials&#8221;項目があることを確認します。
<ul class="wp-block-list">
<li>&#8220;パスワードと鍵&#8221; (Seahorse&#8221;にある、&#8221;パスワード&#8221;→&#8221;ログイン&#8221;を右クリックし、デフォルトに指定します。</li>
</ul>
</li>
</ul>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">先ほど作った、&#8221;keyring-RDP&#8221;ではなく、&#8221;ログイン&#8221;をデフォルトにします。</p>
</div>



<ul class="wp-block-list">
<li>ノートPCを閉じてもサスペンドさせない</li>
</ul>



<p class="wp-block-paragraph">/etc/systemd/logind.conf を編集します。</p>



<pre class="wp-block-code"><code>/etc/systemd/logind.conf
#HandleLidSwitch=suspend                                                                                                                                                                                                                      
HandleLidSwitch=ignore</code></pre>



<p class="wp-block-paragraph">logind (systemd-logind)は、ユーザーログインを管理します。<br>設定を反映させるには、Ubuntuを再起動します。<br>若しくは、logindを再起動させます。</p>



<pre class="wp-block-preformatted">$ sudo systemctl restart systemd-logind</pre>



<h2 class="wp-block-heading">天体画像処理 Siril, Python</h2>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><a rel="noopener" target="_blank" href="https://www.ubuntu.com/">Ubuntu</a> には最初からPythonがインストールされており、そのまま利用可能です。<br>しかし、このPython は、 OS がさまざまな機能を提供するために使用しています。ユーザが勝手にパッケージを導入したりすると、 OS の安定性を損なうことも考えられますので、別途、あたらしいPythonをインストールするのが一般的です。<br><a rel="noopener" target="_blank" href="https://www.python.jp/install/ubuntu/index.html">https://www.python.jp/install/ubuntu/index.html</a></p>
</blockquote>



<p class="wp-block-paragraph">先ずは、Python環境を整えます。<br>Python 3.13.7 を /usr/local/ へ入れます。<br>Sirilをソースから構築し、Python3.13の仮想環境を作り、Siril Pythonスクリプトを動かします。</p>


<a rel="noopener" target="_blank" href="https://www.python.jp/install/ubuntu/index.html" title="Ubuntu環境のPython - python.jp" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/ade0bd68cc9e80550d1cb0971edbaa7b.png" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Ubuntu環境のPython &#8211; python.jp</div><div class="blogcard-snippet external-blogcard-snippet">Ubuntu には最初からPythonがインストールされており、そのまま利用可能です。 しかし、このPython は、 OS がさまざまな機能を提供するために使用しています。ユーザが勝手にパッケージを導入したりすると、 OS の安定性を損な&#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://www.python.jp/install/ubuntu/index.html" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">www.python.jp</div></div></div></div></a>

<a target="_self" href="https://globe3.ddns.net/wp/python-on-ubuntu-siril-1-4-0-beta2/" title="Siril 1.4.x で Python を使うために" class="blogcard-wrap internal-blogcard-wrap a-wrap cf"><div class="blogcard internal-blogcard ib-left cf"><div class="blogcard-label internal-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail internal-blogcard-thumbnail"><img loading="lazy" decoding="async" width="160" height="90" src="https://globe3.ddns.net/wp/wp-content/uploads/2025/05/DSA_star-Reduction-py-160x90.jpg" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" srcset="https://globe3.ddns.net/wp/wp-content/uploads/2025/05/DSA_star-Reduction-py-160x90.jpg 160w, https://globe3.ddns.net/wp/wp-content/uploads/2025/05/DSA_star-Reduction-py-120x68.jpg 120w, https://globe3.ddns.net/wp/wp-content/uploads/2025/05/DSA_star-Reduction-py-320x180.jpg 320w" sizes="(max-width: 160px) 100vw, 160px" /></figure><div class="blogcard-content internal-blogcard-content"><div class="blogcard-title internal-blogcard-title">Siril 1.4.x で Python を使うために</div><div class="blogcard-snippet internal-blogcard-snippet">Ubuntu24にインストールした、Siril 1.4.0-beta2で Python を使います。Python仮想環境を指定して、活性化させSirilを起動すると、Siril Pythonモジュールがインストールされ、Pythonスクリプトが使えます。</div></div><div class="blogcard-footer internal-blogcard-footer cf"><div class="blogcard-site internal-blogcard-site"><div class="blogcard-favicon internal-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://globe3.ddns.net/wp" alt="" class="blogcard-favicon-image internal-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain internal-blogcard-domain">globe3.ddns.net</div></div><div class="blogcard-date internal-blogcard-date"><div class="blogcard-post-date internal-blogcard-post-date">2025.05.11</div></div></div></div></a>

<a rel="noopener" target="_blank" href="https://peps.python.org/pep-0668" title="PEP 668 – Marking Python base environments as “externally managed” | peps.python.org" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/9274df3cc110da1ab8e804360cf1839e.png" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">PEP 668 – Marking Python base environments as “externally managed” | peps.python.org</div><div class="blogcard-snippet external-blogcard-snippet">A long-standing practical problem for Python users has been conflicts between OS package managers and Python-specific pa&#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://peps.python.org/pep-0668/" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">peps.python.org</div></div></div></div></a>


<p class="wp-block-paragraph">参照URL<br><a rel="noopener" target="_blank" href="https://qiita.com/keith_campbell/items/e7dc4afc44527b802f6e">https://qiita.com/keith_campbell/items/e7dc4afc44527b802f6e</a><br><a rel="noopener" target="_blank" href="https://qiita.com/AzukiImo/items/5c6dd7e870c9965e41f3">https://qiita.com/AzukiImo/items/5c6dd7e870c9965e41f3</a><br><a rel="noopener" target="_blank" href="https://zenn.dev/eng_ryosan/articles/a635346a3123d3">https://zenn.dev/eng_ryosan/articles/a635346a3123d3</a><br></p>



<p class="wp-block-paragraph">Siril Appimage を動かすには、Ubuntu 24では、&#8221;libfuse2t64&#8243; が必要です。</p>



<p class="wp-block-paragraph">ソースからSiril を構築して、β版も使えます。</p>


<a target="_self" href="https://globe3.ddns.net/wp/try-siril-development-edition-1-4-0/" title="Siril 開発版を試してみよう" class="blogcard-wrap internal-blogcard-wrap a-wrap cf"><div class="blogcard internal-blogcard ib-left cf"><div class="blogcard-label internal-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail internal-blogcard-thumbnail"><img loading="lazy" decoding="async" width="160" height="90" src="https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1-160x90.jpg" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" srcset="https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1-160x90.jpg 160w, https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1-300x169.jpg 300w, https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1-120x68.jpg 120w, https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1-320x180.jpg 320w, https://globe3.ddns.net/wp/wp-content/uploads/2025/04/Siril-1.4.0-beta1.jpg 702w" sizes="(max-width: 160px) 100vw, 160px" /></figure><div class="blogcard-content internal-blogcard-content"><div class="blogcard-title internal-blogcard-title">Siril 開発版を試してみよう</div><div class="blogcard-snippet internal-blogcard-snippet">Siril開発版が使えます。SPCC、GHS、モザイクに有用なプレートソルビングの歪み補正が使えます。</div></div><div class="blogcard-footer internal-blogcard-footer cf"><div class="blogcard-site internal-blogcard-site"><div class="blogcard-favicon internal-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://globe3.ddns.net/wp" alt="" class="blogcard-favicon-image internal-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain internal-blogcard-domain">globe3.ddns.net</div></div><div class="blogcard-date internal-blogcard-date"><div class="blogcard-post-date internal-blogcard-post-date">2025.04.18</div></div></div></div></a>


<p class="wp-block-paragraph">Sirilを起動すると、Python仮想環境が作られます。</p>



<pre class="wp-block-code"><code>Last available version: 1.4.0-beta3
log: Preparing python virtual environment: /home/USRNAME/.local/share/siril/venv.
log: Checking the python module is up-to-date...
log: Installing / updating python module in the background. This may take a few seconds...
log: Repository cloned successfully!
Processing /home/USERNAME/.local/share/siril/.python_module
log: Repository cloned successfully!</code></pre>



<p class="wp-block-paragraph">Siril Python スクリプトを導入すると、<br>/home/USERNAME/.local/share/siril-scripts/preprocessing/<br>などに置かれます。</p>



<h2 class="wp-block-heading">Cosmic Clarity Suite Siril Pythonスクリプトを English 環境で動かす。</h2>



<div class="wp-block-cocoon-blocks-icon-box common-icon-box block-box information-box">
<p class="wp-block-paragraph">Cosmic Clarity Suite Siril Pythonスクリプトは、Ubuntu24では システムの文字セットがJapaneseだと動きませんでした。</p>
</div>


<a target="_self" href="https://globe3.ddns.net/wp/astronomical-image-processing-flow-siril-1-4-cosmic-clarity-suite-6-3-ngc-925-ngc7814-2024/" title="Siril と Cosmic Clarity Suite, 天体画像処理の流れ" class="blogcard-wrap internal-blogcard-wrap a-wrap cf"><div class="blogcard internal-blogcard ib-left cf"><div class="blogcard-label internal-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail internal-blogcard-thumbnail"><img loading="lazy" decoding="async" width="160" height="90" src="https://globe3.ddns.net/wp/wp-content/uploads/2025/06/siril1.4.3-setiastro-cosmic-clarity-160x90.jpg" class="blogcard-thumb-image internal-blogcard-thumb-image wp-post-image" alt="" srcset="https://globe3.ddns.net/wp/wp-content/uploads/2025/06/siril1.4.3-setiastro-cosmic-clarity-160x90.jpg 160w, https://globe3.ddns.net/wp/wp-content/uploads/2025/06/siril1.4.3-setiastro-cosmic-clarity-120x68.jpg 120w, https://globe3.ddns.net/wp/wp-content/uploads/2025/06/siril1.4.3-setiastro-cosmic-clarity-320x180.jpg 320w" sizes="(max-width: 160px) 100vw, 160px" /></figure><div class="blogcard-content internal-blogcard-content"><div class="blogcard-title internal-blogcard-title">Siril と Cosmic Clarity Suite, 天体画像処理の流れ</div><div class="blogcard-snippet internal-blogcard-snippet">Siril-1.4.0, StarNet, Cosmic Clarity SuiteVersion 6.3 を用いた天体画像処理の流れ。NGC 925、NGC7814を撮影、画像処理しました。</div></div><div class="blogcard-footer internal-blogcard-footer cf"><div class="blogcard-site internal-blogcard-site"><div class="blogcard-favicon internal-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://globe3.ddns.net/wp" alt="" class="blogcard-favicon-image internal-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain internal-blogcard-domain">globe3.ddns.net</div></div><div class="blogcard-date internal-blogcard-date"><div class="blogcard-post-date internal-blogcard-post-date">2025.06.03</div></div></div></div></a>


<p class="wp-block-paragraph">Franklin Marekさんに問い合わせすると、Linux では nividia のみ使えるそうです。<br>IntelやAMD製GPUユニットが使えるように、リクエストしてみようかな。</p>



<h2 class="wp-block-heading">Teensyduino シリアル通信 : Althiba 3 接続</h2>



<p class="wp-block-paragraph">AlThiba (マチナカリモート天文台製のコントローラー)は、&#8221;TeenAstro Mount&#8221;で動かします。<br>Teen Astro Mount INDI Driver&#8221;は、&#8221;indi-bin&#8221;に含まれています。</p>



<p class="wp-block-paragraph">Althiba3 をUSB接続し、logを見ると、cdc acm ドライバで動かすようです。<br>さらに、ModemManager がデバイスを制御しようとしている。</p>



<pre class="wp-block-code"><code>
kernel: usb 1-1: new high-speed USB device number 10 using xhci_hcd
kernel: usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x3 has invalid maxpacket 64
kernel: usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x84 has invalid maxpacket 64
kernel: usb 1-1: New USB device found, idVendor=16c0, idProduct=0483, bcdDevice= 2.79
kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-1: Product: USB Serial
kernel: usb 1-1: Manufacturer: Teensyduino
kernel: usb 1-1: SerialNumber: 7939030
kernel: cdc_acm 1-1:1.0: ttyACM0: USB ACM device
mtp-probe: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
mtp-probe: bus: 1, device: 10 was not an MTP device
snapd&#91;984]: hotplug.go:206: hotplug device add event ignored, enable experimental.hotplug
mtp-probe: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
mtp-probe: bus: 1, device: 10 was not an MTP device
ModemManager&#91;1143]: &lt;msg&gt; &#91;base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1': not supported by any plugin</code></pre>



<pre class="wp-block-code"><code>ModemManagerを止める？
systemctl stop ModemManager
それよりもModemManagerを削除しよう。モデムは使わない。。。
$ sudo apt remove modemmanager</code></pre>



<p class="wp-block-paragraph">/dev以下を見ると、</p>



<pre class="wp-block-code"><code>$ ls -l /dev/tty
crw-rw----   1 root   dialout 166,   0  9月 13 20:51 ttyACM0</code></pre>



<p class="wp-block-paragraph">dialoutグループで制御が出来るので、ユーザーアカウントをdialoutグループに登録します。</p>



<pre class="wp-block-code"><code>$ sudo adduser ${USER} dialout
もしくは、
S sudo usermod -a -G dialout ${USER}</code></pre>



<p class="wp-block-paragraph">KStarsを動かし、&#8221;/dev/ttyUSB0が無いよ&#8221; とエラーが表示されたならば、<br>USB接続を確認した、/dev/ttyACM0 にシンボリックシンクを作ります。<br>Ubuntu 24.04では必要ありませんでした。</p>



<pre class="wp-block-code"><code>$ sudo ln -s /dev/ttyACM0 /dev/ttyUSB0</code></pre>



<h2 class="wp-block-heading">天文機器制御 INDI library</h2>


<a rel="noopener" target="_blank" href="https://indilib.org" title="Home" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Findilib.org?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Home</div><div class="blogcard-snippet external-blogcard-snippet">INDI Library provides a framework for control and automation of astronomical instruments.</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://indilib.org/" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">indilib.org</div></div></div></div></a>

<a rel="noopener" target="_blank" href="https://indilib.org/download/ubuntu/category/3-ubuntu.html" title="Ubuntu" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Findilib.org%2Fdownload%2Fubuntu%2Fcategory%2F3-ubuntu.html?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Ubuntu</div><div class="blogcard-snippet external-blogcard-snippet">INDI Library provides a framework for control and automation of astronomical instruments.</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://indilib.org/download/ubuntu/category/3-ubuntu.html" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">indilib.org</div></div></div></div></a>


<p class="wp-block-paragraph">INDI library を使って、Althiba3, ZWO Camera, ZWO EAF を制御し、銀河などを撮像します。</p>



<pre class="wp-block-code"><code>INDI Library 安定版を入れます。
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt update
sudo apt install libindi1 indi-bin kstars-bleeding gsc
ZWOカメラを使うので、
sudo apt install indi-asi</code></pre>



<p class="wp-block-paragraph">libindi1, indi-bin は基本ドライバー、Ekos と GSCを入れます。<br>GSCは、&#8221;Hubble Space Telescope, Guide Catalog&#8221;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">恒星のカタログです。恒星の位置とその等級が含まれています。<br>ハッブル宇宙望遠鏡の運用するために、16等級よりも明るい恒星が、約1900万の恒星が登録されています。<br><a rel="noopener" target="_blank" href="https://heasarc.gsfc.nasa.gov/w3browse/all/gsc.html">https://heasarc.gsfc.nasa.gov/w3browse/all/gsc.html</a></p>
</blockquote>



<p class="wp-block-paragraph">このカタログとINDI libraryシミュレーションを用いて、星空が無くても動作確認ができます。</p>



<p class="wp-block-paragraph">別のパッケージを上書きしようとするパッケージに関するエラーが発生した場合は、</p>



<pre class="wp-block-code"><code>sudo apt-get -o Dpkg::Options::="--force-overwrite" -f install</code></pre>



<h2 class="wp-block-heading">Kstars</h2>



<p class="wp-block-paragraph">Kstarsを動かします。<br>Ekos へ機器のプロファイルと、その構成をトレインとして登録します。</p>



<p class="wp-block-paragraph">File Settings<br>撮影画像ディレクトリ、及び名前形式を決めます。</p>


<a rel="noopener" target="_blank" href="https://kstars-docs.kde.org/ja/user_manual/ekos-capture.html#file-settings" title="Capture" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fkstars-docs.kde.org%2Fja%2Fuser_manual%2Fekos-capture.html%23file-settings?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Capture</div><div class="blogcard-snippet external-blogcard-snippet"></div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://kstars-docs.kde.org/ja/user_manual/ekos-capture.html#file-settings" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">kstars-docs.kde.org</div></div></div></div></a>


<p class="wp-block-paragraph">%f (ファイル名): 拡張子を除いた .esq ファイルの名前<br>%D (日付/時刻): ファイルが保存された時刻と日付<br>%T (タイプ): フレームのタイプ (例: &#8220;Light&#8221;、&#8221;Dark &#8220;など)<br>%e (露出): 露光時間（秒）<br>%F (フィルター): 使用するフィルター名<br>%t (ターゲット): ターゲット名<br>%s (シーケンス): イメージ シーケンスの識別子。* は使用される桁数 (1 ～ 9) です。 このタグは必須であり、形式の最後の要素である必要があります。<br>サフィックス: ファイル名にシーケンス番号を追加するために使用される桁数</p>



<div class="wp-block-cocoon-blocks-blank-box-1 blank-box block-box">
<p class="wp-block-paragraph">例えば次の様に指定します。<br>Format: /%T/%t/%t_%T_%F_%e_%D<br>撮影画像名は、指定されたディレクトリに、次のディレクトリ名、ファイル名になります。<br>/Light/M1/M1_Light_HEUIB-II_180_secs_2025-09-15T23-51-16_001.fits</p>
</div>



<h2 class="wp-block-heading">Ekos Auto Focus 設定</h2>



<p class="wp-block-paragraph">EAFの働きが今ひとつなので、ドキュメントを見てみよう。</p>


<a rel="noopener" target="_blank" href="https://docs.kde.org/trunk5/en/kstars/kstars/ekos-focus.html" title="404 Not Found" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fdocs.kde.org%2Ftrunk5%2Fen%2Fkstars%2Fkstars%2Fekos-focus.html?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">404 Not Found</div><div class="blogcard-snippet external-blogcard-snippet"></div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://docs.kde.org/trunk5/en/kstars/kstars/ekos-focus.html" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">docs.kde.org</div></div></div></div></a>


<p class="wp-block-paragraph">動作原理</p>



<p class="wp-block-paragraph"><strong>Linear 1 Pass</strong>:<br>EkosがVカーブを確立し、データに曲線を当てはめて焦点解を求めます。その後、計算された最小値へ移動します<br>　アルゴリズムはフォーカサーのバックラッシュを補正します。<br>　アルゴリズムは高速で、1回のパスで最適焦点位置を特定します。</p>



<p class="wp-block-paragraph">フォーカサーが再現性のある動作（位置Xへの移動指令時に常に同一位置に移動する）を示す場合、このアルゴリズムが最適です。</p>



<p class="wp-block-paragraph"><strong>Linear</strong>:<br>線形アルゴリズムでは、Ekosは開始点から外側へ移動し、最適焦点を経由して規則的なデータポイントを採取しながら内側へ移動し、さらに内側へ進みV字曲線を描画します。その後、データポイントに二次曲線をフィットさせ、最適焦点を算出します。<br>次に再び最適焦点点を越えて外側へ移動し、ステップサイズを半分にして再度内側へ移動し、第二パスを実行します。第1パスで描かれた曲線に沿い、最小HFR値を検出します。HFR測定値のランダム性を考慮し、許容誤差を用いて最適焦点の決定を支援します。</p>



<p class="wp-block-paragraph">　フォーカサーのバックラッシュを補正します。<br>　アルゴリズムは低速で、最適焦点の特定に2パスを要します。<br>　アルゴリズムは1回目で曲線フィッティングを用いて最適焦点位置を特定し、<br>　2回目では許容誤差を用いて、このHFR値に可能な限り接近して停止を試みます。</p>



<p class="wp-block-paragraph">フォーカサーの動作が不安定な場合（例：フォーカス位置への移動させた時に、実際の位置に変動がある場合）、このアルゴリズムは変動に対する許容値を内蔵しているため最適です。</p>



<ul class="wp-block-list">
<li>Donut Buster (食べられるドーナツを防ぐではなく、環状の星像を防ぎます)
<ul class="wp-block-list">
<li>Time Dilation x:　オートフォーカス実行時にデータポイントごとに露出時間を変える。<br>焦点が合ってないので、HFRは大きくなり、ピーク強度は低い。<br>数値を増やして、背景に埋もれることを防げる。</li>



<li>Outlier Rejection: V曲線の数値から外れた場合を除く。数値を高くしないのが良い？</li>
</ul>
</li>



<li>Scan for Start Position
<ul class="wp-block-list">
<li><br></li>
</ul>
</li>
</ul>



<p class="wp-block-paragraph">EAFの働きが今ひとつなので、ソースを見てみよう。</p>



<p class="wp-block-paragraph"><a rel="noopener" target="_blank" href="https://github.com/KDE/kstars">https://github.com/KDE/kstars</a><br><a rel="noopener" target="_blank" href="https://github.com/KDE/kstars/tree/master/kstars/ekos/focus">https://github.com/KDE/kstars/tree/master/kstars/ekos/focus</a></p>



<p class="wp-block-paragraph">kstars/ekos/focus</p>



<p class="wp-block-paragraph">Focus Process</p>



<h2 class="wp-block-heading">PHD2: Ubuntu 24.04 + PHD2 v2.6.13</h2>


<a rel="noopener" target="_blank" href="https://openphdguiding.org" title="Open PHD Guiding" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fopenphdguiding.org?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">Open PHD Guiding</div><div class="blogcard-snippet external-blogcard-snippet"></div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://openphdguiding.org" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">openphdguiding.org</div></div></div></div></a>


<p class="wp-block-paragraph">Download -&gt; Building PHD2 on Linux<br>こちらを参考にソースから構築します。</p>


<a rel="noopener" target="_blank" href="https://github.com/OpenPHDGuiding/phd2/wiki/BuildingPHD2OnLinux" title="BuildingPHD2OnLinux" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://globe3.ddns.net/wp/wp-content/uploads/cocoon-resources/blog-card-cache/9effcabc238dbe818bc2d2071af0722d.jpg" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">BuildingPHD2OnLinux</div><div class="blogcard-snippet external-blogcard-snippet">PHD2 Guiding. Contribute to OpenPHDGuiding/phd2 development by creating an account on GitHub.</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://github.com/OpenPHDGuiding/phd2/wiki/BuildingPHD2OnLinux" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">github.com</div></div></div></div></a>


<p class="wp-block-paragraph">依存関係のパッケージをインストール</p>



<p class="wp-block-paragraph">INDI Libraryも必要になります。</p>



<pre class="wp-block-code"><code>sudo apt install build-essential git cmake pkg-config libwxgtk3.2-dev \
   wx-common wx3.2-i18n libindi-dev libnova-dev gettext zlib1g-dev libx11-dev \
   libcurl4-gnutls-dev libopencv-dev libeigen3-dev libgtest-dev</code></pre>



<h3 class="wp-block-heading">PHD2 v2.6.24 dev1 を使う</h3>



<p class="wp-block-paragraph">PHD2 v2.6.24 dev1 では、<br><a rel="noopener" target="_blank" href="https://github.com/OpenPHDGuiding/phd2/issues/1441">https://github.com/OpenPHDGuiding/phd2/issues/1441</a><br>こちらのエラーが出ました。</p>



<pre class="wp-block-code"><code>echo 'remove_definitions(-DHAVE_QHY_CAMERA=1)' &gt;&gt; thirdparty/thirdparty.cmake</code></pre>



<p class="wp-block-paragraph">tmpディレクトリを作り直し、</p>



<pre class="wp-block-code"><code>mkdir -p tmp
cd tmp
cmake ..
make
sudo make install</code></pre>



<h3 class="wp-block-heading">PHD2 v2.6.13 を使う</h3>



<p class="wp-block-paragraph">PHD2 v2.6.13 のソースを入手し make していきます。</p>



<pre class="wp-block-code"><code>git clone https://github.com/OpenPHDGuiding/phd2.git
cd phd2
mkdir -p tmp
cd tmp
cmake ..
make
sudo make install</code></pre>



<p class="wp-block-paragraph">PHD2 v2.6.13 では、<br>「ファイルが無いよ」とエラーが出たので、適宜、必要なディレクトリにコピーしました。</p>



<pre class="wp-block-code"><code>does not exist
Visualization.htm
Trouble_shooting.htm
Glossary.html
Tutorials.htm</code></pre>



<p class="wp-block-paragraph">cmake, make, sudo make install 構築しインストールしたプログラム等を削除するには、<br>インストールしたファイルリストがビルドディレクトリに &#8220;install_manifest.txt&#8221; に書き出されます。</p>



<pre class="wp-block-code"><code>$ xargs sudo rm -rf &lt; install_manifest.txt</code></pre>



<p class="wp-block-paragraph">PHD2 v2.6.12 の場合も同じように構築、インストールし、ログを保存しました。<br>古いソースは、手元に残すべきと思いました。</p>



<p class="wp-block-paragraph">もしも、下記のエラーが表示されたならば、cfitsioライブラリがインストールされていません。</p>



<pre class="wp-block-code"><code>CMake Error in contributions/MPI_IS_gaussian_process/CMakeLists.txt:
  Found relative path while evaluating include directories of
  "GuidePerformanceEval":

    "CFITSIO_INCLUDE_DIR-NOTFOUND"</code></pre>



<p class="wp-block-paragraph">次のコマンドで、libcfitsioライブラリを入れます。</p>



<pre class="wp-block-code"><code>$ sudo apt-get install libcfitsio-dev</code></pre>



<h3 class="wp-block-heading">PHD2 v2.6.24 dev1 インストールログ</h3>



<pre class="wp-block-code"><code>$ sudo make install
&#91;sudo: authenticate] パスワード:          
&#91;  4%] Built target usb_openphd
&#91;  4%] Performing update step for 'indi'
-- Already at requested ref: 6aa360543313c9e00819148da9df15647ffa7996
&#91;  5%] No patch step for 'indi'
&#91;  5%] Performing configure step for 'indi'
-- Using bundled httplib
-- Using bundled json library
-- Found libnova: /usr/lib/x86_64-linux-gnu/libnova.so
-- Building INDI Client
-- The following REQUIRED packages have been found:

 * Nova, A general purpose, double precision, Celestial Mechanics, Astrometry and Astrodynamics library, &lt;http://libnova.sourceforge.net>
   Provides INDI with astrodynamics library.
 * Threads
 * ZLIB

-- The following components are going to be built:
-- ## INDI Client
-- Configuring done (0.1s)
-- Generating done (0.0s)
-- Build files have been written to: /home/USERNAME/phd2/tmp/indi-prefix/src/indi-build
&#91;  6%] Performing build step for 'indi'
&#91; 36%] Built target indicore
&#91; 83%] Built target indidevice
&#91; 86%] Built target indiabstractclient
&#91; 93%] Built target sockets
&#91; 96%] Built target indiclient_OBJECT
&#91;100%] Built target indiclientstatic
&#91;  6%] Performing install step for 'indi'
&#91; 36%] Built target indicore
&#91; 83%] Built target indidevice
&#91; 86%] Built target indiabstractclient
&#91; 93%] Built target sockets
&#91; 96%] Built target indiclient_OBJECT
&#91;100%] Built target indiclientstatic
Install the project...
-- Install configuration: ""
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indimacros.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiapi.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indidevapi.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiutility.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/lilxml.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/base64.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indicom.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/sharedblob.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/libastro.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indibase.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indibasetypes.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/basedevice.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/parentdevice.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indistandardproperty.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiproperties.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiproperty.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertybasic.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertyview.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertytext.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertynumber.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertyswitch.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertylight.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indipropertyblob.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiwidgetview.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiwidgettraits.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/abstractbaseclient.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/baseclient.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/lib/libindiclient.a
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/inicpp.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indiversion.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/httplib.h
-- Up-to-date: /home/USERNAME/phd2/tmp/libindi/include/libindi/indijson.hpp
&#91;  6%] Completed 'indi'
&#91;  7%] Built target indi
&#91;  8%] Built target OpenSSAG
&#91;  8%] Built target MPIIS_GP_TOOLS
&#91; 10%] Built target MPIIS_GP
&#91; 10%] Built target GPGuider
&#91; 10%] Built target en_EN_html
&#91; 12%] Built target ar_LY_translation
&#91; 13%] Built target ca_ES_translation
&#91; 14%] Built target cs_CZ_html
&#91; 15%] Built target cs_CZ_translation
&#91; 17%] Built target de_DE_translation
&#91; 19%] Built target es_ES_translation
&#91; 19%] Built target fr_FR_html
&#91; 21%] Built target fr_FR_translation
&#91; 22%] Built target gl_ES_translation
&#91; 24%] Built target it_IT_translation
&#91; 24%] Built target ja_JP_html
&#91; 26%] Built target ja_JP_translation
&#91; 27%] Built target ko_KR_translation
&#91; 28%] Built target nb_NO_translation
&#91; 30%] Built target pl_PL_translation
&#91; 31%] Built target pt_BR_translation
&#91; 32%] Built target ro_RO_translation
&#91; 33%] Built target ru_RU_html
&#91; 34%] Built target ru_RU_translation
&#91; 36%] Built target uk_UA_translation
&#91; 38%] Built target zh_CN_translation
&#91; 38%] Built target zh_TW_html
&#91; 40%] Built target zh_TW_translation
&#91; 93%] Built target phd2
&#91; 93%] Built target gtest
&#91; 94%] Built target gmock
&#91; 95%] Built target gmock_main
&#91; 96%] Built target gtest_main
&#91; 97%] Built target GaussianProcessTest
&#91; 98%] Built target MathToolboxTest
&#91; 99%] Built target GPGuiderTest
&#91; 99%] Built target GuidePerformanceTest
&#91;100%] Built target GuidePerformanceEval
Install the project...
-- Install configuration: "Release"
-- Up-to-date: /usr/include
-- Installing: /usr/include/gmock
-- Installing: /usr/include/gmock/gmock-more-actions.h
-- Installing: /usr/include/gmock/gmock.h
-- Installing: /usr/include/gmock/gmock-more-matchers.h
-- Installing: /usr/include/gmock/gmock-spec-builders.h
-- Installing: /usr/include/gmock/gmock-nice-strict.h
-- Installing: /usr/include/gmock/gmock-actions.h
-- Installing: /usr/include/gmock/gmock-function-mocker.h
-- Installing: /usr/include/gmock/internal
-- Installing: /usr/include/gmock/internal/custom
-- Installing: /usr/include/gmock/internal/custom/gmock-port.h
-- Installing: /usr/include/gmock/internal/custom/gmock-generated-actions.h
-- Installing: /usr/include/gmock/internal/custom/README.md
-- Installing: /usr/include/gmock/internal/custom/gmock-matchers.h
-- Installing: /usr/include/gmock/internal/gmock-pp.h
-- Installing: /usr/include/gmock/internal/gmock-port.h
-- Installing: /usr/include/gmock/internal/gmock-internal-utils.h
-- Installing: /usr/include/gmock/gmock-cardinalities.h
-- Installing: /usr/include/gmock/gmock-matchers.h
-- Installing: /usr/lib/x86_64-linux-gnu/libgmock.a
-- Installing: /usr/lib/x86_64-linux-gnu/libgmock_main.a
-- Installing: /usr/lib/x86_64-linux-gnu/pkgconfig/gmock.pc
-- Installing: /usr/lib/x86_64-linux-gnu/pkgconfig/gmock_main.pc
-- Old export file "/usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets.cmake" will be replaced.  Removing files &#91;/usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets-none.cmake].
-- Installing: /usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets.cmake
-- Installing: /usr/lib/x86_64-linux-gnu/cmake/GTest/GTestTargets-release.cmake
-- Installing: /usr/lib/x86_64-linux-gnu/cmake/GTest/GTestConfigVersion.cmake
-- Installing: /usr/lib/x86_64-linux-gnu/cmake/GTest/GTestConfig.cmake
-- Up-to-date: /usr/include
-- Up-to-date: /usr/include/gtest
-- Installing: /usr/include/gtest/gtest-spi.h
-- Installing: /usr/include/gtest/gtest_pred_impl.h
-- Installing: /usr/include/gtest/gtest-assertion-result.h
-- Installing: /usr/include/gtest/gtest-typed-test.h
-- Installing: /usr/include/gtest/gtest-death-test.h
-- Installing: /usr/include/gtest/gtest-param-test.h
-- Installing: /usr/include/gtest/gtest_prod.h
-- Installing: /usr/include/gtest/gtest-message.h
-- Up-to-date: /usr/include/gtest/internal
-- Installing: /usr/include/gtest/internal/gtest-param-util.h
-- Installing: /usr/include/gtest/internal/gtest-string.h
-- Installing: /usr/include/gtest/internal/gtest-death-test-internal.h
-- Installing: /usr/include/gtest/internal/gtest-port-arch.h
-- Up-to-date: /usr/include/gtest/internal/custom
-- Installing: /usr/include/gtest/internal/custom/gtest-port.h
-- Installing: /usr/include/gtest/internal/custom/gtest.h
-- Installing: /usr/include/gtest/internal/custom/gtest-printers.h
-- Installing: /usr/include/gtest/internal/custom/README.md
-- Installing: /usr/include/gtest/internal/gtest-port.h
-- Installing: /usr/include/gtest/internal/gtest-internal.h
-- Installing: /usr/include/gtest/internal/gtest-filepath.h
-- Installing: /usr/include/gtest/internal/gtest-type-util.h
-- Installing: /usr/include/gtest/gtest.h
-- Installing: /usr/include/gtest/gtest-printers.h
-- Installing: /usr/include/gtest/gtest-test-part.h
-- Installing: /usr/include/gtest/gtest-matchers.h
-- Installing: /usr/lib/x86_64-linux-gnu/libgtest.a
-- Installing: /usr/lib/x86_64-linux-gnu/libgtest_main.a
-- Installing: /usr/lib/x86_64-linux-gnu/pkgconfig/gtest.pc
-- Installing: /usr/lib/x86_64-linux-gnu/pkgconfig/gtest_main.pc
-- Installing: /usr/share/phd2/PHD2GuideHelp.zip
-- Installing: /usr/share/locale/ar_LY/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/ca_ES/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/cs_CZ/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/phd2/locale/cs_CZ/PHD2GuideHelp.zip
-- Installing: /usr/share/locale/de_DE/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/es_ES/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/fr_FR/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/phd2/locale/fr_FR/PHD2GuideHelp.zip
-- Installing: /usr/share/locale/gl_ES/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/it_IT/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/ja_JP/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/phd2/locale/ja_JP/PHD2GuideHelp.zip
-- Installing: /usr/share/locale/ko_KR/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/nb_NO/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/pl_PL/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/pt_BR/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/ro_RO/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/ru_RU/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/phd2/locale/ru_RU/PHD2GuideHelp.zip
-- Installing: /usr/share/locale/uk_UA/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/zh_CN/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/locale/zh_TW/LC_MESSAGES/phd2.mo
-- Installing: /usr/share/phd2/locale/zh_TW/PHD2GuideHelp.zip
-- Installing: /usr/bin/phd2.bin
-- Set non-toolchain portion of runtime path of "/usr/bin/phd2.bin" to ""
-- Installing: /usr/bin/phd2
-- Installing: /usr/lib/phd2/libtoupcam.so
-- Installing: /usr/lib/phd2/libogmacam.so
-- Installing: /usr/lib/phd2/libSVBCameraSDK.so
-- Installing: /usr/lib/phd2/libPlayerOneCamera.so
-- Installing: /usr/lib/phd2/libPlayerOneCamera.so.3
-- Installing: /usr/lib/phd2/libPlayerOneCamera.so.3.10
-- Installing: /usr/lib/phd2/libPlayerOneCamera.so.3.10.0
-- Installing: /usr/share/pixmaps/phd2.png
-- Installing: /usr/share/applications/phd2.desktop
-- Installing: /usr/share/metainfo/phd2.appdata.xml</code></pre>



<h2 class="wp-block-heading">余談</h2>



<p class="wp-block-paragraph">何度もインストールを行うのでメモを残します。システムを壊して、再インストール時にも役立ちます。もちろん&#8221;.ファイル&#8221;を含めたバックアップは必要です。</p>



<p class="wp-block-paragraph">天体撮影に使うノートPCは、いい加減なジャンクPCを使ってます。元がジャンクなので壊れそう。そろそろ買い換えと思い、量販店へ行って実機を見回すと、スリムなノートPCが並んでいる。<br>裏側のネジ数本外し、メモリやSSDを簡単に交換出来なさそう。交換に困る前に、現行物を入手しようか。。。いや、、もぅ困っています。<br></p>



<h2 class="wp-block-heading">ホームディレクトリを残して、再インストール</h2>



<p class="wp-block-paragraph">「推奨するプロプライエタリなソフトウェア」では、&#8221;グラフィックス&#8221;、&#8221;wi-Fi&#8221;、&#8221;メディアフォーマット&#8221;を選択しない。<br>選択すると以前のファイルシステムをフォーマットせずにインストール選択へ進めないようです。</p>



<p class="wp-block-paragraph">ブートローダーをインストールするデバイスを、先ずは選択する。<br>自動で /boot/efi が設定されるようです。ところが、現状でこちらのPC環境では、インストールが完了しません。</p>



<h2 class="wp-block-heading">Intel CPU内蔵 GPUドライバ</h2>



<p class="wp-block-paragraph">UbuntuでIntel GPUを使うための案内ですが、こちらでは全てを試していません。でもGPUを使って、天文画像処理を行いたい。</p>


<a rel="noopener" target="_blank" href="https://dgpu-docs.intel.com/driver/client/overview.html" title="https://dgpu-docs.intel.com/driver/client/overview.html" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fdgpu-docs.intel.com%2Fdriver%2Fclient%2Foverview.html?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">https://dgpu-docs.intel.com/driver/client/overview.html</div><div class="blogcard-snippet external-blogcard-snippet"></div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://dgpu-docs.intel.com/driver/client/overview.html" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">dgpu-docs.intel.com</div></div></div></div></a>


<p class="wp-block-paragraph">ローカルパッケージインデックスを更新し、ソフトウェアリポジトリを管理するためのパッケージをインストールします。</p>



<pre class="wp-block-code"><code>sudo apt-get update
sudo apt-get install -y software-properties-common</code></pre>



<p class="wp-block-paragraph">intel-graphics PPAを追加</p>



<pre class="wp-block-code"><code>sudo add-apt-repository -y ppa:kobuk-team/intel-graphics</code></pre>



<p class="wp-block-paragraph">コンピューティング関連のパッケージをインストールします。</p>



<pre class="wp-block-code"><code>sudo apt-get install -y libze-intel-gpu1 libze1 intel-metrics-discovery intel-opencl-icd clinfo intel-gsc</code></pre>



<p class="wp-block-paragraph">メディア関連のパッケージをインストールしてください。</p>



<pre class="wp-block-code"><code>sudo apt-get install -y intel-media-va-driver-non-free libmfx-gen1 libvpl2 libvpl-tools libva-glx2 va-driver-all vainfo</code></pre>



<p class="wp-block-paragraph">PyTorchを使用する場合は、追加でlibze-devとintel-oclocをインストールしてください</p>



<pre class="wp-block-code"><code>sudo apt-get install -y libze-dev intel-ocloc</code></pre>



<p class="wp-block-paragraph">ハードウェアレイトレーシングのサポートを有効にしたい場合は、追加で libze-intel-gpu-raytracing をインストール</p>



<pre class="wp-block-code"><code>sudo apt-get install -y libze-intel-gpu-raytracing</code></pre>



<p class="wp-block-paragraph">カーネルと計算ドライバーがインストールされ正常に動作していることを確認するには、clinfo を実行してください</p>



<pre class="wp-block-code"><code>clinfo | grep "Device Name"</code></pre>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Intelグラフィックス製品のデバイス名が表示されているはずです。表示されない場合は、/dev/dri/renderD* へのアクセス権限があることを確認してください。通常、これにはユーザーが render グループに属している必要があります：</p>
</blockquote>



<pre class="wp-block-code"><code>$ ls -l /dev/dri/render*
crw-rw----+ 1 root render 226, 128 10月  1 14:52 /dev/dri/renderD128</code></pre>



<pre class="wp-block-code"><code>sudo gpasswd -a ${USER} render
newgrp render</code></pre>


<a rel="noopener" target="_blank" href="https://qiita.com/yamakenjp/items/36c28163a40445146f7f" title="intel Arc GPUでHWEncode環境 - Qiita" class="blogcard-wrap external-blogcard-wrap a-wrap cf"><div class="blogcard external-blogcard eb-left cf"><div class="blogcard-label external-blogcard-label"><span class="fa"></span></div><figure class="blogcard-thumbnail external-blogcard-thumbnail"><img loading="lazy" decoding="async" src="https://s.wordpress.com/mshots/v1/https%3A%2F%2Fqiita.com%2Fyamakenjp%2Fitems%2F36c28163a40445146f7f?w=320&#038;h=180" alt="" class="blogcard-thumb-image external-blogcard-thumb-image" width="320" height="180" /></figure><div class="blogcard-content external-blogcard-content"><div class="blogcard-title external-blogcard-title">intel Arc GPUでHWEncode環境 &#8211; Qiita</div><div class="blogcard-snippet external-blogcard-snippet">さくらのアドベントカレンダー2022 20日目の記事です。 どうも、さくらインターネット やまけんです。 2日目で さくらのクラウドでUniFi Network Applicationを動かす こちらの紹介をしましたが、今度はGPUでのハー&#8230;</div></div><div class="blogcard-footer external-blogcard-footer cf"><div class="blogcard-site external-blogcard-site"><div class="blogcard-favicon external-blogcard-favicon"><img loading="lazy" decoding="async" src="https://www.google.com/s2/favicons?domain=https://qiita.com/yamakenjp/items/36c28163a40445146f7f" alt="" class="blogcard-favicon-image external-blogcard-favicon-image" width="16" height="16" /></div><div class="blogcard-domain external-blogcard-domain">qiita.com</div></div></div></div></a>]]></content:encoded>
					
					<wfw:commentRss>https://globe3.ddns.net/wp/astronomy-ubuntu-pc-setup/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
