On Sun, 2 Feb 2003 08:15, Ben Burton wrote:
> > > Perhaps I should just bite the bullet and put a 4: epoch on all of the
> > > packages that are going into sid. Though in general there have been so
> >
> > Yes, that is the best thing to do.
>
> Yep, I'm going to do that. After all, our users are
> > Perhaps I should just bite the bullet and put a 4: epoch on all of the
> > packages that are going into sid. Though in general there have been so
>
> Yes, that is the best thing to do.
Yep, I'm going to do that. After all, our users are our priority, etc
etc etc, and this will at least hel
On Sun, 2 Feb 2003 00:17, Ben Burton wrote:
> Perhaps I should just bite the bullet and put a 4: epoch on all of the
> packages that are going into sid. Though in general there have been so
Yes, that is the best thing to do.
When I started maintaining KDE packages some of them had an epoch of 4:
Ben Burton wrote:
> This means that your system will *not* smoothly upgrade to the 3.1
> packages that will be uploaded to sid. In this case probably the
> easiest solution is to remove all of the affected packages and then
> reinstall them as you normally would in dselect or whatever package
> m
Hi all. I've had a couple of instances of this problem land in my inbox
just this morning so I figured I'd send a general mailout in the hope of
reducing the problem.
Various unofficial package repositories have at various times used the
incorrect epochs in their package versions. An epoch is t
5 matches
Mail list logo
