Quoting Jonas Smedegaard (2014-06-28 19:09:32)
Quoting Niko Tyni (2014-06-28 09:03:08)
Perhaps something like this (untested) could work?
Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40),
libmodule-build-perl
(The unversioned dependency would guarantee either a perl
On Wed, 02 Jul 2014 14:26:09 +0200, Jonas Smedegaard wrote:
Hmm, I am getting doubts again...
Let's see ...
Niko's declaration, with Gregor's correction, is this:
Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40),
libmodule-build-perl
That declaration relies on
On Wed, Jul 02, 2014 at 07:49:12PM +0200, gregor herrmann wrote:
On Wed, 02 Jul 2014 14:26:09 +0200, Jonas Smedegaard wrote:
Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40),
libmodule-build-perl
That declaration relies on the assumption that any system with a new
On Wed, 02 Jul 2014 22:02:32 +0300, Niko Tyni wrote:
Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40),
libmodule-build-perl
For a future perl-modules 5.22, if the Breaks is kept, everything
should be fine. If the Breaks is dropped there is indeed a loophole
(for
Package: libio-callback-perl
Version: 1.12-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.20-transition
This package fails to build from source with Perl 5.20 (currently in
experimental) and sbuild:
The following packages have unmet dependencies:
Quoting Niko Tyni (2014-06-28 09:03:08)
This package fails to build from source with Perl 5.20 (currently in
experimental) and sbuild:
The following packages have unmet dependencies:
sbuild-build-depends-libio-callback-perl-dummy : Depends: perl ( 5.19)
but 5.20.0-1 is to be installed
On Sat, 28 Jun 2014 09:41:46 +0200, Jonas Smedegaard wrote:
libmodule-build-perl exists as a package, so simply favoring that over
the perl-provided version should work _and_ be deterministic _and_ work
on more relaxed environments permitting undetermnistic fallbacks (read:
backporting
On Sat, Jun 28, 2014 at 09:41:46AM +0200, Jonas Smedegaard wrote:
Quoting Niko Tyni (2014-06-28 09:03:08)
The problem is this dependency:
Build-Depends: perl ( 5.19) | libmodule-build-perl (= 0.40),
Perhaps something like this (untested) could work?
Build-Depends: perl (=
Quoting Niko Tyni (2014-06-28 13:44:57)
On Sat, Jun 28, 2014 at 09:41:46AM +0200, Jonas Smedegaard wrote:
Quoting Niko Tyni (2014-06-28 09:03:08)
The problem is this dependency:
Build-Depends: perl ( 5.19) | libmodule-build-perl (= 0.40),
Perhaps something like this (untested) could work?
On Sat, 28 Jun 2014 14:18:13 +0200, Jonas Smedegaard wrote:
Fine by me, but that allows for perl 5.16 and lower, which have M::B
0.40. If that's not a concern, just drop the versioned part and use
plain libmodule-build-perl?
Right. If that's a concern (it is to me, but some consider
On Sat, Jun 28, 2014 at 02:18:13PM +0200, Jonas Smedegaard wrote:
Quoting Niko Tyni (2014-06-28 13:44:57)
On Sat, Jun 28, 2014 at 09:41:46AM +0200, Jonas Smedegaard wrote:
Relying on a (build-)dependency being resolved by a virtual package
is not allowed by Policy, with the reasoning that
Quoting Niko Tyni (2014-06-28 14:57:01)
On Sat, Jun 28, 2014 at 02:18:13PM +0200, Jonas Smedegaard wrote:
Quoting Niko Tyni (2014-06-28 13:44:57)
On Sat, Jun 28, 2014 at 09:41:46AM +0200, Jonas Smedegaard wrote:
Relying on a (build-)dependency being resolved by a virtual package
is not
On Sat, Jun 28, 2014 at 03:31:29PM +0200, Jonas Smedegaard wrote:
I don't understand. Do you not find it relevant for perl modules to
declare to declare dependencies and build-dependencies
deterministically, or do you find that this particular use of | does
not affect determinism?
The
Quoting Niko Tyni (2014-06-28 09:03:08)
Perhaps something like this (untested) could work?
Build-Depends: perl (= 5.17.1~) | libmodule-build-perl (= 0.40),
libmodule-build-perl
(The unversioned dependency would guarantee either a perl version with
the bundled M::B, or a separate
14 matches
Mail list logo
