Hello community,

here is the log from the commit of package ghc-stm-chans for openSUSE:Factory 
checked in at 2018-05-30 12:20:40
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/ghc-stm-chans (Old)
 and      /work/SRC/openSUSE:Factory/.ghc-stm-chans.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "ghc-stm-chans"

Wed May 30 12:20:40 2018 rev:4 rq:609819 version:3.0.0.4

Changes:
--------
--- /work/SRC/openSUSE:Factory/ghc-stm-chans/ghc-stm-chans.changes      
2017-09-15 22:14:21.034820786 +0200
+++ /work/SRC/openSUSE:Factory/.ghc-stm-chans.new/ghc-stm-chans.changes 
2018-05-30 12:27:18.718266874 +0200
@@ -1,0 +2,7 @@
+Wed May 16 14:36:28 UTC 2018 - [email protected]
+
+- Prefer the new %license attribute over %doc.
+- Update Cabal file to revision 1.
+  * add missing "setup-depends" stanza
+
+-------------------------------------------------------------------

New:
----
  stm-chans.cabal

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

Other differences:
------------------
++++++ ghc-stm-chans.spec ++++++
--- /var/tmp/diff_new_pack.9kwdsn/_old  2018-05-30 12:27:19.442241744 +0200
+++ /var/tmp/diff_new_pack.9kwdsn/_new  2018-05-30 12:27:19.446241605 +0200
@@ -25,6 +25,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/1.cabal#/%{pkg_name}.cabal
 BuildRequires:  ghc-Cabal-devel
 BuildRequires:  ghc-rpm-macros
 BuildRequires:  ghc-stm-devel
@@ -45,6 +46,7 @@
 
 %prep
 %setup -q -n %{pkg_name}-%{version}
+cp -p %{SOURCE1} %{pkg_name}.cabal
 
 %build
 %ghc_lib_build
@@ -59,7 +61,7 @@
 %ghc_pkg_recache
 
 %files -f %{name}.files
-%doc LICENSE
+%license LICENSE
 
 %files devel -f %{name}-devel.files
 %doc AUTHORS CHANGELOG README

++++++ stm-chans.cabal ++++++
----------------------------------------------------------------
-- wren gayle romano <[email protected]>   ~ 2015.05.30
----------------------------------------------------------------

-- By and large Cabal >=1.2 is fine; but >= 1.6 gives tested-with:
-- and source-repository:.
Cabal-Version:  >= 1.6
-- We need a custom build in order to define __HADDOCK__
Build-Type:     Custom

Name:           stm-chans
Version:        3.0.0.4
x-revision: 1
Stability:      provisional
Homepage:       http://code.haskell.org/~wren/
Author:         wren gayle romano, Thomas DuBuisson
Maintainer:     [email protected]
Copyright:      Copyright (c) 2011--2015 wren gayle romano
License:        BSD3
License-File:   LICENSE

Category:       Concurrency
Synopsis:       Additional types of channels for STM.
Description:    Additional types of channels for STM.

-- Should probably still work with GHC-7.6.1 too
Tested-With:
    GHC ==7.8.3, GHC ==7.10.1
Extra-source-files:
    AUTHORS, README, CHANGELOG

custom-setup
    setup-depends: Cabal >= 1.6, base >= 4.1 && < 5

Source-Repository head
    Type:     darcs
    Location: http://community.haskell.org/~wren/stm-chans

----------------------------------------------------------------
Library
    -- N.B., the following versions are required for:
    -- * stm >= 2.4:   T{,B}Queue and newBroadcastTChan{,IO}
    -- * stm >= 2.3.0: fast tryReadTChan, peekTChan, tryPeekTChan,
    --         tryReadTMVar, modifyTVar, modifyTVar', swapTVar.
    -- * stm >= 2.1.2: fast readTVarIO.
    --
    -- Not sure what the real minbound is for base...
    Build-Depends: base >= 4.1 && < 5
                 , stm  >= 2.4

    Hs-Source-Dirs:  src
    Exposed-Modules: Control.Concurrent.STM.TBChan
                   , Control.Concurrent.STM.TBMChan
                   , Control.Concurrent.STM.TMChan
                   , Control.Concurrent.STM.TBMQueue
                   , Control.Concurrent.STM.TMQueue

----------------------------------------------------------------
----------------------------------------------------------- fin.

Reply via email to