Processed: Bump severity for using libgcrypt-config

[Debian Bug Tracking System]

Processing commands for control@bugs.debian.org:

> # Hello,
> #
> # libgcrypt 1.11.0 has been released and the Debian packages will not
> # ship libgcrypt-config. I am bumping these bugs to RC.
> #
> # cu Andreas
> severity 1071837 serious
Bug #1071837 [src:chntpw] chntpw: Please use pkg-config instead of 
libgcrypt-config to locate libgcrypt
Severity set to 'serious' from 'important'
> severity 1071862 serious
Bug #1071862 [src:gfsecret] gfsecret: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071931 serious
Bug #1071931 [src:libaacs] libaacs: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071934 serious
Bug #1071934 [src:libpam-ccreds] libpam-ccreds: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071941 serious
Bug #1071941 [src:monkeysphere] monkeysphere: FTBFS against libgcrypt 1.11 (and 
next libassuan)
Severity set to 'serious' from 'important'
> severity 1071951 serious
Bug #1071951 [src:poldi] poldi: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071955 serious
Bug #1071955 [src:shishi] shishi: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071832 serious
Bug #1071832 [src:aircrack-ng] aircrack-ng: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071838 serious
Bug #1071838 [src:clamz] clamz: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071860 serious
Bug #1071860 [src:fis-gtm] fis-gtm: Searches for libgcrypt with libgcrypt-config
Severity set to 'serious' from 'important'
> severity 1071864 serious
Bug #1071864 [src:gnupg-pkcs11-scd] gnupg-pkcs11-scd: Searches for libgcrypt 
with libgcrypt-config
Severity set to 'serious' from 'important'
> severity 1071930 serious
Bug #1071930 [src:kwallet-pam] kwallet-pam: Searches for libgcrypt with 
libgcrypt-config
Severity set to 'serious' from 'important'
> severity 1071932 serious
Bug #1071932 [src:libbdplus] libbdplus: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071933 serious
Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071937 serious
Bug #1071937 [src:libxslt] libxslt: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071945 serious
Bug #1071945 [src:netatalk] netatalk: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071950 serious
Bug #1071950 [src:openvas-scanner] openvas-scanner: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071952 serious
Bug #1071952 [src:purple-lurch] purple-lurch: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1071954 serious
Bug #1071954 [src:sngrep] sngrep: FTBFS against libgcrypt 1.11
Severity set to 'serious' from 'important'
> severity 1070892 serious
Bug #1070892 [src:abiword] abiword: Please use pkg-config instead of 
libgcrypt-config to locate libgcrypt
Severity set to 'serious' from 'normal'
> severity 1070903 serious
Bug #1070903 [src:axc] axc: Please use pkg-config instead of libgcrypt-config 
to locate libgcrypt
Severity set to 'serious' from 'normal'
> severity 1070904 serious
Bug #1070904 [bitlbee] bitlbee: Please use pkg-config instead of 
libgcrypt-config to locate libgcrypt
Severity set to 'serious' from 'normal'
> severity 1070905 serious
Bug #1070905 [src:collectd] collectd: Please use pkg-config instead of 
libgcrypt-config to locate libgcrypt
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1070892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070892
1070903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070903
1070904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070904
1070905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070905
1071832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071832
1071837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071837
1071838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071838
1071860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071860
1071862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071862
1071864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071864
1071930: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071930
1071931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071931
1071932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071932
1071933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071933
1071934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071934
1071937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071937
1071941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071941
1071945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071945
1071950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071950
1071951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071951
1071952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071952
1071954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071954
1071955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071955
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems