Page MenuHomeSolus

Inclusion of flask-sqlalchemy in the repo
Closed, ResolvedPublic

Description

Name of the software
flask-sqlalchemy

Project/product Homepage
http://flask-sqlalchemy.pocoo.org/2.3/

Why we should include this into the repository, i.e. what does it do that the alternatives do not?
Flask-SQLAlchemy is an extension for Flask that adds support for SQLAlchemy to your application. It aims to simplify using SQLAlchemy with Flask by providing useful defaults and extra helpers that make it easier to accomplish common tasks.

Is it open source?
Yes

If it is open source, please provide a link to the most up to date, versioned source tarball/zipfile. master.zip links will not be accepted.
https://github.com/mitsuhiko/flask-sqlalchemy/archive/2.3.2.tar.gz

Event Timeline

DataDrake triaged this task as Wishlist priority.Oct 23 2018, 10:47 PM
DataDrake moved this task from Backlog to Accepted For Inclusion on the Package Requests board.

I had submitted the revision. Why isn't it being accepted?
I am new to packaging. Did I do something wrong??

@maverick1 You need to wait, because sometime the revision is being buried with other revisions. And the core team usually prioritize package update over new package

I have submitted some package update requests too. Since there was no response, I felt like something was wrong. Did I do something wrong in terms of packaging?

Nope, it's quite normal. The core teams will tell you what's wrong in your patch, they're not going to sugarcoat anything if you do something wrong. But, they are quite busy with other thing than Solus. If your patch not getting any attention, just wait or reach out to them on IRC.

@maverick1 as yursan9 said, it's normal. Between the package request, validation of the request, submission then review of the patch (especially when there are a few iterations because things have the be changed) then landing the patch and sync with stable repository, it may take some time... This also depends on the workload and the current on-going activities.
Once the package has been included in the repository, it gets smoother as updating an existing package is usually not a big thing.

So don't worry it's all fine... just need to be patient.