Bug#938448: marked as done (scoop: Python2 removal in sid/bullseye)
Your message dated Wed, 22 Jan 2020 16:50:07 +
with message-id
and subject line Bug#938448: fixed in scoop 0.7.1.1-5
has caused the Debian Bug report #938448,
regarding scoop: 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.)
--
938448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scoop
Version: 0.7.1.1-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests. Please stop using Python2, and fix this issue
by one of the following actions.
- Convert your Package to Python3. This is the preferred option. In
case you are providing a Python module foo, please consider dropping
the python-foo package, and only build a python3-foo package. Please
don't drop Python2 modules, which still have reverse dependencies,
just document them.
This is the preferred option.
- If the package is dead upstream, cannot be converted or maintained
in Debian, it should be removed from the distribution. If the
package still has reverse dependencies, raise the severity to
"serious" and document the reverse dependencies with the BTS affects
command. If the package has no reverse dependencies, confirm that
the package can be removed, reassign this issue to ftp.debian.org,
make sure that the bug priority is set to normal and retitle the
issue to "RM: PKG -- removal triggered by the Python2 removal".
- If the package has still many users (popcon >= 300), or is needed to
build another package which cannot be removed, document that by
adding the "py2keep" user tag (not replacing the py2remove tag),
using the debian-pyt...@lists.debian.org user. Also any
dependencies on an unversioned python package (python, python-dev)
must not be used, same with the python shebang. These have to be
replaced by python2/python2.7 dependencies and shebang.
This is the least preferred option.
If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like
affects + src:scoop
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: scoop
Source-Version: 0.7.1.1-5
We believe that the bug you reported is fixed in the latest version of
scoop, 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 938...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated scoop 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, 22 Jan 2020 18:17:10 +0200
Source: scoop
Architecture: source
Version: 0.7.1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Adrian Bunk
Closes: 938448
Changes:
scoop (0.7.1.1-5) unstable; urgency=medium
.
* QA upload.
* scoop-doc: Stop recommending the removed python-scoop.
(Closes: #938448)
* debian/control: Remove the obsolete X-Python{,3}-Version.
Checksums-Sha1:
47abd8f5235286cc6070616d344c5b13bcc78c21 2103 scoop_0.7.1.1-5.dsc
20e8a4e61fa6c656862ce83d7405ebd920bdedbd 6748 scoop_0.7.1.1-5.debian.tar.xz
Checksums-Sha256:
94b3664b82b86a3b78a34b8ce333c2eb0dcdae1f927c1590e6e61864197c193e 2103
scoop_0.7.1.1-5.dsc
fff8de30e4858dc85fee2f1916744f8aefaccb23fa92ec7d3e8ca9c053b2e371 6748
scoop_0.7.1.1-5.debian.tar.xz
Files:
13f3ac94cb3368a4a550d76867dc1d38 2103 science optional scoop_0.7.1.1-5.dsc
eea19fe8fde4f8ea00a9d78deec7d1d7 6748 science optional
scoop_0.7.1.1-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBC
Processing of scoop_0.7.1.1-5_source.changes
scoop_0.7.1.1-5_source.changes uploaded successfully to localhost along with the files: scoop_0.7.1.1-5.dsc scoop_0.7.1.1-5.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
scoop_0.7.1.1-5_source.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 22 Jan 2020 18:17:10 +0200
Source: scoop
Architecture: source
Version: 0.7.1.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Adrian Bunk
Closes: 938448
Changes:
scoop (0.7.1.1-5) unstable; urgency=medium
.
* QA upload.
* scoop-doc: Stop recommending the removed python-scoop.
(Closes: #938448)
* debian/control: Remove the obsolete X-Python{,3}-Version.
Checksums-Sha1:
47abd8f5235286cc6070616d344c5b13bcc78c21 2103 scoop_0.7.1.1-5.dsc
20e8a4e61fa6c656862ce83d7405ebd920bdedbd 6748 scoop_0.7.1.1-5.debian.tar.xz
Checksums-Sha256:
94b3664b82b86a3b78a34b8ce333c2eb0dcdae1f927c1590e6e61864197c193e 2103
scoop_0.7.1.1-5.dsc
fff8de30e4858dc85fee2f1916744f8aefaccb23fa92ec7d3e8ca9c053b2e371 6748
scoop_0.7.1.1-5.debian.tar.xz
Files:
13f3ac94cb3368a4a550d76867dc1d38 2103 science optional scoop_0.7.1.1-5.dsc
eea19fe8fde4f8ea00a9d78deec7d1d7 6748 science optional
scoop_0.7.1.1-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl4od3QACgkQiNJCh6LY
mLENWA//aSkO85AIL1OwPHn55shUx8udoZ7uJhSSlORLLVwThNsCVUPFGwEuuU7q
GhdxcduDL2ZGCDiOAOVCRAQi52oZAi9R4Tu0uXqIlM0LAUabrauzTCJA1bBdovCX
bWaeO7vxPxQDlHX9aa+Bf8ekbtutJS4H/JJg6l3LbGtTRJu4/ETZa/OSIdHhzA3v
W0jbqiVlfuLdezsGiGcb+oQokOTWZ8/D4+sW8daUt+L9KQHvZGOgE6fdujFenbvv
ykT30GkfgkmnuG5ONnNU1otFuZI/S1c1XdCoVMU26XbXkjXZQxyfbT+pZTKBH+Cu
a0QW4FLa/Q1baYhWX3TeCgSt8CXHjYD1S3mhLU8hSXt4OEu/JbRlt1MzsLrMxsUI
jNg4Kh7MqZ7U5LPfpWQnm0j9pqDzZCHxvN2XbZQo1K8nq2LsOljGLfBdb9v7a+M1
Rd77JYQU6xizljULbyS9uVd4HRkySqqr+tvSeghIOlcIHyBv5imTxqNeTdzUsign
sqEDnzliAdsMBoM/VeC2EhJKIMJhdYNZrhm5M1ruhHUBwwlEtdBuDIIeBZfdP7VO
G3OAdyTkIZk0WjgoZHx5WubO9M/s7FTLXBQCXH0upwU0qzcNLisfQuz+5ZqDfKdD
7dhKY3OEZIpyS+tpip4rXEgA+96U+zBHqMp7vMktSG7XNn4HxC8=
=51u+
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
Bug#866522: marked as done (mdadm FTCBFS: upstream buildsystem ignores CROSS_COMPILE variable)
Your message dated Wed, 22 Jan 2020 18:04:34 + with message-id and subject line Bug#866522: fixed in mdadm 4.1-5 has caused the Debian Bug report #866522, regarding mdadm FTCBFS: upstream buildsystem ignores CROSS_COMPILE variable 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.) -- 866522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mdadm Version: 4.0-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap mdadm fails to cross build from source, because it uses the build architecture compiler. Its Makefile assigns: CC ?= $(CROSS_COMPILE)gcc Since CC is a builtin variable. Such an assignment is ignored. After fixing the assignment mdadm cross builds successfully. Please consider applying the attached patch. Helmut diff --minimal -Nru mdadm-4.0/debian/changelog mdadm-4.0/debian/changelog --- mdadm-4.0/debian/changelog 2017-06-22 14:23:10.0 +0200 +++ mdadm-4.0/debian/changelog 2017-06-29 22:01:05.0 +0200 @@ -1,3 +1,10 @@ +mdadm (4.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: cross.patch (Closes: #-1) + + -- Helmut Grohne Thu, 29 Jun 2017 22:01:05 +0200 + mdadm (4.0-1) unstable; urgency=medium * New upstream release. LP: #1668128 diff --minimal -Nru mdadm-4.0/debian/patches/cross.patch mdadm-4.0/debian/patches/cross.patch --- mdadm-4.0/debian/patches/cross.patch1970-01-01 01:00:00.0 +0100 +++ mdadm-4.0/debian/patches/cross.patch2017-06-29 22:01:02.0 +0200 @@ -0,0 +1,20 @@ +From: Helmut Grohne +Subject: properly assign CC + +A ?= assignment to a builtin variable is useless. + +Index: mdadm-4.0/Makefile +=== +--- mdadm-4.0.orig/Makefile mdadm-4.0/Makefile +@@ -41,7 +41,9 @@ + + KLIBC_GCC = gcc -nostdinc -iwithprefix include -I$(KLIBC)/klibc/include -I$(KLIBC)/linux/include -I$(KLIBC)/klibc/arch/i386/include -I$(KLIBC)/klibc/include/bits32 + +-CC ?= $(CROSS_COMPILE)gcc ++ifeq ($(origin CC),default) ++CC := $(CROSS_COMPILE)gcc ++endif + CXFLAGS ?= -ggdb + CWFLAGS = -Wall -Wstrict-prototypes -Wextra -Wno-unused-parameter + ifdef WARN_UNUSED diff --minimal -Nru mdadm-4.0/debian/patches/series mdadm-4.0/debian/patches/series --- mdadm-4.0/debian/patches/series 2017-05-12 13:28:13.0 +0200 +++ mdadm-4.0/debian/patches/series 2017-06-29 22:00:05.0 +0200 @@ -3,3 +3,4 @@ sha1-includes.diff readlink-path.patch mdmonitor-service-simplify.diff +cross.patch --- End Message --- --- Begin Message --- Source: mdadm Source-Version: 4.1-5 We believe that the bug you reported is fixed in the latest version of mdadm, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier (supplier of updated mdadm 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, 22 Jan 2020 09:56:25 -0700 Source: mdadm Architecture: source Version: 4.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: dann frazier Closes: 866522 943520 Changes: mdadm (4.1-5) unstable; urgency=medium . * QA upload. * Fix cross-compilation failure. (Closes: #866522). Thanks to Helmut Grohne. * Add support for raid0/linear 'broken' state. (Closes: #943520). Thanks to Guilherme G. Piccoli and Dan Streetman. LP: #1847924. Checksums-Sha1: 0ed9c2d273dd8c08dbb7d21b64baffcdb649633a 1904 mdadm_4.1-5.dsc 6a51348a9d19e5e60353d59f9890e51ec4274d10 96480 mdadm_4.1-5.debian.tar.xz 361c41b624eef28e355436ada41c5a748a5ab718 5924 mdadm_4.1-5_source.buildinfo Checksums-Sha256: c8fb93131f4c39e8e3d6709eec03805f0350142e4fbf12ab53b5f3b9620877bd 1904 mdadm_4.1-5.dsc c30c5665c1f72bd739b2c750ce9bc6b45b161b4c8d6bc2a9f9ecf33f81e063c8 96480 mdadm_4.1-5.debian.tar.xz e459e1d93422054106e911947f542d994b971f1fd999fe64ee579132a60ff2f7 5924 mdadm_4.1-5_source.buildinfo Files: c25f54e3dc2997c676321efa0c50f9ef 1904 admin optional mdadm_4.1-5.dsc 2129211c2ebb2889a29e81db19d6332d 96480 admin op
Bug#943520: marked as done (mdadm: Introduce broken state parsing to mdadm)
Your message dated Wed, 22 Jan 2020 18:04:34 +
with message-id
and subject line Bug#943520: fixed in mdadm 4.1-5
has caused the Debian Bug report #943520,
regarding mdadm: Introduce broken state parsing to mdadm
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.)
--
943520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943520
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mdadm
Version: 4.1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear Maintainer,
* Currently, mounted raid0/md-linear arrays have no indication/warning when one
or more members are removed or suffer from some non-recoverable error
condition. The mdadm tool shows "clean" state regardless if a member was
removed.
* The patch proposed in this SRU addresses this issue by introducing a new
state "broken", which is analog to "clean" but indicates that array is not in a
good/correct state. The commit, available upstream as 43ebc910 ("mdadm:
Introduce new array state 'broken' for raid0/linear") [0], was extensively
discussed and received a good amount of reviews/analysis by both the current
mdadm maintainer as well as an old maintainer.
* One important note here is that this patch requires a counter-part in the
kernel to be fully functional, which was SRUed in LP: #1847773.
It works fine/transparently without this kernel counter-part though.
In Ubuntu, the attached patch was applied to achieve the following:
* Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
Thanks for considering the patch.
diff -Nru mdadm-4.1/debian/control mdadm-4.1/debian/control
--- mdadm-4.1/debian/control2019-05-04 23:58:27.0 -0400
+++ mdadm-4.1/debian/control2019-10-13 17:04:34.0 -0400
@@ -1,8 +1,7 @@
Source: mdadm
Section: admin
Priority: optional
-Maintainer: Ubuntu Developers
-XSBC-Original-Maintainer: Debian QA Group
+Maintainer: Debian QA Group
Build-Depends: debhelper (>= 11), po-debconf, groff-base
Standards-Version: 4.3.0
Vcs-Git: https://git.dgit.debian.org/mdadm
diff -Nru
mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
--- mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
1969-12-31 19:00:00.0 -0500
+++ mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
2019-10-13 17:04:34.0 -0400
@@ -0,0 +1,159 @@
+Subject: Introduce new array state 'broken' for raid0/linear
+
+Currently if a md raid0/linear array gets one or more members removed while
+being mounted, kernel keeps showing state 'clean' in the 'array_state'
+sysfs attribute. Despite udev signaling the member device is gone, 'mdadm'
+cannot issue the STOP_ARRAY ioctl successfully, given the array is mounted.
+
+Nothing else hints that something is wrong (except that the removed devices
+don't show properly in the output of mdadm 'detail' command). There is no
+other property to be checked, and if user is not performing reads/writes
+to the array, even kernel log is quiet and doesn't give a clue about the
+missing member.
+
+This patch is the mdadm counterpart of kernel new array state 'broken'.
+The 'broken' state mimics the state 'clean' in every aspect, being useful
+only to distinguish if an array has some member missing. All necessary
+paths in mdadm were changed to deal with 'broken' state, and in case the
+tool runs in a kernel that is not updated, it'll work normally, i.e., it
+doesn't require the 'broken' state in order to work.
+Also, this patch changes the way the array state is showed in the 'detail'
+command (for raid0/linear only) - now it takes the 'array_state' sysfs
+attribute into account instead of only rely in the MD_SB_CLEAN flag.
+
+Author: Guilherme G. Piccoli
+Origin: upstream,
+git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cb77f8c598ede2b7efec23f899b1cda44c315195
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1847924
+Last-Update: 2019-10-13
+---
+ Detail.c | 14 --
+ Monitor.c | 8 ++--
+ maps.c| 1 +
+ mdadm.h | 1 +
+ mdmon.h | 2 +-
+ monitor.c | 4 ++--
+ 6 files changed, 23 insertions(+), 7 deletions(-)
+
+diff --git a/Detail.c b/Detail.c
+index b3e857a..d24f334 100644
+--- a/Detail.c
b/Detail.c
+@@ -81,6 +81,7 @@ int Detail(char *dev, struct context *c)
+ int external;
+ int inactive;
+ int is_container = 0;
++ char *arrayst;
+
+ if (fd < 0) {
+ pr_err("cannot open %s
Processing of mdadm_4.1-5_source.changes
mdadm_4.1-5_source.changes uploaded successfully to localhost along with the files: mdadm_4.1-5.dsc mdadm_4.1-5.debian.tar.xz mdadm_4.1-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
mdadm_4.1-5_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Jan 2020 09:56:25 -0700 Source: mdadm Architecture: source Version: 4.1-5 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: dann frazier Closes: 866522 943520 Changes: mdadm (4.1-5) unstable; urgency=medium . * QA upload. * Fix cross-compilation failure. (Closes: #866522). Thanks to Helmut Grohne. * Add support for raid0/linear 'broken' state. (Closes: #943520). Thanks to Guilherme G. Piccoli and Dan Streetman. LP: #1847924. Checksums-Sha1: 0ed9c2d273dd8c08dbb7d21b64baffcdb649633a 1904 mdadm_4.1-5.dsc 6a51348a9d19e5e60353d59f9890e51ec4274d10 96480 mdadm_4.1-5.debian.tar.xz 361c41b624eef28e355436ada41c5a748a5ab718 5924 mdadm_4.1-5_source.buildinfo Checksums-Sha256: c8fb93131f4c39e8e3d6709eec03805f0350142e4fbf12ab53b5f3b9620877bd 1904 mdadm_4.1-5.dsc c30c5665c1f72bd739b2c750ce9bc6b45b161b4c8d6bc2a9f9ecf33f81e063c8 96480 mdadm_4.1-5.debian.tar.xz e459e1d93422054106e911947f542d994b971f1fd999fe64ee579132a60ff2f7 5924 mdadm_4.1-5_source.buildinfo Files: c25f54e3dc2997c676321efa0c50f9ef 1904 admin optional mdadm_4.1-5.dsc 2129211c2ebb2889a29e81db19d6332d 96480 admin optional mdadm_4.1-5.debian.tar.xz 006fac32bba9f21f427d884b72f2c867 5924 admin optional mdadm_4.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEECfR9vy0y7twkQ+vuG/g8XlT8hkAFAl4oiikRHGRhbm5mQGRl Ymlhbi5vcmcACgkQG/g8XlT8hkCxiQ/8DxkfLNX0Ivd3n+m1WMVk5GDbqqWFWBM6 O+al+Is22pjjrmkpEdd9HRuj0wEa3sGbLu+GHhJZmyKHEl89IatZ8KDfu/jdg9XC f5lxrL8Kza2RI9k0eJnwvjFoeSlNAjBIERjfLbDb5w/MPY3dAFND8ExB3paT+nhc 0yNB6IPuz1b9oVKydOHz7E3ZxcL/40jHayd+lV3SDI99kbhgCkkSEd2leq9ayQtd 6uPQ3S5xhchuwt3vGhDI84viuH4qsj5sgvoNRpe0SiTUmMrTv/3CeYd62kIGtuhP MTpHMXgMpG7f7rSna9d/qHvmR4B1dWXvBr7f39ghuJYVgCjlia3Gg0tvh82uxHWN AtXkTh4GOeh8vSqMu0tSKypdUmRNki9zqO/kPDmnQH4Dswp0lExslmZdS/pOv+RW ku5s8klgh9vDNOft1J5pEvDu3oieMJ3Dk6W37b6jfh+u5h/KvuPqEh4HGtGjTjcN boyPS20Rqca7WToaHZiHN00fD5b9Jh1WtO8YwiZZf/lDmQkFzRJAvX/2C691QjnK sbCRABu3SwjIYQwVvaNFl8cjQZNzizT/e0m/oyxzANfs6KCqmxiPDQYoEPt0dJ/h cB4mBvmEtvVBMZM4YKg9bmsyWxo3+KR0XycAwkMa9bggAFgjtaSP4dRGutrxJLfy asAsHhU6OyE= =GDFo -END PGP SIGNATURE- Thank you for your contribution to Debian.
Ordem 1666686 inclusão em CPF
Documento 429kb (Visualizar) Boa tarde, segue em anexo Guia do pedido,Cadastramento da inclusão em CPF. Atenciosamente,ADELIA FERREIRA DA SILVA XAVIER
Bug#943994: python3-zeitgeist not compatible with python3
X-Debbugs-CC: bi...@debian.org Hi Laurent, On Sat, 2 Nov 2019 10:40:39 +0100 Laurent Bigonville wrote: > On Sat, 02 Nov 2019 10:31:36 +0100 Laurent Bigonville > wrote: > [...] > > > > Looks like it's not compatible with python3. > > > > Looking at the debian changelog, I personally removed that package back > in March 2018 because it was not compatible, not sure why it was > reintroduced: > > zeitgeist (1.0.1-0.2) unstable; urgency=medium > >* Non-maintainer upload. >* Drop python3-zeitgeist package as the binding is not compatible with > python3, for python3, GIR binding should be used instead. Reintroduce the > python2 binding for now as we still have one rdependency (Closes: #891615) >* Avoid installing files in /usr/lib/zeitgeist/zeitgeist/, move them one > level up to /usr/lib/zeitgeist/ instead >* Do not make the metapackge pull python-zeitgeist, this is not needed for > normal operations > > -- Laurent Bigonville Sun, 11 Mar 2018 19:54:01 +0100 > > An idea? No idea why. Looks like we need to have python3-zeitgeist removed eventually. However before that, I'm going for a workaround: Upload an experimental version with higher version string, e.g., 1.0.2+py3-0. After that, upload 1.0.2-3 onto Sid with python3-zeitgeist removed. This would keep binary package python3-zeitgeist in development repositories so that we do not need to go through NEW queue for another time if we really need that in the future. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Processing of zeitgeist_1.0.2+py3-0~exp1_source.changes
zeitgeist_1.0.2+py3-0~exp1_source.changes uploaded successfully to localhost along with the files: zeitgeist_1.0.2+py3-0~exp1.dsc zeitgeist_1.0.2+py3.orig.tar.xz zeitgeist_1.0.2+py3-0~exp1.debian.tar.xz zeitgeist_1.0.2+py3-0~exp1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
zeitgeist_1.0.2+py3-0~exp1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Jan 2020 16:21:48 -0500 Source: zeitgeist Architecture: source Version: 1.0.2+py3-0~exp1 Distribution: experimental Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: zeitgeist (1.0.2+py3-0~exp1) experimental; urgency=medium . * QA upload. * Upload to experimental to keep the broken python3-zeitgeist package. Checksums-Sha1: 2a39cda342a817e0a21ee43cebfde785679d2bc6 2774 zeitgeist_1.0.2+py3-0~exp1.dsc 85bd6a249941e29c5fbc681e3d5b35419434f69d 840360 zeitgeist_1.0.2+py3.orig.tar.xz cd4b02b111c7676fd83c7368929d50f200a07158 15468 zeitgeist_1.0.2+py3-0~exp1.debian.tar.xz d915666c3564e0ca093020ed22ddba7d0211ce86 18866 zeitgeist_1.0.2+py3-0~exp1_amd64.buildinfo Checksums-Sha256: 40654d1a3468f7412f880933f47dda4df917da15c98873fb487730e459615551 2774 zeitgeist_1.0.2+py3-0~exp1.dsc d023b5904c7076b2701df915dd29b77e256a86d9e80ecfb92f36c9f26371a8ce 840360 zeitgeist_1.0.2+py3.orig.tar.xz 1c7110aa3bb118fccdb73bba0798c1b70c02c0b09d295f48722a1ad9cb99d5ef 15468 zeitgeist_1.0.2+py3-0~exp1.debian.tar.xz ed62871adfda8728bb4743403a4825f6a5ddb509aec5e694bff665b49f70b263 18866 zeitgeist_1.0.2+py3-0~exp1_amd64.buildinfo Files: dff976962c315db2ddfce7a9072067bb 2774 utils optional zeitgeist_1.0.2+py3-0~exp1.dsc 08e9031e158a4ab0824adc2610e7d122 840360 utils optional zeitgeist_1.0.2+py3.orig.tar.xz 60e5e84ba33b0ccf69bcf65edba3c661 15468 utils optional zeitgeist_1.0.2+py3-0~exp1.debian.tar.xz fc6062f24826335c96194645c375988c 18866 utils optional zeitgeist_1.0.2+py3-0~exp1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl4owkkACgkQwpPntGGC Ws77cA//YaRMcftsDjRC7DuKSB/m2VN+vCxuAv44j/XJ66XuDWMXRAL4P+d2RSMv r9vT9NWo2rDo/TawkPOXU4UQv7LE0Ad8wsPO0bSHl6+A4LU9jeCi3HPjfls20I3e 38Pu2Wvm1+vs7UnwJzS0D7GqsTFM4wt+13uxjn/eC2fS7ci7LIq+EBaVZM4zjIm7 ys7Eu4evTnt67PPHZMlVpneaSi5XIe5wy518ECiV+1XxnprnQZso+UUDZ9RiQxWP 4K573BmbqYGf77GSBOpFvlc8q2vOEsbI/FlBX3SbUrUKI+NdyT8znbCv339AAIv/ m1CZiyDK+XK15pFqZv2Nc6L3EwF4HqmyJTje+QYnjh3NRw+UCG5Oc/BZhKfgOpSR xYv0tSLW7YmCHGNLH+RRbQm+hnRKVu6qOjTs4DEdtLFUM5/ZfwXk1T4A4EgiPI9E Nail1ucjEO7EfS3UJob4On5/QHJWVQF3E5WVc3BC2TjJzcxtEpjHgSQuCQgz4u3W KnMiPTf9yjzqTCqaboW/Y5q1qiyY3HAfQ3Ls2bExGDBXrfQo98GfLzeP/puTuuR3 DTm1rPTUzde+qDzBUgPzyiXTDucMI6xqANroQFG9rumbqMqQMCFmzO+7ET+HDYMF NgZ5sVl2kdGR3+URcoHovJ4+CNTB+tbdvFRTdi43kDe4LeaFYf8= =3RK7 -END PGP SIGNATURE- Thank you for your contribution to Debian.
