Bug#991036: Bug#993849: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?
Le mercredi 09 février 2022 à 09:32 +0100, Guido Günther a écrit : > Hi, Hello Adrian, Guido, > On Wed, Feb 09, 2022 at 06:27:50AM +0200, Adrian Bunk wrote: > > Control: severity -1 serious > > > > libhandy is about to be removed from bookworm due to this, > > gnome-authenticator and gnome-metronome need to be updated. > > Just to confirm: I think removal is fine, this API version is > unmaintained upstream and libhandy-1 and libadwaita are in Debian. > Cheers, Regarding gnome-authenticator (which I maintain through DPT), the application has been rewritten in Rust and it now uses GTK4 and libadwaita. All the dependencies (rust crates) of the updated gnome-authenticator are unfortunately not yet all packaged and available in the archive. I am working together with the Rust team to get those dependencies available in the archive, although since there are many new packages, those need a trip through NEW which adds some overall delay regarding their availability. This means that most likely gnome-authenticator will get removed before the new version could be uploaded. I certainly aim for the updated gnome-authenticator to be available for the bookworm release. > -- Guido > Henry-Nicolas signature.asc Description: This is a digitally signed message part
Bug#1003756: squeekboard, build-depends unsatisfiable
X-Debbugs-CC: arnaud.ferra...@gmail.com > squeekboard's build-dependencies are unsatisfiable in unstable due to > the > new version of the rust gtk stack. I tried relaxing the depenencies > (on both the Debian side and cargo side), but it failed with the > following Thanks for the bug report Peter. The MR at [0] would help address this issue, although it is apparently not ready to be merged (see the comment from Arnaud). [0] https://salsa.debian.org/DebianOnMobile-team/squeekboard/-/merge_requests/4 Arnaud, should we maybe involve upstream (if not done already) if we can't easily fix the error you reported in that salsa MR above? Regards, Henry-Nicolas Tourneur signature.asc Description: This is a digitally signed message part
Bug#1002398: Spyne: fix FTBFS
Tags: + patch thanks Dear, Please find in attachment a patch to fix this. I also opened an MR in salsa [1] as well as upstream [2]. The rationale for this FTBFS is as follow: Since Python 3.3, using or importing the ABCs from 'collections' instead of using 'collections.abc' is deprecated. In Python 3.10, it is no longer supported. Best regards, Henry-Nicolas Tourneur [1] https://salsa.debian.org/python-team/packages/spyne/-/merge_requests/1 [2] https://github.com/arskom/spyne/pull/677 diff --git a/debian/changelog b/debian/changelog index 6ceb4cc..81f2844 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,6 +2,10 @@ spyne (2.13.16-3) UNRELEASED; urgency=medium * Scan GitHub tags instead of releases + [ Henry-Nicolas Tourneur ] + * d/patches: add 000_fix_collections.patch, fixes an FTBFS (Closes: +#1002398) + -- Bastian Germann Wed, 10 Nov 2021 15:57:11 +0100 spyne (2.13.16-2) unstable; urgency=medium diff --git a/debian/patches/000_fix_collections.patch b/debian/patches/000_fix_collections.patch new file mode 100644 index 000..500dbff --- /dev/null +++ b/debian/patches/000_fix_collections.patch @@ -0,0 +1,27 @@ +Author: Henry-Nicolas Tourneur +Forwarded: https://github.com/arskom/spyne/pull/677 +Description: Since Python 3.3, using or importing the ABCs from 'collections' + instead of using 'collections.abc' is deprecated. + In Python 3.10, it is no longer supported. +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/spyne/util/etreeconv.py b/spyne/util/etreeconv.py +@@ -48,7 +48,7 @@ def root_dict_to_etree(d): + + if isinstance(val, dict) or isinstance(val, odict): + dict_to_etree(val, retval) +-elif not isinstance(val, collections.Sized) or isinstance(val, six.string_types): ++elif not isinstance(val, collections.abc.Sized) or isinstance(val, six.string_types): + retval.text=str(val) + else: + for a in val: +@@ -74,7 +74,7 @@ def dict_to_etree(d, parent): + child = etree.SubElement(parent, k) + dict_to_etree(v, child) + +-elif not isinstance(v, collections.Sized): ++elif not isinstance(v, collections.abc.Sized): + etree.SubElement(parent, k).text = str(v) + + elif len(v) == 0: diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..58f3ecf --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +000_fix_collections.patch signature.asc Description: This is a digitally signed message part
Bug#1002625: marked as pending in wlr-randr
Control: tag -1 pending Hello, Bug #1002625 in wlr-randr 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/DebianOnMobile-team/wlr-randr/-/commit/90806f87e787e6fff46cebaba6ab2cf9d9fd719e d/tests: use pixman renderer and handle gracefully absence of xwayland (Closes: #1002625) (this message was generated automatically) -- Greetings https://bugs.debian.org/1002625
Bug#1000942: [Pkg-rust-maintainers] Bug#1000942: rust-zbus-macros - autopkgtest failure, makes reverse dependencies FTBFS.
Package: rust-zbus-macros Version: 1.0.0-3 Severity: serious x-debbugs-cc: deb...@nilux.be The rust-zbus-macros autopkgtest is failing: error[E0432]: unresolved import `zbus` --> /tmp/tmp.2o6G5gYnNc/registry/zbus-1.0.0/src/object_server.rs:54:1 | 54 | #[dbus_interface(name = "org.freedesktop.DBus.Introspectable")] | ^^^ no `Type` in the root | = note: this error originates in the attribute macro `dbus_interface` (in Nightly builds, run with -Z macro-backtrace for more info) I also did test-builds of the reverse dependencies rust-zbus and rust-libslirp (note: I had to manually build mio-0.6 to test rust-libslirp as it is currently sitting in new) and they failed with similar errors, so this is not just an autopkgtest issue. I don't know for certain but I assume that just relaxing the dependency was not enough to make it work correctly with the new version of rust-proc-macro-crate. I also tried doing a test rebuild of rust-libslirp (which afaict is the only binary crate that depends on I took a look in the upstream VCS and found a patch for rust-proc-macro-crate 1 and tried applying it, unfortunately it dependeded on a bunch of other upstream commits. Updating to the latest stable upstream helped a bit with getting the patches to apply and I was able to get a succesful build of rust-zbus-macros 1.9.2 with a pile of upstream patches. Unfortunately when running it's autopkgtests I ran into another issue. It seems that rust-zbus has a strictly versioned dependency on the identical version rust-zbus-macros and rust-zbus 1.9.2 brings several new dependencies. dpkg-checkbuilddeps: error: Unmet build dependencies: librust-async-io-1+default-dev (>= 1.3.1-~~) librust-nb-connect-1+default-dev (>= 1.0.2-~~) librust-polling-2+default-dev (>= 2.0.2-~~) That is pretty much as far as i'm prepared to go. I have pushed my attempts to https://salsa.debian.org/rust-team/debcargo-conf/-/tree/zbus-1.9.2 if anyone else wants to pick them up. Hello Peter, Sorry about that and thank you for the bug report. I was actually working yesterday on updating zbus/zbus-macros and its dependencies to the latest upstream release. So far, I am counting 7 new crates that will need to go through NEW and an additional eight one which is flagged as deprecated upstream (nb-connect). I am trying to assess how to best approach that one (if possible, I am busy patching it out based on an upstream commit). The other option would be to prepare/upload a rust-proc-macro-crate-0.1 package and then revert the dependency in rust-zbus-macros. I may do that if noone comes up with a better solution. I would suggest we first try to get an updated zbus in the archive, which I'll be working on. If it get stuck for any reason, then the alternative solution you are proposing has the benefit of introducing fewer new packages (only one vs the 7 new zbus deps mentionned above). Best regards, Henry-Nicolas Tourneur
Bug#998576: marked as pending in squeekboard
Control: tag -1 pending Hello, Bug #998576 in squeekboard 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/DebianOnMobile-team/squeekboard/-/commit/6f7fa64c07f4b6ebd22deaf311e54b98d901a9ee d/patches: add fix_meson_ftbfs (Closes: #998576) (this message was generated automatically) -- Greetings https://bugs.debian.org/998576
Bug#999507: [Pkg-rust-maintainers] Bug#999507: Bug#999507: rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.
Le ven 12 nov 2021 à 10:18, Fabian Grünbichler a écrit : On November 12, 2021 6:38 am, Peter Green wrote: Package: rust-tokio-signal Version: 0.2.7-2 Severity: serious rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream seems to have abandoned the project, there was an alpha release supporting futures 0.2, but the code appears to have been removed from the tokio git repository. So I presume it is abandoned upstream. There are no reverse dependencies in testing, there is a single reverse dependency in unstable which is rc buggy and also appears to be abandoned upstream. If there are no objections in a few weeks, I intend to file a removal request. same here, tokio-signal is now tokio+signal ;) accordingly, it can be RMed with the rest of the legacy tokio 0.1 crates once tokio 1.0 has been uploaded I would not even wait for tokio 1.0 upload and request removal of tokio-signal could be done right away. As it stands, it is broken due to unsastifiable build dependencies and it has no reverse dependencies, as Peter explained. Fabian, I see no point in keeping tokio-signal in the archive in its current state and the package is going away anyway as you mentionned it being superseeded by tokio+signal. Do you see any reasons to keep it until tokio 1.0 upload? Regards, Henry-Nicolas
Bug#991036: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?
Le mardi 07 septembre 2021 à 10:07 +0100, Simon McVittie a écrit : > On Tue, 13 Jul 2021 at 13:36:17 +0300, Adrian Bunk wrote: > > A more recent version is already available in src:libhandy-1. > > > > Both versions will be in bullseye, but still shipping both in > > bookworm would feel wrong. > > I think you're right, but I think it might also be too soon for this > to > be considered RC, because progress cannot be made on its removal > until > some transitions have gone through. > > I've opened bugs for the four remaining reverse-dependencies: > > - #993849: gnome-authenticator > - #993850: gnome-calendar > - #993852: gnome-metronome > - #993853: kgx > > gnome-authenticator has a new upstream version 4.x that uses GTK4 and > libadwaita, but libadwaita is not yet stable and is in NEW (it might > be > possible to bundle a snapshot in gnome-authenticator). gnome- > authenticator 4 > itself is a rewrite from Python into Rust, so this is unlikely to be > quick > to update. (The Debian package is also mis-named, this is not an > official > GNOME application.) > Hello Simon, I am the maintainer of gnome-authenticator in the Python team, and indeed, its rewrite in Rust means it'll take time to update as there are many crate dependencies that needs to be available in the archive first (I am also working with the Rust team to progress this). Ideally, I'd preferr of course that the package remains available in booksworm and I'll be working toward that. Regards, Henry-Nicolas Tourneur signature.asc Description: This is a digitally signed message part
Bug#992576: marked as pending in mfgtools
Control: tag -1 pending Hello, Bug #992576 in mfgtools 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/DebianOnMobile-team/mfgtools/-/commit/08551c95667834f87ccc157f4ebd8f4ad0765da2 d/rules: fix FTBFS on armel/mipsel/m68k/powerpc/sh4 - must link with libatomic (Closes: #992576) (this message was generated automatically) -- Greetings https://bugs.debian.org/992576
Bug#981934: portfolio-filemanager: Package is unfit for release - should not be in unstable
Package: portfolio-filemanager Version: 0.9.8-1 Severity: serious Tags: upstream Justification: Policy 2.2.1 portfolio-filemanager is still a very new software that is not fit for release. Upstream agrees with this and is expecting the software to mature before it could be made part of a stable Debian release. It has been accidentaly uploaded to unstable instead of experimental. This RC bug is created to prevent its transition to testing. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages portfolio-filemanager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1 ii gir1.2-handy-1 1.0.3-1 ii python3 3.9.1-1 ii python3-gi 3.38.0-1+b2 portfolio-filemanager recommends no packages. portfolio-filemanager suggests no packages. -- no debconf information
Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1
X-Debbugs-CC: jbi...@debian.org,bi...@debian.org Adding the geary uploaders directly in CC since they might not have received emails from the BTS for this bug as the maintainer is set to Debian GNOME Maintainers. Best regards, -- Henry-Nicolas Tourneur mxid: @hntourne:matrix.nilux.be irc: hntourne on oftc
Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1
FYI, deleting the user's config under ~/.config, ~/.local/share and ~/.cache fixes the issue and geary starts successfully after that. Of course that is a disruptive operation (user config is gone, and what about pop accounts that cannot resync emails later on). I can probably reproduce the issue on another computer if anyone wants to troubleshoot this issue further. -- Henry-Nicolas Tourneur mxid: @hntourne:matrix.nilux.be irc: hntourne on oftc
Bug#978146: geary: Geary segfaults on startup after upgrade to 3.38.1-1
Package: geary Version: 3.38.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade on bullseye from 3.36 to 3.38 with apt * What exactly did you do (or not do) that was effective (or ineffective)? Upgrade on bullseye from 3.36 to 3.38 with apt * What was the outcome of this action? When starting geary, it segfaults as showned below. * What outcome did you expect instead? Geary to start normally and open the main window *** End of the template - remove these template lines *** *[wrn] 17:44:29.0960 geary:application-certificate-manager.vala:74: No GCR slot URIs found, GCR certificate pinning unavailable *[wrn] 17:44:30.0092 GLib-GObject:invalid (NULL) pointer instance ![crt] 17:44:30.0092 GLib-GObject:g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed *[wrn] 17:44:30.0092 GLib-GObject:invalid (NULL) pointer instance ![crt] 17:44:30.0092 GLib-GObject:g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed ![crt] 17:44:30.0092 geary:application_account_interface_get_account_contexts: assertion 'APPLICATION_IS_ACCOUNT_INTERFACE (self)' failed ![crt] 17:44:30.0092 [no domain]:gee_iterable_iterator: assertion 'self != NULL' failed ![crt] 17:44:30.0092 [no domain]:gee_iterator_next: assertion 'self != NULL' failed ![crt] 17:44:30.0093 geary:application_controller_register_window: assertion 'APPLICATION_IS_CONTROLLER (self)' failed ![crt] 17:44:30.0198 geary:application_account_interface_get_context_for_account: assertion 'APPLICATION_IS_ACCOUNT_INTERFACE (self)' failed ![crt] 17:44:30.0198 geary:application_account_interface_get_context_for_account: assertion 'APPLICATION_IS_ACCOUNT_INTERFACE (self)' failed ![crt] 17:44:30.0198 geary:application_account_interface_get_context_for_account: assertion 'APPLICATION_IS_ACCOUNT_INTERFACE (self)' failed Erreur de segmentation -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages geary depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1 ii gnome-keyring3.36.0-1 ii libc62.31-5 ii libcairo21.16.0-4 ii libenchant-2-2 2.2.12-1 ii libfolks25 0.14.0-1+b1 ii libgck-1-0 3.38.0-1 ii libgcr-base-3-1 3.38.0-1 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libgee-0.8-2 0.20.3-1 ii libglib2.0-0 2.66.4-1 ii libgmime-3.0-0 3.2.7-1 ii libgoa-1.0-0b3.38.0-1 ii libgsound0 1.0.2-4 ii libgspell-1-21.8.4-1 ii libgtk-3-0 3.24.24-1 ii libhandy-1-0 1.0.2-1+b1 ii libjavascriptcoregtk-4.0-18 2.30.4-1 ii libjson-glib-1.0-0 1.6.0-2 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpeas-1.0-01.28.0-2+b1 ii libsecret-1-00.20.4-1 ii libsoup2.4-1 2.72.0-2 ii libsqlite3-0 3.34.0-1 ii libunwind8 1.3.2-2 ii libwebkit2gtk-4.0-37 2.30.4-1 ii libxml2 2.9.10+dfsg-6.3+b1 ii libytnef01.9.3-2 geary recommends no packages. geary suggests no packages. -- no debconf information
Bug#951682:
Hello Ralf, Version 0.25 of this package depends just got it and it depends on librust- markup5ever-0.10+default-dev which is provided by librust-markup5ever-dev. I will close this bug accordingly. Best regards, -- Henry-Nicolas Tourneur mxid: @hntourne:matrix.nilux.be
Bug#961852: python-matrix-nio: autopkgtest failure: No module named 'matrix_nio'
Dear, Please find attached an updated patch which is cleaner than the first one. Best regards, Henry-Nicolas Tourneur Matrix id: @hntourne:matrix.nilux.be Le lun 8 juin 2020 à 12:34, Henry-Nicolas Tourneur a écrit : Dear Matrix-team maintainers, As discussed over the matrix room #debian-matrix:matrix.org, please find in attachment a patch to solve this bug. Basically, this happened because autodep8 tries to derive the Python module name from the package name. In this case, the module name is nio while autodep8 tries to import matrix_nio from the package name, which fails. The patch attached does the following: - Remove the autodep8 autopkgtest - Add a custom autopkgtest (debian/test/control and debian/test/pytest): This autopkgtest is actually using the upstream test cases (pytest-3 tests/), going further than a regular module import. - Adding a debian/salsa-ci.yml file so you can enable CI on your Salsa repo and use that file to validate autopkgtests works fine before uploading to main - Document the changes in debian/changelog Best regards, Henry-Nicolas Tourneur Matrix id: @hntourne:matrix.nilux.be diff --git a/debian/changelog b/debian/changelog index 04ff6e2..05483c4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -7,6 +7,9 @@ python-matrix-nio (0.12.0-1) unstable; urgency=medium * Update changelog entry for release 0.10.0-2 to mention changes to descriptions + [ Henry-Nicolas Tourneur ] + * Replace autodep8 autopkgtest with new autopkg test suite (Closes: #961852) + -- Jonas Smedegaard Sat, 30 May 2020 13:18:16 +0200 python-matrix-nio (0.11.2-2) unstable; urgency=medium diff --git a/debian/control b/debian/control index 51f2b56..de49591 100644 --- a/debian/control +++ b/debian/control @@ -40,7 +40,6 @@ Homepage: https://github.com/poljar/matrix-nio Vcs-Git: https://salsa.debian.org/matrix-team/python-matrix-nio.git Vcs-Browser: https://salsa.debian.org/matrix-team/python-matrix-nio Rules-Requires-Root: no -Testsuite: autopkgtest-pkg-python Package: python3-matrix-nio Architecture: all diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml new file mode 100644 index 000..a5957e7 --- /dev/null +++ b/debian/salsa-ci.yml @@ -0,0 +1,8 @@ +--- +include: + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml + +variables: + SALSA_CI_DISABLE_BLHC: 1 + SALSA_CI_DISABLE_BUILD_PACKAGE_ANY: 1 diff --git a/debian/tests/control b/debian/tests/control new file mode 100644 index 000..2f944a9 --- /dev/null +++ b/debian/tests/control @@ -0,0 +1,27 @@ +Test-Command: pytest-3 tests/ +Restrictions: allow-stderr +Depends: python3-aiofiles, + python3-aiohttp, + python3-aioresponses, + python3-all, + python3-atomicwrites, + python3-cachetools, + python3-fake-factory, + python3-h11, + python3-h2, + python3-hpack, + python3-hyperframe, + python3-hypothesis, + python3-jsonschema, + python3-logbook, + python3-mypy, + python3-mypy-extensions, + python3-olm, + python3-peewee, + python3-pip, + python3-pycryptodome, + python3-pytest, + python3-pytest-benchmark, + python3-pytest-cov, + python3-unpaddedbase64, + @
Bug#961852: python-matrix-nio: autopkgtest failure: No module named 'matrix_nio'
Dear Matrix-team maintainers, As discussed over the matrix room #debian-matrix:matrix.org, please find in attachment a patch to solve this bug. Basically, this happened because autodep8 tries to derive the Python module name from the package name. In this case, the module name is nio while autodep8 tries to import matrix_nio from the package name, which fails. The patch attached does the following: - Remove the autodep8 autopkgtest - Add a custom autopkgtest (debian/test/control and debian/test/pytest): This autopkgtest is actually using the upstream test cases (pytest-3 tests/), going further than a regular module import. - Adding a debian/salsa-ci.yml file so you can enable CI on your Salsa repo and use that file to validate autopkgtests works fine before uploading to main - Document the changes in debian/changelog Best regards, Henry-Nicolas Tourneur Matrix id: @hntourne:matrix.nilux.be diff --git a/debian/changelog b/debian/changelog index 04ff6e2..05483c4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -7,6 +7,9 @@ python-matrix-nio (0.12.0-1) unstable; urgency=medium * Update changelog entry for release 0.10.0-2 to mention changes to descriptions + [ Henry-Nicolas Tourneur ] + * Replace autodep8 autopkgtest with new autopkg test suite (Closes: #961852) + -- Jonas Smedegaard Sat, 30 May 2020 13:18:16 +0200 python-matrix-nio (0.11.2-2) unstable; urgency=medium diff --git a/debian/control b/debian/control index 51f2b56..de49591 100644 --- a/debian/control +++ b/debian/control @@ -40,7 +40,6 @@ Homepage: https://github.com/poljar/matrix-nio Vcs-Git: https://salsa.debian.org/matrix-team/python-matrix-nio.git Vcs-Browser: https://salsa.debian.org/matrix-team/python-matrix-nio Rules-Requires-Root: no -Testsuite: autopkgtest-pkg-python Package: python3-matrix-nio Architecture: all diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml new file mode 100644 index 000..a5957e7 --- /dev/null +++ b/debian/salsa-ci.yml @@ -0,0 +1,8 @@ +--- +include: + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml + +variables: + SALSA_CI_DISABLE_BLHC: 1 + SALSA_CI_DISABLE_BUILD_PACKAGE_ANY: 1 diff --git a/debian/tests/control b/debian/tests/control new file mode 100644 index 000..8d99d7a --- /dev/null +++ b/debian/tests/control @@ -0,0 +1,26 @@ +Tests: pytest +Restrictions: allow-stderr +Depends: python3-all, + python3-pytest, + python3-pip, + python3-pytest-cov, + python3-pytest-benchmark, + python3-hyperframe, + python3-hypothesis, + python3-hpack, + python3-mypy, + python3-mypy-extensions, + python3-aiohttp, + python3-aioresponses, + python3-olm, + python3-peewee, + python3-atomicwrites, + python3-cachetools, + python3-logbook, + python3-unpaddedbase64, + python3-pycryptodome, + python3-aiofiles, + python3-jsonschema, + python3-h2, + python3-h11, + @ diff --git a/debian/tests/pytest b/debian/tests/pytest new file mode 100644 index 000..85f10ae --- /dev/null +++ b/debian/tests/pytest @@ -0,0 +1,6 @@ +#!/bin/sh + +# Get from PyPi what is not packaged into Debian +pip3 install pytest-flake8 pytest-isort faker + +pytest-3 tests/
Bug#689533: exabgp: modifies conffiles (policy 10.7.3): /etc/exabgp/exabgp.env
Thanks a lot for the patch, I did add it to the next ExaBGP version. Kind regards, Henry-Nicolas Tourneur Le dimanche 04 novembre 2012 à 19:47 +, Federico Ceratto a écrit : Tag: patch Hello, A patch for this bug is attached. I moved the /etc/exabgp/exabgp.env file creation to ucf to allow exabgp to generate the file dynamically. Bye, -- Federico -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650856: Crash on restore GUI startup
Package: deja-dup Followup-For: Bug #650856 I did just check on a Wheezy installation and it's not crashing. I assume the best would be to have Pietro Battiston to test this again with an up to date system. Regards, -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages deja-dup depends on: ii dconf-gsettings-backend [gsettings-backend] 0.10.0-3 ii duplicity0.6.18-1 ii libatk1.0-0 2.2.0-2 ii libc62.13-27 ii libcairo-gobject21.10.2-7 ii libcairo21.10.2-7 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-0 2.30.2-6 ii libgnome-keyring03.2.2-2 ii libgtk-3-0 3.2.3-1 ii libnautilus-extension1a 3.2.1-3 ii libnotify4 0.7.5-1 ii libpango1.0-01.29.4-3+b1 Versions of packages deja-dup recommends: pn openssh-client [ssh-client] 1:5.9p1-4 pn python-boto none pn python-rackspace-cloudfiles none deja-dup suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
