Bug#1028025: hippotat shouldn't be a native package

2023-01-06 Thread Adrian Bunk
On Sat, Jan 07, 2023 at 01:11:59AM +, Ian Jackson wrote: >... > IMO It doesn't make sense to separately maintain upstream and debian > branches just to handle a usually-empty difference. I have often > integrated NMUs in packages maintained this way and it works well. >... I do not even care

Bug#1028025: hippotat shouldn't be a native package

2023-01-06 Thread Ian Jackson
Adrian Bunk writes ("Bug#1028025: hippotat shouldn't be a native package"): > I don't know what your workflow is, e.g. git-archive(1) with > export-ignore attribute for debian/ could be used to generate > the orig.tar.xz. My upstream release process does not involve

Bug#1028025: hippotat shouldn't be a native package

2023-01-06 Thread Adrian Bunk
On Fri, Jan 06, 2023 at 11:01:19AM +, Ian Jackson wrote: >... > Adrian Bunk writes ("Bug#1028025: hippotat shouldn't be a native package"): > > After reading the package description, nothing seems to make > > this package native other than the main maintai

Bug#1028025: hippotat shouldn't be a native package

2023-01-06 Thread Ian Jackson
Thanks for taking an interest in this package. Adrian Bunk writes ("Bug#1028025: hippotat shouldn't be a native package"): > After reading the package description, nothing seems to make > this package native other than the main maintainer happening > to also be a DD. >

Bug#1028025: hippotat shouldn't be a native package

2023-01-05 Thread Adrian Bunk
Source: hippotat Version: 1.1.3 Severity: important After reading the package description, nothing seems to make this package native other than the main maintainer happening to also be a DD. Please make the package non-native. There should be no downsides in practice, and it avoids weirdnesses li