Bug#971644: elogind: accidentally hitting Fn-F12 crashes the system (dirty filesystem)
Package: elogind Version: 243.7-1+debian1 Severity: critical Justification: causes serious data loss X-Debbugs-Cc: t...@mirbsd.de Yay, I found another behavioural difference between just running Debian (classic, that is, sysvinit withOUT elogind) and Debian with elogind (to satisfy certain packages’ dependencies, I certainly do not need any of its functionality!). This is in the same manner as #919694 (*why* is that still unfixed‽) and #949698 (now fixed). I’m working on an IBM Thinkpad X61, which has a “suspend to disc” symbol printed in blue on the F12 key, which means Fn-F12 would, if the operating system handles it, suspend to hard disc. This key never did anything without elogind installed. I just hit it by accident. The system immediately(!) became fully unresponsible (could not even move the mouse pointer), but my xterm with tail -F /var/log/syslog captured a number of lines. The first three of it were: Oct 4 01:09:22 tglase-nb vmunix: [1043273.743227] elogind-daemon[1640]: Hibernate key pressed. Oct 4 01:09:22 tglase-nb vmunix: [1043273.747348] elogind-daemon[1640]: Hibernating... Oct 4 01:09:22 tglase-nb vmunix: [1043273.749104] PM: Image not found (code -22) This is clear evidence that elogind *actively* captured that keypress and did something not normal (i.e. not present on a standard pre-systemd system without elogind). Whatever it did apparently failed, but it STILL proceeded to crash the whole system (with the screen flickering a number of times and then the system suddenly powering off). Upon starting it again (losing all my state, unsaved files I was writing, and all that), I’ve seen the usual messages about problems with a dirty filesystem, so it’s evident that elogind positively, actively crashed the system instead of shutting it down cleanly, or, (which would have been the correct thing to do) just returning and not doing *anything* after that whatever it tried to do failed. The other log messages I saw flickering by in xterm are, of course, not preserved (ext4 “helpfully” inserted a whole block of NUL characters into my /var/log/syslog file, though). Now, from evidence to guesswork: from reading the log, I’m guessing it actually *did* try to suspend to disc, failing to do so (naturally, as this system is not set up for it, namely, the RAM is much larger than the swap space, and no equivalent to Windows® 2000’s HIBERFIL.SYS was set up either, mostly because I do not even *use* hibernation, nor do I *want* it). But, like I said, that failure was mishandled. Considering I actually lost (a small amount of) user data, I feel the severity justified. I’ve also just looked at the elogind.conf file I was told to change in one of the two other bugreports I mentioned above. There is some config regarding hibernation, so I guess, now that I know about the problem, I could just turn off as a WORKAROUND *ONLY* (I *assume* changing #HandleHibernateKey=hibernate to HandleHibernateKey=ignore might do the trick) but then I wonder why this is not ignored by default, and the failure to handle suspend-to-disc failure is still present (and someone should probably check if systemd similarily suffers). Anyway, this bugreport should point out something more: People *need* to install libpam-elogind to satisfy package dependencies, which forces elogind installation alongside; elogind now runs a dæmon which changes system behaviour (compared to regular pre-systemd Debian) in unpredictable ways, much to users’ detriment. I believe there exist users who would wish for all these features, but to me, who doesn’t even need them in the first place, a way of satisfying packages without piling new bugs onto the system is direly needed. Sorry for any grumpiness here, I’ve just lost some work and quite an amount of session state and it’s half past one in the bloody night and I visited the manuls (pallas cats) in the zoo earlier which provide for appropriate grumpiness; I don’t intend any insult or something towards any living being (just towards software). -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages elogind depends on: ii dbus 1.12.20-1 ii debconf 1.5.74 ii libacl1 2.2.53-8 ii libc62.31-3 ii libcap2 1:2.43-1 ii libelogind0 243.7-1+debian1 ii libselinux1 3.1-2 ii libudev1 246.6-1 ii lsb-base 11.1.0 Versions of packages elogind recommends: ii libpam-elogind 243.7-1+debian1 ii policykit-1 0.105-29 elogind suggests no packages. -- Configuration Files:
Bug#964399: marked as done (Should ganglia be removed?)
Your message dated Sat, 03 Oct 2020 22:48:36 +
with message-id
and subject line Bug#964399: fixed in ganglia 3.7.2-1
has caused the Debian Bug report #964399,
regarding Should ganglia be removed?
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.)
--
964399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganglia
Severity: serious
Should ganglia be removed? It's dead upstream (last commits from over three
years ago,
last release from 2015), is now orphaned (last active maintainer is no longer a
DD, but
wasn't very actively maintained to begin with, the current packaged version is
from 2013),
most of the plugins depend on Python 2, there's unfixed security issues dating
back to
2013 and doesn't even support ipv6 (730257).
Unless anyone steps up for maintenance (and partly becomes upstream), it should
better
be removed.
Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ganglia
Source-Version: 3.7.2-1
Done: Marcos Fouces
We believe that the bug you reported is fixed in the latest version of
ganglia, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcos Fouces (supplier of updated ganglia package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 02 Oct 2020 00:13:21 +0200
Source: ganglia
Binary: ganglia-monitor ganglia-monitor-dbgsym gmetad gmetad-dbgsym libganglia1
libganglia1-dbgsym libganglia1-dev
Architecture: source amd64
Version: 3.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marcos Fouces
Changed-By: Marcos Fouces
Description:
ganglia-monitor - cluster monitoring toolkit - node daemon
gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon
libganglia1 - cluster monitoring toolkit - shared libraries
libganglia1-dev - cluster monitoring toolkit - development libraries
Closes: 526146 586912 669821 700073 710503 712929 808160 815615 838490 936581
953471 964399 967135
Changes:
ganglia (3.7.2-1) unstable; urgency=medium
.
* Stepping in as new maintainer for
salvaging package (Closes: #964399, #953471)
* New upstream release. (Closes: #700073).
* d/patches:
~ Delete both patches as they're already applied upstream.
~ Add 1_fix-minor-spelling-errors.patch.
* d/control:
~ Bump to dehelper-compat 12. Remove obsolete d/compat file.
~ Remove package ganglia-monitor-python as it still depends
on Python2.x. (Closes: #936581, #967135, #669821, #808160)
~ Remove unneeded build-dependencies.
~ Add Depends on lsb-base in ganglia-monitor package.
~ Set proper for Vcs-* fields. (Closes: #710503)
~ Set Rules-Requires-Root: no
~ Add Pre-Depends: ${misc:Pre-Depends} for ganglia-monitor
and gmetad packages.
~ Bump to Standards-Version 4.5.0 (some changes needed).
* d/rules:
~ Simplify rules file.
~ Build gmetad along all the rest.
~ Remove unneeded *.la files in libganglia1-dev package.
~ Add target to add multiarch support to gmond configuration file.
~ Create link for libganglia.so.0 in all architectures.
* d/{ganglia-monitor,gmetad}.init
~ Major rewrite.
~ Add pid-file support. (Closes: #526146)
~ Source init functions.
~ Add support for status argument (as per policy).(Closes: #712929)
* Update paths for multiarch build in libganglia1 and dev packages.
* Remove d/libganglia1-dev.manpages. There is no more man pages for it.
* Update d/copyright to be dep-5 compliant.
* Delete unneeded ganglia-monitor-python.dir file
* Add service files for ganglia-monitor and gmetad. (Closes: #838490).
* Add upstream metadata.
* Install gmetad.conf in /etc/ganglia/.
* Rewrite {post}{inst,rm} files. (Closes: #815615, #586912)
* Update maintainer email to @debian.org
Checksums-Sha1:
0ca57238f571aca8d98ad503a6bb214e0321c1ac 2192 ganglia_3.7.2-1.dsc
5ea23da8e5b85da53216dd7c742c8154e7aa576e 1302320 ganglia_3.7.2.orig.tar.gz
9fd6e071864de7dc1b762241726ff3157fd9352b 13344 ganglia_3.7.2-1.debian.tar.xz
Bug#966738: marked as done (ganglia: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 22:48:36 +
with message-id
and subject line Bug#936581: fixed in ganglia 3.7.2-1
has caused the Debian Bug report #936581,
regarding ganglia: Unversioned Python removal in sid/bullseye
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.)
--
936581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ganglia
Version: 3.6.0-7
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.
Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).
Please check for dependencies, build dependencies AND autopkg tests.
If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ganglia
Source-Version: 3.7.2-1
Done: Marcos Fouces
We believe that the bug you reported is fixed in the latest version of
ganglia, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 936...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcos Fouces (supplier of updated ganglia package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 02 Oct 2020 00:13:21 +0200
Source: ganglia
Binary: ganglia-monitor ganglia-monitor-dbgsym gmetad gmetad-dbgsym libganglia1
libganglia1-dbgsym libganglia1-dev
Architecture: source amd64
Version: 3.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marcos Fouces
Changed-By: Marcos Fouces
Description:
ganglia-monitor - cluster monitoring toolkit - node daemon
gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon
libganglia1 - cluster monitoring toolkit - shared libraries
libganglia1-dev - cluster monitoring toolkit - development libraries
Closes: 526146 586912 669821 700073 710503 712929 808160 815615 838490 936581
953471 964399 967135
Changes:
ganglia (3.7.2-1) unstable; urgency=medium
.
* Stepping in as new maintainer for
salvaging package (Closes: #964399, #953471)
* New upstream release. (Closes: #700073).
* d/patches:
~ Delete both patches as they're already applied upstream.
~ Add 1_fix-minor-spelling-errors.patch.
* d/control:
~ Bump to dehelper-compat 12. Remove obsolete d/compat file.
~ Remove package ganglia-monitor-python as it still depends
on Python2.x. (Closes: #936581, #967135, #669821, #808160)
~ Remove unneeded build-dependencies.
~ Add Depends on lsb-base in ganglia-monitor package.
~ Set proper for Vcs-* fields. (Closes: #710503)
~ Set Rules-Requires-Root: no
~ Add Pre-Depends: ${misc:Pre-Depends} for ganglia-monitor
and gmetad packages.
~ Bump to Standards-Version 4.5.0 (some changes needed).
* d/rules:
~ Simplify rules file.
~ Build gmetad along all the rest.
~ Remove unneeded *.la files in libganglia1-dev package.
~ Add target to add multiarch support to gmond configuration file.
~ Create link for libganglia.so.0 in all architectures.
* d/{ganglia-monitor,gmetad}.init
~ Major rewrite.
~ Add pid-file support. (Closes: #526146)
~ Source init functions.
~ Add support for status argument (as per policy).(Closes: #712929)
* Update paths for multiarch build in libganglia1 and dev packages.
* Remove d/libganglia1-dev.manpages. There is no more man pages for it.
* Update d/copyright to be
Bug#967135: marked as done (ganglia: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 22:48:36 +
with message-id
and subject line Bug#967135: fixed in ganglia 3.7.2-1
has caused the Debian Bug report #967135,
regarding ganglia: Unversioned Python removal in sid/bullseye
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.)
--
967135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ganglia
Version: 3.6.0-7
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.
Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).
Please check for dependencies, build dependencies AND autopkg tests.
If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: ganglia
Source-Version: 3.7.2-1
Done: Marcos Fouces
We believe that the bug you reported is fixed in the latest version of
ganglia, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 967...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Marcos Fouces (supplier of updated ganglia package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 02 Oct 2020 00:13:21 +0200
Source: ganglia
Binary: ganglia-monitor ganglia-monitor-dbgsym gmetad gmetad-dbgsym libganglia1
libganglia1-dbgsym libganglia1-dev
Architecture: source amd64
Version: 3.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marcos Fouces
Changed-By: Marcos Fouces
Description:
ganglia-monitor - cluster monitoring toolkit - node daemon
gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon
libganglia1 - cluster monitoring toolkit - shared libraries
libganglia1-dev - cluster monitoring toolkit - development libraries
Closes: 526146 586912 669821 700073 710503 712929 808160 815615 838490 936581
953471 964399 967135
Changes:
ganglia (3.7.2-1) unstable; urgency=medium
.
* Stepping in as new maintainer for
salvaging package (Closes: #964399, #953471)
* New upstream release. (Closes: #700073).
* d/patches:
~ Delete both patches as they're already applied upstream.
~ Add 1_fix-minor-spelling-errors.patch.
* d/control:
~ Bump to dehelper-compat 12. Remove obsolete d/compat file.
~ Remove package ganglia-monitor-python as it still depends
on Python2.x. (Closes: #936581, #967135, #669821, #808160)
~ Remove unneeded build-dependencies.
~ Add Depends on lsb-base in ganglia-monitor package.
~ Set proper for Vcs-* fields. (Closes: #710503)
~ Set Rules-Requires-Root: no
~ Add Pre-Depends: ${misc:Pre-Depends} for ganglia-monitor
and gmetad packages.
~ Bump to Standards-Version 4.5.0 (some changes needed).
* d/rules:
~ Simplify rules file.
~ Build gmetad along all the rest.
~ Remove unneeded *.la files in libganglia1-dev package.
~ Add target to add multiarch support to gmond configuration file.
~ Create link for libganglia.so.0 in all architectures.
* d/{ganglia-monitor,gmetad}.init
~ Major rewrite.
~ Add pid-file support. (Closes: #526146)
~ Source init functions.
~ Add support for status argument (as per policy).(Closes: #712929)
* Update paths for multiarch build in libganglia1 and dev packages.
* Remove d/libganglia1-dev.manpages. There is no more man pages for it.
* Update d/copyright to be
Bug#936581: marked as done (ganglia: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 22:48:36 + with message-id and subject line Bug#936581: fixed in ganglia 3.7.2-1 has caused the Debian Bug report #936581, regarding ganglia: Python2 removal in sid/bullseye 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.) -- 936581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ganglia Version: 3.6.0-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:ganglia If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: ganglia Source-Version: 3.7.2-1 Done: Marcos Fouces We believe that the bug you reported is fixed in the latest version of ganglia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcos Fouces (supplier of updated ganglia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 02 Oct 2020 00:13:21 +0200 Source: ganglia Binary: ganglia-monitor ganglia-monitor-dbgsym gmetad gmetad-dbgsym libganglia1 libganglia1-dbgsym libganglia1-dev Architecture: source amd64 Version: 3.7.2-1 Distribution: unstable Urgency: medium Maintainer: Marcos Fouces Changed-By: Marcos Fouces Description: ganglia-monitor - cluster monitoring toolkit - node daemon gmetad - cluster monitoring toolkit - Ganglia Meta-Daemon libganglia1 - cluster monitoring toolkit - shared libraries libganglia1-dev - cluster monitoring toolkit - development libraries Closes: 526146 586912 669821 700073 710503 712929 808160 815615 838490 936581 953471 964399 967135 Changes: ganglia (3.7.2-1) unstable; urgency=medium . * Stepping in as new maintainer for salvaging package (Closes: #964399, #953471) * New upstream release. (Closes: #700073). * d/patches: ~ Delete both patches as they're already applied upstream. ~ Add
Bug#957443: marked as done (libint2: ftbfs with GCC-10)
Your message dated Sun, 4 Oct 2020 00:04:27 +0200 with message-id <5f78f56c.1c69fb81.2e904.c...@mx.google.com> and subject line Re: [Debichem-devel] Bug#957443: libint2: ftbfs with GCC-10 has caused the Debian Bug report #957443, regarding libint2: 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.) -- 957443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libint2 Version: 2.6.0-2 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/libint2_2.6.0-2_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 [...] CXX HRRPart0bra0ket0hf001.lo CXX CR_DerivGaussP1InBra_aB_P__0__G100__1___TwoPRep_unit__0__F__1___Ab__up_0.lo CXX _elecpot_D_S.lo CXX eri3_aB_F__0__D__1___TwoPRep_unit__0__P__1___Ab__up_0.lo CXX CR_DerivGaussP1InKet_aB_g__0__l__1___TwoPRep_s__0__s010__1___Ab__up_0.lo CXX _aB_P__0__F__1___TwoPRep_S__0__S__1___Ab__up_0.lo CXX _1emultipole_P_D.lo CXX CR_aB_d__0___CartesianMultipole_sB_2_c_1_c_0_Sb__g__0___Ab__up_.lo CXX OSVRRP0InBra_aB_d__0__g__1___TwoPRep_unit__0__s010__1___Ab__up_0.lo CXX CR_DerivGaussP1InKet_aB_i__0__g__1___TwoPRep_s__0__s001__1___Ab__up_0.lo CXX OSVRRSMultipole_aB_s__0___SphericalMultipole_sB_4_c__minus_2_Sb__i__0___Ab__up_.lo CXX CR_DerivGaussP0InBra_aB_s010__0__h__1___TwoPRep_unit__0__s__1___Ab__up_0.lo CXX CR_DerivGaussP0InBra_aB_h100__0__l__1___TwoPRep_s__0__s__1___Ab__up_0.lo CXX CR_DerivGaussP0InBra_aB_g100__0__f__1___TwoPRep_unit__0__unit__1___Ab__up_0.lo CXX deriv1eri3_aB_P__0__D__1___TwoPRep_unit__0__D__1___Ab__up_0_prereq.lo CXX OSVRRP0InBra_aB_p__0__l__1___TwoPRep_s001__0__s__1___Ab__up_0.lo CXX OSVRRSMultipole_aB_g__0___SphericalMultipole_sB_2_c_1_Sb__s__0___Ab__up_.lo CXX CR_DerivGaussP1InBra_aB_H__0__H010__1___TwoPRep_S__0__S__1___Ab__up_0.lo CXX HRRPart0bra0ket0id010.lo CXX OSVRRP0InBra_aB_p__0__s__1___TwoPRep_s__0__s010__1___Ab__up_0.lo CXX OSVRRSMultipole_aB_k__0___SphericalMultipole_sB_4_c_2_Sb__s__0___Ab__up_.lo CXX eri3_aB_P__0__F__1___TwoPRep_unit__0__F__1___Ab__up_0_prereq.lo CXX _1emultipole_S_F_prereq.lo CXX _aB_F__0__D__1___TwoPRep_S__0__P__1___Ab__up_0.lo CXX CR_aB_d__0___CartesianMultipole_sB_0_c_0_c_0_Sb__f__0___Ab__up_.lo CXX deriv1_aB_G__0__F__1___TwoPRep_P__0__D__1___Ab__up_0_prereq.lo CXX CR_DerivGaussP0InBra_aB_k001__0__g__1___TwoPRep_s__0__s__1___Ab__up_0.lo CXX OSVRRP0InBra_aB_h__0__s__1___TwoPRep_s__0__s__1___Ab__up_0.lo CXX OSVRRP0InBra_aB_p__0__p__1___TwoPRep_unit__0__unit__1___Ab__up_0.lo CXX CR_aB_Y4__0___Overlap_Y4__0___Ab__up_.lo CXX HRRPart1bra0ket0dd001.lo CXX CR_DerivGaussP0InBra_aB_s010__0__s__1___TwoPRep_unit__0__s__1___Ab__up_0.lo CXX CR_aB_d__0___CartesianMultipole_sB_0_c_1_c_1_Sb__s__0___Ab__up_.lo CXX CR_DerivGaussP1InBra_aB_D__0__S010__1___TwoPRep_unit__0__S__1___Ab__up_0.lo CXX HRRPart1bra0ket0g100d.lo CXX HRRPart0bra0ket0d100p.lo CXX OSVRRP1InBra_aB_d010__0__p__1___TwoPRep_unit__0__s__1___Ab__up_0.lo CXX CR_aB_Y3__0___Overlap_Y4__0___Ab__up_.lo CXX OSVRRP1InBra_aB_g100__0__p__1___TwoPRep_unit__0__s__1___Ab__up_0.lo CXX deriv1eri3_aB_S__0__D__1___TwoPRep_unit__0__P__1___Ab__up_0_prereq.lo CXX OSVRRSMultipole_aB_d__0___SphericalMultipole_sB_3_c__minus_3_Sb__s__0___Ab__up_.lo /usr/bin/install -c -d -m 0755 /<>/src/lib/libint/../../../include/libint2 /usr/bin/install -c -m 0644 libint2_params.h libint2_types.h libint2_iface.h /<>/src/lib/libint/../../../include/libint2 find . -name '*.lo' -print > libobjlist /bin/bash
Bug#925510: marked as done (netbeans: Netbeans not usable with java in Buster)
Your message dated Sat, 03 Oct 2020 21:18:46 + with message-id and subject line Bug#925509: fixed in netbeans 12.1-1 has caused the Debian Bug report #925509, regarding netbeans: Netbeans not usable with java in Buster 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.) -- 925509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netbeans Version: 10.0-3 Severity: important Dear Maintainer, I've installed the netbeans package on my Buster installation for Java development and it is behaving is some very weird ways for me. I installed it with apt-get. I also installed Netbeans with Flatpak to see if that worked any better. I have not seen any of the issues I'm seeing with the version in the repo with that version. The issues I am seeing with the repo version also very consistent. I can reboot and restart netbeans however many times I want, they always happen. Updating the system didn't change anything either. The following issues have been happening: Creating a project doesn't work like expected. When you click on finish in the dialog, the loading screen finishes incredably fast, but then nothing happens. When looking at the directory where the project should have been created, you can see it is there. Loading the project doesn't work well, though. Netbeans does not detect the files or even the package found in a project created like this. When I open a project which has been created by a working version of netbeans, the project is loaded much slower than expected. Instead of the usual couple of seconds, it takes more than 10 seconds. The navigator never fills up and just shows please wait. Trying to run the project doesn't do anything either. Creating a new java class is weird too. When clicking Finish, the loading bar goes very fast and the file is created, but I get an error stating "The file newclass.java already exists". The dialog doesn't close by itself. I think it is very likely to all be caused by an error which show up at the bottom of the screen. The red balloon in the bottom bar reveals an "Unexpected Exception". The summary of the error is as follows: A java.lang.NoSuchMethodError exception has occurred. Please report this at https://issues.apache.org/jira/projects/NETBEANS/issues, including a copy of your messages.log file as an attachment. The messages.log file is located in your /home/wouter/.netbeans/10.0/var/log folder. The full log can be found here: https://pastebin.com/0wgJNt15 I hope that helps. I can provide more information if needed. Kind regards, Wouter -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages netbeans depends on: ii default-jdk [java8-sdk] 2:1.11-71 ii libnb-apisupport3-java 10.0-3 ii libnb-ide14-java10.0-3 ii libnb-java5-java10.0-3 ii libnb-platform18-java 10.0-2 ii openjdk-11-jdk [java8-sdk] 11.0.3+1-1 netbeans recommends no packages. netbeans suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: netbeans Source-Version: 12.1-1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of netbeans, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated netbeans package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 22:51:24 +0200 Source: netbeans Architecture: source Version: 12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes:
Bug#929561: marked as done (libnb-ide14-java: broken symlink: /usr/share/netbeans/ide14/modules/ext/gson-2.7.jar -> ../../../../java/gson.jar)
Your message dated Sat, 03 Oct 2020 21:18:46 + with message-id and subject line Bug#929561: fixed in netbeans 12.1-1 has caused the Debian Bug report #929561, regarding libnb-ide14-java: broken symlink: /usr/share/netbeans/ide14/modules/ext/gson-2.7.jar -> ../../../../java/gson.jar 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.) -- 929561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libnb-ide14-java Version: 10.0-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m9.4s ERROR: FAIL: Broken symlinks: /usr/share/netbeans/ide14/modules/ext/gson-2.7.jar -> ../../../../java/gson.jar (libnb-ide14-java) Is libnb-ide14-java missing a Depends/Recommends/Suggests: libgoogle-gson-java ? cheers, Andreas libnb-ide14-java_10.0-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: netbeans Source-Version: 12.1-1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of netbeans, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 929...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated netbeans package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 22:51:24 +0200 Source: netbeans Architecture: source Version: 12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 653132 805769 815028 877626 920706 922190 925509 929561 935008 960692 960749 Changes: netbeans (12.1-1) unstable; urgency=medium . * Only build libnb-absolutelayout-java from now on. Drop netbeans and Co because it is not viable to maintain the editor in Debian. We recommend to install the flatpack version from flathub instead. (Closes: #925509, #929561, #960692, #815028, #805769, #920706, #922190) (Closes: #960749, #653132, #877626, #935008) * Remove Andrew Ross from Uploaders. He is not active anymore. Checksums-Sha1: bbef1f88563985db882fde19293caf43afd305a5 2112 netbeans_12.1-1.dsc 601a44d378977b9938aa0e190cea4b8d383b90ab 5964 netbeans_12.1.orig.tar.xz b25ba096575fb0a48e52714de750fdcf2122bbe1 7968 netbeans_12.1-1.debian.tar.xz 9cf065b7587057053b08d711032b156e67f2fae5 10324 netbeans_12.1-1_amd64.buildinfo Checksums-Sha256: 8e692e803bbe26b59b45874825ad85841a320d643f3286faa96ac2443fc6e2e9 2112 netbeans_12.1-1.dsc b46bd28a436c750ca463ab6c17cf036180ca374b6bda137d0739acd8d204c037 5964 netbeans_12.1.orig.tar.xz 93ee8e861643294873ce72b2adba5d0630dcc3193db803086736633f507cb70d 7968 netbeans_12.1-1.debian.tar.xz 3509f31bcf70a6425341e7c6c96274d19c3c6fc37c41959074ab326cd4ab7aa4 10324 netbeans_12.1-1_amd64.buildinfo Files: c8b4632eee5cbe6a703015aca2433a53 2112 java optional netbeans_12.1-1.dsc 0ea201e4af76cb2fb7eda037934d79c4 5964 java optional netbeans_12.1.orig.tar.xz 2ba9692ba711147e1981ca8a99da0cb7 7968 java optional netbeans_12.1-1.debian.tar.xz 24d6038330fc38eb5f45a15a28b2df89 10324 java optional netbeans_12.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl945dBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkTxAP/i24Yw1T5fr3TcFUBNkM7aAW5qGkR7qf/oZ5 5f1SHk6MHRkwJoG/LNU4t9p/zeGuNulO1CDYfRVJcmOQ1GjpbGVNOPb11k59dsc+ vxGFK02wVY/8Wvu3IsfrUmyMDHJ0QVoZCMy2dTHqX4o6YcoA8m2X7CKoFsAwIxHa ew7+gncRNmJLvg4gpiQWlKOwAqfpqOnGSB5gYYXbm3oY7b/Sgv6NtS5dW9UUvDE3 LeHJHBH65gheqwLnjybb6pjZyTnINQN+hyXqfyEy1vlyTmIT782HZSEJ2Uah2i25 lxIwa84ME2Y3f9w133yGxNyx301WgGqprnVEaFyeoV8HN8zPGw71GiAnIDdIHsKo rHfqks2MVXnAWbdRAh0tjWnLzXLPkpMYlEWqKIQTsPqpYZ+yDSlYyfnWWnfKRtHD hxRb20gMqVFSty+zjDsXD9jXn+FLlMprRfVEL5y5l6CpcigfX88TZNuv8CaGsfqu o3CNONLNh4mL5eIlh8B4lXs9ZvIsWUc+Ag8cKUTFgoscuYWihDGVnQGTI6AZiFi7
Bug#925509: marked as done (netbeans: Netbeans not usable with java in Buster)
Your message dated Sat, 03 Oct 2020 21:18:46 + with message-id and subject line Bug#925509: fixed in netbeans 12.1-1 has caused the Debian Bug report #925509, regarding netbeans: Netbeans not usable with java in Buster 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.) -- 925509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netbeans Version: 10.0-3 Severity: important Dear Maintainer, I've installed the netbeans package on my Buster installation for Java development and it is behaving is some very weird ways for me. I installed it with apt-get. I also installed Netbeans with Flatpak to see if that worked any better. I have not seen any of the issues I'm seeing with the version in the repo with that version. The issues I am seeing with the repo version also very consistent. I can reboot and restart netbeans however many times I want, they always happen. Updating the system didn't change anything either. The following issues have been happening: Creating a project doesn't work like expected. When you click on finish in the dialog, the loading screen finishes incredably fast, but then nothing happens. When looking at the directory where the project should have been created, you can see it is there. Loading the project doesn't work well, though. Netbeans does not detect the files or even the package found in a project created like this. When I open a project which has been created by a working version of netbeans, the project is loaded much slower than expected. Instead of the usual couple of seconds, it takes more than 10 seconds. The navigator never fills up and just shows please wait. Trying to run the project doesn't do anything either. Creating a new java class is weird too. When clicking Finish, the loading bar goes very fast and the file is created, but I get an error stating "The file newclass.java already exists". The dialog doesn't close by itself. I think it is very likely to all be caused by an error which show up at the bottom of the screen. The red balloon in the bottom bar reveals an "Unexpected Exception". The summary of the error is as follows: A java.lang.NoSuchMethodError exception has occurred. Please report this at https://issues.apache.org/jira/projects/NETBEANS/issues, including a copy of your messages.log file as an attachment. The messages.log file is located in your /home/wouter/.netbeans/10.0/var/log folder. The full log can be found here: https://pastebin.com/0wgJNt15 I hope that helps. I can provide more information if needed. Kind regards, Wouter -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages netbeans depends on: ii default-jdk [java8-sdk] 2:1.11-71 ii libnb-apisupport3-java 10.0-3 ii libnb-ide14-java10.0-3 ii libnb-java5-java10.0-3 ii libnb-platform18-java 10.0-2 ii openjdk-11-jdk [java8-sdk] 11.0.3+1-1 netbeans recommends no packages. netbeans suggests no packages. -- no debconf information --1553552508-eximdsn-479279952-- --- End Message --- --- Begin Message --- Source: netbeans Source-Version: 12.1-1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of netbeans, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 925...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated netbeans package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 22:51:24 +0200 Source: netbeans Architecture: source Version: 12.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers
Bug#971636: undefined symbol: ZEND_HASH_GET_APPLY_COUNT
Package: php-lua Version: 2.0.5+1.1.0-3 Severity: grave Hello, after install php-lua I get: > php -v PHP Warning: PHP Startup: Unable to load dynamic library 'lua.so' (tried: /usr/lib/php/20180731/lua.so (/usr/lib/php/20180731/lua.so: undefined symbol: ZEND_HASH_GET_APPLY_COUNT), /usr/lib/php/20180731/lua.so.so (/usr/lib/php/20180731/lua.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0 PHP 7.3.19-1~deb10u1 (cli) (built: Jul 5 2020 06:46:45) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by Zend Technologies with Xdebug v2.7.0RC2, Copyright (c) 2002-2019, by Derick Rethans After remove php-lua it looks good: > php -v PHP 7.3.19-1~deb10u1 (cli) (built: Jul 5 2020 06:46:45) ( NTS ) Copyright (c) 1997-2018 The PHP Group Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by Zend Technologies with Xdebug v2.7.0RC2, Copyright (c) 2002-2019, by Derick Rethans CU Jörg -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:en_US:de_LU:de_CH:de_BE:de_AT (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-lua depends on: ii libapache2-mod-php7.3 [phpapi-20180731] 7.3.19-1~deb10u1 ii libc62.28-10 ii liblua5.2-0 5.2.4-1.1+b2 ii php-common 2:69 ii php7.3-cgi [phpapi-20180731] 7.3.19-1~deb10u1 ii php7.3-cli [phpapi-20180731] 7.3.19-1~deb10u1 ii php7.3-fpm [phpapi-20180731] 7.3.19-1~deb10u1 ii php7.3-phpdbg [phpapi-20180731] 7.3.19-1~deb10u1 ii ucf 3.0038+nmu1 php-lua recommends no packages. php-lua suggests no packages. -- no debconf information
Bug#967168: marked as done (lysdr: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:26:59 + with message-id and subject line Bug#970280: Removed package(s) from unstable has caused the Debian Bug report #967168, regarding lysdr: Unversioned Python removal in sid/bullseye 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.) -- 967168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lysdr Version: 1.0~git20141206+dfsg1-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0~git20141206+dfsg1-2+rm Dear submitter, as the package lysdr 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/970280 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#938331: marked as done (rainbow: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:24:23 + with message-id and subject line Bug#970257: Removed package(s) from unstable has caused the Debian Bug report #938331, regarding rainbow: Python2 removal in sid/bullseye 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.) -- 938331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rainbow Version: 0.8.7-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:rainbow If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.8.7-2+rm Dear submitter, as the package rainbow 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/970257 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#966788: marked as done (rainbow: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:24:23 + with message-id and subject line Bug#970257: Removed package(s) from unstable has caused the Debian Bug report #938331, regarding rainbow: Unversioned Python removal in sid/bullseye 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.) -- 938331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rainbow Version: 0.8.7-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.8.7-2+rm Dear submitter, as the package rainbow 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/970257 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#952570: marked as done (tcpcopy: build-depends on removed package iptables-dev)
Your message dated Sat, 03 Oct 2020 19:18:18 + with message-id and subject line Bug#969583: Removed package(s) from unstable has caused the Debian Bug report #952570, regarding tcpcopy: build-depends on removed package iptables-dev 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.) -- 952570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tcpcopy Version: 0.6.3-2.1 Severity: serious X-debbugs-cc: peter green tcpcopy build-depends on removed iptables-dev. Please see Peter's message below on how to handle the situation (from bug #951090). On Tue, 11 Feb 2020 01:08:16 + peter green wrote: > Package: keepalived > Version: 1:2.0.19-1 > Severity: serious > > keepalived build-depends on iptables-dev, which is no longer built by the > iptables source package. It is still present in unstable as a cruft package, > but is completely gone from testing. > > Before it's removal iptables-dev was a transitional dummy package depending > on a bunch of other dev packages, please determine which of those dev > packages your package needs and adjust your build-dependencies accordingly. --- End Message --- --- Begin Message --- Version: 0.6.3-2.1+rm Dear submitter, as the package tcpcopy 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/969583 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#889148: marked as done (am-utils: incorrect installation installs scripts instead of executables)
Your message dated Sat, 03 Oct 2020 19:17:54 + with message-id and subject line Bug#969582: Removed package(s) from unstable has caused the Debian Bug report #889148, regarding am-utils: incorrect installation installs scripts instead of executables 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.) -- 889148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: am-utils Version: 6.2+rc20110530-3.2+b1 Severity: grave Justification: renders package unusable Dear Maintainer, I just updated the am-utils package and it became unusable with the update. Any command in the am-utils package would fail with a message like: herschel:~# amq /usr/sbin/amq: error: '/usr/sbin/.libs/amq' does not exist This script is just a wrapper for amq. See the libtool documentation for more information. I was able to recover a working am-utils by recompiling from sources and manually installing the actual binaries from the files created by the build, e.g. in my case A.x86_64-unknown-linux-deb9.3/amq/.libs/pawd and similarly for the others. For some reason the make does not install the real binaries but libtool wrapper scripts, an the latter are then included in the deb package, resulting in an unusable package altogether. Best regards Giacomo Mulas -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.13-jak (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8), LANGUAGE=it_IT,en_EN (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages am-utils depends on: ii debconf1.5.65 ii debianutils4.8.4 ii libamu46.2+rc20110530-3.2+b1 ii libc6 2.26-6 ii libwrap0 7.6.q-27 ii rpcbind [portmap] 0.2.3-0.6 ii ucf3.0036 am-utils recommends no packages. Versions of packages am-utils suggests: pn am-utils-doc pn nis --- End Message --- --- Begin Message --- Version: 6.2+rc20110530-3.2+rm Dear submitter, as the package am-utils 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/969582 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#936988: marked as done (mandrill: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:21:25 + with message-id and subject line Bug#970108: Removed package(s) from unstable has caused the Debian Bug report #936988, regarding mandrill: Python2 removal in sid/bullseye 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.) -- 936988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mandrill Version: 1.0.57-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mandrill If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.57-1+rm Dear submitter, as the package mandrill 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/970108 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#889070: marked as done (am-utils silently drops gdbm support with libgdbm-dev 1.14.1-2)
Your message dated Sat, 03 Oct 2020 19:17:54 + with message-id and subject line Bug#969582: Removed package(s) from unstable has caused the Debian Bug report #889070, regarding am-utils silently drops gdbm support with libgdbm-dev 1.14.1-2 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.) -- 889070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: am-utils Version: 6.2+rc20110530-3.2 Severity: serious https://buildd.debian.org/status/package.php?p=am-utils ... checking gdbm/ndbm.h usability... no checking gdbm/ndbm.h presence... no checking for gdbm/ndbm.h... no ... --- End Message --- --- Begin Message --- Version: 6.2+rc20110530-3.2+rm Dear submitter, as the package am-utils 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/969582 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#937288: marked as done (piggyphoto: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:22:54 + with message-id and subject line Bug#970112: Removed package(s) from unstable has caused the Debian Bug report #937288, regarding piggyphoto: Python2 removal in sid/bullseye 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.) -- 937288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:piggyphoto Version: 0.1dev-git20141014 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:piggyphoto If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.1dev-git20141014+rm Dear submitter, as the package piggyphoto 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/970112 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#966759: marked as done (mandrill: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:21:25 + with message-id and subject line Bug#970108: Removed package(s) from unstable has caused the Debian Bug report #936988, regarding mandrill: Unversioned Python removal in sid/bullseye 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.) -- 936988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936988 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mandrill Version: 1.0.57-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.0.57-1+rm Dear submitter, as the package mandrill 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/970108 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#959451: marked as done (am-utils: Build-Depends on obsolete package linux-kernel-headers)
Your message dated Sat, 03 Oct 2020 19:17:54 + with message-id and subject line Bug#969582: Removed package(s) from unstable has caused the Debian Bug report #959451, regarding am-utils: Build-Depends on obsolete package linux-kernel-headers 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.) -- 959451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:am-utils Version: 6.2+rc20110530-3.2 Severity: serious linux-kernel-headers was removed from unstable in 2007 (I think). It is now effectively a virtual package provided by linux-libc-dev, but it's not a documented virtual package name and I would like to stop providing it. Please change the dependency to linux-libc-dev. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Version: 6.2+rc20110530-3.2+rm Dear submitter, as the package am-utils 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/969582 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#938248: marked as done (python-versuchung: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:22:05 + with message-id and subject line Bug#970110: Removed package(s) from unstable has caused the Debian Bug report #938248, regarding python-versuchung: Python2 removal in sid/bullseye 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.) -- 938248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-versuchung Version: 1.1-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-versuchung If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1.1-3+rm Dear submitter, as the package python-versuchung 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/970110 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#839785: marked as done (am-utils: broken shutdown: amq -p causes abort, results in complete hang due to stale /net mount)
Your message dated Sat, 03 Oct 2020 19:17:54 +
with message-id
and subject line Bug#969582: Removed package(s) from unstable
has caused the Debian Bug report #839785,
regarding am-utils: broken shutdown: amq -p causes abort, results in complete
hang due to stale /net mount
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.)
--
839785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: am-utils
Version: 6.2+rc20110530-3.2
Severity: critical
Justification: makes unrelated software on the system break (unrelated
processes hanging)
Hello,
I installed am-utils package today,
and then uninstalled it.
Was pretty astonished to find that
after package uninstall
unrelated processes started hanging (df etc.).
[the usual very annoying symptoms of stale mounts]
Thus figured out rather quickly that there was a stale mount left, despite
am-utils stop having been initiated by package uninstall already:
andi:(pid4532,port1022) on /net type nfs
(rw,relatime,sync,vers=2,rsize=1024,wsize=1024,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,nolock,proto=udp,port=1022,timeo=7,retrans=3,sec=sys,local_lock=all,addr=127.0.0.1)
# sh -x /etc/init.d/am-utils stop
+ PATH=/usr/sbin:/sbin:/usr/bin:/bin
+ export PATH
+ CONF=/etc/default/am-utils
+ test -x /usr/sbin/amd
+ stop_amd
+ amq -p
+ pid=
+ [ -z ]
+ echo Stopping automounter: amd not running
Stopping automounter: amd not running
+ [ 0 -eq 0 ]
+ exit 0
[subsequent shutdown handling is thus completely and fully out-maneuvered]
I realized that in fact amd was not running any more at this point.
So, I re-start:ed the service.
At this point, manually doing
# strace -f amq -p
will show:
stat64("/usr/lib/cmov", 0xbfb262d0) = -1 ENOENT (No such file or
directory)
open("/usr/lib/libnss_db.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat64("/usr/lib", {st_mode=S_IFDIR|0755, st_size=86016, ...}) = 0
munmap(0xb771b000, 163182) = 0
open("/etc/protocols", O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=2932, ...}) = 0
read(3, "# Internet (IP) protocols\n#\n# Up"..., 1024) = 1024
close(3)= 0
socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
bind(3, {sa_family=AF_INET, sin_port=htons(0),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(111),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
gettimeofday({1475612569, 410100}, NULL) = 0
futex(0xb7678180, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0xb76782e0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
write(3,
"\200\0\0008Y\304\273\254\0\0\0\0\0\0\0\2\0\1\206\240\0\0\0\2\0\0\0\3\0\0\0\0"...,
60) = 60
poll([{fd=3, events=POLLIN}], 1, 6) = 1 ([{fd=3, revents=POLLIN}])
read(3,
"\200\0\0\34Y\304\273\254\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\3\371",
400) = 32
close(3)= 0
socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) = 3
open("/etc/bindresvport.blacklist", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=367, ...}) = 0
read(4, "#\n# This file contains a list of"..., 1024) = 367
read(4, "", 1024) = 0
close(4)= 0
bind(3, {sa_family=AF_INET, sin_port=htons(604),
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(1017),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
write(3,
"\200\0\0(m.M]\0\0\0\0\0\0\0\2\0\4\223\363\0\0\0\1\0\0\0\t\0\0\0\0"...,
44) = 44
poll([{fd=3, events=POLLIN}], 1, 4) = 1 ([{fd=3, revents=POLLIN}])
read(3, "", 4000) = 0
write(2, "amq: failed to get PID of amd\n", 30amq: failed to get PID of
amd
) = 30
exit_group(1) = ?
+++ exited with 1 +++
Having attached to a running amd process right before that amq invocation
this will then have resulted in the following report there:
# strace -f -p 4657
strace: Process 4657 attached
_newselect(1024, [3 4 5 6], NULL, NULL, {282, 847391}) = 1 (in [5], left
{281, 93032})
rt_sigprocmask(SIG_BLOCK, [HUP INT TERM CHLD], NULL, 8) = 0
gettimeofday({1475612569, 412383}, NULL) = 0
accept(5, {sa_family=AF_INET, sin_port=htons(604),
sin_addr=inet_addr("127.0.0.1")}, [16]) = 7
dup(0) = 8
close(8)= 0
gettimeofday({1475612569, 412959}, NULL) = 0
gettimeofday({1475612569, 413030}, NULL) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
_newselect(1024, [3 4 5 6 7], NULL, NULL, {281, 0}) = 1 (in [7], left
{280, 999649})
rt_sigprocmask(SIG_BLOCK,
Bug#935209: marked as done (servefile: Please port to Python 3 and/or drop Python 2 package)
Your message dated Sat, 03 Oct 2020 19:20:48 + with message-id and subject line Bug#970107: Removed package(s) from unstable has caused the Debian Bug report #935209, regarding servefile: Please port to Python 3 and/or drop Python 2 package 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.) -- 935209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: servefile Severity: normal User: debian-pyt...@lists.debian.org Usertags: py2removal Hello, please port servefile to Python3 and/or drop the python 2 package. This will help the goal of removing Python 2 from Debian, and would also (more immediately) allow to remove packages currently dependencies of this one. More info at: https://wiki.debian.org/Python/2Removal Thanks, Sandro --- End Message --- --- Begin Message --- Version: 0.4.4-1+rm Dear submitter, as the package servefile 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/970107 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#966793: marked as done (servefile: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:20:48 + with message-id and subject line Bug#970107: Removed package(s) from unstable has caused the Debian Bug report #935209, regarding servefile: Unversioned Python removal in sid/bullseye 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.) -- 935209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:servefile Version: 0.4.4-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.4.4-1+rm Dear submitter, as the package servefile 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/970107 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#835591: marked as done (tcpcopy: FTBFS: xcopy.h:14:43: fatal error: linux/netfilter_ipv4/ip_queue.h: No such file or directory)
Your message dated Sat, 03 Oct 2020 19:18:18 +
with message-id
and subject line Bug#969583: Removed package(s) from unstable
has caused the Debian Bug report #835591,
regarding tcpcopy: FTBFS: xcopy.h:14:43: fatal error:
linux/netfilter_ipv4/ip_queue.h: No such file or directory
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.)
--
835591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcpcopy
Version: 0.6.3-2.1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
tcpcopy fails to build from source in unstable/amd64:
[..]
Preparing to unpack .../09-libxtables-dev_1.6.0-3_amd64.deb ...
Unpacking libxtables-dev (1.6.0-3) ...
Selecting previously unselected package iptables-dev.
Preparing to unpack .../10-iptables-dev_1.6.0-3_all.deb ...
Unpacking iptables-dev (1.6.0-3) ...
Setting up libip4tc0:amd64 (1.6.0-3) ...
Setting up libxtables11:amd64 (1.6.0-3) ...
Setting up libpcap0.8-dev (1.7.4-2) ...
Processing triggers for libc-bin (2.23-5) ...
Setting up libpcap-dev (1.7.4-2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libip6tc0:amd64 (1.6.0-3) ...
Setting up libxtables-dev (1.6.0-3) ...
Setting up libiptc0:amd64 (1.6.0-3) ...
Setting up libip4tc-dev (1.6.0-3) ...
Setting up libip6tc-dev (1.6.0-3) ...
Setting up libiptc-dev (1.6.0-3) ...
Setting up iptables-dev (1.6.0-3) ...
Setting up tcpcopy-build-deps (0.6.3-2.1) ...
Processing triggers for libc-bin (2.23-5) ...
**
** Environment
**
**
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=d2b8cedecf14
TERM=xterm
PAGER=more
DISPLAY=:0
DOCKER_IMAGE=lamby-debian-sid
DEB_BUILD_OPTIONS=parallel=9
PIP_DOWNLOAD_CACHE=/home/lamby/.cache/pip
HOME=/home/lamby
LOGNAME=lamby
SHLVL=1
PWD=/home/lamby/temp/cdt.20160827114200.FQXQIUdeOQ.db.tcpcopy/tcpcopy-0.6.3
OLDPWD=/home/lamby/temp/cdt.20160827114200.FQXQIUdeOQ.db.tcpcopy
GPG_TTY=/dev/console
QUILT_PATCHES=debian/patches
QUILT_NO_DIFF_INDEX=1
QUILT_REFRESH_ARGS=-p ab --no-timestamps --no-index
DEBEMAIL=la...@debian.org
DEBFULLNAME=Chris Lamb
EDITOR=vim
LESS=-cgiFx4M
GPG_KEY=1E953E27D4311E58
BLASTER=A220 I5 D1 H5 P330 T6
_=/usr/bin/env
**
** Building tcpcopy 0.6.3-2.1 on amd64
**
**
dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: info: source package tcpcopy
dpkg-buildpackage: info: source version 0.6.3-2.1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by gregor herrmann
dpkg-source --before-build tcpcopy-0.6.3
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
dh_clean
rm -f debian/debhelper-build-stamp
rm -f debian/tcpcopy.substvars
rm -f debian/tcpcopy.*.debhelper
rm -rf debian/tcpcopy/
rm -rf debian/.debhelper/
rm -f debian/*.debhelper.log
rm -f debian/files
find . \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path
.\*/.hg -o -path .\*/CVS \) -prune -o -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \)
\)
rm -f *-stamp
debian/rules build
dh build
dh_testdir
dh_update_autotools_config
install -d debian/.debhelper/bucket/files
cp -an --reflink=auto config.guess
debian/.debhelper/bucket/files/79ec1614c5855c395a0390df1c2a50a266773256e209815bfc15cfe8252afb6b.tmp
Bug#964693: Bullseye patch
Hello, The fix to fix qpxtool 0.8.0 compilation under Bullseye is trivial, it's just missing an #include. The patch is attached to this mail. Best regards, Stéphane. qpxtool-bullseye-fix.patch Description: Binary data
Bug#945718: marked as done (owncloud-client: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:13:32 + with message-id and subject line Bug#969422: Removed package(s) from unstable has caused the Debian Bug report #945718, regarding owncloud-client: Python2 removal in sid/bullseye 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.) -- 945718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: owncloud-client Version: 2.5.1.10973+dfsg-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.5.1.10973+dfsg-1+rm Dear submitter, as the package owncloud-client 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/969422 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#933290: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)
Your message dated Sat, 03 Oct 2020 19:13:32 + with message-id and subject line Bug#969422: Removed package(s) from unstable has caused the Debian Bug report #933290, regarding BD on texlive-generic-extra which isn't build anymore and isn't in bullseye 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.) -- 933290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: breathe Version: 4.11.1-1 Severity: serious Tags: ftbfs sid bullseye Recently the texlive-base package has stopped building the transitional package texlive-generic-extra. This is an issue for your package as it build-depends on it. Please update the building of your package to use texlive-plain-generic instead. Unfortunately the migration software doesn't detected this kind of situation yet, so your package also FTBFS in bullseye since 2019-07-16. Paul signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 2.5.1.10973+dfsg-1+rm Dear submitter, as the package owncloud-client 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/969422 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#966773: marked as done (pjproject: Unversioned Python removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:11:25 + with message-id and subject line Bug#969323: Removed package(s) from unstable has caused the Debian Bug report #937296, regarding pjproject: Unversioned Python removal in sid/bullseye 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.) -- 937296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pjproject Version: 2.7.2~dfsg-4 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.7.2~dfsg-4+rm Dear submitter, as the package pjproject 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/969323 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#925263: marked as done (Do not release with Buster)
Your message dated Sat, 03 Oct 2020 19:11:25 + with message-id and subject line Bug#969323: Removed package(s) from unstable has caused the Debian Bug report #925263, regarding Do not release with Buster 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.) -- 925263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pjproject Version: 2.7.2~dfsg-4 Severity: serious Hi, as the sole Uploader of src:pjproject for the last two years I think we should not release Buster with src:pjproject. Reasons: - pjsip is a library where a lot of functionality and behaviour is selected at compile time using #define statements. Most of these define statements alter the ABI due to changing structs, which makes it ill-suited as a system wide library to be used by several programs. - Consequently, src:ring (now called jami) has always been built against an embedded copy and src:asterisk also switched to an embedded copy, both tailored to their needs. There are no other source packages depending on src:pjproject left - python-pjproject shipped by the same source package includes the old pjsua module that has been deprecated according to https://trac.pjsip.org/repos/wiki/Python_SIP_Tutorial . There is no rdep in the Debian archive. We don't package the newer pjsua2 module. - Due to the gone rdeps the version currently in the archive is not the latest upstream version. - Upstream sometimes mixes security fixes with large scale code refactoring/formatting, which makes security updates more painful than they need to be. We don't want to have this additional work for Buster when it's not necessary. Note that at least Asterisk upstream has published security advisories for issues in pjsip before and has patched them by adding the fix as patch to the Asterisk source, which makes it much easier to follow. I'm therefor filing this RC bug to start the autoremoval from Buster. I will revisit the packaging after the release of Buster and either drop the package or get it updated (and possibly backported to buster-backports). Bernhard --- End Message --- --- Begin Message --- Version: 2.7.2~dfsg-4+rm Dear submitter, as the package pjproject 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/969323 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#937296: marked as done (pjproject: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 19:11:25 + with message-id and subject line Bug#969323: Removed package(s) from unstable has caused the Debian Bug report #937296, regarding pjproject: Python2 removal in sid/bullseye 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.) -- 937296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pjproject Version: 2.7.2~dfsg-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pjproject If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.7.2~dfsg-4+rm Dear submitter, as the package pjproject 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/969323 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#864030: marked as done (flashplugin-nonfree: Flashplugin-nonfree cannot download flash plugin)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree: Flashplugin-nonfree cannot download flash plugin 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 Severity: grave Justification: renders package unusable Dear Maintainer, I install flashplugin-nonfree, but it cannot download relevant package from Adobe. Gives 404 File not found. Please substitute it with correct link. Here is the example output: 404 Not Found 2017-06-03 16:20:00 ERROR 404: Not Found. ERROR: wget failed to download https://fpdownload.adobe.com/get/flashplayer/pdc/24.0.0.186/flash_player_npapi_linux.x86_64.tar.gz More information might be available at: http://wiki.debian.org/FlashPlayer *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: Debian version: 8.8 Architecture: amd64 Package version: 1:3.6.1+deb8u1 MD5 checksums: 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or directory Alternatives: update-alternatives: error: no alternatives for flash-mozilla.so ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such file or directory /usr/lib/mozilla/plugins/flash-mozilla.so: cannot open `/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory) -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.25-5+deb8u1 ii ca-certificates20141019+deb8u3 ii debconf [debconf-2.0] 1.5.56 ii gnupg 1.4.18-7+deb8u3 ii libatk1.0-02.14.0-1 ii libcairo2 1.14.0-2.1+deb8u2 ii libcurl3-gnutls7.38.0-4+deb8u5 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u2 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-02.24.25-3+deb8u1 ii libnspr4 2:4.12-1+debu8u1 ii libnss32:3.26-1+debu8u2 ii libpango1.0-0 1.36.8-3 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.4-1+b1 ii wget 1.16-1+deb8u2 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii fonts-dejavu 2.34-1 pn hal ii iceweasel 45.9.0esr-1~deb8u1 ii konqueror-nsplugins4:4.14.2-1 ii ttf-mscorefonts-installer 3.6 pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#857765: marked as done (flashplugin-nonfree has 33 severe security flaws, orphaned?)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree has 33 severe security flaws, orphaned? 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8 Severity: grave Tags: security Dear Debian Maintainers, since almost 3 months this package no longer works as expected. It fails to download the latest hashes from: https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/ On new installations this package is unfunctional, therefore I marked this bug "grave". Most Debian users having it installed are stuck with the terribly outdated version 24.0.0.186 from December 2016. Adobe released updated versions on its patchdays in: January 2017: 24.0.0.194 fixing 13 CVE's February 2017: 24.0.0.221 fixing 13 CVE's March 2017: 25.0.0.127 fixing 7 CVE's I regularly informed the maintainer of this package by mail when new versions were available, but never got a response. So I suppose that the assigned e-mail address ist no longer valid. It appears this package is orphaned and unmaintained leaving severe security risks, as Adobes CVE's are published meanwhile. This package by design needs regular maintainence to function. --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#854467: marked as done (cannot upgrade)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding cannot upgrade 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.7 File: /usr/sbin/update-flashplugin-nonfree # update-flashplugin-nonfree --status Flash Player version installed on this system : 24.0.0.186 Flash Player version available on upstream site: 24.0.0.194 flash-mozilla.so - auto mode link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 # update-flashplugin-nonfree --install ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc More information might be available at: http://wiki.debian.org/FlashPlayer --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#946889: marked as done (flashplugin-nonfree: Update build-depends and depends on libpango1.0-0)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #946889, regarding flashplugin-nonfree: Update build-depends and depends on libpango1.0-0 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.) -- 946889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.7 Severity: grave Justification: will soon render package unusable This package Depends on the transitional package libpango1.0-0, which has been requested to be removed (#940744). Please replace this dependency with a dependency on the core Pango library libpango-1.0-0, together with any of the accompanying libraries that are needed: libpangocairo-1.0-0, libpangoft2-1.0-0, libpangox-1.0-0 and/or libpangoxft-1.0-0. Because the only packages that still depend on libpango1.0-0[1] are qtile and flashplugin-nonfree, which already have unrelated release-critical bugs and are not in stable or testing, I'm reporting this as RC and will continue with the removal of libpango1.0-0 even if this bug isn't fixed. smcv [1] % dak rm -R -n -b libpango1.0-0 ... # Broken Depends: flashplugin-nonfree/contrib: flashplugin-nonfree [amd64 i386] qtile: python3-qtile [amd64 arm64 armel armhf i386 mips64el mipsel ppc64el] # Broken Build-Depends: qtile: libpango1.0-0 --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#853095: marked as done (flashplugin-nonfree: Unable to update to the last flash version)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree: Unable to update to the last flash version 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 Severity: important Dear Maintainer, It's impossible to update to the last version of flash player with "update- flashplugin-nonfree --install". "update-flashplugin-nonfree --status" shows this : Flash Player version installed on this system : 24.0.0.186 Flash Player version available on upstream site: 24.0.0.194 --> but the "install" option does nothing. So, the flash player is stuck into 24.0.0.186 instead of 24.0.0.194. -- Package-specific info: Debian version: 8.7 Architecture: amd64 Package version: 1:3.6.1+deb8u1 Adobe Flash Player version: LNX 24,0,0,186 MD5 checksums: a618a20ef0bf4f463960134486a2ed7b /var/cache/flashplugin-nonfree/flash_player_npapi_linux.x86_64.tar.gz 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl 52d5e951bafcdb493d1a980a62c0f80e /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. lrwxrwxrwx 1 root root 34 Jan 29 12:21 /usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to /etc/alternatives/flash-mozilla.so -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.39 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.25-5 ii ca-certificates20141019+deb8u2 ii debconf [debconf-2.0] 1.5.56 ii gnupg 1.4.18-7+deb8u3 ii libatk1.0-02.14.0-1 ii libcairo2 1.14.0-2.1+deb8u2 ii libcurl3-gnutls7.38.0-4+deb8u5 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-02.24.25-3+deb8u1 ii libnspr4 2:4.12-1+debu8u1 ii libnss32:3.26-1+debu8u1 ii libpango1.0-0 1.36.8-3 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.4-1+b1 ii wget 1.16-1+deb8u1 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii fonts-dejavu 2.34-1 pn hal pn iceweasel pn konqueror-nsplugins ii ttf-mscorefonts-installer 3.6 pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#889804: marked as done (flashplugin-nonfree: Does not work anymore because adobe site have moved to https and script does not hanlde redirect)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #889804, regarding flashplugin-nonfree: Does not work anymore because adobe site have moved to https and script does not hanlde redirect 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.) -- 889804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.7 Severity: grave Justification: renders package unusable update-flashplugin-nonfree --status Flash Player version installed on this system : 28.0.0.161 link to Adobe Flash Player not found on http://www.adobe.com/ at get-upstream-version.pl line 58. ERROR: failed to get upstream version More information might be available at: http://wiki.debian.org/FlashPlayer -- Package-specific info: Debian version: buster/sid Architecture: amd64 Package version: 1:3.7 Adobe Flash Player version: [@LNX 28,0,0,161 MD5 checksums: 99bbfc9d1c2977c7d8f86f4d3fc830a4 /var/cache/flashplugin-nonfree/adobewebpage.html f953c34ab0b018d448221c3f5fa9bbd5 /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 lrwxrwxrwx 1 root root 34 Aug 21 2016 /usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to /etc/alternatives/flash-mozilla.so -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.17 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.30-2 ii ca-certificates20170717 ii debconf [debconf-2.0] 1.5.65 ii gnupg 2.2.4-2 ii gnupg2 2.2.4-2 ii libatk1.0-02.26.1-3 ii libcairo2 1.15.10-1 ii libcurl3-gnutls7.58.0-2 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-1 ii libgcc11:7.3.0-1 ii libglib2.0-0 2.55.1-1 ii libgtk2.0-02.24.32-1 ii libnspr4 2:4.18-1 ii libnss32:3.35-2 ii libpango1.0-0 1.40.14-1 ii libstdc++6 7.3.0-1 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxt6 1:1.1.5-1 ii wget 1.19.4-1 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii firefox-esr52.6.0esr-2 ii fonts-dejavu 2.37-1 pn hal-flash pn iceweasel ii konqueror-nsplugins4:16.08.3-1 pn ttf-mscorefonts-installer ii ttf-xfree86-nonfree4.2.1-5 -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#859904: marked as done (flashplugin-nonfree fails update)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree fails update 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** update-flashplugin-nonfree --install fails.. -- Package-specific info: Debian version: 8.7 Architecture: amd64 Package version: 1:3.6.1+deb8u1 MD5 checksums: 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or directory Alternatives: update-alternatives: error: no alternatives for flash-mozilla.so ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such file or directory /usr/lib/mozilla/plugins/flash-mozilla.so: cannot open `/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory) -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.25-5 ii ca-certificates20141019+deb8u2 ii debconf [debconf-2.0] 1.5.56 ii gnupg 1.4.18-7+deb8u3 ii libatk1.0-02.14.0-1 ii libcairo2 1.14.0-2.1+deb8u2 ii libcurl3-gnutls7.38.0-4+deb8u5 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgtk2.0-02.24.25-3+deb8u1 ii libnspr4 2:4.12-1+debu8u1 ii libnss32:3.26-1+debu8u1 ii libpango1.0-0 1.36.8-3 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.4-1+b1 ii wget 1.16-1+deb8u1 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii fonts-dejavu 2.34-1 pn hal ii iceweasel 45.8.0esr-1~deb8u1 pn konqueror-nsplugins pn ttf-mscorefonts-installer pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#857766: marked as done (ERROR: wget failed to download)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding ERROR: wget failed to download 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 Severity: important Dear Maintainer, * What led up to the situation? i tried to install flashplayer-plugin * What exactly did you do (or not do) that was effective (or ineffective)? $sudo apt-get -t jessie-backports install flashplugin-nonfree * What was the outcome of this action? ERROR: wget failed to download https://fpdownload.adobe.com/get/flashplayer/pdc/24.0.0.186/flash_player_npapi_linux.i386.tar.gz * What outcome did you expect instead? download of flashplayer-plugin -- Package-specific info: Debian version: 8.7 Architecture: i386 Package version: 1:3.6.1+deb8u1 MD5 checksums: 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or directory Alternatives: update-alternatives: error: no alternatives for flash-mozilla.so ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such file or directory /usr/lib/mozilla/plugins/flash-mozilla.so: cannot open `/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory) -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages flashplugin-nonfree depends on: ii binutils 2.25-5 ii ca-certificates20141019+deb8u2 ii debconf [debconf-2.0] 1.5.56 ii gnupg 1.4.18-7+deb8u3 ii libatk1.0-02.14.0-1 ii libcairo2 1.14.0-2.1+deb8u2 ii libcurl3-gnutls7.38.0-4+deb8u5 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-02.24.25-3+deb8u1 ii libnspr4 2:4.12-1+debu8u1 ii libnss32:3.26-1+debu8u1 ii libpango1.0-0 1.36.8-3 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.4-1+b1 ii wget 1.16-1+deb8u1 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: pn flashplugin-nonfree-extrasound ii fonts-dejavu2.34-1 pn hal ii iceweasel 45.8.0esr-1~deb8u1 pn konqueror-nsplugins pn ttf-mscorefonts-installer pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#861434: marked as done (cannot upgrade from 24 to 25)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding cannot upgrade from 24 to 25 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.7 Flash Player version installed on this system : 24.0.0.186 Flash Player version available on upstream site: 25.0.0.148 sh /usr/sbin/update-flashplugin-nonfree --install ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.25.0.0.148.sha512.i386.pgp.asc --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#851819: marked as done (ERROR: wget failed to download http://people.debian.org/~bartm/...)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding ERROR: wget failed to download http://people.debian.org/~bartm/... 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree /usr/sbin/update-flashplugin-nonfree --install ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.i386.pgp.asc --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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#858888: marked as done (flashplugin-nonfree: wget tries to download old version)
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree: wget tries to download old version 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 Severity: important Dear Maintainer, update-flashplugin-nonfree found a new version of plugin: # update-flashplugin-nonfree --status Flash Player version installed on this system : Flash Player version available on upstream site: 25.0.0.127 update-alternatives: error: no alternatives for flash-mozilla.so , but tries to download an old one: # update-flashplugin-nonfree --install --2017-03-28 12:50:16-- https://fpdownload.adobe.com/get/flashplayer/pdc/24.0.0.186/flash_player_npapi_linux.x86_64.tar.gz Распознаётся fpdownload.adobe.com (fpdownload.adobe.com)… 2.17.215.70 Подключение к fpdownload.adobe.com (fpdownload.adobe.com)|2.17.215.70|:443... соединение установлено. HTTP-запрос отправлен. Ожидание ответа... 404 Not Found 2017-03-28 12:50:17 ОШИБКА 404: Not Found. ERROR: wget failed to download https://fpdownload.adobe.com/get/flashplayer/pdc/24.0.0.186/flash_player_npapi_linux.x86_64.tar.gz More information might be available at: http://wiki.debian.org/FlashPlayer As a result i can not to update or install flash plugin. Some information about my system: # apt-cache show flashplugin-nonfree Package: flashplugin-nonfree Version: 1:3.6.1+deb8u1 # cat /etc/debian_version 8.7 -- Package-specific info: Debian version: 8.7 Architecture: amd64 Package version: 1:3.6.1+deb8u1 MD5 checksums: 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl 82cd4f82b2023fad1d43092de8e002a7 /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz md5sum: /usr/lib/flashplugin-nonfree/libflashplayer.so: No such file or directory Alternatives: update-alternatives: error: no alternatives for flash-mozilla.so ls: cannot access /usr/lib/mozilla/plugins/flash-mozilla.so: No such file or directory /usr/lib/mozilla/plugins/flash-mozilla.so: cannot open `/usr/lib/mozilla/plugins/flash-mozilla.so' (No such file or directory) -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.25-5 ii ca-certificates20141019+deb8u2 ii debconf [debconf-2.0] 1.5.56 ii gnupg 1.4.18-7+deb8u3 ii libatk1.0-02.14.0-1 ii libcairo2 1.14.0-2.1+deb8u2 ii libcurl3-gnutls7.38.0-4+deb8u5 ii libfontconfig1 2.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc11:4.9.2-10 ii libglib2.0-0 2.42.1-1+b1 ii libgtk2.0-02.24.25-3+deb8u1 ii libnspr4 2:4.12-1+debu8u1 ii libnss32:3.26-1+debu8u1 ii libpango1.0-0 1.36.8-3 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.4-1+b1 ii wget 1.16-1+deb8u1 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii fonts-dejavu 2.34-1 pn hal pn iceweasel pn konqueror-nsplugins pn ttf-mscorefonts-installer pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 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.
Bug#851066: marked as done (flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org))
Your message dated Sat, 03 Oct 2020 19:01:09 + with message-id and subject line Bug#969112: Removed package(s) from unstable has caused the Debian Bug report #851066, regarding flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org) 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.) -- 851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flashplugin-nonfree Version: 1:3.7 Severity: important Dear Maintainer, Now Adobe has once again started releasing updates to the Linux version of the flash plugin, the updater recognises the version number of the latest version, but it is not yet available at people.debian.org. In addition, the documentation states that the player will be downloaded from www.adobe.com, where it is clearly going there for the version information, but to poeple.debian.org for the actual file. * What led up to the situation? Running 'update-flashplugin-nonfree --install' * What was the outcome of this action? # update-flashplugin-nonfree --install ERROR: wget failed to download http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.24.0.0.194.sha512.amd64.pgp.asc More information might be available at: http://wiki.debian.org/FlashPlayer * What outcome did you expect instead? A proper update of the flash installer -- Package-specific info: Debian version: stretch/sid Architecture: amd64 Package version: 1:3.7 Adobe Flash Player version: LNX 11,2,202,632 MD5 checksums: 29c85bc8504422120cf89702986ff8e1 /var/cache/flashplugin-nonfree/get-upstream-version.pl ace1a0801f00a25fd90172f63e98e101 /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz e3a1280f91b278b8832500f362d0546b /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 /usr/lib/gnash/libgnashplugin.so - priority 10 /usr/lib/lightspark/liblightsparkplugin.so - priority 0 lrwxrwxrwx 1 root root 34 Jul 22 2014 /usr/lib/mozilla/plugins/flash-mozilla.so -> /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to /etc/alternatives/flash-mozilla.so -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf, i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flashplugin-nonfree depends on: ii binutils 2.27.51.20161220-1 ii ca-certificates20161130 ii debconf [debconf-2.0] 1.5.59 ii gnupg 2.1.17-2 ii gnupg2 2.1.17-2 ii libatk1.0-02.22.0-1 ii libcairo2 1.14.8-1 ii libcurl3-gnutls7.51.0-1 ii libfontconfig1 2.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libgcc11:6.2.1-5 ii libglib2.0-0 2.50.2-2 ii libgtk2.0-02.24.31-1 ii libnspr4 2:4.12-6 ii libnss32:3.26.2-1 ii libpango1.0-0 1.40.3-3 ii libstdc++6 6.2.1-5 ii libx11-6 2:1.6.4-2 ii libxext6 2:1.3.3-1 ii libxt6 1:1.1.5-1 ii wget 1.18-4 flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: ii firefox-esr45.6.0esr-1 ii fonts-dejavu 2.37-1 pn hal-flash ii iceweasel 45.6.0esr-1 pn konqueror-nsplugins pn ttf-mscorefonts-installer pn ttf-xfree86-nonfree -- no debconf information --- End Message --- --- Begin Message --- Version: 1:3.7+rm Dear submitter, as the package flashplugin-nonfree 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/969112 The version of this package that was in Debian prior to this removal
Bug#961116: marked as done (gnome-shell-extension-suspend-button: Not suitable for next release: Does not work with gnome 3.36)
Your message dated Sat, 03 Oct 2020 19:01:52 + with message-id and subject line Bug#969117: Removed package(s) from unstable has caused the Debian Bug report #961116, regarding gnome-shell-extension-suspend-button: Not suitable for next release: Does not work with gnome 3.36 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.) -- 961116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-extension-suspend-button Version: 0~git20191005-1 Severity: serious Control: tags -1 upstream Control: forwarded -1 https://github.com/laserb/gnome-shell-extension-suspend-button/issues/53 This extension is currently not compatible with gnome 3.36 and it is unclear if it will be adapted to he new interface as upstream seems a bit inactive. Filing this bug to keep this extension out of testing and to see if this gets resolved Note: gnome 3.36 has built-in facilities like this plugin, but requires additional click. -- tobi --- End Message --- --- Begin Message --- Version: 0~git20191005-1+rm Dear submitter, as the package gnome-shell-extension-suspend-button 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/969117 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#965219: Recipe for reproduction
Hi Quotes from IRC for documentation purposes [19:47:41] -*- elbrus is looking into bug #965219 [19:47:44] [zwiebelbot] Debian#965219: dbconfig-common: Write file error (wrong owner) - https://bugs.debian.org/965219 [19:48:18] does anybody know why root can't "exec > $file" anymore in sid/bullseye? [19:48:52] (if file is owned by a different user and having strict permissions) [19:49:03] it works in buster [19:51:10] elbrus: /proc/sys/fs/protected_regular. For directories like /tmp [19:52:06] 2 on my system [19:52:34] 0 on the buster system I'm testing on [19:53:04] ansgar: can you point me at (or in the direction of) some documentation about it? [19:53:32] elbrus: linux-doc, Documentation/admin-guide/sysctl/fs.rst.gz [19:53:41] awesome, thanks [19:53:48] and I assume the default changed? [19:54:05] elbrus: It's clearly an unsafe operation as user www-data could replace the file with a symlink to something else. [19:54:14] And then root would overwrite an unrelated file. [19:54:26] elbrus: Yes. It's a new feature. [19:54:43] that explains, I'll need to find a work around Paul PS: man proc.5 also has the info signature.asc Description: OpenPGP digital signature
Processed: confine to bullseye
Processing commands for cont...@bugs.debian.org: > tags 965219 bullseye sid Bug #965219 [dbconfig-common] dbconfig-common: Write file error (wrong owner) Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 965219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#965219: Recipe for reproduction
Processing control commands: > tags -1 confirmed Bug #965219 [dbconfig-common] dbconfig-common: Write file error (wrong owner) Added tag(s) confirmed. > severity -1 serious Bug #965219 [dbconfig-common] dbconfig-common: Write file error (wrong owner) Severity set to 'serious' from 'important' -- 965219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971106: marked as done (vips: FTBFS: ValueError: Namespace conflict: DocSection('interpolate'))
Your message dated Sat, 03 Oct 2020 17:33:51 +
with message-id
and subject line Bug#971106: fixed in vips 8.10.1-2
has caused the Debian Bug report #971106,
regarding vips: FTBFS: ValueError: Namespace conflict: DocSection('interpolate')
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.)
--
971106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vips
Version: 8.10.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/libvips'
> gcc -DHAVE_CONFIG_H -I. -I.. -I../libvips/include -DG_DISABLE_ASSERT
> -DG_DISABLE_CHECKS-pthread -I/usr/include/libmount -I/usr/include/blkid
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -pthread -I/usr/include/pango-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libgsf-1
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/libxml2 -fopenmp -DMAGICKCORE_HDRI_ENABLE=0
> -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/x86_64-linux-gnu//ImageMagick-6
> -I/usr/include/ImageMagick-6 -I/usr/include/libpng16
> -I/usr/lib/x86_64-linux-gnu/hdf5/serial/include -pthread
> -I/usr/include/librsvg-2.0 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/cairo
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2
> -I/usr/include/libpng16 -I/usr/include/poppler/glib -I/usr/include/poppler
> -I/usr/include/cairo -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1
> -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread
> -I/usr/include/OpenEXR -I/usr/include/openslide -pthread
> -I/usr/include/orc-0.4 -I/usr/include/x86_64-linux-gnu
> -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -D_FORTIFY_SOURCE=2
> -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -c -o introspect.o introspect.c
> /bin/bash ../libtool --tag=CXX --mode=link g++ -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -no-undefined -version-info 54:3:12 -Wl,-z,relro
> -Wl,-z,now -o libvips.la -rpath /usr/lib/x86_64-linux-gnu
> resample/libresample.la arithmetic/libarithmetic.la colour/libcolour.la
> conversion/libconversion.la convolution/libconvolution.la
> deprecated/libdeprecated.la foreign/libforeign.la freqfilt/libfreqfilt.la
> histogram/libhistogram.la draw/libdraw.la iofuncs/libiofuncs.la
> morphology/libmorphology.la mosaicing/libmosaicing.la create/libcreate.la -lz
> -lMagickCore-6.Q16 -lpng16 -lz -limagequant -ltiff -ljpeg
> -Wl,--export-dynamic -lgmodule-2.0 -pthread -lgio-2.0 -lgobject-2.0
> -lglib-2.0 -lexpat -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0
> -lharfbuzz -lfontconfig -lfreetype -lgsf-1 -lgobject-2.0 -lglib-2.0 -lxml2
> -lfftw3 -lorc-0.4 -lm -pthread -llcms2 -lgif -lrsvg-2 -lm -lgio-2.0
> -lgdk_pixbuf-2.0 -lgobject-2.0 -lglib-2.0 -lcairo -lpoppler-glib
> -lgobject-2.0 -lglib-2.0 -lcairo -lIlmImf-2_5 -lImath-2_5 -lHalf-2_5
> -lIex-2_5 -lIexMath-2_5 -lIlmThread-2_5 -pthread -lopenslide -lcfitsio
> -lpthread -lwebpmux -lwebpdemux -lwebp
> -L/usr/lib/x86_64-linux-gnu/hdf5/serial/lib -lmatio -lhdf5 -lz -lexif -lm
> libtool: link: g++ -fPIC -DPIC -shared -nostdlib
> /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/crti.o
> /usr/lib/gcc/x86_64-linux-gnu/10/crtbeginS.o -Wl,--whole-archive
> resample/.libs/libresample.a arithmetic/.libs/libarithmetic.a
> colour/.libs/libcolour.a conversion/.libs/libconversion.a
> convolution/.libs/libconvolution.a deprecated/.libs/libdeprecated.a
> foreign/.libs/libforeign.a freqfilt/.libs/libfreqfilt.a
> histogram/.libs/libhistogram.a draw/.libs/libdraw.a
> iofuncs/.libs/libiofuncs.a morphology/.libs/libmorphology.a
> mosaicing/.libs/libmosaicing.a create/.libs/libcreate.a
> -Wl,--no-whole-archive
Bug#971120: marked as done (astroplan: FTBFS: AssertionError in test_schedule_insert_slot)
Your message dated Sat, 03 Oct 2020 15:33:37 +
with message-id
and subject line Bug#971120: fixed in astroplan 0.6-3
has caused the Debian Bug report #971120,
regarding astroplan: FTBFS: AssertionError in test_schedule_insert_slot
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.)
--
971120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroplan
Version: 0.6-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 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 '/<>'
> py3versions: no X-Python3-Version in control file, using supported versions
> xvfb-run -a python3.8 setup.py test
> Matplotlib created a temporary config/cache directory at
> /tmp/matplotlib-ijh8gge6 because the default path
> (/sbuild-nonexistent/.config/matplotlib) is not a writable directory; it is
> highly recommended to set the MPLCONFIGDIR environment variable to a writable
> directory, in particular to speed up the import of Matplotlib and to better
> support multiprocessing.
> running test
> installing to temporary directory: /tmp/astroplan-test-q8j0250l
> = test session starts
> ==
> platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /tmp/astroplan-test-q8j0250l/lib/python3.8/site-packages, inifile:
> setup.cfg
> plugins: openfiles-0.5.0, cov-2.8.1, filter-subpackage-0.1.1,
> astropy-header-0.1.2, hypothesis-5.32.1, arraydiff-0.3, remotedata-0.3.2,
> doctestplus-0.7.0
> collected 97 items
>
> astroplan/constraints.py . [
> 5%]
> astroplan/target.py .[
> 6%]
> astroplan/plots/tests/test_sky.py . [
> 7%]
> astroplan/tests/test_constraints.py [
> 31%]
> astroplan/tests/test_moon.py . [
> 32%]
> astroplan/tests/test_observer.py . [
> 67%]
> astroplan/tests/test_periodic.py . [
> 72%]
> astroplan/tests/test_scheduling.py ...F. [
> 85%]
> astroplan/tests/test_target.py ... [
> 88%]
> astroplan/tests/test_utils.py ...[
> 91%]
> docs/faq/iers.rst s [
> 92%]
> docs/faq/precision.rst s [
> 93%]
> docs/tutorials/constraints.rst s [
> 94%]
> docs/tutorials/periodic.rst s[
> 95%]
> docs/tutorials/plots.rst s [
> 96%]
> docs/tutorials/scheduling.rst s [
> 97%]
> docs/tutorials/speed.rst . [
> 98%]
> docs/tutorials/summer_triangle.rst .
> [100%]
>
> === FAILURES
> ===
> __ test_schedule_insert_slot
> ___
>
> def test_schedule_insert_slot():
> start = Time('2016-02-06 03:00:00')
> schedule = Schedule(start, start + 5*u.hour)
> # testing for when float comparison doesn't work, does it start/end
> at the right time
> duration = 2*u.hour + 1*u.second
> end_time = start + duration
> block = TransitionBlock.from_duration(duration)
> schedule.insert_slot(end_time - duration, block)
> > assert not end_time - duration == start
> E AssertionError: assert not ( value=2016-02-06 05:00:01.000> - ) == scale='utc' format='iso' value=2016-02-06 03:00:00.000>
>
> astroplan/tests/test_scheduling.py:78: AssertionError
> === warnings summary
> ===
> astroplan/plots/time_dependent.py:9
>
> /tmp/astroplan-test-q8j0250l/lib/python3.8/site-packages/astroplan/plots/time_dependent.py:9:
> DeprecationWarning: Using or importing the ABCs from 'collections' instead
> of from 'collections.abc' is deprecated since Python 3.3, and in 3.9 it will
> stop working
> from collections import Sequence
>
>
Bug#971611: marked as done (fonts-sil-gentiumplus-compact: upgrade to version 5.000-3 fails trying to overwrite directory)
Your message dated Sat, 03 Oct 2020 15:18:31 + with message-id and subject line Bug#971611: fixed in fonts-sil-gentiumplus-compact 5.000-4 has caused the Debian Bug report #971611, regarding fonts-sil-gentiumplus-compact: upgrade to version 5.000-3 fails trying to overwrite directory 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.) -- 971611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fonts-sil-gentiumplus-compact Version: 5.000-2 Severity: normal X-Debbugs-Cc: bpate...@gmail.com Dear Maintainer, fonts-sil-gentiumplus-compact came up for upgrade to version 5.000-3 this evening, but it failed with the following output: Preparing to unpack .../fonts-sil-gentiumplus-compact_5.000-3_all.deb ... Unpacking fonts-sil-gentiumplus-compact (5.000-3) over (5.000-2) ... dpkg: error processing archive /var/cache/apt/archives/fonts-sil-gentiumplus- compact_5.000-3_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/fonts-sil-gentiumplus-features', which is also in package fonts-sil-gentiumplus 5.000-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) -- Package-specific info: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii fontconfig 2.13.1-4.2amd64generic font configuration library - support binaries ii libfreetype6:amd64 2.10.2+dfsg-3 amd64FreeType 2 font engine, shared library files ii libfreetype6:i386 2.10.2+dfsg-3 i386 FreeType 2 font engine, shared library files ii libxft2:amd64 2.3.2-2 amd64FreeType-based font drawing library for X -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/24 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fonts-sil-gentiumplus-compact depends on: ii fontconfig 2.13.1-4.2 fonts-sil-gentiumplus-compact recommends no packages. fonts-sil-gentiumplus-compact suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: fonts-sil-gentiumplus-compact Source-Version: 5.000-4 Done: Hideki Yamane We believe that the bug you reported is fixed in the latest version of fonts-sil-gentiumplus-compact, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hideki Yamane (supplier of updated fonts-sil-gentiumplus-compact package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 23:55:30 +0900 Source: fonts-sil-gentiumplus-compact Architecture: source Version: 5.000-4 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Hideki Yamane Closes: 971611 Changes: fonts-sil-gentiumplus-compact (5.000-4) unstable; urgency=medium . * debian/doc-base - Avoid conflict with fonts-sil-gentiumplus (Closes: #971611) Checksums-Sha1: a304a907c6ab5c175752cd28fce554a5dd40b41b 2246 fonts-sil-gentiumplus-compact_5.000-4.dsc a4a765fa4179c8f3cb733276d3e702351e966f5d 5220 fonts-sil-gentiumplus-compact_5.000-4.debian.tar.xz 08c52eee86eda1c578203e8397f044c3eaa0fa1e 5773 fonts-sil-gentiumplus-compact_5.000-4_amd64.buildinfo Checksums-Sha256: 2379b04ebbf6b479b0d59377ae7ae00c9ecc571229e32e61ee678ee596bd26c2 2246 fonts-sil-gentiumplus-compact_5.000-4.dsc 2a790eed6a994bfb4adc577595d1d1ece7150dc4ce91d11b41d7a55b2aee2257 5220 fonts-sil-gentiumplus-compact_5.000-4.debian.tar.xz 3e479d66a0d25cbc90686d0b9990409481de07fc8006de05fda7edd308daea5c 5773
Bug#971195: marked as done (ceres-solver: FTBFS: rm: cannot remove 'debian/tmp/usr/share/doc/ceres/html/_static/js/modernizr.min.js': No such file or directory)
Your message dated Sat, 03 Oct 2020 15:03:43 + with message-id and subject line Bug#971195: fixed in ceres-solver 1.14.0-9 has caused the Debian Bug report #971195, regarding ceres-solver: FTBFS: rm: cannot remove 'debian/tmp/usr/share/doc/ceres/html/_static/js/modernizr.min.js': No such file or directory 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.) -- 971195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceres-solver Version: 1.14.0-8 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 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 '/<>' > # make lintian happy > # https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.0 -> > /usr/share/javascript/mathjax > sed -i > 's/https:\/\/cdnjs.cloudflare.com\/ajax\/libs\/mathjax\/2.7.1/\/usr\/share\/javascript\/mathjax/g' > /<>/debian/tmp/usr/share/doc/ceres/html/*.html > rm debian/tmp/usr/share/doc/ceres/html/_static/jquery.js > ln -s /usr/share/javascript/jquery/jquery.js > debian/tmp/usr/share/doc/ceres/html/_static/jquery.js > rm debian/tmp/usr/share/doc/ceres/html/_static/js/modernizr.min.js > rm: cannot remove > 'debian/tmp/usr/share/doc/ceres/html/_static/js/modernizr.min.js': No such > file or directory > make[1]: *** [debian/rules:65: override_dh_installdocs] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/ceres-solver_1.14.0-8_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 --- Source: ceres-solver Source-Version: 1.14.0-9 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ceres-solver, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ceres-solver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 16:50:51 +0200 Source: ceres-solver Architecture: source Version: 1.14.0-9 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Jochen Sprickerhof Closes: 971195 Changes: ceres-solver (1.14.0-9) unstable; urgency=medium . * Fix js replacement in -doc. Thanks to Nick Lamprianidis (Closes: #971195) * Drop wrong lintian-overrides Checksums-Sha1: a838164d7142f4c63ad3de2b276758133d879f56 2347 ceres-solver_1.14.0-9.dsc e9658bd44e7ca78d7b1a509edeb118d1969d116f 5996 ceres-solver_1.14.0-9.debian.tar.xz 69113e0e15df1321fd0aa425e8eedd59255877ef 9132 ceres-solver_1.14.0-9_source.buildinfo Checksums-Sha256: 49c0e06ec6607d8fbd872fcaef2665d19abeb7b5643854c6f787f85522869fd2 2347 ceres-solver_1.14.0-9.dsc 2c2b47dde744a4b3cc3d44b0901ea98f9d09943f01d9d643c773753c633e0689 5996 ceres-solver_1.14.0-9.debian.tar.xz 393e5069426265b30bb6b1a3641a46412383de16f135b7b8e83654e226d7f6ed 9132 ceres-solver_1.14.0-9_source.buildinfo Files: af9c52cf18863308b4c88c4dd58c8687 2347 math optional ceres-solver_1.14.0-9.dsc 1dd07af8cf676841941099e09f4068fa 5996 math optional ceres-solver_1.14.0-9.debian.tar.xz ae6c2d07cdcce2a088a18de4df5e621b 9132 math optional ceres-solver_1.14.0-9_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl94j+IACgkQW//cwljm lDMTFg//Zqxu27GHYF3PGZio49rfEPH5wAUtAx3zNmdS1HsOhBqWPZyAj5HGI5v1 WEotl1Th9evlXEMFjbcTRYBquRS5WyrydhtKdruHmBIjuLcRUVOPDWh8z76U4+Zj tBDpKig9h5UtpNNIIaPp+fQbCPEKx85XNNJYRlKRCNDO3NAOaUK7hQ5lAdiZrHw/ I8VXmK9r/P8VuGq/afnU0ZaY6WpfuhjENqcVcj1mXJtvz0iWN/E5hViV5joZMKAJ 2y+ABC5MigbhVsbF0tP1R1E0wPmVBfhRV3qHCvdi3t4aRZlsdKXNVxID4Xp8vyhQ
Bug#971611: marked as pending in fonts-sil-gentiumplus-compact
Control: tag -1 pending Hello, Bug #971611 in fonts-sil-gentiumplus-compact reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/fonts-team/fonts-sil-gentiumplus-compact/-/commit/f74d81dec807cb0d8d024a4f6687d7e485c1730e Avoid conflict with fonts-sil-gentiumplus (Closes: #971611) (this message was generated automatically) -- Greetings https://bugs.debian.org/971611
Processed: Bug#971611 marked as pending in fonts-sil-gentiumplus-compact
Processing control commands: > tag -1 pending Bug #971611 [fonts-sil-gentiumplus-compact] fonts-sil-gentiumplus-compact: upgrade to version 5.000-3 fails trying to overwrite directory Added tag(s) pending. -- 971611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: astroplan: FTBFS: AssertionError in test_schedule_insert_slot
Processing commands for cont...@bugs.debian.org: > package src:astroplan Limiting to bugs with field 'package' containing at least one of 'src:astroplan' Limit currently set to 'package':'src:astroplan' > retitle 971120 astroplan: FTBFS: AssertionError in test_schedule_insert_slot Bug #971120 [src:astroplan] astroplan: FTBFS: WARNING: CacheMissingWarning: Remote data cache could not be accessed due to FileNotFoundError: [Errno 2] No such file or directory: '/sbuild-nonexistent/.astropy' [astroplan.utils] Changed Bug title to 'astroplan: FTBFS: AssertionError in test_schedule_insert_slot' from 'astroplan: FTBFS: WARNING: CacheMissingWarning: Remote data cache could not be accessed due to FileNotFoundError: [Errno 2] No such file or directory: '/sbuild-nonexistent/.astropy' [astroplan.utils]'. > forwarded 971120 https://github.com/astropy/astroplan/issues/475 Bug #971120 [src:astroplan] astroplan: FTBFS: AssertionError in test_schedule_insert_slot Set Bug forwarded-to-address to 'https://github.com/astropy/astroplan/issues/475'. > End of message, stopping processing here. Please contact me if you need assistance. -- 971120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963798: marked as done (srt: empty documentation package)
Your message dated Sat, 03 Oct 2020 14:50:40 +
with message-id
and subject line Bug#963798: fixed in srt 1.4.2-1
has caused the Debian Bug report #963798,
regarding srt: empty documentation package
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.)
--
963798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: srt
Version: 1.4.1-5
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear colleagues,
Doing a no-change rebuild of srt for buster-backports/amd64, I noticed that
'gbp buildpackage' fails on 'dh clean --with sphinxdoc':
dpkg-checkbuilddeps: error: Unmet build dependencies: cmake chrpath help2man
libgnutls28-dev libssl-dev pkg-config tclsh
.[1;33mW: Unmet build-dependency in source.[0m
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 001-multiarch-rpath.patch
dh clean --with sphinxdoc
dh: error: unable to load addon sphinxdoc: Can't locate
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the
Debian::Debhelper::Sequence
BEGIN failed--compilation aborted at (eval 14) line 1.
make: *** [debian/rules:21: clean] Error 25
The core issue is that sphinxdoc is installed in chroot while dh_clean is first
called on host system. Figuring this out, I noticed that libsrt-doc has no files
except of changelog.gz and copyright.
I fixed the issues and provided a doc-base registration of HTML manual.
Please review the attached patches and upload a backportvto buster once fixed.
Vasyl
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-108-generic (SMP w/6 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to
en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
>From ec7f2e365f90ea8d2d9e7b7f730f902d9b59b6b8 Mon Sep 17 00:00:00 2001
From: Vasyl Gello
Date: Fri, 19 Jun 2020 08:09:12 +
Subject: [PATCH 1/4] debian: move python3-sphinx to Build-Depends-Indep
Fixes FTBFS edge case using pbuilder chroot, when dh_clean invoked
on host system to build source package fails to find debhelper sequence
provided by a package listed in Build-Depends and installed later inside
the chroot.
The solution is adapted from pynfft package:
https://salsa.debian.org/science-team/pynfft/-/commit/4c4c47acc0dba6ee0f3fa6cf4c3fc6ffbe41
The "override_dh_auto_build" conflicts with
"override_dh_auto_build-{arch,indep}", so
renaming "override_dh_auto_build" to "override_dh_auto_build-arch".
Thanks-To: to Mattia Rizzolo
Signed-off-by: Vasyl Gello
---
debian/control | 2 +-
debian/rules | 6 --
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/debian/control b/debian/control
index 063cae9..58c9ae8 100644
--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,8 @@ Build-Depends: debhelper-compat (= 13),
libgnutls28-dev,
libssl-dev,
pkg-config,
- python3-sphinx,
tclsh
+Build-Depends-Indep: python3-sphinx
Standards-Version: 4.5.0
Section: libs
Homepage: https://github.com/Haivision/srt
diff --git a/debian/rules b/debian/rules
index 7a832ed..081541a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -18,7 +18,7 @@ include /usr/share/dpkg/default.mk # provides DEB_VERSION
export USE_ENCLIB=gnutls
%:
- dh $@ --with sphinxdoc
+ dh $@
override_dh_auto_clean:
dh_clean
@@ -33,12 +33,14 @@ override_dh_auto_configure:
cd build-openssl && cmake .. $(CMAKE_OPTS) -DUSE_ENCLIB=openssl
cd build-gnutls && cmake .. $(CMAKE_OPTS) -DUSE_ENCLIB=gnutls
-DTARGET_srt=srt-gnutls
-override_dh_auto_build:
+override_dh_auto_build-arch:
#dh_auto_build --builddirectory=debian/build/openssl
#dh_auto_build --builddirectory=debian/build/gnutls
mkdir -p build-openssl build-gnutls
cd build-openssl && $(MAKE)
cd build-gnutls && $(MAKE)
+
+override_dh_auto_build-indep:
http_proxy='http://127.0.0.1:9/' python3 -m sphinx -N -c debian -bhtml
docs debian/html
override_dh_auto_install:
--
2.27.0
>From 6a0ca791c0c832dda75f6f00b0453b34933cf4ab Mon Sep 17 00:00:00 2001
From: Vasyl Gello
Date: Sat, 27 Jun 2020 10:49:24 +
Subject: [PATCH 2/4] debian: install HTML documents to libsrt-doc
Documents generated by sphinx were installed nowhere,
and libsrt-doc had no
Bug#971541: marked as done (astroquery: autopkgtest failure on armhf)
Your message dated Sat, 03 Oct 2020 14:34:26 +
with message-id
and subject line Bug#971541: fixed in astroquery 0.4.1+dfsg-2
has caused the Debian Bug report #971541,
regarding astroquery: autopkgtest failure on armhf
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.)
--
971541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroquery
Version: 0.4.1+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Autopkgtests have recently started running on armhf, and there
astroquery fails [1].
I've copied what I hope is the relevant part of the log below.
I've marked this as a regression as 0.3.9+dfsg-1 passes in Debian
stable, and 0.4+dfsg-3 passes in Ubuntu.
Regards
Graham
[1] https://ci.debian.net/packages/a/astroquery/testing/armhf/
=== FAILURES ===
_ test_all_tables[toi-query34] _
self =
cols = [,
,
, , , ...]
def _convert_vals(self, cols):
for col in cols:
# If a specific dtype was specified for a column, then use that
# to set the defaults, otherwise use the generic defaults.
default_converters = ([convert_numpy(col.dtype)] if col.dtype
else self.default_converters)
# If the user supplied a specific convert then that takes
precedence over defaults
converters = self.converters.get(col.name, default_converters)
col.converters = self._validate_and_copy(col, converters)
# Catch the last error in order to provide additional information
# in case all attempts at column conversion fail. The initial
# value of of last_error will apply if no converters are defined
# and the first col.converters[0] access raises IndexError.
last_err = 'no converters defined'
while not hasattr(col, 'data'):
try:
converter_func, converter_type = col.converters[0]
if not issubclass(converter_type, col.type):
raise TypeError('converter type does not match
column type')
> col.data = converter_func(col.str_vals)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:960:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
vals = ['9048843364125']
def generic_converter(vals):
> return numpy.array(vals, numpy_type)
E OverflowError: Python int too large to convert to C long
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:904: OverflowError
During handling of the above exception, another exception occurred:
patch_get = <_pytest.monkeypatch.MonkeyPatch object at 0xf299fb08>
table = 'toi', query = {'where': 'toi=256.01'}
@pytest.mark.filterwarnings("error")
@pytest.mark.parametrize("table,query", ALL_TABLES)
def test_all_tables(patch_get, table, query):
> data = NasaExoplanetArchive.query_criteria(table, select="*", **query)
/usr/lib/python3/dist-packages/astroquery/nasa_exoplanet_archive/tests/test_nasa_exoplanet_archive.py:188:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3/dist-packages/astroquery/utils/class_or_instance.py:25: in f
return self.fn(obj, *args, **kwds)
/usr/lib/python3/dist-packages/astroquery/utils/process_asyncs.py:29:
in newmethod
result = self._parse_result(response, verbose=verbose)
/usr/lib/python3/dist-packages/astroquery/nasa_exoplanet_archive/core.py:471:
in _parse_result
data = ascii.read(text, format="ipac", fast_reader=False,
converters=CONVERTERS)
/usr/lib/python3/dist-packages/astropy/io/ascii/ui.py:323: in read
dat = reader.read(table)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:1209: in read
table = self.outputter(cols, self.meta)
/usr/lib/python3/dist-packages/astropy/io/ascii/core.py:990: in __call__
self._convert_vals(cols)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
cols = [,
,
, , , ...]
def _convert_vals(self, cols):
for col in cols:
# If a specific dtype was specified for a column, then use that
# to set the defaults, otherwise use the generic defaults.
default_converters = ([convert_numpy(col.dtype)] if col.dtype
else
Bug#966950: marked as done (espresso: FTBFS: Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar))
Your message dated Sat, 03 Oct 2020 12:33:32 + with message-id and subject line Bug#966950: fixed in espresso 6.5-2 has caused the Debian Bug report #966950, regarding espresso: FTBFS: Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar) 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.) -- 966950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: espresso Version: 6.5-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[3]: Entering directory '/<>/UtilXlib' > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -x f95-cpp-input -D__FFTW3 -D__MPI -D__SCALAPACK > -I/<>//include -I/<>//FoX/finclude > -I/<>//S3DE/iotk/include/ -I. -c parallel_include.f90 > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -x f95-cpp-input -D__FFTW3 -D__MPI -D__SCALAPACK > -I/<>//include -I/<>//FoX/finclude > -I/<>//S3DE/iotk/include/ -I. -c util_param.f90 > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -x f95-cpp-input -D__FFTW3 -D__MPI -D__SCALAPACK > -I/<>//include -I/<>//FoX/finclude > -I/<>//S3DE/iotk/include/ -I. -c clocks_handler.f90 > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -x f95-cpp-input -D__FFTW3 -D__MPI -D__SCALAPACK > -I/<>//include -I/<>//FoX/finclude > -I/<>//S3DE/iotk/include/ -I. -c cuda_util.f90 > mpif90 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > -x f95-cpp-input -D__FFTW3 -D__MPI -D__SCALAPACK > -I/<>//include -I/<>//FoX/finclude > -I/<>//S3DE/iotk/include/ -I. -c mp.f90 > mp.f90:2657:19: > > 2657 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_DOUBLE_PRECISION, & > | 1 > .. > 2701 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/COMPLEX(8)). > mp.f90:2662:19: > > 2662 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_DOUBLE_PRECISION, & > | 1 > .. > 2706 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (REAL(8)/COMPLEX(8)). > mp.f90:2613:19: > > 2613 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_INTEGER, & > | 1 > .. > 2701 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2618:19: > > 2618 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_INTEGER, & > | 1 > .. > 2706 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2569:19: > > 2569 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_INTEGER, & > | 1 > .. > 2701 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2574:19: > > 2574 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_INTEGER, & > | 1 > .. > 2706 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2525:19: > > 2525 |CALL MPI_Irecv( recvbuf, 1, MPI_INTEGER, & > | 1 > .. > 2701 |CALL MPI_Irecv( recvbuf, size(recvbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2530:19: > > 2530 |CALL MPI_Isend( sendbuf, 1, MPI_INTEGER, & > | 1 > .. > 2706 |CALL MPI_Isend( sendbuf, size(sendbuf), MPI_DOUBLE_COMPLEX, & > | 2 > Error: Type mismatch between actual argument at (1) and actual argument at > (2) (INTEGER(4)/COMPLEX(8)). > mp.f90:2453:30: > > 2453 |CALL
Bug#971618: marked as done (diaspora: aspects membership list is broken)
Your message dated Sat, 03 Oct 2020 12:18:27 + with message-id and subject line Bug#971618: fixed in diaspora 0.7.14.0-8 has caused the Debian Bug report #971618, regarding diaspora: aspects membership list is broken 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.) -- 971618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diaspora Version: 0.7.14.0-7 Severity: grave Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8158 Attaching screenshot of broken aspect selection list. This is possibly caused by newer version of jquery in debian (upstream is still using jquery 3.4.1 and we are already on 3.5.1 which dropped support for self closing html tags). Though trying with older versions of jquery from rubygems.org/rails-assets.org (jquery-ui-rails, rails-assets-jquery) did not fix it. Another possibility is mismatch in backbone.js versions. --- End Message --- --- Begin Message --- Source: diaspora Source-Version: 0.7.14.0-8 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of diaspora, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated diaspora package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 17:27:37 +0530 Source: diaspora Architecture: source Version: 0.7.14.0-8 Distribution: experimental Urgency: medium Maintainer: Debian Ruby Team Changed-By: Pirate Praveen Closes: 971618 Changes: diaspora (0.7.14.0-8) experimental; urgency=medium . * Use rails-assets-backbone instead of backbone-on-rails * Fix all invalid self-closing tags (Closes: #971618) Thanks again to Akshay S Dinesh. Checksums-Sha1: c941a8cd06626df2c4ccb500a34da5e16fa7b7af 2061 diaspora_0.7.14.0-8.dsc 8c09cd1586bd33212dfaa11a188d5c7338d3d671 383896 diaspora_0.7.14.0-8.debian.tar.xz 285f15b4e549c71652b8b2f494511fb74ed2e7a7 8518 diaspora_0.7.14.0-8_amd64.buildinfo Checksums-Sha256: a09907b0ead51960d341655d70a7ac524a179eb4cb801702487a76876ca2ec60 2061 diaspora_0.7.14.0-8.dsc 03b85716686dd0729161e4a85141d8cf16bd38ebbb9e58f717e9d710b439bae7 383896 diaspora_0.7.14.0-8.debian.tar.xz d40ec01e4766976ce3efb997c6be40c256d6f837117c86b49ea0e25bd76c081d 8518 diaspora_0.7.14.0-8_amd64.buildinfo Files: 1091dfc1cdfab7323035b4fe7bc56a5e 2061 net optional diaspora_0.7.14.0-8.dsc f84a28b091641dad05eb2dd97af8 383896 net optional diaspora_0.7.14.0-8.debian.tar.xz 3f76c7a227cd18c7e2788d1c9220992b 8518 net optional diaspora_0.7.14.0-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl94aGIACgkQj1PgGTsp S3VIpxAAkkun2g2fk2QeckiUupPWpa+METWlxnv9PKPJJ24jOmH06J6QuID1xzqP x78DOdgPVfM0Yua49KF+RdqXJnIJ5oR6GUN9BSwv9GE6Zg51SHz66FHSmJlVLHGw kti5ikrkUOVIDFwOiGIquvy6eaYRLYnol/wEVHt45j+gP0KMwV+Dcc4t5/s3jXRf T4mx8XGHU4B4ZyQoYc5IYH+6wLHhQk1ITW4ffNDbAThnyduFS6MmD1JHymuzlsCN OTy7xe/r6RTqeYKkH8rUMbz0dFBIxTtVKFAzb1azk1y2iw4CCNgdIsxKo8UEk5v0 WqZuPNhNb5iF70Kx+1UD/fme6IC9u8s73HyQ3eySuQmoYoh9rvw4fl9abVEum9cq eYn8cwaOrGkrDAnG0KoqHCWWDl6zdYsvRdDDCLMrFBu6hJXiSK3+yqXrQmjhQDXM q6d1wEFhoQ2/b0PThz+k0tOAwklJKt6jgTfCXKH7T6dcWzw51fcyvJKb3+vb3DPk 8hKBKSEiiPxAlszBhTGpyMnXS8E2CUDzOLOTyEO97kXKU6DwNL4zTtsSi805VY5l enVSTY6w7uWDgX8PmIHizCIbUMhDgBmzoBOw9+Aq3P1HwcAobTIiJeeZPoNlAXZH J3C4fD9GOnkwbWpICTEeH46EsYbsZTjAuQW0vs41K7BsstfXl3w= =mits -END PGP SIGNATURE End Message ---
Processed: found 971611 in 5.000-3, notfound 971611 in 5.000-2
Processing commands for cont...@bugs.debian.org: > found 971611 5.000-3 Bug #971611 [fonts-sil-gentiumplus-compact] fonts-sil-gentiumplus-compact: upgrade to version 5.000-3 fails trying to overwrite directory Marked as found in versions fonts-sil-gentiumplus-compact/5.000-3. > notfound 971611 5.000-2 Bug #971611 [fonts-sil-gentiumplus-compact] fonts-sil-gentiumplus-compact: upgrade to version 5.000-3 fails trying to overwrite directory No longer marked as found in versions fonts-sil-gentiumplus-compact/5.000-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 971611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fwd: Re: Bug#969788: nextcloud-desktop: Upgrade removed part of configuration
Processing control commands: > severity -1 important Bug #969788 [nextcloud-desktop] nextcloud-desktop: Upgrade removed part of configuration Severity set to 'important' from 'grave' -- 969788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969788: Fwd: Re: Bug#969788: nextcloud-desktop: Upgrade removed part of configuration
Control: severity -1 important
Somehow this message didn't reach the BTS...
Forwarded Message
Von: Sandro Knauß
An: Tobias Frost , 969...@bugs.debian.org, Markus Frosch <
lazyfro...@debian.org>, Erwan David
Betreff: Re: Bug#969788: nextcloud-desktop: Upgrade removed part of
configuration
Datum: Thu, 24 Sep 2020 21:04:34 +0200
> Control: severity 969576 important
>
> Hey,
>
> from my side it seems like not many people have the problem that the
> configuration is lost while doing the upgrade. So I think, it is just a
> normal
> bug you found. Please report it upstream and provide us the url, so that we
> can track the upstream status.
>
> hefee
>
> --
> On Donnerstag, 10. September 2020 20:16:48 CEST you wrote:
> > On Thu, 10 Sep 2020 19:27:37 +0200 Tobias Frost wrote:
> > > I'll see if I can find some logs…
> >
> > Ok, it seems so that my instance deletes its configuration itself…
> >
> > But I think that needs a word on my configuration:
> > ~/Documents is synced with my Nextcloud intance
> > I have setup XDG_DATA and XDG_CONFIG to be on
> > ~/Documents/XDG/$hostname/{XDG_DATA XDG_CONFIG}
> > (to be able to share XDG configurations files on complicant apps more easy
> > between PCs)
> >
> > ~/Documents/XDG/isildor/XDG_CONFIG/Nextcloud is a symlink to
> > ~/.config/Nextcloud (so it is not on the share)
> >
> > It seems that nextcloud app is deleting that file, (following the symlink)
> >
> > Of course this could be a read herring, as I naively tried to reconfigure
> > the nextcloud without deleting Documents and I just got conflict everywhere
> > now.
> >
> > It is possible the the app is following the symlink and thinks, hey , file
> > not on the nextcloud server, delete it… Could be another bug though; (I
> > guess it should not follow symlinks, at least it used to ignore symlinks
> > when syncing to servers)
> >
> > Next step I'll try a fresh resync…
>
> --
> Mein öffentlicher Schlüssel / My public key: E68031D299A6527C
> Fingerabdruck / Fingerprint:
> D256 4951 1272 8840 BB5E 99F2 E680 31D2 99A6 527C
> Runterladen z.B. bei/ Get it e.g. here:
> pool.sks-keyservers.net, ...
>
> Ich habe meinen Schlüssel 2015 gewechselt / I've switched my GnuPG key 2015.
> Hier ein Dokument, was meinen Wechsel deutlich macht ( mit beiden Schlüsseln
> unterschrieben)
> Here's a document, that proves I wanted to do this switch ( it is signed by
> both keys)
> http://sandroknauss.de/files/transition2015.asc
--
mar...@lazyfrosch.de
https://lazyfrosch.de
Bug#957170: marked as done (elpa: ftbfs with GCC-10)
Your message dated Sat, 03 Oct 2020 11:03:27 + with message-id and subject line Bug#957170: fixed in elpa 2019.11.001-4 has caused the Debian Bug report #957170, regarding elpa: 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.) -- 957170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:elpa Version: 2016.05.001-6 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/elpa_2016.05.001-6_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 [...] .. 3473 | call mpi_allreduce(z, tmp, n, MPI_REAL8, MPI_PROD, mpi_comm_rows, mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(8)/REAL(8)). src/elpa1_compute.F90:1357:27: 1357 | call mpi_allreduce(xc,vav,1,MPI_DOUBLE_COMPLEX,MPI_SUM,mpi_comm_cols,mpierr) | 1 .. 3473 | call mpi_allreduce(z, tmp, n, MPI_REAL8, MPI_PROD, mpi_comm_rows, mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (COMPLEX(8)/REAL(8)). src/elpa1_compute.F90:923:25: 923 | call MPI_Bcast(aux_bc,n_aux_bc,MPI_REAL8,np_bc,mpi_comm_cols,mpierr) | 1 .. 4484 |call MPI_Bcast(tmp1,nb*(nb+1)/2,MPI_DOUBLE_COMPLEX,pcol(n, nblk, np_cols),mpi_comm_cols,mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/COMPLEX(8)). src/elpa1_compute.F90:970:30: 970 | call mpi_reduce(tmp1,tmp2,nstor*(lce-lcs+1),MPI_REAL8,MPI_SUM,np,mpi_comm_rows,mpierr) | 1 .. 1914 |call mpi_reduce(tmp1,tmp2,nstor*(lce-lcs+1),MPI_DOUBLE_COMPLEX,MPI_SUM,np,mpi_comm_rows,mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/COMPLEX(8)). src/elpa1_compute.F90:670:27: 670 | call MPI_Bcast(hvb,nb,MPI_REAL8,cur_pcol,mpi_comm_cols,mpierr) | 1 .. 4484 |call MPI_Bcast(tmp1,nb*(nb+1)/2,MPI_DOUBLE_COMPLEX,pcol(n, nblk, np_cols),mpi_comm_cols,mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/COMPLEX(8)). src/elpa1_compute.F90:325:24: 325 | call MPI_Bcast(vr,l_rows+1,MPI_REAL8,pcol(istep, nblk, np_cols),mpi_comm_cols,mpierr) |1 .. 4484 |call MPI_Bcast(tmp1,nb*(nb+1)/2,MPI_DOUBLE_COMPLEX,pcol(n, nblk, np_cols),mpi_comm_cols,mpierr) | 2 Error: Type mismatch between actual argument at (1) and actual argument at (2) (REAL(8)/COMPLEX(8)). src/elpa1_compute.F90:431:27: 431 | call mpi_allreduce(x,vav,1,MPI_REAL8,MPI_SUM,mpi_comm_cols,mpierr) | 1 .. 3473 | call mpi_allreduce(z, tmp, n, MPI_REAL8, MPI_PROD, mpi_comm_rows, mpierr) | 2 Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar) src/elpa_reduce_add_vectors.X90:146:33: 146 | if(k>0) call mpi_reduce(aux1,aux2,k,MPI_REAL8,MPI_SUM,ipt,comm_t,mpierr) | 1 Error:
Bug#957168: marked as done (elkcode: ftbfs with GCC-10)
Your message dated Sat, 03 Oct 2020 10:48:27 + with message-id and subject line Bug#957168: fixed in elkcode 6.3.2-2 has caused the Debian Bug report #957168, regarding elkcode: 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.) -- 957168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:elkcode Version: 6.3.2-1 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/elkcode_6.3.2-1_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 [...] 13 | proj_x_loc,proj_zona_loc,exclude_bands_loc,proj_s_loc,proj_s_qaxis_loc) | 1 Warning: Unused dummy argument ‘proj_zona_loc’ at (1) [-Wunused-dummy-argument] w90_stub.f90:9:17: 9 | real_lattice_loc,recip_lattice_loc,kpt_latt_loc,num_bands_tot, & | 1 Warning: Unused dummy argument ‘real_lattice_loc’ at (1) [-Wunused-dummy-argument] w90_stub.f90:9:35: 9 | real_lattice_loc,recip_lattice_loc,kpt_latt_loc,num_bands_tot, & | 1 Warning: Unused dummy argument ‘recip_lattice_loc’ at (1) [-Wunused-dummy-argument] w90_stub.f90:8:35: 8 | subroutine wannier_setup(seed__name,mp_grid_loc,num_kpts_loc, & | 1 Warning: Unused dummy argument ‘seed__name’ at (1) [-Wunused-dummy-argument] w90_stub.f90:10:74: 10 | num_atoms_loc,atom_symbols_loc,atoms_cart_loc, gamma_only_loc,spinors_loc, & | 1 Warning: Unused dummy argument ‘spinors_loc’ at (1) [-Wunused-dummy-argument] mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c modw90.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c zfftifc_fftw.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c elk.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c zbsht.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c zfsht.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c rbsht.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c rfsht.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c projsbf.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c fsmooth.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c nfftifc.f90 mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` -Wall -ffast-math -funroll-loops -fopenmp `dpkg-buildflags --get LDFLAGS` -c rfinp.f90 mpif90 `dpkg-buildflags --get FFLAGS`
Processed: Bug#957170 marked as pending in elpa
Processing control commands: > tag -1 pending Bug #957170 [src:elpa] elpa: ftbfs with GCC-10 Added tag(s) pending. -- 957170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957170: marked as pending in elpa
Control: tag -1 pending Hello, Bug #957170 in elpa reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/elpa/-/commit/b86d85247d6b65bbe5bf2730cc33a9c3f75c7b52 * debian/rules (DEB_FCFLAGS_MAINT_APPEND): New variable, appends -fallow-argument-mismatch-fallow-argument-mismatch to the gfortran flags. (Closes: #957170) (this message was generated automatically) -- Greetings https://bugs.debian.org/957170
Processed: Bug#957168 marked as pending in elkcode
Processing control commands: > tag -1 pending Bug #957168 [src:elkcode] elkcode: ftbfs with GCC-10 Added tag(s) pending. -- 957168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957168: marked as pending in elkcode
Control: tag -1 pending Hello, Bug #957168 in elkcode reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/elkcode/-/commit/01a50ed8a1bb9424a2de8cee61284969f1eb1a99 * debian/patches/makeflags.patch: Add -fallow-argument-mismatch to F90_OPTS and F77_OPTS (Closes: #957168). (this message was generated automatically) -- Greetings https://bugs.debian.org/957168
Bug#952356: marked as done (php-sabredav: FTBFS: tests failed)
Your message dated Sat, 03 Oct 2020 10:03:45 + with message-id and subject line Bug#952356: fixed in php-sabredav 1.8.12-9 has caused the Debian Bug report #952356, regarding php-sabredav: FTBFS: tests failed 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.) -- 952356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-sabredav Version: 1.8.12-8 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 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 '/<>' > phpunit --configuration tests/phpunit.xml > PHPUnit 8.5.2 by Sebastian Bergmann and contributors. > > ..SSS..WW..W.W..WWWW...W. 61 / 1201 ( > 5%) > ..WW..W.WWWW..R.. 122 / 1201 ( > 10%) > ..R.R...RR..W..WW 183 / 1201 ( > 15%) > ...W.WWWW...RW..W...W...WW... 244 / 1201 ( > 20%) > .WWWW..WW 305 / 1201 ( > 25%) > .WWWW..WW...RSRSSW.WRSRS...RW 366 / 1201 ( > 30%) > .R.WWWW.WW.WW.W...WW...WW.W.. 427 / 1201 ( > 35%) > WW..W.W..RS.. 488 / 1201 ( > 40%) > .WW.WW.W..W.W...WW.E.RW.. 549 / 1201 ( > 45%) > W.SS...RW..WW...WWWWWR.S.RW...RRR 610 / 1201 ( > 50%) > W 671 / 1201 ( > 55%) > ..R...... 732 / 1201 ( > 60%) > ...W. 793 / 1201 ( > 66%) > ..W.W..W.WW.. 854 / 1201 ( > 71%) > WW..W..WWW..R..W. 915 / 1201 ( > 76%) > ..WW...WW 976 / 1201 ( > 81%) > ...WW...WW.W.WWW. 1037 / 1201 ( > 86%) > .W.WW..W.S... 1098 / 1201 ( > 91%) > WW.W.R.RW.WW...W..WRSS... 1159 / 1201 ( > 96%) > .E1201 / 1201 > (100%) > > Time: 2.63 seconds, Memory: 30.00 MB > > There were 2 errors: > > 1) Sabre\DAV\Auth\Backend\AbstractDigestTest::testAuthenticateNoHeaders > Trying to access array offset on value of type bool > > /<>/lib/Sabre/HTTP/DigestAuth.php:125 > /<>/lib/Sabre/DAV/Auth/Backend/AbstractDigest.php:61 > /<>/tests/Sabre/DAV/Auth/Backend/AbstractDigestTest.php:22 > > 2) Sabre\HTTP\DigestAuthTest::testInvalidDigest2 > Trying to access array offset on value of type bool > > /<>/lib/Sabre/HTTP/DigestAuth.php:136 > /<>/lib/Sabre/HTTP/DigestAuth.php:100 > /<>/tests/Sabre/HTTP/DigestAuthTest.php:164 > > -- > > There were 140 warnings: > > 1) Sabre\CalDAV\Backend\PDOSQLiteTest::testCreateCalendarAndFetch > assertInternalType() is deprecated and will be removed in PHPUnit 9. Refactor > your test to use assertIsArray(), assertIsBool(), assertIsFloat(), > assertIsInt(), assertIsNumeric(), assertIsObject(), assertIsResource(), > assertIsString(), assertIsScalar(), assertIsCallable(), or assertIsIterable() > instead. > > 2) Sabre\CalDAV\Backend\PDOSQLiteTest::testUpdateCalendarAndFetch > assertInternalType() is deprecated and will be removed in PHPUnit 9. Refactor > your test to use assertIsArray(), assertIsBool(), assertIsFloat(), > assertIsInt(), assertIsNumeric(), assertIsObject(), assertIsResource(), > assertIsString(), assertIsScalar(), assertIsCallable(), or assertIsIterable() > instead. > > 3) Sabre\CalDAV\Backend\PDOSQLiteTest::testCreateCalendarIncorrectComponentSet > The @expectedException, @expectedExceptionCode, @expectedExceptionMessage, > and @expectedExceptionMessageRegExp annotations are deprecated. They will be > removed in PHPUnit 9. Refactor your test to use expectException(), > expectExceptionCode(), expectExceptionMessage(), or > expectExceptionMessageRegExp() instead. > > 4) Sabre\CalDAV\Backend\PDOSQLiteTest::testCreateCalendarObjectNoComponent > The @expectedException, @expectedExceptionCode, @expectedExceptionMessage, > and @expectedExceptionMessageRegExp annotations are deprecated. They will be > removed
Bug#943210: marked as done (php-sabredav: Python2 removal in sid/bullseye)
Your message dated Sat, 03 Oct 2020 10:03:45 + with message-id and subject line Bug#943210: fixed in php-sabredav 1.8.12-9 has caused the Debian Bug report #943210, regarding php-sabredav: Python2 removal in sid/bullseye 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.) -- 943210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-sabredav Version: 1.8.12-8 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: php-sabredav Source-Version: 1.8.12-9 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of php-sabredav, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated php-sabredav package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 03 Oct 2020 08:54:41 + Source: php-sabredav Architecture: source Version: 1.8.12-9 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Mike Gabriel Closes: 943210 952356 Changes: php-sabredav (1.8.12-9) unstable; urgency=medium . * debian/patches: + Add 0012-py2to3.patch. Port Python scripts from Py2 to Py3. + Add 0013-phpunit-8.x+9.x.patch. Adapt unit tests to PHPUnit 8.x/9.x. (Closes: #952356). + Add 0014-array-access-as-bool.patch. Don't access variable as array, if actually boolean. + Add 2001-set-sabredav-mysql-password.patch. Set a MySQL user password for autopkgtests. * debian/control: + Switch from python to python3 in B-D and D. (Closes: #943210). + Bump DH compat level to version 13. + Bump Standards-Version: to 4.5.0. No changes needed. * debian/tests/control: + Add restrictions: needs-root, isolation-container. Require php-mysql, mysql-server. * debian/tests/phpunit: + Bootstrap MySQL database, run unit tests unprivileged.
Bug#957084: marked as done (chemtool: ftbfs with GCC-10)
Your message dated Sat, 03 Oct 2020 10:03:31 + with message-id and subject line Bug#957084: fixed in chemtool 1.6.14-6 has caused the Debian Bug report #957084, regarding chemtool: 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.) -- 957084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:chemtool Version: 1.6.14-5 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/chemtool_1.6.14-5_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 [...] main.c: In function ‘file_ok_sel’: main.c:3027:35: note: length computed here 3027 | strncpy (datadir, filename, strlen (filename) - strlen (tempstr) + 1); | ^ In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31, from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtk.h:126, from ct1.h:9, from inout.c:6: /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 73 | GTimeVal last_popdown; | ^~~~ In file included from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /usr/include/glib-2.0/gobject/gbinding.h:28, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from ct1.h:9, from inout.c:6: /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here 551 | struct _GTimeVal |^ inout.c: In function ‘import_pdb’: inout.c:732:13: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 732 | (void)fgets (line, (int)sizeof (line), fp); | ^~~~ inout.c: In function ‘check_babel’: inout.c:6054:13: warning: ignoring return value of ‘fgets’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 6054 | (void)fgets (data, 80, xfile); | ^~~ inout.c: In function ‘check_fig2sxd’: inout.c:6133:3: warning: ignoring return value of ‘fscanf’ declared with attribute ‘warn_unused_result’ [-Wunused-result] 6133 | fscanf (xfile, "%s", myname); | ^~~~ gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,--as-needed -o src-cht/cht cht.o -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype -lX11 -lm gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,--as-needed -o chemtool main.o draw.o graph.o chemproc.o undo.o inout.o -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0
Bug#971519: marked as done (node-locate-character: Rebuild from sources)
Your message dated Sat, 03 Oct 2020 09:49:35 + with message-id and subject line Bug#971519: fixed in node-locate-character 2.0.5+repack-1 has caused the Debian Bug report #971519, regarding node-locate-character: Rebuild from sources 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.) -- 971519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-locate-character Version: 2.0.5-1 Severity: serious Justification: source-is-missing 2.0.5 is packaged from npm registry temporarily to be able to build rollup 2. Upstream didn't push 2.0.5 source in git repo (last github release/HEAD is 2.0.1), then 2.0.5 was packaged from npm registry instead. This bug is a reminder to avoid having 2.0.5-1 pushed outside experimental --- End Message --- --- Begin Message --- Source: node-locate-character Source-Version: 2.0.5+repack-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-locate-character, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-locate-character package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 03 Oct 2020 11:25:59 +0200 Source: node-locate-character Architecture: source Version: 2.0.5+repack-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 932958 971519 Changes: node-locate-character (2.0.5+repack-1) unstable; urgency=medium . * Team upload * Repack using source from https://gitlab.com/Rich-Harris/locate-character/-/commits/master (Closes: #971519), and back to unstable * New upstream version 2.0.5+repack (Closes: #932958) * Restore build and test Checksums-Sha1: 4f31fda9f5ad77717881845122c1c3f9e3b11470 2208 node-locate-character_2.0.5+repack-1.dsc 0538d37c7f415a39b3d7946e508f2159ad0c6943 3130 node-locate-character_2.0.5+repack.orig.tar.gz da30332fb5c8c6a4a30549e0336bfa7caefc2b07 3408 node-locate-character_2.0.5+repack-1.debian.tar.xz Checksums-Sha256: c0d930e51cbf877da921d21a4ff329d252180432703d5ffc54999535e6da3814 2208 node-locate-character_2.0.5+repack-1.dsc e3e543af4ae68fda9707de81fa413c3f0d75b99a94154df5ba8997b5ca5fb313 3130 node-locate-character_2.0.5+repack.orig.tar.gz cbb81f282e860b084732360bf31b1b63fba3e432df7e45b0d966355c2784a1a7 3408 node-locate-character_2.0.5+repack-1.debian.tar.xz Files: 0caaade9b8665307eeaab3699a781e75 2208 javascript optional node-locate-character_2.0.5+repack-1.dsc 4e365dfb6e5a25de49f51a5c5ebcb339 3130 javascript optional node-locate-character_2.0.5+repack.orig.tar.gz 7ed1ec365ed00abf6ade4dfe94ba1a34 3408 javascript optional node-locate-character_2.0.5+repack-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAl94RFUACgkQ9tdMp8mZ 7ukhpBAAmBAswi/lprxnLyAJb69lU9DMjBPZumSX71OSpzvN0yvEt5Y1W7KLoZmi 0ptBuAx57KT5ZLBHDM3UkFcslo1W6zhmaqBFSDq70keKRjMAY1UZPky6O23ghX5n r1zKK+uiIzUiRG838CCqI2+gsofyu+/Xe+XR5U3JVNN4QV2ZmAurCpQlqWtMAQHg LjImdWVt2WEEpD6EmOX9T5cfnGUNyMQo24BA20iGqdtpBi0pihfR3rMMGPGqx/MF YqcXZnsHeDRCDMUpGDEnHot3rTJbXb48OhWVQX/1nJsMsmdgmeZ09FHUr02PpfXN CRE3JIorlVNTGpuRUJmp82h3TEtOjXlPurbTGDFFXqq4BV4SfdeLoCgIL4Le22p+ GB9WY/I0LCwtFcdgtlboCLfXIEDLaNsZ66/ARwGtl6ey2KUzdPtBtN2cVML10Smr 7cqA62F63+HaR7Zc2lv8AZnvBsK5IaE7dcz5/EbPQt5Nh4VndNDSJxPEsiakeb8w /alJLo9LbhgjsV0u86SqOEn1KDMfBoEKdtEWvJSc37pMKf3VaGBJi2A0uo/4Ckic goTj2GsUGWPPf2RRc7uClSKqGS2Ge6+Fb4Q9x0koPPf/RdAqsbfpVxza+kKMNco+ Qn4zt6SHyZinLRoOth8oQbsLMF4p1/aoa3nqlFQPKySw7lj6bH8= =1liI -END PGP SIGNATURE End Message ---
Processed: Bug#957084 marked as pending in chemtool
Processing control commands: > tag -1 pending Bug #957084 [src:chemtool] chemtool: ftbfs with GCC-10 Added tag(s) pending. -- 957084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957084: marked as pending in chemtool
Control: tag -1 pending Hello, Bug #957084 in chemtool reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/chemtool/-/commit/7d0413fe4f5bce35fe9c16fd196758319df05442 * debian/patches/957084_gcc10.patch: New patch, fixes build failure with gcc10/-fno-common (Closes: #957084). (this message was generated automatically) -- Greetings https://bugs.debian.org/957084
Processed: Re: Bug#968157: src:haskell-cborg: testsuite fails due to bus errors on armhf
Processing control commands: > severity -1 important Bug #968157 [src:haskell-cborg] src:haskell-cborg: testsuite fails due to bus errors on armhf Severity set to 'important' from 'serious' -- 968157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968157: src:haskell-cborg: testsuite fails due to bus errors on armhf
Control: severity -1 important haskell-cborg has been removed from armhf (see #968084). Lowering the severity to allow it to migrate to testing. -- Ilias
Bug#971618: diaspora: aspects membership list is broken
Package: diaspora Version: 0.7.14.0-7 Severity: grave Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8158 Attaching screenshot of broken aspect selection list. This is possibly caused by newer version of jquery in debian (upstream is still using jquery 3.4.1 and we are already on 3.5.1 which dropped support for self closing html tags). Though trying with older versions of jquery from rubygems.org/rails-assets.org (jquery-ui-rails, rails-assets-jquery) did not fix it. Another possibility is mismatch in backbone.js versions.
Processed: diaspora: aspects membership list is broken
Processing control commands: > forwarded -1 https://github.com/diaspora/diaspora/issues/8158 Bug #971618 [diaspora] diaspora: aspects membership list is broken Set Bug forwarded-to-address to 'https://github.com/diaspora/diaspora/issues/8158'. -- 971618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#887635: marked as done (dms binary-any FTBFS)
Your message dated Sat, 03 Oct 2020 07:05:10 + with message-id and subject line Bug#970903: Removed package(s) from unstable has caused the Debian Bug report #887635, regarding dms binary-any FTBFS 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.) -- 887635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dms Version: 1.0.8.1-1 Severity: serious https://buildd.debian.org/status/package.php?p=dms=sid ... dh_install make[1]: Leaving directory '/<>' dh_installdocs -a debian/rules override_dh_sphinxdoc make[1]: Entering directory '/<>' dh_sphinxdoc -X searchtools.js -X translations.js dh_sphinxdoc: Sphinx documentation not found dh_sphinxdoc /usr/share/doc/dms-doc/html/ dh_sphinxdoc: Path /usr/share/doc/dms-doc/html/ not found in any built package (searched in: dms-core dms-wsgi dms-dr dms) debian/rules:52: recipe for target 'override_dh_sphinxdoc' failed make[1]: *** [override_dh_sphinxdoc] Error 2 Can be reproduced with "dpkg-buildpackage -B". --- End Message --- --- Begin Message --- Version: 1.0.8.1-1+rm Dear submitter, as the package dms 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/970903 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#904297: marked as done (dms-core: fails to install: calls /etc/init.d/procps incorrectly)
Your message dated Sat, 03 Oct 2020 07:05:10 +
with message-id
and subject line Bug#970903: Removed package(s) from unstable
has caused the Debian Bug report #904297,
regarding dms-core: fails to install: calls /etc/init.d/procps incorrectly
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.)
--
904297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dms-core
Version: 1.0.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Selecting previously unselected package dms-core.
(Reading database ...
(Reading database ... 10054 files and directories currently installed.)
Preparing to unpack .../dms-core_1.0.8.1-1_amd64.deb ...
Unpacking dms-core (1.0.8.1-1) ...
Setting up dms-core (1.0.8.1-1) ...
Adding user `dmsdmd' to group `bind' ...
Adding user dmsdmd to group bind
Done.
Adding user `dmsdmd' to group `dms' ...
Adding user dmsdmd to group dms
Done.
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
dpkg: error processing package dms-core (--configure):
installed dms-core package post-installation script subprocess returned
error exit status 3
Errors were encountered while processing:
dms-core
cheers,
Andreas
dms-core_1.0.8.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.0.8.1-1+rm
Dear submitter,
as the package dms 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/970903
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#971615: golang-github-russellhaering-goxmldsig: CVE-2020-15216
Source: golang-github-russellhaering-goxmldsig Version: 0.0~git20180430.7acd5e4-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-russellhaering-goxmldsig. CVE-2020-15216[0]: | In goxmldsig (XML Digital Signatures implemented in pure Go) before | version 1.1.0, with a carefully crafted XML file, an attacker can | completely bypass signature validation and pass off an altered file as | a signed one. A patch is available, all users of goxmldsig should | upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 | or version 1.1.0 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-15216 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15216 [1] https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7 [2] https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64 Regards, Salvatore
Bug#971609: r-cran-sna: Not build in Debian, unsatisfiable build-deps
Control: block -1 by 951510 Control: block -1 by 951511 On Fri, Oct 02, 2020 at 03:13:33PM -0700, Steve Langasek wrote: > So it would be good if those would get uploaded to the archive, given there > is another package that build-depends on them. The question "Shall we re-submit, or is that not enough?" in [1] was never answered and so nothing happened from our side. I have just re-uploaded - lets see what might happen. Kind regards Andreas. [1] https://alioth-lists.debian.net/pipermail/r-pkg-team/2020-February/010262.html -- http://fam-tille.de
Processed: Re: Bug#971609: r-cran-sna: Not build in Debian, unsatisfiable build-deps
Processing control commands: > block -1 by 951510 Bug #971609 [src:r-cran-sna] r-cran-sna: Not build in Debian, unsatisfiable build-deps 971609 was not blocked by any bugs. 971609 was not blocking any bugs. Added blocking bug(s) of 971609: 951510 > block -1 by 951511 Bug #971609 [src:r-cran-sna] r-cran-sna: Not build in Debian, unsatisfiable build-deps 971609 was blocked by: 951510 971609 was not blocking any bugs. Added blocking bug(s) of 971609: 951511 -- 971609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958579: marked as done (cgmanager: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Sat, 03 Oct 2020 06:13:48 + with message-id and subject line Bug#834540: Removed package(s) from unstable has caused the Debian Bug report #958579, regarding cgmanager: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cgmanager Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package cgmanager declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Version: 0.41-2+rm Dear submitter, as the package cgmanager 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/834540 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 ---
