Emmanuel Bourg (2017-06-15):
> Is this the only solution?
Probably not, but reverting the single change that triggered the
regression looks like a safe way to unbreak this situation. Especially
when the said change only happened many months after the relevant
package was
Emmanuel Bourg (2017-06-15):
> If you upload a NMU could you please push the changes to the Git
> repository?
I'll look into this when I've slept a bit. Reminders/prods welcome.
KiBi.
signature.asc
Description: Digital signature
__
This is the maintainer address of
Le 15/06/2017 à 18:09, Cyril Brulebois a écrit :
> If all succeed, I intend to NMU ca-certificates-java with the attached
> changes. I could have reintroduced the old package, but I chose to retain
> the svn to git changes, and to drop the version for the openjdk-7 case,
> since even jessie had a
Cyril Brulebois (2017-06-15):
> I was just saying this on IRC:
>
> “should I try to reinstate ca-certificates-java's old dependencies and
> compare? from my initial bug report, that's the change in the archive
> that led to the regression.”
>
> and mentioned earlier
Package: upgrade-reports
Severity: critical
Justification: makes upgrade from stable abort
[ X-D-Cc:
debian-rele...@lists.debian.org
pkg-java-maintainers@lists.alioth.debian.org
pkg-gnome-maintain...@lists.alioth.debian.org ]
Hi,
Regression spotted by Pere in some debian-edu job, but also
5 matches
Mail list logo