In T8036#154581, @FriesischScott wrote:

@JoshStrobl I am receiving 403s when attempting to clone any of the repositories (seafile or the dependencies).

In T8036#154581, @FriesischScott wrote:

@JoshStrobl I am receiving 403s when attempting to clone any of the repositories (seafile or the dependencies).

@JoshStrobl I am receiving 403s when attempting to clone any of the repositories (seafile or the dependencies).

In T8036#154388, @MariusSpangenberger wrote:

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?

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?

This package is now being removed from the repository.

This package is now being removed from the repository.

This package is now being removed from the repository.

These packages are now being removed from the repository, alongside libsearpc and ccnet

This package is now being removed from the repository.

This package is now being removed from the repository.

I would help to maintain this package. I might need some help along the way, but I have some experience with terraform.

I can also add it's a builddep for R3610

Was resolved with R4352:a91f85c775c4aabf539cde4421efa935e1bc63c2

Alright.

Hi,
I am willing to maintain this package.
Losing this packet would be very sad, it's a really good replacement of notepad++.

Resolved thanks to @chax

New version 1.1.1 was released recently, so i will try to package it.

I volunteer as Maintainer.

I volunteer as Maintainer.

Thanks for picking up maintainership of ipscan @chax

Here it is: D6505

Correct, a package update. Submitted, though it's not linked to this task.

@Gnat008 I assume you mean you have a package update, in which case great! Please submit the patch, once it's landed we can close this issue, and thanks for taking up maintainership of this package!

Hey I use this thing, so I can take it in my basket.
But tbf, I'd rather quietly wait for a release as it works well enough for my needs unless someone report issues that have been fixed on master.

I can take this, if that's okay.

@xulongwu4, thanks for the tip, i wasn't aware of this option, it works now.
I just need to cleanup a bit and i will submit the patch when i'm done.

@chax Did you enable network in solbuild by setting networking : yes in your package.yml file?

Yes, tried to update package.yml and then i realized that ipscan changed the way it builds. Now it uses gradle (gradle wrapper) to build.
There are a couple of problems with new build system.
Gradle wrapper doesn't work at all inside solbuild, having some network issues, not being able to download gradle zip.

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.

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.

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.

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.

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.

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.

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.

Since Herald is derp.

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.

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.

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.

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.

@chax Any update on this?

I also see that there is newer version available, so i will try to update it to 3.5.5 and submit patch

I volunteer as maintainer.

I volunteer to maintain this package as I use it occasionaly. Should be solved by D5023

Perhaps this could be replaced with GCL? This seems to be older, while GCL is GNU's official Common Lisp.

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.

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.

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.