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!
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!
FS#54994 - [devtools] makechrootpkg leaves behind empty directory tree if download of source failed
Attached to Project:
Arch Linux
Opened by Erich Eckner (deepthought) - Monday, 31 July 2017, 18:20 GMT
Last edited by Levente Polyak (anthraxx) - Tuesday, 22 January 2019, 01:01 GMT
Opened by Erich Eckner (deepthought) - Monday, 31 July 2017, 18:20 GMT
Last edited by Levente Polyak (anthraxx) - Tuesday, 22 January 2019, 01:01 GMT
|
DetailsIf 'makepkg ... --verifysource' inside makechrootpkg's 'download_source()' fails, the temporary directory is not being removed, leaving behind an empty directory tree of the structure 'tmp.XXXXXX/foobar/src' for package foobar.
The attached patch (against git revision 75fdff1811a0487f82c75b2e260da905102b4eea) will get rid of the directories if the said command failed. It would be nice, if you could include it in the source - otherwise the 32-bit build slaves will be jammed with a lot temporary directories :-) If you don't want to include it, let me know (and possibly a reason therefore), and I will probably patch it into our fork of the devtools. Cheers, deep42thought |
This task depends upon
Closed by Levente Polyak (anthraxx)
Tuesday, 22 January 2019, 01:01 GMT
Reason for closing: Implemented
Additional comments about closing: fixed in git 8310abb3485bdf63fc3557e3020a43f9f9e03927
Tuesday, 22 January 2019, 01:01 GMT
Reason for closing: Implemented
Additional comments about closing: fixed in git 8310abb3485bdf63fc3557e3020a43f9f9e03927
This has been corrected in the attached patch (which now also is being tested / has been tested in the archlinux32 build system).
sry, I should have done this before :-/