On Sat, 2019-03-09 at 18:43 +0100, Andreas Tille wrote: > On Sat, Mar 09, 2019 at 04:33:12PM +0000, Adam D. Barratt wrote: > > On Mon, 2018-12-03 at 09:29 +0100, Andreas Tille wrote: > > > I tried to build > > > > > > https://salsa.debian.org/med-team/profphd/tree/debian/stretch-p > > > ropo > > > sed-updates > > > > > > in a stretch chroot, but got: > > > > > > ... > > > dh_builddeb > > > dpkg-deb: building package 'profphd' in '../profphd_1.0.42- > > > 1+deb9u1_all.deb'. > > > dpkg-genbuildinfo > > > dpkg-genchanges -v >../profphd_1.0.42-1+deb9u1_amd64.changes > > > dpkg-genchanges: warning: 'since' option specifies non-existing > > > version > > > dpkg-genchanges: warning: use newest entry that is earlier than > > > the > > > one specified > > > dpkg-genchanges: error: is not a valid version > > > dpkg-buildpackage: error: dpkg-genchanges gave error exit status > > > 255 > > > > > > > > > Sorry for my ignorance since I'm very rarely upload to proposed- > > > updates: > > > Is there something else I need to specify (please guide me to the > > > Fine > > > Manual, thank you). > > > > What tool and command line did you use to build the package that > > led to > > that error being generated? > > Sorry, that is 3 monthes ago. I usually use pbuilder. Should we > find out about that issue or would you simply volunteer to sponsor a > build that works for you to keep things simple? I'd be super happy > if this could be as simple as possible from the table.
To be honest, I have no particular desire to start sponsoring uploads to p-u, particularly for packages I know nothing about and don't use. Is the issue still reproducible? Regards, Adam
