Bug#930565: dev-ref: should use distro-info instead of hardcoding version numbers

2022-03-30 Thread kaliko
On 3/29/22 11:00, kaliko wrote: Alright then here is a patch using distro-info (forking currently fails at least with my account on salsa). Humm, error between keyboard and chair actually… Here is the salsa "Merge request":

Bug#930565: dev-ref: should use distro-info instead of hardcoding version numbers

2022-03-29 Thread kaliko
Hi Holger, On 3/28/22 14:12, Holger Levsen wrote: On Wed, Mar 02, 2022 at 02:21:20PM +0100, kaliko wrote: On Sat, 15 Jun 2019 16:26:33 + Holger Levsen wrote: […] and then for bullseye we should use distro-info(-data). (wondering how to do this sensibly at run time and not at build

Bug#930565: dev-ref: should use distro-info instead of hardcoding version numbers

2022-03-28 Thread Holger Levsen
On Wed, Mar 02, 2022 at 02:21:20PM +0100, kaliko wrote: > On Sat, 15 Jun 2019 16:26:33 + Holger Levsen > wrote: > > […] > > and then for bullseye we should use distro-info(-data). (wondering how > > to do this sensibly at run time and not at build time...) > What is "run time" for manual

Bug#930565: dev-ref: should use distro-info instead of hardcoding version numbers

2022-03-02 Thread kaliko
On Sat, 15 Jun 2019 16:26:33 + Holger Levsen wrote: […] and then for bullseye we should use distro-info(-data). (wondering how to do this sensibly at run time and not at build time...) What is "run time" for manual (pdf, html, etc…), do you mean when the manual is actually shown in the

Bug#930565: dev-ref: should use distro-info instead of hardcoding version numbers

2019-06-15 Thread Holger Levsen
package: developers-reference severity: wishlist x-debbugs-cc: Osamu Aoki , 930...@bugs.debian.org On Sat, Jun 15, 2019 at 03:53:07PM +, Holger Levsen wrote: > Now I wonder, dies it make sense to do an upload now, for buster, and > then another upload with these numbers changed, for bullseye,