Bug#972744: marked as done (openstack-debian-images: bullseye: /updates -> -security)

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 07:52:05 +
with message-id 
and subject line Bug#972744: fixed in openstack-debian-images 1.49
has caused the Debian Bug report #972744,
regarding openstack-debian-images: bullseye: /updates -> -security
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.)


-- 
972744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-debian-images
Version: 1.47
Severity: serious
File: /usr/sbin/build-openstack-debian-image
User: debian-de...@lists.debian.org
Usertags: bullseye-security

With the release of Debian bullseye and later, security updates are
provided in the bullseye-security suite instead of bullseye/updates.

The above script references ${RELEASE}/updates but when bullseye is
released that should be replaced by ${RELEASE}-security so it looks
like the script would generate an incorrect sources.list using /updates
instead of -security which would cause the target system to not get
security updates from bullseye in a timely manner, which could be
problematic for openstack images since IIRC those have automatic
security updates enabled and so no human will notice this issue.

I suggest that this script check the version of the Debian release in
question using distro-info and then if the release is 11 or higher,
then use $release-security otherwise use $release/updates as before.

It is much better to use distro-info than to hard-code the release
version numbers. It might even be a good idea to include the security
suite information in distro-info itself and look it up there.

   $ grep -B3 -A2 /updates /usr/sbin/build-openstack-debian-image
   if [ "${RELEASE}" != "sid" ] && [ "${RELEASE}" != "unstable" ] ; then
echo "deb ${SOURCE_LIST_MIRROR} ${RELEASE}-updates main${NON_FREE}
   deb-src ${SOURCE_LIST_MIRROR} ${RELEASE}-updates main${NON_FREE}
   deb ${SECURITY_MIRROR_URL} ${RELEASE}/updates main${NON_FREE}
   deb-src ${SECURITY_MIRROR_URL} ${RELEASE}/updates main${NON_FREE}
   " >>${MOUNT_DIR}/etc/apt/sources.list
   fi

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: openstack-debian-images
Source-Version: 1.49
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
openstack-debian-images, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openstack-debian-images 
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: Mon, 02 Nov 2020 08:32:14 +0100
Source: openstack-debian-images
Architecture: source
Version: 1.49
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 972744
Changes:
 openstack-debian-images (1.49) unstable; urgency=medium
 .
   * Use "bullseye-security" instead of "bullseye-updates" (Closes: #972744).
Checksums-Sha1:
 edad7b633229f74e465c0cc3e13cba5ab9baaf18 1759 openstack-debian-images_1.49.dsc
 691a8b37d46cd98359526475fb1e6133256a4d42 31088 
openstack-debian-images_1.49.tar.xz
 26a49b1bf4b26b50aaa82e0645141bd9ce6d2715 5913 
openstack-debian-images_1.49_amd64.buildinfo
Checksums-Sha256:
 2536fcdae25332af00b8964e1a954c721698cc6d888b05377fdfc34a0a56eb76 1759 
openstack-debian-images_1.49.dsc
 feaae62f7cbde4797c9bad5e046bf3f313a2efb6ccb56118a2ccc331203536cd 31088 
openstack-debian-images_1.49.tar.xz
 a29b063c0c9efa7ba67d358c7dabeb16ce44e3533169029

Bug#972966: marked as done (tensorpipe FTBFS on armel/mipsel/m68k/powerpc/riscv64/sh4: undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0')

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 05:04:58 +
with message-id 
and subject line Bug#972966: fixed in tensorpipe 0.0~git20200928.95ff931-1
has caused the Debian Bug report #972966,
regarding tensorpipe FTBFS on armel/mipsel/m68k/powerpc/riscv64/sh4: undefined 
reference to symbol '__atomic_load_8@@LIBATOMIC_1.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.)


-- 
972966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tensorpipe
Version: 0.0~git20200805.42033c5-3
Severity: important
Tags: ftbfs patch

https://buildd.debian.org/status/package.php?p=tensorpipe&suite=sid

...
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now 
CMakeFiles/tensorpipe_test.dir/test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/context_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/connection_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/uv/uv_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/uv/context_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/uv/loop_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/uv/connection_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/uv/sockaddr_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/listener_test.cc.o 
CMakeFiles/tensorpipe_test.dir/core/context_test.cc.o 
CMakeFiles/tensorpipe_test.dir/proto/core_test.cc.o 
CMakeFiles/tensorpipe_test.dir/channel/basic/basic_test.cc.o 
CMakeFiles/tensorpipe_test.dir/channel/xth/xth_test.cc.o 
CMakeFiles/tensorpipe_test.dir/channel/mpt/mpt_test.cc.o 
CMakeFiles/tensorpipe_test.dir/channel/channel_test.cc.o 
CMakeFiles/tensorpipe_test.dir/common/system_test.cc.o 
CMakeFiles/tensorpipe_test.dir/common/defs_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/shm/reactor_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/shm/loop_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/shm/connection_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/shm/sockaddr_test.cc.o 
CMakeFiles/tensorpipe_test.dir/transport/shm/shm_test.cc.o 
CMakeFiles/tensorpipe_test.dir/util/ringbuffer/shm_ringbuffer_test.cc.o 
CMakeFiles/tensorpipe_test.dir/util/ringbuffer/protobuf_streams_test.cc.o 
CMakeFiles/tensorpipe_test.dir/util/ringbuffer/ringbuffer_test.cc.o 
CMakeFiles/tensorpipe_test.dir/util/shm/segment_test.cc.o 
CMakeFiles/tensorpipe_test.dir/channel/cma/cma_test.cc.o -o tensorpipe_test  
-Wl,-rpath,"/<>/obj-arm-linux-gnueabi/tensorpipe:/<>/obj-arm-linux-gnueabi/lib"
 ../libtensorpipe.so.0 /usr/lib/arm-linux-gnueabi/libprotobuf.so 
../../lib/libgtest_main.so.1.10.0 /usr/lib/arm-linux-gnueabi/libuv.so 
/usr/lib/arm-linux-gnueabi/libpthread.so /usr/lib/arm-linux-gnueabi/libdl.so 
/usr/lib/arm-linux-gnueabi/librt.so ../../lib/libgtest.so.1.10.0 -lpthread 
/usr/bin/ld: 
CMakeFiles/tensorpipe_test.dir/util/ringbuffer/shm_ringbuffer_test.cc.o: 
undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
/usr/bin/ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: 
DSO missing from command line
collect2: error: ld returned 1 exit status
make[3]: *** [tensorpipe/test/CMakeFiles/tensorpipe_test.dir/build.make:504: 
tensorpipe/test/tensorpipe_test] Error 1


Fix/Workaround:

--- debian/rules.old2020-10-26 16:39:12.175986248 +
+++ debian/rules2020-10-26 16:39:47.807678187 +
@@ -1,6 +1,10 @@
 #!/usr/bin/make -f
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mipsel powerpc riscv64 sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
+
 %:
dh $@ -Scmake
 
--- End Message ---
--- Begin Message ---
Source: tensorpipe
Source-Version: 0.0~git20200928.95ff931-1
Done: Mo Zhou 

We believe that the bug you reported is fixed in the latest version of
tensorpipe, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated tensorpipe 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

Bug#972778: marked as done (zbar ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 02:57:43 +
with message-id 
and subject line Bug#972778: fixed in zbar 0.23.1-2
has caused the Debian Bug report #972778,
regarding zbar ftbfs with python3.9
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.)


-- 
972778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zbar
Version: 0.23.1-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

this looks like cython3 is not run during the build (python3-defaults from
experimental).

https://people.debian.org/~ginggs/python3.9-default/zbar_0.23.1-1build1_amd64-2020-10-23T04:27:31Z.build

[...]
python/enum.c: In function ‘enumitem_print’:
python/enum.c:84:31: error: ‘PyTypeObject’ {aka ‘struct _typeobject’}
has no member named ‘tp_print’
   84 | return(self->name->ob_type->tp_print(self->name, fp, flags));
  |   ^~
python/enum.c: At top level:
python/enum.c:118:6: error: ‘PyTypeObject’ {aka ‘struct _typeobject’}
has no member named ‘tp_print’
  118 | .tp_print   = (printfunc)enumitem_print,
  |  ^~~~
python/enum.c:118:23: warning: initialization of ‘PyObject * (*)(PyObject *,
PyObject *)’ {aka ‘struct _object * (*)(struct _object *, struct _object
*)’} from ‘long int’ makes pointer from integer without a cast
[-Wint-conversion]
  118 | .tp_print   = (printfunc)enumitem_print,
  |   ^
python/enum.c:118:23: note: (near initialization for
‘zbarEnumItem_Type.tp_getattro’)
python/enum.c: In function ‘enumitem_print’:
python/enum.c:85:1: warning: control reaches end of non-void function
[-Wreturn-type]
   85 | }
  | ^
make[3]: *** [Makefile:1476: python/zbar_la-enum.lo] Error 1
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:1897: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:977: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: error: make -j16 returned exit code 2
--- End Message ---
--- Begin Message ---
Source: zbar
Source-Version: 0.23.1-2
Done: Boyuan Yang 

We believe that the bug you reported is fixed in the latest version of
zbar, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated zbar 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: Sun, 01 Nov 2020 21:12:17 -0500
Source: zbar
Architecture: source
Version: 0.23.1-2
Distribution: unstable
Urgency: high
Maintainer: Gürkan Myczko 
Changed-By: Boyuan Yang 
Closes: 972778
Changes:
 zbar (0.23.1-2) unstable; urgency=high
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
 .
   [ Boyuan Yang ]
   * Bump debhelper compat to v13.
   * debian/patches/0003: Add upstream patch for compatibility with
 python3.9. (Closes: #972778)
Checksums-Sha1:
 6ae34dc67e59bbbd88f8a1059471ec3da6de26c0 2643 zbar_0.23.1-2.dsc
 ae4340d783a52d743db0e7607e53b2656f4bb978 1019268 zbar_0.23.1.orig.tar.gz
 8e3f04e8ef79fcba51886501168b6c5eb1988c19 12096 zbar_0.23.1-2.debian.tar.xz
 42cbdf17337ff937bca9cde84cd0e82e7413da7f 22386 zbar_0.23.1-2_amd64.buildinfo
Checksums-Sha256:
 af13efa3478cbad7da333d604ec847205d5fbdabbebe85da3959e47be34d9127 2643 
zbar_0.23.1-2.dsc
 297439f8859089d2248f55ab95b2a90bba35687975365385c87364c77fdb19f3 1019268 
zbar_0.23.1.orig.tar.gz
 54683acf912435da536e2ef590393435c8b7325b9d8aa6ad8da3d83a90dac0ed 12096 
zbar_0.23.1-2.debian.tar.xz
 38cfe118fab8822ce4fe326e67b789937079d87fce0bc6c0b8d3eae2bf3ee65c 22386 
zbar_0.23.1-2_amd64.buildinfo
Files:
 fe3f6fde9f06e09c2d9afcc4c81376a9 2643 libs optional zbar_0.23.1-2.dsc
 04f1ffafd0f12473d82763931d9c7c68 1019268 libs optional zbar_0.23.1.orig.tar.gz
 c31127628aa3686ccf5ae78ed83017d9 12096 libs optional 
zbar_0.23.1-2.debian.tar.xz
 9f699777b38b393df4104479f35f2dac 22386 libs optional 
zbar_0.23.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdk

Bug#953187: marked as done (kinfocenter: should recommend or suggest samba)

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 02:47:08 +
with message-id 
and subject line Bug#953187: fixed in kinfocenter 4:5.19.5-2
has caused the Debian Bug report #953187,
regarding kinfocenter: should recommend or suggest samba
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.)


-- 
953187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kinfocenter
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The Samba status monitor dialog is blank and says
 Error run smbstatus: execve: No such file or directory

As the samba package description points out, Samba users need not have this
package installed, so at least a Suggests would help users know it's needed.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (2, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

- -- debconf-show failed

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCXmEovAAKCRByvHFIwKst
px8LAQCFR8tK/2r+srBOUe+TW07D9O4Fl5+Z9qA0eB5KkamKvwEAk9U+rImR2Abl
dDkX7rd5O71F7xYbwlrE0fAJEZzL2Aw=
=5vuv
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: kinfocenter
Source-Version: 4:5.19.5-2
Done: Norbert Preining 

We believe that the bug you reported is fixed in the latest version of
kinfocenter, 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 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated kinfocenter 
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: Mon, 02 Nov 2020 11:16:42 +0900
Source: kinfocenter
Architecture: source
Version: 4:5.19.5-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Norbert Preining 
Closes: 953187
Changes:
 kinfocenter (4:5.19.5-2) experimental; urgency=medium
 .
   [ Scarlett Moore ]
- Add missing copyright information from all files.
- Follow closely to updated KDE License policy and update license
  text and short names.
   * Update lintian-override for manual page name change.
   * Add maint options for hardening=+all.
   * Refresh upstream/metadata.
 - Remove obsolete fields already defined in d/copyright.
 - Update repository info to point to invent.kde.org repo.
 - Add new bug-database entry.
 - Update changelog to point to announcements page.
   * Remove the override for dh_install as both of these
 removals (oui and usb.ids were leftover from dh_links
 symlinks to custom one no longer used and now we are
 removing the actual items and not custom.
   * Fix "should recommend or suggest samba"
 Add samba to suggests. (Closes: #953187)
Checksums-Sha1:
 698d7156ee49a2b5fb64661edadeb1c501ecdcd0 2815 kinfocenter_5.19.5-2.dsc
 8101828b0a9ab3b15a36c590935867c9508db8fa 488 kinfocenter_5.19.5.orig.tar.xz.asc
 40c1df970ada340491b672d4e137defebb11e708 18040 
kinfocenter_5.19.5-2.debian.tar.xz
 4280dd1a9c2e8dbc01a63ad9256dacbae2b64b69 23376 
kinfocenter_5.19.5-2_source.buildinfo
Checksums-Sha256:
 9c200f2bd5e802028d4373ccb6cd9d4b74bf7e9430da9d4831c65604da64b656 2815 
kinfocenter_5.19.5-2.dsc
 31aa2fed8bec3b7bbbd54048f3591ca943c658ffa20c8103aa4cd2a30f53b9bb 488 
kinfocenter_5.19.5.orig.tar.xz.asc
 5a25609647e6ea4922a9bc8dfbf3e1837c1daf3d3aa14942ac5bdae3fcecf0ca 18040 
kinfocenter_5.19.5-2.debian.tar.xz
 bd250d251272e1a6f95186333a8bf236713317441029f4a4381636ca959bdea5 23376 
kinfocenter_5.19.5-2_source.buildinfo
Files:
 752bb5be532ba44e421a51c7ea28c24d 2815 kde optional kinfocenter_5.19.5-2.dsc
 5b8661eadc099ba1756f05c2b36ee61b 488 kde optional 
kinfocenter_5.19.5.orig.tar.xz.asc
 0ead0b032d8bb8e8b32ecfd9142c3411 18040 kde optional 
kinfocenter_5.19.5-2.debian.tar.xz
 04a8544bc4f9f14f7c97ab15545cf085 23376 kde optional 
kinfocent

Bug#973149: marked as done (kwin: FTBFS: egl_dmabuf.cpp:97:9: error: ‘EGL_TEXTURE_Y_XUXV_WL’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 01:06:06 +
with message-id 
and subject line Bug#973149: fixed in kwin 4:5.19.5-2
has caused the Debian Bug report #973149,
regarding kwin: FTBFS: egl_dmabuf.cpp:97:9: error: ‘EGL_TEXTURE_Y_XUXV_WL’ was 
not declared in this scope
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.)


-- 
973149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kwin
Version: 4:5.17.5-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fno-operator-names -fno-exceptions -Wall -Wextra 
> -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
> -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
> -Werror=return-type -Wvla -Wdate-time -Wsuggest-override -Wlogical-op 
> -Wl,--no-undefined -Wl,--fatal-warnings -Wl,--enable-new-dtags -Wl,-z,relro 
> -Wl,--as-needed -shared  -o ../../../bin/kwin_packagestructure_scripts.so 
> CMakeFiles/kwin_packagestructure_scripts.dir/kwin_packagestructure_scripts_autogen/mocs_compilation.cpp.o
>  CMakeFiles/kwin_packagestructure_scripts.dir/scripts.cpp.o  
> /usr/lib/x86_64-linux-gnu/libKF5Package.so.5.74.0 
> /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.74.0 
> /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.74.0 
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.14.2 
> /<>/platformsupport/scenes/opengl/egl_dmabuf.cpp:97:9: error: 
> ‘EGL_TEXTURE_Y_XUXV_WL’ was not declared in this scope
>97 | EGL_TEXTURE_Y_XUXV_WL,
>   | ^
> /<>/platformsupport/scenes/opengl/egl_dmabuf.cpp:114:9: error: 
> ‘EGL_TEXTURE_Y_UV_WL’ was not declared in this scope; did you mean 
> ‘GL_TEXTURE_VIEW’?
>   114 | EGL_TEXTURE_Y_UV_WL,
>   | ^~~
>   | GL_TEXTURE_VIEW
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> [ 49%] Built target kwin_packagestructure_scripts
> make  -f 
> plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/build.make
>  
> plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/depend
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
> "Unix Makefiles" /<> 
> /<>/plugins/kpackage/windowswitcher 
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/plugins/kpackage/windowswitcher 
> /<>/obj-x86_64-linux-gnu/plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/DependInfo.cmake
>  --color=
> /<>/platformsupport/scenes/opengl/egl_dmabuf.cpp:131:9: error: 
> ‘EGL_TEXTURE_Y_U_V_WL’ was not declared in this scope
>   131 | EGL_TEXTURE_Y_U_V_WL,
>   | ^~~~
> Scanning dependencies of target kwin_packagestructure_windowswitcher
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> make  -f 
> plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/build.make
>  
> plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/build
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> [ 49%] Building CXX object 
> plugins/kpackage/windowswitcher/CMakeFiles/kwin_packagestructure_windowswitcher.dir/kwin_packagestructure_windowswitcher_autogen/mocs_compilation.cpp.o
> cd /<>/obj-x86_64-linux-gnu/plugins/kpackage/windowswitcher && 
> /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CORE_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 
> -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_USE_QSTRINGBUILDER 
> -DTRANSLATION_DOMAIN=\"kwin_package_windowswitcher\" -D_GNU_SOURCE 
> -D_LARGEFILE64_SOURCE -Dkwin_packagestructure_windowswitcher_EXPORTS 
> -I/<>/obj-x86_64-linux-gnu/plugins/kpackage/windowswitcher 
> -I/<>/plugins/kpackage/windowswitcher 
> -I/<>/obj-x86_64-linux-gnu/plugins/kpackage/windowswitcher/kwin_packagestructure_windowswitcher_autogen/include
>  -I/<>/platformsupport -I/<>/tabbox 
> -I/<>/effects -I/<>/libkwineffects 
> -I/<>/obj-x86_64-linux-gnu 
> -I/<>/obj-x86_64-linux-gnu/libkwineffects 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.14.2 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui/5.14.2/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.14.2 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore/5.14.2/QtCore -isystem 
>

Bug#973499: marked as done (rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys)

[Debian Bug Tracking System]

Your message dated Mon, 02 Nov 2020 00:18:36 +
with message-id 
and subject line Bug#973499: fixed in rust-onig-sys 69.5.1-2
has caused the Debian Bug report #973499,
regarding rust-onig: autopkgtest fails on i386/armhf with new bindgen/onig-sys
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.)


-- 
973499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: rust-onig
Version: 5.0.0-3
Severity: serious

The autopkgtest for rust-onig fails with memory errors on i386 and armhf.


https://ci.debian.net/data/autopkgtest/testing/armhf/r/rust-onig/7843624/log.gz

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.p7bE9eMN2s/target/armv7-unknown-linux-gnueabihf/debug/deps/onig-38f586f8e98643ab`
 (signal: 7, SIGBUS: access to undefined memory)


https://ci.debian.net/data/autopkgtest/testing/i386/r/rust-onig/7842255/log.gz

Caused by:
  process didn't exit successfully: 
`/tmp/tmp.SP8w1ClZkZ/target/i686-unknown-linux-gnu/debug/deps/onig-cd997929b710cbf4`
 (signal: 11, SIGSEGV: invalid memory reference)


Doing some searching I notice that the onig, syntect and bat crates have all 
had new major versions released.
So I decided to test the latest version of onig on i386, unfortunately that 
failed too.

I then tried doing a test outside of the "debcargo" environment, I first tried 
using
an upstream git checkout but that failed to find it's embedded copy of libonig
so I decided to use cargo clone instead.

cargo install cargo clone
cargo clone onig
cd onig
cargo test

I have reported this upstream at 
https://github.com/rust-onig/rust-onig/issues/155
--- End Message ---
--- Begin Message ---
Source: rust-onig-sys
Source-Version: 69.5.1-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-onig-sys, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-onig-sys 
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: Sun, 01 Nov 2020 23:51:00 +
Source: rust-onig-sys
Architecture: source
Version: 69.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 973499
Changes:
 rust-onig-sys (69.5.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Package onig_sys 69.5.1 from crates.io using debcargo 2.4.3
   * Apply upstream patch to make oniguruma build correctly on 32-bit
 architectures (Closes: #973499).
Checksums-Sha1:
 01e52edf3d8258400f2eb1cfaddb03225c8caaf1 2301 rust-onig-sys_69.5.1-2.dsc
 81fd42b22d7220c131a576d44df9716547c1ee97 4576 
rust-onig-sys_69.5.1-2.debian.tar.xz
 b7cf76b9352f8891cc967aba42ee52bb09f0997c 10005 
rust-onig-sys_69.5.1-2_source.buildinfo
Checksums-Sha256:
 b0b2ce520d9654484879540412e63ef6a3108a032b3899ba7f9e40400e7797df 2301 
rust-onig-sys_69.5.1-2.dsc
 0a9cc7d6ce79272ebd997cf16acb81a417492993c9853494852d0af5690e9edc 4576 
rust-onig-sys_69.5.1-2.debian.tar.xz
 b2eb541544833dd098203631db70af0d0009dd1d3ebba757bbdb3a1f1befaa35 10005 
rust-onig-sys_69.5.1-2_source.buildinfo
Files:
 c71c10074be5e93064ee3c0c0df8bd70 2301 rust optional rust-onig-sys_69.5.1-2.dsc
 826102cb5f620a22383e4d40dfa0be62 4576 rust optional 
rust-onig-sys_69.5.1-2.debian.tar.xz
 8011ecbe3b42585df9e2f4303d1c3454 10005 rust optional 
rust-onig-sys_69.5.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl+fSmUUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsGoBAAmubOyosjhSOWnj4LjDqO414n+xYP
ZVP1bMT1Gb6IXak+Dv9lxErUE6095XSSkgEXEb+DKAIhfxip3v/aARR4U/olVD++
WId6Ch0/0H5ImwGp8aGGmsilfhP7iCcy29zC1WuFvMsa2ExwrdTSTfo207KPmYWd
bKjHLV1dJWgjey8PUrAjVc7UHFtgfZ4+CYTGET8fK35CHBG9lCeh4qvX/AzGO3xa
oC9SDrRMeBxp53U5rnjOBEwBYoWe0xmwa+ir05L6RDl29UHSE19RVW2lUhvEcYdo
hJApBAFo1UXfPViD7yW9qsFAcoEATO24yE/jO6ZeLJ1dC0c6t3sSzFhWoQAqL7wx
bNWdSjxI0NzVj5aECZl8zTJ6T9FQUCjJOFkyESgCI/GTjSgRXTqe9xBKLenvRkLM
u/j8tyBzTDkeQ7VJ26pvj11s0vg5/F7XQPytz5BPcwN3tRe2nZ4lzBLUvaXejdNJ
rdEnQrMvrWRh8BuYkLlV+6olwycfCPPPUESf1GCtceUdk8+2sCdPpxXwj

Processed: RFS: dmagnetic/0.27-1 -- Interpreter to play textadventures from Magnetic Scrolls in glorious ANSI Art

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 973497
Bug #973497 [sponsorship-requests] RFS: dmagnetic/0.27-1 -- Interpreter to play 
textadventures from Magnetic Scrolls in glorious ANSI Art
Marked Bug as done
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
973497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#972853: marked as done (Parameter -comand doesn't work)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 23:32:34 +
with message-id 
and subject line Re: Parameter -comand doesn't work
has caused the Debian Bug report #972853,
regarding Parameter -comand doesn't work
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.)


-- 
972853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tty-share
Version: 0.6.2+ds1-1

Hi,

when trying to use a different shell (or, bash with an option), I've
tried using '-command' as described in 'tty-share --help', which then fails:

daniel@daniel:~$ tty-share -comand /bin/bash
flag provided but not defined: -comand
Usage of tty-share:
  -args string
The command arguments
  -command string
The command to run (default "/bin/bash")
  -logfile string
The name of the file to log (default "-")
  -server string
tty-server address (default "go.tty-share.com:7654")
  -useTLS
Use TLS to connect to the server (default true)
  -version
Print the tty-share version
daniel@daniel:~$

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Hi Daniel,

> when trying to use a different shell (or, bash with an option), I've
> tried using '-command' as described in 'tty-share --help', which then fails:
>
> daniel@daniel:~$ tty-share -comand /bin/bash
> flag provided but not defined: -comand

I saw that the parameter used was '-comand' instead of '-command'. Please try
again this way:

tty-share -command /bin/bash

For me it's normal, see:
root@77cefca5e5c3:/# tty-share -command /bin/bash
Web Terminal:
https://go.tty-share.com/s/R0HUJgV-hArzQ17VxqJYFyHJAkkO0CxJ8HwAIgWScrI=


Thanks for opening the bug!
I'll close it, feel free to reopen it.

Regards,
-- 
Francisco Vilmar Cardoso Ruviaro 
4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00--- End Message ---

Bug#973520: marked as done (openstack-pkg-tools: uses python2)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 23:19:04 +
with message-id 
and subject line Bug#973520: fixed in openstack-pkg-tools 115
has caused the Debian Bug report #973520,
regarding openstack-pkg-tools: uses python2
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.)


-- 
973520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openstack-pkg-tools
Version: 114
Severity: serious
tags: patch

Hello,


diff -Nru openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot 
openstack-pkg-tools-113ubuntu1/build-tools/pkgos-generate-snapshot
--- openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot 2019-11-20 
10:25:50.0 +
+++ openstack-pkg-tools-113ubuntu1/build-tools/pkgos-generate-snapshot  
2020-07-30 23:34:17.0 +
@@ -3,7 +3,7 @@
 set -e
 
 rm -f dist/*
-python setup.py sdist
+python3 setup.py sdist
 package=$(cd dist; ls -1 *.tar.gz)
 version=$(echo $package | sed -e "s/\.tar\.gz//" -e "s/.*-//g")
 deb_version=$(echo $version | sed -e "s/\.0a/~a/" -e "s/\.0b/~b/" -e 
"s/\.dev/~dev/")


Please apply to let python2 go away

Patch provided by James Page 

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: openstack-pkg-tools
Source-Version: 115
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
openstack-pkg-tools, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated openstack-pkg-tools 
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: Sun, 01 Nov 2020 20:32:43 +0100
Source: openstack-pkg-tools
Architecture: source
Version: 115
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 973520
Changes:
 openstack-pkg-tools (115) unstable; urgency=medium
 .
   [ James Page ]
   * build-tools/pkgos-generate-snapshot: Use python3 for generation
 of snapshots. (Closes: #973520)
 .
   [ Gianfranco Costamagna ]
   * Commit Ubuntu delta to Debian
Checksums-Sha1:
 4cf5eebc4700340dbac69fa1b90310b833297391 1723 openstack-pkg-tools_115.dsc
 9ac6cf952e8b47dae26bc790cf2b90f601e3fda2 91652 openstack-pkg-tools_115.tar.xz
 56c7115b4605144b772a071951d48aa906faa91e 5860 
openstack-pkg-tools_115_amd64.buildinfo
Checksums-Sha256:
 9e173e6a44852ef61a5b7aa4b586ce68b7007dbde449330607fb0e11ea62961a 1723 
openstack-pkg-tools_115.dsc
 c7ac64e45c8b5d3e16dc89828841913d22bd41c66932dfc4454eb19304a089cc 91652 
openstack-pkg-tools_115.tar.xz
 94d643419aec1d3e0e301ef50380b7f542584111913adfcae5fe19cc63428d6e 5860 
openstack-pkg-tools_115_amd64.buildinfo
Files:
 3fb7e335447fbe3384581a4e31d73cc4 1723 devel optional 
openstack-pkg-tools_115.dsc
 193b735a06dc166061def68dff0aef5b 91652 devel optional 
openstack-pkg-tools_115.tar.xz
 22b117486a955bd271e423ba6b66e8db 5860 devel optional 
openstack-pkg-tools_115_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl+fPA0ACgkQ1BatFaxr
Q/5pWQ//e7qglnxmRFPPRvjr5qyaAxcSMAgcIFxg51e2Hfs6t6pYusHtTAD07i/z
eyOObnmXH8tsUGqUWYt3RvTv2Ixrtlfj7k/bm9R4qfPAUzSuT/vm80J0TDP+dwGa
4P2kpctjtHu0FIgdiG5o+f9kQPUYhPdcKmEIublGcsIoCpX9PTVs1a1FirMChsZZ
za0zvtUw8U2UX4gHhd/5Vc7OponmSwoua7tKD0s5ZuRmnEXo1MPYG6txN98XUhNJ
m2/loqPTwt0WYOFTdrvwZ9Out192RLgnYnBBLboBahgZtKIBqPsVw97Obtzfnjk9
j3BNARIgCWoMWFg9oRyeqw7O6TZy13AUE3LTsWgBulJvZ/x+M9FXCwLX3h+VqsXT
AlMG0jXwWAJQL9KrD9fi+y4irnc3xxHZsB7r8Oj3ycpiZmUQd89tkEWfpOIiBpqV
u7hQUL4sJpMG2CctxqP5OkU4g3BM230qN5Jt2te3aaqLP5HFRufdZiblEdL0e0cr
vrqRq5jBiZYKf4SjaIhVjtPU7DND6wWkkLmDCtjV6LS+5buuvMFf5juNNgJH9BjG
h8w8PnFFW38fFcXcJ37dWWkC4o7JTZbE58P2rfqTJAKOylownRtzlGHC75c4YTQE
yZO74hDKgNX19gSmKgKAbjgSwy+Lbg+nzdRRfIfRvn6IBbYdvhw=
=QYXY
-END PGP SIGNATURE End Message ---

Bug#969704: marked as done (mes: please upgrade to guile-3.0 soon, if feasible)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 22:48:56 +
with message-id 
and subject line Bug#969704: fixed in mes 0.22-5
has caused the Debian Bug report #969704,
regarding mes: please upgrade to guile-3.0 soon, if feasible
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.)


-- 
969704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mes
Severity: wishlist

Please migrate to guile-3.0 as soon as it's feasible. If we can, I'd
like to have the option to drop guile-2.2 from bullseye, so that we
won't have to maintain two versions throughout that release.

Thanks 
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Source: mes
Source-Version: 0.22-5
Done: Vagrant Cascadian 

We believe that the bug you reported is fixed in the latest version of
mes, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated mes 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: Sun, 01 Nov 2020 13:54:36 -0800
Source: mes
Architecture: source
Version: 0.22-5
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 969704
Changes:
 mes (0.22-5) unstable; urgency=medium
 .
   * debian/patches: Support for guile 3.0 from upstream git.
   * debian/control: Switch to guile 3.0 (Closes: #969704).
Checksums-Sha1:
 15107c48f5869e171c65fb752bf905fb1b2b65d3 1574 mes_0.22-5.dsc
 57e4806baeb9d9078d3c4d142617003d78f172e2 12924 mes_0.22-5.debian.tar.xz
 4ea5666b0681ba8ef88a3f704db2eff9014f4f06 7622 mes_0.22-5_i386.buildinfo
Checksums-Sha256:
 fbcc6fe4f44ee1dc250f10e3841dcfab6ea44e2bb547e39cb24297fe5f4e55b3 1574 
mes_0.22-5.dsc
 256564905b8e889b80bd5baf25b687386f3cce9be238d51ec202eba5ecf9f1b1 12924 
mes_0.22-5.debian.tar.xz
 9497c178644398f344c30d6c9286d2507c4b12f783c375bf1afb25350f17f5be 7622 
mes_0.22-5_i386.buildinfo
Files:
 285d31f7f8a0deffb63c450598ab6837 1574 devel optional mes_0.22-5.dsc
 0365d5ec74f8fb309799376557477a89 12924 devel optional mes_0.22-5.debian.tar.xz
 28b64aed9a6fb458edbbf240e8e4d0b0 7622 devel optional mes_0.22-5_i386.buildinfo

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCX585ShMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqgOYA/2gSK6k8UwoOb1GgJhvbU6m/90hcsWQm
mhz75Kky+I7kAP0ePN7a8+z5iWXIyaU6D/6Zl1LtkLqKM6+rsG4Aq4uKDg==
=9Brk
-END PGP SIGNATURE End Message ---

Bug#952464: marked as done (clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 22:00:09 +
with message-id 
and subject line Bug#952464: fixed in clazy 1.7-4
has caused the Debian Bug report #952464,
regarding clazy: flaky arm64 autopkgtest: unable to execute command: 
Segmentation fault
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.)


-- 
952464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clazy
Version: 1.6-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

With a recent upload of gcc-10 to unstable, the autopkgtest of clazy
failed on arm64 in testing when that autopkgtest was run with the binary
packages of gcc-10 from unstable. I looked into the history of your
autopkgtest and it fails very often.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests. Please either fix the test to be more robust, or or use the
"flaky" restriction for the offending test until a solution has been found.

I copied the output at the bottom of this report. All the failing tests
that I inspected look like it, albeit the test that fails differs
between runs.

I'll have the migration software ignore the results of your autopkgtest
on arm64 until this bug is fixed.

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/c/clazy/4369731/log.gz

Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-Xclang -plugin-arg-clazy -Xclang qt4-compat  -c  -Xclang
-plugin-arg-clazy -Xclang old-style-connect clazy/qt4compat2.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang old-style-connect -Xclang
-plugin-arg-clazy -Xclang export-fixes clazy/onlyQt1.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-Xclang -plugin-arg-clazy -Xclang only-qt  -c  -Xclang -plugin-arg-clazy
-Xclang old-style-connect clazy/onlyQt2.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c -Wno-deprecated-declarations -Xclang -plugin-arg-clazy -Xclang
raw-environment-function raw-environment-function/main.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang inefficient-qlist
inefficient-qlist/main.cpp
Qt version: 51205
Qt headers: /usr/include/aarch64-linux-gnu/qt5
clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin -Xclang
clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang qenums qenums/main.cpp
Running: clang -Xclang -load -Xclang ClazyPlugin.so -Xclang -add-plugin
-Xclang clazy  -Wno-unused-value -Qunused-arguments -std=c++14 -isystem
/usr/include/aarch64-linux-gnu/qt5 -fPIC -L /usr/lib/aarch64-linux-gnu
-c  -Xclang -plugin-arg-clazy -Xclang rule-of-three
rule-of-three/bug403193.cpp
output_file=rule-of-three/bug403193.cpp.out
[FAIL] rule-of-three (Failed to build test. Check
rule-of-three/bug403193.cpp.out for details)
---
Contents of rule-of-three/bug403193.cpp.out:
Stack dump:
0.  Program arguments: /usr/lib/llvm-8/bin/clang -cc1 -triple
aarch64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name
bug403193.cpp -mreloca

Bug#971589: marked as done (clazy's test suite uses the default clang, while the package uses the versioned one)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 22:00:09 +
with message-id 
and subject line Bug#971589: fixed in clazy 1.7-4
has caused the Debian Bug report #971589,
regarding clazy's test suite uses the default clang, while the package uses the 
versioned one
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.)


-- 
971589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:clazy
Version: 1.7-3
Severity: serious
Tags: sid bullseye

This is seen when updating llvm-defaults to point to 11, and then running the
autopkg test.  The test tries to run with the updated default clang (11), but
the package is still built using the previous 10 version.  The package itself
uses a versioned clang for building, and also gets this dependency encoded in
the package.  The plugins are not compatible across versions, so the test should
always use the version that the package was built for.
--- End Message ---
--- Begin Message ---
Source: clazy
Source-Version: 1.7-4
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
clazy, 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.
Pino Toscano  (supplier of updated clazy 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: Sun, 01 Nov 2020 19:06:17 +0100
Source: clazy
Binary: clazy clazy-dbgsym clazy-tests
Architecture: source amd64
Version: 1.7-4
Distribution: experimental
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 clazy  - Clang plugin for additional warnings
 clazy-tests - test files for Clazy
Closes: 952464 971589
Changes:
 clazy (1.7-4) experimental; urgency=medium
 .
   * Add a new package clazy-tests, mostly for autopkgtest purposes:
 - use --destdir=debian/clazy to install everything directly in clazy
 - make clazy-tests depend on the exact clazy version
 - make clazy-tests depend on the package (clang-tools-N) that provides
   the default version of clang-apply-replacements
   * Ship a shell file /usr/share/clazy/debian-$(DPKG_ARCHITECTURE).sh in
 clazy-tests with the paths of clang and clang-apply-replacements.
   * Adapt the run-tests autopkgtest to clazy-tests: (Closes: #952464, #971589)
 - replace the clang, and clang-tools dependencies with clazy-tests
 - source the shell configuration file provided by clazy-tests
 - export the right environment variables for clang, and
   clang-apply-replacements, so the upstream test script can use them
   * Bump the debhelper compatibility to 13:
 - switch the debhelper-compat build dependency to 13
   * Minimize the upstream GPG signing key.
   * Set field Upstream-Contact in debian/copyright.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
   * Update references to the upstream Git repository.
Checksums-Sha1:
 95b5d394cd11fbe576fd25fda1fae3c5258a171d 2469 clazy_1.7-4.dsc
 0c2a9df52ff1b88e606ea3fb27182dd7050c9e4f 18748 clazy_1.7-4.debian.tar.xz
 028a87fe989eb2b60b559f63dff7b56d6b1f9fca 94685860 clazy-dbgsym_1.7-4_amd64.deb
 0a8ed0f1ce622232b2e34dc2b07e0ecebffed96c 14836 clazy-tests_1.7-4_amd64.deb
 29bae9c4b72823b5d957f0e9b9806d205f06634a 12168 clazy_1.7-4_amd64.buildinfo
 457b55e9a75e73c6e1fe7c42fbf7b2193ab9ba0e 613208 clazy_1.7-4_amd64.deb
Checksums-Sha256:
 b90c9e19d2efbcd44119fe2675f96ac6d13d53c0191196a40ca102691bb621c4 2469 
clazy_1.7-4.dsc
 d88b63e9f0189bef4319b0117afc591f0f7c8688fcd1b20482246f5f4e35d814 18748 
clazy_1.7-4.debian.tar.xz
 59591e1904bfd4fc6cacb233980cfecb7c6bc8980662b451ba13ef0cded8b872 94685860 
clazy-dbgsym_1.7-4_amd64.deb
 4b2dc869ef2fd5ff464d1ec8d1a2321280c74d7a8ba90cadcb1161561b39d4c6 14836 
clazy-tests_1.7-4_amd64.deb
 18aeef7f8f3c6f8bc03a844e14b655f061010559a9d984bafdb64b1a6d1f4247 12168 
clazy_1.7-4_amd64.buildinfo
 f2f590be0b0070971fec9dd0ab6891659651c704fb59d286aea07cbf1e4b7a46 613208 
clazy_1.7-4_amd64.deb
Files:
 4389d683db75fd315921a8ce0fadd509 2469 devel optional clazy

Bug#973510: marked as done (ITP: nim-hts -- wrapper for hts C library)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 22:00:09 +
with message-id 
and subject line Bug#973510: fixed in nim-hts 0.3.12+ds-1
has caused the Debian Bug report #973510,
regarding ITP: nim-hts -- wrapper for hts C library
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.)


-- 
973510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist

Subject: ITP: nim-hts -- wrapper for hts C library
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: nim-hts
  Version : 0.3.12
  Upstream Author : Brent Pedersen
* URL : https://github.com/brentp/hts-nim
* License : Expat
  Programming Lang: C
  Description : wrapper for hts C library
 The hts library is well accepted for the handling of millions of
 DNA sequences from what once was the high-throughput sequencing machines
 in biological research and medical diagnostics/therapy control.

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/nim-hts
--- End Message ---
--- Begin Message ---
Source: nim-hts
Source-Version: 0.3.12+ds-1
Done: Steffen Moeller 

We believe that the bug you reported is fixed in the latest version of
nim-hts, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated nim-hts 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, 31 Oct 2020 22:32:09 +0100
Source: nim-hts
Binary: nim-hts-dev nim-hts-examples
Architecture: source all
Version: 0.3.12+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Steffen Moeller 
Description:
 nim-hts-dev - wrapper for hts C library
 nim-hts-examples - examples for nim-hts: wrapper for hts C library
Closes: 973510
Changes:
 nim-hts (0.3.12+ds-1) unstable; urgency=medium
 .
   * Initial release (Closes: #973510)
Checksums-Sha1:
 5046c509348426a52a4de0834359ca39f068ce42 2224 nim-hts_0.3.12+ds-1.dsc
 8e3a329c39b62d882d471dea80eca941e4559216 524460 nim-hts_0.3.12+ds.orig.tar.xz
 b973b85cf0009a5bca2f6d4d1d330a4899399335 340360 
nim-hts_0.3.12+ds-1.debian.tar.xz
 8ef7cd47cbcb980e233944ce638f9172111dbeb4 34880 nim-hts-dev_0.3.12+ds-1_all.deb
 48c7cb6da3845f2d36017d2bf13008f78bcf4a5a 1171224 
nim-hts-examples_0.3.12+ds-1_all.deb
 27a9a4df410747c3ed677b9949d23bdf662a1ff8 7325 
nim-hts_0.3.12+ds-1_amd64.buildinfo
Checksums-Sha256:
 aedf1802ea6b491d50fb37a26acc5f0c0cc9da9ea8e8ce4a71c2fa08149f04a9 2224 
nim-hts_0.3.12+ds-1.dsc
 40321c8b1c94ed2929628e641cfed9f4602e39e1f467a8f0772808b880e97443 524460 
nim-hts_0.3.12+ds.orig.tar.xz
 e262f7854c75d8fead1dec3b7acf16235a5af4a7124ac2b5197f257441adf650 340360 
nim-hts_0.3.12+ds-1.debian.tar.xz
 b7b6d518edf698bac1bdf472d6c50880af886a319e5e86bda17e26dde9e0cc54 34880 
nim-hts-dev_0.3.12+ds-1_all.deb
 bf91484bdd3254716f99d18e3e6b47eb60234a4412dbc7997e81d260dba7554c 1171224 
nim-hts-examples_0.3.12+ds-1_all.deb
 bb3960f5db8ba2baa3315fbdded17cedbe64381ba71084c13e37ad9f48d662b6 7325 
nim-hts_0.3.12+ds-1_amd64.buildinfo
Files:
 fc83c8096d9d2736c4350c151ff49524 2224 libs optional nim-hts_0.3.12+ds-1.dsc
 60e64d67d80ef77caeac1a50fb6e 524460 libs optional 
nim-hts_0.3.12+ds.orig.tar.xz
 39124b44c6f5845b23c1eb82e42351ed 340360 libs optional 
nim-hts_0.3.12+ds-1.debian.tar.xz
 baea250855625d478ab0369fd36931f1 34880 libs optional 
nim-hts-dev_0.3.12+ds-1_all.deb
 fa5335bca4b6183ccb126a836c30b1ef 1171224 libs optional 
nim-hts-examples_0.3.12+ds-1_all.deb
 c7824d7c8018f4ccdc1aa6bb9e9888ee 7325 libs optional 
nim-hts_0.3.12+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAxFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl+fFDcTHG1vZWxsZXJA
ZGViaWFuLm9yZwAKCRAv2L7awCDu0VeyD/YvlOmXD4+MbrwdERqvAGRNXoDhPnBf
MXUSZlnwno3pouj0gqAt8H/GdbHX7broXAqoS28pWewm5GQNV1Qd201nVXi8xTxz
r+ZGTb6qyzr1j8jCqEk2sw1go2VmWoF9c/48CwBUdStd8UyR39PTkAahaBewE/yk
VOckqu+MQm+TyuWEI3nyVVb7CQQP3nPo1Sc2P2r6ahgbc0S4SXEkr4nxHuJkfV8l
9+mKEjo9qPLzWT81PMZdM3zb8RxBBF6QB4E4DqnpU3xWg9YCU7YL5JQGkdjNa4SF
L/ze+yW/UBKdWq3MkSQ

Bug#947017: marked as done (ITP: org-drill -- emacs self-learning mode with spaced repetition)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 22:00:09 +
with message-id 
and subject line Bug#947017: fixed in org-drill 2.7.0+20200412+dfsg1-1
has caused the Debian Bug report #947017,
regarding ITP: org-drill -- emacs self-learning mode with spaced repetition
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.)


-- 
947017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
X-Debbugs-Cc: tho...@koch.ro, debian-emac...@lists.debian.org, Phillip Lord 


org-drill was bundled as contrib in org-mode but needed an update and a new 
maintainer.
It has now a new maintainer
https://lists.gnu.org/archive/html/emacs-orgmode/2019-06/msg00191.html
is on melpa
https://melpa.org/#/org-drill
and has been removed from org-mode.
https://code.orgmode.org/bzg/org-mode/commit/2c8e8b4a186473729b983318c2befc1732127165

(BTW, once this is done: https://melpa.org/#/org-drill-table )

* Package name: org-drill
  Version : 2.7
  Upstream Author : Paul Sexton , Phillip Lord 

* URL : https://gitlab.com/phillord/org-drill
* License : GPL-3+
  Programming Lang: elisp
  Description : emacs self-learning mode with spaced repetition

Org-Drill is an extension for Emacs' org-mode. Org-Drill uses a spaced
repetition algorithm to conduct interactive “drill sessions”, using org files
as sources of facts to be memorised. The material to be remembered is
presented in random order. The self-rated recall of each item is used to
schedule the item for later revision.
--- End Message ---
--- Begin Message ---
Source: org-drill
Source-Version: 2.7.0+20200412+dfsg1-1
Done: Thomas Koch 

We believe that the bug you reported is fixed in the latest version of
org-drill, 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 947...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Koch  (supplier of updated org-drill 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: Sun, 1 Nov 2020 20:09:06 +0100
Source: org-drill
Binary: elpa-org-drill
Architecture: source all
Version: 2.7.0+20200412+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Thomas Koch 
Description:
 elpa-org-drill - emacs org-mode contrib for self-testing using spaced 
repetition
Closes: 947017
Changes:
 org-drill (2.7.0+20200412+dfsg1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #947017)
Checksums-Sha1:
 0052528bf7e284b56db7ad526f27085ed931c120 2097 
org-drill_2.7.0+20200412+dfsg1-1.dsc
 2b1528a560625e7774e6499032bd4d4e97f33993 72096 
org-drill_2.7.0+20200412+dfsg1.orig.tar.gz
 a236660398412a2fd09d97fabd20cdc1c1a96a23 1768 
org-drill_2.7.0+20200412+dfsg1-1.debian.tar.xz
 847b4018972de428cddc692c5a7452e1a8bd2c5e 62036 
elpa-org-drill_2.7.0+20200412+dfsg1-1_all.deb
 f631c907c07143ba4eb579a655248c98d357497e 8195 
org-drill_2.7.0+20200412+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 6b826a2879177bf8bf501b0ee0e1cfd9b68ebaa65531f0cf02c33eed3a82ceb3 2097 
org-drill_2.7.0+20200412+dfsg1-1.dsc
 2269b8535a89bab46ded62e554bb178cb94d6967ec9ea7b0d20df36dadf7a635 72096 
org-drill_2.7.0+20200412+dfsg1.orig.tar.gz
 7489f6a1696d546d1c16dc766bfe58bda55af5210b00e64fae20420a19e056f6 1768 
org-drill_2.7.0+20200412+dfsg1-1.debian.tar.xz
 4f34b4eeaca4f7db9c2c4485953a3f5ea14f5a0dd4bbc01052cbc0a491794614 62036 
elpa-org-drill_2.7.0+20200412+dfsg1-1_all.deb
 730b80afe421f1da772adb5fca83c7622c6e5c940fc67888e446bf8284ad6fb1 8195 
org-drill_2.7.0+20200412+dfsg1-1_amd64.buildinfo
Files:
 7a6b02e5842b11d358d6043786d5d69e 2097 lisp optional 
org-drill_2.7.0+20200412+dfsg1-1.dsc
 66828a0062d666fe8452f563f65a438e 72096 lisp optional 
org-drill_2.7.0+20200412+dfsg1.orig.tar.gz
 10e984d3510ba85dc4c1d945edda9f11 1768 lisp optional 
org-drill_2.7.0+20200412+dfsg1-1.debian.tar.xz
 9e3e7a288213e3889452afca2ff7157d 62036 lisp optional 
elpa-org-drill_2.7.0+20200412+dfsg1-1_all.deb
 2ef62752960a10a261b50ef401f09071 8195 lisp optional 
org-drill_2.7.0+20200412+dfsg1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdgQCBVl/ppbxMTvKB/xIkQQrploFAl+fIbQACgkQB/xIkQQr

Bug#954960: marked as done (steam: new steam update crashes with fatal error: could not load steamui.so)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:35:02 +
with message-id 
and subject line Bug#954960: fixed in glib2.0 2.66.2-1+exp1
has caused the Debian Bug report #954960,
regarding steam: new steam update crashes with fatal error: could not load 
steamui.so
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.)


-- 
954960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: steam
Version: 1.0.0.61-2
Severity: important

Dear Maintainer,

The latest Steam client upgrade fails to run, crashing with a dialog box saying:

   Fatal Error: Failed to load steamui.so

There's no other details unfortunately.

Best,
Ximin

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable'), (300, 'unstable'), (100, 'experimental'), 
(1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages steam depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.30-2
ii  libgl1-mesa-dri19.3.3-1
ii  libgl1-mesa-glx19.3.3-1
ii  libgpg-error0  1.37-1
ii  libstdc++6 10-20200312-2
ii  libudev1   244.3-1
ii  libx11-6   2:1.6.9-2
ii  libxcb-dri3-0  1.13.1-5
ii  libxinerama1   2:1.1.4-2
ii  xz-utils   5.2.4-1+b1

Versions of packages steam recommends:
ii  ca-certificates   20190110
ii  fontconfig2.13.1-2+b1
ii  fonts-liberation  1:1.07.4-11
ii  gnome-terminal [x-terminal-emulator]  3.36.0.1-1
ii  libxss1   1:1.2.3-1
ii  mesa-vulkan-drivers   19.3.3-1
ii  steam-devices 1.0.0.61-2
ii  xfce4-terminal [x-terminal-emulator]  0.8.9.1-1
ii  xterm [x-terminal-emulator]   353-1

Versions of packages steam suggests:
pn  nvidia-driver-libs-i386  
ii  nvidia-vulkan-icd440.64-1

Versions of packages steam is related to:
ii  libc6   2.30-2
ii  libgl1  1.3.1-1
ii  libgl1-mesa-dri 19.3.3-1
ii  libglx-mesa0 [libglx-vendor]19.3.3-1
ii  libglx-nvidia0 [libglx-vendor]  440.64-1
ii  libxcb-dri3-0   1.13.1-5
ii  nvidia-driver   440.64-1
ii  nvidia-driver-libs  440.64-1
pn  nvidia-driver-libs-i386 

-- debconf information excluded

-- debsums errors found:
debsums: package steam is not installed
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.2-1+exp1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Sun, 01 Nov 2020 13:11:00 +
Source: glib2.0
Architecture: source
Version: 2.66.2-1+exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 896019 954960 955331
Changes:
 glib2.0 (2.66.2-1+exp1) experimental; urgency=medium
 .
   * Branch for experimental
   * postinst: Clean up outdated copies of GLib to avoid infrequent
 upgrade issues on non-merged-/usr systems
 (Closes: #896019, #954960, #955331)
Checksums-Sha1:
 79ef1a37bb0292a18c0dcc568d3c34e352c5ef84 3384 glib2.0_2.66.2-1+exp1.dsc
 bda2ed9180c25cd55640b6dd874d16d3f6151ed2 103764 
glib2.0_2.66.2-1+exp1.debian.tar.xz
 0c6119303c75d45e5f5fee47f376a751e4fd1589 7923 
glib2.0_2.66.2-1+exp1_source.buildinfo
Checksums-Sha256:
 b865e8454a0a1e98ff078233d3794e430b16c8ea21d68fc9e9abb34bdb4e52df 3384 
glib2.0_2.66.2-1+exp1.dsc
 7b5fa0e4d7cdf2231

Bug#896019: marked as done (libglib2.0-0: undefined symbols if a non-dpkg-managed libglib-2.0.so.0.* is present in /lib/MULTIARCH)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:35:02 +
with message-id 
and subject line Bug#896019: fixed in glib2.0 2.66.2-1+exp1
has caused the Debian Bug report #896019,
regarding libglib2.0-0: undefined symbols if a non-dpkg-managed 
libglib-2.0.so.0.* is present in /lib/MULTIARCH
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.)


-- 
896019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.56.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I recently updated a number of packages on my Debian/testing laptop, via 
aptitude
and included in that upgrade to satisfy dependencies was libglib-2.0-0.

Since installing, many many programs on my system refuse to start. Trying
to run nmcli, for example, returns:

nmcli: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0: 
undefined symbol: g_date_copy

I also see like errors trying to run lightdm, urxvt, vi.
This file appears to be a symlink, pointing at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5600.1.

There is a .4200.0 in that directory. I tried symlinking to that, but got a 
different set of undefined
symbol errors keeping me from running things- g_option_group_unref.

This does appear to gravely reduce the functionality of my workstation.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (250, 'unstable'), (600, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/zsh

Versions of packages libglib2.0-0 depends on:
ii  libc62.27-3
ii  libffi6  3.2.1-4
ii  libmount12.30.2-0.1
ii  libpcre3 8.39-9
ii  libselinux1  2.6-3+b1
ii  zlib1g   2.8.dfsg-2+b1

Versions of packages libglib2.0-0 recommends:
ii  libglib2.0-data   2.56.1-2
ii  shared-mime-info  1.7-1
ii  xdg-user-dirs 0.15-2

libglib2.0-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glib2.0
Source-Version: 2.66.2-1+exp1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
glib2.0, 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 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated glib2.0 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: Sun, 01 Nov 2020 13:11:00 +
Source: glib2.0
Architecture: source
Version: 2.66.2-1+exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 896019 954960 955331
Changes:
 glib2.0 (2.66.2-1+exp1) experimental; urgency=medium
 .
   * Branch for experimental
   * postinst: Clean up outdated copies of GLib to avoid infrequent
 upgrade issues on non-merged-/usr systems
 (Closes: #896019, #954960, #955331)
Checksums-Sha1:
 79ef1a37bb0292a18c0dcc568d3c34e352c5ef84 3384 glib2.0_2.66.2-1+exp1.dsc
 bda2ed9180c25cd55640b6dd874d16d3f6151ed2 103764 
glib2.0_2.66.2-1+exp1.debian.tar.xz
 0c6119303c75d45e5f5fee47f376a751e4fd1589 7923 
glib2.0_2.66.2-1+exp1_source.buildinfo
Checksums-Sha256:
 b865e8454a0a1e98ff078233d3794e430b16c8ea21d68fc9e9abb34bdb4e52df 3384 
glib2.0_2.66.2-1+exp1.dsc
 7b5fa0e4d7cdf22315fe15f2c2d103e7afd46f62a163cee0daf36449b859cd3e 103764 
glib2.0_2.66.2-1+exp1.debian.tar.xz
 9444274a99f2e9464b49f2e9822e6b3fe86416e66eb916cdc8938e7be6954785 7923 
glib2.0_2.66.2-1+exp1_source.buildinfo
Files:
 c53030901a2bea71faf85919c7e09e87 3384 libs optional glib2.0_2.66.2-1+exp1.dsc
 c3648c80b587267330a8b603ccad5ba7 103764 libs optional 
glib2.0_2.66.2-1+exp1.debian.tar.xz
 ba27cc3ef035e4b86d4730e53469ad75 7923 libs optional 
glib2.0_2.66.2-1+exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAl+fJEwACgkQ4FrhR4+B
TE9fcBAAncbmKeCdf0dwRJwQPZk3RKxUQBVgjGrlzsxQL6pxC5ceDlhe1gQHJGPj
Iedpx30ZJtXFvz2zOI5USnF1Ujdo8EYxxBxYXjGY+UTCKvMfXvL/4YPck43YW+yy
uF9ASUeT8y5HpmOmh48XNo7sskGdeFQp3O3TM9eWF+V2ZkgceYOmBp6Wh3PUZwxo
nSNL6QtbYQc3bBt5pMJz4p5THvgjUOm7uskQb/z1yoa

Bug#955331: marked as done (After upgrading to buster, libgobject-2.0.so.0 give error "undefined symbol: g_variant_dict_ref")

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:35:02 +
with message-id 
and subject line Bug#955331: fixed in glib2.0 2.66.2-1+exp1
has caused the Debian Bug report #955331,
regarding After upgrading to buster, libgobject-2.0.so.0 give error "undefined 
symbol: g_variant_dict_ref"
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.)


-- 
955331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0
Version: 2.58.3-2+deb10u2

I upgraded my system (a headless microserver) to buster today using the 
standard commands (apt-get upgrade and apt-get dist-upgrade) and did not notice 
any errors causing it to fail.

However my minidlna server (the latest packaged version, 1.2.1+dfsg-1+b1) does 
not start giving the following error:

$ sudo /etc/init.d/minidlna start
/usr/sbin/minidlnad: symbol lookup error: 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0: undefined symbol: 
g_variant_dict_ref


The same error is given by trying to run ffmpeg.  Looking back, the error did 
appear twice when upgrading the system:

Setting up libgtk2.0-0:i386 (2.24.32-3) ...
/usr/lib/i386-linux-gnu/libgtk2.0-0/gtk-query-immodules-2.0: symbol lookup 
error: /usr/lib/i386-linux-gnu/libgobject-2.0.so.0: undefined symbol: 
g_variant_dict_ref

And:

Processing triggers for libgdk-pixbuf2.0-0:i386 (2.38.1+dfsg-1) ...
/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: symbol lookup 
error: /usr/lib/i386-linux-gnu/libgobject-2.0.so.0: undefined symbol: 
g_variant_dict_ref


Searching for advice I found bug reports  (894763, 896019) related to a 
different symbol error for the same library, with the discussion based on older 
versions not being deleted.  Although the symlink was to the newer file, there 
was an older version (libgobject-2.0.so.0.3600.4) so I deleted this.  As that 
did not make any difference I moved the file and symlinks and reinstalled the 
libglib2.0-0 package.  However this did not fix the problem but also showed the 
error.

$ sudo apt-get --reinstall install libglib2.0-0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1,334 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 99760 files and directories currently installed.)
Preparing to unpack .../libglib2.0-0_2.58.3-2+deb10u2_i386.deb ...
Unpacking libglib2.0-0:i386 (2.58.3-2+deb10u2) over (2.58.3-2+deb10u2) ...
Setting up libglib2.0-0:i386 (2.58.3-2+deb10u2) ...
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas: symbol lookup error: 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0: undefined symbol: 
g_variant_dict_ref
Processing triggers for libc-bin (2.28-10) …

The files that were reinstalled matched the ones I moved away:

$ ls -il /usr/lib/i386-linux-gnu/libgobj*
668723 -rw-r--r-- 1 root root 585560 Nov  6 08:29 
/usr/lib/i386-linux-gnu/libgobject-2.0.a
673372 lrwxrwxrwx 1 root root 19 Nov  6 08:29 
/usr/lib/i386-linux-gnu/libgobject-2.0.so -> libgobject-2.0.so.0
672715 lrwxrwxrwx 1 root root 26 Nov  6 08:29 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0 -> libgobject-2.0.so.0.5800.3
669037 -rw-r--r-- 1 root root 406900 Nov  6 08:29 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0.5800.3

Using find there are no other files matching the name "libgobject*" in other 
directories to conflict.  And here is a dpkg search output, as it was requested 
on one of the other bug reports:

$ dpkg -S libglib-2.0.so
libglib2.0-dev:i386: 
/usr/share/gdb/auto-load/usr/lib/i386-linux-gnu/libglib-2.0.so.0.5800.3-gdb.py
libglib2.0-dev:i386: /usr/lib/i386-linux-gnu/libglib-2.0.so
libglib2.0-0:i386: /usr/lib/i386-linux-gnu/libglib-2.0.so.0.5800.3
libglib2.0-0:i386: /usr/lib/i386-linux-gnu/libglib-2.0.so.0


My system details are

Kernel: Linux kierkegaard 4.19.0-8-686-pae #1 SMP Debian 4.19.98-1 (2020-01-26) 
i686 GNU/Linux
Share C Library: Version: 2.28-10
Hardware:

Architecture:i686
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   48 bits physical, 48 bits virtual
CPU(s):  2
On-line CPU(s) list: 0,1
Thread(s) per core:  1
Core(s) per socket:  2
Socket(s):   1
Vendor ID:   AuthenticAMD
CPU family:  16
Model:   6
Model name:  AMD Turion(tm) II Neo N54L Dual-Core Processor
Stepping:3
CPU MHz: 1300.000
CPU max MHz: 2200.
CPU min MHz: 800.
BogoMIPS: 

Bug#969702: marked as done (nyacc: please upgrade to guile-3.0 soon, if feasible)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:28:04 +
with message-id 
and subject line Bug#969702: fixed in nyacc 1.00.2-3
has caused the Debian Bug report #969702,
regarding nyacc: please upgrade to guile-3.0 soon, if feasible
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.)


-- 
969702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nyacc
Severity: wishlist

Please migrate to guile-3.0 as soon as it's feasible. If we can, I'd
like to have the option to drop guile-2.2 from bullseye, so that we
won't have to maintain two versions throughout that release.

Thanks 
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
--- Begin Message ---
Source: nyacc
Source-Version: 1.00.2-3
Done: Vagrant Cascadian 

We believe that the bug you reported is fixed in the latest version of
nyacc, 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 969...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian  (supplier of updated nyacc 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: Sun, 01 Nov 2020 13:07:11 -0800
Source: nyacc
Architecture: source
Version: 1.00.2-3
Distribution: unstable
Urgency: medium
Maintainer: Vagrant Cascadian 
Changed-By: Vagrant Cascadian 
Closes: 969702
Changes:
 nyacc (1.00.2-3) unstable; urgency=medium
 .
   * Remove lintian overrides for guile byte-copiled objects, no longer
 needed with newer lintian versions.
   * debian/control: Update to guile-3.0 and add versioned dependencies to
 guile-bytestructures (Closes: #969702).
   * debian/control: Upgrade debhelper compat to 13.
   * debian/copyright: Remove redundant stanza for doc/nyacc-ug.*
Checksums-Sha1:
 8acc10d1c6ca86c8f1ae047d4ca2a421415c3a53 1551 nyacc_1.00.2-3.dsc
 2e3e9bb1da61e51c90b520ef99baeffa3d2d88f9 4880 nyacc_1.00.2-3.debian.tar.xz
 2888aa7b35b0029ec3253d7b66e172017a8578a7 5915 nyacc_1.00.2-3_i386.buildinfo
Checksums-Sha256:
 2da0cfd481932508f2b34964358670d806ce9328ac231dbe346ea62d2bb2e37e 1551 
nyacc_1.00.2-3.dsc
 41b30105d96f5192d5991b7ad89d82d1fd3ad1357cec994c1e2a6f8046a0da1b 4880 
nyacc_1.00.2-3.debian.tar.xz
 36d6fac3273254bd4615dbf58a1963b6d456e269f0569c45d19d14c73683ae88 5915 
nyacc_1.00.2-3_i386.buildinfo
Files:
 16d75b93b0601d7dc675ccfd893ab419 1551 devel optional nyacc_1.00.2-3.dsc
 d90e2894f3b27148a13227e16cc147c1 4880 devel optional 
nyacc_1.00.2-3.debian.tar.xz
 25d3d63092ac876a493ac927a3817312 5915 devel optional 
nyacc_1.00.2-3_i386.buildinfo

-BEGIN PGP SIGNATURE-

iIkEARYKADEWIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCX58kmRMcdmFncmFudEBk
ZWJpYW4ub3JnAAoJENxRj8h/lxaqTRcA/jNAmi4D55L+CTKg0J6qb8C5RhDKuZ7B
1R0kzDYai2e+AP9WFGJVYy8lkvYTPWCLWJn7Wp7l1F1NDCOh+DdAi8wwBg==
=DWOE
-END PGP SIGNATURE End Message ---

Bug#972231: marked as done (CVE-2020-15250)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:27:16 +
with message-id 
and subject line Bug#972231: fixed in junit4 4.13.1-1
has caused the Debian Bug report #972231,
regarding CVE-2020-15250
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.)


-- 
972231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: junit4
Version: 4.12-8
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

Please see 
https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: junit4
Source-Version: 4.13.1-1
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
junit4, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated junit4 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: Sun, 01 Nov 2020 21:10:34 +0100
Source: junit4
Architecture: source
Version: 4.13.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 888223 972231
Changes:
 junit4 (4.13.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 4.13.1.
 - Fix CVE-2020-15250: local information disclosure. (Closes: #972231)
   * Switch to debhelper-compat = 13.
   * Refresh Version.patch for new release.
   * Drop privacy-breach-logo.patch and java9/java10-compatibility patches.
 Fixed upstream.
   * Do not install homepage.html. It is gone. (Closes: #888223)
   * Remove junit4-doc.doc-base.2 because homepage.html has been removed.
   * Use debian/copyright format 1.0.
Checksums-Sha1:
 f8300efbf30edb6977a62a3a03d2416105e38b88 2387 junit4_4.13.1-1.dsc
 3a0ecbc272e4bc9029b649b87306f09ee5e69016 844352 junit4_4.13.1.orig.tar.xz
 862dcdfb851950e524b715b9ef06d0362f935d55 28744 junit4_4.13.1-1.debian.tar.xz
 54e4e9bd98448536a08f64d93691daaf9e176dc6 15334 junit4_4.13.1-1_amd64.buildinfo
Checksums-Sha256:
 21edf1119a06ad3be2f4aa116735a4b1ad6d99781d07729e3f67664d8ba78fcd 2387 
junit4_4.13.1-1.dsc
 5a9c9dcceb78c279337eb5a07f5f27356a93699dcd9dd041b4c30db885ca228d 844352 
junit4_4.13.1.orig.tar.xz
 682e443277b24a2ebf310f8f4840b7c95fe783cf04de37442de26443a52616b2 28744 
junit4_4.13.1-1.debian.tar.xz
 af7efa9e567b860f69bbaf154bdd9a76946fe9ef0c8f8387819c75d15fdcb3a1 15334 
junit4_4.13.1-1_amd64.buildinfo
Files:
 24282055807c1925b9d8350af06e4208 2387 java optional junit4_4.13.1-1.dsc
 33ec2d3f743d8e848fdfdd671ecde99c 844352 java optional junit4_4.13.1.orig.tar.xz
 55eb12828af2a85b445d6c2f00cc9a39 28744 java optional 
junit4_4.13.1-1.debian.tar.xz
 b528142f23dbedd0ce904b0a09270d84 15334 java optional 
junit4_4.13.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl+fIgNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk17UP/RLxLb9ATEu2dZdz8SROKLQGinH8eoedPvUu
jmzzZY7J/vt4bij85lT2lbng2EkzswJGC4xE8Jo7F5bps3PjubpFL8omKW5AdHcC
pTTP/l/Q1BE062Ibyog61bLvc1UBOaDgY4H9Bx3AOUXMmKR4yv0J5ftQqLlkBU3b
Y2M5jYKWhj0dynR5NZrIm90BR7dKHp6yYA7S48VbvYsAqXB6cXposipRtPU90Clh
0DgGilgeFY0ZLSS5uqJslH+iXCRgAXURUYeeECSI1xUKMjmlNccksDSjk7pVk+pZ
3AWQa1orh4rE8VNfyxkROnCg+ss905PnMVZSyYLvnrNkNxwxIHUh8CzNRPh1pPGd
dD+xe+xqy1khUze29BazOsB2NP7F5ZOlAYoZBHyxU5nphvoWjzZefx8OJuwWuoYO
jaeL50nF+jIrOM5ZEliPmf3QJ2bErrdakKHBAUr7Qj6LesWvv/rev70mIc5xl/YD
LuoyLOD2Clh9EWqv73Vshoa66md5smgfjk/QSR8g4mxX5NwPyugwFpIAWZT0QPPi
G8WljUqHYDhUsggtQ6kSX4JNY0CB4RGea+h2GBaJzcHkOi5zhHcZZdGf+a9jnbpx
cBK5yggNAgCeD9kG18BAsTBNyC2YqL8TeDIk6WLVPlrhTGULasf3OWgRb6ldGgx4
m8xYy33+
=FIzm
-END PGP SIGNATURE End Message ---

Bug#973235: marked as done (golang-github-c-bata-go-prompt: FTBFS: src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package "golang.org/x/sys/unix")

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 22:26:21 +0100
with message-id <34f84d89-020c-cb62-c67c-6a5c3607e...@micard.lu>
and subject line Bug fixed
has caused the Debian Bug report #973235,
regarding golang-github-c-bata-go-prompt: FTBFS: 
src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package 
"golang.org/x/sys/unix"
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.)


-- 
973235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-c-bata-go-prompt
Version: 0.2.3+git20181109.b6d2b43-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
> src/github.com/pkg/term/termios/ioctl.go:8:2: cannot find package 
> "golang.org/x/sys/unix" in any of:
>   /usr/lib/go-1.15/src/golang.org/x/sys/unix (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/sys/unix (from 
> $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer returned 
> exit code 1
> make: *** [debian/rules:4: build] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/10/27/golang-github-c-bata-go-prompt_0.2.3+git20181109.b6d2b43-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---

Hello,

The bug has been fixed in version 0.2.3+git20181109.b6d2b43-2 which
was uploaded to unstable today.

Cheers,

--
Aloïs Micard (creekorful) 

GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2--- End Message ---

Bug#888223: marked as done (junit4-doc: Dead links in file:///usr/share/doc/junit4-doc/homepage.html)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:27:16 +
with message-id 
and subject line Bug#888223: fixed in junit4 4.13.1-1
has caused the Debian Bug report #888223,
regarding junit4-doc: Dead links in 
file:///usr/share/doc/junit4-doc/homepage.html
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.)


-- 
888223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: junit4-doc
Version: 4.12-4
Severity: normal

Dear Maintainer,

Installed junit4-doc.

Link to cookbook doesn't exist - checked, file not in package.
A quick check shows it existing in testing.

Just logging that this is broken in stable.

Thanks
Joel

-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')

junit4-doc depends on no packages.

Versions of packages junit4-doc recommends:
ii  default-jdk-doc   2:1.8-58
ii  libhamcrest-java-doc  1.3-6

Versions of packages junit4-doc suggests:
ii  junit4  4.12-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: junit4
Source-Version: 4.13.1-1
Done: Markus Koschany 

We believe that the bug you reported is fixed in the latest version of
junit4, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated junit4 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: Sun, 01 Nov 2020 21:10:34 +0100
Source: junit4
Architecture: source
Version: 4.13.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 888223 972231
Changes:
 junit4 (4.13.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 4.13.1.
 - Fix CVE-2020-15250: local information disclosure. (Closes: #972231)
   * Switch to debhelper-compat = 13.
   * Refresh Version.patch for new release.
   * Drop privacy-breach-logo.patch and java9/java10-compatibility patches.
 Fixed upstream.
   * Do not install homepage.html. It is gone. (Closes: #888223)
   * Remove junit4-doc.doc-base.2 because homepage.html has been removed.
   * Use debian/copyright format 1.0.
Checksums-Sha1:
 f8300efbf30edb6977a62a3a03d2416105e38b88 2387 junit4_4.13.1-1.dsc
 3a0ecbc272e4bc9029b649b87306f09ee5e69016 844352 junit4_4.13.1.orig.tar.xz
 862dcdfb851950e524b715b9ef06d0362f935d55 28744 junit4_4.13.1-1.debian.tar.xz
 54e4e9bd98448536a08f64d93691daaf9e176dc6 15334 junit4_4.13.1-1_amd64.buildinfo
Checksums-Sha256:
 21edf1119a06ad3be2f4aa116735a4b1ad6d99781d07729e3f67664d8ba78fcd 2387 
junit4_4.13.1-1.dsc
 5a9c9dcceb78c279337eb5a07f5f27356a93699dcd9dd041b4c30db885ca228d 844352 
junit4_4.13.1.orig.tar.xz
 682e443277b24a2ebf310f8f4840b7c95fe783cf04de37442de26443a52616b2 28744 
junit4_4.13.1-1.debian.tar.xz
 af7efa9e567b860f69bbaf154bdd9a76946fe9ef0c8f8387819c75d15fdcb3a1 15334 
junit4_4.13.1-1_amd64.buildinfo
Files:
 24282055807c1925b9d8350af06e4208 2387 java optional junit4_4.13.1-1.dsc
 33ec2d3f743d8e848fdfdd671ecde99c 844352 java optional junit4_4.13.1.orig.tar.xz
 55eb12828af2a85b445d6c2f00cc9a39 28744 java optional 
junit4_4.13.1-1.debian.tar.xz
 b528142f23dbedd0ce904b0a09270d84 15334 java optional 
junit4_4.13.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl+fIgNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk17UP/RLxLb9ATEu2dZdz8SROKLQGinH8eoedPvUu
jmzzZY7J/vt4bij85lT2lbng2EkzswJGC4xE8Jo7F5bps3PjubpFL8omKW5AdHcC
pTTP/l/Q1BE062Ibyog61bLvc1UBOaDgY4H9Bx3AOUXMmKR4yv0J5ftQqLlkBU3b
Y2M5jYKWhj0dynR5NZrIm90BR7dKHp6yYA7S48VbvYsAqXB6cXposipRtPU90Clh
0DgGilgeFY0ZLSS5uqJslH+iXCRgAXURUYeeECSI1xUKMjmlNccksDSjk7pVk+pZ
3AWQa1orh4rE8VNfyxkROnCg+ss905PnMVZSyYLvnrNkNxwxIHUh8CzNRPh1pPGd
dD+xe+xqy1khUze29BazOsB2NP7F5ZOlAYoZBHyxU5nphvoWjzZefx8OJuwWuoYO
jaeL50nF+jIrOM5ZEliPmf3QJ2bErrdakKHBAUr7Qj6LesWvv/rev70mIc5xl/YD
LuoyLOD2Clh9EWqv73Vshoa66md5smgfjk/QSR8g4mxX5NwPyugwFpIAWZT0QPPi
G8WljUqHYDhUsggtQ6kS

Bug#973316: marked as done (nmu: tpm2-abrmd_2.3.3-1 tpm2-tools_4.3.0-1)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 22:19:56 +0100
with message-id <20201101211956.gb1230...@ramacher.at>
and subject line Re: Bug#973316: nmu: tpm2-abrmd_2.3.3-1 tpm2-tools_4.3.0-1
has caused the Debian Bug report #973316,
regarding nmu: tpm2-abrmd_2.3.3-1 tpm2-tools_4.3.0-1
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.)


-- 
973316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal

Hello,

libtpm2-tss bump the soname of its lib. Make the package
tpm2-abrmd needs to build against the latest libtpm2-tss.
Please see #972118
We have split the tpm2-tss already so that the SONAME matches the
package name.

  nmu tpm2-abrmd_2.3.3-1 . ANY . -m 'Rebuild against the new
libtpm2-tss, see #972118.'
  nmu tpm2-tools_4.3.0-1 . ANY . -m 'Rebuild against the new
libtpm2-tss, see #972659.'

Thanks.|

Yours,
Paul
--- End Message ---
--- Begin Message ---
On 2020-10-29 02:20:10 +0800, Ying-Chun Liu (PaulLiu) wrote:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: binnmu
> Severity: normal
> 
> Hello,
> 
> libtpm2-tss bump the soname of its lib. Make the package
> tpm2-abrmd needs to build against the latest libtpm2-tss.
> Please see #972118
> We have split the tpm2-tss already so that the SONAME matches the
> package name.
> 
>   nmu tpm2-abrmd_2.3.3-1 . ANY . -m 'Rebuild against the new
> libtpm2-tss, see #972118.'
>   nmu tpm2-tools_4.3.0-1 . ANY . -m 'Rebuild against the new
> libtpm2-tss, see #972659.'

Scheduled some time ago already but I forgot to close the bug. Doing
that now.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#972808: marked as done (cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 21:20:09 +
with message-id 
and subject line Bug#972808: fixed in cura-engine 1:4.7.1-2
has caused the Debian Bug report #972808,
regarding cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’
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.)


-- 
972808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cura-engine
Version: 1:4.7.1-1
Severity: serious
Tags: ftbfs

A native build of cura-engine on unstable amd64 ends with:

| [ 86%] Building CXX object 
CMakeFiles/SparseGridTest.dir/tests/utils/SparseGridTest.cpp.o
| /usr/bin/c++ -DARCUS -DBUILD_TESTS -DBUILD_TESTS=1 
-I/usr/include/polyclipping -I/<>/obj-x86_64-linux-gnu -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wall 
-static-libstdc++ -fopenmp -std=gnu++11 -o 
CMakeFiles/SparseGridTest.dir/tests/utils/SparseGridTest.cpp.o -c 
/<>/tests/utils/SparseGridTest.cpp
| In file included from /usr/include/gtest/gtest.h:387,
|  from /<>/tests/utils/SparseGridTest.cpp:4:
| /<>/tests/utils/SparseGridTest.cpp: In member function ‘virtual 
void cura::GetNearbyTest_GetNearby_Test::TestBody()’:
| /<>/tests/utils/SparseGridTest.cpp:48:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|48 | EXPECT_NE(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| /<>/tests/utils/SparseGridTest.cpp:54:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|54 | EXPECT_EQ(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| /<>/tests/utils/SparseGridTest.cpp: In member function ‘virtual 
void cura::GetNearbyTest_getNearbyLine2_Test::TestBody()’:
| /<>/tests/utils/SparseGridTest.cpp:99:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|99 | EXPECT_NE(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| /<>/tests/utils/SparseGridTest.cpp:105:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|   105 | EXPECT_EQ(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| /<>/tests/utils/SparseGridTest.cpp: In member function ‘virtual 
void cura::GetNearbyTest_getNearbyLine_Test::TestBody()’:
| /<>/tests/utils/SparseGridTest.cpp:144:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|   144 | EXPECT_NE(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| /<>/tests/utils/SparseGridTest.cpp:150:38: error: ‘find_if’ is 
not a member of ‘std’; did you mean ‘find’?
|   150 | EXPECT_EQ(result.end(), std::find_if(result.begin(), 
result.end(), [&point](const typename SparsePointGridInclusive::Elem 
&elem) { return elem.val == point; }))
|   |  ^~~
| make[3]: *** [CMakeFiles/SparseGridTest.dir/build.make:98: 
CMakeFiles/SparseGridTest.dir/tests/utils/SparseGridTest.cpp.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:1295: CMakeFiles/SparseGridTest.dir/all] 
Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:185: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" returned exit code 2
| make: *** [debian/rules:10: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This must be a very recent issue as neither crossqa (10 days ago) nor
reproducible builds (6 days ago) have run into this issue. It's reliably
reproducible anyhow. I'm unsure wha

Bug#973533: marked as done (nmu: util-linux_2.36-3+b1)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 22:19:06 +0100
with message-id <20201101211906.ga1230...@ramacher.at>
and subject line Re: Bug#973533: nmu: util-linux_2.36-3+b1
has caused the Debian Bug report #973533,
regarding nmu: util-linux_2.36-3+b1
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.)


-- 
973533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

util-linux doesn't know about the new capabilities from Linux 5.9 yet, e.g.:

% setpriv --bounding-set -all echo test
setpriv: libcap-ng is too old for "all" caps

The problem is not actually libcap-ng but util-linux having picked up an old CAP_LAST_CAP when it 
was built.

Rebuilding against linux-libc-dev 5.9 fixes this:

nmu util-linux_2.36-3+b1 . linux-any . unstable . -m "Rebuild against linux-libc-dev >= 5.9 to 
pick up new capabilities" --extra-depends 'linux-libc-dev (>= 5.9)'

(not sure if linux-any is supported here)
--- End Message ---
--- Begin Message ---
On 2020-11-01 14:00:04 +0100, Felix Geyer wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> util-linux doesn't know about the new capabilities from Linux 5.9 yet, e.g.:
> 
> % setpriv --bounding-set -all echo test
> setpriv: libcap-ng is too old for "all" caps
> 
> The problem is not actually libcap-ng but util-linux having picked up an old
> CAP_LAST_CAP when it was built.
> Rebuilding against linux-libc-dev 5.9 fixes this:
> 
> nmu util-linux_2.36-3+b1 . linux-any . unstable . -m "Rebuild against
> linux-libc-dev >= 5.9 to pick up new capabilities" --extra-depends
> 'linux-libc-dev (>= 5.9)'
> (not sure if linux-any is supported here)

Scheduled, thanks

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---

Bug#972974: marked as done (clamav-freshclam start faild.)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 20:39:49 +
with message-id 
and subject line Bug#972974: fixed in clamav 0.103.0+dfsg-2
has caused the Debian Bug report #972974,
regarding clamav-freshclam start faild.
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.)


-- 
972974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav-freshclam
Version: 0.103.0+dfsg-1
Severity: grave
Justification: renders package unusable

clamav-freshclam start faild with:
Okt 26 18:44:41 host freshclam[31527]: ERROR: initialize: libfreshclam init
failed.
Okt 26 18:44:41 host freshclam[31527]: ERROR: Initialization error!
Okt 26 18:44:41 bert freshclam[31527]: ERROR: Can't open
/var/log/clamav/freshclam.log in append mode (check permissions!).
Okt 26 18:44:41 host systemd[1]: clamav-freshclam.service: Main process exited,
code=exited, status=2/INVALIDARGUMENT
Okt 26 18:44:41 host systemd[1]: clamav-freshclam.service: Failed with result
'exit-code'.

clamav-freshcalm was installed for the first time on this host.



-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamav"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "30"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
ConcurrentDatabaseReload = "yes"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertEncrypted disabled
StructuredCCOnly disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly disabled
DevACDepth disabled
DevPerformance disabled
DevLiblog disabled
DisableCertCheck disabled
AlgorithmicDetection = "yes"
BlockMax disabled
PhishingAlwaysBlockSSLMismatch disabled
PhishingAlwaysBlockCloak disabled
PartitionIntersection disabled
OLE2BlockMacros disabled
ArchiveBlockEncrypted disabled

Config file: freshclam.conf
---
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogSyslog disabled
LogFacility 

Bug#963853: marked as done (clamav: FTBFS on IPv6-only environments)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 20:39:49 +
with message-id 
and subject line Bug#963853: fixed in clamav 0.103.0+dfsg-2
has caused the Debian Bug report #963853,
regarding clamav: FTBFS on IPv6-only environments
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.)


-- 
963853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clamav
Version: 0.102.3+dfsg-1
Severity: serious
Justification: FTBFS (when it built before)

During archive-wide test rebuilding of an IPv6-only environment (which
appears on some normal buildds)[1] we noticed that this package fails:

  Sun Jun 28 05:38:28 2020 -> !TCP: getaddrinfo failed: Address family for 
hostname not supported
  Sun Jun 28 05:38:28 2020 -> *Closing the main socket.
  
  ***
  *** Failed to run /<>/unit_tests/../clamd/clamd -c 
test-clamd.conf, expected 0 exitcode, but was 1
  ***
  
  ***
  *** Failed to run clamd
  ***
  FAIL check4_clamd.sh (exit status: 42)

The full log is available at 
http://perl.debian.net/rebuild-logs/sid-v6only/clamav_0.102.3+dfsg-1/clamav_0.102.3+dfsg-1_amd64-2020-06-28T05:34:48Z.build

One way to replicate this environment is like so:

  # unshare -n
  # ip li set lo up
  # ip li add dummy0 type dummy
  # ip li set dummy0 up

Cheers
Dominic

[1] this test showed approximately 100 packages in the archive failing,
but nearly all of them were due to the behaviour of libio-socket-ip-perl,
so will be fixed centrally. I'm filing bugs about the small number of
unrelated cases.
--- End Message ---
--- Begin Message ---
Source: clamav
Source-Version: 0.103.0+dfsg-2
Done: Sebastian Andrzej Siewior 

We believe that the bug you reported is fixed in the latest version of
clamav, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated clamav 
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: Sun, 01 Nov 2020 20:29:46 +0100
Source: clamav
Architecture: source
Version: 0.103.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: ClamAV Team 
Changed-By: Sebastian Andrzej Siewior 
Closes: 963853 972974
Changes:
 clamav (0.103.0+dfsg-2) unstable; urgency=medium
 .
   * Update apparmor profile for freshclam. Thanks to Michael Borgelt.
 (Closes: #972974)
   * Fix testsuite in an IPv6 only environment (Closes: #963853).
Checksums-Sha1:
 e1d18fdab459433ac644076ebcaed276331c64f6 2777 clamav_0.103.0+dfsg-2.dsc
 688960ed1b30057a0a87178575d581075e4f2f60 220168 
clamav_0.103.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 c3cefa16b8568a9030e9dd4fbd6ce4af8e0e21a40a2950bf4ef84b33844bdff8 2777 
clamav_0.103.0+dfsg-2.dsc
 4bbd7d88e64ed5d054e071c48d72abc0ef80b1fd382941497b3ca6d093811a77 220168 
clamav_0.103.0+dfsg-2.debian.tar.xz
Files:
 fd596cd84261036eff8769a7f89cd3c1 2777 utils optional clamav_0.103.0+dfsg-2.dsc
 0132ac27af211790d545bc43e4234995 220168 utils optional 
clamav_0.103.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEV4kucFIzBRM39v3RBWQfF1cS+lsFAl+fEhcACgkQBWQfF1cS
+ltOkAwAp3j7VM+gdbYQSbXW1TewDgJfU65I971XWNWXC8/to6e49r+YIQNZcoIY
NIeSo6kNZaSk3kdB9bwBBZ+yDQf1luGVyZkdeP/zsS32liTQ8g/3YRWArOMTCGS3
csgPoB6uDv1TG8pld0ItYWCP5c4P+iUMP3TKy1GVZUZ/kom/9CIzr5KX8NxZLpfo
6R/BUSQmZ83pDu5fSwDyCLuRz46QMXP2aRFdjnh2M+SouTkFEBoVBzss0j0uTGeO
UPi6Ipommf6/lG5t7KpzAwCUEHpYbUdIa4cNQNpWEaDCXg59AUM+mktMCtcu/Vs5
9tN54pjho4jFfZlXm5SmlVLb8rNGtpASih1RWyKbaPaBnX4cDJpRVpU9Ax7ABJBI
NQcAHICrBuF60SQnZFur+vl+l2nk0W4oyFuG74ngk/COFEhqA2tqOZ73vHyLphWF
kvNiJC6ZnIZMHTRGwEyTLeiiPPDCml0qjjLNGBXve0jKqQ9LSS9yFpCk5AX+ox3L
pT89dF9n
=pjJp
-END PGP SIGNATURE End Message ---

Bug#882689: marked as done (libidn2: [INTL:de] Initial German translation)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 20:48:33 +0100
with message-id <834dc6b89d34ad5afa3169b38c69b8acbc9c5922.ca...@josefsson.org>
and subject line Re: libidn2: [INTL:de] Initial German translation
has caused the Debian Bug report #882689,
regarding libidn2: [INTL:de] Initial German translation
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.)


-- 
882689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libidn2
Version: 2.0.2
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the German translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Package: libidn2
Version: 2.0.5-1

Hi.  Releases since 2.0.5 have included German translations, so I'm
closing this report.  If there is a problem with the translations,
please send corrections via the translationproject.

/Simon



signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: src:rhino: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.7.7.2-1
Bug #973559 [src:rhino] src:rhino: fails to migrate to testing for too long: 
autopkgtest regression
Marked as fixed in versions rhino/1.7.7.2-1.
Bug #973559 [src:rhino] src:rhino: fails to migrate to testing for too long: 
autopkgtest regression
Marked Bug as done
> block -1 by 970501
Bug #973559 {Done: Paul Gevers } [src:rhino] src:rhino: 
fails to migrate to testing for too long: autopkgtest regression
973559 was not blocked by any bugs.
973559 was not blocking any bugs.
Added blocking bug(s) of 973559: 970501

-- 
973559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:xnnpack: fails to migrate to testing for too long: FTBFS on armhf

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.0~git20200827.37297a6-1
Bug #973560 [src:xnnpack] src:xnnpack: fails to migrate to testing for too 
long: FTBFS on armhf
Marked as fixed in versions xnnpack/0.0~git20200827.37297a6-1.
Bug #973560 [src:xnnpack] src:xnnpack: fails to migrate to testing for too 
long: FTBFS on armhf
Marked Bug as done

-- 
973560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:r-cran-openmx: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.18.1-1
Bug #973558 [src:r-cran-openmx] src:r-cran-openmx: fails to migrate to testing 
for too long: autopkgtest regression
Marked as fixed in versions r-cran-openmx/2.18.1-1.
Bug #973558 [src:r-cran-openmx] src:r-cran-openmx: fails to migrate to testing 
for too long: autopkgtest regression
Marked Bug as done
> block -1 by 971681
Bug #973558 {Done: Paul Gevers } [src:r-cran-openmx] 
src:r-cran-openmx: fails to migrate to testing for too long: autopkgtest 
regression
973558 was not blocked by any bugs.
973558 was not blocking any bugs.
Added blocking bug(s) of 973558: 971681

-- 
973558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#960824: marked as done (restinio: Missing atomic library on several architectures)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 19:34:04 +
with message-id 
and subject line Bug#960824: fixed in restinio 0.6.6-3
has caused the Debian Bug report #960824,
regarding restinio: Missing atomic library on several architectures
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.)


-- 
960824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: restinio
Version: 0.6.6-1
Tags: upstream

The package fail to build on several architectures.  The issue at hand
seem to be missing atomic support in the compiler.  I found a similar
problem and a proposed CMake fix in
https://github.com/kimwalisch/primesieve/pull/46 >.

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Source: restinio
Source-Version: 0.6.6-3
Done: Felix Salfelder 

We believe that the bug you reported is fixed in the latest version of
restinio, 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 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felix Salfelder  (supplier of updated restinio 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: Mon, 19 Oct 2020 08:51:24 +0100
Source: restinio
Architecture: source
Version: 0.6.6-3
Distribution: unstable
Urgency: medium
Maintainer: Felix Salfelder 
Changed-By: Felix Salfelder 
Closes: 960824
Changes:
 restinio (0.6.6-3) unstable; urgency=medium
 .
   * Link atomic on a few architectures (Closes: #960824)
 Thanks to Adrian Bunk.
   * Disable tests (avoid internet access).
Checksums-Sha1:
 9bfb1bdea0a74afc96dd29add0ae9d4dc44bab57 2030 restinio_0.6.6-3.dsc
 09e2ab834cb41cf400f066cdbe0bda42571b3f65 5784 restinio_0.6.6-3.debian.tar.xz
 a4708c4b1fd8efa06910d15a549dd11c14d25b0b 7518 restinio_0.6.6-3_source.buildinfo
Checksums-Sha256:
 d14164caa6133d07fec6fde51cfb4ec9a8fb1a3ef8d0afab20d5db3190d281b5 2030 
restinio_0.6.6-3.dsc
 3e39fd1d7977e067127112a4b0b72fa83a6d60a246cca92f045f8f8dbb2cc61c 5784 
restinio_0.6.6-3.debian.tar.xz
 6175aae18287a8e67c0f64751345f09851a6b4be5f7af38f74f3c70212136f5d 7518 
restinio_0.6.6-3_source.buildinfo
Files:
 e50c55530ed873b555b0526a0c30b2d4 2030 libs optional restinio_0.6.6-3.dsc
 1cb031c3f2a1b75aaaddca41acd5ad3f 5784 libs optional 
restinio_0.6.6-3.debian.tar.xz
 f61edfbf4d0da61391080fe4ca5ec59c 7518 libs optional 
restinio_0.6.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEKooWhuTJfVjOx6UQc9PBbl+Tg+0FAl+fDFkUHGZlbGl4QHNh
bGZlbGRlci5vcmcACgkQc9PBbl+Tg+3Nyg/+KzHJ1GF5wsvNsra6x4kbeU1kBmXQ
7pVAhA1BmQz1iRt+uOChwyplp2KLbKfLK3zKQTnaxiTtukO/4EU0VvN5sOhSvXHg
EHhhhIApovOgvFPCdzNMnnA8LSPeu3On9FpWmD5fPE3TX+8hF90oWtBhNh0mHjou
HjC9hsA+btZIheYWiJo9KfomIS2qCUTiTyygqn/9WCkYijcXnTCb2n6UlH7LAcxB
VCisHi+7UJdEr2FlI/9dXier06L9sQp49h9QEkxcGViV4mQ9jK07bnU1z9/qx4Gu
Q4NYyltAEdUsQu+Shq8YQ5weWCzjZFFy2jfJkayZX+Il0xLeYvTt4SVSVLJcZV7M
Hi4TISsnaNqiXOGHBKzXQsJdlab7iOEhUuPEMIFZ7ADhyjZ9/Vu3RtC6mp4FPRKz
dV23Tn/ClCSvb//6ctvWKSr2ji4G3wTOKsW1LaejcmcEKeqsf03SpRbNb0HwEisL
X9aqOdVe80xSr0WisFtm+EWo9Qilixo8OONJMCNKUF0KKfbCKWGX17ph/6wN9Hdm
UxK2l3FpAxyWtZch1SHq4dhsegh1yr5a6DHr+ym4t/wCMe1SrLHtteKOTYgV0XBS
VdLfq+2Sr+OxinghHd5leYSFeFPi9RRLaMX7oRaDXx4eG9flXXfbzVMVvEF5DAmN
YEdDb0jtGuZ1OM0=
=JrRa
-END PGP SIGNATURE End Message ---

Bug#964072: marked as done (clamav: freshclam update fails when using different working dir besides default /var/lib/clamav)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 19:48:33 +0100
with message-id <20201101184833.ksuumsw2eojddntm@flow>
and subject line Re: Bug#964072: clamav: freshclam update fails when using 
different working dir besides default /var/lib/clamav
has caused the Debian Bug report #964072,
regarding clamav: freshclam update fails when using different working dir 
besides default /var/lib/clamav
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.)


-- 
964072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav
Version: 0.102.3+dfsg-0+deb10u1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
 -wanted to use a different dir for updating the virus signatures
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 -created a new folder with identical access rights (like /var/lib/clamav) 
and changed
  the DataBaseDirectory in clamd.conf and freshclam.conf accordingly
 -then attempted to run freshclam for update (automatic freshclam update 
eas stopped beforehand) 
   * What was the outcome of this action?
 -error message: !checkdbdir: Can't open directory /var/lib/clamavtest/
 !Update failed.
   * What outcome did you expect instead?
 -a successful update since the config files were correctly adjusted and 
the access rights of the dir are identical to the default

*** End of the template - remove these template lines ***


-- Package-specific info:
--- configuration ---
Checking configuration files in /etc/clamav

Config file: clamd.conf
---
AlertExceedsMax disabled
PreludeEnable disabled
PreludeAnalyzerName = "ClamAV"
LogFile = "/var/log/clamav/clamav.log"
LogFileUnlock disabled
LogFileMaxSize = "4294967295"
LogTime = "yes"
LogClean disabled
LogSyslog disabled
LogFacility = "LOG_LOCAL6"
LogVerbose disabled
LogRotate = "yes"
ExtendedDetectionInfo = "yes"
PidFile disabled
TemporaryDirectory disabled
DatabaseDirectory = "/var/lib/clamavtest"
OfficialDatabaseOnly disabled
LocalSocket = "/var/run/clamav/clamd.ctl"
LocalSocketGroup = "clamav"
LocalSocketMode = "666"
FixStaleSocket = "yes"
TCPSocket disabled
TCPAddr disabled
MaxConnectionQueueLength = "15"
StreamMaxLength = "26214400"
StreamMinPort = "1024"
StreamMaxPort = "2048"
MaxThreads = "12"
ReadTimeout = "180"
CommandReadTimeout = "30"
SendBufTimeout = "200"
MaxQueue = "100"
IdleTimeout = "30"
ExcludePath disabled
MaxDirectoryRecursion = "15"
FollowDirectorySymlinks disabled
FollowFileSymlinks disabled
CrossFilesystems = "yes"
SelfCheck = "3600"
DisableCache disabled
VirusEvent disabled
ExitOnOOM disabled
AllowAllMatchScan = "yes"
Foreground disabled
Debug disabled
LeaveTemporaryFiles disabled
User = "clamav"
Bytecode = "yes"
BytecodeSecurity = "TrustSigned"
BytecodeTimeout = "6"
BytecodeUnsigned disabled
BytecodeMode = "Auto"
DetectPUA disabled
ExcludePUA disabled
IncludePUA disabled
ScanPE = "yes"
ScanELF = "yes"
ScanMail = "yes"
ScanPartialMessages disabled
PhishingSignatures = "yes"
PhishingScanURLs = "yes"
HeuristicAlerts = "yes"
HeuristicScanPrecedence disabled
StructuredDataDetection disabled
StructuredMinCreditCardCount = "3"
StructuredMinSSNCount = "3"
StructuredSSNFormatNormal = "yes"
StructuredSSNFormatStripped disabled
ScanHTML = "yes"
ScanOLE2 = "yes"
AlertBrokenExecutables disabled
AlertEncrypted disabled
AlertEncryptedArchive disabled
AlertEncryptedDoc disabled
AlertOLE2Macros disabled
AlertPhishingSSLMismatch disabled
AlertPhishingCloak disabled
AlertPartitionIntersection disabled
ScanPDF = "yes"
ScanSWF = "yes"
ScanXMLDOCS = "yes"
ScanHWP3 = "yes"
ScanArchive = "yes"
ForceToDisk disabled
MaxScanTime = "12"
MaxScanSize = "104857600"
MaxFileSize = "26214400"
MaxRecursion = "16"
MaxFiles = "1"
MaxEmbeddedPE = "10485760"
MaxHTMLNormalize = "10485760"
MaxHTMLNoTags = "2097152"
MaxScriptNormalize = "5242880"
MaxZipTypeRcg = "1048576"
MaxPartitions = "50"
MaxIconsPE = "100"
MaxRecHWP3 = "16"
PCREMatchLimit = "1"
PCRERecMatchLimit = "5000"
PCREMaxFileSize = "26214400"
OnAccessMountPath disabled
OnAccessIncludePath disabled
OnAccessExcludePath disabled
OnAccessExcludeRootUID disabled
OnAccessExcludeUID disabled
OnAccessExcludeUname disabled
OnAccessMaxFileSize = "5242880"
OnAccessDisableDDD disabled
OnAccessPrevention disabled
OnAccessExtraScanning disabled
OnAccessCurlTimeout = "5000"
OnAccessMaxThreads = "5"
OnAccessRetryAttempts disabled
OnAccessDenyOnError disabled
DevACOnly di

Bug#971354: marked as done (Please build-depends on python3-setuptools-scm >= 4.1.2)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 19:04:40 +
with message-id 
and subject line Bug#971354: fixed in lazy-object-proxy 1.5.1-2
has caused the Debian Bug report #971354,
regarding Please build-depends on python3-setuptools-scm >= 4.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.)


-- 
971354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lazy-object-proxy
Severity: important

Hi,

I tried to backport lazy-object-proxy to Buster, and it failed with
python3-setuptools-scm 3.2.0. After backporting and using python3-setuptools-scm
4.1.2, it could build.

So please add the >= 4.1.2 constraint in debian/control to ease backporting.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: lazy-object-proxy
Source-Version: 1.5.1-2
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
lazy-object-proxy, 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.
Sandro Tosi  (supplier of updated lazy-object-proxy 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: Sun, 01 Nov 2020 13:49:42 -0500
Source: lazy-object-proxy
Architecture: source
Version: 1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 971354
Changes:
 lazy-object-proxy (1.5.1-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * debian/control
 - set setuptools-scm as a versioned b-d as >= 4.1.2; Closes: #971354
Checksums-Sha1:
 fd0bf39a85d1d5526f765a6712bbf5d919487e64 2158 lazy-object-proxy_1.5.1-2.dsc
 1b68482a35831b0d242e60597c75e0fc4473f6a9 5336 
lazy-object-proxy_1.5.1-2.debian.tar.xz
 a9da86a681c22bc02fa8dc09d163b0b9e0827335 6705 
lazy-object-proxy_1.5.1-2_source.buildinfo
Checksums-Sha256:
 5732e9d2424139180e563fac6d00414788526822c33e1ae120cb8c055864b1be 2158 
lazy-object-proxy_1.5.1-2.dsc
 41a0b38ab8585c84e31485ba3d7b652b945260af6a46542d57a479615ce3c545 5336 
lazy-object-proxy_1.5.1-2.debian.tar.xz
 222ccd09db578889aa1b87fd7b24db1cf89c185fe1c1ff1bb80b23cd91c6bbcf 6705 
lazy-object-proxy_1.5.1-2_source.buildinfo
Files:
 f1fbf7cbaf536e4edd96b19ca862d0eb 2158 python optional 
lazy-object-proxy_1.5.1-2.dsc
 fba5db286051e461e4b0caed186fe656 5336 python optional 
lazy-object-proxy_1.5.1-2.debian.tar.xz
 20962378a6bc78fafb592a6aa12d239b 6705 python optional 
lazy-object-proxy_1.5.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl+fA1cACgkQh588mTgB
qU8F4RAA02KA8wYKKH9sj7PIAU6QGfzn0PUp1789ho7IaK5KU/uPOgwvimRJtgCu
PVmRT+CK36YFu3rwtNT7a/6pGpIYE08+pMF4NaweF86yHDpCMsvMje+HguzsVOdh
pWBj0k7xdeI03uA4+B7guHKpQ2IPSlEK4ugZ8nniwY5GB/Due1fXpChMbxjrYKD+
FD698TyEuTyEqx97rSHZczpoY9G30ke/RpSlm7ROSWngslHAxkvugkhYOHn+JjWr
jF+nU8x3Sz7RgtAxa0k6P1haQ8iRyNsCln/P5Pt0efj3sTvx8cYqzoLzoIX7LTO4
or0D0TOR/BjZ/ag3Bg/Syv8zW/C06JMADW9bSALDN2Ap33H1ZKh8HwcBHz+XBNqw
bTA/MLVrPDhBfuqsE+tl3x855Vfp88M2x6+Mseh0c3XI+QJdtvth7hcUZMrOaXtf
w9Yj0gSYwLFBBW6HlyngzmDUBfUg8/sTwXxA+cHHaiNRvVp1bKoYm2Bi65YT2DLY
omMUqtCoh38h+2tjODTFxWU8gj0o1XfrILta7E8CvriH1p6imgN3bYdhwg4WaNft
Gf4mAJdOugwmpDqxXDPI6aZdhPnVinZe/BXmJdzr2klzHo1AbK7hPeFlQtZuR8Sy
FERotvUoh7/aty8JyWNGm/K1m5//VsHfc/1BTkvKfL4d/FS/T+Q=
=tRqU
-END PGP SIGNATURE End Message ---

Bug#971199: marked as done (texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 19:07:03 +
with message-id 
and subject line Bug#971199: fixed in texext 0.6.6-2
has caused the Debian Bug report #971199,
regarding texext: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.8 returned exit code 13
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.)


-- 
971199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texext
Version: 0.6.6-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):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_texext/build/texext
> copying texext/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext
> copying texext/math_dollar.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext
> copying texext/_version.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext
> copying texext/mathcode.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext
> creating /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_mathdollar.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/for_docstrings.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_plotdirective.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/conftest.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_custom_plotdirective.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_tinypages.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_docstrings.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> copying texext/tests/test_custom_plotcontext.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests
> creating 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/some_math.rst -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/index.rst -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages
> copying texext/tests/tinypages/conf.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages
> creating 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages/_static
> copying texext/tests/tinypages/_static/README.txt -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/tinypages/_static
> creating 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/index.rst -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/plot_and_math.rst -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective
> copying texext/tests/plotdirective/conf.py -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective
> creating 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective/_static
> copying texext/tests/plotdirective/_static/README.txt -> 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/tests/plotdirective/_static
> UPDATING 
> /<>/.pybuild/cpython3_3.8_texext/build/texext/_version.py
> set /<>/.pybuild/cpython3_3.8_texext/build/texext/_version.py to 
> '0.6.6'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_texext/build; 
> python3.8 -m pytest 
> = test session starts 
> ==
> platform linux -- Python 3.8.6, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>
> collected 17 items
> 
> texext/tests/test_custom_plotcontext.py  [ 
> 23%]
> texext/tests/test_custom_plotdirective.py .. [ 
> 35%]
> texext/tests/test_docstrings.py ..   [ 
> 47%]
> texext/tests/test_mathdollar.py .  

Bug#961985: marked as done (hub is no longer the official GitHub API tool)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 19:04:35 +
with message-id 
and subject line Bug#961985: fixed in hub 2.7.0~ds1-2
has caused the Debian Bug report #961985,
regarding hub is no longer the official GitHub API tool
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.)


-- 
961985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hub
Version: 2.7.0~ds1-1+b10
Severity: normal

hub is no longer the official GitHub API tool and has been replaced
with gh, please update the package description:

https://github.blog/changelog/2020-05-11-github-cli-allows-you-to-close-reopen-and-add-metadata-to-issues-and-pull-requests/
https://cli.github.com/
https://github.com/cli/cli

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hub depends on:
ii  git1:2.26.2-1
ii  libc6  2.30-8

Versions of packages hub recommends:
ii  xclip  0.13-1

hub suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: hub
Source-Version: 2.7.0~ds1-2
Done: =?utf-8?q?Alo=C3=AFs_Micard?= 

We believe that the bug you reported is fixed in the latest version of
hub, 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 961...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aloïs Micard  (supplier of updated hub 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: Sun, 01 Nov 2020 19:47:01 +0100
Source: hub
Architecture: source
Version: 2.7.0~ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Aloïs Micard 
Closes: 961985
Changes:
 hub (2.7.0~ds1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 9 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Aloïs Micard ]
   * Bump debhelper compat to 13.
   * Add d/upstream/metadata.
   * Indicate that hub is not Github official client anymore (Closes: #961985).
   * Add Rules-Requires-Root: no.
Checksums-Sha1:
 6c5bdacc40a60ef4cdad5f1f91673e3c62ba63c1 2402 hub_2.7.0~ds1-2.dsc
 63f65d6563caca6f6e7c4d9f37bc9b87d82153a9 5112 hub_2.7.0~ds1-2.debian.tar.xz
 bb44cd54de940039d79c316282a41269bf4f5a20 8347 hub_2.7.0~ds1-2_amd64.buildinfo
Checksums-Sha256:
 ef651f1f246a97f0dd155e9bc249ba36ee64cd89976c2447e17c3e6c1a7e301a 2402 
hub_2.7.0~ds1-2.dsc
 01d873720ceae3d85891e2ab9091a0eda6926937f2515df59267b4dfecd7f386 5112 
hub_2.7.0~ds1-2.debian.tar.xz
 fee80e1d7f6d1ab84dca09a0034ab39eefe1a74bf2fdd43aa5b83d4c3cb064ae 8347 
hub_2.7.0~ds1-2_amd64.buildinfo
Files:
 57ef9d51c47a022a43ca0bb54b6baa52 2402 net optional hub_2.7.0~ds1-2.dsc
 274242df6f76a9cad5cf425f2ba8 5112 net optional 
hub_2.7.0~ds1-2.debian.tar.xz
 708e15115452a4834f5b174f7d0a23c1 8347 net optional 
hub_2.7.0~ds1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECYc16JDXWgmzZBaOGg64LwcfXv4FAl+fA6EQHGFsb2lzQG1p
Y2FyZC5sdQAKCRAaDrgvBx9e/kdED/4rIfAudwKA8eoNm7uNwaJ4GPrZdts+RXMn
9K+L2TjubRn7dIqkEghWP5f2K95nrclVjEmEp3lnIur+P3MGYWJ21I9zFBq7JwQk
2afMOOFnILkKsGCz6FVItVE/WqQkupkz+VNIMAMyENWLl9arfUfvNFZfghb5TQFw
6uDkp22nvzl1g5sfe5sZYbsZjoHm0vYmSKVfkr3HRruz61ap9gggpqtQv/eR8mUx
a6MKQRgMXPneBg2Qb/0I4b6FrWthQFz8u7NdubDNGsTP+cMZLJvyIlYOU8T3m3VA
ueOskuQv28hadwUxUdUYsFAcAqOjQL7lGKQJXOyx5ZN3e6IzSgijrWvYMncfEr2e
qaMtoY0SzBsc/icm6ANKqfO3XkRvs5ymUOAH9OZB/83oV9DWbnEzipkghnnZW58L
zNPJjoALrKWtHwMD1vdllI

Bug#922617: marked as done (clamav-freshclam: tries to set SE Linux context before creating dir and fails)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 19:24:15 +0100
with message-id <20201101182415.r3evh5p7punvol3b@flow>
and subject line Re: Bug#922617: clamav-freshclam: tries to set SE Linux 
context before creating dir and fails
has caused the Debian Bug report #922617,
regarding clamav-freshclam: tries to set SE Linux context before creating dir 
and fails
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.)


-- 
922617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav-freshclam
Version: 0.100.2+dfsg-2
Severity: normal
Tags: patch


The init script tries to set the context of the directory (think chown or
chmod) before creating it.  Here is the patch to fix it.

--- /etc/init.d/clamav-freshclam.orig   2019-02-19 00:18:42.180626975 +1100
+++ /etc/init.d/clamav-freshclam2019-02-19 00:19:35.828821960 +1100
@@ -187,13 +187,13 @@
 make_dir()
 {
   DIR=$1
-  [ -x /sbin/restorecon ] && /sbin/restorecon "$DIR"
   if [ -d "$DIR" ]; then
 return 0;
   fi
   [ -n "$User" ] || User=clamav
   mkdir -p -m 0755 "$DIR"
   chown "$User" "$DIR"
+  [ -x /sbin/restorecon ] && /sbin/restorecon "$DIR"
 }
 
 # Debconf Functions
--- End Message ---
--- Begin Message ---
On 2019-02-19 00:25:21 [+1100], Russell Coker wrote:
> Version: 0.100.2+dfsg-2
…
> The init script tries to set the context of the directory (think chown or
> chmod) before creating it.  Here is the patch to fix it.

I'm going to close this. The report says 0.100.2+dfsg-2 but looking at
0.100.2+dfsg-1 I see

|debian/common_functions-
|debian/common_functions-make_dir()
|debian/common_functions-{
|debian/common_functions-  DIR=$1
|debian/common_functions-  if [ -d "$DIR" ]; then
|debian/common_functions-return 0;
|debian/common_functions-  fi
|debian/common_functions-  [ -n "$User" ] || User=clamav
|debian/common_functions-  mkdir -p -m 0755 "$DIR"
|debian/common_functions-  chown "$User" "$DIR"
|debian/common_functions:  pathfind restorecon && restorecon "$DIR"

which is what the patch suggests. This is also part of the most recent
version of the package.

> --- /etc/init.d/clamav-freshclam.orig 2019-02-19 00:18:42.180626975 +1100
> +++ /etc/init.d/clamav-freshclam  2019-02-19 00:19:35.828821960 +1100
> @@ -187,13 +187,13 @@
>  make_dir()
>  {
>DIR=$1
> -  [ -x /sbin/restorecon ] && /sbin/restorecon "$DIR"
>if [ -d "$DIR" ]; then
>  return 0;
>fi
>[ -n "$User" ] || User=clamav
>mkdir -p -m 0755 "$DIR"
>chown "$User" "$DIR"
> +  [ -x /sbin/restorecon ] && /sbin/restorecon "$DIR"
>  }
>  
>  # Debconf Functions

Sebastian--- End Message ---

Bug#939850: marked as done (clamav-daemon: timeout on /run/clamav/clamd.ctl, too slow to reload daily.ldb rules)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 19:35:46 +0100
with message-id <20201101183546.jyokrpyvud2sc3nu@flow>
and subject line Re: Bug#939850: clamav-daemon: timeout on 
/run/clamav/clamd.ctl, too slow to reload daily.ldb rules
has caused the Debian Bug report #939850,
regarding clamav-daemon: timeout on /run/clamav/clamd.ctl, too slow to reload 
daily.ldb rules
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.)


-- 
939850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clamav-daemon
Severity: important

Dear maintainer,

Since a couple of week, I get the following errors from my MTA exim:

From /var/log/exim4/paniclog: 

malware acl condition: clamd /var/run/clamav/clamd.ctl : unable to read 
from socket (Connection timed out)

I'm on buster with an up-to-date box, using the following version
for clamav:

clamav   0.101.4+dfsg-0+deb10u1   amd64
clamav-base  0.101.4+dfsg-0+deb10u1   all 
clamav-daemon0.101.4+dfsg-0+deb10u1   amd64
clamav-freshclam 0.101.4+dfsg-0+deb10u1   amd64
libclamav9:amd64 0.101.4+dfsg-0+deb10u1   amd64

Going through clamav's log. I found out that the socket become
unavailable when clamav is reloading its database. See bug #432334[1].

Usually, this is not a problem since the reload is quite quick.
However, currently and on my server, it take up to 2 minutes and half.

See logs:

Aug 25 09:02:44 lyra clamd[892]: Sun Aug 25 09:02:44 2019 -> Reading 
databases from /var/lib/clamav
Aug 25 09:05:29 lyra clamd[892]: Sun Aug 25 09:05:29 2019 -> Database 
correctly reloaded (6291419 signatures)
Aug 26 09:05:21 lyra clamd[892]: Mon Aug 26 09:05:21 2019 -> Reading 
databases from /var/lib/clamav
Aug 26 09:08:09 lyra clamd[892]: Mon Aug 26 09:08:09 2019 -> Database 
correctly reloaded (6292270 signatures)
Aug 27 09:07:57 lyra clamd[892]: Tue Aug 27 09:07:57 2019 -> Reading 
databases from /var/lib/clamav
Aug 27 09:10:47 lyra clamd[892]: Tue Aug 27 09:10:47 2019 -> Database 
correctly reloaded (6293807 signatures)
Aug 28 09:10:36 lyra clamd[892]: Wed Aug 28 09:10:36 2019 -> Reading 
databases from /var/lib/clamav
Aug 28 09:13:26 lyra clamd[892]: Wed Aug 28 09:13:26 2019 -> Database 
correctly reloaded (6295218 signatures)
Aug 29 09:13:16 lyra clamd[892]: Thu Aug 29 09:13:16 2019 -> Reading 
databases from /var/lib/clamav
Aug 29 09:16:07 lyra clamd[892]: Thu Aug 29 09:16:07 2019 -> Database 
correctly reloaded (6296694 signatures)
Aug 30 09:15:55 lyra clamd[892]: Fri Aug 30 09:15:55 2019 -> Reading 
databases from /var/lib/clamav
Aug 30 09:18:48 lyra clamd[892]: Fri Aug 30 09:18:48 2019 -> Database 
correctly reloaded (629 signatures)
Aug 31 09:18:38 lyra clamd[892]: Sat Aug 31 09:18:38 2019 -> Reading 
databases from /var/lib/clamav
Aug 31 09:21:32 lyra clamd[892]: Sat Aug 31 09:21:32 2019 -> Database 
correctly reloaded (6300225 signatures)

(today's logs are the same)

During that reload time, clamav become unreachable and trigger errors
for exim. I had a look at what files where taking that much time to
reload and the issue seems to come from the daily.ldb.

# for file in *.cvd; do echo -n "${file} "; clamscan -d ${file} 
/etc/modules | grep Time:; done
bytecode.cvd Time: 0.033 sec (0 m 0 s)
daily.cvd Time: 73.116 sec (1 m 13 s)
main.cvd Time: 8.738 sec (0 m 8 s)

# sigtool -u daily.cvd

# for file in daily.*; do echo -n "${file} "; clamscan -d ${file} 
/etc/modules | grep Time:; done
daily.cdb Time: 0.008 sec (0 m 0 s)
daily.cfg Time: 0.009 sec (0 m 0 s)
daily.crb Time: 0.008 sec (0 m 0 s)
daily.fp Time: 0.009 sec (0 m 0 s)
daily.ftm Time: 0.008 sec (0 m 0 s)
daily.hdb Time: 0.447 sec (0 m 0 s)
daily.hdu Time: 0.008 sec (0 m 0 s)
daily.hsb Time: 1.609 sec (0 m 1 s)
daily.hsu Time: 0.008 sec (0 m 0 s)
daily.idb Time: 0.009 sec (0 m 0 s)
daily.ign Time: 0.010 sec (0 m 0 s)
daily.ign2 Time: 0.010 sec (0 m 0 s)
daily.ldb Time: 62.581 sec (1 m 2 s)
daily.ldu Time: 0.008 sec (0 m 0 s)
daily.mdb Time: 0.084 sec (0 m 0 s)
daily.mdu Time: 0.008 sec (0 m 0 s)
daily.msb Time: 0.008 sec (0 m 0 s)
daily.msu Time: 0.009 sec (0 m 0 s)
daily.ndb Time: 0.029 sec (0 m 0 s)
daily.ndu Time: 0.009 sec (0 m 0 s)
daily.pdb Time: 0.020 sec (0 m 0 s)
daily.sfp Time: 0.008 sec (0 m 0 

Bug#750156: marked as done (puddletag: Puddletag does not Album Art panel (under Gnome 3/Gnome Shell))

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 13:28:30 -0500
with message-id 

and subject line Re: Bug#750156: puddletag: Puddletag does not Album Art panel 
(under Gnome 3/Gnome Shell)
has caused the Debian Bug report #750156,
regarding puddletag: Puddletag does not Album Art panel (under Gnome 3/Gnome 
Shell)
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.)


-- 
750156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: puddletag
Version: 1.0.2-1
Severity: normal

Dear Maintainer,

There is supposed to be a Album Cover/Album Art panel in puddletag.
When I select the corresponding menu item (Windows>Artwork) nothing
happens though. No panel is added, no window is opened, nothing.
Album Art information is accessible by using a workaround (extended
tags), it just is not very convenient.

It seems that I am not the only one having this problem, see e.g.
http://sourceforge.net/apps/phpbb/puddletag/viewtopic.php?f=3&t=137
so this *might* be an upstream bug.

It might have something to do with my using Gnome Shell/Gnome3  as a 
window manager/desktop environment.

ii  gnome-shell3.8.4-8.1amd64graphical shell for the GNOME des

TIA
/ralph

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages puddletag depends on:
ii  libjs-sphinxdoc   1.2.2+dfsg-2
ii  python2.7.6-2
ii  python-acoustid   1.0.0-1
ii  python-audioread  1.0.1-1
ii  python-configobj  4.7.2+ds-5
ii  python-mutagen1.22-1
ii  python-pyparsing  2.0.1+dfsg1-1
ii  python-qt44.10.4+dfsg-2
ii  python-support1.0.15

Versions of packages puddletag recommends:
ii  libchromaprint-tools  1.1-1+b1
ii  python-musicbrainz2   0.7.4-1

Versions of packages puddletag suggests:
pn  quodlibet  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0.1-1

> puddletag was recently reintroduced to Debian unstable, it would be
> great if you could check the new version.

this is fixed in the version in unstable

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---

Bug#972318: marked as done (FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 19:23:50 +0100
with message-id <55f1337b-52a4-8382-a724-c4443f2b0...@debian.org>
and subject line fixed
has caused the Debian Bug report #972318,
regarding FTBFS on ppc64el
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.)


-- 
972318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-10
Version: 1:10.0.1-6
Severity: serious
Tags: ftbfs

Dear Maintainer,

Your package FTBFS on ppc64el:

  https://buildd.debian.org/status/package.php?p=llvm-toolchain-10

The rebuild was triggered by the update of OCaml from 4.08.1 to
4.11.1, but the error looks independent (I might be wrong).

The build log ends with:
> ar ruv libFuzzer.a Fuzzer*.o
> -g -O2 -fdebug-prefix-map=/<>/build-llvm=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2
> Segmentation fault
> ar: `u' modifier ignored since `D' is the default (see `U')
> ar: creating libFuzzer.a
> ar: Fuzzer*.o: No such file or directory
> make[1]: *** [debian/rules:420: debian-libfuzzer-build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:286: binary-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
> status 2


Cheers,

-- 
Stéphane

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---

fixed 972318 1:10.0.1-8
thanks--- End Message ---

Bug#972333: marked as done (llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 19:22:59 +0100
with message-id <3bb0c82b-ff45-8a31-e55d-c66f5dcec...@debian.org>
and subject line fixed
has caused the Debian Bug report #972333,
regarding llvm-toolchain-11: FTBFS on ppc64el: realloc(): invalid old size
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.)


-- 
972333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-11
Version: 1:11.0.0-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

llvm-toolchain-11 currently FTBFS on mipsel64:
| cd build-llvm; \
| CFLAGS=`dpkg-buildflags --get CFLAGS`; \
| CFLAGS="$CFLAGS `dpkg-buildflags --get CPPFLAGS`"; \
| echo $CFLAGS; \
| /<>/build-llvm/tools/clang/stage2-bins/bin/clang++ -c $CFLAGS 
-std=c++11 /<>/compiler-rt/lib/fuzzer/*.cpp -IFuzzer; \
| ar ruv libFuzzer.a Fuzzer*.o
| -g -O2 -fdebug-prefix-map=/<>/build-llvm=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2
| realloc(): invalid old size
| Aborted
| ar: `u' modifier ignored since `D' is the default (see `U')
| ar: creating libFuzzer.a
| ar: Fuzzer*.o: No such file or directory
| make[1]: *** [debian/rules:425: debian-libfuzzer-build] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-11&arch=ppc64el&ver=1%3A11.0.0-2&stamp=1602683353&raw=0

It fails in the same step as llvm-toolchain-10 (#972318), but fails in a
different way.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

fixed 972333 1:11.0.0-4
thanks--- End Message ---

Bug#765104: marked as done (Update hfsprogs to 572.1.1)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 18:18:32 +
with message-id 
and subject line Bug#765104: fixed in hfsprogs 540.1.linux3-1
has caused the Debian Bug report #765104,
regarding Update hfsprogs to 572.1.1
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.)


-- 
765104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hfsprogs
Severity: normal

Hello,

hfsprogs which is derived from diskdev_cmds is very out of date vs Apple
sources. It is currently version 332.25 which was from 10.4 (~ 5-6 years
old) when upstream is up to 10.9.5 and version 572.1.1. Version 10.10 will
likely be released in a week or so.

http://www.opensource.apple.com/release/os-x-1095/

Thanks,

Chris Cheney
--- End Message ---
--- Begin Message ---
Source: hfsprogs
Source-Version: 540.1.linux3-1
Done: John Paul Adrian Glaubitz 

We believe that the bug you reported is fixed in the latest version of
hfsprogs, 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 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
hfsprogs 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: Sun, 01 Nov 2020 18:56:49 +0100
Source: hfsprogs
Architecture: source
Version: 540.1.linux3-1
Distribution: unstable
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Closes: 765104 958522 967986
Changes:
 hfsprogs (540.1.linux3-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #765104)
   * Remove all Debian patches for the previous upstream version
   * Set myself as maintainer in debian/control (Closes: #958522)
   * Strip unnecessary CFLAGS and LDFLAGS from debian/rules
   * Remove unnecessary override_dh_auto_build from debian/rules
   * Add uuid-dev to Build-Depends in debian/control
   * Remove installation of hfsbootdata.img from debian/rules
   * Update debhelper version to 12 and switch to debhelper-compat
   * Add patch from Fedora to allow building hfsprogs with gcc
   * Add patch from Fedora to fix FTBFS on ARM
   * Add patch from Fedora to fix FTBFS with glibc >= 2.32 (Closes: #967986)
   * Add patch to replace $(PWD) with $(CURDIR) in Makefile
   * Convert debian/copyright to machine-readable format and update years
   * Add Vcs-* fields to debian/control
   * Update Homepage field in debian/control
   * Reformat debian/control to match commonly used format
   * Update Standards-Version to 4.5.0 in debian/control
Checksums-Sha1:
 c5a34ae719d5dea271b3d896df94fd2b485f54b4 1950 hfsprogs_540.1.linux3-1.dsc
 edf695e9b8d36aa7a13e976c8e19746b26dd52ec 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 8ffae2a650c0e891e42850fe83964aafe4ec8e55 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 a42ea92897b5ef6a640e82469c5d7c4257d94b18 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Checksums-Sha256:
 de22cca663e1ad470cd9dae6daddc9c07c1eb55ed7a4dd2c5976f1360acb908b 1950 
hfsprogs_540.1.linux3-1.dsc
 b01b203a97f9a3bf36a027c13ddfc59292730552e62722d690d33bd5c24f5497 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 a7f11771e650b585d4887c2cc034c3d23c2cb29fc4c76bed424486ceb954a7b2 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 885ea1e8f0eb22f99e63c25fc540b191c50b9ff5e8cb230bf01387946cc74383 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Files:
 a18ca1d0f3e69a47b0bfb19decb44137 1950 otherosfs optional 
hfsprogs_540.1.linux3-1.dsc
 0435afc389b919027b69616ad1b05709 411205 otherosfs optional 
hfsprogs_540.1.linux3.orig.tar.gz
 c7b05fade62898d4d9fef6f2e02b1c23 15428 otherosfs optional 
hfsprogs_540.1.linux3-1.debian.tar.xz
 280157a006d22fda13d5b49fce2d3769 6308 otherosfs optional 
hfsprogs_540.1.linux3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl+e920ACgkQdCY7N/W1
+RM/AA//V23actm2KU225htt3GE555tFxSSn2pbUcwKKjhDxUlx/8d4hNithnY+j
ukdj8xzA1XAoRleeLsQkpTC6DoMAWUISfZyNZ5/oU5BFTTZea2yfJuvCetb7F+Cq
mI654XoxqX1ScbnJtM0Rm5pbJxbvOOGNQaCCToIS/s51ZaizNfJjOu6OsLUZkK8p
P6kJUqc6qy6tKPP7xTBTxaQf/rL96IE7ClFP5Two59Rwjwg1et5C8XG7xFi2beJp
6hhtcx/DefFcZzxv3RdKiruOm22ueRRqOA8/vPvNAkCFib4CKaielJahO

Bug#967986: marked as done (hfsprogs: Removal of sys/sysctl.h)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 18:18:32 +
with message-id 
and subject line Bug#967986: fixed in hfsprogs 540.1.linux3-1
has caused the Debian Bug report #967986,
regarding hfsprogs: Removal of sys/sysctl.h
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.)


-- 
967986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hfsprogs
Version: 332.25-11
Severity: important

Hello,

Version 2.32 of glibc will not ship the sysctl() function and the
 header any more. sysctl itself has been deprecated in
Linux and will be removed. This package is using it, so will start FTBFS
when we upload version 2.32 of glibc.

Samuel
--- End Message ---
--- Begin Message ---
Source: hfsprogs
Source-Version: 540.1.linux3-1
Done: John Paul Adrian Glaubitz 

We believe that the bug you reported is fixed in the latest version of
hfsprogs, 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.
John Paul Adrian Glaubitz  (supplier of updated 
hfsprogs 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: Sun, 01 Nov 2020 18:56:49 +0100
Source: hfsprogs
Architecture: source
Version: 540.1.linux3-1
Distribution: unstable
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Closes: 765104 958522 967986
Changes:
 hfsprogs (540.1.linux3-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #765104)
   * Remove all Debian patches for the previous upstream version
   * Set myself as maintainer in debian/control (Closes: #958522)
   * Strip unnecessary CFLAGS and LDFLAGS from debian/rules
   * Remove unnecessary override_dh_auto_build from debian/rules
   * Add uuid-dev to Build-Depends in debian/control
   * Remove installation of hfsbootdata.img from debian/rules
   * Update debhelper version to 12 and switch to debhelper-compat
   * Add patch from Fedora to allow building hfsprogs with gcc
   * Add patch from Fedora to fix FTBFS on ARM
   * Add patch from Fedora to fix FTBFS with glibc >= 2.32 (Closes: #967986)
   * Add patch to replace $(PWD) with $(CURDIR) in Makefile
   * Convert debian/copyright to machine-readable format and update years
   * Add Vcs-* fields to debian/control
   * Update Homepage field in debian/control
   * Reformat debian/control to match commonly used format
   * Update Standards-Version to 4.5.0 in debian/control
Checksums-Sha1:
 c5a34ae719d5dea271b3d896df94fd2b485f54b4 1950 hfsprogs_540.1.linux3-1.dsc
 edf695e9b8d36aa7a13e976c8e19746b26dd52ec 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 8ffae2a650c0e891e42850fe83964aafe4ec8e55 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 a42ea92897b5ef6a640e82469c5d7c4257d94b18 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Checksums-Sha256:
 de22cca663e1ad470cd9dae6daddc9c07c1eb55ed7a4dd2c5976f1360acb908b 1950 
hfsprogs_540.1.linux3-1.dsc
 b01b203a97f9a3bf36a027c13ddfc59292730552e62722d690d33bd5c24f5497 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 a7f11771e650b585d4887c2cc034c3d23c2cb29fc4c76bed424486ceb954a7b2 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 885ea1e8f0eb22f99e63c25fc540b191c50b9ff5e8cb230bf01387946cc74383 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Files:
 a18ca1d0f3e69a47b0bfb19decb44137 1950 otherosfs optional 
hfsprogs_540.1.linux3-1.dsc
 0435afc389b919027b69616ad1b05709 411205 otherosfs optional 
hfsprogs_540.1.linux3.orig.tar.gz
 c7b05fade62898d4d9fef6f2e02b1c23 15428 otherosfs optional 
hfsprogs_540.1.linux3-1.debian.tar.xz
 280157a006d22fda13d5b49fce2d3769 6308 otherosfs optional 
hfsprogs_540.1.linux3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl+e920ACgkQdCY7N/W1
+RM/AA//V23actm2KU225htt3GE555tFxSSn2pbUcwKKjhDxUlx/8d4hNithnY+j
ukdj8xzA1XAoRleeLsQkpTC6DoMAWUISfZyNZ5/oU5BFTTZea2yfJuvCetb7F+Cq
mI654XoxqX1ScbnJtM0Rm5pbJxbvOOGNQaCCToIS/s51ZaizNfJjOu6OsLUZkK8p
P6kJUqc6qy6tKPP7xTBTxaQf/rL96IE7ClFP5Two59Rwjwg1et5C8XG7xFi2beJp
6hhtcx/DefFcZzxv3RdKiruOm22ueRRqOA8/vPvNAkCFib4CKaielJahOke/LTE+
KxstUmrzq7tEQxgTbbSKP0mcxPP4HZVoNyZ/++LvTYD/HdjLJ5SEZGu

Bug#958522: marked as done (ITA: hfsprogs -- mkfs and fsck for HFS and HFS+ file systems)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 18:18:32 +
with message-id 
and subject line Bug#958522: fixed in hfsprogs 540.1.linux3-1
has caused the Debian Bug report #958522,
regarding ITA: hfsprogs -- mkfs and fsck for HFS and HFS+ file systems
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.)


-- 
958522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal
User: debian-powe...@lists.debian.org
Usertags: powerpc ppc64

Hello!

I'm orphaning the hfsprogs package with the intention to adopt it.

The package hasn't been updated for a long time by the current
maintainer and has a couple of issues that need resolving.

He has also agreed on handing over maintenance [1].

Thanks,
Adrian

> [1] https://lists.debian.org/debian-powerpc/2020/04/msg00197.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: hfsprogs
Source-Version: 540.1.linux3-1
Done: John Paul Adrian Glaubitz 

We believe that the bug you reported is fixed in the latest version of
hfsprogs, 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 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
hfsprogs 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: Sun, 01 Nov 2020 18:56:49 +0100
Source: hfsprogs
Architecture: source
Version: 540.1.linux3-1
Distribution: unstable
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Closes: 765104 958522 967986
Changes:
 hfsprogs (540.1.linux3-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #765104)
   * Remove all Debian patches for the previous upstream version
   * Set myself as maintainer in debian/control (Closes: #958522)
   * Strip unnecessary CFLAGS and LDFLAGS from debian/rules
   * Remove unnecessary override_dh_auto_build from debian/rules
   * Add uuid-dev to Build-Depends in debian/control
   * Remove installation of hfsbootdata.img from debian/rules
   * Update debhelper version to 12 and switch to debhelper-compat
   * Add patch from Fedora to allow building hfsprogs with gcc
   * Add patch from Fedora to fix FTBFS on ARM
   * Add patch from Fedora to fix FTBFS with glibc >= 2.32 (Closes: #967986)
   * Add patch to replace $(PWD) with $(CURDIR) in Makefile
   * Convert debian/copyright to machine-readable format and update years
   * Add Vcs-* fields to debian/control
   * Update Homepage field in debian/control
   * Reformat debian/control to match commonly used format
   * Update Standards-Version to 4.5.0 in debian/control
Checksums-Sha1:
 c5a34ae719d5dea271b3d896df94fd2b485f54b4 1950 hfsprogs_540.1.linux3-1.dsc
 edf695e9b8d36aa7a13e976c8e19746b26dd52ec 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 8ffae2a650c0e891e42850fe83964aafe4ec8e55 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 a42ea92897b5ef6a640e82469c5d7c4257d94b18 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Checksums-Sha256:
 de22cca663e1ad470cd9dae6daddc9c07c1eb55ed7a4dd2c5976f1360acb908b 1950 
hfsprogs_540.1.linux3-1.dsc
 b01b203a97f9a3bf36a027c13ddfc59292730552e62722d690d33bd5c24f5497 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 a7f11771e650b585d4887c2cc034c3d23c2cb29fc4c76bed424486ceb954a7b2 15428 
hfsprogs_540.1.linux3-1.debian.tar.xz
 885ea1e8f0eb22f99e63c25fc540b191c50b9ff5e8cb230bf01387946cc74383 6308 
hfsprogs_540.1.linux3-1_amd64.buildinfo
Files:
 a18ca1d0f3e69a47b0bfb19decb44137 1950 otherosfs optional 
hfsprogs_540.1.linux3-1.dsc
 0435afc389b919027b69616ad1b05709 411205 otherosfs optional 
hfsprogs_540.1.linux3.orig.tar.gz
 c7b05fade62898d4d9fef6f2e02b1c23 15428 otherosfs optional 
hfsprogs_540.1.linux3-1.debian.tar.xz
 280157a006d22fda13d5b49fce2d3769 6308 otherosfs optional 
hfsprogs_540.1.linux3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAl+e920ACgkQdCY7N/W1
+RM/AA//V23actm

Bug#961710: marked as done (rr: Is it possible to reintroduce rr on i386 if depending on sse2-support)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 17:34:37 +
with message-id 
and subject line Bug#961710: fixed in rr 5.4.0-1~exp1
has caused the Debian Bug report #961710,
regarding rr: Is it possible to reintroduce rr on i386 if depending on 
sse2-support
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.)


-- 
961710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rr
Version: 5.2.0-4
Severity: wishlist

Dear Maintainer,
in bug #915337 the i386 support got dropped because of
the i386 baseline violation.

Would it be enough to depend just on i386 on
the package sse2-support.

That way the user gets an error when attempting to install
on an non-sse-enabled system.

There was a discussion in [1] that I think matches
the situation here too. There the result, as far as I see,
was that it would be sufficient to have the user informed of
the problem instead of letting the process crash.

Kind regards,
Bernhard

[1] https://lists.debian.org/debian-devel/2014/09/msg00666.html




-- System Information:
Debian Release: 10.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-9-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rr depends on:
ii  libc6   2.28-10
ii  libcapnp-0.6.1  0.6.1-1
ii  libgcc1 1:8.3.0-6
ii  libstdc++6  8.3.0-6

rr recommends no packages.

rr suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: rr
Source-Version: 5.4.0-1~exp1
Done: Stephen Kitt 

We believe that the bug you reported is fixed in the latest version of
rr, 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 961...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated rr 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: Sun, 01 Nov 2020 18:12:33 +0100
Source: rr
Binary: rr rr-dbgsym
Architecture: source i386
Version: 5.4.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 rr - application execution recorder, player and debugger
Closes: 961710 961926
Changes:
 rr (5.4.0-1~exp1) experimental; urgency=medium
 .
   * New upstream release, restoring i386 support and introducing support
 for some Zen CPUs and some AArch64 platforms.
 Closes: #961710, #961926.
   * Switch to debhelper compatibility level 13.
Checksums-Sha1:
 3227d6635e209fe1cc1f2ae73c248a472a19d142 1927 rr_5.4.0-1~exp1.dsc
 b4716dd10b01ae4b8d35ae08f4f67fc46f0693d9 1434820 rr_5.4.0.orig.tar.gz
 ce61ecb96fb23331cd855f3960bd6a36acedc820 9412 rr_5.4.0-1~exp1.debian.tar.xz
 c86c760b5379826441e88c787f66a172e004e0aa 14747884 
rr-dbgsym_5.4.0-1~exp1_i386.deb
 4e8546faeb833aa26e96bf5324295e57faf834ee 8646 rr_5.4.0-1~exp1_i386.buildinfo
 17eff631623f74058559eadcc670637068ef837e 1267992 rr_5.4.0-1~exp1_i386.deb
Checksums-Sha256:
 54e9e5ccd1873a5bcc53a3fcb2fd668e9cdb613ca288b6bbe8320e354f91908f 1927 
rr_5.4.0-1~exp1.dsc
 ba3f604b76a1e917055efeac60c51148bcb578e64a55ceddad8b1a6f2740717e 1434820 
rr_5.4.0.orig.tar.gz
 04530f346d521d4fd70839f995e5540b3f85fbc81c696fdfa4c0d484182fc1fd 9412 
rr_5.4.0-1~exp1.debian.tar.xz
 f6cd9fe5614bbdbd585845b49d8af41de910afb2801c49d8ddd5d7cefc0abdef 14747884 
rr-dbgsym_5.4.0-1~exp1_i386.deb
 2fdf15e81881fdc7ff853af394a1d51be44ba06d726821dbc5d598e6a4efd3c3 8646 
rr_5.4.0-1~exp1_i386.buildinfo
 2be1e12409fbe9aad21320110dab453c94fbf9a2d283b4df272dfc469edd90af 1267992 
rr_5.4.0-1~exp1_i386.deb
Files:
 c0571772587b6759e2f6a240f287e3ad 1927 devel optional rr_5.4.0-1~exp1.dsc
 826ff8d4fb51eee79b891774c129f350 1434820 devel optional rr_5.4.0.orig.tar.gz
 787e5f11857b6d54151f0b59aa0c1947 9412 devel optional 
rr_5.4.0-1~exp1.debian.tar.xz
 9d5aee38567d2525c3b68d5f0cf0c406 14747884 debug optional 
rr-dbgsym_5.4.0-1~exp1_i386.deb

Bug#961926: marked as done (rr: record fails on i386)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 17:34:37 +
with message-id 
and subject line Bug#961926: fixed in rr 5.4.0-1~exp1
has caused the Debian Bug report #961926,
regarding rr: record fails on i386
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.)


-- 
961926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rr
Version: 5.3.0-3
Severity: normal

Dear Maintainer,
thank you for building i386 again.

Unfortunately I found recording not working in a small test [1].

A git bisect led to a helper function introduced by upstream in [2].
This helper uses a function parameter of type off_t.
But the pwrite64 from glibc uses off64_t.
Therefore offset values with the highest bit set get incorrectly
converted to the 64 bit type, e.g.: 0xb622 -> 0xb622
Therefore the write fails and rr stops.

Attached patch makes rr work on i386 and passing most tests
in my test VM, except [3]. Have not tested for side effects at amd64.

I am going to try to forward this to upstream too,
will update this bug then.

Kind regards,
Bernhard




[1]
$ /usr/bin/rr record /bin/ls
rr: Saving execution to trace directory `/home/benutzer/.local/share/rr/ls-0'.
[FATAL /build/rr-wu2MDM/rr-5.3.0/src/AddressSpace.cc:320:map_rr_page()] 
 (task 6291 (rec:6291) at time 14)
 -> Assertion `child_fd == -EACCES' failed to hold. Unexpected error mapping 
rr_page
Tail of trace dump:
[FATAL /build/rr-wu2MDM/rr-5.3.0/src/DumpCommand.cc:180:dump_events_matching()] 
TraceTaskEvent times non-increasing
=== Start rr backtrace:
/usr/bin/rr(_ZN2rr13dump_rr_stackEv+0x43)[0x6489e3]
/usr/bin/rr(_ZN2rr15notifying_abortEv+0x5a)[0x648a8a]
/usr/bin/rr(_ZN2rr12FatalOstreamD1Ev+0x53)[0x569723]
/usr/bin/rr(+0x6f175)[0x521175]
/usr/bin/rr(_ZN2rr4dumpERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_9DumpFlagsERKSt6vectorIS5_SaIS5_EEP8_IO_FILE+0x8d)[0x521c5d]
/usr/bin/rr(+0xb7985)[0x569985]
/usr/bin/rr(_ZN2rr21EmergencyDebugOstreamD2Ev+0x81)[0x569c11]
/usr/bin/rr(_ZN2rr12AddressSpace11map_rr_pageERNS_18AutoRemoteSyscallsE+0x8b8)[0x50d188]
/usr/bin/rr(_ZN2rr12AddressSpace17post_exec_syscallEPNS_4TaskE+0x88)[0x50f7b8]
/usr/bin/rr(_ZN2rr4Task17post_exec_syscallEv+0x46)[0x625b26]
/usr/bin/rr(+0xf989f)[0x5ab89f]
/usr/bin/rr(+0x114183)[0x5c6183]
/usr/bin/rr(_ZN2rr19rec_process_syscallEPNS_10RecordTaskE+0xa3)[0x5cd1c3]
/usr/bin/rr(_ZN2rr13RecordSession21syscall_state_changedEPNS_10RecordTaskEPNS0_9StepStateE+0xe5d)[0x59143d]
/usr/bin/rr(_ZN2rr13RecordSession11record_stepEv+0x45b)[0x5978bb]
/usr/bin/rr(_ZN2rr13RecordCommand3runERSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EE+0xf68)[0x58c6d8]
/usr/bin/rr(main+0x298)[0x5054a8]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0xb791bef1]
/usr/bin/rr(_start+0x31)[0x505611]
=== End rr backtrace
Abgebrochen



[2] 
https://github.com/mozilla/rr/commit/531062cca8670f13ae99de3322df650e43269784



[3]
98% tests passed, 20 tests failed out of 1157
Total Test time (real) = 3370.80 sec
The following tests FAILED:
440 - quotactl (Failed)
441 - quotactl-no-syscallbuf (Failed)
512 - sem (Failed)
513 - sem-no-syscallbuf (Failed)
534 - shm (Failed)
535 - shm-no-syscallbuf (Failed)
536 - shm_unmap (Failed)
537 - shm_unmap-no-syscallbuf (Failed)
708 - std_random (Failed)
709 - std_random-no-syscallbuf (Failed)
962 - vsyscall_reverse_next (Failed)
963 - vsyscall_reverse_next-no-syscallbuf (Failed)
1110 - shm_checkpoint (Failed)
 - shm_checkpoint-no-syscallbuf (Failed)
1116 - signal_stop (Failed)
1117 - signal_stop-no-syscallbuf (Failed)
1118 - signal_checkpoint (Failed)
1119 - signal_checkpoint-no-syscallbuf (Failed)
1132 - step_signal (Failed)
1133 - step_signal-no-syscallbuf (Failed)
Errors while running CTest




-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.6.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rr depends on:
ii  libc6   2.30-8
ii  libcapnp-0.7.0  0.7.0-6
ii  libgcc-s1   10.1.0-3
ii  libstdc++6  10.1.0-3
ii  python3 3.8.2-3
ii  sse2-support5

rr recommends no packages.

rr suggests no pa

Bug#928074: marked as done (ITP: nim-docopt -- command line interface generator and arg parser)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 17:00:08 +
with message-id 
and subject line Bug#928074: fixed in nim-docopt 0.6.8-1
has caused the Debian Bug report #928074,
regarding ITP: nim-docopt -- command line interface generator and arg parser
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.)


-- 
928074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller 

* Package name: nim-docopt
* URL : https://github.com/docopt/docopt.nim/
* License : MIT
  Programming Lang: nim
  Description : command line interface generator and arg parser

The package is to be team-maintained on salsa.d.o/nim-team/nim-docopt
--- End Message ---
--- Begin Message ---
Source: nim-docopt
Source-Version: 0.6.8-1
Done: Steffen Moeller 

We believe that the bug you reported is fixed in the latest version of
nim-docopt, 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 928...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steffen Moeller  (supplier of updated nim-docopt 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, 31 Oct 2020 19:48:47 +0100
Source: nim-docopt
Binary: nim-docopt-dev
Architecture: source all
Version: 0.6.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Nim Team 
Changed-By: Steffen Moeller 
Description:
 nim-docopt-dev - command line interface generator and arg parser
Closes: 928074
Changes:
 nim-docopt (0.6.8-1) unstable; urgency=medium
 .
   * Initial release (Closes: #928074)
 .
   * Reupload with corrected maintainer address - thanks, Ansgar!
Checksums-Sha1:
 b8333543b130ce70364937914a62c20d0cdc8c86 2036 nim-docopt_0.6.8-1.dsc
 2b589c44ba635acae3e78cb06bf4888404d3 15769 nim-docopt_0.6.8.orig.tar.gz
 79b6be5cd2facd17af4643f2dae7b5eb21a5bd20 2228 nim-docopt_0.6.8-1.debian.tar.xz
 907dd50123910832cd1c5ae0c9dd41813bd258c7 10340 nim-docopt-dev_0.6.8-1_all.deb
 18fdb7ac5914efc4635808593d11734b93777a28 6448 
nim-docopt_0.6.8-1_amd64.buildinfo
Checksums-Sha256:
 ad8fa211c8a62507900f497589f062e5738ba69ed382c9a0b0c57c35994f5bcc 2036 
nim-docopt_0.6.8-1.dsc
 5ee208fb9bc71a52303cdade8b428bdfeb29ab7c2b22c59942a151e5dd558fa2 15769 
nim-docopt_0.6.8.orig.tar.gz
 817c9de1092e6ad86a109a36a7860f41eab3a2fe1a78723cf1a81d3c2542d537 2228 
nim-docopt_0.6.8-1.debian.tar.xz
 7bb8af4583759b11f792340033a4a691a2e83d8def58789919c584f5ba2a06d7 10340 
nim-docopt-dev_0.6.8-1_all.deb
 91bf8d873ece6c4fa24be037f5a7df40dd55f7acb871aee48e503c54e168d635 6448 
nim-docopt_0.6.8-1_amd64.buildinfo
Files:
 5927965768b50c89f36091f6ca9d1202 2036 libs optional nim-docopt_0.6.8-1.dsc
 420e9ab53e1241d0f8a66e43d06cbf03 15769 libs optional 
nim-docopt_0.6.8.orig.tar.gz
 6feb222779544a9b2412aed2b0e12bea 2228 libs optional 
nim-docopt_0.6.8-1.debian.tar.xz
 134291a44c8d75fd17f064e3b2133b00 10340 libs optional 
nim-docopt-dev_0.6.8-1_all.deb
 c88bc9dba5fd13345cf8905ea8b2d9ff 6448 libs optional 
nim-docopt_0.6.8-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl+dxfUTHG1vZWxsZXJA
ZGViaWFuLm9yZwAKCRAv2L7awCDu0TG9D/4w6Mt2pjFuCSd1amcXQ2NFxlYl9Kpt
3tOkbJMHVJ3jTF1i5eOau5421YJIVB98Ut45Ul0xTQbZl3YtRMZZeVEFWVxBSOMe
QjqfGvDAWTEsJJfYGPbP/vkA7P9l20+pKmAfslNFOHqARz+FK2X2HiehORilub95
nKH1o3GdqLnHqymKsqGplF2IB0EYee5F4U8YymD4claDJ831PhOyjk8SOKGh8F/p
MRhQWSWpJMsou9Z1CwavUGEGp5cddROd7rErifUHi+qPRG1xIZuhESBKRvsw3BBY
cAAbk3sEqS/Xzm8hhcH+BsWhdRghQQDwZD28+dLxTWlh+1fQ5lg2If9OXRnMU73r
WcuMlo2nFk+YXTJPA24EpReS03a6t3VHh+JVlvnUvZuFqnCpAB7UzZzKi9viEQEz
FAhRTYnNkyAHdvYpJPmDyNhdnfLnbMxbEMfJ7L386edOaHEMl+bnPpr356swDi0y
M5OEbdkf4qSLEd9JC1WPwMi19VZfeuW/odFk73h0DczaHyWcqqpP3Q8z4XMtJjxH
IFrHKy5d6y3EgIUH+auYfJTBdOy2dRG3OOBggOGIr4RQWUL48IlKBw6YKWDQ1qtH
FooZsYAAxDpq35LzimSSGvpZA3XmTShPhp0Zp2KKq5IHSK3GsCqeCTsOnG5PiwPB
wp140PGDFYphww==
=xwLD
-END PGP SIGNATURE End Message ---

Bug#973512: marked as done (RuntimeError: dictionary keys changed during iteration)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:34:50 +
with message-id 
and subject line Bug#973512: fixed in onioncircuits 0.7-2
has caused the Debian Bug report #973512,
regarding RuntimeError: dictionary keys changed during iteration
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.)


-- 
973512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: onioncircuits
Version: 0.7-1
Severity: normal

Dear Maintainer,

Thank you for maintaining onioncircuits.

Much like the tenet of patron privacy that public
libraries hold dear, I love the ideal of voters
using TOR to privately and safely explore new
ideas without fear of repercussion from neighbors
or employers, and ultimately become a better
informed electorate that can actually rule itself
wisely enough to successfully sustain a democratic
form of government.

The main reason I'm writing is to suggest
improving the dependency info for the
onioncircuits package to specify at least version
1.8.0-2 of the python3-stem package.

It currently accepts any version, but when I tried
1.7.1-1, onioncircuits failed with

Traceback (most recent call last):
  File "/usr/bin/onioncircuits", line 668, in 
app = OnionCircuitsApplication()
  File "/usr/bin/onioncircuits", line 644, in __init__
self.connect_controller()
  File "/usr/bin/onioncircuits", line 658, in connect_controller
self.controller = stem.connection.connect(**connect_args)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 291, in 
connect
return _connect_auth(control_connection, password, password_prompt, 
chroot_path, controller)
  File "/usr/lib/python3/dist-packages/stem/connection.py", line 375, in 
_connect_auth
return controller(control_socket, is_authenticated = True)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1057, in 
__init__
super(Controller, self).__init__(control_socket, is_authenticated)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 585, in 
__init__
self._post_authentication()
  File "/usr/lib/python3/dist-packages/stem/control.py", line 3902, in 
_post_authentication
owning_pid = self.get_conf('__OwningControllerProcess', None)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2170, in 
get_conf
entries = self.get_conf_map(param, default, multiple)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 2273, in 
get_conf_map
for key in reply:
RuntimeError: dictionary keys changed during iteration


Doing 

root$ aptitude install python3-stem

fixed it.

Thanks, and kind regards,
Kingsley

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages onioncircuits depends on:
ii  gir1.2-glib-2.01.62.0-5
ii  gir1.2-gtk-3.0 3.24.13-1
ii  python3-gi 3.34.0-6
ii  python3-pkg-resources  41.1.0-1
ii  python3-pycountry  20.7.3+ds1-1
ii  python3-stem   1.8.0-2
pn  python3:any

onioncircuits recommends no packages.

Versions of packages onioncircuits suggests:
ii  tor-geoipdb  0.4.2.7-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: onioncircuits
Source-Version: 0.7-2
Done: Sascha Steinbiss 

We believe that the bug you reported is fixed in the latest version of
onioncircuits, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sascha Steinbiss  (supplier of updated onioncircuits 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: Sun, 01 Nov 2020 15:20:49 +0100
Source: onioncircuits
Architecture: source
Version: 0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Chan

Bug#966730: marked as done (dipy: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#936400: fixed in dipy 1.2.0-1
has caused the Debian Bug report #936400,
regarding dipy: 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.)


-- 
936400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dipy
Version: 0.13.0-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 ---
Source: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nibabel (>= 3.0.0)
   * Make Debian Med team maintainer and move package to med-team on Salsa
   * Remove debian/gbp.conf since repository now follows default layout
 as described in policy
   * Remove unused debian/blends file
   * Remove outdated debian/README.source
   * debhelper-compat 13 (routine-update)
   * Remove debian/cythonized-files
   * (Build-)Depends: pandas
Checksums-Sha1:
 0e7a71b3e6490a08d5d6da599577b583add0acf4 2405 dipy_1.2.0-1.dsc
 c26a5d6dee40b61b2d0d3f985f8e5f8535a4d106 6064158 dipy_1.2.0.orig.tar.gz
 a1dbafab699c0ea6b912731d046be11d00b65108 6640 dipy_1.2.0-1.debian.tar.xz
 ae47ae4dda772bcd223e1daf3466a270db0d69f8 11658 dipy_1.2.0-1_amd64.buildinfo
 2d58bd66b14a0ef4b20f4faa4e3994643573fd6a 2210732 
python-dipy-doc_1.2.0-1_all.deb
 0923db9a146bd52f8fd79311856786b498f4537f 8776 
python3-dipy-lib_1.2.0-1_amd64.deb
 58d514fd30d3215519465d0a2501970506248d03 3102988 python3-dipy_1.2.0-1_all.deb
Checksums-Sha256:
 f19c0dea924d1533f118fe2fa6201221419cb02d95f2f4d768486804f093d8e3 2405 
dipy_1.2.0-1.dsc
 6c2123d8001aab88991a41ff8023cb711cc044d88c9f16e687f4ef1bb00980ed 6064158 
dipy_1.2.0.orig.tar.gz
 2946b22d173fb1237f623fad2f10b9bc86055672f68d546dbc0c6e735d178cf6 6640 
dipy_1.2.0-1.debian.tar.xz
 3fde861a

Bug#966730: marked as done (dipy: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#942973: fixed in dipy 1.2.0-1
has caused the Debian Bug report #942973,
regarding dipy: 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.)


-- 
942973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dipy
Version: 0.13.0-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 ---
Source: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nibabel (>= 3.0.0)
   * Make Debian Med team maintainer and move package to med-team on Salsa
   * Remove debian/gbp.conf since repository now follows default layout
 as described in policy
   * Remove unused debian/blends file
   * Remove outdated debian/README.source
   * debhelper-compat 13 (routine-update)
   * Remove debian/cythonized-files
   * (Build-)Depends: pandas
Checksums-Sha1:
 0e7a71b3e6490a08d5d6da599577b583add0acf4 2405 dipy_1.2.0-1.dsc
 c26a5d6dee40b61b2d0d3f985f8e5f8535a4d106 6064158 dipy_1.2.0.orig.tar.gz
 a1dbafab699c0ea6b912731d046be11d00b65108 6640 dipy_1.2.0-1.debian.tar.xz
 ae47ae4dda772bcd223e1daf3466a270db0d69f8 11658 dipy_1.2.0-1_amd64.buildinfo
 2d58bd66b14a0ef4b20f4faa4e3994643573fd6a 2210732 
python-dipy-doc_1.2.0-1_all.deb
 0923db9a146bd52f8fd79311856786b498f4537f 8776 
python3-dipy-lib_1.2.0-1_amd64.deb
 58d514fd30d3215519465d0a2501970506248d03 3102988 python3-dipy_1.2.0-1_all.deb
Checksums-Sha256:
 f19c0dea924d1533f118fe2fa6201221419cb02d95f2f4d768486804f093d8e3 2405 
dipy_1.2.0-1.dsc
 6c2123d8001aab88991a41ff8023cb711cc044d88c9f16e687f4ef1bb00980ed 6064158 
dipy_1.2.0.orig.tar.gz
 2946b22d173fb1237f623fad2f10b9bc86055672f68d546dbc0c6e735d178cf6 6640 
dipy_1.2.0-1.debian.tar.xz
 3fde861a

Bug#973531: marked as done (ITP: sakia -- client for the duniter crypto-currency project)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:11 +
with message-id 
and subject line Bug#973531: fixed in sakia 0.53.1-1
has caused the Debian Bug report #973531,
regarding ITP: sakia -- client for the duniter crypto-currency project
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.)


-- 
973531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: sakia
  Version : 0.53.1
  Upstream Author : inso 
* URL : https://git.duniter.org/clients/python/sakia
* License : GPL-3
  Programming Lang: Python
  Description : client for the duniter crypto-currency project

 Sakia is a Python3 and PyQt5 client for the duniter project.
 .
 Duniter (previously uCoin) is a libre software
 allowing to create a new kind of P2P crypto-currencies
 based on individuals and Universal Dividend.

This package will be maintained in the Debian Cryptocoin Team.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+eoAsACgkQLHwxRsGg
ASG1EBAArtGkJVNzSZeNqy+waQhBxmZj+fztL4gcfOiG22Qd3Jd+orJK3j0zAdfw
skgjb1KP54NGs74bhCtBa3N1vHu2Ig8BhinW/VrqBxFUL/MM64QpJ5PVrHZFttQT
9Y4xKR6bjfJHZp66V2voGs7nfUYEmkdTHIeXJ5nhM7QEcNNf+xLvsOpW8x1lXHid
ccAilhylkK8RWMYVW5w9jgz8bcikIjUaEXt/9lLkhbx+2fwtUeTG3Zc07ow1w9Yr
qhY+kiNFei+hAKCjR/vc4opE7+7nd5Qm4jf0YBVlyPW9fVJ6Wke29w/BeLML9vPp
iPnLm3uny9OD+Vejo8bTxUaCogrA5+O9/bl09zx13cXfeuagXzeMqTEyuLDz2zVX
5Wibs6r2oiz9xBr7nn/SZp1Oi6TJf5lBZQ2AhpS8mVqM4V2/lUEjgkA6m2J7OAvC
9RoU53LStc56APpgpBA0WaANNEFcIw2Y4jz6wQ8E5WHSUT3dmayqnlUn3l7yVTKY
/rry7P1ZY4l+vh0aqOOtboAu7T6EX/QCqe/JnwHADRv+2oIb2sMdGT/BYqKUB9gw
/u/xvbl5Y1UV/is8dfKKz17QNOiWHUbdhTiiY6RRTyWWv/ReYvPi8hE6CzeSumOP
KthLNyOzyYPsjzFIK3ZPSdt19V/gqTo763H9+U2J7QNkSIhkjco=
=sop8
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: sakia
Source-Version: 0.53.1-1
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
sakia, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated sakia 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: Sun, 01 Nov 2020 12:51:14 +0100
Source: sakia
Binary: sakia
Architecture: source all
Version: 0.53.1-1
Distribution: experimental
Urgency: low
Maintainer: Debian Cryptocoin Team 
Changed-By: Jonas Smedegaard 
Description:
 sakia  - client for the duniter crypto-currency project
Closes: 973531
Changes:
 sakia (0.53.1-1) experimental; urgency=low
 .
   * initial release;
 closes: bug#973531
Checksums-Sha1:
 3fbccbba4d0aaf0b7f23fed4fd1f9f2a491635b6 2021 sakia_0.53.1-1.dsc
 f750f48be8e369cbcd8562ebdf9911fbbccdd082 1010233 sakia_0.53.1.orig.tar.bz2
 259ffb7a22af50bd3399890adf4e96124a9dfe68 6636 sakia_0.53.1-1.debian.tar.xz
 b99385631428f79fc3bb054d7769681215847daf 285384 sakia_0.53.1-1_all.deb
 a91a7bee5dbd7d7e25501ba4f5e63cd27fe8dc9d 10281 sakia_0.53.1-1_amd64.buildinfo
Checksums-Sha256:
 ee6b7bc3bf198e844910ae496480acd99fc6e79ac7511e65446e5604d2db3af5 2021 
sakia_0.53.1-1.dsc
 94bcc64975e27a0146fa8d735ba0a93e7172dbaed7d7a8dfdf22b49903d3042b 1010233 
sakia_0.53.1.orig.tar.bz2
 a2c235c456638b28dc093a6bc5640cfaa76a313ef911a42e916d6c4009362509 6636 
sakia_0.53.1-1.debian.tar.xz
 b81569ec95b7a7c809a982ede94ea03caf4bfc699700b499d9693d776a39589d 285384 
sakia_0.53.1-1_all.deb
 1e1329f3f6d352a52d56d1ab24b7fc0b49e02691c00fd06282f475d2ec4fbef6 10281 
sakia_0.53.1-1_amd64.buildinfo
Files:
 0bbbd569b28839c19c87698ce0aa3d13 2021 utils optional sakia_0.53.1-1.dsc
 7afbb9bc6c2e527d1e399f68b3956627 1010233 utils optional 
sakia_0.53.1.orig.tar.bz2
 30903953699470714a149bade763ca51 6636 utils optional 
sakia_0.53.1-1.debian.tar.xz
 907e10c3ee1de6bec58244f5dd07c3e3 285384 utils optional sakia_0.53.1-1_all.deb
 4b35cace14a7472ddd100116d7635552 10281 utils optional 
sakia_0.53.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+P

Bug#971079: marked as done (ITP: gap-aclib -- Almost Crystallographic Groups - A Library and Algorithms)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:10 +
with message-id 
and subject line Bug#971079: fixed in gap-aclib 1.3.2-1
has caused the Debian Bug report #971079,
regarding ITP: gap-aclib -- Almost Crystallographic Groups - A Library and 
Algorithms
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.)


-- 
971079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Joachim Zobel 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: gap-aclib
  Version : 1.3.2
  Upstream Author : Karel Dekimpe , Bettina Eick

* URL : http://www.gap-system.org/Packages/aclib.html
* License : Artistic-2
  Programming Lang: GAP 4
  Description : Almost Crystallographic Groups - A Library and Algorithms

The AClib package contains a library of almost crystallographic groups and a
some algorithms to compute with these groups. A group is called almost
crystallographic if it is finitely generated nilpotent-by-finite and has no
non-trivial finite normal subgroups. Further, an almost crystallographic
group is called almost Bieberbach if it is torsion-free. The almost
crystallographic groups of Hirsch length 3 and a part of the almost
cyrstallographic groups of Hirsch length 4 have been classified by Dekimpe.
This classification includes all almost Bieberbach groups of Hirsch lengths 3
or 4. The AClib package gives access to this classification; that is, the
package contains this library of groups in a computationally useful form. The
groups in this library are available in two different representations. First,
each of the groups of Hirsch length 3 or 4 has a rational matrix
representation of dimension 4 or 5, respectively, and such representations
are available in this package. Secondly, all the groups in this libraray are
(infinite) polycyclic groups and the package also incorporates polycyclic
presentations for them. The polycyclic presentations can be used to compute
with the given groups using the methods of the Polycyclic package.

I am packaging this because it is a dependency for gap-hap (see Bug#968545).
--- End Message ---
--- Begin Message ---
Source: gap-aclib
Source-Version: 1.3.2-1
Done: Joachim Zobel 

We believe that the bug you reported is fixed in the latest version of
gap-aclib, 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.
Joachim Zobel  (supplier of updated gap-aclib 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: Mon, 21 Sep 2020 06:54:25 +0200
Source: gap-aclib
Binary: gap-aclib
Architecture: source all
Version: 1.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Joachim Zobel 
Changed-By: Joachim Zobel 
Description:
 gap-aclib  - GAP AClib - Almost Crystallographic Groups - A Library and Algori
Closes: 971079
Changes:
 gap-aclib (1.3.2-1) unstable; urgency=low
 .
   [ Joachim Zobel ]
   * Initial Release (Closes: #971079).
   * Created with gap2deb
   * Corrected license (Artistic-2)
   * Patch doc-doc2etc adapts to gap directory structure
   * Patch doc-sixdot to adapt to build outside of the gap tree
   * Adapted doc/Makefile
   * Added another link
   * Added tex build dependencies
Checksums-Sha1:
 50b795496b0837465ed975e1103ed70dac350565 1847 gap-aclib_1.3.2-1.dsc
 2acce2e8ad0f1af522bcac438b7721aad3ff0e37 262820 gap-aclib_1.3.2.orig.tar.gz
 c4620c5d9f1f14360b3feb325bc1f9a8cced0727 6236 gap-aclib_1.3.2-1.debian.tar.xz
 5c6ae038d0eefeaf1a4517ca0fc985c52bd34d3f 229248 gap-aclib_1.3.2-1_all.deb
 3131403660546c60594872597bb438b1d35162e5 8028 gap-aclib_1.3.2-1_amd64.buildinfo
Checksums-Sha256:
 66f587f6dee0ac8403022624a822d748762c8ca5a2cc96c31a754e61c7b75460 1847 
gap-aclib_1.3.2-1.dsc
 28e18eb752c848e1d77ae8323bab56020eff63490eb37741e5480e2842ad862a 262820 
gap-aclib_1.3.2.orig.tar.gz
 8c581763b53ef952a7acfe1dcaf9b8c39da57944673988a8cae277f4c6891cc9 6236 
gap-aclib_1.3.2-1.debian.tar.xz
 ba38c409c573007a9ccaedf35026b670e25cabaaf9729c94a56744c9ee0bc1ba 229248 
gap-aclib_1.3.2-1_all.deb
 b578e5c210d8af6c6d9dd780

Bug#936400: marked as done (dipy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#936400: fixed in dipy 1.2.0-1
has caused the Debian Bug report #936400,
regarding dipy: 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.)


-- 
936400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dipy
Version: 0.14.0-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:dipy

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: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nib

Bug#942973: marked as done (dipy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#942973: fixed in dipy 1.2.0-1
has caused the Debian Bug report #942973,
regarding dipy: 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.)


-- 
942973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 0.14.0-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_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: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nibabel (>= 3.0.0)
   * Make Debian Med team maintainer and move package to med-team on Salsa
   * Remove debian/gbp.conf since repository now follows default layo

Bug#923657: marked as done (dipy: do not Build-Depends: python-sphinx)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#923657: fixed in dipy 1.2.0-1
has caused the Debian Bug report #923657,
regarding dipy: do not Build-Depends: python-sphinx
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.)


-- 
923657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 0.14.0-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

dipy cannot be cross built, because a number of its Build-Depends are
not satisfiable. One of them is python-sphinx. Closer inspection reveals
that python-sphinx does not have to be in Build-Depends, because it is
only needed for building the documentation, which is shipped in an
Architecture: all package. The attached patch moves python-sphinx to
Build-Depends-Indep. In the process, the python-dipy-doc package will no
longer be built at all when the nodoc profile is active. (Formerly, it
would build an empty package.) Using reproducible builds, I verified
that python-dipy-lib is bit-identical between an arch-only and full
build. Please consider applying the attached patch and close this bug
whenever python-sphinx is removed from Build-Depends.

Helmut
diff --minimal -Nru dipy-0.14.0/debian/changelog dipy-0.14.0/debian/changelog
--- dipy-0.14.0/debian/changelog2018-05-14 20:59:42.0 +0200
+++ dipy-0.14.0/debian/changelog2019-03-03 12:29:06.0 +0100
@@ -1,3 +1,10 @@
+dipy (0.14.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Demote python-sphinx to Build-Depends-Indep. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 03 Mar 2019 12:29:06 +0100
+
 dipy (0.14.0-1) unstable; urgency=medium
 
   * Fresh upstream release
diff --minimal -Nru dipy-0.14.0/debian/control dipy-0.14.0/debian/control
--- dipy-0.14.0/debian/control  2018-05-14 20:59:42.0 +0200
+++ dipy-0.14.0/debian/control  2019-03-03 12:28:39.0 +0100
@@ -9,11 +9,11 @@
python-scipy,
cython (>= 0.13),
python-matplotlib,
-   python-sphinx (>= 1.0),
python-numpydoc,
python-nose,
python-nibabel (>= 2.1.0),
libgomp1,
+Build-Depends-Indep: python-sphinx (>= 1.0),
 Standards-Version: 3.9.7
 Homepage: http://dipy.org
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-exppsy/dipy.git
@@ -73,6 +73,7 @@
 Section: doc
 Depends: ${misc:Depends}, libjs-jquery
 Suggests: python-dipy
+Build-Profiles: 
 Description: Python library for the analysis of diffusion MRI datasets -- 
documentation
  DIPY is a library for the analysis of diffusion magnetic resonance
  imaging data.
diff --minimal -Nru dipy-0.14.0/debian/rules dipy-0.14.0/debian/rules
--- dipy-0.14.0/debian/rules2018-05-14 20:59:42.0 +0200
+++ dipy-0.14.0/debian/rules2019-03-03 12:29:05.0 +0100
@@ -76,7 +76,7 @@
: # Prune duplicate LICENSE file
find debian/ -name LICENSE -delete
: # Only now lets build docs
-ifeq (,$(filter nodoc,$(DEB_BUILD_OPTIONS)))
+ifneq (,$(filter python-dipy-doc,$(shell dh_listpackages)))
: # Copy pregenerated examples
cp -rp doc-examples/*/examples_built/* doc/examples_built/
export PYTHONPATH=$$(/bin/ls -d 
$(INSTALL_PATH)/usr/lib/$(PYTHON)/*-packages) \
--- End Message ---
--- Begin Message ---
Source: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 923...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu

Bug#942973: marked as done (dipy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#936400: fixed in dipy 1.2.0-1
has caused the Debian Bug report #936400,
regarding dipy: 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.)


-- 
936400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 0.14.0-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_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: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nibabel (>= 3.0.0)
   * Make Debian Med team maintainer and move package to med-team on Salsa
   * Remove debian/gbp.conf since repository now follows default layo

Bug#971043: marked as done (ITP: gap-fga -- GAP FGA - Free Group Algorithms)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:10 +
with message-id 
and subject line Bug#971043: fixed in gap-fga 1.4.0-1
has caused the Debian Bug report #971043,
regarding ITP: gap-fga -- GAP FGA - Free Group Algorithms
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.)


-- 
971043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Joachim Zobel 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: gap-fga
  Version : 1.4.0
  Upstream Author : Christian Sievers 
* URL : http://www.gap-system.org/Packages/fga.html
* License : GPL2+
  Programming Lang: GAP 4
  Description : GAP FGA - Free Group Algorithms

The FGA package installs methods for computations with finitely generated
subgroups of free groups and provides a presentation for their automorphism
groups.

This is a dependency for gap-hap. I am working on packaging this (see #968545).
--- End Message ---
--- Begin Message ---
Source: gap-fga
Source-Version: 1.4.0-1
Done: Joachim Zobel 

We believe that the bug you reported is fixed in the latest version of
gap-fga, 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.
Joachim Zobel  (supplier of updated gap-fga 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, 31 Oct 2020 21:52:28 +0100
Source: gap-fga
Binary: gap-fga
Architecture: source all
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Joachim Zobel 
Changed-By: Joachim Zobel 
Description:
 gap-fga- GAP FGA - Free Group Algorithms
Closes: 971043
Changes:
 gap-fga (1.4.0-1) unstable; urgency=medium
 .
   [ Joachim Zobel ]
   * Initial release (Closes: #971043).
   * Created with gap2deb
   * Patch doc-doc2etc adapts to gap directory structure
   * Patch doc-back2sixdot replaces GAPROOT with ../../..
   * Patch doc-date sets "March 2018" in documentation
   * Adapted doc/Makefile
   * Added another link
   * Added tex build dependencies
   * Added autopkgtest
Checksums-Sha1:
 6d9471b40251c7e1190b0413ca9aaa2a49300b39 1809 gap-fga_1.4.0-1.dsc
 378de4ddaf9af439a459c875b877321c57bc2466 181480 gap-fga_1.4.0.orig.tar.gz
 82e42201b7e8224dfd68068380034fbab6397273 3728 gap-fga_1.4.0-1.debian.tar.xz
 cb4b0e0d01b2253dc8a2dd99d922056a7aacb565 172004 gap-fga_1.4.0-1_all.deb
 c8eb597f202c04a9c00c7b497a639f7ef4df54c9 7905 gap-fga_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
 d220141e2fedb7ca945eff8c8fa223bc3a72463ee4b176e6fec25d1bb9958deb 1809 
gap-fga_1.4.0-1.dsc
 69ffdb182470bf26b1ae45edcd369b96d9dc1803181dc0c2249021cc5a4a5b49 181480 
gap-fga_1.4.0.orig.tar.gz
 d3f63728ba18c37d4d8d8c6bf6485fe371ec2ca1302ce64f41211cda09e835cb 3728 
gap-fga_1.4.0-1.debian.tar.xz
 c471b5e3851b7bbfbc38020437c1990d94e7841501e7ae953a6ec714b386c7ea 172004 
gap-fga_1.4.0-1_all.deb
 6660bd3b1f9e5a583026b3b6b1a6c512ed26a624cb3a332d4ed61ff1b60a0e94 7905 
gap-fga_1.4.0-1_amd64.buildinfo
Files:
 e529603b5243000ed34894f0dc2209b5 1809 math optional gap-fga_1.4.0-1.dsc
 a5ec9d900943aaff31498d1c82598eff 181480 math optional gap-fga_1.4.0.orig.tar.gz
 966929044285382a0e466b43ae43bd88 3728 math optional 
gap-fga_1.4.0-1.debian.tar.xz
 73e61532102a6654e802034db78b726f 172004 math optional gap-fga_1.4.0-1_all.deb
 9b422333a35fe49940394d5849052b51 7905 math optional 
gap-fga_1.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQgKOpASi6dgKxFMUjw58K0Ui44cFAl+erLQACgkQjw58K0Ui
44dDlw/+IFyA/3z3T3PX5WuCaZ8RbeuzvaNBU1DkwDoExHEQ+mNr5cvc1f38ywsi
IuHQ98uVKLFVEx/TL1MU/RI1OZXfUQVOhbrY1xqq51Dbos95WsEGjBVTkkkCJlgZ
8Oasn996rgJT8dX+uG6fSpWvcKgZ+EBpcLMuWrrOUuLerK9gADeghGJRX3jiFmBl
ZrcggRDRMbDv607pggaFzTFtTy1p4I6eb/x1bXZ/Uwph8w+liD76V9FMyiOIKB2G
43lqgwf+G92tfRUfcJQPp4eLjwBtNAE2/wbbDX5I96LxusEVlb2t/c2hYI5WUs1C
e6MqasYTxJtWJ3+ztYwBJ/v0jrheClmOfvC7UoptLFTqSYjFlrggBtrCkrdYNbbQ
ORakOtAQW5L15fu3oarUIelGKP5gAW5S3onPB8MSKjctaJqoOdxuMOobeDqZ0tKE
lXqcbBpUeuujwB195cb8mm2MeVr/mqbwLaXC4OSOW7ZV3zZpXdoP3kSaUYXNMd6b
E6YJAp8LoQlJQrvbHDTPOO+X4wKo6HPX9Wbp3BMrE4eDTMF2Hcf4OSMTx5FypIAj
VepjmZcBvbg7bftCYH

Bug#936400: marked as done (dipy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#942973: fixed in dipy 1.2.0-1
has caused the Debian Bug report #942973,
regarding dipy: 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.)


-- 
942973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942973
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dipy
Version: 0.14.0-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:dipy

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: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nib

Bug#849904: marked as done (python-dipy: please add dependency “Suggests: python-dipy-doc”)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 16:00:09 +
with message-id 
and subject line Bug#849904: fixed in dipy 1.2.0-1
has caused the Debian Bug report #849904,
regarding python-dipy: please add dependency “Suggests: python-dipy-doc”
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.)


-- 
849904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dipy
Version: 0.11.0-1
Severity: minor

Dear Maintainer,

Working with the ‘dipy’ packages requires understanding how it works
and what it does.

Please set a “Suggests: python-dipy-doc” dependency to the binary
package ‘python3-dipy’, or other binary packages for which it is
appropriate.

This will present the suggestion to administrators choosing which
packages to install.

-- 
 \  “It is clear that thought is not free if the profession of |
  `\   certain opinions makes it impossible to earn a living.” |
_o__)  —Bertrand Russell, _Free Thought and Official Propaganda_, 1928 |
Ben Finney 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dipy
Source-Version: 1.2.0-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
dipy, 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 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated dipy 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, 31 Oct 2020 22:37:04 +0100
Source: dipy
Binary: python-dipy-doc python3-dipy python3-dipy-lib
Architecture: source all amd64
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 python-dipy-doc - Python library for the analysis of diffusion MRI datasets -- 
docu
 python3-dipy - Python library for the analysis of diffusion MRI datasets
 python3-dipy-lib - Python library for the analysis of diffusion MRI datasets 
-- Pyth
Closes: 849904 923657 936400 942973
Changes:
 dipy (1.2.0-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * debian/
 + provide python3 packaging
 + suggest python-dipy-doc (Closes: #849904)
 .
   [ Andreas Tille ]
   * cme fix dpkg-control
   * Standards-Version: 4.5.0 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Drop Python2 package
 Closes: #936400, #942973, #923657
   * Versioned Build-Depends: python3-nibabel (>= 3.0.0)
   * Make Debian Med team maintainer and move package to med-team on Salsa
   * Remove debian/gbp.conf since repository now follows default layout
 as described in policy
   * Remove unused debian/blends file
   * Remove outdated debian/README.source
   * debhelper-compat 13 (routine-update)
   * Remove debian/cythonized-files
   * (Build-)Depends: pandas
Checksums-Sha1:
 0e7a71b3e6490a08d5d6da599577b583add0acf4 2405 dipy_1.2.0-1.dsc
 c26a5d6dee40b61b2d0d3f985f8e5f8535a4d106 6064158 dipy_1.2.0.orig.tar.gz
 a1dbafab699c0ea6b912731d046be11d00b65108 6640 dipy_1.2.0-1.debian.tar.xz
 ae47ae4dda772bcd223e1daf3466a270db0d69f8 11658 dipy_1.2.0-1_amd64.buildinfo
 2d58bd66b14a0ef4b20f4faa4e3994643573fd6a 2210732 
python-dipy-doc_1.2.0-1_all.deb
 0923db9a146bd52f8fd79311856786b498f4537f 8776 
python3-dipy-lib_1.2.0-1_amd64.deb
 58d514fd30d3215519465d0a2501970506248d03 3102988 python3-dipy_1.2.0-1_all.deb
Checksums-Sha256:
 f19c0dea924d1533f118fe2fa6201221419cb02d95f2f4d768486804f093d8e3 2405 
dipy_1.2.0-1.dsc
 6c2123d8001aab88991a41ff8023cb711cc044d88c9f16e687f4ef1bb00980ed 6064158 
dipy_1.2.0.orig.tar.gz
 2946b22d173fb1237f623fad2f10b9bc86055672f68d546dbc0c6e735d178cf6 6640 
dipy_1.2.0-1.debian.tar.xz
 3fde861a6e6c3a908c8c1a475154b82ee98b7ae36737b46b193a95f644f30984 11658 
dipy_1.2.0-1_amd64.buildinfo
 e7f8d46944243a5d066193fbe3a3e20afa622d4f99d57cbb83faf29f6ab44541 2210732 
python-dipy-doc_1.2.0-1_all.deb
 a0e0ffef98c136175ac67d325150ed263fd2bc429780fe5a87a23e768bdf0319 8776 
python3-dipy-lib_1.2.0-1_amd64.deb
 b65fe900ce8a58b8e74971eb887b29ba51b295314f823589c469fba23d3a06ff 3102988 
python3-dipy_1.2.0-1_all.deb
File

Bug#965609: marked as done (jpnevulator: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:48:34 +
with message-id 
and subject line Bug#965609: fixed in jpnevulator 2.3.6-1
has caused the Debian Bug report #965609,
regarding jpnevulator: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpnevulator
Version: 2.3.4-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package jpnevulator uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: jpnevulator
Source-Version: 2.3.6-1
Done: Freddy Spierenburg 

We believe that the bug you reported is fixed in the latest version of
jpnevulator, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Freddy Spierenburg  (supplier of updated jpnevulator 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: Tue, 28 Jul 2020 13:44:45 +0200
Source: jpnevulator
Architecture: source
Version: 2.3.6-1
Distribution: unstable
Urgency: low
Maintainer: Freddy Spierenburg 
Changed-By: Freddy Spierenburg 
Closes: 958136 965609
Changes:
 jpnevulator (2.3.6-1) unstable; urgency=low
 .
   * New upstream release.
   * Upgrade to more recent debhelper version. (Closes: #965609)
   * Start signing the source package.
   * Update copyright file according to current machine readable rules.
   * Add upstream/metadata information.
   * Make rules more dh compliant.
   * Remove no longer needed compat file.
   * Add Dockerfile and README to easily create the package.
   * (Helmut Grohne) Fix FTCBFS: Let dh_auto_build pass cross tools to
 make. (Closes: #958136)
Checksums-Sha1:
 f93c9efbd58267e9263aa70892b93284354941a7 1993 jpnevulator_2.3.6-1.dsc
 75bed43047a241aac4d51e6df40d4329911756f1 36063 jpnevulator_2.3.6.orig.tar.gz
 fa38b7dbe589a785b3168f33282c64201da6 833 jpnevulator_2.3.6.orig.tar.gz.asc
 2d1f3643ac058f6baaac530f639b1b0a1bb1fb11 19536 
jpnevulator_2.3.6-1.debian.tar.xz
 2637462e8bcf4f28b396205eca964beff4492d18 5440 
jpnevulator_2.3.6-1_source.buildinfo
Checksums-Sha256:
 7c652defcc6cf767773866fa48243f4c0ee5af6dc7757d4455f0f8dc1dc84eeb 1993 
jpnevulator_2.3.6-1.dsc
 4f9e1c38a23f7b15794731ee31f873f33371b9d9ea412f5404d9f008a85e803d 36063 
jpnevulator_2.3.6.orig.tar.gz
 fc5717fe8ee182211b48d525afff982eac5e06c720c1d8e84d1f41556a6bbe6e 833 
jpnevulator_2.3.6.orig.tar.gz.asc
 864dbe4520a119d1f72ece71c215f5bf3105cb44abf9bf05b23bc610c2e04ab0 19536 
jpnevulator_2.3.6-1.debian.tar.xz
 d816b51a1a5d3f045c2e180966bbb3e17331aa19b3f3dc1dcb39c6eca7e373db 5440 
jpnevulator_2.3.6-1_source.buildinfo
Files:
 958604bb99fdbe80a71f2d4a7b0c43e1 1993 comm optional jpnevulator_2.3.6-1.dsc
 49b0e69d2f97447e28b5fdd0aabbf258 36063 comm optional 
jpnevulator_2.3.6.orig.tar.gz
 4ea36b1bac4df8928c3312d5b1fe8bac 833 comm optional 
jpnevulator_2.3.6.orig.tar.gz.asc
 e3df9a82b2d6827ddc8d5ac3124c9d72 19536 comm optional 
jpnevulator_2.3.6-1.debian.tar.xz
 69c7999c74160add7a51857a2db04824 54

Bug#958136: marked as done (jpnevulator FTCBFS: does not pass cross tools to make)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:48:34 +
with message-id 
and subject line Bug#958136: fixed in jpnevulator 2.3.6-1
has caused the Debian Bug report #958136,
regarding jpnevulator FTCBFS: does not pass cross tools to make
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.)


-- 
958136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpnevulator
Version: 2.3.4-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

jpnevulator fails to cross build from source, because it does not pass
cross tools to make. The easiest way of doing so - using dh_auto_build -
makes jpnevulator cross buildable. Please consider applying the attached
patch.

Helmut
diff --minimal -Nru jpnevulator-2.3.4/debian/changelog 
jpnevulator-2.3.4/debian/changelog
--- jpnevulator-2.3.4/debian/changelog  2016-08-27 01:23:03.0 +0200
+++ jpnevulator-2.3.4/debian/changelog  2020-04-18 22:10:22.0 +0200
@@ -1,3 +1,10 @@
+jpnevulator (2.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 18 Apr 2020 22:10:22 +0200
+
 jpnevulator (2.3.4-1) unstable; urgency=low
 
   * New upstream release.
diff --minimal -Nru jpnevulator-2.3.4/debian/control 
jpnevulator-2.3.4/debian/control
--- jpnevulator-2.3.4/debian/control2016-08-27 00:54:39.0 +0200
+++ jpnevulator-2.3.4/debian/control2020-04-18 22:10:22.0 +0200
@@ -3,7 +3,7 @@
 Section: comm
 Priority: optional
 Maintainer: Freddy Spierenburg 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 7)
 Standards-Version: 3.9.8
 
 Package: jpnevulator
diff --minimal -Nru jpnevulator-2.3.4/debian/rules 
jpnevulator-2.3.4/debian/rules
--- jpnevulator-2.3.4/debian/rules  2015-10-02 21:17:31.0 +0200
+++ jpnevulator-2.3.4/debian/rules  2020-04-18 22:10:21.0 +0200
@@ -38,7 +38,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE) CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)"
+   dh_auto_build -- CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)"
#docbook-to-man debian/jpnevulator.sgml > jpnevulator.1
 
touch $@
--- End Message ---
--- Begin Message ---
Source: jpnevulator
Source-Version: 2.3.6-1
Done: Freddy Spierenburg 

We believe that the bug you reported is fixed in the latest version of
jpnevulator, 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 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Freddy Spierenburg  (supplier of updated jpnevulator 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: Tue, 28 Jul 2020 13:44:45 +0200
Source: jpnevulator
Architecture: source
Version: 2.3.6-1
Distribution: unstable
Urgency: low
Maintainer: Freddy Spierenburg 
Changed-By: Freddy Spierenburg 
Closes: 958136 965609
Changes:
 jpnevulator (2.3.6-1) unstable; urgency=low
 .
   * New upstream release.
   * Upgrade to more recent debhelper version. (Closes: #965609)
   * Start signing the source package.
   * Update copyright file according to current machine readable rules.
   * Add upstream/metadata information.
   * Make rules more dh compliant.
   * Remove no longer needed compat file.
   * Add Dockerfile and README to easily create the package.
   * (Helmut Grohne) Fix FTCBFS: Let dh_auto_build pass cross tools to
 make. (Closes: #958136)
Checksums-Sha1:
 f93c9efbd58267e9263aa70892b93284354941a7 1993 jpnevulator_2.3.6-1.dsc
 75bed43047a241aac4d51e6df40d4329911756f1 36063 jpnevulator_2.3.6.orig.tar.gz
 fa38b7dbe589a785b3168f33282c64201da6 833 jpnevulator_2.3.6.orig.tar.gz.asc
 2d1f3643ac058f6baaac530f639b1b0a1bb1fb11 19536 
jpnevulator_2.3.6-1.debian.tar.xz
 2637462e8bcf4f28b396205eca964beff4492d18 5440 
jpnevulator_2.3.6-1_source.buildinfo
Checksums-Sha256:
 7c652defcc6cf767773866fa48243f4c0ee5af6dc7757d4455f0f8dc1dc84eeb 1993 
jpnevulator_2.3.6-1.dsc
 4f9e1c38a23f7b15794731ee31f873f33371b9d9ea412f5404d9f008a85e803d 36063 
jpnevulator_2.3.6.orig.t

Bug#925338: marked as done (xfce4-session: Please support new logind virtual packages)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:21:51 +
with message-id 
and subject line Bug#925338: fixed in xfce4-session 4.14.2-2
has caused the Debian Bug report #925338,
regarding xfce4-session: Please support new logind virtual packages
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.)


-- 
925338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-session
Version: 4.12.1-6
Severity: normal
Tags: patch

Dear Maintainer,

Please change xfce4-session to use the new default-logind and logind virtual
packages.  This will enable xfce4-session to also be used on systems using
elogind and non-systemd inits.

The logind and default-logind virtual packages have been seconded for inclusion
in Debian Policy (see #917431) and libpam-elogind and libpam-systemd providing
these have been uploaded.   
 

I also suggest removing systemd-shim which is no longer in the archive and the
unnecessary reference to systemd-sysv.

Patch below.

Thanks

Mark

commit 7f6e2c337fa07ae45405e4bdc743f248b2851469
Author: Mark Hindley 
Date:   Sat Mar 23 11:40:05 2019 +

Use new virtual logind packages for xfce4-session Recommends. Also remove
systemd-shim which is no longer in archive.

diff --git a/debian/control b/debian/control
index bedb8fe..bc8e05d 100644
--- a/debian/control
+++ b/debian/control
@@ -21,8 +21,8 @@ Breaks: xfce4-utils
 Replaces: xfce4-utils
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}, xfce4-settings (>= 4.10.0), xfconf
-Recommends: xfwm4, xfdesktop4, libpam-systemd [linux-any],
- systemd-sysv [linux-any] | systemd-shim, upower, dbus-x11, x11-xserver-utils,
+Recommends: xfwm4, xfdesktop4, default-logind [linux-any] | logind [linux-any],
+ upower, dbus-x11, x11-xserver-utils,
  light-locker
 Suggests: sudo, fortunes-mod
 Provides: x-session-manager
--- End Message ---
--- Begin Message ---
Source: xfce4-session
Source-Version: 4.14.2-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-session, 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.
Yves-Alexis Perez  (supplier of updated xfce4-session 
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: Sun, 01 Nov 2020 16:03:47 +0100
Source: xfce4-session
Architecture: source
Version: 4.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 836062 902137 902362 925338
Changes:
 xfce4-session (4.14.2-2) unstable; urgency=medium
 .
   [ Mark Hindley ]
   * Use default-logind | logind virtual packages (Closes: #925338).
   * Use default-dbus-session-bus | dbus-session-bus virtual packages
 (Closes: #836062).
   * Depend rather than Recommend x11-xserver-utils (Closes:  #902137).
   * Don't clean upstream generated source files (Closes: #902362).
   * Remove obsolete systemd-shim recommendation.
Checksums-Sha1:
 21145c638618172b98754c287c197355e3b75439 1819 xfce4-session_4.14.2-2.dsc
 479147e216962d21dcfac24336e0f70fff60c482 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 bb933fecb8c12dd5a43c1181d96a026329522ad4 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Checksums-Sha256:
 06523344785e9ef210e99301baf103fad8492c7626f64e20fceaa68781a93296 1819 
xfce4-session_4.14.2-2.dsc
 f3d401b8d67635384d861ec55411c9efcad3eb325f358b16140963ac1afb815b 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 e21b896571ec1c8ef01596d25dd87c3243d07bfe0eaf482f82276bf2d259edae 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Files:
 ec7ca1388d37f6655c762d4e1305feb2 1819 xfce optional xfce4-session_4.14.2-2.dsc
 47feab169fd2dec1c743c8121d912538 14600 xfce optional 
xfce4-session_4.14.2-2.debian.tar.xz
 9a5adabd1f11e5e1da83774059bc21bd 15465 xfce optional 
xfce4-session_4.14.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl+e0J0ACgkQ3rYcyPpX
RFuidwf9E/J+paYt989v26ZxXOLRYw3ISuvP+KPj3o9CqB8k

Bug#902362: marked as done (xfce4-session: 'debian/rules clean' after build causes removal of xfce4-session/*.[hc])

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:21:51 +
with message-id 
and subject line Bug#902362: fixed in xfce4-session 4.14.2-2
has caused the Debian Bug report #902362,
regarding xfce4-session: 'debian/rules clean' after build causes removal of 
xfce4-session/*.[hc]
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.)


-- 
902362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-session
Version: 4.13.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

xfce4-session fails to build twice in a row. The first build succeeds,
but during subsequent debian/rules clean the following files disappear:

xfce4-session/xfsm-client-dbus.h
xfce4-session/xfsm-manager-dbus.c
xfce4-session/xfsm-marshal.h
xfce4-session/xfsm-manager-dbus.h
xfce4-session/xfsm-chooser-icon.h
xfce4-session/xfsm-client-dbus.c
xfce4-session/xfsm-marshal.c

causing the second build to fail.

There is no explicit deletion command being shown during make distclean.
Full buildlog attached.


Andreas


xfce4-session_4.13.0-1_twice.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: xfce4-session
Source-Version: 4.14.2-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-session, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-session 
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: Sun, 01 Nov 2020 16:03:47 +0100
Source: xfce4-session
Architecture: source
Version: 4.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 836062 902137 902362 925338
Changes:
 xfce4-session (4.14.2-2) unstable; urgency=medium
 .
   [ Mark Hindley ]
   * Use default-logind | logind virtual packages (Closes: #925338).
   * Use default-dbus-session-bus | dbus-session-bus virtual packages
 (Closes: #836062).
   * Depend rather than Recommend x11-xserver-utils (Closes:  #902137).
   * Don't clean upstream generated source files (Closes: #902362).
   * Remove obsolete systemd-shim recommendation.
Checksums-Sha1:
 21145c638618172b98754c287c197355e3b75439 1819 xfce4-session_4.14.2-2.dsc
 479147e216962d21dcfac24336e0f70fff60c482 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 bb933fecb8c12dd5a43c1181d96a026329522ad4 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Checksums-Sha256:
 06523344785e9ef210e99301baf103fad8492c7626f64e20fceaa68781a93296 1819 
xfce4-session_4.14.2-2.dsc
 f3d401b8d67635384d861ec55411c9efcad3eb325f358b16140963ac1afb815b 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 e21b896571ec1c8ef01596d25dd87c3243d07bfe0eaf482f82276bf2d259edae 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Files:
 ec7ca1388d37f6655c762d4e1305feb2 1819 xfce optional xfce4-session_4.14.2-2.dsc
 47feab169fd2dec1c743c8121d912538 14600 xfce optional 
xfce4-session_4.14.2-2.debian.tar.xz
 9a5adabd1f11e5e1da83774059bc21bd 15465 xfce optional 
xfce4-session_4.14.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl+e0J0ACgkQ3rYcyPpX
RFuidwf9E/J+paYt989v26ZxXOLRYw3ISuvP+KPj3o9CqB8kazcyRCCUsuajWzI1
xW+0FJtFvi74brkou1dQnhiBk1Sx56qHd3zGiyALQTH/p9Yx6Wte3SLIQ4jyjwgD
/TbOebm92K9pHGjmr/u7VSDcNuxfW0oILxDhWHM0TC19i+i7SEtKSVGskpZCY23O
Hkx8JLhni/xChCmdsYoFZ8/iv4uXdme5EGSf5U4y5MzxL1tYdTCFAsezXxrtksb5
xb4Vn/sJSsJ4W4bhUYisbMYHux8lVczvwz93Ud1auyUY3KgGwNmDqiYR7VamQ/a7
L5Fj87ei+812k6ocyepWQrxXFYUXzw==
=mWUV
-END PGP SIGNATURE End Message ---

Bug#836062: marked as done (xfce4-session: please switch from dbus-x11 to default-dbus-session-bus | dbus-session-bus)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:21:50 +
with message-id 
and subject line Bug#836062: fixed in xfce4-session 4.14.2-2
has caused the Debian Bug report #836062,
regarding xfce4-session: please switch from dbus-x11 to 
default-dbus-session-bus | dbus-session-bus
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.)


-- 
836062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-session
Version: 4.12.1-4
Severity: normal
User: d...@packages.debian.org
Usertags: dbus-launch default-dbus-session-bus

As described in 
I'm trying to reduce how much dbus-launch is used in Debian.
This package currently Depends on dbus-x11 as a way to get a session bus.

This package falls into the "desktop sessions" category: please replace

Recommends: dbus-x11

with

Recommends: default-dbus-session-bus | dbus-session-bus

so that either dbus-user-session or dbus-x11 can be used. My short-term
goal with this is that major desktop environments in Debian stretch should
be able to run with either dbus-user-session or dbus-x11, with the other
one uninstalled.

This package will also need a change in upstream code to avoid running
dbus-launch when DBUS_SESSION_BUS_ADDRESS is unset, but
XDG_RUNTIME_DIR/bus exists. I've opened a separate bug for that.

Thanks,
S
--- End Message ---
--- Begin Message ---
Source: xfce4-session
Source-Version: 4.14.2-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-session, 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 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-session 
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: Sun, 01 Nov 2020 16:03:47 +0100
Source: xfce4-session
Architecture: source
Version: 4.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 836062 902137 902362 925338
Changes:
 xfce4-session (4.14.2-2) unstable; urgency=medium
 .
   [ Mark Hindley ]
   * Use default-logind | logind virtual packages (Closes: #925338).
   * Use default-dbus-session-bus | dbus-session-bus virtual packages
 (Closes: #836062).
   * Depend rather than Recommend x11-xserver-utils (Closes:  #902137).
   * Don't clean upstream generated source files (Closes: #902362).
   * Remove obsolete systemd-shim recommendation.
Checksums-Sha1:
 21145c638618172b98754c287c197355e3b75439 1819 xfce4-session_4.14.2-2.dsc
 479147e216962d21dcfac24336e0f70fff60c482 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 bb933fecb8c12dd5a43c1181d96a026329522ad4 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Checksums-Sha256:
 06523344785e9ef210e99301baf103fad8492c7626f64e20fceaa68781a93296 1819 
xfce4-session_4.14.2-2.dsc
 f3d401b8d67635384d861ec55411c9efcad3eb325f358b16140963ac1afb815b 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 e21b896571ec1c8ef01596d25dd87c3243d07bfe0eaf482f82276bf2d259edae 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Files:
 ec7ca1388d37f6655c762d4e1305feb2 1819 xfce optional xfce4-session_4.14.2-2.dsc
 47feab169fd2dec1c743c8121d912538 14600 xfce optional 
xfce4-session_4.14.2-2.debian.tar.xz
 9a5adabd1f11e5e1da83774059bc21bd 15465 xfce optional 
xfce4-session_4.14.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl+e0J0ACgkQ3rYcyPpX
RFuidwf9E/J+paYt989v26ZxXOLRYw3ISuvP+KPj3o9CqB8kazcyRCCUsuajWzI1
xW+0FJtFvi74brkou1dQnhiBk1Sx56qHd3zGiyALQTH/p9Yx6Wte3SLIQ4jyjwgD
/TbOebm92K9pHGjmr/u7VSDcNuxfW0oILxDhWHM0TC19i+i7SEtKSVGskpZCY23O
Hkx8JLhni/xChCmdsYoFZ8/iv4uXdme5EGSf5U4y5MzxL1tYdTCFAsezXxrtksb5
xb4Vn/sJSsJ4W4bhUYisbMYHux8lVczvwz93Ud1auyUY3KgGwNmDqiYR7VamQ/a7
L5Fj87ei+812k6ocyepWQrxXFYUXzw==
=mWUV
-END PGP SIGNATURE End Message ---

Bug#902137: marked as done (xfce4-session-logout fails if x11-xserver-utils is not installed)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:21:51 +
with message-id 
and subject line Bug#902137: fixed in xfce4-session 4.14.2-2
has caused the Debian Bug report #902137,
regarding xfce4-session-logout fails if x11-xserver-utils is not installed
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.)


-- 
902137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-session
Version: 4.12.1-6
Severity: normal

If x11-xserver-utils is not installed nothing happens after clicking on
an option in the xfce logout dialogue.  If logout is clicked again the
message: "Failed to log out. Session manager must be in idle state when
requesting a shutdown." comes up.

It seems therefore that x11-xserver-utils should be a dependency of
xfce4-session and not just recommended.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.12-20180618 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-session depends on:
ii  libatk1.0-02.28.1-1
ii  libc6  2.27-3
ii  libcairo2  1.15.10-3
ii  libdbus-1-31.12.8-3
ii  libdbus-glib-1-2   0.110-2
ii  libfontconfig1 2.13.0-5
ii  libfreetype6   2.8.1-2
ii  libgdk-pixbuf2.0-0 2.36.11-2
ii  libglib2.0-0   2.56.1-2
ii  libgtk2.0-02.24.32-1
ii  libice62:1.0.9-2
ii  libpango-1.0-0 1.42.0-1
ii  libpangocairo-1.0-01.42.0-1
ii  libpangoft2-1.0-0  1.42.0-1
ii  libpolkit-gobject-1-0  0.105-20
ii  libsm6 2:1.2.2-1+b3
ii  libwnck22  2.30.7-5.1
ii  libx11-6   2:1.6.5-1
ii  libxfce4ui-1-0 4.12.1-3
ii  libxfce4util7  4.12.1-3
ii  libxfconf-0-2  4.12.1-1
ii  xfce4-settings 4.12.3-1
ii  xfconf 4.12.1-1

Versions of packages xfce4-session recommends:
ii  dbus-x11   1.12.8-3
ii  libpam-systemd 238-5
pn  light-locker   
ii  systemd-sysv   238-5
pn  upower 
ii  x11-xserver-utils  7.7+8
ii  xfdesktop4 4.12.4-1
ii  xfwm4  4.12.4-1

Versions of packages xfce4-session suggests:
pn  fortunes-mod  
ii  sudo  1.8.23-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4-session
Source-Version: 4.14.2-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-session, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-session 
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: Sun, 01 Nov 2020 16:03:47 +0100
Source: xfce4-session
Architecture: source
Version: 4.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 836062 902137 902362 925338
Changes:
 xfce4-session (4.14.2-2) unstable; urgency=medium
 .
   [ Mark Hindley ]
   * Use default-logind | logind virtual packages (Closes: #925338).
   * Use default-dbus-session-bus | dbus-session-bus virtual packages
 (Closes: #836062).
   * Depend rather than Recommend x11-xserver-utils (Closes:  #902137).
   * Don't clean upstream generated source files (Closes: #902362).
   * Remove obsolete systemd-shim recommendation.
Checksums-Sha1:
 21145c638618172b98754c287c197355e3b75439 1819 xfce4-session_4.14.2-2.dsc
 479147e216962d21dcfac24336e0f70fff60c482 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 bb933fecb8c12dd5a43c1181d96a026329522ad4 15465 
xfce4-session_4.14.2-2_amd64.buildinfo
Checksums-Sha256:
 06523344785e9ef210e99301baf103fad8492c7626f64e20fceaa68781a93296 1819 
xfce4-session_4.14.2-2.dsc
 f3d401b8d67635384d861ec55411c9efcad3eb325f358b16140963ac1afb815b 14600 
xfce4-session_4.14.2-2.debian.tar.xz
 e21b896571ec1c8ef01596d25dd87c324

Bug#973006: marked as done (gourmet: Missing dependency on python3-argcomplete)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:18:42 +
with message-id 
and subject line Bug#973006: fixed in gourmet 0.17.5~alpha2-6
has caused the Debian Bug report #973006,
regarding gourmet: Missing dependency on python3-argcomplete
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.)


-- 
973006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gourmet
Version: 0.17.5~alpha2-4
Severity: important

Dear Maintainer,

I have the following output:
Traceback (most recent call last):
  File "/usr/bin/gourmet", line 33, in 
sys.exit(load_entry_point('gourmet==0.17.5', 'console_scripts',
'gourmet')())
  File "/usr/bin/gourmet", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1014, in _gcd_import
  File "", line 991, in _find_and_load
  File "", line 975, in _find_and_load_unlocked
  File "", line 671, in _load_unlocked
  File "", line 783, in exec_module
  File "", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/gourmet/GourmetRecipeManager.py", line
11, in 
from gourmet import (
  File "/usr/lib/python3/dist-packages/gourmet/batchEditor.py", line 3, in

from . import gglobals
  File "/usr/lib/python3/dist-packages/gourmet/gglobals.py", line 8, in

from .optionparser import args
  File "/usr/lib/python3/dist-packages/gourmet/optionparser.py", line 2, in

import argcomplete
ModuleNotFoundError: No module named 'argcomplete'

Manually installing python3-argcomplete solved the issue.



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gourmet depends on:
ii  gir1.2-gtk-3.0  3.24.23-2
ii  python3 3.8.6-1
ii  python3-bs4 4.9.3-1
ii  python3-gi  3.38.0-1+b1
ii  python3-pil 7.2.0-1+b1
ii  python3-reportlab   3.5.53-1
ii  python3-sqlalchemy  1.3.19+ds1-1

Versions of packages gourmet recommends:
pn  kpython3-gtkspellcheck  
ii  python3-lxml4.6.1-1
pn  python3-pyglet  

Versions of packages gourmet suggests:
pn  python3-ebooklib  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gourmet
Source-Version: 0.17.5~alpha2-6
Done: Christian Marillat 

We believe that the bug you reported is fixed in the latest version of
gourmet, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Marillat  (supplier of updated gourmet 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: Sun, 01 Nov 2020 16:02:13 +0100
Source: gourmet
Architecture: source
Version: 0.17.5~alpha2-6
Distribution: unstable
Urgency: medium
Maintainer: Christian Marillat 
Changed-By: Christian Marillat 
Closes: 973006
Changes:
 gourmet (0.17.5~alpha2-6) unstable; urgency=medium
 .
   * Move python3-argcomplete from Recommends to Depends and add
 python3-requests and python3-toml to Depends (Closes: #973006)
Checksums-Sha1:
 371fb1b22eb1f34727c6b91f06921d1925225bc9 1860 gourmet_0.17.5~alpha2-6.dsc
 194895ba45297db0d99f36d189dafb1b2031ce01 4884 
gourmet_0.17.5~alpha2-6.debian.tar.xz
 723b94b60825b854bb04e61676dcb59135315bf7 10516 
gourmet_0.17.5~alpha2-6_source.buildinfo
Checksums-Sha256:
 fc3945715348b704c90d7daffcd677a85f02508dbb32079b42a5901156684bd5 1860 
gourmet_0.17.5~alpha2-6.dsc
 83bfa946f4ed8e7fab1601b2e8ca1aaef5e8bd3ae7568ac9a693664c31000abf 4884 
gourmet_0.17.5~alpha2-6.debian.tar.xz
 a9c770959e383b336d2e24b8cd56a

Bug#972793: marked as done (hg-git: autopkgtest needs update for new version of dulwich: lots of deprecation *warnings*)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 15:03:37 +
with message-id 
and subject line Bug#972793: fixed in hg-git 0.9.0-2
has caused the Debian Bug report #972793,
regarding hg-git: autopkgtest needs update for new version of dulwich: lots of 
deprecation *warnings*
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.)


-- 
972793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hg-git
Version: 0.9.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, dulw...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dulwich

Dear maintainer(s),

With a recent upload of dulwich the autopkgtest of hg-git fails in
testing when that autopkgtest is run with the binary packages of dulwich
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
dulwichfrom testing0.20.6-1.1
hg-git from testing0.9.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of dulwich to
testing [1]. Of course, dulwich shouldn't just break your autopkgtest
(or even worse, your package), but it seems to me that the change in
dulwich was intended and your package needs to update to the new
situation. Also, failing on deprecation warnings should really be
avoided in autopkgtesting (that's more something for upstreams test
framework), please disable deprecation warnings if possible.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=dulwich

https://ci.debian.net/data/autopkgtest/testing/amd64/h/hg-git/7682446/log.gz

--- /tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/tests/test-renames.t
+++
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/tests/test-renames.t.err
@@ -371,6 +371,16 @@
   adding objects
   added 2 commits with 2 trees and 3 blobs
   updating reference refs/heads/master
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:411:
DeprecationWarning: Use SendPackResult.refs instead.
+if remote_name and new_refs:
+  /usr/lib/python3/dist-packages/mercurial/pycompat.py:362:
DeprecationWarning: Use SendPackResult.refs instead.
+iteritems = lambda x: x.items()
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:431:
DeprecationWarning: Use SendPackResult.refs instead.
+if old_refs == new_refs:
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:434:
DeprecationWarning: Use SendPackResult.refs instead.
+elif len(new_refs) > len(old_refs):
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:436:
DeprecationWarning: Use SendPackResult.refs instead.
+elif len(old_refs) > len(new_refs):

   $ cd ../gitrepo
   $ git log master --pretty=oneline

ERROR: test-renames.t output changed
!.
---
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/tests/test-file-removal.t
+++
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/tests/test-file-removal.t.err
@@ -168,6 +168,12 @@
   searching for changes
   adding objects
   added 9 commits with 8 trees and 5 blobs
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:431:
DeprecationWarning: Use SendPackResult.refs instead.
+if old_refs == new_refs:
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:434:
DeprecationWarning: Use SendPackResult.refs instead.
+elif len(new_refs) > len(old_refs):
+
/tmp/autopkgtest-lxc.1m_ql5en/downtmp/build.IYS/src/hggit/git_handler.py:435:
DeprecationWarning: Use SendPackResult.refs instead.
+ret = 1 + (len(new_refs) - len(old_refs))

   $ cd ..
   $ git --git-dir=gitrepo2 log --pretty=medium

ERROR: test-file-removal.t output changed
!.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: hg-git
Source-Version: 0.9.0-2
Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= 

We believe that the bug you reported is fixed in the latest version of
hg-git, 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 972...@bugs.debian.org,
and the maintainer will

Processed: RFS: inkscape-textext/1.2.0-1 [ITP] -- Re-editable LaTeX graphics for Inkscape

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 973542
Bug #973542 [sponsorship-requests] RFS: inkscape-textext/1.2.0-1 [ITP] -- 
Re-editable LaTeX graphics for Inkscape
Marked Bug as done
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
973542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#964770: marked as done (lintian: lintian will get stuck on arm64)

[Debian Bug Tracking System]

Your message dated Sun, 1 Nov 2020 06:39:16 -0800
with message-id 

and subject line Re: Bug#964770: lintian: lintian will get stuck on arm64
has caused the Debian Bug report #964770,
regarding lintian: lintian will get stuck on arm64
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.)


-- 
964770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.83.0
Severity: normal

It seems that lintian will get stuck with it on arm64.
I've confirmed this on arm64. It may happen on other platform, but I don't
know.

This issue does not occur on amd64.

At first, I've faced it on arm64v8:focal cloud image, [1]
but it seems that this issue is not specific to the image itself.

[1] https://bugs.launchpad.net/cloud-images/+bug/1881217

Here is the reproducible steps:

  $ docker run -it arm64v8/debian:unstable
  # apt update
  # apt install -y lintian
  # lintian --help

As a result, lintian does not show usage help.
Here is the version about lintian:

  # dpkg -l | grep lintian
  ii  lintian  2.83.0 all   
   Debian package checker

Additional information:

It seems that IO::Async::Loop related code will stuck:

  # perl -d /usr/bin/lintian --help

  Loading DB routines from perl5db.pl version 1.55
  Editor support available.

  Enter h or 'h h' for help, or 'man perldebug' for more help.

  main::(/usr/bin/lintian:55):};
DB<1>
  ^C
  
IO::Async::Loop::Epoll::loop_once(/usr/share/perl5/IO/Async/Loop/Epoll.pm:187):
  187:   $self->post_wait;
DB<1> T
  @ = DB::DB called from file '/usr/share/perl5/IO/Async/Loop/Epoll.pm' line 187
  . = IO::Async::Loop::Epoll::loop_once(ref(IO::Async::Loop::Epoll)) called from
  file '/usr/share/perl5/IO/Async/Loop.pm' line 654
  . = IO::Async::Loop::await(ref(IO::Async::Loop::Epoll), 
ref(IO::Async::Future))
  called from file '/usr/share/perl5/Lintian/Util.pm' line 628
  $ = Lintian::Util::safe_qx('nproc') called from file
  '/usr/share/perl5/Lintian/Internal/FrontendUtil.pm' line 123
  @ = Lintian::Internal::FrontendUtil::default_parallel() called from file
  '/usr/share/lintian/commands/lintian.pm' line 93
  $ = require '/usr/share/lintian/commands/lintian.pm' called from file
  '/usr/bin/lintian' line 36
  . = eval {...} called from file '/usr/bin/lintian' line 36
  . =
  main::__ANON__[/usr/bin/lintian:55]('/usr/share/lintian/commands/lintian.pm')
  called from file '/usr/bin/lintian' line 120
  . = dplint::run_tool('/usr/bin/lintian', 'lintian') called from file
  '/usr/bin/lintian' line 299
  . = dplint::main() called from file '/usr/bin/lintian' line 383

The trace log indicates that $loop->run_child will stuck at 
safe_qx /usr/share/perl5/Lintian/Util.pm:

   608  my $loop = IO::Async::Loop->new;
   609  my $future = $loop->new_future;
   610  my $status;
   611
   612  $loop->run_child(
   613  command => [@command],
   614  on_finish => sub {
   615  my ($pid, $exitcode, $stdout, $stderr) = @_;
   616  $status = ($exitcode >> 8);
   617
   618  if ($status) {
   619  my $message = "Command @command exited with status 
$status";
   620  $message .= ": $stderr" if length $stderr;
   621  $future->fail($message);
   622  return;
   623  }
   624
   625  $future->done($stdout);
   626  });
   627
   628  $loop->await($future);
   629

Regards,
--- End Message ---
--- Begin Message ---
Hi Kentaro,

On Sun, Nov 1, 2020 at 6:36 AM Kentaro Hayashi  wrote:
>
> (It is ok to close, I think)

I agree. Closing this bug. Thanks!

Kind regards
Felix Lechner--- End Message ---

Bug#973247: marked as done (python-cryptography: CVE-2020-25659: Bleichenbacher timing oracle attack against RSA decryption)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 13:49:11 +
with message-id 
and subject line Bug#973247: fixed in python-cryptography 3.2.1-1
has caused the Debian Bug report #973247,
regarding python-cryptography: CVE-2020-25659: Bleichenbacher timing oracle 
attack against RSA decryption
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.)


-- 
973247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cryptography
Version: 3.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 2.6.1-3+deb10u2
Control: found -1 2.6.1-3

Hi,

The following vulnerability was published for python-cryptography.

CVE-2020-25659[0]:
| bleichenbacher timing oracle attack against RSA decryption

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-25659
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25659
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1889988
[2] 
https://github.com/pyca/cryptography/commit/58494b41d6ecb0f56b7c5f05d5f5e3ca0320d494
[3] https://github.com/pyca/cryptography/security/advisories/GHSA-hggm-jpg3-v476

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: python-cryptography
Source-Version: 3.2.1-1
Done: Tristan Seligmann 

We believe that the bug you reported is fixed in the latest version of
python-cryptography, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated 
python-cryptography 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: Sun, 01 Nov 2020 15:22:43 +0200
Source: python-cryptography
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Tristan Seligmann 
Changed-By: Tristan Seligmann 
Closes: 973247
Changes:
 python-cryptography (3.2.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Tristan Seligmann ]
   * New upstream release.
 - Closes: #973247 (CVE-2020-25659)
Checksums-Sha1:
 11b44ea9dbde5215ec7a9e07ee99851dfb224a23 3034 python-cryptography_3.2.1-1.dsc
 20708a4955dcf7e2bb53d05418273d2bc0f80ab4 540994 
python-cryptography_3.2.1.orig.tar.gz
 91b2ab3b4f955fe49f0e2c91e62608912f51f4c7 488 
python-cryptography_3.2.1.orig.tar.gz.asc
 8d0caea05cdb6bbe3f8c81322f0e50291cbbf397 11784 
python-cryptography_3.2.1-1.debian.tar.xz
 41436d567c423e3610fd56fb13ac2e345a584bf7 9375 
python-cryptography_3.2.1-1_amd64.buildinfo
Checksums-Sha256:
 fddbc1bb0c7fb73a09efeed7498c6669d8e96078168355da8def6b665e4eb004 3034 
python-cryptography_3.2.1-1.dsc
 d3d5e10be0cf2a12214ddee45c6bd203dab435e3d83b4560c03066eda600bfe3 540994 
python-cryptography_3.2.1.orig.tar.gz
 41cb889b5ecb9fe555667139bab7a28cd3e8911841a16b95953410c0406e417e 488 
python-cryptography_3.2.1.orig.tar.gz.asc
 0c68541d2ade034952d1962ca062e832a0861bbf7d8cc673fea0a0635095cccd 11784 
python-cryptography_3.2.1-1.debian.tar.xz
 19a0713e6ae1ec047203af7f32b9eae823763a857b6225f34e1982c87bd93d3d 9375 
python-cryptography_3.2.1-1_amd64.buildinfo
Files:
 1e77f929f206efdbbca772b740ad0eb5 3034 python optional 
python-cryptography_3.2.1-1.dsc
 906eb57df20bb8a60222a5196c38d843 540994 python optional 
python-cryptography_3.2.1.orig.tar.gz
 049acbc45710fc9663002369ca7e8495 488 python optional 
python-cryptography_3.2.1.orig.tar.gz.asc
 136ce715d442cee24913d17898189f83 11784 python optional 
python-cryptography_3.2.1-1.debian.tar.xz
 9d93a7e2eef93e02eead3b42797b93ba 9375 python optional 
python-cryptography_3.2.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGTBAEBCgB9FiEEXAZWhXVRbQoz/6ejwImQ+x9jeJMFAl+eumBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDVD
MDY1Njg1NzU1MTZEMEEzM0ZGQTdBM0MwODk5MEZCMUY2Mzc4OTMACgkQwImQ+x9j
eJPOyAf/YHriXPTvA5hrc4RZvUCtNN5v6T9roWbk1INC3KOArAiFcIPAJwoO8fFV
bnL51629B

Bug#963551: marked as done (python3-bitstring: Update, DeprecationWarning)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 13:49:02 +
with message-id 
and subject line Bug#963551: fixed in python-bitstring 3.1.7-2
has caused the Debian Bug report #963551,
regarding python3-bitstring: Update, DeprecationWarning
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.)


-- 
963551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-bitstring
Version: 3.1.5-2
Severity: minor

The bitstring package is at version 3.1.7 upstream.

There is another problem: broken backslash sequences trigger a
DeprecationWarning. This makes the package unusable with pytest.

Patch: https://github.com/scott-griffiths/bitstring/pull/206


-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable'), (550, 'experimental'), (550, 
'oldstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-bitstring depends on:
ii  python3  3.8.2-3

python3-bitstring recommends no packages.

Versions of packages python3-bitstring suggests:
pn  python-bitstring-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-bitstring
Source-Version: 3.1.7-2
Done: Graham Inggs 

We believe that the bug you reported is fixed in the latest version of
python-bitstring, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated python-bitstring 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: Sun, 01 Nov 2020 12:18:49 +
Source: python-bitstring
Architecture: source
Version: 3.1.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Graham Inggs 
Closes: 963551
Changes:
 python-bitstring (3.1.7-2) unstable; urgency=medium
 .
   * Team upload
   * Switch to debhelper 13
   * Set Rules-Requires-Root: no
   * Fix invalid escape sequences (Closes: #963551)
   * Drop trailing whitespace from debian/control
   * Update debian/copyright
   * Drop unnecessary Testsuite: autopkgtest field
   * Replace deprecated ADTTMP variable with AUTOPKGTEST_TMP
   * Bump Standards-Version to 4.5.0, no changes
Checksums-Sha1:
 0844666b1c7fad861ab5d1f8fe30f1b981759f7a  python-bitstring_3.1.7-2.dsc
 596188cb5838ffdf0e887855bcdb04fc710a0218 6576 
python-bitstring_3.1.7-2.debian.tar.xz
Checksums-Sha256:
 fc6bf8600f329cad6f5f7dea3a6759a3f239815c1ad83d1d93606ed852084bd0  
python-bitstring_3.1.7-2.dsc
 aff52447f4f205f08e531241ccbe8fa537ba2db4530345b37448760b73f45486 6576 
python-bitstring_3.1.7-2.debian.tar.xz
Files:
 0187603b9496404ad4243e93443caacf  python optional 
python-bitstring_3.1.7-2.dsc
 5156c641978d5d4738668f291c492905 6576 python optional 
python-bitstring_3.1.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAl+euBQACgkQr8/sjmac
4cL5CxAAkPxK7rN/AUA7ziMEdvRN+35fkHYCKXGW3HrRAECYl/4C2NzTc/TcRZUj
oXHF3Iezo4AytBjaurWFL2yVMCMfd3e75L3RgO/NNYLzkUBCXgiF4J2oA6nQxOiL
4G72beFAK3Ppf8PdRWJpW28vRAKeaWb3UY+V2IdFGIsYr5xKzqAtJqKXwVTYsIcc
LgPQumusSlkLIUUWs4Dvz4appRwxoUcZOYj3Kg/G/htegiIfvzPEjCFFTjIyWYMv
Y/gIshCWkHdroOh2XCmrFbr7K2XkE3KSiFRFFNRCVroo63X5OJhe8jkYSxc4edlJ
7S8z8KNAWqBHS6BLqhFE9aO4ZBLS2SSjBMrFgteoT0aQE3LIq4LLDcBMjkguVKuy
l8bImJ7IAFTZgm1Tf1bkkgxWEptv3QOiRARSc6qbvw01+48APO6NaSfUS+fzC+2h
+OmmAaqeIMlPPhcbPxLV5uDIg+GCtC2uxOyJlw31I1cXorE9eQL9pWSZ0dfDCw5y
4xvNuzG+Hjpz4jBxOWwiiHBwhtiiYGTmmwVhXiyZVE4k7t1XRuC7IlofjhLs1In0
Tf2snhw0x27Lj9FzRxqcnNo1meKZbhv5I3OCdrS9rVAGNhLU3cY4U3EPE/5ndxdU
JNJ5YkJBjQwQeLypZ7E9DdESPVgTnAicZcOHZytLMBUHLPpg4sU=
=j9UY
-END PGP SIGNATURE End Message ---

Bug#973359: marked as done (booth: autopkgtest timed out on armhf and i386)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 13:48:21 +
with message-id 
and subject line Bug#973359: fixed in booth 1.0-205-gc9e90fe-2
has caused the Debian Bug report #973359,
regarding booth: autopkgtest timed out on armhf and i386
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.)


-- 
973359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: booth
Version: 1.0-205-gc9e90fe-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout fails-always

Dear maintainers,

booth has an autopkgtest, great. On ci.d.n we aremonitoring tests that
take extremely long to run, and today I noticed booth. It seems to wait
for a response that is never coming.

Could you please check and if possible make the autopkgtest robust
against these failure mode to not waste precious time on the
infrastructure? I have no clue, but maybe these are even real failure
modes you want to improve. Please be aware that armhf and i386
autopkgtests run in lxc containers on a different host architecture (not
sure if that is related at all, but just so you know). Also, if these
tests can't be made to work on those architecture, we recently added
support to autopkgtest to declare which architectures are supported
(announcement to d-d-a coming up shortly).

Thanks for considering. I'll put this package on the ci.d.n denylist for
armhf and i386 until this bug has been resolved.

Paul

https://ci.debian.net/data/autopkgtest/testing/i386/b/booth/7795114/log.gz
https://ci.debian.net/data/autopkgtest/testing/armhf/b/booth/7802544/log.gz

=== status ===
booth_lockpid=1880 booth_lockfile='/var/run/booth//booth.pid'
booth_pid=1880 booth_state=started booth_type=site
booth_cfg_name='booth' booth_id=1696554816 booth_addr_string='127.0.0.1'
booth_port=9929
ticket: ticket-A, leader: NONE

=== grant ===
Oct 29 00:00:10 ci-302-eebbc9ed booth: [1891]: info: grant request sent,
waiting for the result ...
autopkgtest [02:46:46]: ERROR: timed out on command "su -s /bin/bash
root -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 ||
true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.4xyiwrju/downtmp/build.7Q1/src"; mkdir
-p -m 1777 -- "/tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-artifacts";
export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.4xyiwrju/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.4xyiwrju/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=32; unset
LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY
LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; export
AUTOPKGTEST_NORMAL_USER=debci; export ADT_NORMAL_USER=debci; chmod +x
/tmp/autopkgtest-lxc.4xyiwrju/downtmp/build.7Q1/src/debian/tests/boothd;
touch /tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-stdout
/tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-stderr;
/tmp/autopkgtest-lxc.4xyiwrju/downtmp/build.7Q1/src/debian/tests/boothd
2> >(tee -a /tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-stderr >&2) >
>(tee -a /tmp/autopkgtest-lxc.4xyiwrju/downtmp/boothd-stdout);" (kind: test)
autopkgtest [02:46:47]: test boothd: ---]
autopkgtest [02:46:47]: test boothd:  - - - - - - - - - - results - - -
- - - - - - -
boothd   FAIL timed out



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: booth
Source-Version: 1.0-205-gc9e90fe-2
Done: Valentin Vidic 

We believe that the bug you reported is fixed in the latest version of
booth, 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 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Valentin Vidic  (supplier of updated booth 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)


---

Processed: RFS: cwm/6.7-1 -- lightweight and efficient window manager for X11

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 962806
Bug #962806 [sponsorship-requests] RFS: cwm/6.7-1 -- lightweight and efficient 
window manager for X11
Marked Bug as done
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
962806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close #973373
Bug #973373 [blueman] blueman: Blueman requires authentication twice on start-up
Marked Bug as done
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
973373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#970558: marked as done (openblas: segfault in zgemm_oncopy_EMAG8180 during sagemath test on arm64)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 12:33:33 +
with message-id 
and subject line Bug#970558: fixed in openblas 0.3.12+ds-2
has caused the Debian Bug report #970558,
regarding openblas: segfault in zgemm_oncopy_EMAG8180 during sagemath test on 
arm64
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.)


-- 
970558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenblas0
Version: 0.3.10+ds-3
Severity: normal

Hi,

a sagemath test segfaulted in libopenblas.so.0 / zgemm_oncopy_EMAG8180 when 
building on arm-ubc-01.debian.org,
see 
https://buildd.debian.org/status/fetch.php?pkg=sagemath&arch=arm64&ver=9.2%7Ebeta12-1&stamp=159992&raw=0

openblas was called by numpy and the issue looks similar to #966175 where the 
segfault occurred in dgemm_oncopy_HASWELL.

Extract from the stack backtrace:

#5  0xab2fe3b0 in zgemm_oncopy_EMAG8180 () from 
/usr/lib/aarch64-linux-gnu/libopenblas.so.0
#6  0xaaac8430 in zgetrf_single () from 
/usr/lib/aarch64-linux-gnu/libopenblas.so.0
#7  0xaa064f3c in zgesv_ () from 
/usr/lib/aarch64-linux-gnu/liblapack.so.3
#8  0xaa00f330 in ?? () from 
/usr/lib/python3/dist-packages/numpy/linalg/_umath_linalg.cpython-38-aarch64-linux-gnu.so

Best,
Tobias
--- End Message ---
--- Begin Message ---
Source: openblas
Source-Version: 0.3.12+ds-2
Done: =?utf-8?q?S=C3=A9bastien_Villemot?= 

We believe that the bug you reported is fixed in the latest version of
openblas, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated openblas 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: Sun, 01 Nov 2020 10:47:26 +0100
Source: openblas
Architecture: source
Version: 0.3.12+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Closes: 970558
Changes:
 openblas (0.3.12+ds-2) unstable; urgency=medium
 .
   * reunify-arm64-buffersize.patch: new patch from upstream (Closes: #970558)
Checksums-Sha1:
 1f03cba1122862a0b3736a25e7698cc233af9694 4891 openblas_0.3.12+ds-2.dsc
 6a2ef4423561ff527f5e9cabc610a8488c4b2863 22992 
openblas_0.3.12+ds-2.debian.tar.xz
 730bf4de37b81164888a6dbae2d8d78360c63b0a 13984 
openblas_0.3.12+ds-2_amd64.buildinfo
Checksums-Sha256:
 11ed7c2ff857591ac7d153d100a7881ff97ec0b8d67d1cc1464b625fed515500 4891 
openblas_0.3.12+ds-2.dsc
 f6515b9cda063c35ae415161307d5d38047df35c9e47a4b9bcf60db95b342f96 22992 
openblas_0.3.12+ds-2.debian.tar.xz
 ad1b64513b9c26c99e08a5c81f5ac9ccd690177e382f01f03e4b4714c3bbd01d 13984 
openblas_0.3.12+ds-2_amd64.buildinfo
Files:
 f95fdd02ced14d8b15653747d6cffb1b 4891 devel optional openblas_0.3.12+ds-2.dsc
 651d1f39ce0be6ecae1f40a29ce9c9e1 22992 devel optional 
openblas_0.3.12+ds-2.debian.tar.xz
 ef17726961d0bf35bb3eec2acfe65853 13984 devel optional 
openblas_0.3.12+ds-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAl+eqGkACgkQLOzpNQ7O
vkoJ6Q//Xmtcg2rqdlOmN7CSo9aTB3bx9F7+EvJcFFkknikjupOEA/U/d/0mYHIe
zW7xh967TY0qTufRaaocl3JdX1mnMWkTWz7n0QoOrsSYrRL5uUuTLGbYoCuPqmtB
LFNGdsnAuxSuky0f5rc6KFbb+SN5G1mVSZ5nys7Qc40p+Opad9+UXxOGUGKAc3Cj
+t9m7D3LHZknWgyyrSDXxDjGc/lLUoJaOylibeCtQS99pRUCvNvpW8/TSVqas98h
WgCa8wFKyyhJlZuUKSQFJ6V3JMjZn9g0NDwyZAhy3bb5R53hI8a73bsz42YcEnA9
+LbcjvkKW4mQc1TmLS+elTLdM5OxmZ0dgrU/Nw0tCy2XPuntd9EnDZ/0Utv5YcAY
FH5E9d05Jnc1vAd8nUp69VzEJWuwbU5FU9By28D05Xwr6ygbdXo52R0ca94/YQXb
xEbN62s2GdiuLsoDcDALYXTtstBzyyi9/4aZUgiWEOE6EECJn/SDPed2s/S1priv
sqVebLgg7MArnCiQJDupIM18Y+bqrMkUGmI9KXQz8OpXI2xPkZyGzC3K5B9cvK+Z
w4/ETaY7cAMYgSBdo42XmUMclCejpp975IHPFOnMf1jW01LlHlyV5JvxtlZ8Zg91
dN4inrVtEP430fg1CQ2o0BFYdmpEGa7a/yxT4Yij8q65m+EZ4Pk=
=3J/d
-END PGP SIGNATURE End Message ---

Bug#973484: marked as done (qemu-system-arm: -machine virt does not allow two serial port for arm emulation)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 20:56:48 +0900 (JST)
with message-id 
<20201101.205648.1793002892738184147.ryuta...@ict.e.titech.ac.jp>
and subject line Re: Bug#973484: qemu-system-arm: -machine virt does not allow 
two serial port for arm emulation
has caused the Debian Bug report #973484,
regarding qemu-system-arm: -machine virt does not allow two serial port for arm 
emulation
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.)


-- 
973484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-arm
Version: 1:5.1+dfsg-4+b1
Severity: wishlist
Tags: upstream
Control: block 973038 by -1

Dear Maintainer,

I am trying to make autopkgtest-virt-qemu usable on arm64 as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038

autopkgtest-virt-qemu needs two serial ports in the emulation.
But qemu-system-aarch64 only allows at most one serial port.
This is an upstream design decision as
https://lists.nongnu.org/archive/html/qemu-discuss/2018-11/msg1.html

An unofficial patch is available at
https://unix.stackexchange.com/questions/479085/can-qemu-m-virt-on-arm-aarch64-have-multiple-serial-ttys-like-such-as-pl011-t

Best regards, Ryutaroh Matsumoto


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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 qemu-system-arm depends on:
ii  libaio1 0.3.112-8
ii  libc6   2.31-4
ii  libcapstone34.0.1+really+3.0.5-2+b1
ii  libepoxy0   1.5.4-1
ii  libfdt1 1.6.0-1
ii  libgbm1 20.1.9-1
ii  libgcc-s1   10.2.0-15
ii  libglib2.0-02.66.1-2
ii  libgnutls30 3.6.15-4
ii  libibverbs1 31.0-1
ii  libjpeg62-turbo 1:2.0.5-1.1
ii  libnettle8  3.6-2
ii  libnuma12.0.12-1+b1
ii  libpixman-1-0   0.36.0-1
ii  libpmem11.9.1-3
ii  libpng16-16 1.6.37-3
ii  librdmacm1  31.0-1
ii  libsasl2-2  2.1.27+dfsg-2
ii  libseccomp2 2.4.4-1+b1
ii  libslirp0   4.3.1-1
ii  libspice-server10.14.3-1
ii  libstdc++6  10.2.0-15
ii  liburing1   0.7-1
ii  libusb-1.0-02:1.0.23-2
ii  libvdeplug2 4.0.1-2
ii  libvirglrenderer1   0.8.2-4
ii  qemu-system-common  1:5.1+dfsg-4+b1
ii  qemu-system-data1:5.1+dfsg-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages qemu-system-arm recommends:
ii  ipxe-qemu 1.0.0+git-20190125.36a4c85-5
ii  qemu-efi-aarch64  2020.08-1
ii  qemu-efi-arm  2020.08-1
pn  qemu-system-gui   
ii  qemu-utils1:5.1+dfsg-4+b1

Versions of packages qemu-system-arm suggests:
pn  qemu-block-extra  
pn  samba 
pn  vde2  

-- no debconf information
--- End Message ---
--- Begin Message ---
By giving "-device pci-serial-2x,chardev1=ttyS0,chardev2=ttyS1"
to qemu-system-aarch64, one can use two serial ports...

Ryutaroh--- End Message ---

Bug#972317: marked as done (FTBFS on ppc64el)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 12:04:37 +
with message-id 
and subject line Bug#972317: fixed in llvm-toolchain-11 1:11.0.0-4
has caused the Debian Bug report #972317,
regarding FTBFS on ppc64el
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.)


-- 
972317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-9
Version: 1:9.0.1-14
Severity: serious
Tags: ftbfs

Dear Maintainer,

Your package FTBFS on ppc64el:

  https://buildd.debian.org/status/package.php?p=llvm-toolchain-9

The rebuild was triggered by the update of OCaml from 4.08.1 to
4.11.1, but the error looks independent (I might be wrong).

The build log ends with:
> clang-9: error: unable to execute command: Segmentation fault
> clang-9: error: clang frontend command failed due to signal (use -v to 
> see invocation)
> clang version 9.0.1-14+b1 
> Target: powerpc64le-unknown-linux-gnu
> Thread model: posix
> InstalledDir: /<>/build-llvm/tools/clang/stage2-bins/bin
> clang-9: note: diagnostic msg: PLEASE submit a bug report to 
> https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, 
> and associated run script.
> clang-9: note: diagnostic msg: 
> 
> 
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> clang-9: note: diagnostic msg: /tmp/testCXXCompiler-2f55c9.cpp
> clang-9: note: diagnostic msg: /tmp/testCXXCompiler-2f55c9.sh
> clang-9: note: diagnostic msg: 
> 
> 
> gmake[3]: *** [CMakeFiles/cmTC_2f83f.dir/build.make:85: 
> CMakeFiles/cmTC_2f83f.dir/testCXXCompiler.cxx.o] Error 254
> gmake[3]: Leaving directory 
> '/<>/libcxxabi/build/CMakeFiles/CMakeTmp'
> gmake[2]: *** [Makefile:140: cmTC_2f83f/fast] Error 2
> gmake[2]: Leaving directory 
> '/<>/libcxxabi/build/CMakeFiles/CMakeTmp'
> 
> 
> 
>   
> 
>   CMake will not be able to correctly generate this project.
> Call Stack (most recent call first):
>   CMakeLists.txt:21 (project)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/libcxxabi/build/CMakeFiles/CMakeOutput.log".
> See also "/<>/libcxxabi/build/CMakeFiles/CMakeError.log".
> make[1]: *** [debian/rules:438: debian-libcxx-build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:282: binary-arch] Error 2
> dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
> status 2


Cheers,

-- 
Stéphane

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-11
Source-Version: 1:11.0.0-4
Done: Sylvestre Ledru 

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-11, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-11 
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, 31 Oct 2020 21:49:01 +0100
Source: llvm-toolchain-11
Architecture: source
Version: 1:11.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 972317
Changes:
 llvm-toolchain-11 (1:11.0.0-4) unstable; urgency=medium
 .
   * Cherry-pick some fixes from
 https://github.com/opencollab/llvm-toolchain-integration-test-suite/
   * Only install hwasan_symbolize when found
   * Don't use gold on ppc64el. It fails to build in that case
 (Closes: #972317)
 .
   [ John Paul Adrian Glaubitz ]
   * Limit maximum parallel link jobs to 4 on sparc and sparc64
Checksums-Sha1:
 7

Bug#972700: marked as done (ITP: ruby-gitlab-fog-azure-rm -- Azure Blob Storage with CarrierWave and Fog)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 12:00:08 +
with message-id 
and subject line Bug#972700: fixed in ruby-gitlab-fog-azure-rm 0.7.0-1
has caused the Debian Bug report #972700,
regarding ITP: ruby-gitlab-fog-azure-rm -- Azure Blob Storage with CarrierWave 
and Fog
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.)


-- 
972700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

Package https://rubygems.org/gems/gitlab-fog-azure-rm

New dependency for gitlab 13.3.0
--- End Message ---
--- Begin Message ---
Source: ruby-gitlab-fog-azure-rm
Source-Version: 0.7.0-1
Done: Pirate Praveen 

We believe that the bug you reported is fixed in the latest version of
ruby-gitlab-fog-azure-rm, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated 
ruby-gitlab-fog-azure-rm 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: Sun, 01 Nov 2020 12:39:03 +0530
Source: ruby-gitlab-fog-azure-rm
Binary: ruby-gitlab-fog-azure-rm
Architecture: source all
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Pirate Praveen 
Description:
 ruby-gitlab-fog-azure-rm - Azure Blob Storage with CarrierWave and Fog
Closes: 972700
Changes:
 ruby-gitlab-fog-azure-rm (0.7.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #972700)
Checksums-Sha1:
 fe738e81970063b8d76ef6099e041fb4b385fbe2 2311 
ruby-gitlab-fog-azure-rm_0.7.0-1.dsc
 0b2f89b6b361fd03b9afe7fed4998f1fe0b216b0 58426 
ruby-gitlab-fog-azure-rm_0.7.0.orig.tar.gz
 dfea4415427d70b9e4aeb96316a575fdee661dba 2548 
ruby-gitlab-fog-azure-rm_0.7.0-1.debian.tar.xz
 622f5b29415984129dce59562dd0c18ac742d52e 31824 
ruby-gitlab-fog-azure-rm_0.7.0-1_all.deb
 9ea0ac83658c9a35b382f8b48d868aedf7c934fb 9962 
ruby-gitlab-fog-azure-rm_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 d9927859265f6d10a3512e7464bf042188ec3c0e115df12942e353a7bce89408 2311 
ruby-gitlab-fog-azure-rm_0.7.0-1.dsc
 395b8ae33020f480e1181f746aa9778ed35c404433fb6a026d6c20ebaa749eb1 58426 
ruby-gitlab-fog-azure-rm_0.7.0.orig.tar.gz
 f47c3502122003ee7b4a036a2fa067b62ba35f7e6bdbf536ff647a56f161defc 2548 
ruby-gitlab-fog-azure-rm_0.7.0-1.debian.tar.xz
 5e227eec1150ca78410eb754481272efdd4f81e9f7a49b83903108c61e88d871 31824 
ruby-gitlab-fog-azure-rm_0.7.0-1_all.deb
 71773bbf701e539ad29bd974fc55c620006b26e03376c0d69420c5f71ab20d53 9962 
ruby-gitlab-fog-azure-rm_0.7.0-1_amd64.buildinfo
Files:
 379ea8578d7024dea899a7ee2a36da5d 2311 ruby optional 
ruby-gitlab-fog-azure-rm_0.7.0-1.dsc
 44411e4b3dfb9a7a21d17c34b987bc1e 58426 ruby optional 
ruby-gitlab-fog-azure-rm_0.7.0.orig.tar.gz
 722a4660122343d7d68aa84bf588d542 2548 ruby optional 
ruby-gitlab-fog-azure-rm_0.7.0-1.debian.tar.xz
 25fb4187dff5c63b3478acfb18673651 31824 ruby optional 
ruby-gitlab-fog-azure-rm_0.7.0-1_all.deb
 3f14b3324f8c0052199bf87eced9a146 9962 ruby optional 
ruby-gitlab-fog-azure-rm_0.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl+efqcACgkQj1PgGTsp
S3UyqA/+OEO1ktCHJf6Q36IfLc6Fhg1Xudqsv+4PwE8kcDrFrt1aCnoiLO8oPtvC
Eh1CKzh1zugcZAOVs16pW2yivdUkiNFkUvW/nyHTUq2ihg4HoCxOpRdTOw3lx0AB
2OTKfw7YKYaa2GvrMBDjlKiEVzV8sduxSOzNxJQfdJTU6KqERKHsFTny2LZBtiji
+H0UCvCZwHNPGhjAygvph9u8RGRpNVsqVSgxZMKy1m/xhKnhHy+MiW2n9aZc04YZ
+leVtjdtNre/KqMVfjpJ6AIHz6qjZ3FN6YoKcRZv2wLzNWx5iuM6SdQHnIOdj2do
evl5qrOMAPbP0M0WNcGb+sVQ+fuYLjs9G7LPwtG6VHl5qf8gWqpTKJdBN4QpMA+Q
5RHoS6jTvRDqodtw0Mv0QOwXiDHxSjWjSUiO/yvkNWYt+L+QpTYDQRDWWhNdhuD4
rxYVSr+wE55GXkkzWNq52UMBAoR1ypObFNoyZwVQQzAfEd/y7ckbS/eR8kg0w/Td
Qj4h7UDetNVpGA9LcBLFQhVgH5Lw3U42WD7eCfGYRNs++vxKzs/pxP+oN1IZtiIT
sc6qjSfQIjreQ+aYO0Ws2PWuvJJgFtgcDItp15p8aaZluawWb2/hJUnHg5UHm38N
l/rcpq6C1tFq6e11kGFZFNI/JvOYTVgoB7C4cS0LGNBb1YDQ9D4=
=1fJY
-END PGP SIGNATURE End Message ---

Bug#973068: marked as done (undercover-el: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 11:05:12 +
with message-id 
and subject line Bug#973068: fixed in undercover-el 0.7.0-2
has caused the Debian Bug report #973068,
regarding undercover-el: 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.)


-- 
973068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undercover-el
Version: 0.7.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package undercover-el
> dpkg-buildpackage: info: source version 0.7.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Lev Lamberov 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with elpa
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building undercover-el using existing 
> ./undercover-el_0.7.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building undercover-el in 
> undercover-el_0.7.0-1.debian.tar.xz
> dpkg-source: info: building undercover-el in undercover-el_0.7.0-1.dsc
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -L test --eval "(load \"undercover.el\")" -l 
> test/first-example-library-test.el --eval \(ert-run-tests-batch-and-exit\)
> Loading /<>/undercover.el (source)...
> Package cl is deprecated
> Running 10 tests (2020-10-27 12:25:27+, selector ‘t’)
> Test test-001/edebug-handlers-are-setted backtrace:
>   signal(ert-test-failed (((should (eq 'undercover--stop-point-before 
>   ert-fail(((should (eq 'undercover--stop-point-before (symbol-functio
>   (if (unwind-protect (setq value-2 (apply fn-0 args-1)) (setq form-de
>   (let (form-description-4) (if (unwind-protect (setq value-2 (apply f
>   (let ((value-2 'ert-form-evaluation-aborted-3)) (let (form-descripti
>   (let* ((fn-0 #'eq) (args-1 (condition-case err (let ((signal-hook-fu
>   (closure (t) nil (let* ((fn-0 #'eq) (args-1 (condition-case err (let
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name test-001/edebug-handlers-are-setted :
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests [#s(ert-test 
>   ert-run-tests(t #f(compiled-function (event-type &rest event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   eval((ert-run-tests-batch-and-exit) t)
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test test-001/edebug-handlers-are-setted condition:
> (ert-test-failed
>  ((should
>(eq 'undercover--stop-point-before
>   (symbol-function ...)))
>   :form
>   (eq undercover--stop-point-before nil)
>   :value nil))
>FAILED   1/10  test-001/edebug-handlers-are-setted (0.000124 sec)
>passed   2/10  test-002/result-is-correct (0.001455 sec)
>passed   3/10  test-003/functions-are-covered (0.54 sec)
>passed   4/10  test-004/check-distance-stop-points-number-of-covers 
> (0.000121 sec)
>passed   5/10  test-005/check-coverage-statistics (0.001180 sec)
>passed   6/10  test-006/check-environment-variables (0.68 sec)
>passed   7/10  test-008/should-error (0.000867 sec)
>passed   8/10  test-009/check-simplecov-report (0.003059 sec)
>passed   9/10  test-010/check-text-report (0.001166 sec)
>passed  10/10  test-011/check-text-report-file (0.001415 sec)
> 
> Ran 10 tests, 9 results as expected, 1 unexpected (2020-10-27 12:25:27+, 
> 0.107047 sec)
> 
> 1 unexpected results:
>FAILED  test-001/edebug-handlers-are-setted
> 
> Error: (error "Unsupported report-format")
> dh_elpa_test: error: emacs -batch -Q -l package --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa\")" --eval 
> "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa-src\"

Bug#971512: marked as done (ITP: rpma -- remote pmem access library)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 11:00:14 +
with message-id 
and subject line Bug#971512: fixed in rpma 0.9.0-1
has caused the Debian Bug report #971512,
regarding ITP: rpma -- remote pmem access library
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.)


-- 
971512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Adam Borowski 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: rpma
  Version : 0.9
  Upstream Author : Intel
* URL : https://github.com/pmem/rpma
* License : BSD-3
  Programming Lang: C
  Description : remote pmem access library

 The Remote Persistent Memory Access (RPMA) is a C library to simplify
 accessing persistent memory devices on remote hosts over Remote Direct
 Memory Access (RDMA).

This version isn't fit for production use yet, but should be useful for
adventureous users for development and/or feedback.  Thus, 0.9 will go
to rc-buggy.
--- End Message ---
--- Begin Message ---
Source: rpma
Source-Version: 0.9.0-1
Done: Adam Borowski 

We believe that the bug you reported is fixed in the latest version of
rpma, 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.
Adam Borowski  (supplier of updated rpma 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: Wed, 21 Oct 2020 06:23:36 +0200
Source: rpma
Binary: librpma-dev librpma0 librpma0-dbgsym
Architecture: source amd64
Version: 0.9.0-1
Distribution: experimental
Urgency: medium
Maintainer: Adam Borowski 
Changed-By: Adam Borowski 
Description:
 librpma-dev - remote pmem access library (headers)
 librpma0   - remote pmem access library (runtime)
Closes: 971512
Changes:
 rpma (0.9.0-1) experimental; urgency=medium
 .
   * Initial release (Closes: #971512)
Checksums-Sha1:
 4039029f201f796dc2bc5b950df98b9f4edf30c0 1997 rpma_0.9.0-1.dsc
 713cd91b9f227e0a2e85e08262de7440bcfb45a6 176726 rpma_0.9.0.orig.tar.gz
 dc2706755d5ccb44da41f62f202f654977dd8b85 8280 rpma_0.9.0-1.debian.tar.xz
 7daed57b5804d5f32206c69e9d4cf33a99df5c39 63108 librpma-dev_0.9.0-1_amd64.deb
 873c97f13e9d4d4217391e2aae633113cdf784b8 50636 
librpma0-dbgsym_0.9.0-1_amd64.deb
 04fedc4b47dc15688ab2cee2f1e5c719e0961b42 22976 librpma0_0.9.0-1_amd64.deb
 234f70c9653a81669261de7a5ecb07eb938ad830 8279 rpma_0.9.0-1_amd64.buildinfo
Checksums-Sha256:
 00f1c23278c3534b8a998f38f0b3aaf1b6aff06e145a5f5a0376ab1f7fadf8af 1997 
rpma_0.9.0-1.dsc
 d15f3fbbfdfbfdc8a113d276996d048284bb38fa13f5ef099184ff0fad21c7f6 176726 
rpma_0.9.0.orig.tar.gz
 e3ea7f97d5397dedbb1f6e19415efcb3de8f6ec9de819605b3815a151e53faa0 8280 
rpma_0.9.0-1.debian.tar.xz
 d8851bde0160f85f793b08d5ac9c94c2c15df9cd9b9993dbeed5876f88cd6988 63108 
librpma-dev_0.9.0-1_amd64.deb
 912928c4a5a274e31e25acc1745e95c6317e3ff216810230bc88cad1f71cac5c 50636 
librpma0-dbgsym_0.9.0-1_amd64.deb
 890eefe7bb4df589c4a50897e327f4110877d08b4ce8c74f1bdcdb5565db8e0f 22976 
librpma0_0.9.0-1_amd64.deb
 0a110ebc8845fe11ee0e64e4308b0b19f09efc617ea074c3be1b76c693f22372 8279 
rpma_0.9.0-1_amd64.buildinfo
Files:
 817cfee980c1f74f4a0dc586391b70ef 1997 libs optional rpma_0.9.0-1.dsc
 01cdc6af49998f92703749efab6d2c1c 176726 libs optional rpma_0.9.0.orig.tar.gz
 afcb14a12434f71fed0e40c1d869708c 8280 libs optional rpma_0.9.0-1.debian.tar.xz
 34573cd9d4e6f5ffb21b6d866fea2a6a 63108 libdevel optional 
librpma-dev_0.9.0-1_amd64.deb
 b5196d29f57f6feae4a376e101369062 50636 debug optional 
librpma0-dbgsym_0.9.0-1_amd64.deb
 1bb6927513a46f9e7f7078bd0915f53f 22976 libs optional librpma0_0.9.0-1_amd64.deb
 bf6445d459abbae8a435a75d6f0e0d8e 8279 libs optional 
rpma_0.9.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl+edY0ACgkQweDZLphv
fH7HERAAto6A6wA2qSnASd5M5ENzWr/sRYSX+A/tM7bQ7Gk/ztrHPoNG//9+azGh
bgBtfPp0OGxccmflLdXXbDCC6tntnAioJDu/BRwdEPHLvaUy/8ttV3hZHV0ydCQJ
ho99ydb51cGMyejwKmgYxJWaiUTUvhzzOfp/fYh9GtwM+81bJUvG/CUGjSf1gCmM
FRTN1vkfCuE1cF1TXaW5uza6bK1UvOXMJULUlvIuafGmty6mo2vHonctvLgdUNG3
+MNZXcFo8kEdGZF8LyDGf+bku48Re0250mPTV

Bug#970938: marked as done (ruby-gon: CVE-2020-25739)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 10:49:16 +
with message-id 
and subject line Bug#970938: fixed in ruby-gon 6.4.0-1
has caused the Debian Bug report #970938,
regarding ruby-gon: CVE-2020-25739
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.)


-- 
970938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gon
Version: 6.3.2-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for ruby-gon.

CVE-2020-25739[0]:
| An issue was discovered in the gon gem before gon-6.4.0 for Ruby.
| MultiJson does not honor the escape_mode parameter to escape fields as
| an XSS protection mechanism. To mitigate, json_dumper.rb in gon now
| does escaping for XSS by default without relying on MultiJson.


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-25739
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25739
[1] https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ruby-gon
Source-Version: 6.4.0-1
Done: Sruthi Chandran 

We believe that the bug you reported is fixed in the latest version of
ruby-gon, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated ruby-gon 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: Sun, 01 Nov 2020 15:46:41 +0530
Source: ruby-gon
Architecture: source
Version: 6.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Sruthi Chandran 
Closes: 965269 970938
Changes:
 ruby-gon (6.4.0-1) unstable; urgency=medium
 .
   [ Sruthi Chandran ]
   * Team upload
   * New upstream release (Closes: #965269, #970938) (Fixes: CVE-2020-25739)
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 9728f746f4959af29f3e1538e4e7d4522869d622 1943 ruby-gon_6.4.0-1.dsc
 ed3a9745d1821233725a63671dbdae5843dfb046 153597 ruby-gon_6.4.0.orig.tar.gz
 9e36beb1cd960530dd53aa9b36528e2235a47eb3 4516 ruby-gon_6.4.0-1.debian.tar.xz
 bad6b983f4d96cc63bba00d3b1688377e5c0845c 9951 ruby-gon_6.4.0-1_amd64.buildinfo
Checksums-Sha256:
 c5dd897fc382aa0c2d185bde175a496c19bf7f0f724ef9b23ace455423b315eb 1943 
ruby-gon_6.4.0-1.dsc
 41b53c2d4cdb54ed912473a132add63236b13b198d656dd73673c9f1d76c90e4 153597 
ruby-gon_6.4.0.orig.tar.gz
 94cb6343cd3473fe31ebf76dd78cb9359bba405fc630a6a54f3e5688811645c3 4516 
ruby-gon_6.4.0-1.debian.tar.xz
 1a623f5919e6e345f6e06208015e549ad9affe1e2f9b23f7f8633289695281c1 9951 
ruby-gon_6.4.0-1_amd64.buildinfo
Files:
 d49d31845242cc9d7738d42fb3b85b4d 1943 ruby optional ruby-gon_6.4.0-1.dsc
 e0d52be4e90691c043a885000298bac6 153597 ruby optional 
ruby-gon_6.4.0.orig.tar.gz
 28996ff333bdf4cc7b747dd5a4b83549 4516 ruby optional 
ruby-gon_6.4.0-1.debian.tar.xz
 181a632b091f067d24a1a214d0816d50 9951 ruby optional 
ruby-gon_6.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAl+ejeAACgkQx+ob4VdN
7V0A0QwAjbgNwdp07y9FSfJqbnrObXUgW8Ct4vlpIFtfVf15envgGtx1b0BWTkzQ
TOaikED9WrZEbHCbOn6JEOOtqbkA1zTKpaVDPiW1O3hpJe4C+hbBJDA5dZXqMsDA
yb8boVPvioSVspV46j1+JG+x6/bDEJT11kFzir0rf11Hwm0sLzy6M21FN9B6Z4cq
Y5pJGD+s97j7kdtmqoCFE9qGlnsIKK8GH+nL5lcS/Qgq3bgf4KLpTMYvP0/K+nBu
+oraSTax08Ne0aO/qxnO4oQi6Mfg1dTMXntjufG7LsSjNz7ZI/ga7M1pbvtJLOv9
Y1hv/Yr4UBFiznoI05orMMY4RC+TdeD7ujWiCwJGLYVxE0C3CMqhz2W4FLcKkFa9
N/wJRqqqaJ1v8F2VHgvAWiKegzCt4nwGwRr6PFZWxo9NA8bJvg5qBG8fhMLZ+fC2
o773aDykKNH1RtSAPi8E4jyLZqYyKQ2gwDCATxOomt2QHhQnupxJeNlXv9eMjKyg
UwfpyzUL
=+XUG
-END PGP SIGNATURE End Message ---

Bug#965269: marked as done (ruby-gon: ftbfs with rails 6 in experimental)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 10:49:16 +
with message-id 
and subject line Bug#965269: fixed in ruby-gon 6.4.0-1
has caused the Debian Bug report #965269,
regarding ruby-gon: ftbfs with rails 6 in experimental
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.)


-- 
965269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ruby-gon
Version: 6.3.2-1
Severity: important
User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition
Control: forwarded -1 https://github.com/gazay/gon/issues/262

Hi,

This package's autopkgtest and rebuilds failed with rails 6 currently in
experimental. rails 6 will be uploaded to unstable in two weeks, so
please make sure this package is ready for rails 6. The severity of
this bug will be raised to serious after rails 6 is uploaded to
unstable.


Relevant errors,

Failures:

 1) Gon#include_gon outputs correct js with a script string
Failure/Error:
  expect(@base.include_gon).to eq(wrap_script(
'window.gon={};' +
%Q(gon.str="#{escaped_str}";))
  )

  expected: 
"\n//\n"
   got: 
"\n//\n"


  (compared using ==)

  Diff:
  @@ -1,6 +1,6 @@
   
   //  
-window.gon={};gon.str="\u003c/script\u003e\u003cscript\u003ealert('!')\u003c/script\u003e";
  +window.gon={};gon.str="alert('!')";
   //]]>
   
# ./spec/gon/basic_spec.rb:118:in `block (3 levels) in (required)>'


Finished in 0.82567 seconds (files took 3.3 seconds to load)
72 examples, 1 failure


Same is forwarded upstream https://github.com/gazay/gon/issues/262
--- End Message ---
--- Begin Message ---
Source: ruby-gon
Source-Version: 6.4.0-1
Done: Sruthi Chandran 

We believe that the bug you reported is fixed in the latest version of
ruby-gon, 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 965...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sruthi Chandran  (supplier of updated ruby-gon 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: Sun, 01 Nov 2020 15:46:41 +0530
Source: ruby-gon
Architecture: source
Version: 6.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Sruthi Chandran 
Closes: 965269 970938
Changes:
 ruby-gon (6.4.0-1) unstable; urgency=medium
 .
   [ Sruthi Chandran ]
   * Team upload
   * New upstream release (Closes: #965269, #970938) (Fixes: CVE-2020-25739)
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 9728f746f4959af29f3e1538e4e7d4522869d622 1943 ruby-gon_6.4.0-1.dsc
 ed3a9745d1821233725a63671dbdae5843dfb046 153597 ruby-gon_6.4.0.orig.tar.gz
 9e36beb1cd960530dd53aa9b36528e2235a47eb3 4516 ruby-gon_6.4.0-1.debian.tar.xz
 bad6b983f4d96cc63bba00d3b1688377e5c0845c 9951 ruby-gon_6.4.0-1_amd64.buildinfo
Checksums-Sha256:
 c5dd897fc382aa0c2d185bde175a496c19bf7f0f724ef9b23ace455423b315eb 1943 
ruby-gon_6.4.0-1.dsc
 41b53c2d4cdb54ed912473a132add63236b13b198d656dd73673c9f1d76c90e4 153597 
ruby-gon_6.4.0.orig.tar.gz
 94cb6343cd3473fe31ebf76dd78cb9359bba405fc630a6a54f3e5688811645c3 4516 
ruby-gon_6.4.0-1.debian.tar.xz
 1a623f5919e6e345f6e06208015e549ad9affe1e2f9b23f7f8633289695281c1 9951 
ruby-gon_6.4.0-1_amd64.buildinfo
Files:
 d49d31845242cc9d7738d42fb3b85b4d 1943 ruby optional ruby-gon_6.4.0-1.dsc
 e0d52be4e90691c043a885000298bac6 153597 ruby optional 
ruby-gon_6.4.0.orig.tar.gz
 28996ff333bdf4cc7b747dd5a4b83549 4516 ruby optional 
ruby-gon_6.4.0-1.debian.tar.xz
 181a632b091f067d24a1a214d0816d50 9951 ruby optional 
ruby-gon_6.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAl+ejeAACgkQx+ob4VdN
7V0A0QwAjbgNwdp07y9FSfJqbnrObXUgW8Ct4vlpIFtfVf15envgGtx1b0BWTkzQ
TOaikED9WrZEbHCbOn6JEOOtqbkA1zTKpaVDPiW1O3hpJe4C+hbBJDA5dZXqMsDA
yb8boVPvioSV

Bug#954460: marked as done (remove mentions of "volatile" repo from sources.list)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 10:33:34 +
with message-id 
and subject line Bug#954460: fixed in apt-setup 1:0.160
has caused the Debian Bug report #954460,
regarding remove mentions of "volatile" repo from sources.list
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.)


-- 
954460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-setup
Severity: wishlist
Tags: patch

Forwarding MR from salsa here:

I just found out that volatile is still mentioned in sources.list,
which I consider outdated and confusing for the end user. This MR
changes the wording of the comment in the sources.list to address
that.

Please feel free to change the wording as you find appropriate.

https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/3

patch:
https://salsa.debian.org/installer-team/apt-setup/-/merge_requests/3/diffs?commit_id=8de2bfd444c383867f31680de2b9dadbf61e601b

--
Samuel Henrique 
--- End Message ---
--- Begin Message ---
Source: apt-setup
Source-Version: 1:0.160
Done: Holger Wansing 

We believe that the bug you reported is fixed in the latest version of
apt-setup, 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 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Wansing  (supplier of updated apt-setup 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: Sun, 01 Nov 2020 11:12:07 +0100
Source: apt-setup
Architecture: source
Version: 1:0.160
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Closes: 954460
Changes:
 apt-setup (1:0.160) unstable; urgency=medium
 .
   [ Samuel Henrique ]
   * Remove mention of volatile repo from generated sources.list file.
 Closes: #954460
 .
   [ Updated translations ]
   * Bulgarian (bg.po) by Damyan Ivanov
   * Greek (el.po) by Vangelis Skarmoutsos
   * Basque (eu.po) by Iñaki Larrañaga Murgoitio
   * Persian (fa.po) by سهیل خانعلی‌پور
   * Italian (it.po) by Milo Casagrande
   * Marathi (mr.po) by Prachi Joshi
   * Punjabi (Gurmukhi) (pa.po) by Aman ALam
 .
   [ New translations ]
   * Kabyle (kab.po) by Slimane Selyan Amiri
   * Occitan (oc.po) by Quentin PAGÈS
Checksums-Sha1:
 94638f14df36b7dd331bbd6acc91a2f7f8c9c780 1823 apt-setup_0.160.dsc
 e3a8e80a1d2be518a4678f54d054f00034eff6e4 260512 apt-setup_0.160.tar.xz
 251967447c7ea9a88e921822024108f2beb54b88 6502 apt-setup_0.160_amd64.buildinfo
Checksums-Sha256:
 d5174f2d0d502927a6b740ab042c487886112a9164817348a10888f499dc6f5b 1823 
apt-setup_0.160.dsc
 dbea5cdba91d6a065d1eb817a255185a8346dcd9ab281b88c78bbaebe0b01856 260512 
apt-setup_0.160.tar.xz
 e34758ef4197991826eef850ca839e6d11900b75caa722c684b570b60e4cd336 6502 
apt-setup_0.160_amd64.buildinfo
Files:
 04a485dae55d3bdb1b6581659129c933 1823 debian-installer optional 
apt-setup_0.160.dsc
 1e166533dcbd878d3ca1a8a717ea4b23 260512 debian-installer optional 
apt-setup_0.160.tar.xz
 f42b2daaa8c7ca3b16359913bd6fa33e 6502 debian-installer optional 
apt-setup_0.160_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAl+ei5AVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2GK0P/1gkzSocnQK/eRRlsucYtrj0m1d4
hTWhDvPvm/wTJEb3qlD77Vb+Q0LdTXsxy0IfGgEb/EYyMxwYVslTD4WouWDE7wVy
wbCBggtnRqvDZ2IaArYBNRn4WaYN/v8vN7uhP5i8K1McnNmcE4wPv75sHSDWHfRZ
iUWHoJaEPRtoJ1KXbmSOU9tj7KBd0xccaxjX1tZB1wmjDCU8bTbOSMfoD629TkEt
Gym5e2Q66IgthJbVDnNplRaYPIS1Ac6OknCKN0xuYjcN356yGUNGPS4mIlY0sFVd
bU8UVJnFLZu3Q6EKX6ZPM9cD1s1RcS4Z0Y7LiOTXGbzQo0QTvOndCEHjmP3ZzY5j
yiCA3lLe70R1ZVzftQYEWSCZNEpAJg6QdWSKQl9rbFjYyXjP+lzrrulAQTaMPU1e
2sFRyLr605W8hFVK9WBiAHmdJc4FIuZKPUYJm0macto9D5RdBRCJSHnl/TGOUIIB
4kYrnEgGOdUjqHv/1spqaSaj3TbcXlyySrvzgXMzdh3Tcdi+wg27bQ5rYlkwS96u
SIzi6629t13UydUODJl8NpG4fk7o/d9ask08zphWSVHoEuzQCzaucS9BMyAB+P4n
kzvhLrFfF4Pj69T55rM1q/ebSvXe+Rr6M8dIxkwRlOpXwu2Zm0fxBkM78wmLM3mr
j9EbPv8Aja+CuVy7
=me7M
-END PGP SIGNATURE End Message ---

Bug#973190: marked as done (geneweb: FTBFS: ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string is not available.)

[Debian Bug Tracking System]

Your message dated Sun, 01 Nov 2020 10:03:22 +
with message-id 
and subject line Bug#973190: fixed in geneweb 6.08+git20181019+dfsg-3
has caused the Debian Bug report #973190,
regarding geneweb: FTBFS: ocamlc.opt: OCaml has been configured with 
-force-safe-string: -unsafe-string is not available.
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.)


-- 
973190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geneweb
Version: 6.08+git20181019+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 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 '/<>/wserver'
> camlp5r pa_extend.cmo q_MLast.cmo -o pa_macro5.ppo pa_macro5.ml
> ocamlc -c -I "`camlp5 -where`" -impl pa_macro5.ppo
> camlp5r ../wserver/pa_macro5.cmo -DUNIX -o wserver.ppi wserver.mli
> ocamlc.opt -unsafe-string  -I /usr/lib/ocaml/camlp5/ -c -intf wserver.ppi
> ocamlc.opt: OCaml has been configured with -force-safe-string: -unsafe-string 
> is not available.
> Usage: ocamlc  
> Options are:
>   -a  Build a library
>   -alert   Enable or disable alerts according to :
> +  enable alert 
> -  disable alert 
> ++ treat  as fatal error
> -- treat  as non-fatal
> @  enable  and treat it as fatal error
>  can be 'all' to refer to all alert names
>   -absname  Show absolute filenames in error messages
>   -annot  (deprecated) Save information in .annot
>   -bin-annot  Save typedtree in .cmt
>   -c  Compile only (do not link)
>   -cc   Use  as the C compiler and linker
>   -cclib   Pass option  to the C linker
>   -ccopt   Pass option  to the C compiler and linker
>   -color {auto|always|never}  Enable or disable colors in compiler messages
> The following settings are supported:
>   autouse heuristics to enable colors only if supported
>   always  enable colors
>   never   disable colors
> The default setting is 'auto', and the current heuristic
> checks that the TERM environment variable exists and is
> not empty or "dumb", and that isatty(stderr) holds.
>   If the option is not specified, these setting can alternatively
>   be set through the OCAML_COLOR environment variable.
>   -error-style {contextual|short}  Control the way error messages and 
> warnings are printed
> The following settings are supported:
>   short   only print the error and its location
>   contextual  like "short", but also display the source code
>   snippet corresponding to the location of the error
> The default setting is 'contextual'.
>   If the option is not specified, these setting can alternatively
>   be set through the OCAML_ERROR_STYLE environment variable.
>   -compat-32  Check that generated bytecode can run on 32-bit platforms
>   -config  Print configuration values and exit
>   -config-var  Print the value of a configuration variable, a newline, and 
> exit
> (print nothing and exit with error value if the variable does not exist)
>   -custom  Link in custom mode
>   -dllib   Use the dynamically-loaded library 
>   -dllpath   Add  to the run-time search path for shared libraries
>   -dtypes  (deprecated) same as -annot
>   -for-pack   Generate code that can later be `packed' with
>  ocamlc -pack -o .cmo
>   -g  Save debugging information
>   -stop-after {parsing|typing} Stop after the given compilation pass.
>   -i  Print inferred interface
>   -I   Add  to the list of include directories
>   -impl   Compile  as a .ml file
>   -intf   Compile  as a .mli file
>   -intf-suffix   Suffix for interface files (default: .mli)
>   -intf_suffix   (deprecated) same as -intf-suffix
>   -keep-docs  Keep documentation strings in .cmi files
>   -no-keep-docs  Do not keep documentation strings in .cmi files (default)
>   -keep-locs  Keep locations in .cmi files (default)
>   -no-keep-locs  Do not keep locations in .cmi files
>   -labels  Use commuting label mode
>   -linkall  Link all modules, even unused ones
>   -make-runtime  Build a runtime system with given C objects and libraries
>   -make_runtime  (deprecated) same as -make-runtime
>   -modern  (deprecated) same as -labels
>   -alias-deps  Do record dependencies for module aliases
>   -no-alias-deps  Do not record dependencies for module aliases
>   -app-funct  Activate applicative functors
>   -no-app-funct  Deactivate applicative functors
>   -no-check-prims  Do not che