Your message dated Sun, 11 Aug 2019 09:15:47 +0200 with message-id <20c45ecb-b7fc-fe7b-2015-704d10306...@tiscali.it> and subject line Re: Bug#933536: marked as done (FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist) has caused the Debian Bug report #933536, regarding FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist 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.) -- 933536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: satpy Version: 0.16.1-1 Severity: serious Justification: FTBFS Control: affects -1 src:python-scipy satpy now FTBFS (and fails tests) because of the recent upgrade of python3-pygac to 1.1.0-2. test_basic_check_satpy (satpy.tests.test_config.TestCheckSatpy) Test 'check_satpy' basic functionality. ... ERROR:pygac.gac_io:Environment variable PYGAC_CONFIG_FILE not set! Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pygac/gac_io.py", line 48, in <module> CONFIG_FILE = os.environ['PYGAC_CONFIG_FILE'] File "/usr/lib/python3.7/os.py", line 678, in __getitem__ raise KeyError(key) from None KeyError: 'PYGAC_CONFIG_FILE' ERROR test_specific_check_satpy (satpy.tests.test_config.TestCheckSatpy) Test 'check_satpy' with specific features provided. ... ok test_areas_pyproj (satpy.tests.test_config.TestBuiltinAreas) Test all areas have valid projections with pyproj. ... ok test_areas_rasterio (satpy.tests.test_config.TestBuiltinAreas) Test all areas have valid projections with rasterio. ... ok ====================================================================== ERROR: test_basic_check_satpy (satpy.tests.test_config.TestCheckSatpy) Test 'check_satpy' basic functionality. ---------------------------------------------------------------------- The failed tests prevent scipy from migrating to testing. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Il 06/08/19 21:27, Debian Bug Tracking System ha scritto: > Your message dated Tue, 06 Aug 2019 19:24:17 +0000 > with message-id <e1hv54d-000j84...@fasolo.debian.org> > and subject line Bug#933536: fixed in satpy 0.16.1-2 > has caused the Debian Bug report #933536, > regarding FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist > 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.) > > -- Antonio Valentino
--- End Message ---
