Bug#1028528: transition: libcotp

2023-06-19 Thread Sebastian Ramacher
Control: tags -1 = confirmed

On 2023-06-12 19:40:14 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Hello Sebastian,
> 
> On Fri, 20 Jan 2023 20:26:50 +0100 Sebastian Ramacher  
> wrote:
> > Control: tags -1 trixie
> > 
> > On 2023-01-19 15:38:06 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > > Hi Sebastian,
> > > 
> > > On 1/17/23 22:37, Sebastian Ramacher wrote:
> > > > Control: tags -1 moreinfo
> > > > 
> > > > On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > > >> Package: release.debian.org
> > > >> Severity: normal
> > > >> User: release.debian@packages.debian.org
> > > >> Usertags: transition
> > > >> 
> > > >> Dear Release Team,
> > > >> 
> > > >> I would like to update libcotp in unstable to the 2.0.0-1.
> > > >> 
> > > >> I would like to request a transition slot for libcotp, changing the
> > > >> library name from libcotp12 to libcotp2. The version 2.0.0
> > > > 
> > > > Why is the SONAME going backwards?
> > > > 
> > > I believe this was an upstream decision, please check it out:
> > > 
> > > "the soversion is now set only from the $major version (e.g. 2),
> > > and not from $major$minor (e.g. 12) like it used to be."
> > > https://github.com/paolostivanin/libcotp/releases/tag/v2.0.0
> > 
> > Is upstream aware that the can never release with major versions 11 and
> > 12 (at least)? Please clarify this with upstream.
> > 
> Yes, upstream is aware of this.
> 
> 
> > In any case, let's postpone this transition to trixie.
> > 
> I just uploaded version 2.0.1-1~exp1 for experimental.
> I await your authorization to proceed with the transition.

Please go ahead.

Cheers
-- 
Sebastian Ramacher



Bug#1028528: transition: libcotp

2023-06-12 Thread Francisco Vilmar Cardoso Ruviaro
Hello Sebastian,

On Fri, 20 Jan 2023 20:26:50 +0100 Sebastian Ramacher  
wrote:
> Control: tags -1 trixie
> 
> On 2023-01-19 15:38:06 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > Hi Sebastian,
> > 
> > On 1/17/23 22:37, Sebastian Ramacher wrote:
> > > Control: tags -1 moreinfo
> > > 
> > > On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> > >> Package: release.debian.org
> > >> Severity: normal
> > >> User: release.debian@packages.debian.org
> > >> Usertags: transition
> > >> 
> > >> Dear Release Team,
> > >> 
> > >> I would like to update libcotp in unstable to the 2.0.0-1.
> > >> 
> > >> I would like to request a transition slot for libcotp, changing the
> > >> library name from libcotp12 to libcotp2. The version 2.0.0
> > > 
> > > Why is the SONAME going backwards?
> > > 
> > I believe this was an upstream decision, please check it out:
> > 
> > "the soversion is now set only from the $major version (e.g. 2),
> > and not from $major$minor (e.g. 12) like it used to be."
> > https://github.com/paolostivanin/libcotp/releases/tag/v2.0.0
> 
> Is upstream aware that the can never release with major versions 11 and
> 12 (at least)? Please clarify this with upstream.
> 
Yes, upstream is aware of this.


> In any case, let's postpone this transition to trixie.
> 
I just uploaded version 2.0.1-1~exp1 for experimental.
I await your authorization to proceed with the transition.


Thanks!
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028528: transition: libcotp

2023-01-20 Thread Sebastian Ramacher
Control: tags -1 trixie

On 2023-01-19 15:38:06 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Hi Sebastian,
> 
> On 1/17/23 22:37, Sebastian Ramacher wrote:
> > Control: tags -1 moreinfo
> > 
> > On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: transition
> >> 
> >> Dear Release Team,
> >> 
> >> I would like to update libcotp in unstable to the 2.0.0-1.
> >> 
> >> I would like to request a transition slot for libcotp, changing the
> >> library name from libcotp12 to libcotp2. The version 2.0.0
> > 
> > Why is the SONAME going backwards?
> > 
> I believe this was an upstream decision, please check it out:
> 
> "the soversion is now set only from the $major version (e.g. 2),
> and not from $major$minor (e.g. 12) like it used to be."
> https://github.com/paolostivanin/libcotp/releases/tag/v2.0.0

Is upstream aware that the can never release with major versions 11 and
12 (at least)? Please clarify this with upstream.

In any case, let's postpone this transition to trixie.

Cheers

> 
> 
> I checked it this way:
> 
> $ readelf -d libcotp.so.1.2.8 | grep SONAME
>  0x000e (SONAME) Library soname: [libcotp.so.12]
> 
> $ readelf -d libcotp.so.2.0.0 | grep SONAME
>  0x000e (SONAME) Library soname: [libcotp.so.2]
> 
> 
> > Cheers
> > 
> 
> Thanks!
> -- 
> Francisco Vilmar Cardoso Ruviaro 
> 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00




-- 
Sebastian Ramacher



Bug#1028528: transition: libcotp

2023-01-19 Thread Francisco Vilmar Cardoso Ruviaro
Hi Sebastian,

On 1/17/23 22:37, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
> 
> On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>> 
>> Dear Release Team,
>> 
>> I would like to update libcotp in unstable to the 2.0.0-1.
>> 
>> I would like to request a transition slot for libcotp, changing the
>> library name from libcotp12 to libcotp2. The version 2.0.0
> 
> Why is the SONAME going backwards?
> 
I believe this was an upstream decision, please check it out:

"the soversion is now set only from the $major version (e.g. 2),
and not from $major$minor (e.g. 12) like it used to be."
https://github.com/paolostivanin/libcotp/releases/tag/v2.0.0


I checked it this way:

$ readelf -d libcotp.so.1.2.8 | grep SONAME
 0x000e (SONAME) Library soname: [libcotp.so.12]

$ readelf -d libcotp.so.2.0.0 | grep SONAME
 0x000e (SONAME) Library soname: [libcotp.so.2]


> Cheers
> 

Thanks!
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1028528: transition: libcotp

2023-01-17 Thread Sebastian Ramacher
Control: tags -1 moreinfo

On 2023-01-12 11:45:45 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I would like to update libcotp in unstable to the 2.0.0-1.
> 
> I would like to request a transition slot for libcotp, changing the
> library name from libcotp12 to libcotp2. The version 2.0.0

Why is the SONAME going backwards?

Cheers

> introducing the ABI change has been in experimental since 2023-01-10.
> 
> I have successfully rebuilt the reversed dependencies on amd64.
> 
> $ reverse-depends -b src:libcotp
> Reverse-Build-Depends
> * otpclient (for libcotp-dev)
> 
> There is already a tracker available here:
> 
> https://release.debian.org/transitions/html/auto-libcotp.html
> 
> Thanks!
> -- 
> Francisco Vilmar Cardoso Ruviaro 
> 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00




-- 
Sebastian Ramacher



Bug#1028528: transition: libcotp

2023-01-12 Thread Francisco Vilmar Cardoso Ruviaro
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear Release Team,

I would like to update libcotp in unstable to the 2.0.0-1.

I would like to request a transition slot for libcotp, changing the
library name from libcotp12 to libcotp2. The version 2.0.0
introducing the ABI change has been in experimental since 2023-01-10.

I have successfully rebuilt the reversed dependencies on amd64.

$ reverse-depends -b src:libcotp
Reverse-Build-Depends
* otpclient (for libcotp-dev)

There is already a tracker available here:

https://release.debian.org/transitions/html/auto-libcotp.html

Thanks!
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00


OpenPGP_signature
Description: OpenPGP digital signature