Debian Package Tracker
Register | Log in
Subscribe

python-fuse

Python bindings for FUSE (Filesystems in USErspace) (Python 3 package)

Choose email to subscribe with

general
  • source: python-fuse (main)
  • version: 2:1.0.1-1
  • maintainer: Sebastien Delafond (DMD)
  • arch: any
  • std-ver: 4.5.1
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2:0.2.1-10
  • oldstable: 2:0.2.1-14
  • stable: 2:0.3.1-1
  • testing: 2:1.0.0-3
  • unstable: 2:1.0.1-1
versioned links
  • 2:0.2.1-10: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:0.2.1-14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:0.3.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:1.0.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2:1.0.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-fuse
action needed
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.
Created: 2021-01-18 Last update: 2021-01-18 16:04
lintian reports 1 warning normal
Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.
Created: 2020-07-29 Last update: 2020-07-29 12:33
testing migrations
  • excuses:
    • Migration status for python-fuse (2:1.0.0-3 to 2:1.0.1-1): Waiting for test results, another package or too young (no action required now - check later)
    • Issues preventing migration:
    • Too young, only 1 of 5 days old
    • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-fuse.html
    • Not considered
news
[rss feed]
  • [2021-01-18] Accepted python-fuse 2:1.0.1-1 (source) into unstable (Sebastien Delafond)
  • [2020-01-17] python-fuse 2:1.0.0-3 MIGRATED to testing (Debian testing watch)
  • [2020-01-12] Accepted python-fuse 2:1.0.0-3 (source) into unstable (Sandro Tosi)
  • [2019-11-23] python-fuse 2:1.0.0-2 MIGRATED to testing (Debian testing watch)
  • [2019-11-18] Accepted python-fuse 2:1.0.0-2 (source) into unstable (Sebastien Delafond)
  • [2019-08-04] python-fuse 2:1.0.0-1 MIGRATED to testing (Debian testing watch)
  • [2019-07-30] Accepted python-fuse 2:1.0.0-1 (source) into unstable (Sebastien Delafond)
  • [2018-09-01] python-fuse 2:0.3.1-1 MIGRATED to testing (Debian testing watch)
  • [2018-08-27] Accepted python-fuse 2:0.3.1-1 (source) into unstable (Sebastien Delafond)
  • [2018-08-27] Accepted python-fuse 2:0.3.0-2 (source) into unstable (Sebastien Delafond)
  • [2018-04-18] python-fuse 2:0.3.0-1 MIGRATED to testing (Debian testing watch)
  • [2018-04-13] Accepted python-fuse 2:0.3.0-1 (source amd64) into unstable, unstable (Sebastien Delafond)
  • [2018-02-22] python-fuse 2:0.2.1-16 MIGRATED to testing (Debian testing watch)
  • [2018-02-16] Accepted python-fuse 2:0.2.1-16 (source) into unstable (Sebastien Delafond)
  • [2016-07-07] python-fuse 2:0.2.1-14 MIGRATED to testing (Debian testing watch)
  • [2016-07-02] Accepted python-fuse 2:0.2.1-14 (source amd64) into unstable (Sebastien Delafond)
  • [2016-06-27] Accepted python-fuse 2:0.2.1-13 (source amd64) into unstable (Sebastien Delafond)
  • [2016-03-28] python-fuse 2:0.2.1-12 MIGRATED to testing (Debian testing watch)
  • [2016-03-21] Accepted python-fuse 2:0.2.1-12 (source amd64) into unstable (Sebastien Delafond)
  • [2015-05-09] python-fuse 2:0.2.1-11 MIGRATED to testing (Britney)
  • [2015-05-03] Accepted python-fuse 2:0.2.1-11 (source amd64) into unstable (Sebastien Delafond)
  • [2014-10-01] python-fuse 2:0.2.1-10 MIGRATED to testing (Britney)
  • [2014-09-25] Accepted python-fuse 2:0.2.1-10 (source amd64) into unstable (Sebastien Delafond)
  • [2013-12-31] python-fuse 2:0.2.1-9 MIGRATED to testing (Debian testing watch)
  • [2013-12-20] Accepted python-fuse 2:0.2.1-9 (source amd64) (Sebastien Delafond)
  • [2013-08-22] python-fuse 2:0.2.1-8 MIGRATED to testing (Debian testing watch)
  • [2013-08-11] Accepted python-fuse 2:0.2.1-8 (source amd64) (Sebastien Delafond)
  • [2011-10-13] python-fuse 2:0.2.1-7 MIGRATED to testing (Debian testing watch)
  • [2011-10-02] Accepted python-fuse 2:0.2.1-7 (source i386) (Sebastien Delafond)
  • [2011-09-29] Accepted python-fuse 2:0.2.1-6 (source i386) (Sebastien Delafond)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (0, 1)
  • buildd: logs, clang, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • screenshots
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2:1.0.1-1
  • 2 bugs

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing