Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64371 - [asp] NOT DOING WHAT IS STATED IN MAN FOR EXPORT FUNCTION

Attached to Project: Arch Linux
Opened by Sp1d3rmxn (sp1d3rmxn) - Sunday, 03 November 2019, 14:12 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 03 November 2019, 14:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The export function does not give the current version being pushed as a package to a repository for certain packages without explanation.

In particular this is happening in python and other important system packages. Issuing an "asp export python" does not give the current version in the repository, instead of version "3.7.4" you get version "3.8.0".

According to the current documentation for "asp" in man it states:

"export TARGET...
Dump the build source files for each target into a directory of the target’s name in $PWD. Targets can be specified simply as package to check out the source files at HEAD, or in repository/package format to checkout the source files which were used to push the package which exists in repository."

Python version 3.8.0 does not exist in the repository, version 3.7.4 does. This is further verified by "pacman -Ss python" or visiting "https://www.archlinux.org/packages/extra/x86_64/python/". Neither of which show any version "3.8.0". Therefore it appears to be not true that "source files which were used to push the package which exists in repository" because version 3.8.0 does not exist as is easily proven.

Additional info:
* Not sure why this was closed because what is written here is effortlessly provably true. There is no explanation or anything that indicates one is to expect "testing"/"staging" type of packages here at all. Closing this does not change the fact that one is literally guessing at which version will be retrieved. If "asp export" is to be grabbing testing versions, it would be logical to give the end user some choice in this instead of inaccurately claiming what is written in the man page.

Steps to reproduce:
asp export python (you will logically expect the current version instead you get the testing/staging version without warning or explanation).

(There are many other important system packages like this that mysteriously have higher versions without any documentation explaining why this is happening or why the decision is made to have "asp" grab from trunk when the documentation from "asp" states nothing of that accord.)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 03 November 2019, 14:13 GMT
Reason for closing:  Not a bug

Loading...