These packages have been deemed to not be adequately maintained or integrated into the Solus repositories and/or Solus software stack.
Basic Information (seafile):
Basic Information (seafile-client):
| R1844 libsearpc | |||
| D6788 | R1844:88750380d11d Update libsearpc to latest 3.1-latest | ||
| R2880 seafile | |||
| D6789 | R2880:d1e8c6a1322c Update seafile to 7.0.1 | ||
| R2881 seafile-client | |||
| D6790 | R2881:a18898fcafcf Update seafile-client to 7.0.1 | ||
This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.
If you wish to become the dedicated package maintainer for this package, please bear in mind that this package has been marked as a result of being either poorly integrated or maintained. If you are intent on becoming the maintainer for this package, please do so with:
In the event you wish to become a package maintainer for this, please comment that you will be stepping forward to do so. This way, a Core Team member, or a member of the Triage Team, can remove the Planned Deprecation tag.
These packages are now being removed from the repository, alongside libsearpc and ccnet
Is it standard practice that unmaintained packages get removed from the repo and therefore get removed from every system as soon as the owner updates his packages?
I rely on Seafile for my work and the automatic removal was unfortunate. If I step up to maintain the packages can they be included again?
Yes, this is a completely normal and standard practice. The package gets marked as "obsolete" and eopkg will automatically remove it from the system. This is the same mechanism we also use to replace or rename a package.
I rely on Seafile for my work and the automatic removal was unfortunate. If I step up to maintain the packages can they be included again?
You'll need to maintain and re-introduce its dependencies, which includes libsearpc and ccnet as well. The respective repos have been disabled but you should still be able to clone them, update them, and provide a patch referencing this task. I can re-enable the repositories once patches are submitted and approved, and remove them from the deprecations list.
@JoshStrobl I am receiving 403s when attempting to clone any of the repositories (seafile or the dependencies).
I've created a patch for libsearpc, seafile, and seafile-client and built all packages successfully. ccnet is no longer needed.
@FriesischScott Did you already create a patch yourself? Otherwise I'll submit my patch. Tell me if you require the *.eopkgs so I can share them till Seafile is back in the repository.
@JoshStrobl I'll queue up as maintainer for stated packages if @FriesischScott passes. At least I'll regularly submit patches since I rely on Seafile and while building it myself, I can also maintain respective packages for Solus.
@r3r57 Obviously I only saw your patches after I was ready to submit mine :). In any case I subscribed myself to the releases on Github on all related repositories for future updates.