On 2012-05-29 19:50, Tomasz Rybak wrote:
Thanks for the explanation.
I have decided to put:
Replaces: python-pyopencl ( 2011.2+git20120508-1)
Breaks: python-pyopencl ( ${source:Version}),
python-pyopencl ( ${source:Version}),
python3-pyopencl ( ${source:Version}),
python3-pyopencl (
On 2012-05-27 21:06, Tomasz Rybak wrote:
Should I put
Breaks/Replaces: python-pyopencl ( 2011.2.2+git20120508-1)
or
Breaks/Replaces: python-pyopencl ( ${source:Version})?
Policy 7.6 uses hard-coded version, but many packages put
${source:Version} into debian/control. What is advised?
A
Dnia 2012-05-29, wto o godzinie 11:33 +0200, Andreas Beckmann pisze:
On 2012-05-27 21:06, Tomasz Rybak wrote:
Should I put
Breaks/Replaces: python-pyopencl ( 2011.2.2+git20120508-1)
or
Breaks/Replaces: python-pyopencl ( ${source:Version})?
Policy 7.6 uses hard-coded version, but many
Dnia 2012-05-22, wto o godzinie 14:10 +0200, Andreas Beckmann pisze:
Package: python-pyopencl-headers
Version: 2011.2+git20120508-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
Package: python-pyopencl-headers
Version: 2011.2+git20120508-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'unstable' fails
5 matches
Mail list logo