compiling from git: mention libicu-dev early on

[bertsky]

(otherwise training tools will be deactivated)

[stweil]

Please re-open if those changes are really required for a Debian based Linux distribution.

[bertsky]

On Debian – in my case libpango1.0-dev did not pull libfribidi-dev...

[stweil]

I just checked that for Debian stable, old stable and old old stable: in all cases libpango1.0-dev has an unconditional dependency for libfribidi-dev, so any installation with libpango1.0-dev but without libfribidi-dev would be broken.

The same is true for Debian testing.

[bertsky]

Very strange.

[amitdo]

Reference: https://packages.debian.org/search?suite=default&section=all&arch=any&searchon=names&keywords=libpango1.0-dev

[amitdo]

@bertsky,

Do you use any 3rd party repo for Debian packages?

[bertsky]

Do you use any 3rd party repo for Debian packages?

Oops! I did have Debian testing in the sources list. Hence my versions of build-essential etc are actually from Debian trixie. But there, still, libpango1.0-dev depends on libfribidi-dev ...

[amitdo]

https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

[bertsky]

https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

Indeed – that was not a good decision at the time. But I did create a pin rule to prevent testing from slipping in unwarranted:

Package: *
Pin: release a=stable
Pin-Priority: 700

Package: *
Pin: release a=testing
Pin-Priority: 650

So IIUC it would only prefer that source if I requested certain versions...

[amitdo]

Basically you combined oldoldstable with nextnexttobethenextstable :-)

[bertsky]

Basically you combined oldoldstable with nextnexttobethenextstable :-)

I know, I know – call me crazy!