Your message dated Mon, 10 Aug 2020 23:40:13 +0200
with message-id <20200810214013.ga22...@ramacher.at>
and subject line Re: Bug#968066: haskell-hgettext: autopkgtest fails with newer
version of ghc
has caused the Debian Bug report #968066,
regarding haskell-hgettext: autopkgtest fails with newer version of ghc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
968066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hgettext
Version: 0.1.31.0-5
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ghc
Dear maintainer(s),
With a recent upload of ghc the autopkgtest of haskell-hgettext fails in
testing when that autopkgtest is run with the binary packages of ghc
from unstable. It passes when run with only packages from testing. In
tabular form:
pass fail
ghc from testing 8.8.3-3
haskell-hgettext from testing 0.1.31.0-5
versioned deps [0] from testing from unstable
all others from testing from testing
I copied some of the output at the bottom of this report. It seems there
is some versioned dependency missing somewhere, either in the test
definition or in package itself, or something really breaks
haskell-hgettext in testing and doesn't declare it. If I read the error
correctly and understand a tiny bit of the haskell packaging, something
should prevent mix and match of packages build with different versions
of ghc.
Currently this regression is blocking the migration of ghc to testing
[1]. Of course, ghc shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in ghc was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from ghc should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
ghc/8.8.3-3. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=ghc
https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hgettext/6551760/log.gz
autopkgtest [14:11:27]: test cabal-install-compatibility:
[-----------------------
Warning: No remote package servers have been specified. Usually you
would have
one specified in the config file.
Resolving dependencies...
cabal: Could not resolve dependencies:
[__0] trying: example-0.1.0 (user goal)
[__1] next goal: example:setup.Cabal (dependency of example)
[__1] rejecting: example:setup.Cabal-3.0.1.0/installed-3.0... (conflict:
example => example:setup.Cabal>=1.8 && <1.25)
[__1] fail (backjumping, conflict set: example, example:setup.Cabal)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: example, example:setup.Cabal
autopkgtest [14:11:28]: test cabal-install-compatibility:
-----------------------]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.1.31.0-7
On 2020-08-07 21:40:24 +0200, Paul Gevers wrote:
> Source: haskell-hgettext
> Version: 0.1.31.0-5
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:ghc
>
> Dear maintainer(s),
>
> With a recent upload of ghc the autopkgtest of haskell-hgettext fails in
> testing when that autopkgtest is run with the binary packages of ghc
> from unstable. It passes when run with only packages from testing. In
> tabular form:
>
> pass fail
> ghc from testing 8.8.3-3
> haskell-hgettext from testing 0.1.31.0-5
> versioned deps [0] from testing from unstable
> all others from testing from testing
>
> I copied some of the output at the bottom of this report. It seems there
> is some versioned dependency missing somewhere, either in the test
> definition or in package itself, or something really breaks
> haskell-hgettext in testing and doesn't declare it. If I read the error
> correctly and understand a tiny bit of the haskell packaging, something
> should prevent mix and match of packages build with different versions
> of ghc.
>
> Currently this regression is blocking the migration of ghc to testing
> [1]. Of course, ghc shouldn't just break your autopkgtest (or even
> worse, your package), but it seems to me that the change in ghc was
> intended and your package needs to update to the new situation.
>
> If this is a real problem in your package (and not only in your
> autopkgtest), the right binary package(s) from ghc should really add a
> versioned Breaks on the unfixed version of (one of your) package(s).
> Note: the Breaks is nice even if the issue is only in the autopkgtest as
> it helps the migration software to figure out the right versions to
> combine in the tests.
>
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
>
> Paul
>
> [0] You can see what packages were added from the second line of the log
> file quoted below. The migration software adds source package from
> unstable to the list if they are needed to install packages from
> ghc/8.8.3-3. I.e. due to versioned dependencies or breaks/conflicts.
> [1] https://qa.debian.org/excuses.php?package=ghc
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hgettext/6551760/log.gz
>
> autopkgtest [14:11:27]: test cabal-install-compatibility:
> [-----------------------
> Warning: No remote package servers have been specified. Usually you
> would have
> one specified in the config file.
> Resolving dependencies...
> cabal: Could not resolve dependencies:
> [__0] trying: example-0.1.0 (user goal)
> [__1] next goal: example:setup.Cabal (dependency of example)
> [__1] rejecting: example:setup.Cabal-3.0.1.0/installed-3.0... (conflict:
> example => example:setup.Cabal>=1.8 && <1.25)
> [__1] fail (backjumping, conflict set: example, example:setup.Cabal)
> After searching the rest of the dependency tree exhaustively, these were the
> goals I've had most trouble fulfilling: example, example:setup.Cabal
>
> autopkgtest [14:11:28]: test cabal-install-compatibility:
> -----------------------]
This issue has been fixed in unstable:
--- haskell-hgettext-0.1.31.0/debian/patches/newer-src-exts 1970-01-01
01:00:00.000000000 +0100
+++ haskell-hgettext-0.1.31.0/debian/patches/newer-src-exts 2020-07-30
13:22:57.000000000 +0200
@@ -0,0 +1,22 @@
+--- a/hgettext.cabal
++++ b/hgettext.cabal
+@@ -31,8 +31,8 @@
+ other-modules: Internal
+
+ hs-source-dirs: src
+- build-depends: base >=4.5 && <4.13
+- , Cabal >=1.14 && <1.25 || == 2.0.* || ==
2.2.* || == 2.4.*
++ build-depends: base >=4.5 && <5
++ , Cabal >=1.14
+ , containers >=0.4.2 && <0.7
+ , directory >=1.1 && <1.4
+ , filepath >=1.3 && <1.5
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
