Package: pmount
Version: 0.9.99-alpha-1.1
Severity: wishlist
Currently, pmount has only support for LUKS and LUKS2. However, for the
sake of file exchange with windows, it would be nice to enable bitlocker
devices too.
This should be strait forward as cryptsetup already supports bitlocker.
The de
Dear Dmitry,
On Sun, 28 Aug 2022 21:44:23 +0300 Dmitry Shachnev
wrote:
Source: pysph
Version: 1.0~b1-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintain
Hi all,
On Fri, Aug 12, 2022 at 4:51 PM David Gobbi wrote:
>
> I've created a GDCM pull request where the necessary changes can be
> discussed. Lots of work remains to be done.
>
> https://github.com/malaterre/GDCM/pull/145
Thanks a *lot* David !
So the code has been merged upstream. I am pla
Hi Simon
On 2022-08-29 08:09:59 +0200, Simon Josefsson wrote:
> I could upload a real version too, maybe that is faster? Can do today unless
> someone objects.
The rebuilds were scheduled yesterday. See
https://buildd.debian.org/status/package.php?p=libidn2
Cheers
>
> /Simon
>
> > 28 aug. 2
This may be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787758
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: eribe...@debian.org
Hi,
The last upload_date that I can see from `bapase' seems to be 17th of August.
Same case while checking `date' from `upload_history'.
Could you consider checking what might be wrong?
Best,
Nilesh
On Aug 28, 2022 at 4:29:03 AM, Luca Falavigna wrote:
> Control: tags 1017132 + patch
> Control: tags 1017132 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for opentracing-cpp (versioned as 1.6.0-2.1) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it lo
Dear maintainer
Only a careful question:
Is there a chance to bring this package back to testing?
I need this package to maintain my YubiKey.
Thank you for the support
Bernhard
I installed dracut, and ran 'sudo dracut -f' more than twice, with
reboots, but it didn't fixed the issue. It remains the same.
(I sent this mail over 2 weeks ago to your personal email by mistake,
I'm sorry).
El 17/8/22 a las 16:24, Michael Biebl escribió:
Can you try dracut as your ini
Source: adduser
Version: 3.128
Severity: normal
symptoms: piuparts run fails with:
0m17.8s ERROR: WARN: Broken symlinks:
/usr/share/man/da/man8/addgroup.8.gz -> adduser.8.gz (adduser)
/usr/share/man/da/man8/delgroup.8.gz -> deluser.8.gz (adduser)
/usr/share/man/de/man8/addgroup.8.gz ->
Package: ntp
Version: 1:4.2.8p12+dfsg-4
Severity: minor
Upon upgrading an LXC to Debian 10.12, the ntp package was left
half-configured because the service would not start. Output was:
systemd[1]: Starting Network Time Service...
syste
[Jeff Epler]
> Is there a specific sender address that it will suffice to whitelist, or
> does the list need to permit mail from any address, regardless of
> subscription status?
Not really, as any user is expected to be able reach the maintainer
using that address, and such sender can come from a
On Fri, Aug 19, 2022 at 7:51 PM Borden wrote:
> The file /usr/share/doc/certbot/README.rst.gz provides a generic overview of
> certbot and advice to refer to the official documentation at
> https://certbot.eff.org/instructions?ws=apache&os=debiantesting . However,
> will be confusing for new us
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org,
python3-report...@packages.debian.org
Debian FTP Master(s) and Reportbug Maintainers,
Currently, python3-reportbug is Priority: standard.
It has only
reassign -1 src:abinit 9.6.2-1
On 8/29/22 00:51, Adrian Bunk wrote:
Usually that's a strong indication about ABI breakage in a library.
I know nothing about Fortran ABI rules, but nf90_def_var_oneDim()
gaining 3 (optional) parameters in 4.6.0 is suspiciously close
to #3 in the backtrace.
>
Pl
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, pyth...@packages.debian.org
Debian FTP Master(s) and Matthias,
Currently, python3 is Priority: optional.
The following Buster packages have Priority: s
Source: pygame
Version: 2.1.2+dfsg-3
Severity: normal
Tags: ftbfs, patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear Maintainer,
Pygame has been failing on riscv64 after updated to 2.1.2 [1] because of
test_src_alpha_sdl2_blitter [2].
I
I think this extension may be obsolete since GNOME Shell 43 now has a
sound device chooser built into the new system status menu.
Thank you,
Jeremy Bicha
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, p...@packages.debian.org
Debian FTP Master(s) and Niko,
Currently, perl-modules-5.34 and perl-modules-5.36 are libs/standard.
However, Debian Policy 2.
Hi,
On 8/28/22 11:18, Sebastian Ramacher wrote:
I'd like to do a transition of libzim 7->8. I've done local rebuilds
of all the reverse dependencies, python-libzim needs a patch (ready in
experimental), and all the rest (zim-tools, libkiwix, kiwix-tools, kiwix)
will need binNMUs.
Please go ahe
Package: libgtkhex-4-1
Version: 43~alpha-1
Severity: grave
Justification: renders package unusable
Hey.
When trying to upgrade:
Unpacking libgtkhex-4-1:amd64 (43~alpha-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libgtkhex-4-1_43~alpha-1_amd64.deb (--unpack):
trying to overwri
Fix proposed as a salsa MR at
https://salsa.debian.org/php-team/pear/php-mail/-/merge_requests/1
--
Athos Ribeiro
On Sun, 28 Aug 2022 at 19:27, Tobias Frost wrote:
> So, even with the switch, the build system needs it at least at
> configure time, which is the reason why it failed at the second time.
> (make distclean was the command that failed; as the removal of lua
> was only directly before the build, it
Debian FTP Master(s) and Debian DNS Team,
"Accepted bind9 1:9.18.6-1 (source amd64 all) into unstable, unstable":
https://tracker.debian.org/news/1357381
apparently reverted the Priority for bind9-libs from "optional" back
to "standard".
Please change the Priority for bind9-libs from "sta
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: debian-b...@lists.debian.org, debian-ker...@lists.debian.org
Debian FTP Master(s),
nfs-utils Commit aba2cc13 [1] (Jan 19, 2022) by Ben Hutchings says:
d/control: Reduce priority of
On 21/08/2022 07.40, Paul Gevers wrote:
Can you ignore the autopkgtest "regression" on ppc64el and let the CVE
fixes into testing?
Linux 5.19 seems to take longer getting into sid
our hosts are running stable and we're using the lxc backend of
autopkgtest. So you'll need to wait until a fix
Package: vmpk
Version: 0.8.7-1
Severity: normal
X-Debbugs-Cc: a...@transient.nz
Dear Maintainer,
if I select a "Program" such as "Rhodes Piano", this selection is displayed
after restart but "Acoustic Grand Piano" is played. Program "Rhodes Piano" must
be selected again after restart for this opt
On domingo, 28 de agosto de 2022 23:52:09 (CEST) Ash Joubert wrote:
> I can confirm that, after upgrading libdrumstick packages to 2.7.1-1,
> configuring a FluidSynth MIDI connection restores functionality. The
> missing step was to configure a sound font: the default "default.sf2"
> does not exist
Control: reassign -1 src:netcdf-fortran 4.6.0+ds-1
Control: affects -1 src:abinit
On Mon, Aug 01, 2022 at 10:16:38PM +0200, Sebastiaan Couwenberg wrote:
> Installing the dbgsym packages makes the backtrace a little more
> informative:
>
> Backtrace for this error:
> #0 0x7f889dd4b93f in ???
>
Source: igv
Version: 2.13.0+dfsg-1
Hello, as spot by Ubuntu builders [1] with a more restricted internet access,
your package is trying to call some external websites during testing.
Please use autopkgtests if you really want such tests to run.
[1]
https://launchpadlibrarian.net/619496372/buil
Pedro,
thank you for your detailed explanation.
I can confirm that, after upgrading libdrumstick packages to 2.7.1-1,
configuring a FluidSynth MIDI connection restores functionality. The
missing step was to configure a sound font: the default "default.sf2"
does not exist. You might consider e
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: spnavcfg
Version : 1.0
* URL : https://github.com/FreeSpacenav/spnavcfg
* License : GPL
Description : GUI to configure 3Dconnexion devices
T
On Sun, 28 Aug 2022 17:56:04 +0200 Philippe SWARTVAGHER
wrote:
Changes since the last upload:
libcdio-paranoia (10.2+2.0.1-1) unstable; urgency=medium
.
* New upstream release
* New maintainer (Closes: #881910)
* Add Vcs-* fields in d/control
* Bump Standards-Version to 4.6
Package: libsofia-sip-ua0
Version: 1.12.11+20110422.1+1e14eea~dfsg-3
Severity: normal
Bug #871435 was not fixed completely in 1.12.11+20110422.1+1e14eea~dfsg-2
as there is still an instance of version dependent methods
as found by grepping for '(SSL|TLS).*_method'
libsofia-sip-ua/stun/stun.c:1356
On Tue, 16 Aug 2022 at 12:51, Simon McVittie wrote:
> debcrossgen puts c_args, cpp_args, c_link_args and cpp_link_args in the
> [properties] section of the cross-file that it generates, but recent
> versions of Meson want this to be in the [built-in options] section
> instead.
We have been movin
tags 1018370 upstream
forwarded 1018370 https://github.com/gnome-keysign/gnome-keysign/issues/115
thanks
Control: tag -1 pending patch
Hi Matthias,
On Sun, 07 Aug 2022 10:32:36 +0200 Paul Gevers wrote:
If I didn't make a mistake, pypy-packaging is keeping pypy in the key
package set because it Build-Depends on it. Again, if I didn't make a
mistake, there are no reverse Build-Depends or Depends an
Package: libmsgpack-dev
Version: 4.0.0-1
Severity: normal
Many packages currently Build-Depend on libmsgpack-dev when they really
need libmsgpack-cxx-dev. This bug exists to collect the blockers for
removing the "Depends: libmsgpack-cxx-dev".
-- System Information:
Debian Release: bookworm/sid
Hello,
On Sat 27 Aug 2022 at 03:15PM -04, Douglas Katzman wrote:
>
> I suspect that the heap exhaustion is corrected for this release.
You have in mind an upcoming 2.2.8 release, right? 2.2.7 is still
showing the test failure.
> Also I think this particular GC invariant failure is not of the u
Sadly this patch cannot be applied to node-terser without regression
Le 28 août 2022 19:29:33 GMT+02:00, Mohd Bilal a écrit :
>Hi Yadd :)
>
>On Thu, 25 Aug 2022 10:58:21 +0200 Yadd wrote:
>> ruby-terser uses a patched terser.js (see
>> https://github.com/ahorek/terser-ruby/blob/master/patches/t
Hi,
Am 28.08.22 um 17:46 schrieb Rene Engelhard:
Hi,
Am 31.07.22 um 16:44 schrieb Rene Engelhard:
This is now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016420
(where the upstream bug which that one is marked as forwarded to has
also the reasoning why support for < 3.16 was dropped wh
On Sun, Jun 05, 2022 at 08:43:45AM -0400, James McCoy wrote:
> Remaining dependencies that need to be packaged:
>
> glutin → winit → smithay-client-toolkit → calloop
> ⤷ glutin_glx_sys
>
> Hopefully will be able to make it through this in the next few weeks
> (based on NEW speed).
All depe
Source: abseil
Version: 0~20220623.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=abseil&arch=ppc64el&ver=0%7E20220623.0-1&stamp=1661712847&raw=0
151
Control: tags -1 - moreinfo
Hi Jonathan,
On Sun, Aug 28, 2022 at 05:04:47PM +0100, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed moreinfo
>
> On Sat, Jun 25, 2022 at 10:51:24AM +0200, Salvatore Bonaccorso wrote:
> > In the same upload a couple of other bugfixes were done which seem
> > s
Source: libgovirt
Version: 0.3.8-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: evolution-3.46
Tags: bookworm sid ftbfrs upstream
Forwarded: https://gitlab.gnome.org/GNOME/libgovirt/-/issues/6
libgovirt 0.3.8 fails to build with librest 0.9.1 currently in Debian
Source: zope.security
Version: 5.3-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that y
Source: yt
Version: 4.0.5-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your packa
Source: youtube-dl
Version: 2021.12.17-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means th
Source: yotta
Version: 0.20.5-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your p
Source: yapf
Version: 0.32.0-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your pa
Source: yanc
Version: 0.3.3-4
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your pac
Source: yamllint
Version: 1.26.3-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that you
Source: xraylarch
Version: 0.9.58+ds1-4
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means tha
Source: xlwt
Version: 1.3.0-4
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your pac
Source: xhtml2pdf
Version: 0.2.5-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that you
Source: x2gobroker
Version: 0.0.4.3-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: wsgiproxy2
Version: 0.5.1-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that yo
Source: whatmaps
Version: 0.0.12-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that you
Source: websockify
Version: 0.10.0+dfsg1-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means
Control: tags -1 pending
This is already fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
This is already fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Control: tags -1 pending
This is already fixed in git.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Source: webassets
Version: 3:0.12.1-1.1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means tha
Source: voltron
Version: 0.1.7+git20200109-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it mean
Source: voluptuous
Version: 0.12.2-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that y
Source: vitables
Version: 3.0.2-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: valinor
Version: 1.1.4-7
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: uncertainties
Version: 3.1.6-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: trash-cli
Version: 0.17.1.14-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: umap-learn
Version: 0.4.5+dfsg-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means th
Source: transforms3d
Version: 0.3.1+ds-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means th
Source: traittypes
Version: 0.2.1-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that yo
Source: tpot
Version: 0.11.7+dfsg-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that yo
Source: tldp
Version: 0.7.13-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your pa
Source: tldextract
Version: 3.1.2-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that yo
Source: theano
Version: 1.0.5+dfsg-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that y
Source: testresources
Version: 2.0.1-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: syslog-ng
Version: 3.35.1-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that yo
Source: swiglpk
Version: 4.65.1-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: swift
Version: 2.29.1-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your p
Source: swift-bench
Version: 1.2.0-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that y
Source: svtplay-dl
Version: 3.0-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: spyder-unittest
Version: 0.5.0-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means th
Source: sphinx-celery
Version: 2.0.0-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: sosreport
Version: 4.0-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: sparql-wrapper-python
Version: 1.8.5-2
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it me
Source: skimage
Version: 0.19.3-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: seqdiag
Version: 2.0.0+dfsg-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: scoary
Version: 1.6.16-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your
Source: scikit-learn
Version: 1.1.2+dfsg-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means
Source: rows
Version: 0.4.1-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your pac
Source: routes
Version: 2.5.1-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your p
Source: ros-vcstools
Version: 0.1.42-4
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: ros-laser-geometry
Version: 1.6.7-3
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means
Source: ros-kdl-parser
Version: 1.14.2-1
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means th
Source: ros-interactive-markers
Version: 1.12.0-8
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it
Source: ros-image-pipeline
Version: 1.16.0-5
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it mean
Source: ros-image-common
Version: 1.12.0-11
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means
Source: ros-geometry
Version: 1.13.2-8
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
Source: ros-geometry2
Version: 0.7.5-9
User: python-modules-t...@lists.alioth.debian.org
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that
1 - 100 of 520 matches
Mail list logo
