Hello,
2011/12/30 Paul Wise p...@debian.org:
I suggest that you contact upstream to find out why they do not use
versioned names for the plugin-related files.
They plan to do that but in the long run along with other changes,
probably it won't happen in the upcoming 1.8 series (which were
2012/1/19 Manuel A. Fernandez Montecelo manuel.montez...@gmail.com:
[...]
This is not fixed yet, but I am unconvinced about the utility of such
script and if it was for me I would remove it altogether, as I did
with other ad-hoc script in the package which was not even shipped. I
will
Hi Paul,
2011/12/29 Paul Wise p...@debian.org:
The following files are in violation of policy section 8.2. Please move
them to a different package and then drop the Breaks on all the old
versions of libogremain.
I don't doubt that you are right, but there are some complications and
I hope
On Thu, 2011-12-29 at 13:04 +, Manuel A. Fernandez Montecelo wrote:
What do you think?
I suggest that you contact upstream to find out why they do not use
versioned names for the plugin-related files.
Your solution sounds fine, I'm not sure if it will work for these:
libogre-1.7.3:
Package: libogre-1.7.3
Version: 1.7.3-1
Severity: serious
Justification: Policy 8.2
The following files are in violation of policy section 8.2. Please move
them to a different package and then drop the Breaks on all the old
versions of libogremain.
libogre-1.7.3: /etc/OGRE/plugins.cfg
5 matches
Mail list logo
