Bug#995587: transition: ruby3.0-add

2021-12-07 Thread Antonio Terceiro
Hi,

On Sat, 2 Oct 2021 15:14:39 -0300 Antonio Terceiro  wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> We would like to add support for ruby3.0 in ruby-defaults.

This can now be closed. There are 4 unfixed packages in the tracker, but
they are all out of testing. Some of them probably need to be removed
from the archive entirely, but we will look at them later and give
someone who cares a chance to fix them before that.


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-31 Thread Antonio Terceiro
On Sat, Oct 30, 2021 at 11:43:35AM +0200, Sebastian Ramacher wrote:
> Those have been scheduled. Note that a bunch of them have only built and
> installed the extension for the default ruby version, e.g.,
> ruby-debug-inspector and libprelude.

Yes. Please amend the ben file like this:

is_affected = (.depends ~ /ruby2.7/ | .depends ~ /ruby3.0/) & ! .source ~ 
/^(ruby2\.7|ruby3\.0|ruby-defaults|dislocker|epic5|graphviz|hivex|kamailio|klayout|kross-interpreters|libprelude|marisa|ngraph-gtk|notmuch|obexftp|redland-bindings|rubyluabridge|ruby-standalone|subtle|subversion|uwsgi|vim-command-t|weechat|robot-testing-framework|treil|vim|nbdkit)$/


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-30 Thread Sebastian Ramacher
On 2021-10-29 10:36:25 -0300, Lucas Kanashiro wrote:
> On Thu, 28 Oct 2021 23:34:28 +0200 Sebastian Ramacher 
> wrote:
> > Yes, please go ahead
> 
> I just uploaded ruby-defaults/1:2.7.6 to unstable adding ruby3.0 as an
> alternative interpreter, it should be available soon. Below you can find a
> list of binNMUs for the dependency level 1:
> 
> dislocker
> epic5
> graphviz
> hivex
> kamailio
> klayout
> kross-interpreters
> libprelude
> libselinux
> marisa
> mecab
> ngraph-gtk
> notmuch
> protobuf
> qdbm
> raspell
> redland-bindings
> remctl
> rrdtool
> ruby-atomic
> ruby-augeas
> ruby-bcrypt
> ruby-bcrypt-pbkdf
> ruby-bert
> ruby-bindex
> ruby-binding-ninja
> ruby-cairo
> ruby-cbor
> ruby-character-set
> ruby-charlock-holmes
> ruby-concurrent
> ruby-cool.io
> ruby-curb
> ruby-curses
> ruby-damerau-levenshtein
> ruby-dataobjects-postgres
> ruby-dataobjects-sqlite3
> ruby-debian
> ruby-debug-inspector
> ruby-eb
> ruby-ed25519
> ruby-enumerable-statistics
> ruby-escape-utils
> ruby-eventmachine
> ruby-exif
> ruby-fast-blank
> ruby-fast-stemmer
> ruby-fast-xs
> ruby-fcgi
> ruby-ffi
> ruby-ffi-yajl
> ruby-filesystem
> ruby-fusefs
> ruby-gitlab-pg-query
> ruby-god
> ruby-gpgme
> ruby-hiredis
> ruby-hitimes
> ruby-jaro-winkler
> ruby-kgio
> ruby-ldap
> ruby-levenshtein
> ruby-libxml
> ruby-liquid-c
> ruby-murmurhash3
> ruby-mysql2
> ruby-narray
> ruby-ncurses
> ruby-nfc
> ruby-nio4r
> ruby-nokogiri
> ruby-odbc
> ruby-oily-png
> ruby-oj
> ruby-ox
> ruby-pcaprub
> ruby-pg
> ruby-posix-spawn
> ruby-prof
> ruby-prometheus-client-mmap
> ruby-rblineprof
> ruby-rbtree
> ruby-rdiscount
> ruby-re2
> ruby-redcarpet
> ruby-redcloth
> ruby-regexp-property-values
> ruby-rinku
> ruby-rjb
> ruby-rmagick
> ruby-rpam-ruby19
> ruby-rpatricia
> ruby-rugged
> ruby-sdl
> ruby-sequel-pg
> ruby-serialport
> ruby-shadow
> ruby-stackprof
> ruby-strptime
> ruby-termios
> ruby-thrift
> ruby-timfel-krb5-auth
> ruby-tioga
> ruby-tokyocabinet
> ruby-uconv
> ruby-unf-ext
> ruby-unicode
> ruby-version-sorter
> ruby-vmstat
> ruby-websocket-driver
> ruby-xmlhash
> ruby-xmlparser
> ruby-yajl
> ruby-zoom
> spglib
> stfl
> subtle
> subversion
> uwsgi
> vim-command-t
> weechat
> xapian-bindings

Those have been scheduled. Note that a bunch of them have only built and
installed the extension for the default ruby version, e.g.,
ruby-debug-inspector and libprelude.

> 
> 
> The following packages are also part of the dependency level 1 but they are
> still FTBFSes, let's skip them for now.
> 
> obexftp
> ruby-byebug
> ruby-ferret
> ruby-dataobjects-mysql
> ruby-gd
> ruby-json
> ruby-kyotocabinet
> ruby-libvirt
> ruby-mmap2
> ruby-psych
> ruby-ruby-magic-static
> ruby-sigar
> 
> -- 
> Lucas Kanashiro
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-29 Thread Lucas Kanashiro
On Thu, 28 Oct 2021 23:34:28 +0200 Sebastian Ramacher 
 wrote:

> Yes, please go ahead

I just uploaded ruby-defaults/1:2.7.6 to unstable adding ruby3.0 as an 
alternative interpreter, it should be available soon. Below you can find 
a list of binNMUs for the dependency level 1:


dislocker
epic5
graphviz
hivex
kamailio
klayout
kross-interpreters
libprelude
libselinux
marisa
mecab
ngraph-gtk
notmuch
protobuf
qdbm
raspell
redland-bindings
remctl
rrdtool
ruby-atomic
ruby-augeas
ruby-bcrypt
ruby-bcrypt-pbkdf
ruby-bert
ruby-bindex
ruby-binding-ninja
ruby-cairo
ruby-cbor
ruby-character-set
ruby-charlock-holmes
ruby-concurrent
ruby-cool.io
ruby-curb
ruby-curses
ruby-damerau-levenshtein
ruby-dataobjects-postgres
ruby-dataobjects-sqlite3
ruby-debian
ruby-debug-inspector
ruby-eb
ruby-ed25519
ruby-enumerable-statistics
ruby-escape-utils
ruby-eventmachine
ruby-exif
ruby-fast-blank
ruby-fast-stemmer
ruby-fast-xs
ruby-fcgi
ruby-ffi
ruby-ffi-yajl
ruby-filesystem
ruby-fusefs
ruby-gitlab-pg-query
ruby-god
ruby-gpgme
ruby-hiredis
ruby-hitimes
ruby-jaro-winkler
ruby-kgio
ruby-ldap
ruby-levenshtein
ruby-libxml
ruby-liquid-c
ruby-murmurhash3
ruby-mysql2
ruby-narray
ruby-ncurses
ruby-nfc
ruby-nio4r
ruby-nokogiri
ruby-odbc
ruby-oily-png
ruby-oj
ruby-ox
ruby-pcaprub
ruby-pg
ruby-posix-spawn
ruby-prof
ruby-prometheus-client-mmap
ruby-rblineprof
ruby-rbtree
ruby-rdiscount
ruby-re2
ruby-redcarpet
ruby-redcloth
ruby-regexp-property-values
ruby-rinku
ruby-rjb
ruby-rmagick
ruby-rpam-ruby19
ruby-rpatricia
ruby-rugged
ruby-sdl
ruby-sequel-pg
ruby-serialport
ruby-shadow
ruby-stackprof
ruby-strptime
ruby-termios
ruby-thrift
ruby-timfel-krb5-auth
ruby-tioga
ruby-tokyocabinet
ruby-uconv
ruby-unf-ext
ruby-unicode
ruby-version-sorter
ruby-vmstat
ruby-websocket-driver
ruby-xmlhash
ruby-xmlparser
ruby-yajl
ruby-zoom
spglib
stfl
subtle
subversion
uwsgi
vim-command-t
weechat
xapian-bindings


The following packages are also part of the dependency level 1 but they 
are still FTBFSes, let's skip them for now.


obexftp
ruby-byebug
ruby-ferret
ruby-dataobjects-mysql
ruby-gd
ruby-json
ruby-kyotocabinet
ruby-libvirt
ruby-mmap2
ruby-psych
ruby-ruby-magic-static
ruby-sigar

--
Lucas Kanashiro



Bug#995587: transition: ruby3.0-add

2021-10-29 Thread Antonio Terceiro
On Thu, Oct 28, 2021 at 11:34:28PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2021-10-20 09:45:10 -0300, Antonio Terceiro wrote:
> > Control: tag -1 - moreinfo
> > 
> > On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote:
> > > Control: tags -1 moreinfo
> > > 
> > > On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
> > > > Hi,
> > > > 
> > > > On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
> > > > > Package: release.debian.org
> > > > > Severity: normal
> > > > > User: release.debian@packages.debian.org
> > > > > Usertags: transition
> > > > > 
> > > > > We would like to add support for ruby3.0 in ruby-defaults.
> > > > > 
> > > > > Ben file:
> > > > > 
> > > > > title = "ruby3.0-add";
> > > > > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source 
> > > > > ~ /^(ruby2.7|ruby3.0|ruby-defaults)$/);
> > > > > is_good = .depends ~ /ruby3.0/;
> > > > > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> > > > > 
> > > > > We already did a mass rebuild some time ago, and the results don't 
> > > > > look
> > > > > bad. We should be doing a new one soon, and will come up with a list 
> > > > > of
> > > > > binNMUs
> > > > 
> > > > This is a friendly ping. We would like to make the switch in unstable
> > > > soon and start doing binNMUs.
> > > > 
> > > > We have these bugs related to this transition:
> > > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
> > > > 
> > > > Most of those bugs are for leaf libraries. We already started fixing the
> > > > ones that block a lof of other (e.g. the ones with C extensions that
> > > > FTBFS with ruby3.0) so they are ready to be binNMUed.
> > > 
> > > ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
> > > So let's at least wait until it migrated.
> > 
> > ruby3.0 is now in testing. Can we go ahead with this?
> 
> Yes, please go ahead

Thanks, we will upload ruby-defaults shortly.

Note that we do not necessarily want/need to block involved packages
from migrating, as adding ruby3.0 support does not break anything since
the default is still unchanged.


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-28 Thread Sebastian Ramacher
Control: tags -1 confirmed

On 2021-10-20 09:45:10 -0300, Antonio Terceiro wrote:
> Control: tag -1 - moreinfo
> 
> On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote:
> > Control: tags -1 moreinfo
> > 
> > On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
> > > Hi,
> > > 
> > > On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
> > > > Package: release.debian.org
> > > > Severity: normal
> > > > User: release.debian@packages.debian.org
> > > > Usertags: transition
> > > > 
> > > > We would like to add support for ruby3.0 in ruby-defaults.
> > > > 
> > > > Ben file:
> > > > 
> > > > title = "ruby3.0-add";
> > > > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
> > > > /^(ruby2.7|ruby3.0|ruby-defaults)$/);
> > > > is_good = .depends ~ /ruby3.0/;
> > > > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> > > > 
> > > > We already did a mass rebuild some time ago, and the results don't look
> > > > bad. We should be doing a new one soon, and will come up with a list of
> > > > binNMUs
> > > 
> > > This is a friendly ping. We would like to make the switch in unstable
> > > soon and start doing binNMUs.
> > > 
> > > We have these bugs related to this transition:
> > > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
> > > 
> > > Most of those bugs are for leaf libraries. We already started fixing the
> > > ones that block a lof of other (e.g. the ones with C extensions that
> > > FTBFS with ruby3.0) so they are ready to be binNMUed.
> > 
> > ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
> > So let's at least wait until it migrated.
> 
> ruby3.0 is now in testing. Can we go ahead with this?

Yes, please go ahead

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-20 Thread Antonio Terceiro
On Wed, Oct 20, 2021 at 03:12:17PM +0200, Sebastiaan Couwenberg wrote:
> On 10/20/21 2:45 PM, Antonio Terceiro wrote:
> > On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote:
> >> On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
> >>> On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
>  Package: release.debian.org
>  Severity: normal
>  User: release.debian@packages.debian.org
>  Usertags: transition
> 
>  We would like to add support for ruby3.0 in ruby-defaults.
> 
>  Ben file:
> 
>  title = "ruby3.0-add";
>  is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
>  /^(ruby2.7|ruby3.0|ruby-defaults)$/);
>  is_good = .depends ~ /ruby3.0/;
>  is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> 
>  We already did a mass rebuild some time ago, and the results don't look
>  bad. We should be doing a new one soon, and will come up with a list of
>  binNMUs
> >>>
> >>> This is a friendly ping. We would like to make the switch in unstable
> >>> soon and start doing binNMUs.
> >>>
> >>> We have these bugs related to this transition:
> >>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
> >>>
> >>> Most of those bugs are for leaf libraries. We already started fixing the
> >>> ones that block a lof of other (e.g. the ones with C extensions that
> >>> FTBFS with ruby3.0) so they are ready to be binNMUed.
> >>
> >> ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
> >> So let's at least wait until it migrated.
> > 
> > ruby3.0 is now in testing. Can we go ahead with this?
> 
> There are 169 packages affected by the transition according to the
> tracker, the ruby3.0 usertag has 152 unresolved ftbfs bugreports.
>
> Does it really make sense to start this transition when most rdeps fail
> to build?

Yes.

Those two sets of packages are more or less distinct. The only
intersection is of packages that have C extensions (and thus a
dependency on the specific ruby versions it was build against) *and* to
build against ruby3.0.

Most of the FTBFS bugs are against pure-Ruby packages that fail against
ruby3.0, and are not even listed in the transition tracker.

A good part of the packages that *are* listed in the transition will be
good after a binNMU. To fix those we need to have ruby3.0 as a supported
version in unstable in the first place.

Also as we are "just" adding ruby3.0 support, this has little effect on
users since ruby2.7 is still the default.


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-20 Thread Sebastiaan Couwenberg
On 10/20/21 2:45 PM, Antonio Terceiro wrote:
> On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote:
>> On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
>>> On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@packages.debian.org
 Usertags: transition

 We would like to add support for ruby3.0 in ruby-defaults.

 Ben file:

 title = "ruby3.0-add";
 is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
 /^(ruby2.7|ruby3.0|ruby-defaults)$/);
 is_good = .depends ~ /ruby3.0/;
 is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;

 We already did a mass rebuild some time ago, and the results don't look
 bad. We should be doing a new one soon, and will come up with a list of
 binNMUs
>>>
>>> This is a friendly ping. We would like to make the switch in unstable
>>> soon and start doing binNMUs.
>>>
>>> We have these bugs related to this transition:
>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
>>>
>>> Most of those bugs are for leaf libraries. We already started fixing the
>>> ones that block a lof of other (e.g. the ones with C extensions that
>>> FTBFS with ruby3.0) so they are ready to be binNMUed.
>>
>> ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
>> So let's at least wait until it migrated.
> 
> ruby3.0 is now in testing. Can we go ahead with this?

There are 169 packages affected by the transition according to the
tracker, the ruby3.0 usertag has 152 unresolved ftbfs bugreports.

Does it really make sense to start this transition when most rdeps fail
to build?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#995587: transition: ruby3.0-add

2021-10-20 Thread Antonio Terceiro
Control: tag -1 - moreinfo

On Sat, Oct 16, 2021 at 03:46:11PM +0200, Sebastian Ramacher wrote:
> Control: tags -1 moreinfo
> 
> On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
> > Hi,
> > 
> > On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: transition
> > > 
> > > We would like to add support for ruby3.0 in ruby-defaults.
> > > 
> > > Ben file:
> > > 
> > > title = "ruby3.0-add";
> > > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
> > > /^(ruby2.7|ruby3.0|ruby-defaults)$/);
> > > is_good = .depends ~ /ruby3.0/;
> > > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> > > 
> > > We already did a mass rebuild some time ago, and the results don't look
> > > bad. We should be doing a new one soon, and will come up with a list of
> > > binNMUs
> > 
> > This is a friendly ping. We would like to make the switch in unstable
> > soon and start doing binNMUs.
> > 
> > We have these bugs related to this transition:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
> > 
> > Most of those bugs are for leaf libraries. We already started fixing the
> > ones that block a lof of other (e.g. the ones with C extensions that
> > FTBFS with ruby3.0) so they are ready to be binNMUed.
> 
> ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
> So let's at least wait until it migrated.

ruby3.0 is now in testing. Can we go ahead with this?


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-16 Thread Sebastian Ramacher
Control: tags -1 moreinfo

On 2021-10-15 06:44:36 -0300, Antonio Terceiro wrote:
> Hi,
> 
> On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > We would like to add support for ruby3.0 in ruby-defaults.
> > 
> > Ben file:
> > 
> > title = "ruby3.0-add";
> > is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
> > /^(ruby2.7|ruby3.0|ruby-defaults)$/);
> > is_good = .depends ~ /ruby3.0/;
> > is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> > 
> > We already did a mass rebuild some time ago, and the results don't look
> > bad. We should be doing a new one soon, and will come up with a list of
> > binNMUs
> 
> This is a friendly ping. We would like to make the switch in unstable
> soon and start doing binNMUs.
> 
> We have these bugs related to this transition:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org
> 
> Most of those bugs are for leaf libraries. We already started fixing the
> ones that block a lof of other (e.g. the ones with C extensions that
> FTBFS with ruby3.0) so they are ready to be binNMUed.

ruby3.0 isn't in testing yet - it currently fails to build on ppc64el.
So let's at least wait until it migrated.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-15 Thread Antonio Terceiro
Hi,

On Sat, Oct 02, 2021 at 03:14:39PM -0300, Antonio Terceiro wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> We would like to add support for ruby3.0 in ruby-defaults.
> 
> Ben file:
> 
> title = "ruby3.0-add";
> is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
> /^(ruby2.7|ruby3.0|ruby-defaults)$/);
> is_good = .depends ~ /ruby3.0/;
> is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;
> 
> We already did a mass rebuild some time ago, and the results don't look
> bad. We should be doing a new one soon, and will come up with a list of
> binNMUs

This is a friendly ping. We would like to make the switch in unstable
soon and start doing binNMUs.

We have these bugs related to this transition:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby3.0;users=debian-r...@lists.debian.org

Most of those bugs are for leaf libraries. We already started fixing the
ones that block a lof of other (e.g. the ones with C extensions that
FTBFS with ruby3.0) so they are ready to be binNMUed.


signature.asc
Description: PGP signature


Bug#995587: transition: ruby3.0-add

2021-10-02 Thread Antonio Terceiro
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

We would like to add support for ruby3.0 in ruby-defaults.

Ben file:

title = "ruby3.0-add";
is_affected = (.depends ~ /ruby2.7 | .depends ~ /ruby3.0/) & !.source ~ 
/^(ruby2.7|ruby3.0|ruby-defaults)$/);
is_good = .depends ~ /ruby3.0/;
is_bad = .depends ~ /ruby2.7/ & !.depends ~ /ruby3.0/;

We already did a mass rebuild some time ago, and the results don't look
bad. We should be doing a new one soon, and will come up with a list of
binNMUs


signature.asc
Description: PGP signature