Do not refer to FlySpray numbers

These references to bug numbers assume we will forever be using that bug
tracker. It is better to properly comment the code instead (which was
done in almost all cases anyway).

Signed-off-by: Allan McRae <allan@archlinux.org>

2 files changed, 2 insertions, 2 deletions

diff --git a/lib/libalpm/add.c b/lib/libalpm/add.c
index 45c57b05..ac4e36a6 100644
--- a/lib/libalpm/add.c
+++ b/lib/libalpm/add.c
@@ -530,7 +530,7 @@ static int commit_single_pkg(alpm_handle_t *handle, alpm_pkg_t *newpkg,
 	}
 
 	/* prepare directory for database entries so permission are correct after
-	   changelog/install script installation (FS#12263) */
+	   changelog/install script installation */
 	if(_alpm_local_db_prepare(db, newpkg)) {
 		alpm_logaction(handle, ALPM_CALLER_PREFIX,
 				"error: could not create database entry %s-%s\n",
diff --git a/lib/libalpm/dload.c b/lib/libalpm/dload.c
index 342afbc2..8537b3db 100644
--- a/lib/libalpm/dload.c
+++ b/lib/libalpm/dload.c
@@ -466,7 +466,7 @@ static int curl_download_internal(struct dload_payload *payload,
 
 	/* disconnect relationships from the curl handle for things that might go out
 	 * of scope, but could still be touched on connection teardown.  This really
-	 * only applies to FTP transfers. See FS#26327 for an example. */
+	 * only applies to FTP transfers. */
 	curl_easy_setopt(curl, CURLOPT_NOPROGRESS, 1L);
 	curl_easy_setopt(curl, CURLOPT_ERRORBUFFER, (char *)NULL);