apron is marked for autoremoval from testing

[Debian testing autoremoval watch]

apron 0.9.10-9 is marked for autoremoval from testing on 2018-06-11

It (build-)depends on packages with these RC bugs:
897098: ppl: ppl FTBFS with TeX Live 2018

Re: Unison rebuild

[Leopold Palomo-Avellaneda]

On 25/05/18 13:29, Stéphane Glondu wrote:
> Le 23/05/2018 à 11:00, Leopold Palomo-Avellaneda a écrit :
>> in the mid time waiting for the NMU of unison I'm trying to rebuild the 
>> unison
>> package in a pbuilder stretch environment and I fails.
>> [...]
> 
> Strange. I just tried with a fresh pbuilder environment and I observe no
> such failure. I also tried cowbuilder.
> 

Maybe is that I have added backports as sources or debhelper 11 by default. In
any case, if I could use yours, I install them and that's all.


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?



signature.asc
Description: OpenPGP digital signature

Re: Unison rebuild

[Stéphane Glondu]

Le 23/05/2018 à 11:00, Leopold Palomo-Avellaneda a écrit :
> in the mid time waiting for the NMU of unison I'm trying to rebuild the unison
> package in a pbuilder stretch environment and I fails.
> [...]

Strange. I just tried with a fresh pbuilder environment and I observe no
such failure. I also tried cowbuilder.

Cheers,

-- 
Stéphane

Bug#900018: FTBFS with latest cmdliner

[Andy Li]

On Fri, May 25, 2018 at 3:02 PM, Mehdi Dogguy  wrote:
>
> I have the feeling that OPAM team is not willing to support OPAM 1.2.2
> for a long time. So it doesn't make sense, at least for me, to
> include it in Buster.
>
> Yesterday, I've uploaded opam-file-format to NEW. As soon as it gets
> accepted, I'll upload latest version of OPAM to Debian/Sid.
>
> It's based on the discussion with upstream at
>> https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6
>
>
Upstream mentioned in the linked discussion (above) that opam 1.2.2 is
their LTS release.
Sadly, opam 2 is not yet final, and "is still subject to
backwards-incompatible changes". See
https://bugzilla.redhat.com/show_bug.cgi?id=1501992#c23
I think we better stick to 1.2.2 for now.

Best regards,
Andy

Bug#900018: FTBFS with latest cmdliner

[Mehdi Dogguy]

Hi Andy,

On 2018-05-25 08:40, Andy Li wrote:

I've a patch:
https://github.com/ocaml/opam/compare/1.2.2...andyli:1.2.2-fix.patch


That's great!

FWIW, I've opened this bug report so that Opam doesn't migrate to
testing before being fixed or updated to a newer version. I have
the feeling that OPAM team is not willing to support OPAM 1.2.2
for a long time. So it doesn't make sense, at least for me, to
include it in Buster.

Yesterday, I've uploaded opam-file-format to NEW. As soon as it gets
accepted, I'll upload latest version of OPAM to Debian/Sid.


It's based on the discussion with upstream at
https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6



Thanks for the pointer.

Cheers,

--
Mehdi