Hi
Fixing this bug either means getting rid of the conflict in the
binutils-mingw-w64 packages (and probably have replaces with breaks
instead) or having mingw32-ocaml depend on mingw32 instead of mingw-w64
(through mingw-ocaml).
Cheers
Luk
--
To UNSUBSCRIBE, email to
Hi,
On Fri, Apr 06, 2012 at 12:09:14AM +0200, David Kalnischkies wrote:
For mingw32-ocaml the reason is:
binutils-mingw-w64-i686 Conflicts on mingw32-binutils
The naming is again to confusing for me now to inspect it deeper now,
but i guess the transition from mingw32 to mingw64 is messed up.
On 04/07/12 22:51, Stephen Kitt wrote:
Re-reading policy section 7 leads me to believe that the correct
approach is a Conflicts/Replaces relationship: mingw-w64-binutils-i686
Breaks should be preferred over Conflicts in such case. (I'm not sure it
makes a difference though).
--
Mehdi
--
On Wed, Jul 04, 2012 at 10:58:18PM +0200, Mehdi Dogguy wrote:
On 04/07/12 22:51, Stephen Kitt wrote:
Re-reading policy section 7 leads me to believe that the correct
approach is a Conflicts/Replaces relationship: mingw-w64-binutils-i686
Breaks should be preferred over Conflicts in such case.
Hi,
2012/3/6 Stéphane Glondu glo...@debian.org:
Le 06/03/2012 08:18, Andreas Beckmann a écrit :
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.
[...]
Precision: it fails when using apt,
Package: mingw32-ocaml
Version: 3.12.1+debian2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.
From the attached log
Le 06/03/2012 08:18, Andreas Beckmann a écrit :
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.
[...]
Precision: it fails when using apt, but it works using aptitude.
Could you please
7 matches
Mail list logo
