Community Packages

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#62671 - [exploitdb 20190427-1] does not update

Attached to Project: Community Packages
Opened by TheTruth (TheTruth) - Saturday, 18 May 2019, 13:27 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 19 May 2019, 03:38 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Eli Schwartz (eschwartz)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
1) Fresh install of exploitdb (https://www.archlinux.org/packages/community/any/exploitdb/)
2) Use the update command of searchsploit (searchsploit -u)
3) Git fetches/pulls the repository but aborts
3.1) error: The following untracked working tree files would be overwritten by merge: ...
3.2) After abort it updates exploitdb-papers [works]


Additional info:
* package version(s)
The package can be found in https://www.archlinux.org/packages/community/any/exploitdb/

* config and/or log files etc.
see attachment


Steps to reproduce:
`searchsploit -u`
   searchsploit_update_log.txt (9.8 KiB)
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Sunday, 19 May 2019, 03:38 GMT
Reason for closing:  Won't fix
Comment by Eli Schwartz (eschwartz) - Sunday, 19 May 2019, 03:37 GMT
The update command is designed to assume that your db sources as defined in /etc/searchsploit_rc are a git repository, and it will then edit that, which is not generally considered a good thing for root-owned files (in /usr/share). The package will definitely not package a .git directory for this purpose, and I don't wish to encourage updating pacman-owned files as root either way.

Note that you can configure /etc/searchsploit_rc or better yet "${HOME}/.searchsploit_rc" to point to a different location, and keep a more up-to-date copy of the exploitdb anywhere you like. This is my advice if you want to keep e.g. daily updates.

As for the system package, I try to update it every week or two, and I have just pushed another update now, containing the latest exploits/shellcodes.

Loading...