[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Adding copilot



On Thu, 16 Jun 2022, Ivan Perez wrote:

TL;DR: I'm using docker to run this in a fresh machine; it's not working even without copilot. Details included.

On 2022-05-31 01:34, Scott Talbert wrote:
On Mon, 30 May 2022, Ivan Perez wrote:

Hi,

I'm just following up on this.

Have you had a chance to review what4's dependencies? Is there anything I can help with?

Really hoping we can make this happen.

Hey Ivan,

Unfortunately, I have not made any progress.  Too much to do and too
little time.  :(

Something that would be very helpful, if you have time, would be to
figure out the changes required to the package plan[1] in order to
add/update all the necessary dependencies.  This will give us the full
scope of what changes need to be implemented in Debian and then we
could start working on them.

The way that it works is that you would add copilot to the
packages.txt file, and then run ./test-packages.pl and see if it
succeeds.  I have already started working on it here[2], so you could
start with my changes. You can see that I patched the copilot-theorem
cabal file with the changes that I mentioned.

Hi,

I understand. Thanks for the progress you made.

Hopefully I can help also move things forward.

I'm trying to first get things to run without any changes, and then I can add the modifications for copilot.

Right now I'm getting an error without your changes.

To make sure I don't mess my installation, I'm doing this in a docker image. It's not completing the execution of ./test-packages.pl.

This is my docker image:

```Dockerfile
FROM debian:latest

ENV DEBIAN_FRONTEND="noninteractive"
RUN apt-get update
RUN apt-get install --yes libfile-slurp-perl libipc-run-perl \
 liblist-moreutils-perl libtext-patch-perl libdpkg-perl \
 cabal-install dctrl-tools patchutils git

RUN git clone https://salsa.debian.org/haskell-team/package-plan
RUN cabal update
WORKDIR package-plan
CMD ./test-packages.pl
```

This is the tail of the terminal when I run that image:

```
Patching yi-language.cabal (version 0.19.0)
Writing 00-index.tar...
Creating fake global package db
Testing packages in 1 different groups
Running cabal-install (group default)...
Cabal install failed:
Warning: the --global flag is deprecated -- it is generally considered a bad
idea to install packages into the global store
cabal: Could not resolve dependencies:
[__0] next goal: aeson (user goal)
[__0] rejecting: aeson-2.1.0.0 (constraint from command line flag requires
(==2.0.3.0))
[__0] trying: aeson-2.0.3.0
[__1] next goal: arbtt (user goal)
[__1] rejecting: arbtt-0.11.1 (conflict: aeson==2.0.3.0, arbtt => aeson>=0.10
&& <1.6)
[__1] rejecting: arbtt-0.11, arbtt-0.10.4, arbtt-0.10.3, arbtt-0.10.2,
arbtt-0.10.1, arbtt-0.10.0.2, arbtt-0.10.0.1, arbtt-0.10, arbtt-0.9.0.13,
arbtt-0.9.0.12, arbtt-0.9.0.11, arbtt-0.9.0.10, arbtt-0.9.0.9, arbtt-0.9.0.8,
arbtt-0.9.0.7, arbtt-0.9.0.6, arbtt-0.9.0.5, arbtt-0.9.0.4, arbtt-0.9.0.3,
arbtt-0.9.0.2, arbtt-0.9.0.1, arbtt-0.9, arbtt-0.8.1.4, arbtt-0.8.1.3,
arbtt-0.8.1.2, arbtt-0.8.1.1, arbtt-0.8.1, arbtt-0.8, arbtt-0.7,
arbtt-0.6.4.1, arbtt-0.6.4, arbtt-0.6.2, arbtt-0.6.1, arbtt-0.6, arbtt-0.5,
arbtt-0.4.5.1, arbtt-0.4.5, arbtt-0.4.4, arbtt-0.4.3, arbtt-0.4.2,
arbtt-0.4.1, arbtt-0.4, arbtt-0.3.0, arbtt-0.2.0, arbtt-0.1.5, arbtt-0.1.4,
arbtt-0.1.3, arbtt-0.1.2, arbtt-0.1.1, arbtt-0.1 (constraint from command line
flag requires (==0.11.1))
[__1] fail (backjumping, conflict set: aeson, arbtt)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: aeson, arbtt

Use of uninitialized value $_[0] in join or string at /usr/share/perl5/File/Slurp.pm line 321.
2 error(s) in total.
```

Should I do something differently? Do I need to install something else?

Note that this is without any changes. Once this runs, then I can try with the changes.

Nope - you're doing nothing wrong! Sorry - I should have mentioned this to you sooner, but the team is in process of upgrading the entire package set to Stackage LTS 19 and the package plan is currently broken. The good news about this is that most of the packages are going to be upgraded to much newer versions, so this should actually make the effort to get copilot added much smaller. The bad news is that currently things are a bit in flux. So, perhaps wait a week and check back? You can see the current state of the package plan here (and you can see the current error is the same one you're seeing, so that shows you did it right):

https://jenkins.debian.net/view/haskell/job/haskell-package-plan/

Scott


Reply to: