Hello,
The current snap ‘sqlmap’ appears to be unmaintained. The upstream project has newer versions available.
Current snap: Install sqlmap on Linux | Snap Store Publisher: khiemdoan Last update: 2024
I have created an updated snap package that builds the latest version of sqlmap and would like to maintain the snap going forward.
My snap build: sqlmap-snap/snapcraft.yaml at main · INEFFABLEJATIN/sqlmap-snap · GitHub
Could the ‘sqlmap’ snap name be transferred to me so I can maintain it?
It appears that the original snap’s publisher has provided a contact channel:
You should contact the publisher first regarding the snap’s maintenance issues before bringing it up to the store.
Note that most snap publishers are doing their work as a hobby/side project, do not escalate this issue until sufficient communication effort is made.
In the meantime feel free to publish the snap using an alternative name, and request the store or instruct the user to set up a command alias using the upstream-preferred name.
Thanks for the guidance.
I will try contacting the current publisher of the sqlmap snap to ask about the maintenance status.
If the snap is no longer being maintained, I would be happy to take over maintenance and keep it updated with the upstream sqlmap releases.
In the meantime I will publish my snap under an alternative name.
Note that you can also request to become the snap’s contributor, which gives you administrative access to the snap while leaving the snap’s ownership intact.
You’ll need the original snap’s publisher to invite you from the snap’s backstage in order to do so.
I mailed him a day ago if he reply then i will update you on that .
I got no response . i want that name ..
@policy-reviewers can you advise on what the next steps should be here?
FWIW I’d attempted to take over the snap gemini (to repurpose it for the LLM) in a similar fashion several months ago now, first by contacting the original maintainer if they’d be willing to give up the name via transfer and secondly via a dispute.
Months later, I’ve not had anything back from the store team beyond an initial “we’ll look into it” (and separately I can see someone else recently is instead going for gemini-cli and using an alias as an alternative, which isn’t problematic in itself but highlights a bigger issue here).
)
I think if there isn’t already an established process for these kind of situations, there really should be. I remember several years back when Popey were still working here, he’d reached out from an admin capacity asking if I were willing to give up a registered name and I said sure. Reasonably in the same situation were I MIA, I’d have agreed with it just being taken by force.
There’s a fair bit of curation stuff I’d like to see improved, and this is an example of one of them, there’s no benefit to user experience in having multiple snaps doing the same thing whilst the preferred name is unmaintained and yet people can still accidentally use it over the preferred version, or to a similar degree (in e.g., gemini case but not OP here) - misrepresenting what the typical person would expect whilst also being unmaintained!
In this case for sqlmap I’d personally be keen on the ownership being transferred forcibly if the original maintainer doesn’t respond within a suitable time frame, these instances will only get more common over time and user experience is critical IMHO, it’s a slow boiling situation that only gets worse for users over time.
Which is to say 6 years later, I still agree with comments raised here from both myself and @Lin-Buo-Ren - people should be expected to respond to at least Canonical within reasonable time frames or risk having their snaps transfered (or hidden) in the public interest.
sir when it will it happen @James-Carroll thanks for the support…
Note that I am not part of the @store team and have no ability to perform a name transfer, even if I wanted to.
It appears the snap publisher recently updated what is presumably the recipe repository:
Although the change itself doesn’t result in a working snap, it proves that the publisher hasn’t completely abandoned maintenance.
I suggest filing an issue regarding this matter on the issue tracker or, even better, submitting a pull request to fix the build recipe.
yup doing what i can do .. and again thanks for the support
