Bug#945652: i3lock-fancy: diff for NMU version 0.0~git20160228.0.0fcb933-2.1
Control: tags 945652 + patch
Dear maintainer,
I've prepared an NMU for i3lock-fancy (versioned as
0.0~git20160228.0.0fcb933-2.1). The diff
is attached to this message.
Regards.
diff -Nru i3lock-fancy-0.0~git20160228.0.0fcb933/debian/changelog i3lock-fancy-0.0~git20160228.0.0fcb933/debian/changelog
--- i3lock-fancy-0.0~git20160228.0.0fcb933/debian/changelog 2018-01-25 23:54:36.0 -0500
+++ i3lock-fancy-0.0~git20160228.0.0fcb933/debian/changelog 2020-01-01 02:00:53.0 -0500
@@ -1,3 +1,10 @@
+i3lock-fancy (0.0~git20160228.0.0fcb933-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python-tomahawk as alternative dependency; Closes: #945652
+
+ -- Sandro Tosi Wed, 01 Jan 2020 02:00:53 -0500
+
i3lock-fancy (0.0~git20160228.0.0fcb933-2) unstable; urgency=medium
* Move to salsa.debian.org.
diff -Nru i3lock-fancy-0.0~git20160228.0.0fcb933/debian/control i3lock-fancy-0.0~git20160228.0.0fcb933/debian/control
--- i3lock-fancy-0.0~git20160228.0.0fcb933/debian/control 2018-01-25 23:54:05.0 -0500
+++ i3lock-fancy-0.0~git20160228.0.0fcb933/debian/control 2020-01-01 02:00:42.0 -0500
@@ -11,7 +11,7 @@
Package: i3lock-fancy
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, i3lock, imagemagick, scrot, gawk | cpl-plugin-hawki-calib | cpl-plugin-hawki-doc | mawk | original-awk | python-tomahawk
+Depends: ${shlibs:Depends}, ${misc:Depends}, i3lock, imagemagick, scrot, gawk | cpl-plugin-hawki-calib | cpl-plugin-hawki-doc | mawk | original-awk
Suggests: wmctrl, maim
Description: i3lock custom wrapper script
i3lock bash script that takes a screenshot of the desktop, blurs the
Processed: i3lock-fancy: diff for NMU version 0.0~git20160228.0.0fcb933-2.1
Processing control commands: > tags 945652 + patch Bug #945652 [src:i3lock-fancy] i3lock-fancy should stop listing python-tomahawk as alternative dependency Added tag(s) patch. -- 945652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945730: pyconfigure: diff for NMU version 0.2.3-2.1
Control: tags 945730 + patch Dear maintainer, I've prepared an NMU for pyconfigure (versioned as 0.2.3-2.1). The diff is attached to this message. Regards. diff -Nru pyconfigure-0.2.3/debian/changelog pyconfigure-0.2.3/debian/changelog --- pyconfigure-0.2.3/debian/changelog 2018-09-15 16:27:14.0 -0400 +++ pyconfigure-0.2.3/debian/changelog 2020-01-01 01:36:55.0 -0500 @@ -1,3 +1,10 @@ +pyconfigure (0.2.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop python-setuptools from Recommends; Closes: #945730 + + -- Sandro Tosi Wed, 01 Jan 2020 01:36:55 -0500 + pyconfigure (0.2.3-2) unstable; urgency=low * Bump Standards-Version to 4.2.1 diff -Nru pyconfigure-0.2.3/debian/control pyconfigure-0.2.3/debian/control --- pyconfigure-0.2.3/debian/control 2018-09-15 16:22:46.0 -0400 +++ pyconfigure-0.2.3/debian/control 2020-01-01 01:36:43.0 -0500 @@ -17,7 +17,7 @@ python3, autoconf, Recommends: - python3-setuptools | python-setuptools, + python3-setuptools, Description: automatic configure script builder for Python software GNU pyconfigure provides developers with file templates for implementing standard `configure' scripts and `Makefile' recipes for their Python packages.
Processed: pyconfigure: diff for NMU version 0.2.3-2.1
Processing control commands: > tags 945730 + patch Bug #945730 [src:pyconfigure] pyconfigure: Please drop alternative recommends of python-setuptools Added tag(s) patch. -- 945730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930774: any idea when guile-2.2 will be fixed ?
Hi all, Just saw this, any idea when this FTFBS will be fixed. Somebody even shared a patch, maybe that fixes the issue. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
Bug#947780: marked as done (libcrypt1: keep from migrating to testing until libcrypt{,1}-dev situation is fixed in glibc)
Your message dated Wed, 1 Jan 2020 05:56:00 +0100 (CET)
with message-id
and subject line Re: Bug#947780: libcrypt1: keep from migrating to testing
until libcrypt{,1}-dev situation is fixed in glibc
has caused the Debian Bug report #947780,
regarding libcrypt1: keep from migrating to testing until libcrypt{,1}-dev
situation is fixed in glibc
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.)
--
947780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcrypt1
Version: 1:4.4.10-7
Severity: grave
Justification: renders package unusable
Sorry, the migration to testing¹ needs to be postposed a bit,
at least until #947778 is fixed (due to the -dev renaming).
① it won’t migrate as-is currently anyway, because it needs
a new source-only upload and piuparts fails testing, though
the latter might be due to the glibc issue maybe?
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 5.3.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages libcrypt1 depends on:
ii libc6 2.29-6
libcrypt1 recommends no packages.
libcrypt1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 30 Dec 2019, Thorsten Glaser wrote:
> at least until #947778 is fixed (due to the -dev renaming).
This is now built on all relevant architectures for testing migration.
> ① it won’t migrate as-is currently anyway, because it needs
> a new source-only upload
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg--- End Message ---
Bug#946327: khotkeys FTBFS: fixed upstream
Control: tags -1 fixed-upstream The package builds with the following two commits applied in order: https://cgit.kde.org/khotkeys.git/diff/?id=67fd8f06 https://cgit.kde.org/khotkeys.git/diff/?id=ae574373 The former one makes many changes, but appears to be related only due to removing a blank line in a file, so that change could probably be consolidated. A naive uscan and uupdate got me to 5.17.4. With no additional changes this builds fine in sbuild, so maybe a new release would be more convenient. signature.asc Description: This is a digitally signed message part.
Processed: khotkeys FTBFS: fixed upstream
Processing control commands: > tags -1 fixed-upstream Bug #946327 [src:khotkeys] khotkeys FTBFS: error: no matching function for call to ‘KDialog::KDialog(QWidget*&)’ Added tag(s) fixed-upstream. -- 946327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947865: pyopencl: FTBFS in sid
Source: pyopencl Version: 2019.1.1-1 Severity: serious Tags: patch Justification: FTBFS Hello, pyopencl currently FTBFS in sid because apparently moved to libgl-dev. The attached patch fixes that. Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Samuel Linux, c'est simple : ça s'adresse à une machine qui est parfois un peu maraboutée mais qui d'habitude n'a pas d'états d'âme. Sur Usenet y'a plein d'humains et de primates, et ça devient vraiment gore par moment. -+- TP in : Guide du linuxien pervers - "Le linuxien a-t-il une âme ?" -+- --- debian/control.original 2020-01-01 02:25:30.482219682 +0100 +++ debian/control 2020-01-01 02:25:33.052221180 +0100 @@ -15,7 +15,7 @@ python3-setuptools, opencl-c-headers, ocl-icd-opencl-dev | opencl-dev, - mesa-common-dev, + mesa-common-dev, libgl-dev, python3-numpy, python3-sphinx (>= 1.0.7+dfsg) , python3-mako,
Processed: Bug#945390 marked as pending in androguard
Processing control commands: > tag -1 pending Bug #945390 [src:androguard] androguard: autopkgtest failures Added tag(s) pending. -- 945390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945390: marked as pending in androguard
Control: tag -1 pending Hello, Bug #945390 in androguard reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/androguard/commit/5577dad005a884cc9babb15fcd6dc4678fbbf523 compatiblity with networkx 2.4; Closes: #945390 (this message was generated automatically) -- Greetings https://bugs.debian.org/945390
Bug#945390: androguard: autopkgtest failures
On Sun, 24 Nov 2019 08:31:33 +0100 Bas Couwenberg wrote: > Source: androguard > Version: 3.3.5-1 > Severity: serious > Justification: makes the package in question unusable or mostly so > > Dear Maintainer, > > The autopkgtest for your package are failing, which prevent the testing > migration of networkx. > > The logging shows many exceptions like this: > > AttributeError: 'DiGraph' object has no attribute 'node' please note these are _not_ the reason autopkgtests are failing (smoke-test is PASSing), but the real reason is: autopkgtest [17:12:48]: test command1: nosetests3 --with-timer --timer-top-n 50 autopkgtest [17:12:48]: test command1: [--- .S...F..S == FAIL: test_cg_basic (test_entry_points.EntryPointsTest) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.muz8cxzo/downtmp/build.QhB/src/tests/test_entry_points.py", line 181, in test_cg_basic assert result.exit_code == 0 AssertionError: >> begin captured logging << androguard.analysis: INFO: End of creating cross references (XREF) androguard.analysis: INFO: run time: 0min 00s androcfg: INFO: Found The following entry points by search AndroidManifest.xml: ['Lorg/t0t0/androguard/test//TestActivity;'] androguard.analysis: INFO: Found Method --> LTest1;->()V [access_flags=public constructor] @ 0x400 - >> end captured logging << - FAILED (SKIP=2, failures=1) autopkgtest [17:16:10]: test command1: ---] autopkgtest [17:16:10]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 1 autopkgtest [17:16:10]: summary smoke-test PASS command1 FAIL non-zero exit status 1
Processed: bug 945392 is forwarded to https://gitlab.com/mailman/hyperkitty/issues/268, tagging 945392
Processing commands for cont...@bugs.debian.org: > forwarded 945392 https://gitlab.com/mailman/hyperkitty/issues/268 Bug #945392 [src:hyperkitty] hyperkitty: autopkgtest failures Set Bug forwarded-to-address to 'https://gitlab.com/mailman/hyperkitty/issues/268'. > tags 945392 + patch Bug #945392 [src:hyperkitty] hyperkitty: autopkgtest failures Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 945392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937808: python-hglib: diff for NMU version 2.6.1-1.1
On Tue, Dec 31, 2019 at 6:11 PM Julien Cristau wrote: > > Nak. I don't want to drop python support at this stage. can you explain why? there is no package in debian depending on python-hglib, and in a week it will be auto-removed from testing because of this I've just asked to remove the upload, let's hope it's enough (it was with no delay) > > Julien > > On December 31, 2019 11:58:44 PM GMT+01:00, Sandro Tosi > wrote: >> >> Control: tags 937808 + patch >> >> >> Dear maintainer, >> >> I've prepared an NMU for python-hglib (versioned as 2.6.1-1.1). The diff >> is attached to this message. >> >> Regards. >> -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#937808: python-hglib: diff for NMU version 2.6.1-1.1
Nak. I don't want to drop python support at this stage. Julien On December 31, 2019 11:58:44 PM GMT+01:00, Sandro Tosi wrote: >Control: tags 937808 + patch > > >Dear maintainer, > >I've prepared an NMU for python-hglib (versioned as 2.6.1-1.1). The >diff >is attached to this message. > >Regards.
Processed: bug 945390 is forwarded to https://github.com/androguard/androguard/issues/769
Processing commands for cont...@bugs.debian.org: > forwarded 945390 https://github.com/androguard/androguard/issues/769 Bug #945390 [src:androguard] androguard: autopkgtest failures Set Bug forwarded-to-address to 'https://github.com/androguard/androguard/issues/769'. > thanks Stopping processing here. Please contact me if you need assistance. -- 945390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937808: python-hglib: diff for NMU version 2.6.1-1.1
Control: tags 937808 + patch
Dear maintainer,
I've prepared an NMU for python-hglib (versioned as 2.6.1-1.1). The diff
is attached to this message.
Regards.
diff -Nru python-hglib-2.6.1/debian/changelog python-hglib-2.6.1/debian/changelog
--- python-hglib-2.6.1/debian/changelog 2019-12-31 17:58:41.0 -0500
+++ python-hglib-2.6.1/debian/changelog 2019-12-31 17:55:13.0 -0500
@@ -1,3 +1,13 @@
+python-hglib (2.6.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #937808
+ * debian/patches
+- add upstream fixes for mercurial 5.2 compatibility (tests)
+- switch to 3.0 (quilt) source format
+
+ -- Sandro Tosi Tue, 31 Dec 2019 17:55:13 -0500
+
python-hglib (2.6.1-1) unstable; urgency=medium
* New upstream release
diff -Nru python-hglib-2.6.1/debian/control python-hglib-2.6.1/debian/control
--- python-hglib-2.6.1/debian/control 2019-12-31 17:58:41.0 -0500
+++ python-hglib-2.6.1/debian/control 2019-12-31 15:32:29.0 -0500
@@ -5,26 +5,12 @@
Build-Depends:
debhelper (>= 7.0.50),
dh-python,
- python-all,
- python-nose,
python3-all,
python3-nose,
mercurial (>= 1.9),
Standards-Version: 3.9.8
Homepage: https://www.mercurial-scm.org/wiki/PythonHglib
-Package: python-hglib
-Architecture: all
-Depends:
- mercurial (>= 1.9),
- ${python:Depends},
- ${misc:Depends},
-Description: Python library for interfacing with Mercurial's command server
- python-hglib is a library with a fast, convenient interface to Mercurial.
- It uses Mercurial's command server for communication with hg. This approach
- avoids relying on Mercurial's (unstable) internal Python API, and avoids
- licensing issues for non-GPL code.
-
Package: python3-hglib
Architecture: all
Depends:
diff -Nru python-hglib-2.6.1/debian/patches/12e6aaef0f6e.patch python-hglib-2.6.1/debian/patches/12e6aaef0f6e.patch
--- python-hglib-2.6.1/debian/patches/12e6aaef0f6e.patch 1969-12-31 19:00:00.0 -0500
+++ python-hglib-2.6.1/debian/patches/12e6aaef0f6e.patch 2019-12-31 17:49:41.0 -0500
@@ -0,0 +1,25 @@
+
+# HG changeset patch
+# User Matt Harbison
+# Date 1557281819 14400
+# Node ID 12e6aaef0f6ed289658ed2df3240e705fae3e029
+# Parent 33b512aa8dba0cbe523188fbb62d30ae2125a236
+tests: handle the removal of `obsolete._enabled` in Mercurial
+
+I'm not sure why we can't just set `experimental.evolution=all`, but it didn't
+work.
+
+diff -r 33b512aa8dba -r 12e6aaef0f6e tests/test-hidden.py
+--- a/tests/test-hidden.py Mon Apr 30 10:38:03 2018 -0400
b/tests/test-hidden.py Tue May 07 22:16:59 2019 -0400
+@@ -22,6 +22,9 @@
+ super(test_obsolete_baselib, self).setUp()
+ self.append('.hg/obs.py',
+ "import mercurial.obsolete\n"
++"# 3.2 and later\n"
++"mercurial.obsolete.isenabled = lambda r, opt: True\n"
++"# Dropped in 5.1\n"
+ "mercurial.obsolete._enabled = True")
+ self.append('.hg/hgrc','\n[extensions]\nobs=.hg/obs.py')
+
+
diff -Nru python-hglib-2.6.1/debian/patches/1a318162f06f.patch python-hglib-2.6.1/debian/patches/1a318162f06f.patch
--- python-hglib-2.6.1/debian/patches/1a318162f06f.patch 1969-12-31 19:00:00.0 -0500
+++ python-hglib-2.6.1/debian/patches/1a318162f06f.patch 2019-12-31 17:50:00.0 -0500
@@ -0,0 +1,79 @@
+
+# HG changeset patch
+# User Augie Fackler
+# Date 1576077658 18000
+# Node ID 1a318162f06f171f0fe1ebc26ff016ebbccc0dbd
+# Parent 513ebe91dc7228babfd1096617ba86dc172349d0
+grep: update tests to cope with behavior change in hg 5.2
+
+I wonder if we should make hglib's grep behave consistently across all
+hg versions somehow, but I'm not going to attempt that for now.
+
+diff -r 513ebe91dc72 -r 1a318162f06f tests/test-grep.py
+--- a/tests/test-grep.py Wed Dec 11 09:39:53 2019 -0500
b/tests/test-grep.py Wed Dec 11 10:20:58 2019 -0500
+@@ -10,13 +10,22 @@
+ # no match
+ self.assertEquals(list(self.client.grep(b('c'))), [])
+
+-self.assertEquals(list(self.client.grep(b('a'))),
+- [(b('a'), b('0'), b('a')), (b('b'), b('0'), b('ab'))])
+-self.assertEquals(list(self.client.grep(b('a'), b('a'))),
+- [(b('a'), b('0'), b('a'))])
++if self.client.version >= (5, 2):
++self.assertEquals(list(self.client.grep(b('a'))),
++ [(b('a'), b('a'), b('b'))])
++self.assertEquals(list(self.client.grep(b('a'), b('a'))),
++ [(b('a'), b('a'), b(''))])
+
+-self.assertEquals(list(self.client.grep(b('b'))),
+- [(b('b'), b('0'), b('ab'))])
++self.assertEquals(list(self.client.grep(b('b'))),
++ [(b('b'), b('ab'), b(''))])
++else:
++self.assertEquals(list(self.client.grep(b('a'))),
++ [(b('a'), b('0'), b('a')), (b('b'), b('0'),
Processed: python-hglib: diff for NMU version 2.6.1-1.1
Processing control commands: > tags 937808 + patch Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye Added tag(s) patch. -- 937808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: linux: CPU runs at considerably higher temperatures)
Processing control commands: > severity -1 grave Bug #945055 [linux] linux: CPU runs at considerably higher temperatures Severity set to 'grave' from 'important' -- 945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937730: Bug#934264: Please update (4.6.2?) and provide/switch to python3
On Tue, Dec 31, 2019 at 04:22:09PM -0500, Scott Talbert wrote: > > > That's recorded as TODO item in d/changelog now. > > > > FYI, I just worked on converting envisage to python3: > > https://salsa.debian.org/python-team/modules/python-envisage > > > > I asked Dmitry S. to upload it. > > Hey all, I worked more on mayavi2 and I think is probably ready enough > for upload: > > - Removed wxPython as dependency - only PyQt is currently supported in > mayavi for Python3. This will be pulled in automatically by traitsui, > pyface, etc. > > - Cleaned up all lintian errors/warnings > > - Worked further at getting the tests working. They are a lot closer > but not completely functional. > > - The package builds, installs, and runs fine as best as I can tell, > although I don't know how to do much with it. > > Feel free to upload if you think it is ready. Uploaded. Thanks a lot for your work on this. > Happy New Year, Same to you, Andreas. -- http://fam-tille.de
Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4
Hi László, > File "/<>/tests/admin_inlines/tests.py", line 1, in > from selenium.common.exceptions import NoSuchElementException > ModuleNotFoundError: No module named 'selenium' > > Are you going to upload it fixed to Sid? Thanks for uploading sqlite. This exception was already fixed in #947549… > Happy New Year! … you too. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#937730: Bug#934264: Please update (4.6.2?) and provide/switch to python3
> > > python-envisage has not yet been converted to Python3 and seems to be > > > required: > > > $ mayavi2 > > > Traceback (most recent call last): > > > File "/usr/bin/mayavi2", line 464, in > > > from mayavi.plugins.app import Mayavi, setup_logger > > > File "/usr/lib/python3/dist-packages/mayavi/plugins/app.py", line 19, > > > in > > > from .mayavi_workbench_application import MayaviWorkbenchApplication > > > File > > > "/usr/lib/python3/dist-packages/mayavi/plugins/mayavi_workbench_application.py", > > > line 13, in > > > from envisage.ui.workbench.api import WorkbenchApplication > > > ModuleNotFoundError: No module named 'envisage' > > > > That's recorded as TODO item in d/changelog now. > > FYI, I just worked on converting envisage to python3: > https://salsa.debian.org/python-team/modules/python-envisage > > I asked Dmitry S. to upload it. Hey all, I worked more on mayavi2 and I think is probably ready enough for upload: - Removed wxPython as dependency - only PyQt is currently supported in mayavi for Python3. This will be pulled in automatically by traitsui, pyface, etc. - Cleaned up all lintian errors/warnings - Worked further at getting the tests working. They are a lot closer but not completely functional. - The package builds, installs, and runs fine as best as I can tell, although I don't know how to do much with it. Feel free to upload if you think it is ready. Happy New Year, Scott
Bug#947339: slingshot: should this package be removed?
Hi Sandro (and ftpmasters), On Tue, Dec 24, 2019 at 08:51:22PM -0500, Sandro Tosi wrote: > if I dont hear back within a week with a good reason to keep this > package in debian, i'll file for its removal. As the package's uploader (and upstream author), I support its removal. I have neither the time nor the interest to port it to python3. Thanks, Ryan -- |)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F |\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A signature.asc Description: PGP signature
Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4
On Sun, Dec 29, 2019 at 10:07 PM László Böszörményi (GCS) wrote: > On Sun, Dec 29, 2019 at 5:57 PM Chris Lamb wrote: > > I don't fully understand the ramifications or risks of uploading the > > current Fossil tree I'm afraid so I will have to leave that judgement > > to you. Can you let me know your intention either way so that we don't > > lose this down the cracks and delay Paul's work further? I would not > > want to disable the test and remember to re-enable it again, after all. > OK, I did some testing and couldn't find any immediate problem. Going > to upload the current Fossil tree soon, then follow what problem may > arise in Debian or in upstream issues. The upload is done and built on all architectures. As I see, your experimental upload now should be OK. At least the FTBFS reason is not SQLite3 related but: ERROR: admin_inlines.tests (unittest.loader._FailedTest) [...] File "/<>/tests/admin_inlines/tests.py", line 1, in from selenium.common.exceptions import NoSuchElementException ModuleNotFoundError: No module named 'selenium' Are you going to upload it fixed to Sid? Happy New Year! Laszlo/GCS
Bug#936433: docopt: diff for NMU version 0.6.2-2.2
Control: tags 936433 + patch
Dear maintainer,
I've prepared an NMU for docopt (versioned as 0.6.2-2.2). The diff
is attached to this message.
Regards.
diff -Nru docopt-0.6.2/debian/changelog docopt-0.6.2/debian/changelog
--- docopt-0.6.2/debian/changelog 2019-10-11 00:57:20.0 -0400
+++ docopt-0.6.2/debian/changelog 2019-12-31 14:44:57.0 -0500
@@ -1,3 +1,10 @@
+docopt (0.6.2-2.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #936433
+
+ -- Sandro Tosi Tue, 31 Dec 2019 14:44:57 -0500
+
docopt (0.6.2-2.1) unstable; urgency=medium
[ Matthias Klose ]
diff -Nru docopt-0.6.2/debian/control docopt-0.6.2/debian/control
--- docopt-0.6.2/debian/control 2019-10-11 00:57:20.0 -0400
+++ docopt-0.6.2/debian/control 2019-12-31 14:44:07.0 -0500
@@ -3,8 +3,6 @@
Priority: optional
Maintainer: Agustin Henze
Build-Depends: debhelper (>= 11),
- python-all,
- python-setuptools,
python3-all,
python3-setuptools,
dh-python,
@@ -13,15 +11,6 @@
Vcs-Git: https://salsa.debian.org/debian/docopt.git
Vcs-Browser: https://salsa.debian.org/debian/docopt
-Package: python-docopt
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
-Description: command-line interface description language
- docopt helps you define an interface for your command-line app and
- automatically generate a parser for it. Its interface descriptions are
- based on a formalization of the standard conventions used in help
- messages and man pages.
-
Package: python3-docopt
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}
diff -Nru docopt-0.6.2/debian/python-docopt.examples docopt-0.6.2/debian/python-docopt.examples
--- docopt-0.6.2/debian/python-docopt.examples 2019-10-11 00:57:20.0 -0400
+++ docopt-0.6.2/debian/python-docopt.examples 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-examples/*
diff -Nru docopt-0.6.2/debian/rules docopt-0.6.2/debian/rules
--- docopt-0.6.2/debian/rules 2019-10-11 00:57:20.0 -0400
+++ docopt-0.6.2/debian/rules 2019-12-31 14:44:31.0 -0500
@@ -9,7 +9,7 @@
export PYBUILD_NAME=$(DEB_SOURCE)
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_auto_clean:
dh_auto_clean
Processed: docopt: diff for NMU version 0.6.2-2.2
Processing control commands: > tags 936433 + patch Bug #936433 [src:docopt] docopt: Python2 removal in sid/bullseye Added tag(s) patch. -- 936433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 947855 is serious, severity of 947856 is serious, severity of 947857 is serious ...
Processing commands for cont...@bugs.debian.org: > severity 947855 serious Bug #947855 [php-php-mongodb] php-php-mongodb: Remove depends/build-depends on src:mongodb Severity set to 'serious' from 'normal' > severity 947856 serious Bug #947856 [php-mongo-php-adapter] php-mongo-php-adapter: Remove depends/build-depends on src:mongodb Severity set to 'serious' from 'normal' > severity 947857 serious Bug #947857 [golang-github-juju-testing] golang-github-juju-testing: Remove depends/build-depends on src:mongodb Severity set to 'serious' from 'normal' > block 947743 with 947855 947856 947857 Bug #947743 [ftp.debian.org] RM: mongodb -- RoQA; rc-buggy; un-upgreadable due to license issues; not part of stable; preventing some py2rm work 947743 was not blocked by any bugs. 947743 was not blocking any bugs. Added blocking bug(s) of 947743: 947855, 947857, and 947856 > thanks Stopping processing here. Please contact me if you need assistance. -- 947743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947743 947855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947855 947856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947856 947857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal RC severity updates - 2019-12-31 19:36:42.616848+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # for more details on this severity bump > # python-docopt is a module and has 0 external rdeps or not in testing > severity 936433 serious Bug #936433 [src:docopt] docopt: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal blocks updates - 2019-12-31 19:36:42.550967+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # python-future > block 937773 by 936299 Bug #937773 [src:python-future] python-future: Python2 removal in sid/bullseye 937773 was blocked by: 937330 937144 936338 937240 937599 938016 937300 936523 937445 936508 937605 938270 937901 938861 936999 937773 was blocking: 936326 937558 937695 938168 938244 938528 938756 Added blocking bug(s) of 937773: 936299 > End of message, stopping processing here. Please contact me if you need assistance. -- 937773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947338: cherrytree: should this package be removed?
On Fri, Dec 27, 2019 at 12:33 PM Simon McVittie wrote: > > On Tue, 24 Dec 2019 at 20:12:23 -0500, Sandro Tosi wrote: > > i believe there are several issues with cherrytree: > > > > - python2-only application > > - depends on pygtk, deprecated > > - depends on gtksourceview, deprecated > > - upstream is rewriting it in C++, so there's no hope for a py3k port > > > > i think it's time to remove it (and eventuall re-introduce it in Debian > > once the > > C++ port is completed); if i dont hear back within a week with a good > > reason to > > keep this package in Debian, i'll file for it's removal. > > cherrytree is also the last thing keeping orphaned GNOME 2 package > src:pygtksourceview in Debian, so please ask for that package to be > removed (RoQA) at the same time. reassigned this bug to ftp.d.o and opened #947854 for src:pygtksourceview -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Processed: reassign 947339 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 947339 ftp.debian.org Bug #947339 [src:slingshot] slingshot: should this package be removed? Bug reassigned from package 'src:slingshot' to 'ftp.debian.org'. No longer marked as found in versions slingshot/0.9-2. Ignoring request to alter fixed versions of bug #947339 to the same values previously set > retitle 947339 RM: slingshot -- RoQA; python2-only; upstream dormant since 8+ > years Bug #947339 [ftp.debian.org] slingshot: should this package be removed? Changed Bug title to 'RM: slingshot -- RoQA; python2-only; upstream dormant since 8+ years' from 'slingshot: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 947339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 947338 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 947338 ftp.debian.org Bug #947338 [src:cherrytree] cherrytree: should this package be removed? Bug reassigned from package 'src:cherrytree' to 'ftp.debian.org'. No longer marked as found in versions cherrytree/0.37.6-1.1. Ignoring request to alter fixed versions of bug #947338 to the same values previously set > retitle 947338 RM: cherrytree -- RoQA; python2-only; depends on > pygtk/gtksourceview, deprecated; upstream is rewriting it in C++, so there's > no hope for a py3k port Bug #947338 [ftp.debian.org] cherrytree: should this package be removed? Changed Bug title to 'RM: cherrytree -- RoQA; python2-only; depends on pygtk/gtksourceview, deprecated; upstream is rewriting it in C++, so there's no hope for a py3k port' from 'cherrytree: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 947338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 947853
Processing commands for cont...@bugs.debian.org: > affects 947853 libreoffice-java-common Bug #947853 [libjuh-java,libjurt-java,libridl-java,libunoloader-java] uninstallable due to wrong ure epoch in Breaks: Added indication that 947853 affects libreoffice-java-common > thanks Stopping processing here. Please contact me if you need assistance. -- 947853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: submitter 947853
Processing commands for cont...@bugs.debian.org: > submitter 947853 David Witbrodt Bug #947853 [libjuh-java,libjurt-java,libridl-java,libunoloader-java] uninstallable due to wrong ure epoch in Breaks: Changed Bug submitter to 'David Witbrodt ' from 'Rene Engelhard '. > thanks Stopping processing here. Please contact me if you need assistance. -- 947853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947853: uninstallable due to wrong ure epoch in Breaks:
Package: libjuh-java,libjurt-java,libridl-java,libunoloader-java Version: 1:6.4.0~rc1-3 Severity: serious Tags: pending On Tue, Dec 31, 2019 at 12:54:16PM -0500, David Witbrodt wrote: > It looks like you introduced some "Breaks" in 1:6.4.0~rc1-3 that were not > present before, and now things like libjuh-java have a Breaks on > ure (< 1:6.4.0~beta1-1). The epoch "1" on ure is problematic: > > # apt-cache policy libreoffice ure > libreoffice: > Installed: 1:6.4.0~rc1-4 > [...] > ure: > Installed: 6.4.0~rc1-4 > > As you can see, ure is versioned without the epoch, while libreoffice*.deb > packages _are_ versioned with the epoch. In addition to my reply on-list: Making a proper bugreport out if this since ftp-master is currently broken and a upload will take even if done now... Will mark as reported by you once I have the number. > PS: if I have misdiagnosed anything above, sorry for the noise. It looked > to me like a versioning problem has been introduced, and (if that is so) I > wanted to make you aware of it ASAP. No, completely correct anaysis. Regards, Rene >
Bug#947446: Heads up: version 1:6.4.0~rc1-4 makes libreoffice-java-common uninstallable
Hi, On Tue, Dec 31, 2019 at 12:54:16PM -0500, David Witbrodt wrote: > It looks like you introduced some "Breaks" in 1:6.4.0~rc1-3 that were not > present before, and now things like libjuh-java have a Breaks on Jup. See #947446. > ure (< 1:6.4.0~beta1-1). The epoch "1" on ure is problematic: > > # apt-cache policy libreoffice ure > libreoffice: > Installed: 1:6.4.0~rc1-4 > [...] > ure: > Installed: 6.4.0~rc1-4 > > As you can see, ure is versioned without the epoch, while libreoffice*.deb > packages _are_ versioned with the epoch. *sigh*. Indeed. Will upload a new version ASAP. Regards, Rene
Processed: python3-networkx needs Breaks on packages in buster it breaks
Processing control commands: > block -1 by 945390 945392 Bug #947852 [src:networkx] python3-networkx needs Breaks on packages in buster it breaks 947852 was not blocked by any bugs. 947852 was not blocking any bugs. Added blocking bug(s) of 947852: 945392 and 945390 > affects -1 python3-networkx Bug #947852 [src:networkx] python3-networkx needs Breaks on packages in buster it breaks Added indication that 947852 affects python3-networkx -- 947852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947852: python3-networkx needs Breaks on packages in buster it breaks
Source: networkx Version: 2.4-2 Severity: serious Control: block -1 by 945390 945392 Control: affects -1 python3-networkx The autopkgtest have shown that python3-networkx breaks older versions of some packages, at least androguard and python3-django-hyperkitty. Breaks on the affected versions in buster are needed to prevent people from ending up with known-broken combinations of packages, e.g. during upgrades or when using backports.
Bug#945920: Random Chromium crashes
On Mon, 30 Dec 2019 13:50:36 -0800 Eloston wrote: [...] $ ./debian/rules get-orig-source Hi, this fails for me: [...] test ! -e debian || rm -rf debian cp -r ../debian ./ cp: cannot stat '../debian': No such file or directory make: *** [debian/rules:212: get-orig-source] Error 1 ./debian/rules get-orig-source 441.08s user 24.95s system 92% cpu 8:25.08 total Files and directories: $ ll total 12K drwxr-sr-x 50 toto staff 4.0K Dec 31 14:40 chromium-79.0.3945.79 -rw-r--r-- 1 toto staff 2.9K Dec 31 14:30 chromium-build-deps_79.0.3945.79-1_all.deb -rw-r--r-- 1 toto staff 3.6K Dec 31 12:28 enable-tracing.patch $ pwd /usr/local/src/chromium/chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371 Regards, Toto -- Sent from my GNU Emacs running on GNU/Linux
Bug#947274: marked as done (singularity: missing Build-Depends: python3-setuptools)
Your message dated Tue, 31 Dec 2019 17:26:08 +
with message-id
and subject line Bug#947274: fixed in singularity 1.0a1-2
has caused the Debian Bug report #947274,
regarding singularity: missing Build-Depends: python3-setuptools
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.)
--
947274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity
Version: 1.0a1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
singularity/experimental FTBFS in a minimal chroot:
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
Traceback (most recent call last):
File "setup.py", line 5, in
from setuptools import setup, find_packages
ModuleNotFoundError: No module named 'setuptools'
E: pybuild pybuild:341: clean: plugin distutils failed with: exit code=1:
python3.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:4: clean] Error 255
Andreas
singularity_1.0a1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: singularity
Source-Version: 1.0a1-2
We believe that the bug you reported is fixed in the latest version of
singularity, 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.
Kari Pahula (supplier of updated singularity 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, 31 Dec 2019 16:51:48 +0200
Source: singularity
Architecture: source
Version: 1.0a1-2
Distribution: experimental
Urgency: medium
Maintainer: Kari Pahula
Changed-By: Kari Pahula
Closes: 947274
Changes:
singularity (1.0a1-2) experimental; urgency=medium
.
* Add missing build-dep python3-setuptools (Closes: #947274)
Checksums-Sha1:
6efd0496f6eb2585592245667538727c3608d89a 1789 singularity_1.0a1-2.dsc
060dd67a88b1c73496a6472628c10c52dc076a5b 14492
singularity_1.0a1-2.debian.tar.xz
f5af1efd2392622b1c70971feeb714709303b2c3 7028
singularity_1.0a1-2_source.buildinfo
Checksums-Sha256:
de461ed2147ee7a82ef2ac09f6a6d7c4fcaaa05576f2db322a4e684b1c066fb1 1789
singularity_1.0a1-2.dsc
5020d0f53ede15a2fe1ac308632957b98a6245848bd2118e188ef8f9409afce3 14492
singularity_1.0a1-2.debian.tar.xz
74d7c43766c1f1cd763af3a260ed6be897e60a56098b7f6600f40b11ad69a02e 7028
singularity_1.0a1-2_source.buildinfo
Files:
969bdc2f6a55e6c67aa0ac8e8afb5f01 1789 games optional singularity_1.0a1-2.dsc
6d879c618f3df82b2c175c07ce7527c3 14492 games optional
singularity_1.0a1-2.debian.tar.xz
056ea1196cdbece093cda1704514890f 7028 games optional
singularity_1.0a1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEECcOX/lMRGGlaUzRFhAhn7p2PJlwFAl4LYyAACgkQhAhn7p2P
JlyvLw/8CuAPpdu4McFU+1QbBZbVUdgT/1idEcczg8BdeBw6LnPE9ScwzM3cPp2S
CjIQiJmZ24O55+ehNM6j7kIcnQet4BD3rWMUi48NtCjLlw0dCPLVqG4P3aflLJr2
96zMSbes0280MZFms//tPm4QdkKZB/k8t+a8Lw+mJVafBVQSg1wDeP8A+rW3KpX1
x1goISXiFQWbKlUgmo1oKQfze44uWXJSrZRYD8j25W9daevSYJOc/OuQBqNn4xYz
4WSE000dqNHnzexFMtkIi5oJGirMXRN86tCC29K+dM4ldYA9v0/ZyaFX9zrWSbsn
+CLnAGtdiI277OaW7Gnv+8sTumcN5wCnXH4o0mCKXZA1E/HtkiuxHHzlIgAamZrx
XmWsfccByeLUNByohylv1Q23z6EFfxUWlIhdeaQN6mvszDolid4SabEzm0bXgAgg
FS+WomKk0y9vJFLI3dXxuvtBARxTvS7GrnGrMNStz7FmHVCrRXKDs9l49Ltp7d85
m44WYMIjmZIPuyt5ftDqCg7W37GaeH3kBqTbnreHeaK2s0Y6uboFLFN7PialZWCA
fJozAkW3dVHn9TWILgwhxKr1XR5FRiqzij6wyzuA+j3tp1lzMVrzfkzqTlAKvZAn
urSxvyzqY1WWrXVwbfgxno2K9D9zrXtQoOfk6jBD56+VBUT0EHg=
=sjJr
-END PGP SIGNATURE End Message ---
Bug#947793: marked as done (tkmpeg not working)
Your message dated Tue, 31 Dec 2019 17:26:52 +
with message-id
and subject line Bug#947793: fixed in tkmpeg 1.0.7-2
has caused the Debian Bug report #947793,
regarding tkmpeg not working
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.)
--
947793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tk-mpeg 1.0.7-1
Severity: serious
Tkmpeg does not work and causes saods9 to fail:
Error in startup script: couldn't load file
"/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so":
/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so: undefined symbol:
_ZTVSt9basic_iosIcSt11char_traitsIcEE
while executing
"load /usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so tkmpeg"
("package ifneeded tkmpeg 1.0" script)
invoked from within
"package require tkmpeg"
(file "/usr/share/saods9/library/ds9.tcl" line 207)
This is seen in the saods9 CI tests,
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/saods9/3742299/log.gz
No idea what the cause is.
--- End Message ---
--- Begin Message ---
Source: tkmpeg
Source-Version: 1.0.7-2
We believe that the bug you reported is fixed in the latest version of
tkmpeg, 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.
Ole Streicher (supplier of updated tkmpeg 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: Tue, 31 Dec 2019 15:38:31 +0100
Source: tkmpeg
Architecture: source
Version: 1.0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Tcl/Tk Debian Packagers
Changed-By: Ole Streicher
Closes: 947793
Changes:
tkmpeg (1.0.7-2) unstable; urgency=medium
.
* Add simple (superficial) test
* Add gitlab CI config
* Add CPPFLAGS to CFLAGS
* Re-add stdc++ shared library linking. Closes: #947793
Checksums-Sha1:
f4b5988650a80b40f93490c340673d0e72959101 1970 tkmpeg_1.0.7-2.dsc
bbd43555b8074479b7b2d9bef543a9f4d3bbb2f7 3404 tkmpeg_1.0.7-2.debian.tar.xz
Checksums-Sha256:
e94e8c269d29f94b3e22080af5a7db23bc9a1e14cf0ff88d22fb544ea01fd9d6 1970
tkmpeg_1.0.7-2.dsc
63ffcd1451724a12156747ddd8aeec8bf0ff75b46a7abcf4483a19721018a2fc 3404
tkmpeg_1.0.7-2.debian.tar.xz
Files:
70f55b724fb785abc96ecabcc77e2cf7 1970 interpreters optional tkmpeg_1.0.7-2.dsc
4c16301469165cda1657b1dc493311ea 3404 interpreters optional
tkmpeg_1.0.7-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl4LXlQACgkQmk9WvbkO
GL3OOhAAgQkF7eF8MRcgJHzYyB4MkaUx3UxvsWWtsQbGlUB/Ie1DXAU8XmYK3epN
vMhPrVVLezafyccrW+nPbIxqu6wnDcgENRaqeP/sBo6sugd5q4+4a92Al+OSh3tR
tAH16SzJniD2V2kHo4FgA7tuSXBLNSSmODwSJwTiq+BaWgzC52QH3AyG/yngn/Eh
B2w35nZcaghDy2yWAJueykUr32AC7ZPjdkvYphT8z7lqYzwBucIRtVFhETQGoRKG
nI7bdNFcENuPfotk/jnEDwMVGpEKphvkxsHs5rjxG0NCw8AOvmgNRg6KfVgUnObl
oOreinlTmiGf8rdNfAq9KFqJ6fbrDX1glSTLhGaQAIgPezDv27V7DxMq7OtWwaTa
Z82PkhCpntfifdFN88XSRYIzIVQ1ethV3gby61VOB8gqDR/dXGAOzI/psHds/tCi
V4NnzcTqPT2uZHxmimifbvgBW4KmgYELKyTB4Ju/hbnp/svQFGMnjwnEkzpCYK06
/IUIDgqXkXSMTwVRIiZdG4pET7K6fSP25SxzKspmdBSUURf9olmXDfVZkZgdbYaY
oFVsWOVByVU18mT1BYDCcD8a8MCQ0dD+NH1P6ZFPyo7SwrdSe+rqf3OujepSXDym
BZX8mgTxay738+A4OagJWez9WWhgyiq8c+Ht0VfsasoEpgDRSu8=
=jzpF
-END PGP SIGNATURE End Message ---
Bug#938489: marked as done (sinntp: Python2 removal in sid/bullseye)
Your message dated Tue, 31 Dec 2019 17:26:16 + with message-id and subject line Bug#938489: fixed in sinntp 1.6-0.1 has caused the Debian Bug report #938489, regarding sinntp: 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.) -- 938489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sinntp Version: 1.5-1.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:sinntp 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: sinntp Source-Version: 1.6-0.1 We believe that the bug you reported is fixed in the latest version of sinntp, 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 sinntp 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: Thu, 26 Dec 2019 08:55:37 +0200 Source: sinntp Architecture: source Version: 1.6-0.1 Distribution: unstable Urgency: medium Maintainer: Piotr Lewandowski Changed-By: Adrian Bunk Closes: 783971 827146 938489 Changes: sinntp (1.6-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. - Uses Python 3. (Closes: #938489) * Updated Homepage and debian/watch. (Closes: #783971, #827146) Checksums-Sha1: 3f6031f33438995c32ffded11db44267642d 1972 sinntp_1.6-0.1.dsc ad11b50e592716841194685639e82477f88eade4 20315 sinntp_1.6.orig.tar.gz 145b3ec50180857107e2f03b0c49b7919ce83777 2688 sinntp_1.6-0.1.debian.tar.xz Checksums-Sha256: df05cd14802d6ae38f2e8e430bbf12e69b971d1c6c572f755db21a493ad2abd8 1972 sinntp_1.6-0.1.dsc 351acc6cdf408ba2ce23277a89a90d0a6657932445e6a9effd882446e31560ea 20315 sinntp_1.6.orig.tar.gz 60acf73a679c9ec4e6e15d7eb539e8eac5c11de5948c01c1347d51e7423e8c64 2688 sinntp_1.6-0.1.debian.tar.xz Files:
Bug#947280: marked as done (src:paraview: FTBFS on armel an mipsel: undefined reference to `__atomic_fetch_add_8')
Your message dated Tue, 31 Dec 2019 17:10:29 +
with message-id
and subject line Bug#947280: fixed in paraview 5.7.0-4
has caused the Debian Bug report #947280,
regarding src:paraview: FTBFS on armel an mipsel: undefined reference to
`__atomic_fetch_add_8'
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.)
--
947280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:paraview
Version: 5.7.0-3
Severity: serious
Tags: patch
Justification: FTBFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The same error is spotted in the logs of failed paraview 5.7.0 builds for
armel[1] and mipsel[2]:
/usr/bin/ld: ../../../../lib/mipsel-linux-gnu/libvtkprotobuf-pv5.7.so.5.7:
undefined reference to `__atomic_fetch_add_8'
[1]
https://buildd.debian.org/status/fetch.php?pkg=paraview=armel=5.7.0-3=1576169428=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=paraview=mipsel=5.7.0-1=1570637214=0
Please find attached a patch aiming to solve this problem. Not sure it'll
be sufficient to build successfully, but it should solve this issue at
least.
Thanks,
_g.
- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl4BOnkACgkQ7+hsbH/+
z4Mb8gf/Zv+G/8fE0SNC1wR9l81HtcduHKpMzvaDV7cuk35kAMr/W60ieLqfaT7p
Z9PPgi3YD+CqElw317qbGwwxQI0VuMDxiSVKEXJsZePrg2Ff25wgy4pwSBpSjel+
9kljY0vTp0QxbO2ryZi846aH46PnQF9bppdhUocNg6igeSB/x9TUHICvyhVQ5ZNS
gKDnR5jcKlk5DIr2TRA9Xa/TEIONfoQAjGs+tNwWDYpLQnwYHQ+vT+9gL80U6MkO
jRnVKbHI0V7KQj4saoQf4eqSz2tX29hecrMQcut43YxCX3YDiomV9CxrWDWAbIOf
rzWBeG0mAHxtzdD55XqbtuN+R8jEQQ==
=z9To
-END PGP SIGNATURE-
diff -Nru paraview-5.7.0/debian/changelog paraview-5.7.0/debian/changelog
--- paraview-5.7.0/debian/changelog 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/changelog 2019-12-23 22:33:43.0 +0100
@@ -1,3 +1,10 @@
+paraview (5.7.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New patch libatomic.patch: tentative fix for FTBFS on armel and mipsel
+
+ -- Gilles Filippini Mon, 23 Dec 2019 22:33:43 +0100
+
paraview (5.7.0-3) unstable; urgency=medium
* Hard-code Build-Dep on python3.8-dev. This wasn't being pulled in correctly
diff -Nru paraview-5.7.0/debian/patches/libatomic.patch
paraview-5.7.0/debian/patches/libatomic.patch
--- paraview-5.7.0/debian/patches/libatomic.patch 1970-01-01
01:00:00.0 +0100
+++ paraview-5.7.0/debian/patches/libatomic.patch 2019-12-23
22:33:43.0 +0100
@@ -0,0 +1,22 @@
+Index: paraview-5.7.0/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
+===
+--- paraview-5.7.0.orig/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
paraview-5.7.0/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
+@@ -312,10 +312,16 @@ if (CMAKE_SYSTEM_NAME STREQUAL "Linux")
+ endif ()
+ endif ()
+
++if ((DEB_HOST_MULTIARCH STREQUAL "arm-linux-gnueabi") OR (DEB_HOST_MULTIARCH
STREQUAL "mipsel-linux-gnu"))
++ set(ATOMIC_LIB atomic)
++else ()
++ set(ATOMIC_LIB "")
++endif ()
++
+ target_link_libraries(vtkprotoc
+ PRIVATE
+ ${vtkprotoc_no_as_needed}
+ vtklibprotoc
+ ParaView::protobuf
+-Threads::Threads)
++Threads::Threads ${ATOMIC_LIB})
+ add_executable(ParaView::protoc ALIAS vtkprotoc)
diff -Nru paraview-5.7.0/debian/patches/series
paraview-5.7.0/debian/patches/series
--- paraview-5.7.0/debian/patches/series2019-12-11 10:16:00.0
+0100
+++ paraview-5.7.0/debian/patches/series2019-12-23 22:33:43.0
+0100
@@ -2,3 +2,4 @@
security-format.patch
override-fix.patch
python3.8.patch
+libatomic.patch
diff -Nru paraview-5.7.0/debian/rules paraview-5.7.0/debian/rules
--- paraview-5.7.0/debian/rules 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/rules 2019-12-23 22:33:43.0 +0100
@@ -73,7 +73,8 @@
-DPARAVIEW_ENABLE_PDAL=ON \
-DPARAVIEW_ENABLE_XDMF3=ON \
-DPARAVIEW_ENABLE_MOTIONFX=ON \
- -DPARAVIEW_PLUGIN_ENABLE_EyeDomeLighting=ON
+ -DPARAVIEW_PLUGIN_ENABLE_EyeDomeLighting=ON \
+ -DDEB_HOST_MULTIARCH=$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
override_dh_auto_configure:
Bug#947268: marked as done (gnat-gps-common: ships /usr/share/javascript/prototype/prototype.js)
Your message dated Tue, 31 Dec 2019 16:59:32 + with message-id and subject line Bug#947268: fixed in gnat-gps 19.2-2 has caused the Debian Bug report #947268, regarding gnat-gps-common: ships /usr/share/javascript/prototype/prototype.js to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnat-gps-common Version: 19.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships a file owned by libjs-prototype: /usr/share/javascript/prototype/prototype.js >From the attached log (scroll to the bottom...): Preparing to unpack .../gnat-gps-common_19.2-1_all.deb ... Unpacking gnat-gps-common (19.2-1) ... dpkg: error processing archive /var/cache/apt/archives/gnat-gps-common_19.2-1_all.deb (--unpack): trying to overwrite '/usr/share/javascript/prototype/prototype.js', which is also in package libjs-prototype 1.7.1-3 Errors were encountered while processing: /var/cache/apt/archives/gnat-gps-common_19.2-1_all.deb Andreas libjs-prototype=1.7.1-3_gnat-gps-common=19.2-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gnat-gps Source-Version: 19.2-2 We believe that the bug you reported is fixed in the latest version of gnat-gps, 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. Nicolas Boulenguez (supplier of updated gnat-gps 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, 31 Dec 2019 12:09:26 +0100 Source: gnat-gps Architecture: source Version: 19.2-2 Distribution: experimental Urgency: medium Maintainer: Ludovic Brenta Changed-By: Nicolas Boulenguez Closes: 947268 Changes: gnat-gps (19.2-2) experimental; urgency=medium . * Fix project name for renamed libgpr -> libgnatprj. * Fix creation of javascript symbolic links. Closes: #947268. Checksums-Sha1: a5fdb5b1760e901192a894ab41bcea7a73d47ade 2787 gnat-gps_19.2-2.dsc d6276f50c927c8accf4122b8393bd62b18d32ef1 55732 gnat-gps_19.2-2.debian.tar.xz Checksums-Sha256: f62e16ab6b2cbb05072b1917fc664b7fda21fad37d7c3bd15abda1d36fa28e98 2787 gnat-gps_19.2-2.dsc 0fbbc232c90aebe96ab31c6b0f9f409f1cbbee554789ed339986441a753fe1d3 55732 gnat-gps_19.2-2.debian.tar.xz Files: 766b29ea13b623b298bb4ced6e7a8147 2787 devel optional gnat-gps_19.2-2.dsc b6ab3da7d28e8c6de18c34caa8cfa7ef 55732 devel optional gnat-gps_19.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl4LU1ITHG5pY29sYXNA ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jX1pEACx00o15r6bN0S348ifu2niGnnmlM2t gzXh9Sm0d41VfAe/dLeYqOYkxe/cBPGq70s9bKqEEnKphkTtdYl3zs5tjJ4iVPoV cagMwJdS7dxICTaKXe0OR8WYapRb+pk9OjkzaMVHHHGAvI6ptllk3Qhv3nf9IYli azItIPJ+2aZDaZPUZT/3lLq3/BmXJc/uDmAzFgHp+LZ2x1+NvY0CXYc52/Wh4rAa omBvavIxQXD8ZpYr8LxsySMPqdzUWAlbI2lkGdzt4q/UBJAzoCAfgWcm6CGTeJ/u ItVzROvWQHWrcoE6DIu9Hv9Y7rbIqxjYBdU7oqAePPvYrCVklbFWpy6lcV0iDoa+ +R4Ya5lt5RnmruEC6u/rFbBbvNoesHq72M0U+rx7e1pZlm/5TaYAKLeGpH9/aYuG XLY4c2ClxD/xjjqy77Y+wyif+m+yijima0MTlPkmKgB/Hnqip/mlN05oc740b9Y1 E5lPvQ2J1nXNRjfrsm/xOgMlHOgPDNQVv17I8BqvapA5RszajurqG71yYPNfTXLG B51kUtnDzU5T404fVmUTHq/Wk3alpZC0ZeDDjNojvMoPOIAF7QU6V9pEVu5CI9kl 0wHgzWUx8mJOnstTJ6rhKGErl6TCVbJNSamYxxhHDf3eCGSL6nDDKCRbHdduLiRQ bcKiKulpR/d2pg== =y0m8 -END PGP SIGNATURE End Message ---
Bug#947822: marked as done (geeqie: file conflict with older geeqie-common)
Your message dated Tue, 31 Dec 2019 16:58:35 + with message-id and subject line Bug#947822: fixed in geeqie 1:1.5.1-4 has caused the Debian Bug report #947822, regarding geeqie: file conflict with older geeqie-common 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.) -- 947822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: geeqie Version: 1:1.5.1-3 Severity: serious There was a problem when updating your package (sorry for the German): , | Vorbereitung zum Entpacken von .../6-geeqie_1%3a1.5.1-3_amd64.deb ... | Entpacken von geeqie (1:1.5.1-3) über (1:1.5.1-2) ... | dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-aJs4JD/6-geeqie_1%3a1.5.1-3_amd64.deb (--unpack): | Versuch, »/usr/share/man/man1/geeqie.1.gz« zu überschreiben, welches auch in Paket geeqie-common 1:1.5.1-2 ist | Vorbereitung zum Entpacken von .../7-geeqie-common_1%3a1.5.1-3_all.deb ... | Entpacken von geeqie-common (1:1.5.1-3) über (1:1.5.1-2) ... | Fehler traten auf beim Bearbeiten von: | /tmp/apt-dpkg-install-aJs4JD/6-geeqie_1%3a1.5.1-3_amd64.deb ` Thou shalt not move files between packages without proper Replaces & Breaks - see Policy § 7.6.1. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.6-nouveau (SMP w/2 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) Versions of packages geeqie depends on: ii geeqie-common1:1.5.1-3 ii libc62.29-7 ii libcairo21.16.0-4 ii libexiv2-14 0.25-4 ii libffmpegthumbnailer4v5 2.1.1-0.2+b1 ii libgcc1 1:9.2.1-21 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-2 ii libglib2.0-0 2.62.4-1 ii libgtk2.0-0 2.24.32-4 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-4 ii liblirc-client0 0.10.1-6 ii liblua5.1-0 5.1.5-8.1+b3 ii libpango-1.0-0 1.42.4-8 ii libpangocairo-1.0-0 1.42.4-8 ii libstdc++6 9.2.1-21 ii libtiff5 4.1.0+git191117-1 ii sensible-utils 0.0.12+nmu1 Versions of packages geeqie recommends: ii cups-bsd [lpr] 2.3.1-1 ii exiftran 2.10-3+b1 ii exiv20.25-4 ii imagemagick 8:6.9.10.23+dfsg-2.1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2 ii librsvg2-common 2.46.4-1 pn ufraw-batch pn zenity Versions of packages geeqie suggests: pn geeqie-dbg pn gimp ii libjpeg-turbo-progs [libjpeg-progs] 1:1.5.2-2+b1 pn ufraw pn xpaint -- no debconf information --- End Message --- --- Begin Message --- Source: geeqie Source-Version: 1:1.5.1-4 We believe that the bug you reported is fixed in the latest version of geeqie, 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. Andreas Rönnquist (supplier of updated geeqie 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, 31 Dec 2019 13:57:39 +0100 Source: geeqie Architecture: source Version: 1:1.5.1-4 Distribution: unstable Urgency: medium Maintainer: Andreas Rönnquist Changed-By: Andreas Rönnquist Closes: 947822 Changes: geeqie (1:1.5.1-4) unstable; urgency=medium . * Add Breaks and Replaces on geeqie-common (<= 1.5.1-2) (Closes: #947822) Checksums-Sha1: e7ccfa42bf99da14d0810ff1971184ee09dbd257 2367 geeqie_1.5.1-4.dsc 70e277e109fd1074abe79d924459da667f07d3ae 32148 geeqie_1.5.1-4.debian.tar.xz 528ee539717ea528d32b2ea061248b737055bcf2 14453 geeqie_1.5.1-4_source.buildinfo Checksums-Sha256:
Bug#947816: GeoLite2 databases are now non-free
Nope; that’s what I get for filing bugs while sleep deprived. Sorry for the spam! On Tue, Dec 31, 2019 at 04:10 Faidon Liambotis wrote: > On Mon, Dec 30, 2019 at 11:37:52PM -0500, Harlan Lieberman-Berg wrote: > > > > > > Based on this license change, it seems to me that geoipupdate can no > > longer be in main. Contrib may be a suitable home, however? > > geoipupdate is already in contrib (it has always been that way). Did you > perhaps miss that, or did I misunderstood your question? > > Regards, > Faidon > -- Harlan Lieberman-Berg ~hlieberman
Processed: add blocking bug
Processing commands for cont...@bugs.debian.org:
> block 947074 by 947184
Bug #947074 {Done: Paolo Greppi } [src:node-yarnpkg]
node-yarnpkg_1.21.1-1_all.changes REJECTED
947074 was not blocked by any bugs.
947074 was not blocking any bugs.
Added blocking bug(s) of 947074: 947184
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
947074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: severity of 947499 is serious
Processing commands for cont...@bugs.debian.org: > severity 947499 serious Bug #947499 [libxcb-xinput-dev] libxcb-xinput-dev: Should depend on libxcb-xfixes0-dev Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 947499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#938489 marked as pending in sinntp
Processing control commands: > tag -1 pending Bug #938489 [src:sinntp] sinntp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #938489 to the same tags previously set -- 938489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938489: marked as pending in sinntp
Control: tag -1 pending Hello, Bug #938489 in sinntp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/sinntp/commit/446fec16ab2eb6acede0f755b195ff3775012a09 Import Debian changes 1.6-0.1 sinntp (1.6-0.1) unstable; urgency=medium * Non-maintainer upload. * New upstream release. - Uses Python 3. (Closes: #938489) * Updated Homepage and debian/watch. (Closes: #783971, #827146) (this message was generated automatically) -- Greetings https://bugs.debian.org/938489
Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1
I was affected by the same bug (Freebox Revolution from Free (French ISP) here). I switched to isc-dhcp-client by creating a file /etc/NetworkManager/conf.d/dhcp-client.conf containing the 2 following lines: [main] dhcp=dhclient Then I restarted NetworkManager using this command: sudo service NetworkManager restart and IPv4 is working as expected again. The bug is therefore probably related to the internal dhcp client. Regards
Bug#947032: marked as done (from PIL import Image ModuleNotFoundError No module named PIL)
Your message dated Tue, 31 Dec 2019 13:35:25 + with message-id and subject line Bug#947032: fixed in mnemosyne 2.7+ds-1 has caused the Debian Bug report #947032, regarding from PIL import Image ModuleNotFoundError No module named PIL 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.) -- 947032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947032 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mnemosyne Version: 2.6.1+ds-1 This issue began on first mnemosyne run post install after adjusting font and screen layout properties using its prefs screen. On exiting the first use of the prefs screen, and on each subsequent mnemosyne start, this exception happened: Traceback (innermost last): File "/usr/bin/mnemosyne", line 262, in debug_file=options.debug_file) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 234, in initialise self.start_review() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 357, in start_review self.config()["study_mode"])) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/controllers/default_controller.py", line 103, in set_study_mode study_mode.activate() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/study_modes/scheduled_forgotten_new.py", line 23, in activate self.review_controller().reset(new_only=False) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 53, in reset self.show_new_question() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 115, in show_new_question self.update_dialog() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 194, in update_dialog self.update_qa_area(redraw_all) File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 234, in update_qa_area w.clear_answer() File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 251, in clear_answer self.update_stretch_factors() File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 147, in update_stretch_factors self.estimate_height(self.question_text) File "/usr/lib/python3/dist-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 114, in estimate_height from PIL import Image ModuleNotFoundError: No module named 'PIL' Mnemosyne exits with an error code after reporting the error. Installed the python3 and mnemosyne packages with --no-install-recommends, but their 'apt-cache show' outputs, though likely not enough information, do not indicate that PIL or Pillow are recommended packages of either. $ cat /etc/issue Debian GNU/Linux 10 Python 2 is not installed on the host experiencing the issue: $ python -bash: python: command not found $ which python $ python3 --version Python 3.7.3 $ dpkg --status python3 ... Source: python3-defaults Version: 3.7.3-1 Replaces: python3-minimal (<< 3.1.2-2) Provides: python3-profiler Depends: python3.7 (>= 3.7.3-1~), libpython3-stdlib (= 3.7.3-1) Pre-Depends: python3-minimal (= 3.7.3-1) ... $ cd /usr/lib/python3/dist-packages/mnemosyne $ grep -R ' PIL ' pyqt_ui/review_wdgt.py:from PIL import Image This fixed it: $ sudo apt-get install python3-pil Perhaps this exception can be avoided by just adding python3-pil to the mnemosyne package's 'Depends' attribute. Thanks!--- End Message --- --- Begin Message --- Source: mnemosyne Source-Version: 2.7+ds-1 We believe that the bug you reported is fixed in the latest version of mnemosyne, 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. Julien Puydt (supplier of updated mnemosyne 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: Tue, 31 Dec 2019 14:09:49 +0100 Source: mnemosyne Architecture: source Version: 2.7+ds-1 Distribution: unstable Urgency: medium Maintainer: Robert Lemmen Changed-By: Julien Puydt Closes: 947032 Changes:
Bug#937849: marked as done (python-jedi: Python2 removal in sid/bullseye)
Your message dated Tue, 31 Dec 2019 13:35:45 + with message-id and subject line Bug#937849: fixed in python-jedi 0.15.2-1 has caused the Debian Bug report #937849, regarding python-jedi: 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.) -- 937849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-jedi Version: 0.14.1-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:python-jedi 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: python-jedi Source-Version: 0.15.2-1 We believe that the bug you reported is fixed in the latest version of python-jedi, 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 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Piotr Ożarowski (supplier of updated python-jedi 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: Tue, 31 Dec 2019 14:02:43 +0100 Source: python-jedi Architecture: source Version: 0.15.2-1 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Piotr Ożarowski Closes: 937849 Changes: python-jedi (0.15.2-1) unstable; urgency=medium . [ Sandro Tosi ] * Drop python2 support; Closes: #937849 . [ Piotr Ożarowski ] * New upstream release Checksums-Sha1: 511440e00cac02e6736aa657a2edacbb856a94fa 2171 python-jedi_0.15.2-1.dsc 6ca62b92ddf39f032f113fa50ad916d582ccf230 40677 python-jedi_0.15.2.orig-vim.tar.gz 03782c1ea840b57a5b97275e2e6fe68ef9021424 913832 python-jedi_0.15.2.orig.tar.gz 8404b23427cc227df87cb880de459be817e666cb 3620 python-jedi_0.15.2-1.debian.tar.xz 4e834d43ad48a9bf07d662ef54d296c7377b7eea 7197 python-jedi_0.15.2-1_amd64.buildinfo Checksums-Sha256: 113dd4609b1b0a6c3ec279aa7fb6fce9ff792e8493c0b4ba0161c70fb4a942b4 2171 python-jedi_0.15.2-1.dsc
Bug#947828: freedv FTBFS on most architectures, unconditionally uses x86 asm for avx detection.
Package: freedv
Version: 1.4-1
Severity: serious
Tags: patch
Freedv 1.4 added support for the 2020 codec. This feature is only enabled if
avx support is detected. Comments in the source code claim that this is because
without avx support it will not be processed fast enough for realtime
operation. I have not dug into the question of if the 2020 code benefits from
avx specifically or if avx is just being used as a proxy for general CPU
performance.
Unfortunately the avx detection code is i386/amd64 specific inline assembler,
so it causes a compile failure on everything else.
The attached debdiff puts the asm behind architecture ifdefs and uses a stub
that always returns false on other architectures.
I may or may not NMU this later.
diff -Nru freedv-1.4/debian/changelog freedv-1.4/debian/changelog
--- freedv-1.4/debian/changelog 2019-11-18 03:32:07.0 +
+++ freedv-1.4/debian/changelog 2019-12-31 10:20:26.0 +
@@ -1,3 +1,10 @@
+freedv (1.4-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Put x86 specific code behind ifdefs.
+
+ -- Peter Michael Green Tue, 31 Dec 2019 10:20:26 +
+
freedv (1.4-1) unstable; urgency=medium
* New upstream release
diff -Nru freedv-1.4/debian/patches/put-x86-specific-code-behind-ifdefs
freedv-1.4/debian/patches/put-x86-specific-code-behind-ifdefs
--- freedv-1.4/debian/patches/put-x86-specific-code-behind-ifdefs
1970-01-01 00:00:00.0 +
+++ freedv-1.4/debian/patches/put-x86-specific-code-behind-ifdefs
2019-12-31 10:20:26.0 +
@@ -0,0 +1,27 @@
+Description: Put x86 specific code behind ifdefs.
+Author: Peter Michael Green
+
+--- freedv-1.4.orig/src/fdmdv2_main.cpp
freedv-1.4/src/fdmdv2_main.cpp
+@@ -4496,6 +4496,8 @@ void MainFrame::CloseSerialPort(void)
+ // Tests the underlying platform for AVX support. 2020 needs AVX support to
run
+ // in real-time, and old processors do not offer AVX support
+ //
++#if defined(__x86_64__) || defined(_M_X64) || defined(__i386) ||
defined(_M_IX86)
++
+ void __cpuid(int* cpuinfo, int info)
+ {
+ __asm__ __volatile__(
+@@ -4538,6 +4540,12 @@ void MainFrame::checkAvxSupport(void)
+
+ isAvxPresent = avxSupported;
+ }
++#else
++void MainFrame::checkAvxSupport(void)
++{
++isAvxPresent = false;
++}
++#endif
+
+ #ifdef __UDP_SUPPORT__
+
diff -Nru freedv-1.4/debian/patches/series freedv-1.4/debian/patches/series
--- freedv-1.4/debian/patches/series2019-11-18 03:32:07.0 +
+++ freedv-1.4/debian/patches/series2019-12-31 10:20:26.0 +
@@ -2,3 +2,4 @@
HID-PTT
debian-version
optional-lpcnetfreedv
+put-x86-specific-code-behind-ifdefs
Processed: tagging 944820
Processing commands for cont...@bugs.debian.org: > tags 944820 + pending Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 944820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 944820
Processing commands for cont...@bugs.debian.org: > tags 944820 + buster Bug #944820 [simplesamlphp] SimpleSAMLphp fails when consuming assertion Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 944820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 947805 with 942343, block 942428 with 942343
Processing commands for cont...@bugs.debian.org: > unblock 947805 with 942343 Bug #947805 [upnp-router-control] Please port to gupnp/gssdp 1.2 947805 was blocked by: 942343 947805 was blocking: 942428 Removed blocking bug(s) of 947805: 942343 > block 942428 with 942343 Bug #942428 [release.debian.org] transition: gssdp/gupnp 942428 was blocked by: 947805 942428 was not blocking any bugs. Added blocking bug(s) of 942428: 942343 > thanks Stopping processing here. Please contact me if you need assistance. -- 942428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942428 947805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 947805 with 942343
Processing commands for cont...@bugs.debian.org: > block 947805 with 942343 Bug #947805 [upnp-router-control] Please port to gupnp/gssdp 1.2 947805 was not blocked by any bugs. 947805 was blocking: 942428 Added blocking bug(s) of 947805: 942343 > thanks Stopping processing here. Please contact me if you need assistance. -- 947805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 942343 is serious
Processing commands for cont...@bugs.debian.org: > severity 942343 serious Bug #942343 [src:caja-extensions] caja-extensions: please prepare for gssdp/gupnp 1.2 transition Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 942343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Block fortunes-mario py2removal by related RFS
Processing commands for cont...@bugs.debian.org: > block 945672 by 947773 Bug #945672 [src:fortunes-mario] fortunes-mario: Python2 removal in sid/bullseye 945672 was not blocked by any bugs. 945672 was blocking: 937695 Added blocking bug(s) of 945672: 947773 > kthxbye Stopping processing here. Please contact me if you need assistance. -- 945672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sollya ftbfs with libfplll6
Processing commands for cont...@bugs.debian.org: > tags 947720 + confirmed upstream Bug #947720 [src:sollya] sollya ftbfs with libfplll6 Added tag(s) upstream and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 947720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946022: marked as done (gitlab-workhorse: build-depends on obsolete package.)
Your message dated Tue, 31 Dec 2019 09:49:42 + with message-id and subject line Bug#946022: fixed in gitlab-workhorse 8.16.0+debian-2 has caused the Debian Bug report #946022, regarding gitlab-workhorse: build-depends on obsolete package. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 946022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gitlab-workhorse Version: 8.8.1+debian-3 Severity: serious Tags: patch gitlab-workhorse build-depends on golang-logrus (>= 1.0~), golang-logrus used to be a transitional package, but is now (in testing) only an unversioned virtual package that does not satisfy your build-dependency. Please update your build-dependency to golang-github-sirupsen-logrus-dev --- End Message --- --- Begin Message --- Source: gitlab-workhorse Source-Version: 8.16.0+debian-2 We believe that the bug you reported is fixed in the latest version of gitlab-workhorse, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated gitlab-workhorse 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: Tue, 31 Dec 2019 14:56:45 +0530 Source: gitlab-workhorse Architecture: source Version: 8.16.0+debian-2 Distribution: unstable Urgency: low Maintainer: Debian Go Packaging Team Changed-By: Pirate Praveen Closes: 931662 946022 Changes: gitlab-workhorse (8.16.0+debian-2) unstable; urgency=low . [ Adrian Bunk ] * Update the build dependency from golang-logrus-dev to golang-github-sirupsen-logrus-dev. (Closes: #946022) * Add test dependency on netstat. (Closes: #931662) Checksums-Sha1: 876e7b3b31170c53a24f05adb8d31c46fdf2ee6f 3013 gitlab-workhorse_8.16.0+debian-2.dsc a63c1e7753e8c8118236fb90340363aa3c852ce0 4220 gitlab-workhorse_8.16.0+debian-2.debian.tar.xz 757ac8bec34511b80dc300d87a9aebbbd786201c 5282 gitlab-workhorse_8.16.0+debian-2_source.buildinfo Checksums-Sha256: f9f9dfe9f744c0919d3d4938d267442bc2b614d524dbcc7cd8085574dfd1df9f 3013 gitlab-workhorse_8.16.0+debian-2.dsc 0471f5f42859bbf772ead6b0290111ed7ba6a10bac21d296ee6a7376acc525dd 4220 gitlab-workhorse_8.16.0+debian-2.debian.tar.xz b658ba0b4a3e316c7e3857c0eb1596bbce8552dbcbce264ef0366ad078174b20 5282 gitlab-workhorse_8.16.0+debian-2_source.buildinfo Files: 27a4b14edd3cfffc272573631548910c 3013 httpd optional gitlab-workhorse_8.16.0+debian-2.dsc 521adc3adc47685d4cc18739931e36ca 4220 httpd optional gitlab-workhorse_8.16.0+debian-2.debian.tar.xz 36a8bf407fe60196ee53e338059b4d48 5282 httpd optional gitlab-workhorse_8.16.0+debian-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/OFtr184QaN6dPMgC3aSB2Kmt4UFAl4LFesACgkQC3aSB2Km t4VdyRAAt96KUiTiIpyNClgLA07vjBm4O/5hiedX5uuiIaFX7pYdO+6UThqJ4F0n Q9BSfKzFeDLKo8m4aWwicQBxkqAzwduCC5etDH/s28VuOSNPZLlbV3HkeDORt1il G7VfhoCXbLdj7qE7hnH7U9CSMoqQMmuZS9dt5aWPVPMB/2Xb5I9OYey7O3NDuyZF trg3IewuQ/5f9sZesBY/TRsRbnW4kvZatnz0SSkLrygK4yR3jksPThs+luDREycQ zxxatZ5KbVj55YZmFTTZGnTw/2i1E4nsXrlLi2AliWKkK6n2Xo8hqBz+Y4fy9JQV Ks9VEb7tU5y9Oz+9g12Zuqlg3ab+8Kl3a00BqySaq0+EQsG78XPyz8ocOcjNA6y7 SBeeXztgJUV51dYf8AL+5h3w/ox9Wqpkm2p+PtZJcs+8pffvwcWJxgT4LwVJVlrD R32BqHqcAKtyBOvJ5mHbkNzZEExiUl7iscqA1qov5HswONQ6c7ZfLiKpFs9QwAvE f8HQI95qdoVNymPsH40OlCJaAf+RpXYeyZ4dX1OqNd3WvMhkZPH3s18zyOoFKTdf 4A/nygh58WZXOrDOMYGgzqVj4vbNjaKc2ntNLbXj7Kyj/V4wvp+tUXvNObvG9A+m 5hkKuZPlpM8aRmOLEIjvr0vWLRIsDpekHhnK9fuMR7ahvlGDtWg= =eJmP -END PGP SIGNATURE End Message ---
Processed: Fixing severity after recent GR
Processing commands for cont...@bugs.debian.org: > severity 944748 normal Bug #944748 [nftables] nftables: no init script Severity set to 'normal' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 944748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946022: gitlab-workhorse: diff for NMU version 8.16.0+debian-1.1
Control: tags 931662 + pending Control: tags 946022 + pending Dear maintainer, I've prepared an NMU for gitlab-workhorse (versioned as 8.16.0+debian-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru gitlab-workhorse-8.16.0+debian/debian/changelog gitlab-workhorse-8.16.0+debian/debian/changelog --- gitlab-workhorse-8.16.0+debian/debian/changelog 2019-12-09 18:03:49.0 +0200 +++ gitlab-workhorse-8.16.0+debian/debian/changelog 2019-12-31 11:03:38.0 +0200 @@ -1,3 +1,12 @@ +gitlab-workhorse (8.16.0+debian-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Update the build dependency from golang-logrus-dev +to golang-github-sirupsen-logrus-dev. (Closes: #946022) + * Add test dependency on netstat. (Closes: #931662) + + -- Adrian Bunk Tue, 31 Dec 2019 11:03:38 +0200 + gitlab-workhorse (8.16.0+debian-1) unstable; urgency=medium * Add README.source to explain how to recreate orig.tar diff -Nru gitlab-workhorse-8.16.0+debian/debian/control gitlab-workhorse-8.16.0+debian/debian/control --- gitlab-workhorse-8.16.0+debian/debian/control 2019-12-09 18:03:49.0 +0200 +++ gitlab-workhorse-8.16.0+debian/debian/control 2019-12-31 11:03:38.0 +0200 @@ -25,7 +25,7 @@ golang-github-prometheus-common-dev, golang-procfs-dev, golang-github-stretchr-testify-dev, - golang-logrus-dev (>= 1.0~), + golang-github-sirupsen-logrus-dev, golang-golang-x-crypto-dev, golang-golang-x-net-dev, golang-golang-x-sys-dev (>= 0.0~git20180510.7dfd129~), diff -Nru gitlab-workhorse-8.16.0+debian/debian/tests/control gitlab-workhorse-8.16.0+debian/debian/tests/control --- gitlab-workhorse-8.16.0+debian/debian/tests/control 2019-12-09 18:03:49.0 +0200 +++ gitlab-workhorse-8.16.0+debian/debian/tests/control 2019-12-31 11:03:38.0 +0200 @@ -1,3 +1,3 @@ Tests: listeningPort -Depends: @, psmisc +Depends: @, psmisc, netstat Restrictions: allow-stderr
Processed: gitlab-workhorse: diff for NMU version 8.16.0+debian-1.1
Processing control commands: > tags 931662 + pending Bug #931662 [src:gitlab-workhorse] gitlab-workhorse autopkgtest requires netstat but lacks test dep Ignoring request to alter tags of bug #931662 to the same tags previously set > tags 946022 + pending Bug #946022 [gitlab-workhorse] gitlab-workhorse: build-depends on obsolete package. Ignoring request to alter tags of bug #946022 to the same tags previously set -- 931662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931662 946022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: gitlab-workhorse: diff for NMU version 8.16.0+debian-1.1
Processing control commands: > tags 931662 + pending Bug #931662 [src:gitlab-workhorse] gitlab-workhorse autopkgtest requires netstat but lacks test dep Added tag(s) pending. > tags 946022 + pending Bug #946022 [gitlab-workhorse] gitlab-workhorse: build-depends on obsolete package. Added tag(s) pending. -- 931662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931662 946022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947816: GeoLite2 databases are now non-free
On Mon, Dec 30, 2019 at 11:37:52PM -0500, Harlan Lieberman-Berg wrote: > > > Based on this license change, it seems to me that geoipupdate can no > longer be in main. Contrib may be a suitable home, however? geoipupdate is already in contrib (it has always been that way). Did you perhaps miss that, or did I misunderstood your question? Regards, Faidon
Bug#934370: marked as done (r-cran-fs: autopkgtest regression)
Your message dated Tue, 31 Dec 2019 09:04:29 +
with message-id
and subject line Bug#934370: fixed in r-cran-fs 1.3.1+dfsg-2
has caused the Debian Bug report #934370,
regarding r-cran-fs: autopkgtest regression
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.)
--
934370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-fs
Version: 1.3.1+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 1.3.1+dfsg-1, r-cran-fs has been failing its own
autopkgtests [1] with the following error:
+ test_check("reprex")
+ }
-- 1. Failure: make_filebase() works from absolute infile, outfile (@test-filepa
fs::path_dir(x) not equal to path_temp().
Classes differ: character is not fs_path/character
-- 2. Failure: make_filebase() works from absolute infile, outfile (@test-filepa
fs::path_dir(x) not equal to path_temp().
Classes differ: character is not fs_path/character
== testthat results ===
OK: 25 SKIPPED: 55 FAILED: 2
1. Failure: make_filebase() works from absolute infile, outfile
(@test-filepaths.R#25)
2. Failure: make_filebase() works from absolute infile, outfile
(@test-filepaths.R#29)
Error: testthat unit tests failed
Execution halted
Regards
Graham
[1] https://ci.debian.net/packages/r/r-cran-fs/unstable/amd64/
--- End Message ---
--- Begin Message ---
Source: r-cran-fs
Source-Version: 1.3.1+dfsg-2
We believe that the bug you reported is fixed in the latest version of
r-cran-fs, 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 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dylan Aïssi (supplier of updated r-cran-fs 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: Tue, 31 Dec 2019 09:33:44 +0100
Source: r-cran-fs
Architecture: source
Version: 1.3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Dylan Aïssi
Closes: 934370
Changes:
r-cran-fs (1.3.1+dfsg-2) unstable; urgency=medium
.
* Team upload.
* Fix autopkgtests (Closes: #934370)
Checksums-Sha1:
5fca38346683fba401dace103729c7dbe9979d03 2094 r-cran-fs_1.3.1+dfsg-2.dsc
3fd594ef8f44918bb4a8863778dda3dc80771c97 3568
r-cran-fs_1.3.1+dfsg-2.debian.tar.xz
0e1d2a19ca20a325f0838947b627a6c2853be0f0 8953
r-cran-fs_1.3.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
98dd5bf8ed5f9ef8dca80c91916d06b43e0c953ed87f8896eceb74c7ca1ef9b5 2094
r-cran-fs_1.3.1+dfsg-2.dsc
d16e2ce2ac15ad4e616693d8679e9ff1820e8b9a8984c4d09ef88d0e1ca18e8c 3568
r-cran-fs_1.3.1+dfsg-2.debian.tar.xz
fbaf4e6f3705a6e986fb0fb951d93c3484448c69f86a70b8d646bc37593599ab 8953
r-cran-fs_1.3.1+dfsg-2_amd64.buildinfo
Files:
e138ab0ff6e51b6be56a461de9cee85b 2094 gnu-r optional r-cran-fs_1.3.1+dfsg-2.dsc
5ca236272105141baec8915784929098 3568 gnu-r optional
r-cran-fs_1.3.1+dfsg-2.debian.tar.xz
058b217d52b3db1f21b028dadbba9e9d 8953 gnu-r optional
r-cran-fs_1.3.1+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAl4LCjMSHGRhaXNzaUBk
ZWJpYW4ub3JnAAoJEGEu8WE+BQ9UIz0QAKl8B0lfknSoocYvn9O2Zm7PIGDtI5od
bVRRV7b5MIALrYADzWYq1khM3vaRIbyGrYOR6SIWv4FVhCTD745E7ioYMC1lxid5
nYY9k50ale+ujS4cY/nDpBUcZsDhZqpo9qhg9/6fbs9RlC9OsLjs+mxvggxVBu9H
ycnrm4yR9lJXunwI7Kyw/xZD7rycHOLgZNfIG3JTCnwWl4GMEfStQHLEi7ehBAc+
gejcVx9YiGF8il6tPjlp7/1Ew3dVN5+T5UxJ7bWvipoLDOARZGsbZ0YU0hzBeVEq
ln3IoIYpRGt4IbtPuWPc75XD/kmDPJaTtymkX4fcNVMms7L80NQ7lSchhDp1aphp
IXNLFhDtRHS1E/Is1m9xz6KL2VUduqH82oRVfvyzggECWjl0CqbbbHD5D5qO3OOM
RNFYIpMHtZKfpOAOtKEsePqX7eohAx1iSh9XitI9VNUuMd7+N12YX842T/6OTSh5
yktF5ZxSWi1nNkAnYIo1RCkyR7YiDrLJKsHtG7WzwALdXtmqdof9uFdbSqWotIdv
xQQjNqKDjpc7vYMbE83tuVlNdTr5MPa5JhBQ5ekMGQsVcVccpRh9rC2Wp+qnFZ2S
BbaunZ6ndoRqS3OtM+Qyv5UQhcG9CMr1QoVakM1S9uJ7Ka0k1xD92paqDCC15Op6
YgYWTdpPDbDJ
=70s8
-END PGP SIGNATURE End Message ---
