Re: opencpn problems

Micha Lenk <[email protected]> Thu, 14 May 2026 15:38:26 +0200
Newsgroups gmane.linux.debian.backports.general
Message-ID <[email protected]>
------2SFU0FJA5XZSO2V55CTOLG33R1LDUS
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi Alec,

Alec Leamas <leamas=2Ealec@gmail=2Ecom> hat am 11=2E05=2E2026 23:15 CEST g=
eschrieben:
>=20
> =20
> Dear List,=20
>=20
> I have problems with the opencpn package=2E
>=20
> Upstream released the 5=2E14 version about two months ago=2E As usual, I=
 pushed a new version to sid=2E When everything works, as it usually does, =
the sid version is migrated to testing and I can make the backports which a=
lmost all Debian users use=2E
>=20
> However, opencpn in sid has become FTBFS due to problems in the glew pac=
kage [1]=2E This problem looks complicated and not likely to be resolved sh=
ortly=2E=20
>=20
> I also have a libcxx-serial dependency to update [2]=2E This is somethin=
g I control and will do=2E
>=20
> opencpn is a leaf package without reverse deps which builds just fine ag=
ainst testing=2E Given this, would it be possible to get an exception to ma=
ke trixie and bookworm backports from sid rather than testing?
>=20
> Or, is there some other way Debian users don't have to wait for (probabl=
y) months for 5=2E14?
>=20
> I might need to make a new upload, likely after fixing libcxx-serial=2E =
But without an exception this is not a priority=2E
>=20
> Thoughts?

For now I'd prefer if we could instead invest the resource to fix the situ=
ation in sid, i=2Ee=2E help to fix the RC bug in glew so that it can cleanl=
y transition to testing before we do a backport=2E At least #1136422 on gle=
w seems to be actively worked on=2E=2E=2E

Best regards,
Micha
------2SFU0FJA5XZSO2V55CTOLG33R1LDUS
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><body><div dir=3D"auto">Hi Alec,<br><br>Alec Leamas &l=
t;leamas=2Ealec@gmail=2Ecom&gt; hat am 11=2E05=2E2026 23:15 CEST geschriebe=
n:<br>&gt; <br>&gt;=C2=A0 <br>&gt; Dear List, <br>&gt; <br>&gt; I have prob=
lems with the opencpn package=2E<br>&gt; <br>&gt; Upstream released the 5=
=2E14 version about two months ago=2E As usual, I pushed a new version to s=
id=2E When everything works, as it usually does, the sid version is migrate=
d to testing and I can make the backports which almost all Debian users use=
=2E<br>&gt; <br>&gt; However, opencpn in sid has become FTBFS due to proble=
ms in the glew package [1]=2E This problem looks complicated and not likely=
 to be resolved shortly=2E <br>&gt; <br>&gt; I also have a libcxx-serial de=
pendency to update [2]=2E This is something I control and will do=2E<br>&gt=
; <br>&gt; opencpn is a leaf package without reverse deps which builds just=
 fine against testing=2E Given this, would it be possible to get an excepti=
on to make trixie and bookworm backports from sid rather than testing?<br>&=
gt; <br>&gt; Or, is there some other way Debian users don't have to wait fo=
r (probably) months for 5=2E14?<br>&gt; <br>&gt; I might need to make a new=
 upload, likely after fixing libcxx-serial=2E But without an exception this=
 is not a priority=2E<br>&gt; <br>&gt; Thoughts?<br><br>For now I'd prefer =
if we could instead invest the resource to fix the situation in sid, i=2Ee=
=2E help to fix the RC bug in glew so that it can cleanly transition to tes=
ting before we do a backport=2E At least #1136422 on glew seems to be activ=
ely worked on=2E=2E=2E<br><br>Best regards,<br>Micha</div></body></html>
------2SFU0FJA5XZSO2V55CTOLG33R1LDUS--