Re: Forcing bundler to rebuild all native gems for bookworm to trixie update

To: debian-ruby@lists.debian.org
Subject: Re: Forcing bundler to rebuild all native gems for bookworm to trixie update
From: Ananthu C V <weepingclown@disroot.org>
Date: Wed, 16 Apr 2025 20:51:58 +0000
Message-id: <[🔎] 4175649A-38E3-4B36-B303-D61ACC00237C@disroot.org>
In-reply-to: <[🔎] d71e874d-febd-480b-97a8-acd17c40964b@onenetbeyond.org>
References: <[🔎] d71e874d-febd-480b-97a8-acd17c40964b@onenetbeyond.org>

Hi,

I do not know what the problem that's causing this is, but from a quick lookup it seems a "gem pristine --all" can rebuild all native extensions, if manually tracking each native gem is a concern (with bundler probably something lile "bundle exec gem pristine --all"?). I am not really aware of any side effects this would have though.

--
Best,
Ananthu

Reply to:

Follow-Ups:
- Re: Forcing bundler to rebuild all native gems for bookworm to trixie update
  - From: Pirate Praveen <praveen@onenetbeyond.org>

References:
- Forcing bundler to rebuild all native gems for bookworm to trixie update
  - From: Pirate Praveen <praveen@onenetbeyond.org>

Prev by Date: Forcing bundler to rebuild all native gems for bookworm to trixie update
Next by Date: Re: Forcing bundler to rebuild all native gems for bookworm to trixie update
Previous by thread: Forcing bundler to rebuild all native gems for bookworm to trixie update
Next by thread: Re: Forcing bundler to rebuild all native gems for bookworm to trixie update
Index(es):
- Date
- Thread