don't reverse change order when handling crates.io index updates

Author: syphar

src/build_queue.rs

@@ -290,9 +290,6 @@ impl BuildQueue {
 
         debug!("queueing changes from {last_seen_reference} to {new_reference}");
 
-        // I believe this will fix ordering of queue if we get more than one crate from changes
-        changes.reverse();
-
         for change in &changes {
             if let Some((ref krate, ..)) = change.crate_deleted() {
                 match delete_crate(&mut conn, &self.storage, &self.config, krate)