Le 16/08/2024 à 07:19, Paul Gevers a écrit :
The OCaml compiler has two compilation modes: native and vm.
The new version disabled the native mode on 32bits architectures.
Some packages that were ok with the last version aren't anymore.
Hope that makes things clearer,
Partially. My (not expl
Hi
On 16-08-2024 06:31, julien.pu...@gmail.com wrote:
The OCaml compiler has two compilation modes: native and vm.
The new version disabled the native mode on 32bits architectures.
Some packages that were ok with the last version aren't anymore.
Hope that makes things clearer,
Partially. My
Hi,
Le jeudi 15 août 2024 à 21:52 +0200, Paul Gevers a écrit :
>
> On 13-08-2024 08:03, Stéphane Glondu wrote:
> > Howevever, many of them are related to the fact that i386
> > and armhf are no longer native (ocaml 5 dropped support for native
> > compilation on 32-bit architectures), hence the
Hi
On 13-08-2024 08:03, Stéphane Glondu wrote:
Howevever, many of them are related to the fact that i386
and armhf are no longer native (ocaml 5 dropped support for native
compilation on 32-bit architectures), hence the corresponding
uninstallability or autopkgtest issues for coq-related packa
Dear Emilio,
Le 12/08/2024 à 10:31, Emilio Pozuelo Monfort a écrit :
As expected, removal hints will be needed, which I've put in 3
categories:
# Independent broken packages
hol-light (#1073882)
ocaml-ffmpeg (#1072440)
ocaml-lo (#1075329)
pa-ounit (#1073907)
ppx-tools (#1078383
On 12/08/2024 07:37, Stéphane Glondu wrote:
Le 07/08/2024 à 10:18, Emilio Pozuelo Monfort a écrit :
Let's go ahead with this one.
The needed recompilations are mostly done.
As expected, removal hints will be needed, which I've put in 3 categories:
# Independent broken packages
hol-light
Le 07/08/2024 à 10:18, Emilio Pozuelo Monfort a écrit :
Let's go ahead with this one.
The needed recompilations are mostly done.
As expected, removal hints will be needed, which I've put in 3 categories:
# Independent broken packages
hol-light (#1073882)
ocaml-ffmpeg (#1072440)
ocaml-l
Control: tags -1 confirmed
On 25/07/2024 10:54, Emilio Pozuelo Monfort wrote:
On 17/07/2024 21:56, Adrian Bunk wrote:
On Wed, Jul 17, 2024 at 11:28:04AM +0200, Emilio Pozuelo Monfort wrote:
On 16/07/2024 13:16, Adrian Bunk wrote:
On Tue, Jul 16, 2024 at 10:25:43AM +0200, Stéphane Glondu wrote
On 17/07/2024 21:56, Adrian Bunk wrote:
On Wed, Jul 17, 2024 at 11:28:04AM +0200, Emilio Pozuelo Monfort wrote:
On 16/07/2024 13:16, Adrian Bunk wrote:
On Tue, Jul 16, 2024 at 10:25:43AM +0200, Stéphane Glondu wrote:
Hi,
Hi Stéphane,
Le 27/06/2024 à 11:38, Stéphane Glondu a écrit :
The re
Le 22/07/2024 à 12:16, Stéphane Glondu a écrit :
I've added packages that declare rebuilt packages in their
testsuite-triggers field. That makes a total of 104 packages.
I've scheduled those packages, and it revealed 5 failures:
- bdebstrap: seems unrelated to OCaml (rather to Python I'd say)
-
Hi Paul,
Le 21/07/2024 à 08:18, Paul Gevers a écrit :
I've scheduled tests of all OCaml packages that provide tests (there
are 86 of them). I did not specify any priority, I hope that's fine.
That's fine for now. I guess you submitted via pasting the json you
created in the self-service.
In
Hi,
On 21-07-2024 1:14 p.m., Adrian Bunk wrote:
The proper solution would be that release team tooling automatically
schedules rebuilds and autopkgtests with the rebuilt packages for
transitions prepared in experimental.
But even with experimental that isn't always possible because there
migh
On Sun, Jul 21, 2024 at 08:18:50AM +0200, Paul Gevers wrote:
>...
> PS: one other idea I'm having. There are multiple teams doing these kind of
> rebuilds and archive creation; does each have their own tools and does it
> their own way, I guess so? Has anybody ever tried to have the teams join
> fo
Hi Stéphane,
On 21-07-2024 6:40 a.m., Stéphane Glondu wrote:
I've scheduled tests of all OCaml packages that provide tests (there are
86 of them). I did not specify any priority, I hope that's fine.
That's fine for now. I guess you submitted via pasting the json you
created in the self-servic
Hi,
Le 20/07/2024 à 21:24, Paul Gevers a écrit :
Thanks. I've triggered test of camlbz2 with ocaml-next. It does seem
to work :-)
Great, so next is some expectation. You're free to use this service, but
if you schedule lots of tests (hundreds), please use an appropriate low
priority, to not
On Thu, Jul 18, 2024 at 10:51:01AM +0200, Stéphane Glondu wrote:
> Hi,
>
> Le 17/07/2024 à 21:56, Adrian Bunk a écrit :
> > > Other than that, I'm happy with the current state and we could go ahead.
> > > So
> > > if you can get those bindings disabled, then I think we can go ahead.
> >
> > I tr
Hi,
Le 17/07/2024 à 21:56, Adrian Bunk a écrit :
Other than that, I'm happy with the current state and we could go ahead. So
if you can get those bindings disabled, then I think we can go ahead.
I tried looking at that, but this "ideally" is in level 15 of the ocaml
transition.
The bindings a
On Wed, Jul 17, 2024 at 11:28:04AM +0200, Emilio Pozuelo Monfort wrote:
> On 16/07/2024 13:16, Adrian Bunk wrote:
> > On Tue, Jul 16, 2024 at 10:25:43AM +0200, Stéphane Glondu wrote:
> > > Hi,
> >
> > Hi Stéphane,
> >
> > > Le 27/06/2024 à 11:38, Stéphane Glondu a écrit :
> > > > The remaining un
On 16/07/2024 13:16, Adrian Bunk wrote:
On Tue, Jul 16, 2024 at 10:25:43AM +0200, Stéphane Glondu wrote:
Hi,
Hi Stéphane,
Le 27/06/2024 à 11:38, Stéphane Glondu a écrit :
The remaining unknowns are llvm-toolchain-{14,15,16,17,18}... [...]
I've done a rebuild of the OCaml universe with yes
On Tue, Jul 16, 2024 at 10:25:43AM +0200, Stéphane Glondu wrote:
> Hi,
Hi Stéphane,
> Le 27/06/2024 à 11:38, Stéphane Glondu a écrit :
> > The remaining unknowns are llvm-toolchain-{14,15,16,17,18}... [...]
>
> I've done a rebuild of the OCaml universe with yesterday's unstable
> (mostly). The "
Hi,
Le 27/06/2024 à 11:38, Stéphane Glondu a écrit :
The remaining unknowns are llvm-toolchain-{14,15,16,17,18}... [...]
I've done a rebuild of the OCaml universe with yesterday's unstable
(mostly). The "missing" packages are the same, but the llvm-toolchain-16
build got far enough to FTBFS
Hi,
Le 26/06/2024 à 11:38, Emilio Pozuelo Monfort a écrit :
Assuming xen gets fixed, I checked if the rest could be removed:
$ dak rm -Rn -s testing approx cairo-ocaml camlimages camltemplate
coinst cothreads cryptgps facile frama-c gd4o hlins hol-light lablgl
ledit mcl14 misery mlpcap nproc
On 21/06/2024 07:25, Stéphane Glondu wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: oc...@packages.debian.org
Control: affects -1 + src:ocaml
User: release.debian@packages.debian.org
Usertags: transition
Dear Release Team,
I uploaded ocaml 5.2.0 to experimental, and it bu
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: oc...@packages.debian.org
Control: affects -1 + src:ocaml
User: release.debian@packages.debian.org
Usertags: transition
Dear Release Team,
I uploaded ocaml 5.2.0 to experimental, and it builds successfully on
all release architectures
24 matches
Mail list logo
