Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

2019-08-08 Thread Guillem Jover
On Wed, 2019-08-07 at 16:19:30 +0200, Axel Beckert wrote: > Guillem Jover wrote: > > Some of the features got removed, to trim down dependencies, and the > > API adapted to match the rest of the libdpkg-perl codebase, but if > > the removed output formats are needed, or anything else seems > >

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

2019-08-07 Thread Axel Beckert
Hi Guillem, Guillem Jover wrote: > > So some of us wonder if you would generally allow Debian Perl Team > > members (or maybe even someone else) to also officially take over the > > upstream development of Parse::DebianChangelog — as you seem to have > > done for the packaging back in 2015. > >

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

2019-08-07 Thread Guillem Jover
Hi! On Sun, 2019-07-28 at 22:38:29 +0200, Axel Beckert wrote: > the Debian Perl Team maintained libparse-debianchangelog-perl for > quite some years now using debian-specific patches against your > upstream version 1.2.0 from http://www.djpig.de/software/. > > Being sick of doing upstream work

Bug#933128: Would you be willing to pass Parse::DebianChangelog upstream development to someone else?

2019-07-28 Thread Axel Beckert
Hi Frank, the Debian Perl Team maintained libparse-debianchangelog-perl for quite some years now using debian-specific patches against your upstream version 1.2.0 from http://www.djpig.de/software/. Being sick of doing upstream work in form of debian-specific patches, the Debian Perl Team is