Bug#997222: libexplain: FTBFS in bullseye
tir. 6. des. 2022 kl. 00:20 skrev Santiago Vila : > > Hi. > > I'm considering to make an upload to fix this in bullseye. > > Am I right to think that the termiox patch with the following changelog > entry is also desirable to be able to build from bullseye+recent kernel? > >- Patch: termiox removed since kernel 5.12, from ALT Linux. > Yes, this still still seems to be the right thing to do. I see that the release that resides in Sid/testing hasn't been pushed to the correct repo on salsa. If it is of interest, the commit can be found in my fork [1] Regards, Håvard [1] https://salsa.debian.org/haava/libexplain/-/commit/cbda43b911408c6aae87321773ce1529526fba01
Bug#988289: htmldoc: CVE-2019-19630
On Mon, 10 May 2021 00:28:43 +0530 Utkarsh Gupta wrote: > Hello, > > That's pretty unfortunate what happened. Since I fixed this in jessie > (back when it was LTS), I'll take care of stretch (now that it's LTS) > and subsequently buster as well. Thanks! > > Hi Utkarsh, I wasn't aware this versioning could be a problem. I can make a release to buster if you want. I would need a sponsor though, so if your determined, I won't rip it out of your hands. Regardless who does it, can we fix CVE-2021-20308 [0] as well? It's marked as unimportant but since we already is preparing packages... I'v prepared a release to unstable and bullseye with the fix for cve-2021-20308 it's on the mentors site now. Håvard [0] https://security-tracker.debian.org/tracker/CVE-2021-20308
Bug#988289: htmldoc: CVE-2019-19630
Hi Utkarsh > >> I can make a release to buster if you want. I would need a sponsor >> though, so if your determined, I won't rip it out of your hands. > > That'd be helpful, thank you! Please let me know when you have a dsc ready? I've got the release ready for buster and uploaded it to mentors [0]. I also sent a request to the RM, for buster-pu, but haven't got any response yet [1]. > >> Regardless who does it, can we fix CVE-2021-20308 [0] as well? It's >> marked as unimportant but since we already is preparing packages... > > Absolutely, by all means! > >> I'v prepared a release to unstable and bullseye with the fix for >> cve-2021-20308 it's on the mentors site now. > > Since this CVE is "unimportant", uploading to bullseye won't make > sense. Rather we can upload to unstable and file an unblock request, > that'd be a good way out here. > > That said, I couldn't find the dsc there, could you sense the link to > dsc for unstable and I'll be very happy to sponsor the upload. Thanks! > :) > I was lucky with the sponsoring to unstable, the package got uploaded earlier today. I also got it unblocked, so it will migrate to bullseye. Håvard [0] https://mentors.debian.net/package/htmldoc/ [1] https://bugs.debian.org/#988365
Bug#988289: htmldoc: CVE-2019-19630
On 12.05.2021 00:13, Utkarsh Gupta wrote: > Hi Håvard, > > On Wed, May 12, 2021 at 2:11 AM Håvard Flaget Aasen > wrote: >> I've got the release ready for buster and uploaded it to mentors [0]. I >> also sent a request to the RM, for buster-pu, but haven't got any >> response yet [1]. > > Thanks for the buster update; uploaded! \o/ > You'll not receive any reply to -pu bug unless the release team has > some problem with it. However, you'll receive a reply when someone > from the release team will batch-accept the uploads from the proposed > queue. > > So basically, we're all good and set! > >> I was lucky with the sponsoring to unstable, the package got uploaded >> earlier today. I also got it unblocked, so it will migrate to bullseye. > > Awesome, thank you! > > > - u > Thanks for the sponsoring Utkarsh! I made a package for stretch as well, and uploaded it to mentors. [0] Though I'm not sure about this lts stuff. So far this package I made just targets "stretch". else it's quite identical to the package you sponsored to buster. If you have your own package it might be better suited. Håvard
Bug#959225: libcap-ng: diff for NMU version 0.7.9-2.2
Package: libcap-ng Version: 0.7.9-2.1 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for libcap-ng (versioned as 0.7.9-2.2) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards, Håvard diff -Nru libcap-ng-0.7.9/debian/changelog libcap-ng-0.7.9/debian/changelog --- libcap-ng-0.7.9/debian/changelog 2019-10-17 23:30:59.0 +0200 +++ libcap-ng-0.7.9/debian/changelog 2020-05-19 14:54:57.0 +0200 @@ -1,3 +1,13 @@ +libcap-ng (0.7.9-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * d/control +- Remove dependency on linux-kernel-headers closes: #959225 +- Remove libattr1-dev as build dependency closes: #953925 +- Build for default python3 version closes: #943627 + + -- Håvard Flaget Aasen Tue, 19 May 2020 14:54:57 +0200 + libcap-ng (0.7.9-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru libcap-ng-0.7.9/debian/control libcap-ng-0.7.9/debian/control --- libcap-ng-0.7.9/debian/control 2019-10-17 23:30:14.0 +0200 +++ libcap-ng-0.7.9/debian/control 2020-05-19 14:53:03.0 +0200 @@ -5,11 +5,10 @@ dh-autoreconf, dh-python , autotools-dev, -libattr1-dev, -linux-kernel-headers, +linux-libc-dev, swig , -libpython3-all-dev , -python3-all-dev:any +libpython3-dev , +python3-dev:any Standards-Version: 3.9.8 Section: libs Homepage: http://people.redhat.com/sgrubb/libcap-ng
Bug#978279: marked as pending in afew
Control: tag -1 pending Hello, Bug #978279 in afew 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/packages/afew/-/commit/ef9a6c241721ec0de127ab3d4e889483fec7c94a Remove regenerated file by scm. Closes: #978279 (this message was generated automatically) -- Greetings https://bugs.debian.org/978279
Bug#978279: marked as pending in afew
Hi Nilesh The reason I haven't uploaded is because I'm not a DD, so I don't have the necessary permissions. I believe the packaging is finished, so if you would do a short review and upload it, it would be appreciated. Regards, Håvard On Thu, 28 Jan 2021 17:56:32 +0530 Nilesh Patra wrote: > Hi Håvard > > Looks like you've fixed this, but not uploaded yet. > Is there anything missing, or should I upload this one? > > Regards, > Nilesh > > > On Thu, 14 Jan 2021 11:09:50 + =?UTF-8?B?SMOldmFyZCBGbGFnZXQgQWFzZW4=?= > wrote: > > Control: tag -1 pending > > > > Hello, > > > > Bug #978279 in afew 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/packages/afew/-/commit/ef9a6c241721ec0de127ab3d4e889483fec7c94a > > > > > > Remove regenerated file by scm. Closes: #978279 > > > > > > (this message was generated automatically) > > -- > > Greetings > > > > https://bugs.debian.org/978279 > > > > > > >
Bug#978279: marked as pending in afew
> > I see that you are a DM, If you agree to add yourself to the uploader's > field, I'll happily grant permissions. Thanks! I updated, and included myself in the uploader's field. > > > > I believe the packaging is finished, so if you would do a short review > > and upload it, it would be appreciated. > > > > Looks good, however I'm unsure about this one change: > > * Why add yourself to copyright?[1] Usually this is done by the person who > debianizes the initial package which is Free Ekanayaka >IMHO, this should be reverted. I reverted the commit. I wasn't aware of this, I'm quite sure I've seen people adding their names to this field before. > > [1]: > https://salsa.debian.org/python-team/packages/afew/-/commit/b1431c378d6e44f4e706570b238ffed072c3b61b > Both changes has been pushed to salsa Håvard
Bug#975834: python-blosc: FTBFS: dh_auto_configure: error: pybuild --configure -i python{version} -p "3.8 3.9" returned exit code 13
Hi Adrian I believe there has been some mixing with the bugs here. Bug #975834 [0] is not a duplicate of #976569 [1] and should not have been merged. I believe #975834 was a problem with CMake in python-blosc, which was fixed in version 1.9.2+ds1-2 with this commit [2]. The bug #975834 happened when c-blosc was still at version 1.17.1+ds1-1. Bug #976569 happened when c-blosc was updated to 1.20.1+ds1-1 and got compiled without snappy support. which is the reason for the bug. Regards, Håvard [0] https://bugs.debian.org/cgi-bin/#975834 [1] https://bugs.debian.org/cgi-bin/#976569 [2] https://salsa.debian.org/python-team/packages/python-blosc/-/commit/8e961cd6ae1c82eed6170a6683acb209fb08714a
Bug#1002347: marked as pending in python-boltons
Control: tag -1 pending Hello, Bug #1002347 in python-boltons 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/packages/python-boltons/-/commit/ba4cdc1095d553d92fdd9b2207b87a426a5469be Cherry-pick upstream patch, py3.10 compatibility. Closes: #1002347 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002347
Bug#1001429: marked as pending in python-qtpy
Control: tag -1 pending Hello, Bug #1001429 in python-qtpy 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/packages/python-qtpy/-/commit/ed3dcde6b69ec74e74f075e5156d4bebe2655eac autopkgtest: Add allow-stderr as restriction. Closes: #1001429 Tests fails because of a deprecation warning. (this message was generated automatically) -- Greetings https://bugs.debian.org/1001429
Bug#1002127: marked as pending in python-trie
Control: tag -1 pending Hello, Bug #1002127 in python-trie 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/packages/python-trie/-/commit/92202ddc78ea795afafa877d5fe6a0c93fe33578 New upstream release supports Python 3.10. Closes: #1002127 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002127
Bug#1000732: marked as pending in python-click-threading
Control: tag -1 pending Hello, Bug #1000732 in python-click-threading 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/packages/python-click-threading/-/commit/aaaee62067b52199ea3f56fad6033b8ad720ad50 New upstream release. Closes: #996337, #997480, #1000732 Compatible with python3-click version 8.0 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000732
Bug#1000552: marked as pending in python-agate-excel
Control: tag -1 pending Hello, Bug #1000552 in python-agate-excel 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/packages/python-agate-excel/-/commit/96ab4100e6fc19a81fb6e952117108868e30848c New upstream release. Closes: #1000552 New release is compatible with openpyxl version 3.0.9 (this message was generated automatically) -- Greetings https://bugs.debian.org/1000552
Bug#1000953: c-blosc: FTBFS on mips64el
ons. 1. des. 2021 kl. 11:39 skrev Bastian Germann : > > Source: c-blosc > Severity: serious > Version: 1.21.1+ds2-1 > > The build fails on mips64el with: > > 98% tests passed, 35 tests failed out of 1651 > > Total Test time (real) = 452.24 sec > > The following tests FAILED: > 1 - test_api (Failed) > 2 - test_bitshuffle_leftovers (Failed) > 270 - test_compressor (Failed) > 672 - test_noinit (Failed) > 673 - test_nolock (Failed) > 674 - test_nthreads (Failed) > 1606 - test_compat_blosc-1.11.1-blosclz.cdata (Failed) > 1607 - test_compat_blosc-1.11.1-lz4.cdata (Failed) > 1608 - test_compat_blosc-1.11.1-lz4hc.cdata (Failed) > 1609 - test_compat_blosc-1.11.1-snappy.cdata (Failed) > 1610 - test_compat_blosc-1.11.1-zlib.cdata (Failed) > 1611 - test_compat_blosc-1.11.1-zstd.cdata (Failed) > 1612 - test_compat_blosc-1.14.0-blosclz.cdata (Failed) > 1613 - test_compat_blosc-1.14.0-lz4.cdata (Failed) > 1614 - test_compat_blosc-1.14.0-lz4hc.cdata (Failed) > 1615 - test_compat_blosc-1.14.0-snappy.cdata (Failed) > 1616 - test_compat_blosc-1.14.0-zlib.cdata (Failed) > 1617 - test_compat_blosc-1.14.0-zstd.cdata (Failed) > 1618 - test_compat_blosc-1.18.0-blosclz-bitshuffle.cdata (Failed) > 1619 - test_compat_blosc-1.18.0-blosclz.cdata (Failed) > 1620 - test_compat_blosc-1.18.0-lz4-bitshuffle.cdata (Failed) > 1621 - test_compat_blosc-1.18.0-lz4.cdata (Failed) > 1622 - test_compat_blosc-1.18.0-lz4hc.cdata (Failed) > 1623 - test_compat_blosc-1.18.0-zlib.cdata (Failed) > 1624 - test_compat_blosc-1.18.0-zstd.cdata (Failed) > 1625 - test_compat_blosc-1.3.0-blosclz.cdata (Failed) > 1626 - test_compat_blosc-1.3.0-lz4.cdata (Failed) > 1627 - test_compat_blosc-1.3.0-lz4hc.cdata (Failed) > 1628 - test_compat_blosc-1.3.0-snappy.cdata (Failed) > 1629 - test_compat_blosc-1.3.0-zlib.cdata (Failed) > 1630 - test_compat_blosc-1.7.0-blosclz.cdata (Failed) > 1631 - test_compat_blosc-1.7.0-lz4.cdata (Failed) > 1632 - test_compat_blosc-1.7.0-lz4hc.cdata (Failed) > 1633 - test_compat_blosc-1.7.0-snappy.cdata (Failed) > 1634 - test_compat_blosc-1.7.0-zlib.cdata (Failed) > Errors while running CTest > make[1]: *** [Makefile:94: test] Error 8 > make[1]: Leaving directory '/<>/obj-mips64el-linux-gnuabi64' > dh_auto_test: error: cd obj-mips64el-linux-gnuabi64 && make -j4 test > ARGS\+=--verbose ARGS\+=-j4 returned exit code 2 > I believe it's related to cmake and the recently updated package. The previous version of c-blosc (1.21.1+ds1-1) uploaded 2021-10-08 used cmake with version 3.21.3-4, it built successfully. Building c-blosc with the current version of cmake fails, as does the earlier versions of c-blosc, I tested 1.17.1+ds1-1, 1.20.1+ds1-2 and 1.21.1+ds1-1. What's strange is that it's only on mips64el the testsuite fails, none of the other architectures seems to be affected. I have yet to discover where the fault lies, if it's cmake itself or the CMakeLists.txt in c-blosc. The solution to make the testsuite succeed is to override the cmake flag provided by debhelper '-DCMAKE_BUILD_TYPE=None' Changing this to 'Release' is enough to make the testsuite succeed. Regards, Håvard
Bug#995290: wand: FTBFS with imagemagick 6.9.12.20
Control: tags -1 moreinfo On Wed, 29 Sep 2021 10:26:41 +0200 Johannes Schauer Marin Rodrigues wrote: > Source: wand > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > Control: block #994540 by -1 > > Hi, > > wand FTBFS with imagemagick 8:6.9.12.20+dfsg1-1.1 from experimental. The > build log is attached. It seems the new imagemagick version needs some > changes to the expected hashes in the tests. > > Thanks! > > cheers, josch Hi, It looks like Imagemagick has changed some configure options. In commit [1] they changed support for FFTW from default enabled to default disabled. Was it your intent to drop support for FFTW? If so, I need to disable the corresponding tests. This should only affect two of the tests, I can't reproduce the strange color failures. Håvard [1] https://github.com/ImageMagick/ImageMagick6/commit/3e34aa8bdf295e0a9d1630eab6c45cbdc2d90d4f#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810
Bug#938909: Dealing with zope.interface unsatisfiable build-dependency.
If you still wish to disable tests for python 2, you might be looking for this export PYBUILD_DISABLE_python2=test That line in debian/rules should work. You have some more options here: https://wiki.debian.org/Python/Pybuild and perhaps the manpages. On 07.12.2019 09:12, peter green wrote: On 07/12/2019 07:47, peter green wrote: It would be preferable to only disable the testsuite for python2, but I have no idea how to do that, so my current debdiff disables the testsuite completely, I also ran into an issue with the package's clean target not cleaning up properly. Just realized I added moreutils to the build-depends, planning to use it in the clean target fix, but in the end I decided to just delete the file in question. So that build-dep should be dropped before upload.
Bug#922325: marked as pending in pep8-naming
Control: tag -1 pending Hello, Bug #922325 in pep8-naming 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/pep8-naming/commit/acac6b430d0d5c618697990b8682ed899b3becb5 Update autopkgtest. closes: #922325 (this message was generated automatically) -- Greetings https://bugs.debian.org/922325
Bug#942735: (no subject)
In the subject you are speaking of directories, but you do want the directories appended with an m? Is it the files /usr/lib/python3/dist-packages/persistent/*38*.so you want changed to *38m*.so?
Bug#942791: marked as pending in pymssql
Control: tag -1 pending Hello, Bug #942791 in pymssql 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/pymssql/commit/d27767db7b5132258c373c516f847f53a3228dc4 Add 0003-Remove-platform.linux_distribution.patch closes: #942791 (this message was generated automatically) -- Greetings https://bugs.debian.org/942791
Bug#946625: scipy: autopkgtest regularly times out
I might be way off here, but if you want to skip test you can create a patch with this above the class or function you want to skip. -- @pytest.mark.skip(reason="no way of currently testing this") -- More info here [1] This will of course skip the tests at build time as well. I also saw some tests that was marked '@pytest.mark.slow'. These can also be skipped using 'pytest -k-slow' though you might skip over more tests than you want. I must admit I'm on thin ice here, cause I don't even know how your script runs.. [1]: https://docs.pytest.org/en/latest/skipping.html#skip
Bug#947326: antimony: diff for NMU version 0.9.3-1.1
Control: tags 947326 + patch
Control: tags 947326 + pending
Control: tags 947479 + patch
Control: tags 947479 + pending
Dear maintainer,
I've prepared an NMU for antimony (versioned as 0.9.3-1.1) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.
Not sure how long it will be delayed
Regards.
Håvard
diff -Nru antimony-0.9.3/debian/changelog antimony-0.9.3/debian/changelog
--- antimony-0.9.3/debian/changelog 2018-08-28 01:20:45.0 +0200
+++ antimony-0.9.3/debian/changelog 2020-01-06 10:39:41.0 +0100
@@ -1,3 +1,25 @@
+antimony (0.9.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Ondřej Nový ]
+ * d/control: Set Vcs-* to salsa.debian.org
+
+ [ Tiago Bortoletto Vaz ]
+ * Add MPL-2.0 notice to debian/copyright.
+ * Add Boost license notice to debian/copyright.
+
+ [ Håvard Flaget Aasen ]
+ * Explicit build-dependency on dh-python. closes: #947326
+ * Use new CMake discovery for python and boost::python. closes: #947479
+- Patch from Ubuntu.
+ * This package embeds python3, and is only built against the default
+version. Change build-dependency to python3-dev.
+- Patch from Ubuntu.
+ * Remove duplicated header in debian/copyright
+
+ -- Håvard Flaget Aasen Mon, 06 Jan 2020 10:39:41
+0100
+
antimony (0.9.3-1) unstable; urgency=low
* Initial packaging. Based on Peter Felecan package work
diff -Nru antimony-0.9.3/debian/control antimony-0.9.3/debian/control
--- antimony-0.9.3/debian/control 2018-08-28 01:20:45.0 +0200
+++ antimony-0.9.3/debian/control 2020-01-06 09:29:43.0 +0100
@@ -5,8 +5,9 @@
Vcs-Git: https://salsa.debian.org/debian/antimony.git
Maintainer: Tiago Bortoletto Vaz
Build-Depends: debhelper (>= 9),
+ dh-python,
libpng-dev,
- python3-all-dev,
+ python3-dev,
libboost-all-dev,
libgl1-mesa-dev,
lemon,
diff -Nru antimony-0.9.3/debian/copyright antimony-0.9.3/debian/copyright
--- antimony-0.9.3/debian/copyright 2018-08-28 01:20:45.0 +0200
+++ antimony-0.9.3/debian/copyright 2020-01-06 09:30:54.0 +0100
@@ -44,7 +44,6 @@
(See accompanying file LICENSE_1_0.txt or copy at
http://www.boost.org/LICENSE_1_0.txt)
.
-License: Boost-1.0
Boost Software License - Version 1.0 - August 17th, 2003
.
Permission is hereby granted, free of charge, to any person or organization
diff -Nru
antimony-0.9.3/debian/patches/0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
antimony-0.9.3/debian/patches/0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
---
antimony-0.9.3/debian/patches/0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
1970-01-01 01:00:00.0 +0100
+++
antimony-0.9.3/debian/patches/0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
2020-01-06 09:29:43.0 +0100
@@ -0,0 +1,128 @@
+From: Dimitri John Ledkov
+Date: Sun, 27 Oct 2019 14:42:04 +
+Subject: Use new CMake Python discovery, with matching Boost::Python abi.
+
+CMake has a new Python discovery module, that can also export
+major/minor version numbers. Switch to using it.
+
+Boost, has also moved on to standard pythonXY abi component name
+across all distributions/OS, thus use matching version ABI.
+
+If one wants to compile against much older Boost, I guess we could add
+fallback to search for Boost python3 component, but IMHO this should
+not be necessory.
+---
+ CMakeLists.txt | 20 ++--
+ app/CMakeLists.txt | 2 +-
+ lib/fab/CMakeLists.txt | 6 +++---
+ lib/graph/CMakeLists.txt | 6 +++---
+ 4 files changed, 9 insertions(+), 25 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index a325f28..d6434e3 100644
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -8,29 +8,13 @@ set(CMAKE_CXX_FLAGS_DEBUG"-O0")
+
+
+
+-find_package(PythonLibs 3.3 REQUIRED)
++find_package(Python 3.3 REQUIRED COMPONENTS Interpreter Development)
+
+ if (WIN32)
+ add_definitions("-DBOOST_PYTHON_STATIC_LIB")
+ endif()
+
+-if (WIN32)
+-find_package(Boost REQUIRED COMPONENTS python3)
+-elseif (APPLE)
+-foreach (PYTHON_NAME python3 python36 python37)
+-find_package(Boost QUIET COMPONENTS ${PYTHON_NAME})
+-if (${Boost_FOUND})
+-break()
+-endif()
+-endforeach()
+-elseif (UNIX)
+-foreach (PYTHON_NAME python3 python-py36 python-py35 python-py34)
+-find_package(Boost QUIET COMPONENTS ${PYTHON_NAME})
+-if (${Boost_FOUND})
+-break()
+-endif()
+-endforeach()
+-endif()
++find_package(Boost REQUIRED COMPONENTS
python${Python_VERSION_MAJOR}${Python_VERSION_MINOR})
+
+ if (NOT ${Boost_FOUND})
+ message(FATAL_ERROR "Could not find boost::python3")
+diff --git a/app/CMakeLists.txt b/app/CMakeLists.txt
+index ebaff55..cf950d3 100644
+--- a/app/CMakeLists.tx
Bug#997733: marked as pending in pycryptodome
Control: tag -1 pending Hello, Bug #997733 in pycryptodome 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/packages/pycryptodome/-/commit/3b901395845196709fe133e082f9b6586394e5f3 Patch to add compatibility with spinx > 4.0 Closes: #997733 (this message was generated automatically) -- Greetings https://bugs.debian.org/997733
Bug#952332: kxd: diff for NMU version 0.14-1.1
Control: tags 952332 + patch
Control: tags 952332 + pending
Dear maintainer,
I've prepared an NMU for kxd (versioned as 0.14-1.1) and
uploaded it to mentors. Please feel free to tell me if I
should remove it.
Regards,
Håvard
diff -Nru kxd-0.14/debian/changelog kxd-0.14/debian/changelog
--- kxd-0.14/debian/changelog 2019-10-03 18:28:56.0 +0200
+++ kxd-0.14/debian/changelog 2020-04-05 08:29:46.0 +0200
@@ -1,3 +1,12 @@
+kxd (0.14-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Set absolute path in d/rules closes: #952332
+ * Cherry-pick upstream commit, needed for upstream testsuite.
+0001-tests-Add-missing-conn.getresponse-which-was-causing.patch
+
+ -- Håvard Flaget Aasen Sun, 05 Apr 2020 08:29:46 +0200
+
kxd (0.14-1) unstable; urgency=medium
[ Michael Stapelberg ]
diff -Nru kxd-0.14/debian/patches/0001-tests-Add-missing-conn.getresponse-which-was-causing.patch kxd-0.14/debian/patches/0001-tests-Add-missing-conn.getresponse-which-was-causing.patch
--- kxd-0.14/debian/patches/0001-tests-Add-missing-conn.getresponse-which-was-causing.patch 1970-01-01 01:00:00.0 +0100
+++ kxd-0.14/debian/patches/0001-tests-Add-missing-conn.getresponse-which-was-causing.patch 2020-04-05 08:05:44.0 +0200
@@ -0,0 +1,30 @@
+From: Alberto Bertogli
+Date: Sun, 29 Mar 2020 11:40:46 +0100
+Subject: tests: Add missing conn.getresponse() which was causing false
+ negatives
+
+Somewhere around Python 3.8, http.client.HTTPConnection objects changed
+how result handling was done, and ignored SSL errors until
+.getresponse() was called.
+
+This causes the test_no_local_cert to fail, even though the server is
+responding correctly.
+
+This patch fixes this by adding a .getresponse() call, which forces
+validation of the result and makes the test pass again.
+---
+ tests/run_tests | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/tests/run_tests b/tests/run_tests
+index d6d4ba2..9499bfe 100755
+--- a/tests/run_tests
b/tests/run_tests
+@@ -407,6 +407,7 @@ class TrickyRequests(TestCase):
+ conn = self.https_connection("localhost", 19840)
+ try:
+ conn.request("GET", "/v1/")
++conn.getresponse()
+ conn.close()
+ except ssl.SSLError as err:
+ self.assertEqual(err.reason, "SSLV3_ALERT_BAD_CERTIFICATE")
diff -Nru kxd-0.14/debian/patches/series kxd-0.14/debian/patches/series
--- kxd-0.14/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ kxd-0.14/debian/patches/series 2020-04-05 08:05:44.0 +0200
@@ -0,0 +1 @@
+0001-tests-Add-missing-conn.getresponse-which-was-causing.patch
diff -Nru kxd-0.14/debian/rules kxd-0.14/debian/rules
--- kxd-0.14/debian/rules 2019-10-03 18:28:56.0 +0200
+++ kxd-0.14/debian/rules 2020-04-05 08:01:15.0 +0200
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
# -*- makefile -*-
-export GOCACHE=$$(pwd)/debian/cache
+export GOCACHE=$(CURDIR)/debian/cache
%:
dh $@
Bug#955248: fdkaac: diff for NMU version 1.0.0-0.1
Control: tags 955248 + patch Control: tags 955248 + pending Dear maintainer, I've prepared an NMU for fdkaac (versioned as 1.0.0-0.1) and uploaded it to mentors. Please feel free to tell me if I should delete it. Regards, Håvard diff -Nru fdkaac-0.6.3/ChangeLog fdkaac-1.0.0/ChangeLog --- fdkaac-0.6.3/ChangeLog 2016-08-26 14:45:05.0 +0200 +++ fdkaac-1.0.0/ChangeLog 2018-09-03 19:04:36.0 +0200 @@ -1,6 +1,44 @@ +2016-08-26 nu774 + + * update ChangeLog [HEAD -> master] + + * bump [origin/master] + + * Ticket #23: quit supporting MPEG-2 AOT + +2016-08-25 nu774 + + * fix libfdkaac encoder version check for SBR_RATIO availability + + * Use our SBR signaling implementation on old libfdkaac + +2015-10-10 nu774 + + * improve MSVC project + +2015-09-21 nu774 + + * fix indents + + * update compat layer, mainly for MSVC14 issue + +2015-07-22 nu774 + + * add platformtoolset in vcxproj + + * fix build issue on MSVC14 + +2015-06-12 nu774 + + * remove an unused variable decl + + * remove an unused variable decl + + * m4af: move internal struct m4af_itmf_entry_t from header + 2015-02-14 nu774 - * update ChangeLog [HEAD] + * update ChangeLog * bump version [v0.6.2] @@ -10,9 +48,9 @@ 2014-09-13 nu774 - * update ChangeLog [origin/master] + * update ChangeLog - * bump version + * bump version [v0.6.1] 2014-09-12 nu774 diff -Nru fdkaac-0.6.3/configure.ac fdkaac-1.0.0/configure.ac --- fdkaac-0.6.3/configure.ac 2016-08-26 14:45:05.0 +0200 +++ fdkaac-1.0.0/configure.ac 2018-09-03 19:04:36.0 +0200 @@ -13,7 +13,7 @@ AM_PROG_CC_C_O AC_CHECK_HEADERS([sys/time.h]) -AC_CHECK_HEADERS([localcharset.h langinfo.h endian.h byteswap.h]) +AC_CHECK_HEADERS([libcharset.h langinfo.h endian.h byteswap.h]) AC_CHECK_HEADERS([fdk-aac/aacenc_lib.h], , AC_MSG_ERROR([libfdk-aac is required])) @@ -38,6 +38,12 @@ AM_CONDITIONAL([FDK_NO_GETOPT_LONG],[test "$ac_cv_func_getopt_long" != "yes"]) AC_SEARCH_LIBS([aacEncOpen],[fdk-aac],[],[],[]) +CHARSET_LIB= +AC_CHECK_LIB([iconv], [locale_charset], + [CHARSET_LIB=-liconv], + [AC_CHECK_LIB([charset], [locale_charset], [CHARSET_LIB=-lcharset])]) +AC_SUBST([CHARSET_LIB]) + AC_CANONICAL_HOST X_PLATFORM=posix diff -Nru fdkaac-0.6.3/debian/changelog fdkaac-1.0.0/debian/changelog --- fdkaac-0.6.3/debian/changelog 2017-01-23 01:39:23.0 +0100 +++ fdkaac-1.0.0/debian/changelog 2020-04-14 13:04:58.0 +0200 @@ -1,3 +1,10 @@ +fdkaac (1.0.0-0.1) unstable; urgency=medium + + * Non-maintainer upload + * New upstream release closes: #955248 + + -- Håvard Flaget Aasen Tue, 14 Apr 2020 13:04:58 +0200 + fdkaac (0.6.3-1) unstable; urgency=medium * New upstream version diff -Nru fdkaac-0.6.3/Makefile.am fdkaac-1.0.0/Makefile.am --- fdkaac-0.6.3/Makefile.am 2016-08-26 14:45:05.0 +0200 +++ fdkaac-1.0.0/Makefile.am 2018-09-03 19:04:36.0 +0200 @@ -23,7 +23,7 @@ dist_man_MANS = man/fdkaac.1 fdkaac_LDADD = \ -@LIBICONV@ -lfdk-aac -lm +@LIBICONV@ @CHARSET_LIB@ -lfdk-aac -lm if FDK_PLATFORM_POSIX fdkaac_SOURCES += \ diff -Nru fdkaac-0.6.3/MSVC/fdk-aac.vcxproj fdkaac-1.0.0/MSVC/fdk-aac.vcxproj --- fdkaac-0.6.3/MSVC/fdk-aac.vcxproj 2016-08-26 14:45:05.0 +0200 +++ fdkaac-1.0.0/MSVC/fdk-aac.vcxproj 2018-09-03 19:04:36.0 +0200 @@ -1,4 +1,4 @@ - + http://schemas.microsoft.com/developer/msbuild/2003";> @@ -24,10 +24,13 @@ fdk-aac -v140_xp -v120_xp -v110_xp -v100 +v141_xp +v140_xp +v120_xp +v110_xp + + +fdk-aac\$(Platform)\$(Configuration) @@ -50,7 +53,7 @@ NotUsing Level3 WIN32;_LIB;%(PreprocessorDefinitions) - ../fdk-aac/libaacenc/include;../fdk-aac/libFDK/include;../fdk-aac/libMpegTPEnc/include;../fdk-aac/libPCMutils/include;../fdk-aac/libSBRenc/include;../fdk-aac/libSYS/include + ../fdk-aac/libaacenc/include;../fdk-aac/libFDK/include;../fdk-aac/libMpegTPEnc/include;../fdk-aac/libPCMutils/include;../fdk-aac/libSACenc/include;../fdk-aac/libSBRenc/include;../fdk-aac/libSYS/include @@ -71,7 +74,6 @@ - @@ -91,6 +93,7 @@ + @@ -109,6 +112,8 @@ + + @@ -122,7 +127,20 @@ - + + + + + + + + + + + + + + @@ -136,19 +154,18 @@ + + - - - + - diff -Nru fdkaac-0.6.3/MSVC/fdkaac.vcxproj fdkaac-1.0.0/MSVC/fdkaac.vcxproj --- fdkaac-0.6.3/MSVC/fdkaac.vcxproj 2016-08-26 14:45:05.0 +0200 +++ fdkaac-1.0.0/MSVC/fdkaac.vcxproj 2018-09-03 19:04:36.0 +0200 @@ -24,10 +24,10 @@ fdkaac -v140_xp -v120_xp -v110_xp -v100 +v141_xp +
Bug#951986: feedreader: diff for NMU version 2.10.0-1.1
Control: tags 951986 + patch
Control: tags 951986 + pending
Dear maintainer,
I've prepared an NMU for feedreader (versioned as 2.10.0-1.1) and
uploaded it to mentors. Please feel free to tell me if I should remove it.
Regards,
Håvard
diff -Nru feedreader-2.10.0/debian/changelog feedreader-2.10.0/debian/changelog
--- feedreader-2.10.0/debian/changelog 2019-07-21 13:34:34.0 +0200
+++ feedreader-2.10.0/debian/changelog 2020-04-14 14:16:14.0 +0200
@@ -1,3 +1,11 @@
+feedreader (2.10.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Cherry-pick upstream commit. closes: #951986
+0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch
+
+ -- Håvard Flaget Aasen Tue, 14 Apr 2020 14:16:14 +0200
+
feedreader (2.10.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru feedreader-2.10.0/debian/patches/0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch feedreader-2.10.0/debian/patches/0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch
--- feedreader-2.10.0/debian/patches/0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch 1970-01-01 01:00:00.0 +0100
+++ feedreader-2.10.0/debian/patches/0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch 2020-04-13 17:45:18.0 +0200
@@ -0,0 +1,34 @@
+From: PopeRigby
+Date: Wed, 15 Jan 2020 16:28:42 -0800
+Subject: Fix infinite loading icon after opening article in browser
+
+---
+ src/Backend/FeedServer.vala | 2 +-
+ src/Widgets/SharePopover.vala | 1 +
+ 2 files changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/src/Backend/FeedServer.vala b/src/Backend/FeedServer.vala
+index 7660045..ce39f74 100644
+--- a/src/Backend/FeedServer.vala
b/src/Backend/FeedServer.vala
+@@ -57,7 +57,7 @@ public class FeedReader.FeedServer : GLib.Object {
+ var secrets = Secret.Collection.for_alias_sync(secret_service, Secret.COLLECTION_DEFAULT, Secret.CollectionFlags.NONE);
+ if(secrets == null)
+ {
+- secrets = Secret.Collection.create_sync(secret_service, "Login", Secret.COLLECTION_DEFAULT, Secret.CollectionCreateFlags.COLLECTION_CREATE_NONE);
++ secrets = Secret.Collection.create_sync(secret_service, "Login", Secret.COLLECTION_DEFAULT, Secret.CollectionCreateFlags.NONE);
+ }
+
+ var settings_backend = null; // FIXME: Why does SettingsBackend.get_default() crash on Arch Linux?
+diff --git a/src/Widgets/SharePopover.vala b/src/Widgets/SharePopover.vala
+index 0998f92..3c45ff7 100644
+--- a/src/Widgets/SharePopover.vala
b/src/Widgets/SharePopover.vala
+@@ -136,6 +136,7 @@ public class FeedReader.SharePopover : Gtk.Popover {
+ shareInternal(id, url);
+ string idString = (id == null || id == "") ? "" : @" to $id";
+ Logger.debug(@"bookmark: $url$idString");
++ shareDone();
+ }
+ }
+
diff -Nru feedreader-2.10.0/debian/patches/series feedreader-2.10.0/debian/patches/series
--- feedreader-2.10.0/debian/patches/series 2019-07-21 13:34:34.0 +0200
+++ feedreader-2.10.0/debian/patches/series 2020-04-13 18:00:00.0 +0200
@@ -1 +1,2 @@
fix_some_spelling_errors.patch
+0002-Fix-infinite-loading-icon-after-opening-article-in-b.patch
Bug#951979: Anything related to recent patch from Ubuntu?
Hi, I looked into it, you are correct, it has everything to do with the patch. Removing 0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch fixes the ftbfs. I don't know what changed when cmake upgraded from 3.15.4 -> 3.16.3 I also don't know if this is the best solution, but for now it works. You might see if it builds against libboost 1.71.0 which is in experimental. The upstream author might look into this, for this patch is also a commit upstream [1] and there are other people that probably has the same issue [2] I hope this gets it going again, and sorry for the trouble this patch has created. Håvard [1] https://github.com/mkeeter/antimony/commit/222ae890da81a1eacf5c528598e79a91c4bab58a [2] https://github.com/mkeeter/antimony/issues/211
Bug#951945: cramfsswap: diff for NMU version 1.4.1-1.2
Package: cramfsswap Version: 1.4.1-1.1 Severity: normal Tags: patch Dear maintainer, I've prepared an NMU for cramfsswap (versioned as 1.4.1-1.2) and uploaded it to DELAYED/XX. Please feel free to tell me if I should delay it longer. Regards. Håvard diff -Nru cramfsswap-1.4.1/debian/changelog cramfsswap-1.4.1/debian/changelog --- cramfsswap-1.4.1/debian/changelog 2016-12-18 12:50:25.0 +0100 +++ cramfsswap-1.4.1/debian/changelog 2020-03-20 20:30:45.0 +0100 @@ -1,3 +1,14 @@ +cramfsswap (1.4.1-1.2) unstable; urgency=medium + + * Non-maintainer upload. + * Reorder library in Makefile closes: #951945 + * Fix FTCBFS: closes: #871410 +- Let dh_auto_build pass cross compilers to make +- Make compiler substitutable in Makefile +Patch by Helmut Grohne + + -- Håvard Flaget Aasen Fri, 20 Mar 2020 20:30:45 +0100 + cramfsswap (1.4.1-1.1) unstable; urgency=medium * Non-maintainer upload diff -Nru cramfsswap-1.4.1/debian/rules cramfsswap-1.4.1/debian/rules --- cramfsswap-1.4.1/debian/rules 2007-10-14 23:41:26.0 +0200 +++ cramfsswap-1.4.1/debian/rules 2020-03-20 20:17:33.0 +0100 @@ -11,7 +11,7 @@ build: build-stamp build-stamp: dh_testdir - $(MAKE) debian + dh_auto_build -- debian touch build-stamp clean: diff -Nru cramfsswap-1.4.1/Makefile cramfsswap-1.4.1/Makefile --- cramfsswap-1.4.1/Makefile 2007-10-14 23:37:58.0 +0200 +++ cramfsswap-1.4.1/Makefile 2020-03-20 20:16:23.0 +0100 @@ -4,7 +4,7 @@ debian: cramfsswap cramfsswap: cramfsswap.c - gcc -Wall -g -O -o cramfsswap -lz cramfsswap.c + $(CC) -Wall -g -O -o cramfsswap cramfsswap.c -lz strip: strip cramfsswap
Bug#951979: Anything related to recent patch from Ubuntu?
Well I did some more digging.
I believe it's the Python variables which are wrong. Specifically the
${Python_INCLUDE_DIR}
I believe the correct variable is ${Python_INCLUDE_DIRS}
I made a patch, which patches the old patch.
I created a merge request in salsa with the change.
Håvard
Bug#952057: kdocker: diff for NMU version 5.0-1.1
Control: tags 952057 + patch Control: tags 952057 + pending Dear maintainer, I've prepared an NMU for kdocker (versioned as 5.0-1.1) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards, Håvard diff -Nru kdocker-5.0/debian/changelog kdocker-5.0/debian/changelog --- kdocker-5.0/debian/changelog 2016-07-25 14:54:58.0 +0200 +++ kdocker-5.0/debian/changelog 2020-03-30 11:38:07.0 +0200 @@ -1,3 +1,10 @@ +kdocker (5.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Change build-dependency libx11-dev -> libx11-xcb-dev closes: #952057 + + -- Håvard Flaget Aasen Mon, 30 Mar 2020 11:38:07 +0200 + kdocker (5.0-1) unstable; urgency=medium * New upstream release. diff -Nru kdocker-5.0/debian/control kdocker-5.0/debian/control --- kdocker-5.0/debian/control 2016-07-25 03:26:26.0 +0200 +++ kdocker-5.0/debian/control 2020-03-30 11:32:00.0 +0200 @@ -6,7 +6,7 @@ qt5-qmake, qtbase5-dev, qtbase5-dev-tools, - libx11-dev, + libx11-xcb-dev, libxpm-dev, libxmu-dev, libqt5x11extras5-dev,
Bug#951979: antimony: diff for NMU version 0.9.3-1.2
Control: tags 951979 + patch
Control: tags 951979 + pending
Dear maintainer,
I've prepared an NMU for antimony (versioned as 0.9.3-1.2) and
uploaded it to mentors. Please feel free to tell me if I
should remove it.
Regards.
Håvard
diff -Nru antimony-0.9.3/debian/changelog antimony-0.9.3/debian/changelog
--- antimony-0.9.3/debian/changelog 2020-01-06 10:39:41.0 +0100
+++ antimony-0.9.3/debian/changelog 2020-03-30 18:27:18.0 +0200
@@ -1,3 +1,10 @@
+antimony (0.9.3-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add 0003-Change-python-variable-in-cmake.patch closes: #951979
+
+ -- Håvard Flaget Aasen Mon, 30 Mar 2020 18:27:18 +0200
+
antimony (0.9.3-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch
--- antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch 1970-01-01 01:00:00.0 +0100
+++ antimony-0.9.3/debian/patches/0003-Change-python-variable-in-cmake.patch 2020-03-30 18:26:23.0 +0200
@@ -0,0 +1,67 @@
+From: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?=
+Date: Fri, 27 Mar 2020 19:52:14 +0100
+Subject: Change python variable in cmake
+
+---
+ app/CMakeLists.txt | 2 +-
+ lib/fab/CMakeLists.txt | 4 ++--
+ lib/graph/CMakeLists.txt | 4 ++--
+ 3 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/app/CMakeLists.txt b/app/CMakeLists.txt
+index cf950d3..779 100644
+--- a/app/CMakeLists.txt
b/app/CMakeLists.txt
+@@ -175,7 +175,7 @@ add_definitions(-D'GITREV="${GITREV}${GITDIFF}"'
+
+
+ target_include_directories(${ANTIMONY_APP} SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ${AUTOGEN_TARGETS_FOLDER}
+ )
+diff --git a/lib/fab/CMakeLists.txt b/lib/fab/CMakeLists.txt
+index 2f21731..7c0596c 100644
+--- a/lib/fab/CMakeLists.txt
b/lib/fab/CMakeLists.txt
+@@ -67,7 +67,7 @@ add_library(SbFab STATIC
+ )
+
+ target_include_directories(SbFab SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ${PNG_INCLUDE_DIR}
+ )
+@@ -98,7 +98,7 @@ target_link_libraries(SbFabTest SbFab)
+ target_include_directories(SbFabTest SYSTEM PRIVATE
+ ../../vendor
+ ${Boost_INCLUDE_DIRS}
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ )
+
+
+diff --git a/lib/graph/CMakeLists.txt b/lib/graph/CMakeLists.txt
+index 31f7878..d04cc83 100644
+--- a/lib/graph/CMakeLists.txt
b/lib/graph/CMakeLists.txt
+@@ -15,7 +15,7 @@ add_library(SbGraph STATIC
+ )
+
+ target_include_directories(SbGraph SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ )
+ target_link_libraries(SbGraph
+@@ -38,7 +38,7 @@ add_executable(SbGraphTest
+ target_link_libraries(SbGraphTest SbGraph)
+
+ target_include_directories(SbGraphTest SYSTEM PRIVATE
+-${Python_INCLUDE_DIR}
++${Python_INCLUDE_DIRS}
+ ${Boost_INCLUDE_DIRS}
+ ../../vendor
+ )
diff -Nru antimony-0.9.3/debian/patches/series antimony-0.9.3/debian/patches/series
--- antimony-0.9.3/debian/patches/series 2020-01-06 09:29:43.0 +0100
+++ antimony-0.9.3/debian/patches/series 2020-03-30 18:26:23.0 +0200
@@ -1,2 +1,3 @@
bugged_parsercheck
0002-Use-new-CMake-Python-discovery-with-matching-Boost-P.patch
+0003-Change-python-variable-in-cmake.patch
Bug#934949: clips: diff for NMU version 6.30-4.1
Package: clips Version: 6.30-4 Severity: normal Tags: patch pending Dear maintainer, I've prepared an NMU for clips (versioned as 6.30-4.1) and uploaded it to mentors. Please feel free to tell me if I should remove it. Regards. Håvard diff -Nru clips-6.30/debian/changelog clips-6.30/debian/changelog --- clips-6.30/debian/changelog 2017-11-06 22:20:23.0 +0100 +++ clips-6.30/debian/changelog 2020-03-30 20:51:48.0 +0200 @@ -1,3 +1,14 @@ +clips (6.30-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix typo in maintainer address closes: #881009 + * Don't build html files in doc package, so we can remove pdf2htmlex +as build-dependency. closes: #952621, #934949 +- Remove Format: HTML in *.doc-base files +- Edit Makefile in clips_docs.diff + + -- Håvard Flaget Aasen Mon, 30 Mar 2020 20:51:48 +0200 + clips (6.30-4) unstable; urgency=medium * Move pdf2htmlex, sharutils to Build-Depends (Closes: #878841) diff -Nru clips-6.30/debian/clips-doc.doc-base.abstracts clips-6.30/debian/clips-doc.doc-base.abstracts --- clips-6.30/debian/clips-doc.doc-base.abstracts 2017-10-17 23:01:32.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.abstracts 2020-03-30 20:35:09.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/application_abstracts.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/application_abstracts.html -Files: /usr/share/doc/clips-doc/application_abstracts.html diff -Nru clips-6.30/debian/clips-doc.doc-base.apg clips-6.30/debian/clips-doc.doc-base.apg --- clips-6.30/debian/clips-doc.doc-base.apg 2017-10-17 23:01:35.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.apg 2020-03-30 20:35:21.0 +0200 @@ -8,7 +8,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/advanced_programming_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/advanced_programming_guide.html -Files: /usr/share/doc/clips-doc/advanced_programming_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.architecture clips-6.30/debian/clips-doc.doc-base.architecture --- clips-6.30/debian/clips-doc.doc-base.architecture 2017-10-17 23:01:39.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.architecture 2020-03-30 20:35:31.0 +0200 @@ -10,7 +10,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/architecture_manual_v5_1.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/architecture_manual_v5_1.html -Files: /usr/share/doc/clips-doc/architecture_manual_v5_1.html diff -Nru clips-6.30/debian/clips-doc.doc-base.bpg clips-6.30/debian/clips-doc.doc-base.bpg --- clips-6.30/debian/clips-doc.doc-base.bpg 2017-10-17 23:01:41.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.bpg 2020-03-30 20:35:42.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/basic_programming_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/basic_programming_guide.html -Files: /usr/share/doc/clips-doc/basic_programming_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.ig clips-6.30/debian/clips-doc.doc-base.ig --- clips-6.30/debian/clips-doc.doc-base.ig 2017-10-17 23:01:44.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.ig 2020-03-30 20:35:55.0 +0200 @@ -7,7 +7,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/interfaces_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/interfaces_guide.html -Files: /usr/share/doc/clips-doc/interfaces_guide.html diff -Nru clips-6.30/debian/clips-doc.doc-base.usrguide clips-6.30/debian/clips-doc.doc-base.usrguide --- clips-6.30/debian/clips-doc.doc-base.usrguide 2017-10-17 23:01:47.0 +0200 +++ clips-6.30/debian/clips-doc.doc-base.usrguide 2020-03-30 20:36:08.0 +0200 @@ -8,7 +8,3 @@ Format: PDF Files: /usr/share/doc/clips-doc/users_guide.pdf.gz - -Format: HTML -Index: /usr/share/doc/clips-doc/users_guide.html -Files: /usr/share/doc/clips-doc/users_guide.html diff -Nru clips-6.30/debian/control clips-6.30/debian/control --- clips-6.30/debian/control 2017-11-06 22:20:18.0 +0100 +++ clips-6.30/debian/control 2020-03-30 20:01:40.0 +0200 @@ -1,8 +1,8 @@ Source: clips Section: interpreters Priority: optional -Maintainer: Javier Fernández-Sanguino Peña -Build-Depends: libncurses-dev, debhelper (>= 10~), pdf2htmlex, sharutils +Maintainer: Javier Fernández-Sanguino Peña +Build-Depends: libncurses-dev, debhelper (>= 10~), sharutils Standards-Version: 4.1.1 Homepage: http://www.clipsrules.net/ diff -Nru clips-6.30/debian/patches/clips_docs.diff clips-6.30/debian/patches/clips_docs.diff --- clips-6.30/debian/patches/clips_docs.diff 2017-10-17 00:34:21.0 +0200 +++ clips-6.30/debian/patches/clips_docs.diff 2020-03-30 20:51:48.0 +0200 @@ -27,7 +27,7 @@ +ENCODED_DOCS = $(PDF_DOCS:.pdf=.pdf.uu) +HTML_DOCS = $(PDF_DOCS:.pdf=.html) + -+all: $(PDF_DOCS) $(HTML_DOCS) ++all: $(PDF_DOCS) +all-encoded: $(ENCODED_DOCS) + +# Rule to update the documentation
Bug#966982: Uploading disabling that test to DELAYED/2
On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > Hi, > > Since nobody seem to care about this, I've uploaded disabling that > failing test to DELAYED/2. Indeed, to me, it looked like a broken test, > rather than a broken package. Otherwise, a long list of reverse > dependency will be removed from testing in 8 days. > > Debdiff of the change attached. Let me know if you would like me to > cancel the upload. > > Cheers, > > Thomas Goirand (zigo) Thanks for this Thomas but I actually have a package up for RFS to address this issue. I must admit I removed all tests during build. Because of the same reason. same testsuite is being run as an autopkgtest which succeeds. Previous there has also been some issues with these tests bug: [761325] I intend to reopen this bug. Can I persuade you to review and upload my own package instead of doing an NMU? bug: [965370] package in mentors [3] Thanks, H??vard [761325] https://bugs.debian.org/761325 [965370] https://bugs.debian.org/965370 [3] https://mentors.debian.net/package/wand/
Bug#966982: Uploading disabling that test to DELAYED/2
tir. 8. sep. 2020 kl. 14:29 skrev Thomas Goirand : > > On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: > > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > >> Hi, > >> > >> Since nobody seem to care about this, I've uploaded disabling that > >> failing test to DELAYED/2. Indeed, to me, it looked like a broken test, > >> rather than a broken package. Otherwise, a long list of reverse > >> dependency will be removed from testing in 8 days. > >> > >> Debdiff of the change attached. Let me know if you would like me to > >> cancel the upload. > >> > >> Cheers, > >> > >> Thomas Goirand (zigo) > > > > Thanks for this Thomas but I actually have a package up for RFS to > > address this issue. > > I must admit I removed all tests during build. Because of the same > > reason. same testsuite is being run as an autopkgtest which succeeds. > > Previous there has also been some issues with these tests bug: [761325] > > I intend to reopen this bug. > > > > Can I persuade you to review and upload my own package instead of doing > > an NMU? bug: [965370] package in mentors [3] > > > > Thanks, > > H??vard > > > > [761325] https://bugs.debian.org/761325 > > [965370] https://bugs.debian.org/965370 > > [3] https://mentors.debian.net/package/wand/ > > > > Hi Håvard, > Hi Thomas, > I'm very much surprised by this. Why didn't you write in the bug report > then, saying you've addressed the issue and was searching for a sponsor? I guess the reason for that is my workflow, I work from a forked repo and don't push it to the official until it has been released into Debian. I will change this from now on, so the BTS can track when I close a bug in salsa, and make it easier to collaborate with others. > I had the impression that nobody cared, you know... And you can't expect > everyone to closely monitor mentors. I don't expect it, but for me, and many others, it's the only way to get a sponsor. There is a pane in the package tracker page, that informs about the RFS. > > I do not agree that removing all tests is the solution, when only a > single one fails. I would happily sponsor your upload, but *not* if it's > removing all tests. I do agree with you that disabling all the tests isn't the best option, but keep in mind that I enabled the testsuite with the last release, and it didn't last much more than two months before a test failed, because of the test, not the package. The testsuite had been disabled for four years before that. The autopkgtest also uses the same testsuite, which strangely enough succeeds. If my reasoning isn't enough, I will comply and change the package to only disable that one test. > > Cheers, > > Thomas Goirand (zigo) Regards, Håvard
Bug#966982: Uploading disabling that test to DELAYED/2
On Tue, 8 Sep 2020 16:27:20 +0200 Thomas Goirand wrote: > On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: > > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > >> Hi, > >> > >> Since nobody seem to care about this, I've uploaded disabling that > >> failing test to DELAYED/2. Indeed, to me, it looked like a broken test, > >> rather than a broken package. Otherwise, a long list of reverse > >> dependency will be removed from testing in 8 days. > >> > >> Debdiff of the change attached. Let me know if you would like me to > >> cancel the upload. > >> > >> Cheers, > >> > >> Thomas Goirand (zigo) > > > > Thanks for this Thomas but I actually have a package up for RFS to > > address this issue. > > I must admit I removed all tests during build. Because of the same > > reason. same testsuite is being run as an autopkgtest which succeeds. > > Previous there has also been some issues with these tests bug: [761325] > > I intend to reopen this bug. > > > > Can I persuade you to review and upload my own package instead of doing > > an NMU? bug: [965370] package in mentors [3] > > > > Thanks, > > H??vard > > > > [761325] https://bugs.debian.org/761325 > > [965370] https://bugs.debian.org/965370 > > [3] https://mentors.debian.net/package/wand/ > > > > Hi Håvard, > > I'm very much surprised by this. Why didn't you write in the bug report > then, saying you've addressed the issue and was searching for a sponsor? > I had the impression that nobody cared, you know... And you can't expect > everyone to closely monitor mentors. > > I do not agree that removing all tests is the solution, when only a > single one fails. I would happily sponsor your upload, but *not* if it's > removing all tests. > > Cheers, > > Thomas Goirand (zigo) > > Hi Thomas, I wrote a reply to this email without CC'ing you, not sure if you got it. I did the change that you asked for and pushed it to salsa, I did NOT update the package in mentors. I also didn't use your patch, I excluded the test with pybuild in debian/rules. I'd be happy if you still wish to sponsor this. Git repository: g...@salsa.debian.org:debian/wand.git or https://salsa.debian.org/debian/wand.git Regards, Håvard
Bug#955125: marked as pending in subliminal
Control: tag -1 pending Hello, Bug #955125 in subliminal 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/subliminal/-/commit/e1aa2b272e05d07eaffdf65074f47f66e06b0839 d/patches: Update 0001-Examples-directory.patch Closes: #955125 (this message was generated automatically) -- Greetings https://bugs.debian.org/955125
Bug#961338: marked as pending in subliminal
Control: tag -1 pending Hello, Bug #961338 in subliminal 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/subliminal/-/commit/36ce7176e412170da8d44c37679096861d18a20b New upstream version and rebase patches Closes: #961338 (this message was generated automatically) -- Greetings https://bugs.debian.org/961338
Bug#952306: marked as pending in freelan
Control: tag -1 pending Hello, Bug #952306 in freelan 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/debian/freelan/-/commit/b627b089cbb21c904870ca046b009ac0c2d28105 Add 0006-Fix-build-outside-git.patch closes: #952306 (this message was generated automatically) -- Greetings https://bugs.debian.org/952306
Bug#950210: marked as pending in python-opcua
Control: tag -1 pending Hello, Bug #950210 in python-opcua 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/python-opcua/-/commit/d767fcf668de94126e5e5fa8aab9ddaf6caa42ba Add 0004-Fix-comparison-with-literal.patch closes: #950210 (this message was generated automatically) -- Greetings https://bugs.debian.org/950210
Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept
According to [1] and [2] this issue was fixed in package wsgi-intercept version 1.9.0 Though they write that the change was indeed in the httplib2 package. I have not tested the new release of wsgi-intercept myself. Håvard [1] https://github.com/cdent/wsgi-intercept/issues/57 [2] https://github.com/cdent/wsgi-intercept/pull/58
Bug#950038: Looks like a bug in httplib2 rather than on wsgi-intercept
Since you marked it as found after my reply, does it mean that you want it to be fixed in this (python-httplib2) package? How can it be found in a python2 package when python-wsgi-intercept only builds for python3? Thanks, Håvard
Bug#947031: python-libarchive-c: diff for NMU version 2.9-0.1
Control: tags 947031 + pending
Dear maintainer,
I've prepared an NMU for python-libarchive-c (versioned 2.9-0.1)
The change can be smaller if you would like to cherry-pick the upstream
commit, as the patch from the bug submitter.
I also took the liberty to update Standards-Version to current 4.5.0 and
change a folder in autopkgtest as lintian suggested.
I have run autopkgtest against diffoscope to verify that it's tests
still passes.
Regards,
Håvard
diff -Nru python-libarchive-c-2.8/debian/changelog
python-libarchive-c-2.9/debian/changelog
--- python-libarchive-c-2.8/debian/changelog2019-10-08 02:24:30.0
+0200
+++ python-libarchive-c-2.9/debian/changelog2020-02-17 17:17:23.0
+0100
@@ -1,3 +1,13 @@
+python-libarchive-c (2.9-0.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * New upstream version 2.9
+- Version is compatible with python3.8 closes: #947031
+ * Update Standards-Version to 4.5.0
+ * Change from ADTTMP to AUTOPKGTEST_TMP in d/tests/upstream-tests
+
+ -- Håvard Flaget Aasen Mon, 17 Feb 2020 17:17:23
+0100
+
python-libarchive-c (2.8-0.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru python-libarchive-c-2.8/debian/control
python-libarchive-c-2.9/debian/control
--- python-libarchive-c-2.8/debian/control 2019-10-08 02:23:51.0
+0200
+++ python-libarchive-c-2.9/debian/control 2020-02-17 17:09:27.0
+0100
@@ -9,7 +9,7 @@
python3-mock,
python3-pytest,
python3-setuptools
-Standards-Version: 4.3.0
+Standards-Version: 4.5.0
Rules-Requires-Root: no
Homepage: https://github.com/Changaco/python-libarchive-c
Vcs-Browser: https://salsa.debian.org/debian/python-libarchive-c
diff -Nru python-libarchive-c-2.8/debian/tests/upstream-tests
python-libarchive-c-2.9/debian/tests/upstream-tests
--- python-libarchive-c-2.8/debian/tests/upstream-tests 2019-10-08
02:24:24.0 +0200
+++ python-libarchive-c-2.9/debian/tests/upstream-tests 2020-02-17
16:44:57.0 +0100
@@ -2,13 +2,13 @@
set -e
-if ! [ -d "$ADTTMP" ]; then
- echo "ADTTMP not set." >&2
+if ! [ -d "$AUTOPKGTEST_TMP" ]; then
+ echo "AUTOPKGTEST_TMP not set." >&2
exit 1
fi
-cp -rv tests "$ADTTMP"
-cd "$ADTTMP"
+cp -rv tests "$AUTOPKGTEST_TMP"
+cd "$AUTOPKGTEST_TMP"
mkdir -v libarchive
touch README.rst
py.test-3 tests -vv -l -r a
diff -Nru python-libarchive-c-2.8/libarchive/entry.py
python-libarchive-c-2.9/libarchive/entry.py
--- python-libarchive-c-2.8/libarchive/entry.py 2018-06-10 15:01:15.0
+0200
+++ python-libarchive-c-2.9/libarchive/entry.py 2019-10-20 13:18:23.0
+0200
@@ -24,6 +24,8 @@
class ArchiveEntry(object):
+__slots__ = ('_archive_p', '_entry_p')
+
def __init__(self, archive_p, entry_p):
self._archive_p = archive_p
self._entry_p = entry_p
diff -Nru python-libarchive-c-2.8/libarchive/ffi.py
python-libarchive-c-2.9/libarchive/ffi.py
--- python-libarchive-c-2.8/libarchive/ffi.py 2018-06-10 15:27:14.0
+0200
+++ python-libarchive-c-2.9/libarchive/ffi.py 2019-10-20 13:18:23.0
+0200
@@ -162,18 +162,18 @@
try:
ffi('read_support_format_'+f_name, [c_archive_p], c_int, check_int)
except AttributeError: # pragma: no cover
-logger.warning('read format "%s" is not supported' % f_name)
+logger.info('read format "%s" is not supported' % f_name)
READ_FORMATS.remove(f_name)
READ_FILTERS = set((
'all', 'bzip2', 'compress', 'grzip', 'gzip', 'lrzip', 'lzip', 'lzma',
-'lzop', 'none', 'rpm', 'uu', 'xz', 'lz4'
+'lzop', 'none', 'rpm', 'uu', 'xz', 'lz4', 'zstd'
))
for f_name in list(READ_FILTERS):
try:
ffi('read_support_filter_'+f_name, [c_archive_p], c_int, check_int)
except AttributeError: # pragma: no cover
-logger.warning('read filter "%s" is not supported' % f_name)
+logger.info('read filter "%s" is not supported' % f_name)
READ_FILTERS.remove(f_name)
ffi('read_open',
@@ -224,18 +224,18 @@
try:
ffi('write_set_format_'+f_name, [c_archive_p], c_int, check_int)
except AttributeError: # pragma: no cover
-logger.warning('write format "%s" is not supported' % f_name)
+logger.info('write format "%s" is not supported' % f_name)
WRITE_FORMATS.remove(f_name)
WRITE_FILTERS = set((
'b64encode', 'bzip2', 'compress', 'grzip&#x
Bug#950207: python-crontab: diff for NMU version 1.9.3-3.1
Version: 1.9.3-3 Tags: patch pending Dear maintainer, I've prepared an NMU for python-crontab (versioned as 1.9.3-3.1) and uploaded it to DELAYED/XX. Please feel free to tell me if I should delay it longer. Regards. Håvard diff -Nru python-crontab-1.9.3/debian/changelog python-crontab-1.9.3/debian/changelog --- python-crontab-1.9.3/debian/changelog 2019-07-22 01:34:59.0 +0200 +++ python-crontab-1.9.3/debian/changelog 2020-02-21 09:05:51.0 +0100 @@ -1,3 +1,12 @@ +python-crontab (1.9.3-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Remove python as dependency from autopkgtest. closes: #937670, #950207 + * Change from deprecated ADTTMP to AUTOPKGTEST_TMP in autopkgtest. + * Remove ancient X-python-version field in d/control + + -- Håvard Flaget Aasen Fri, 21 Feb 2020 09:05:51 +0100 + python-crontab (1.9.3-3) unstable; urgency=medium * Non-maintainer upload. diff -Nru python-crontab-1.9.3/debian/control python-crontab-1.9.3/debian/control --- python-crontab-1.9.3/debian/control 2019-07-22 01:34:59.0 +0200 +++ python-crontab-1.9.3/debian/control 2020-02-21 08:58:08.0 +0100 @@ -14,8 +14,6 @@ Homepage: https://launchpad.net/python-crontab Vcs-Browser: https://github.com/jmetzmeier/python-crontab-debian Vcs-Git: https://github.com/jmetzmeier/python-crontab-debian.git -X-Python3-Version: >= 3.3 -X-Python-Version: >= 2.7 Package: python3-crontab Architecture: all diff -Nru python-crontab-1.9.3/debian/tests/control python-crontab-1.9.3/debian/tests/control --- python-crontab-1.9.3/debian/tests/control 2019-07-22 01:34:59.0 +0200 +++ python-crontab-1.9.3/debian/tests/control 2020-02-21 08:53:17.0 +0100 @@ -1,3 +1,3 @@ Tests: python3-crontab -Depends: python3-crontab, python, python3-pytest, python3-all +Depends: python3-crontab, python3-pytest, python3-all Restrictions: allow-stderr diff -Nru python-crontab-1.9.3/debian/tests/python3-crontab python-crontab-1.9.3/debian/tests/python3-crontab --- python-crontab-1.9.3/debian/tests/python3-crontab 2019-07-22 01:34:59.0 +0200 +++ python-crontab-1.9.3/debian/tests/python3-crontab 2020-02-21 09:02:32.0 +0100 @@ -1,7 +1,7 @@ #!/bin/sh set -e -u -cp -a tests/ "$ADTTMP" -cd "$ADTTMP/tests/" +cp -a tests/ "$AUTOPKGTEST_TMP" +cd "$AUTOPKGTEST_TMP/tests/" for py in $(py3versions -i); do LC_ALL=C.UTF-8 "$py" -m pytest done
Bug#961509: libxine2-bin: missing Breaks+Replaces: libxine2-doc (<< 1.2.10)
I intend to fix this bug, but I hope it can wait until I have sorted out the build on hurd-i386 as well. Regards, Håvard
