Control: owner 1073481 !

On Sun, Sep 01, 2024 at 06:11:12PM +0100, Julian Gilbey wrote:
> On Sun, Sep 01, 2024 at 04:31:58PM +0100, Colin Watson wrote:
> > On Tue, Aug 20, 2024 at 06:00:16PM +0100, Julian Gilbey wrote:
> > > I wonder whether you could take a look at this at some point?  I took
> > > a quick look at the newer pydantic-core (2.22.0), but there's some bad
> > > news here: there are quite a few Rust packages that need updating
> > > first, and one that needs an ITP too (assuming I've understood
> > > Cargo.toml correctly; I've done this by hand as "cargo debstatus"
> > > can't yet cope with the 2021 edition).  Here's my annotated version of
> > > the relevant sections (I think) of Cargo.toml:
> > 
> > I've started on this, although I had to learn how debcargo worked first
> > and as you note one of the packages will need a trip through NEW.  Give
> > me a little while ...
> 
> Great!  I've done the first two already (strum and serde_json).

I've uploaded new versions of:

  rust-datetime
  rust-enum-dispatch
  rust-iso8601
  rust-num-bigint
  rust-python3-dll-a
  rust-smallvec
  rust-speedate
  rust-version-check

... and also uploaded rust-jiter to NEW.  With all of that and a bit of
Cargo.toml patching, pydantic-core now builds for me locally.

It also needs a new pydantic, which forces the choice of pydantic-core
version: the latest stable release 2.8.2 requires exactly pydantic-core
2.20.1 and breaks with newer versions (well, at least it breaks with
2.23.1 - I didn't try the versions in between).  That makes it easier:
with the uploads above I now only have to patch Cargo.toml for an older
idna, and pydantic 2.8.2 works fairly easily.

I'll upload all this once rust-jiter has passed NEW.

-- 
Colin Watson (he/him)                              [cjwat...@debian.org]

Reply via email to