OK, thanks for that link . . . took a fast look at it.
As far as the latest agama installer goes, that link in the wiki seemed to go to the same place where I got mine less than a week ago . . . .
Apologies, it’s not directly in the wiki. It’s from the Github project. That points to https://agama-project.github.io/ which has a download link you can follow to get the latest (the one I installed from was built very early this morning, my time).
Ultimately, the linking goes to Agama - which has a direct link to the latest build. You can remove the filename from the download link to look at the directory on the build service where the latest builds are published.
Posted my issue on the Github site and did get a fast interaction. Those guys claim that the latest updates to it include all of the requested features. I’m down on spare flash drives at the moment, so I can’t check it. One poster said, “The installer included is up to date,” but another poster said, “We are speaking to you from the future, and the included installer with Leap is speaking to you from the past.”
So, seems like the way to get full function is via the various links to the current installer?
I rolled back to run the install as 15.6 . . . and at some point when I get it working I will upgrade it to 16, the olde fashioned way . . . .
Personal opinion here - it’s odd a (GA) version of agama is not included on a current 16Beta ISO. The agama installer should have had its own Alpha->GA dev cycle, separate from a distro ISO release.
1 Like
Agama isn’t GA yet, so it’s not surprising that the GA version isn’t included in the beta, since it’s not GA yet. 
1 Like
Yep. I don’t disagree . . . those gravitating to Beta or Alpha editions would not be “basic” user types.
Even if on the download page there was a link to “click here for the daily iso for latest Agama edition” . . . that would have been helpful. Time passes, whether anything useful is happening, or not.
openSUSE Leap and Agama are completely independent projects with different release cycles. So it should be logic that Leap 16 Beta can’t contain the latest Agama installer. Agama develops way faster as a fixed beta snapshot could cope with. This can be seen when only reading some minutes on the Agama github page which was provided already above.
As explained on the github page, you need to test it the other way around. You can always download the latest Agama installer and install as example Tumbleweed or Slowroll and always have the newest Agama features.
It is the completely wrong approach for testing of Agama to use the Leap 16 Beta (or any other fixed release distribution) as they contain already heavily outdated versions. For testing of installer features you always need to use the latest Agama download from github. As explained above, this is due to that Agama and openSUSE Leap are completely different and independent projects.
2 Likes
The latest Agama installer offers Leap 16 Beta amongst the available distro install options. (I currently have the Agama version 15 on a USB storage device.)
1 Like
OK, somewhat moot at this point as I installed 15.6 using the olde-fashioned installer that offered “expert partitioner” which I was able to use. But this post is somewhat like offering “plausible deniability” for the association of the two projects . . . but I got the agama installer from the main Leap 16 download page, so they are “associated” . . . . I didn’t go to some Backports page and download agama and then try to use it to install Leap 16 from another backport.
And, seemingly that associated package contained a months old edition of agama . . . that is under-spec’d . . . ???
It’s ALL good, as they say on the streets of Compton . . . good is everywhere, interspersed with the banal.
I have ordered some new flash drives, when they show up I will try the latest edition of the installer and see if the packages are on par with the older installer. But, again, I wasn’t “testing” the agama installer, end user, trying to install Leap 16 into a drive with two other installs on it . . . and with the associated package that mission failed to be accomplished . . . IMHO.
You’re going to see that the versions in Leap 16 beta for all sorts of packages are going to be older than the latest development builds for those packages.
That’s nothing particularly new. The Leap 16 beta build is a snapshot of a bunch of different things - including the installer. That’s also been the case with past Leap beta builds - the installer didn’t stop development just because a beta release (or alpha, or RC release) became available. It continued as well.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.