"Wesley J. Landaker" writes:
> On Friday 05 February 2010 04:43:05 Hideki Yamane wrote:
>> > This is true in general, although it's perhaps worth noting that a rare
>> > pre- depends on a priority required package like debconf by a priority
>> > optional or extra package isn't likely to cause any
On Fri, 5 Feb 2010 14:00:47 -0200
Rogério Brito wrote:
> > BTW, I would rename tomoyo-ccstools to tomoyo-ccstools1.7 and not
> > provide upgrade path for that. If I just would upgrade this pacakge,
> > it'll break system that it works with security policies for 1.6.x, so
> > I should leave it and
On Friday 05 February 2010 04:43:05 Hideki Yamane wrote:
> > This is true in general, although it's perhaps worth noting that a rare
> > pre- depends on a priority required package like debconf by a priority
> > optional or extra package isn't likely to cause any trouble.
>
> Yes, it is true in g
On Feb 05 2010, Hideki Yamane wrote:
> BTW, I would rename tomoyo-ccstools to tomoyo-ccstools1.7 and not
> provide upgrade path for that. If I just would upgrade this pacakge,
> it'll break system that it works with security policies for 1.6.x, so
> I should leave it and provide README.Debian for u
On Thu, 4 Feb 2010 21:01:12 -0700
"Wesley J. Landaker" wrote:
> > It adds additional strong restrictions on the order in which packages
> > must be upgraded. Too many such restrictions and there might not be a
> > way to upgrade at all. Somewhere before that you (via apt/aptitutde/...)
> > get the
On Thursday 04 February 2010 10:49:28 Goswin von Brederlow wrote:
> Hideki Yamane writes:
> > And I have a question - why should we avoid using pre-depends?
> > What kind of problem would it cause?
> > (it doesn't mean I want to use pre-depends, just curious)
>
> It adds additional strong rest
Hideki Yamane writes:
> Hi Matthew,
>
> On Wed, 3 Feb 2010 16:04:13 +1100
> Matthew Palmer wrote:
>> In short: you don't.
>>
>> You should make it clear in the NEWS.Debian file that there are
>> compatibility issues, and your README.Debian should describe how to perform
>> an upgrade manually (
Hi Matthew,
On Wed, 3 Feb 2010 16:04:13 +1100
Matthew Palmer wrote:
> In short: you don't.
>
> You should make it clear in the NEWS.Debian file that there are
> compatibility issues, and your README.Debian should describe how to perform
> an upgrade manually (or point to upstream documentation f
On Wed, Feb 03, 2010 at 01:43:49PM +0900, Hideki Yamane wrote:
> I'm thinking about tomoyo-ccstools package update but it has a problem.
> It has no compatibility with current version (1.6.8) and newer version
> (1.7.1). So, I want users would be able to choice continue upgrading or
> not with
Hi,
I'm thinking about tomoyo-ccstools package update but it has a problem.
It has no compatibility with current version (1.6.8) and newer version
(1.7.1). So, I want users would be able to choice continue upgrading or
not with debconf.
I wrote that, but there's a problem - it compares vers
10 matches
Mail list logo
