mercurial-crecord is marked for autoremoval from testing
mercurial-crecord 0.20151121-2 is marked for autoremoval from testing on 2020-08-21 It is affected by these RC bugs: 804267: mercurial-crecord: remove mercurial-crecord from the archive https://bugs.debian.org/804267 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
ident2 is marked for autoremoval from testing
ident2 1.07-2 is marked for autoremoval from testing on 2020-08-16 It is affected by these RC bugs: 957356: ident2: ftbfs with GCC-10 https://bugs.debian.org/957356 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
bandwidthd_2.0.1+cvs20090917-12_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Aug 2020 21:45:40 +0100 Source: bandwidthd Architecture: source Version: 2.0.1+cvs20090917-12 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 957034 Changes: bandwidthd (2.0.1+cvs20090917-12) unstable; urgency=medium . * QA upload. * Fix ftbfs with GCC-10. (Closes: #957034) * Add dependency on lsb-base. Checksums-Sha1: c414fdc50bb4e610ca5985097ab4582dd1c54ed9 1990 bandwidthd_2.0.1+cvs20090917-12.dsc 19736b9f780ce2932b7c5bb7a129118b29e30f76 46584 bandwidthd_2.0.1+cvs20090917-12.debian.tar.xz d18a642ec5bf7da3d793b518ca2707af9901c303 8052 bandwidthd_2.0.1+cvs20090917-12_amd64.buildinfo Checksums-Sha256: c2f35806f9851753af223dd61968587f0cc7492900dd6a529ad1690882f2d22d 1990 bandwidthd_2.0.1+cvs20090917-12.dsc 95372fcb76419d34bec9f24d5a4437fd6eadfa0b2d2deb8918979439d1656bdd 46584 bandwidthd_2.0.1+cvs20090917-12.debian.tar.xz 55e807596f687d1b96ee4afdadf481aa5d6956a2b6c17fb8437247ce569e1be7 8052 bandwidthd_2.0.1+cvs20090917-12_amd64.buildinfo Files: 3b8aef841b474de9a7a345634b7cfdaa 1990 net optional bandwidthd_2.0.1+cvs20090917-12.dsc e5625c450df4c9db1cf7360a08f50768 46584 net optional bandwidthd_2.0.1+cvs20090917-12.debian.tar.xz b7649babb11da93f414a074c1425a376 8052 net optional bandwidthd_2.0.1+cvs20090917-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl8sbgsACgkQR5mjUUbR KzWEjQ/+MpAbBmX1edr6VVq5vG9PdlDOGPlReWPHSH0Y+aRoOHrmSwdGkVg+5ue5 vk85ECslFrMvdFMyp+7oIe0GJi8eWnZnfyRx5k24j9jPApxjTElvI5NDSrtvgla2 xjIs2Kzt0LRQguUwHOyc4kVL10yHdDbgV8r9axamATJI8o9qSqAviP9BeBTEHlTr 9BNjvxVBfaqkXd/h4MFRR4tc0XgZJktpVWDvQ2SiNs+MHWMXgCehNVUYeyOE6wEY zDlzVhNlnRNFShNFr7e+Mxr4M89Nl8xyR08HbD3BaprWVXrkJez4QK6Ccp1U8M1e yykCl4+99fAlsliBZVQrd9YTeUSD5BQ6+3V9mqx/Mg+XzuxHWNkTsT1h7gcQo/xS dhuN0aeIeBRCVFwjC63RP4SDFrmfWANKfynpt0XCG7TtHK0x18ucVP0Vg5a1H5iT adtJOdH+s6I8yNiFIaqnNqSwDW65LqeQbQpMZuJb6iMn5uICm/n+QPp9YNwNisAb SMGkuPjDKF8SINR9/rZjd5f9E1nUr3/88gtOKYyo+Kilr8+AwvtMSC3BX3+TjWFS OzriTzpDb7YdnvJ+p4Ug9w64mGd4WvpQD/Ewy6hj6hm0aG5JsGWTKiArlCErj43i 7ulw8y0r3WIMhvLspO4JWxVWNgD2WC4NwYzGt87MOT233Zx56YA= =uwj5 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of bandwidthd_2.0.1+cvs20090917-12_source.changes
bandwidthd_2.0.1+cvs20090917-12_source.changes uploaded successfully to localhost along with the files: bandwidthd_2.0.1+cvs20090917-12.dsc bandwidthd_2.0.1+cvs20090917-12.debian.tar.xz bandwidthd_2.0.1+cvs20090917-12_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#957034: marked as done (bandwidthd: ftbfs with GCC-10)
Your message dated Thu, 06 Aug 2020 21:18:27 + with message-id and subject line Bug#957034: fixed in bandwidthd 2.0.1+cvs20090917-12 has caused the Debian Bug report #957034, regarding bandwidthd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957034 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bandwidthd Version: 2.0.1+cvs20090917-11 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/bandwidthd_2.0.1+cvs20090917-11_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] In file included from conf.y:12: bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never defined 250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize); | ^ In file included from conf.y:12: bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never defined 237 | inline struct IPData *FindIp(uint32_t ipaddr); | ^~ bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never defined 234 | inline void Credit(struct Statistics *Stats, const struct ip *ip); | ^~ bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never defined 231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned char q3, unsigned char q4); | ^~ flex -Pbdconfig_ -s -i -t -I conf.l > conf.l.c gcc -g -O2 -I/usr/local/include -DHAVE_CONFIG_H -c -o conf.l.o conf.l.c gcc -Wall -g -O2 -I/usr/local/include -DHAVE_CONFIG_H -c -o pgsql.o pgsql.c In file included from pgsql.c:1: bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never defined 250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize); | ^ In file included from pgsql.c:1: bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never defined 237 | inline struct IPData *FindIp(uint32_t ipaddr); | ^~ bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never defined 234 | inline void Credit(struct Statistics *Stats, const struct ip *ip); | ^~ bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never defined 231 | inline uint32_t IpAddr(unsigned char q1, unsigned char q2, unsigned char q3, unsigned char q4); | ^~ pgsql.c:418:13: warning: ‘pgsqllngjmp’ defined but not used [-Wunused-function] 418 | static void pgsqllngjmp(int signal) | ^~~ gcc -Wall -g -O2 -I/usr/local/include -DHAVE_CONFIG_H -c -o extensions.o extensions.c In file included from extensions.c:1: bandwidthd.h:250:17: warning: inline function ‘DstCredit’ declared but never defined 250 | inline void DstCredit(uint32_t ipaddr, unsigned int psize); | ^ In file included from extensions.c:1: bandwidthd.h:237:23: warning: inline function ‘FindIp’ declared but never defined 237 | inline struct IPData *FindIp(uint32_t ipaddr); | ^~ bandwidthd.h:234:17: warning: inline function ‘Credit’ declared but never defined 234 | inline void Credit(struct Statistics *Stats, const struct ip *ip); | ^~ bandwidthd.h:231:17: warning: inline function ‘IpAddr’ declared but never defined 231 |
Bug#966453: Removed package(s) from unstable
Version: 0.0~git20160715.0.c6aac99-4+rm Dear submitter, as the package golang-github-unknwon-cae has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/966453 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)
Bug#966453: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: golang-github-unknwon-cae | 0.0~git20160715.0.c6aac99-4 | source golang-github-unknwon-cae-dev | 0.0~git20160715.0.c6aac99-4 | all --- Reason --- RoQA; Orphaned, open security issues, dead upstream, no rdeps -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/966453 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)
Bug#967955: marked as done (golang-github-unknwon-cae: CVE-2020-7664)
Your message dated Thu, 06 Aug 2020 17:19:32 + with message-id and subject line Bug#966453: Removed package(s) from unstable has caused the Debian Bug report #967955, regarding golang-github-unknwon-cae: CVE-2020-7664 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-unknwon-cae Version: 0.0~git20160715.0.c6aac99-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-unknwon-cae. CVE-2020-7664[0]: | In all versions of the package github.com/unknwon/cae/zip, the | ExtractTo function doesn't securely escape file paths in zip archives | which include leading or non-leading "..". This allows an attacker to | add or replace files system-wide. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-7664 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7664 [1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.0~git20160715.0.c6aac99-4+rm Dear submitter, as the package golang-github-unknwon-cae has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/966453 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Bug#967956: marked as done (golang-github-unknwon-cae: CVE-2020-7668)
Your message dated Thu, 06 Aug 2020 17:19:32 + with message-id and subject line Bug#966453: Removed package(s) from unstable has caused the Debian Bug report #967956, regarding golang-github-unknwon-cae: CVE-2020-7668 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-unknwon-cae Version: 0.0~git20160715.0.c6aac99-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-unknwon-cae. CVE-2020-7668[0]: | In all versions of the package github.com/unknwon/cae/tz, the | ExtractTo function doesn't securely escape file paths in zip archives | which include leading or non-leading "..". This allows an attacker to | add or replace files system-wide. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-7668 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7668 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.0~git20160715.0.c6aac99-4+rm Dear submitter, as the package golang-github-unknwon-cae has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/966453 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Sean Whitton (the ftpmaster behind the curtain)--- End Message ---
Offrez-vous le calme, la sérénité et le confort
Afin de voir votre message, cliquez sur le lien: http://link.pfmorocco.ma/v/443/de86ac2aa9610f177334790c708c69b6cf48e23edc4d8893
Bug#967990: mmorph: Removal of sys_nerr and sys_errlist
Package: mmorph Version: 2.3.4.2-17 Severity: important Hello, Version 2.32 of glibc will not ship the sys_nerr and sys_errlist symbols any more. This package is using them, so will start FTBFS when we upload version 2.32 of glibc. Samuel
Processed: severity of 804267 is serious
Processing commands for cont...@bugs.debian.org: > severity 804267 serious Bug #804267 [mercurial-crecord] mercurial-crecord: remove mercurial-crecord from the archive Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 804267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967983: gsimplecal: Removal of sys/sysctl.h
Package: gsimplecal Version: 2.1-1 Severity: important Hello, Version 2.32 of glibc will not ship the sysctl() function and the header any more. sysctl itself has been deprecated in Linux and will be removed. This package is using it, so will start FTBFS when we upload version 2.32 of glibc. Samuel
Bug#967086: marked as done (Empty pages when authenticated)
Your message dated Thu, 6 Aug 2020 11:30:38 +0200 with message-id and subject line Re: Bug#967086: Empty pages when authenticated has caused the Debian Bug report #967086, regarding Empty pages when authenticated to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tracker.debian.org Severity: important Dear Maintainer, tracker.debian.org does not seem to respond or responds always empty pages (no error) when I use a client certificate. Cheers, -- Stéphane -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Le 06/08/2020 à 10:43, Julien Cristau a écrit : > tracker.debian.org does not seem to respond or responds always empty > pages (no error) when I use a client certificate. I don't have the issue with my own certificate. I see this in the error log: [Wed Aug 05 11:17:05.798925 2020] [ssl:error] [pid 31979:tid 140564909500160] [client 80.227.5.106:40019] AH02039: Certificate Verification: Error (66): EE certificate key too weak [Wed Aug 05 11:59:09.029731 2020] [ssl:error] [pid 31979:tid 140565890987776] [client 80.227.5.106:9418] AH02039: Certificate Verification: Error (66): EE certificate key too weak >>> >>> This is not my IP address. >> >> Looking at your mail headers, I found 152.81.9.54 and I got similar logs: >> hertzog@ticharich:~$ grep 152.81.9.54 >> /var/log/apache2/tracker.debian.org-error.log >> [Thu Aug 06 07:57:16.520838 2020] [ssl:error] [pid 29597:tid >> 140564724860672] [client 152.81.9.54:55460] AH02039: Certificate >> Verification: Error (66): EE certificate key too weak >> [Thu Aug 06 07:57:48.093622 2020] [ssl:error] [pid 29597:tid >> 140564909500160] [client 152.81.9.54:55462] AH02039: Certificate >> Verification: Error (10): certificate has expired >> >>> When I first encountered the error, I realised my certificate was >>> expired. Then, I generated a new certificate. I still get the >>> undesirable behaviour with the new certificate. >> >> I'm not sure what else I can do to help you here. I'm putting DSA in copy >> in case they know what's going on here. I never had such an issue. >> >> Did you drop you old certificate and restart your browser? >> > Maybe also provide the output of "openssl x509 -noout -text" on the cert. Indeed it's weak: RSA 1024. I used the sso.debian.org portal to generate it. Oh, I misunderstood the "Enrollment type" and chose medium, which I guess caused the weak certificate. What's the purpose of this choice? Anyway, problem solved. Cheers, -- Stéphane--- End Message ---
Bug#967086: Empty pages when authenticated
On Thu, Aug 06, 2020 at 10:37:27AM +0200, Raphael Hertzog wrote: > On Thu, 06 Aug 2020, Stéphane Glondu wrote: > > Le 05/08/2020 à 14:36, Raphael Hertzog a écrit : > > >> tracker.debian.org does not seem to respond or responds always empty > > >> pages (no error) when I use a client certificate. > > > > > > I don't have the issue with my own certificate. > > > > > > I see this in the error log: > > > [Wed Aug 05 11:17:05.798925 2020] [ssl:error] [pid 31979:tid > > > 140564909500160] [client 80.227.5.106:40019] AH02039: Certificate > > > Verification: Error (66): EE certificate key too weak > > > [Wed Aug 05 11:59:09.029731 2020] [ssl:error] [pid 31979:tid > > > 140565890987776] [client 80.227.5.106:9418] AH02039: Certificate > > > Verification: Error (66): EE certificate key too weak > > > > This is not my IP address. > > Looking at your mail headers, I found 152.81.9.54 and I got similar logs: > hertzog@ticharich:~$ grep 152.81.9.54 > /var/log/apache2/tracker.debian.org-error.log > [Thu Aug 06 07:57:16.520838 2020] [ssl:error] [pid 29597:tid 140564724860672] > [client 152.81.9.54:55460] AH02039: Certificate Verification: Error (66): EE > certificate key too weak > [Thu Aug 06 07:57:48.093622 2020] [ssl:error] [pid 29597:tid 140564909500160] > [client 152.81.9.54:55462] AH02039: Certificate Verification: Error (10): > certificate has expired > > > When I first encountered the error, I realised my certificate was > > expired. Then, I generated a new certificate. I still get the > > undesirable behaviour with the new certificate. > > I'm not sure what else I can do to help you here. I'm putting DSA in copy > in case they know what's going on here. I never had such an issue. > > Did you drop you old certificate and restart your browser? > Maybe also provide the output of "openssl x509 -noout -text" on the cert. Cheers, Julien
Bug#967086: Empty pages when authenticated
On Thu, 06 Aug 2020, Stéphane Glondu wrote: > Le 05/08/2020 à 14:36, Raphael Hertzog a écrit : > >> tracker.debian.org does not seem to respond or responds always empty > >> pages (no error) when I use a client certificate. > > > > I don't have the issue with my own certificate. > > > > I see this in the error log: > > [Wed Aug 05 11:17:05.798925 2020] [ssl:error] [pid 31979:tid > > 140564909500160] [client 80.227.5.106:40019] AH02039: Certificate > > Verification: Error (66): EE certificate key too weak > > [Wed Aug 05 11:59:09.029731 2020] [ssl:error] [pid 31979:tid > > 140565890987776] [client 80.227.5.106:9418] AH02039: Certificate > > Verification: Error (66): EE certificate key too weak > > This is not my IP address. Looking at your mail headers, I found 152.81.9.54 and I got similar logs: hertzog@ticharich:~$ grep 152.81.9.54 /var/log/apache2/tracker.debian.org-error.log [Thu Aug 06 07:57:16.520838 2020] [ssl:error] [pid 29597:tid 140564724860672] [client 152.81.9.54:55460] AH02039: Certificate Verification: Error (66): EE certificate key too weak [Thu Aug 06 07:57:48.093622 2020] [ssl:error] [pid 29597:tid 140564909500160] [client 152.81.9.54:55462] AH02039: Certificate Verification: Error (10): certificate has expired > When I first encountered the error, I realised my certificate was > expired. Then, I generated a new certificate. I still get the > undesirable behaviour with the new certificate. I'm not sure what else I can do to help you here. I'm putting DSA in copy in case they know what's going on here. I never had such an issue. Did you drop you old certificate and restart your browser? Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Bug#967086: Empty pages when authenticated
Le 05/08/2020 à 14:36, Raphael Hertzog a écrit : >> tracker.debian.org does not seem to respond or responds always empty >> pages (no error) when I use a client certificate. > > I don't have the issue with my own certificate. > > I see this in the error log: > [Wed Aug 05 11:17:05.798925 2020] [ssl:error] [pid 31979:tid 140564909500160] > [client 80.227.5.106:40019] AH02039: Certificate Verification: Error (66): EE > certificate key too weak > [Wed Aug 05 11:59:09.029731 2020] [ssl:error] [pid 31979:tid 140565890987776] > [client 80.227.5.106:9418] AH02039: Certificate Verification: Error (66): EE > certificate key too weak This is not my IP address. > So maybe get a new certificate? When I first encountered the error, I realised my certificate was expired. Then, I generated a new certificate. I still get the undesirable behaviour with the new certificate. Cheers, -- Stéphane
Bug#966939: marked as done (fdb: FTBFS: dh_sphinxdoc: error: debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not load searchindex.js)
Your message dated Thu, 6 Aug 2020 09:37:49 +0200
with message-id <20200806073749.GA321521@pisco.westfalen.local>
and subject line Re: fdb: FTBFS: dh_sphinxdoc: error:
debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not
load searchindex.js
has caused the Debian Bug report #966939,
regarding fdb: FTBFS: dh_sphinxdoc: error:
debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not
load searchindex.js
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
966939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fdb
Version: 2.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_installdocs README.rst
> install -d debian/python-fdb/usr/share/doc/python-fdb
> install -d debian/.debhelper/generated/python-fdb
> cp --reflink=auto -a README.rst
> debian/python-fdb/usr/share/doc/python-fdb
> chown -R 0:0 debian/python-fdb/usr/share/doc
> chmod -R u\+rw,go=rX debian/python-fdb/usr/share/doc
> install -p -m0644 debian/copyright
> debian/python-fdb/usr/share/doc/python-fdb/copyright
> install -d debian/python3-fdb/usr/share/doc/python3-fdb
> install -d debian/.debhelper/generated/python3-fdb
> install -p -m0644 debian/copyright
> debian/python3-fdb/usr/share/doc/python3-fdb/copyright
> install -d debian/python-fdb-doc/usr/share/doc/python-fdb-doc
> install -d debian/.debhelper/generated/python-fdb-doc
> install -p -m0644 debian/copyright
> debian/python-fdb-doc/usr/share/doc/python-fdb-doc/copyright
> install -d debian/python-fdb-doc/usr/share/doc-base/
> install -p -m0644 debian/python-fdb-doc.doc-base
> debian/python-fdb-doc/usr/share/doc-base/python-fdb-doc
> dh_installdocs --package=python-fdb-doc --doc-main-package=python-fdb-doc html
> cd 'html/..' && find 'html' \( -type f -or -type l \) -and ! -empty
> -print0 | LC_ALL=C sort -z | xargs -0 -I {} cp --reflink=auto --parents -dp
> {} /<>/debian/python-fdb-doc/usr/share/doc/python-fdb-doc
> chown -R 0:0 debian/python-fdb-doc/usr/share/doc
> chmod -R u\+rw,go=rX debian/python-fdb-doc/usr/share/doc
> install -p -m0644 debian/copyright
> debian/python-fdb-doc/usr/share/doc/python-fdb-doc/copyright
> install -p -m0644 debian/python-fdb-doc.doc-base
> debian/python-fdb-doc/usr/share/doc-base/python-fdb-doc
> dh_sphinxdoc --package=python-fdb-doc usr/share/doc/python-fdb-doc/html
> dh_sphinxdoc: error:
> debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not
> load searchindex.js
> make[1]: *** [debian/rules:29: override_dh_installdocs] Error 25
The full build log is available from:
http://qa-logs.debian.net/2020/08/02/fdb_2.0.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.0.1-2
On Mon, Aug 03, 2020 at 10:50:48AM +0200, Lucas Nussbaum wrote:
> Source: fdb
> Version: 2.0.1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200802 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This was fixed in my upload yesterday.
Cheers,
Moritz--- End Message ---
