[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Adding epoch to kworkflow package to correct a wrong upstream version



On 03/12, Tobias Frost wrote:
> On Sat, Mar 11, 2023 at 06:35:39PM -0700, Rodrigo Siqueira wrote:
> > Hi,
> > 
> > While working on a new version of the kworkflow package
> > (https://tracker.debian.org/pkg/kworkflow), we noticed that the current
> > version is 20191112-1.2, and the latest upstream version is 0.6.2.
> > Version 20191112-1.2 was created because the upstream had no official
> > release at that time; for this reason, the 20191112-1.2 was created and
> > named based on a date.
> > 
> > This package did not get any update in a long time, and now the upstream
> > release frequent versions. The latest version is 0.6.2
> > (https://github.com/kworkflow/kworkflow/tags), and I'm trying to release
> > a new version of this package
> > (https://salsa.debian.org/siqueira/kworkflow/-/tree/master/debian). So,
> > to do a clean update, we should add  1:0.6.2-1 as an epoch to fix the
> > problem generated by the first version of this package.
> > 
> > Is that ok?
> 
> I've got recently a very similiar situtation with
> gnome-shell-extension-autohidetopbar, as there it was considered ok to use an
> epoch. [1]

Thanks all for the help with this topic.
 
> 
> [1] https://lists.debian.org/debian-devel/2022/03/msg00424.html
> 
> -- 
> tobi
> 
>  
> > Thanks
> > -- 
> > Rodrigo Siqueira
> > https://siqueira.tech
> 
> 



-- 
Rodrigo Siqueira
https://siqueira.tech

Attachment: signature.asc
Description: PGP signature


Reply to: