[med-svn] [Git][med-team/plink1-9][master] Bump changelogs

Dylan Aïssi gitlab at salsa.debian.org
Wed Nov 11 09:23:56 GMT 2020



Dylan Aïssi pushed to branch master at Debian Med / plink1.9


Commits:
14fceb7e by Dylan Aïssi at 2020-11-11T10:23:43+01:00
Bump changelogs

- - - - -


2 changed files:

- debian/changelog
- debian/upstream.docs/upstream.changelog


Changes:

=====================================
debian/changelog
=====================================
@@ -1,3 +1,9 @@
+plink1.9 (1.90~b6.21-201019-1) UNRELEASED; urgency=medium
+
+  * New upstream release.
+
+ -- Dylan Aïssi <daissi at debian.org>  Wed, 11 Nov 2020 10:21:53 +0100
+
 plink1.9 (1.90~b6.18-200616-1) unstable; urgency=medium
 
   * New upstream release.


=====================================
debian/upstream.docs/upstream.changelog
=====================================
@@ -1,6 +1,12 @@
 # Copy/Paste from https://www.cog-genomics.org/plink/1.9/
 
-16 Jun 2020: Fixed --het bug that caused the wrong variants to be skipped when chrM was present but not at the end of the file.
+19 Oct 2020: Linux binaries no longer default to allowing Intel MKL to use processor-specific code paths, since this behavior made some results more difficult to reproduce across different machines. (This may make some commands a bit slower. You can remove this restriction with --native.)
+
+21 Sep: Fixed --logistic bug that could cause the entire analysis to be skipped with an inaccurate "Skipping --linear/--logistic since phenotype is constant" warning.
+
+16 Sep: Fixed --qfam bug that occurred when a variant filter (--extract, --maf, etc.) was applied simultaneously, and the remaining variant set was not contiguous (so if your only variant filter was --chr on a single chromosome, this bug did not trigger). The bug was pretty obvious if you were affected by it (the .within and .within.perm output files had mismatched variant IDs), but if you're unsure you should rerun --qfam with the latest build.
+
+16 Jun: Fixed --het bug that caused the wrong variants to be skipped when chrM was present but not at the end of the file.
 
 28 Apr: Fixed --allow-extra-chr + --autosome-num/--cow/... segfault that could occur when the chromosome-set flag prohibited X/Y/XY/MT but that chromosome code was in the dataset anyway; an appropriate error message is now printed instead. --ld-window-r2 can now be used with --r.
 



View it on GitLab: https://salsa.debian.org/med-team/plink1-9/-/commit/14fceb7e43236897e89388e3cf95f1a7f192bd41

-- 
View it on GitLab: https://salsa.debian.org/med-team/plink1-9/-/commit/14fceb7e43236897e89388e3cf95f1a7f192bd41
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-med-commit/attachments/20201111/2041300b/attachment-0001.html>


More information about the debian-med-commit mailing list