FS#70156 - [twisted] [python-twisted] pkgbase and directory differ

Attached to Project: Arch Linux
Opened by Erich Eckner (deepthought) - Thursday, 25 March 2021, 08:41 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 25 March 2021, 17:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The packages python-twisted and python2-twisted have pkgbase=twisted, but are checked in under python-twisted/ in the svn/git.

This breaks archlinux32's build master, because it is expected, that the pkgbase matches the directory name.

Is this assumption reasonable and you fix this error on your end or is there nothing wrong with the current directory structure (from your point of view) and we need to change our logic?

Just for reference, this happens in the current git master: 67145cbfbe8bdc4db6fdc16c6d1cbf0413584799

Additional issue, that is connected: The link to the PKGBUILD on the package page is broken, too:
https://archlinux.org/packages/extra/x86_64/python-twisted/ links to https://github.com/archlinux/svntogit-packages/tree/packages/twisted/trunk

I see, that this error is corrected in trunk/ already, but I really think, it should be corrected in the repos/'s PKGBUILDs, too.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 25 March 2021, 17:44 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Testing transitions will soon be concluded, and the old version in [extra] is not expected to ways be perfectly accurate.
Comment by loqs (loqs) - Thursday, 25 March 2021, 14:25 GMT
It will be fixed when python-twisted 21.2.0-1 moves out of testing.
Comment by Erich Eckner (deepthought) - Thursday, 25 March 2021, 16:02 GMT
ah, ok, I didn't check *that* one. Then I'll wait for it being moved to [extra] :)
Comment by Eli Schwartz (eschwartz) - Thursday, 25 March 2021, 17:41 GMT
Right, this is not an error. Our tooling relies on the same assumption yours does, which is why the directory had to be moved at the same time that the pkgbase got changed... But, the tooling relies on it at the time of publishing only.

So this is really just a matter of the timing around the pkgbase change and a testing package happening at the same time. Sometimes (uncommonly) only trunk/ works, and that's just the way it is

Loading...