(continuing with top-posting pattern of this thread...) If we don't do la
cleanup when installing old deb, then there will be bits present in the
installed la that will either easily break building other packages or lead to
propagated binary differences in them. The cleanup removes bits that
It will work, new debs won’t work with old dpkg but there is a dpkg pre-depends
injected into them
The difference is triggers, and some of the la processing. Current fink breaks
debsums (and Debian rules) as it changes the la files after install, this
changes the md5sum and thus breaks
Will old debs work with the new dpkg? Or is the deb compatibility broken
in both directions?
If we're going to need a new tree (called "11.0"?), what distributions
should we put into it? Obviously macOS 11.0. Should we also put 10.14.5
and 10.15 into it? These two share the same /usr/bin/perl
I’m almost positive all the packages are compare (texinfo might have an extra
split) but you can not put dpkg into the 10.5 tree since it’ll break deb
compat. This branch needs a new tree then it can be added.
---
TS
http://www.southofheaven.org/
Life begins and ends with chaos, live between
> On Aug 28, 2020, at 02:42, Hanspeter Niederstrasser
> wrote:
>
> What's the upgrade process for the dpkg1.16 branch and the dists tree?
>
> Several packages are now essential (e.g. time-date-pm and xz) and will have
> to be moved from their present subfolders in dists to 'base'. Also,
What's the upgrade process for the dpkg1.16 branch and the dists tree?
Several packages are now essential (e.g. time-date-pm and xz) and will
have to be moved from their present subfolders in dists to 'base'. Also,
some base packages have newer versions than what's in the dpkg1.16
branch