Hello Stefano,

My understanding is that bugs against backports aren't meant to be filed
in the ordinary BTS.

Xiyue has been looking for a solution for these issues and perhaps this
is a fine place to discuss them, so I'll leave this bug open.

--
Sean Whitton

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmfFpCQZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQEP7D/9tBWo9v3obn3UYTd3XYrrH sDDUnflmrzHsI1ipLX8Lom8EJ0WR9OkLngzkNgPN8n/qbPgBtAdnHzntOqZYfAiy mR1JEgSqD9gkiUOI+AFRMnUUnI5qOMRUXWR402fLk5N9YS3/AIQyGoEr0Xs235uq hBZ/HefGxXh65j7SRYWULUkFandaoOs+jaC82/Kff/nIASzaDpAJItdDHP57ZR/l +7Vq8EH1O6E5tna3O5llq7TVloMGTsgk8akOmuRaPS6aTpT+NGcrvRCE14LPpJTz S1TRTr7gAcHKcuEm/lXJzvIWWo9pmBudUoU10zHGZVZYYuyppyvcEw/rSscdVdgI y3JbOM/pKWUQldgtp5fqGgbCf/gZAfojxywAttox9SsT6VDX5msun5l+t0e7ku5Y t4NGsFqPrruCwi8Vy64SpJcfqMoUltmepKNG+Ckre9qTOWXkrn4GUSbosVCQxbmT zoTHEzjNEZsRpEFlG1a9D+q8A9hC3rwCBFnccb/FWs6FoAGHY0lgiramfLJMXlb9 nrYse7DgjwPCzW12OJO5qlg7klW3whUZxKyCkSKC/GaBYpXA0sJnuZbgwymvKnQW snMN8kQX8F2FRb0Gwmt3lLy6BXnqtyCUDfouP+vCV9GebVukFzddBBHowYBFLR05 yzU8nJhiUCRqXFa/qDfkLA==oNlU
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Us

(adding Xiyue)

On Mon 03 Mar 2025 at 08:44pm +08, Sean Whitton wrote:

Hello Stefano,

My understanding is that bugs against backports aren't meant to be filed
in the ordinary BTS.

Xiyue has been looking for a solution for these issues and perhaps this
is a fine place to discuss them, so I'll leave this bug open.

--
Sean Whitton

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello again,

On Tue, Mar 04, 2025 at 02:21:53PM -0800, Xiyue Deng wrote:

I guess you were trying to recover from a half configured state of
dpkg/apt which could add a lot of uncertainty. Can you try to downgrade Emacs to the stable versions first, install dh-elpa-helper 2.1.7, and
try to upgrade to the backports versions again?

So, to get past dependency issues, the minimal downgrade that I've found working was this:

----

$ sudo apt install -t stable emacs/stable emacs-gtk/stable emacs-common/stable

----

The postinst of emacs-bin-common (pulled in as dependency) failed like this:

----

Setting up emacs-bin-common (1:28.2+1-15+deb12u3) ...
update-alternatives: error: alternative path /usr/bin/emacsclient.emacs doesn't exist

----

*But* at that point, even with unconfigured packages around, upgrading
emacs *again* to the stable-backports version fixed all issues. Not sure
what this means in terms of upgrade path for the next stable release
though...

Thanks a lot for your help!
Cheers
--
Stefano Zacchiroli . zack@upsilon.cc . https://upsilon.cc/zack _. ^ ._
Full professor of Computer Science o o o \/|V|\/ Télécom Paris, Polytechnic Institute of Paris o o o </> <\> Co-founder & CSO Software Heritage o o o o /\|^|/\ Mastodon: https://mastodon.xyz/@zacchiro '" V "'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

On Tue 04 Mar 2025 at 11:55pm +01, Stefano Zacchiroli wrote:

Hello again,

On Tue, Mar 04, 2025 at 02:21:53PM -0800, Xiyue Deng wrote:

I guess you were trying to recover from a half configured state of
dpkg/apt which could add a lot of uncertainty. Can you try to downgrade
Emacs to the stable versions first, install dh-elpa-helper 2.1.7, and
try to upgrade to the backports versions again?

So, to get past dependency issues, the minimal downgrade that I've found working was this:

----

$ sudo apt install -t stable emacs/stable emacs-gtk/stable emacs-common/stable

Please install from stable-security, at least -- the CVEs are bad.

--
Sean Whitton

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmfHprAZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQDq4D/94VnqS/J+CKjh6Wv4A6LD2 TkJSovgZ7A18Fg9Bomsx2ZP3s/mPQAo+7j03Ccuy/sLPQgVdGNPxGmokcr1QmvuM dEYNACLZ/xeE8aUM+IBUnMZJhB9EWbJT8WmCNCvS90CNAgehknFehPARtTBsVD28 i6qglFmYeztqYMGqtIPYm2xCqSqlLcmSxi60GoDQKzmB1IJDDm7i2cfLmrZ1ZPIb CUz+6XGYrGup2e6amlUv4sOPfnF0Ekv9WDeU/yM2UXCMFdQVhYMvVA/EnqnSSdbv xLXWYinwvLfeCIPEShUsDcNz+XrFCOZDV5P5pcj1Uc82FewyRpD4YkwSQ1Tnuq1F 9607eC8g3z7VFFIwu5YKwpj4+7mwOCbUEd5PoG7VmuKVJ9dAo3uecLd8E+lvtcrl QtAP7yWfTYlntUSNxA9B6YPJn3yDjfSzlI7SYUTzSjJh7xJmUFICaj4LdX6XmjKv CnYHjlveyF166r500AyIOapfGNrmW9Mt+zsmVTDLwCpIZvqQJq3fFPaumvFSMzmK 4htd+jnFunws2f3prAdT+EEDsqBLB3DMPo7Uk7Nmze47iEmbSRd7WQOgfbP09xrd cByKewnrqBprvAGdbPUI9xFAZD0zrkAY8aqWtMAptCAsh6YSN4zOc3T69kRAgjGQ HfNcYWAh85KyTKuNdpAsWQ==jZXO
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Us

Sure. It was just a temporary downgrade to fix the postinst issue anyway.

Cheers

--
Sent from a mobile device. Please excuse my brevity, typos, and top-posting.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)