[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56322: Debbug 56322, Ruby packaging issues, ping?
|
From: |
Remco van 't Veer |
|
Subject: |
bug#56322: Debbug 56322, Ruby packaging issues, ping? |
|
Date: |
Mon, 10 Oct 2022 07:05:09 +0200 |
|
User-agent: |
mu4e 1.8.9; emacs 28.1 |
Hi Maxime,
Thanks for taking a look again. I'll make a new patchset to correct the
things you mentioned.
2022/10/09 11:15, Maxime Devos:
> Otherwise, not that I know of, these patches appear
> straightforward. They might need to be done on core-updates though --
> unless this has changed, IIRC ruby-asciidoctor is deep in the package
> graph.
What's the protocol for "doing on core-updates"? I guess I can rebase
on that but who will or should pick up these patches? Is there somebody
I need to ping?
Remco
- bug#56322: Debbug 56322, Ruby packaging issues, ping?, Remco van 't Veer, 2022/10/08
- bug#56322: Debbug 56322, Ruby packaging issues, ping?, Maxime Devos, 2022/10/09
- bug#56322: Debbug 56322, Ruby packaging issues, ping?,
Remco van 't Veer <=
- bug#56322: Debbug 56322, Ruby packaging issues, ping?, Maxime Devos, 2022/10/10
- bug#56322: [PATCH core-updates 0/3] Ruby packaging issues, Remco van 't Veer, 2022/10/12
- bug#56322: [PATCH core-updates 2/3] gnu: ruby: fix unbundling of libffi for inheriting rubies, Remco van 't Veer, 2022/10/12
- bug#56322: [PATCH core-updates 1/3] gnu: ruby: trigger autotools bootstrap, Remco van 't Veer, 2022/10/12
- bug#56322: [PATCH core-updates 3/3] gnu: ruby: regenerate parse.c, Remco van 't Veer, 2022/10/12