Hi,
Axel Beckert (2020-06-07):
> Since Guillem cleared up this and even provided a patch for aptitude
> (which is applied and in testing for a week or two), I changed my
> opinion on this topic completely.
>
>> If another team member +1's the package removal, I'll happily proceed.
>
> Seconded.
Hi,
intrigeri wrote:
> I did not dare proposing this course of action so far because the
> notes from our BoF at DebConf19 are a bit ambiguous about whether we
> decided to remove the package from sid, in addition to removing it
> from testing.
I wasn't at the BoF, but was opposing rather
Hi,
gregor herrmann (2020-05-22):
> On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote:
>
>> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
>> ask (presumably the release team) for libparse-debianchangelog-perl to
>> lose its "key package" status, so the autoremoval
On Fri, 22 May 2020 09:58:12 +0200, intrigeri wrote:
> So, once aptitude >= 0.8.13-1 has migrated to testing, we'll need to
> ask (presumably the release team) for libparse-debianchangelog-perl to
> lose its "key package" status, so the autoremoval machinery can remove
> it from testing due to
Hi,
intrig...@debian.org (2019-07-26):
> Therefore, at the pkg-perl BoF today at DebConf, after pondering other
> options such as orphaning this package, we decided that we don't want
> this package to be included in Bullseye (at least, maintained under
> the Perl team umbrella) unless someone
Hi!,
Guillem Jover:
> Ah! Thanks for the info. How about the following clarification then? :)
Perfect! That's exactly what I would have needed :)
Cheers,
--
intrigeri
Hi!
On Sat, 2019-11-02 at 16:31:24 +0100, intrigeri wrote:
> Guillem Jover:
> > On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote:
> >> Oh, this is very interesting, thanks! I had taken a look at that
> >> module, but from the documentation I understood it only gives us "the
> >> number of
Hi,
Guillem Jover:
> On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote:
>> gregor herrmann:
>> > In dpt-new-upstream we're using Dpkg::Changelog::Debian from
>> > libdpkg-perl, which might help here as well.
>> Oh, this is very interesting, thanks! I had taken a look at that
>> module, but
Hi!
On Sat, 2019-07-27 at 12:20:00 -0300, intrigeri wrote:
> gregor herrmann:
> > In dpt-new-upstream we're using Dpkg::Changelog::Debian from
> > libdpkg-perl, which might help here as well.
> Oh, this is very interesting, thanks! I had taken a look at that
> module, but from the documentation
Hi again,
intrigeri:
> I'm very glad I was mislead. It looks like Dpkg::Changelog{,::*} are
> sufficient for many, if not most, use cases of Parse::DebianChangelog :)
Hoping it will help other affected folks go through this transition,
here are MRs that give examples about how some code can be
gregor herrmann:
> In dpt-new-upstream we're using Dpkg::Changelog::Debian from
> libdpkg-perl, which might help here as well.
Oh, this is very interesting, thanks! I had taken a look at that
module, but from the documentation I understood it only gives us "the
number of changelog entries that
On Fri, 26 Jul 2019 18:28:38 -0300, intrigeri wrote:
> dh-make-perl uses this module for three things:
>
> - t/debian-version.t: extracting the latest version of
>a changelog file
>
> - copyright_from_changelog:
>
> - extract maintainer and date for each changelog entry
>
> -
intrigeri:
> https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=libparse-debian-changelog-removal=debian-perl%40lists.debian.org
Scratch that (typo), it is actually:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=libparse-debian-changelog-perl-removal=debian-perl%40lists.debian.org
> - Users of Parse::DebianChangelog could list their minimal
>requirements for a new implementation.
If more folks want to play this game, we should probably move this to
a wiki page, but for the sake of getting things moving simply, here we
go:
dh-make-perl uses this module for three
Package: libparse-debianchangelog-perl
Version: 1.2.0-13
Severity: serious
Hi,
many years ago, the Debian Perl group has unwillingly inherited the
role of de facto upstream maintainer for this package: all changes
done since 2011 were applied as Debian patches. We don't feel we're in
a good
15 matches
Mail list logo
