Re: Bug#897605: profphd failure in stretch
On Fri, May 04, 2018 at 04:01:48AM +0000, olivier sallou wrote:
> Le jeu. 3 mai 2018 21:55, Andreas Tille <andreas@an3as.eu> a écrit :
>
> > On Thu, May 03, 2018 at 02:58:58PM +0000, olivier sallou wrote:
> > >
> > > newer version in sid (1.0.42-2) added a patch to allow new perl release.
> > A
> > > quick test on sid works (at least no error, just calling program with no
> > > argument), so maybe backporting this release would do the job
> >
> > Ahhh, right - I remember that Tatiana had to do some heavy patching.
> >
> > > > We definitely need some CI test for this package obviously.
> >
> > That was also done by Tatiana.
> >
> > However, a backport does not really close a bug in stretch and the issue
> > is also not really a security issue, right?
> >
>
> This is indeed not a security issue, but package is unusable. Backport
> would at least make software available.
> I don't know know what is usual debian policy regarding this use case. I
> suppose it occured multiple times.
>
> I can't be sure that sid version is really working, it just does not show
> any error. Could tatiana do some 'real' testing?
You should file a bug against release.debian.org with a proposed patch for
stretch to get their opinion of whether it should be fixed in stretch.
It is certainly serious enough if it's unusable, so they only question
will be how invasive the changes are.
If it's too broken (ie can't be realistically fixed) it should probably
be removed from stretch. Agains the release team are the people to
consult about this. If this were the case, then a backport would indeed
be worthwhile.
Cheers,
Dominic.
Reply to: