diff --git a/coverage-4.3.4.tar.gz b/coverage-4.3.4.tar.gz
deleted file mode 100644
index d89fc62..0000000
--- a/coverage-4.3.4.tar.gz
+++ /dev/null
@@ -1,3 +0,0 @@
-version https://git-lfs.github.com/spec/v1
-oid sha256:eaaefe0f6aa33de5a65f48dd0040d7fe08cac9ac6c35a56d0a7db109c3e733df
-size 361491
diff --git a/coverage-4.4.1.tar.gz b/coverage-4.4.1.tar.gz
new file mode 100644
index 0000000..e10f39f
--- /dev/null
+++ b/coverage-4.4.1.tar.gz
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7a9c44400ee0f3b4546066e0710e1250fd75831adc02ab99dda176ad8726f424
+size 369789
diff --git a/python-coverage.changes b/python-coverage.changes
index e109edf..3054dd5 100644
--- a/python-coverage.changes
+++ b/python-coverage.changes
@@ -1,3 +1,53 @@
+-------------------------------------------------------------------
+Wed Oct  4 15:47:22 UTC 2017 - arun@gmx.de
+
+- update to version 4.4.1:
+  * No code changes: just corrected packaging for Python 2.7 Linux
+    wheels.
+
+- changes from version 4.4:
+  * Reports could produce the wrong file names for packages, reporting
+    pkg.py instead of the correct pkg/__init__.py. This is now
+    fixed. Thanks, Dirk Thomas.
+  * XML reports could produce <source> and <class> lines that together
+    didn’t specify a valid source file path. This is now fixed. (issue
+    526)
+  * Namespace packages are no longer warned as having no code. (issue
+    572)
+  * Code that uses sys.settrace(sys.gettrace()) in a file that wasn’t
+    being coverage-measured would prevent correct coverage measurement
+    in following code. An example of this was running doctests
+    programmatically. This is now fixed. (issue 575)
+  * Errors printed by the coverage command now go to stderr instead of
+    stdout.
+  * Running coverage xml in a directory named with non-ASCII
+    characters would fail under Python 2. This is now fixed. (issue
+    573)
+
+- changes from version 4.4b1:
+  * Some warnings can now be individually disabled. Warnings that can
+    be disabled have a short name appended. The [run] disable_warnings
+    setting takes a list of these warning names to disable. Closes
+    both issue 96 and issue 355.
+  * The XML report now includes attributes from version 4 of the
+    Cobertura XML format, fixing issue 570.
+  * In previous versions, calling a method that used collected data
+    would prevent further collection. For example, save(), report(),
+    html_report(), and others would all stop collection. An explicit
+    start() was needed to get it going again. This is no longer
+    true. Now you can use the collected data and also continue
+    measurement. Both issue 79 and issue 448 described this problem,
+    and have been fixed.
+  * Plugins can now find unexecuted files if they choose, by
+    implementing the find_executable_files method. Thanks, Emil
+    Madsen.
+  * Minimal IronPython support. You should be able to run IronPython
+    programs under coverage run, though you will still have to do the
+    reporting phase with CPython.
+  * Coverage.py has long had a special hack to support CPython’s need
+    to measure the coverage of the standard library tests. This code
+    was not installed by kitted versions of coverage.py. Now it is.
+
 -------------------------------------------------------------------
 Fri Aug 11 15:25:50 UTC 2017 - toddrme2178@gmail.com
 
diff --git a/python-coverage.spec b/python-coverage.spec
index 7464527..a413b7a 100644
--- a/python-coverage.spec
+++ b/python-coverage.spec
@@ -18,7 +18,7 @@
 
 %{?!python_module:%define python_module() python-%{**} python3-%{**}}
 Name:           python-coverage
-Version:        4.3.4
+Version:        4.4.1
 Release:        0
 Url:            http://nedbatchelder.com/code/coverage/%{version}
 Summary:        Code coverage measurement for Python