On Tuesday 2021-02-23 08:01, L A Walsh wrote:
1:47 PM, L.A. Walsh wrote:
> If someone has a pre-4.14 rpm, then they can't
> upgrade to suse's current packages. They also cannot build or
> install an rpm>=4.15...
Simon Lees wrote:
This is simply not true, [it's just that]...
if you don't have rpm 4.14 or later on your machine its no
longer in a state we support.
How does this not seem like doublespeak, or speaking with
a forked tongue?
If someone doesn't already have their "upgrade ticket" in
place, they can't get one.
You also can't upgrade from Windows 95 to Windows 10, so stop
wanting to speak to the manager.
On 2021/02/16 00:58, Dominique Leuenberger / DimStar
* The snapshot is going to be large, in the
number of ackages
to 'update' (mostly rebuild counters) and thus lso megabytes.
* The snapshot is the first to be based on glibc 2.33
So, which is it? If glibc is binary compatible, then why do so
many packages need immediate upgrade when glibc is upgraded?
Because the packages were rebuilt (this indeed was a manual trigger AIUI!),
which makes them use all the new features they can, right away.
glibc the library is still binary compatible. The _programs_ aren't.