On 2021/02/23 01:50, Michal Such������������������������ wrote:
On Mon, Feb 22, 2021 at 10:20:09AM +1030, Simon Lees
One feature of open build service that people building derivative
distros use is that packages will use other packages in the same project
/ repo for builds. So if all the custom packages you are using on your
machine are in the same project then it will use them for builds. This
gives you other advantages as well in that if you update one of the
libraries it will automatically rebuild all the packages that depend on it.
There is no such project. The packages are some obsolete TW snapshot.
^^^ Yep! Disk crash = I lost the TW snapshots things were built
against, as it was on my "downloaded from the Internet" disk which wasn't
backed up, as I thought I could always download it again and go from there.
And building on Leap may or may not work - I think the
new rpm spec file
uses features of the new rpm so it is not buildable with old rpm.
suppose that at some point in the history of the rpm package it
contained the new sources and was buildable with old rpm but you need to
find that, rebuild with old rpm, and then you can install the current
one. Not exactly nice experience. And it's quite possible that such
sources were only present in some bootstrap project and locating them in
OBS is pretty much impossible.
And that's why I said that the sources for building the current
packages were no longer included.
You can't build the current binaries unless you have some
unknown set of binaries that came from some unknown set of sources that
was posted for some number of days, then gone.
On 2021/02/23 02:23, Dominique Leuenberger / DimStar wrote:
In case you need/want to dup from something older, use
the DVD/NET iso
and do an offline upgrade (i.e. not on the running system).
Right...a complete wipe of a working system that can't afford
a complete wipe because nothing in opensuse upgrades package configs
reliably, let alone if one uses an offline upgrade (install new packages
The sources for the in binaries in TW now, can't be built on user
systems unless they maintained the TW-treadmill every day. If your
system goes out, standard or not, suse doesn't support upgrades.
If there was an archive of all the TW binaries from when I got
cut off, to today, it would be doable, though very unpleasant. It's not
that I didn't have a standard system, but that TW doesn't supply
the intermediate upgrade-bits past a few day expiration limit.
I.e. subject says it -- can't rebuild from sources because I can't
download readable rpm binaries that contain the build tools.
(Thus I'm rehauling my download stuff to handle leaping)