Hello community,

here is the log from the commit of package ghc-hackage-security for 
openSUSE:Factory checked in at 2019-06-19 21:10:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/ghc-hackage-security (Old)
 and      /work/SRC/openSUSE:Factory/.ghc-hackage-security.new.4811 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "ghc-hackage-security"

Wed Jun 19 21:10:40 2019 rev:12 rq:710627 version:0.5.3.0

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/ghc-hackage-security/ghc-hackage-security.changes    
    2018-10-25 08:21:37.175930908 +0200
+++ 
/work/SRC/openSUSE:Factory/.ghc-hackage-security.new.4811/ghc-hackage-security.changes
      2019-06-19 21:12:15.358734087 +0200
@@ -1,0 +2,5 @@
+Tue Jun 11 14:29:11 UTC 2019 - Peter Simons <psim...@suse.com>
+
+- Update Cabal file for more accurate build dependencies.
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ ghc-hackage-security.spec ++++++
--- /var/tmp/diff_new_pack.T3YUlP/_old  2019-06-19 21:12:16.306735008 +0200
+++ /var/tmp/diff_new_pack.T3YUlP/_new  2019-06-19 21:12:16.306735008 +0200
@@ -1,7 +1,7 @@
 #
 # spec file for package ghc-hackage-security
 #
-# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
+# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -26,7 +26,7 @@
 Group:          Development/Libraries/Haskell
 URL:            https://hackage.haskell.org/package/%{pkg_name}
 Source0:        
https://hackage.haskell.org/package/%{pkg_name}-%{version}/%{pkg_name}-%{version}.tar.gz
-Source1:        
https://hackage.haskell.org/package/%{pkg_name}-%{version}/revision/3.cabal#/%{pkg_name}.cabal
+Source1:        
https://hackage.haskell.org/package/%{pkg_name}-%{version}/revision/6.cabal#/%{pkg_name}.cabal
 BuildRequires:  ghc-Cabal-devel
 BuildRequires:  ghc-base16-bytestring-devel
 BuildRequires:  ghc-base64-bytestring-devel

++++++ hackage-security.cabal ++++++
--- /var/tmp/diff_new_pack.T3YUlP/_old  2019-06-19 21:12:16.350735050 +0200
+++ /var/tmp/diff_new_pack.T3YUlP/_new  2019-06-19 21:12:16.350735050 +0200
@@ -1,7 +1,7 @@
 cabal-version:       1.12
 name:                hackage-security
 version:             0.5.3.0
-x-revision: 3
+x-revision: 6
 
 synopsis:            Hackage security library
 description:         The hackage security library provides both server and
@@ -103,7 +103,7 @@
                        base16-bytestring >= 0.1.1   && < 0.2,
                        base64-bytestring >= 1.0     && < 1.1,
                        bytestring        >= 0.9     && < 0.11,
-                       Cabal             >= 1.14    && < 2.6,
+                       Cabal             >= 1.14    && < 3.2,
                        containers        >= 0.4     && < 0.7,
                        ed25519           >= 0.0     && < 0.1,
                        filepath          >= 1.2     && < 1.5,
@@ -114,7 +114,7 @@
                        -- 0.4.2 introduces TarIndex, 0.4.4 introduces more
                        -- functionality, 0.5.0 changes type of serialise
                        tar               >= 0.5     && < 0.6,
-                       time              >= 1.2     && < 1.9,
+                       time              >= 1.2     && < 1.10,
                        transformers      >= 0.4     && < 0.6,
                        zlib              >= 0.5     && < 0.7,
                        -- whatever versions are bundled with ghc:
@@ -201,7 +201,7 @@
   -- dependency in network is not redundant.)
   if flag(use-network-uri)
     build-depends: network-uri >= 2.6 && < 2.7,
-                   network     >= 2.6 && < 2.9
+                   network     >= 2.6 && < 2.9 || >= 3.0 && < 3.2
   else
     build-depends: network     >= 2.5 && < 2.6
 


Reply via email to