-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BETA flag not shown #140
Comments
@mreid-tt any idea what's going wrong? |
Just uploaded revision 11 and it has the label (revision 10 is still missing it). |
@hgy59 this seems to be a side-effect of how we define beta versions. Technically there are two fields related to beta packages in the DSM developer guide:
The problem is that in our database schema we only define the Lines 402 to 411 in 2b4012b
The field for Lines 463 to 465 in 2b4012b
Now this creates a dependency in our packages for the value of spksrc/mk/spksrc.spk.mk (L208-L210)
The challenge is that when
This structure should not exist based on how our
Now, within the admin interface it lists it as a beta because the view is initialised based on the model above: spkrepo/spkrepo/views/admin.py Lines 274 to 278 in 2b4012b
Then we have the specific columns: spkrepo/spkrepo/views/admin.py Lines 310 to 315 in 2b4012b
So it would be using the synthetic field for Now this is different than what is done in the front-end interface with this code block:
As you can see it is querying the Lines 66 to 67 in 2b4012b
Lines 181 to 183 in 2b4012b
My guess is that the synthetic beta field used by the admin interface is returning |
BETA flag is not shown on some package versions.
See
monit
package.All three revisions (7, 8, 10) are BETA, but only revisions 7 and 8 are displayed with
beta
Label, revision 10 is missing this label.The text was updated successfully, but these errors were encountered: