Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-15 Thread Guillem Jover
On Sun, 2023-01-15 at 11:30:25 +0100, Sven Joachim wrote: > Am 15.01.2023 um 08:41 schrieb Helge Kreutzmann: > > On Fri, Jan 13, 2023 at 10:14:24PM +0100, Sven Joachim wrote: > >> Am 13.01.2023 um 21:50 schrieb Helge Kreutzmann: > > Then this two things should be documented: > > > > 1. .asc files

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-15 Thread Sven Joachim
Hi Helge, Am 15.01.2023 um 08:41 schrieb Helge Kreutzmann: > On Fri, Jan 13, 2023 at 10:14:24PM +0100, Sven Joachim wrote: >> Am 13.01.2023 um 21:50 schrieb Helge Kreutzmann: >> > As you can see, "linuxinfo_4.1.2.orig.tar.xz.asc" is contained in the >> > .dsc file, but not in the .changes file.

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-15 Thread Helge Kreutzmann
Hello Ansgar, On Sun, Jan 15, 2023 at 10:03:33AM +0100, Ansgar wrote: > On Thu, 12 Jan 2023 11:29:53 +0100 Helge Kreutzmann wrote: > > -- Package-specific info: > > This system uses merged-usr-via-aliased-dirs, going behind dpkg's > > back, breaking its core assumptions. This can cause silent file

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-15 Thread Ansgar
Hi, On Thu, 12 Jan 2023 11:29:53 +0100 Helge Kreutzmann wrote: > -- Package-specific info: > This system uses merged-usr-via-aliased-dirs, going behind dpkg's > back, breaking its core assumptions. This can cause silent file > overwrites and disappearances, and its general tools misbehavior. >

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-14 Thread Helge Kreutzmann
Hello Sven, sorry for my slow answer. On Fri, Jan 13, 2023 at 10:14:24PM +0100, Sven Joachim wrote: > Am 13.01.2023 um 21:50 schrieb Helge Kreutzmann: > > As you can see, "linuxinfo_4.1.2.orig.tar.xz.asc" is contained in the > > .dsc file, but not in the .changes file. > > This is the opposite

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-13 Thread Sven Joachim
Am 13.01.2023 um 21:50 schrieb Helge Kreutzmann: > Hello Sven, > On Fri, Jan 13, 2023 at 09:36:47PM +0100, Sven Joachim wrote: >> Am 13.01.2023 um 21:16 schrieb Helge Kreutzmann: >> > Maybe we use the tools differently? >> > >> > Since we use source only uploads, I run: >> > dpkg-buildpackage

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-13 Thread Helge Kreutzmann
Hello Sven, On Fri, Jan 13, 2023 at 09:36:47PM +0100, Sven Joachim wrote: > Am 13.01.2023 um 21:16 schrieb Helge Kreutzmann: > > On Fri, Jan 13, 2023 at 09:05:21PM +0100, Sven Joachim wrote: > >> Am 12.01.2023 um 11:29 schrieb Helge Kreutzmann: > >> > >> > Package: dpkg-dev > >> > Version: 1.21.17

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-13 Thread Sven Joachim
Hello Helge, Am 13.01.2023 um 21:16 schrieb Helge Kreutzmann: > Hello Sven, > On Fri, Jan 13, 2023 at 09:05:21PM +0100, Sven Joachim wrote: >> Am 12.01.2023 um 11:29 schrieb Helge Kreutzmann: >> >> > Package: dpkg-dev >> > Version: 1.21.17 >> > Severity: normal >> > >> > I got a linitian error

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-13 Thread Helge Kreutzmann
Hello Sven, On Fri, Jan 13, 2023 at 09:05:21PM +0100, Sven Joachim wrote: > Am 12.01.2023 um 11:29 schrieb Helge Kreutzmann: > > > Package: dpkg-dev > > Version: 1.21.17 > > Severity: normal > > > > I got a linitian error for my package (linuxinfo) that the upstream > > signature is missing and

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-13 Thread Sven Joachim
Hi Helge, Am 12.01.2023 um 11:29 schrieb Helge Kreutzmann: > Package: dpkg-dev > Version: 1.21.17 > Severity: normal > > I got a linitian error for my package (linuxinfo) that the upstream > signature is missing and should be put alongside the .orig.tar.xz > during the build. > > This worked,

Bug#1028523: dpkg-dev: No obvious way to include upstream signature in dpkg-genchanges

2023-01-12 Thread Helge Kreutzmann
Package: dpkg-dev Version: 1.21.17 Severity: normal I got a linitian error for my package (linuxinfo) that the upstream signature is missing and should be put alongside the .orig.tar.xz during the build. This worked, the signature was included in the .changes file. However, it is not included in