Bug#624818: Intend to Adopt

Hi, I intend to adopt this package, but I'm not a DD so I'll need someone to sponsor my uploads. I intend to upload a new version to mentors.debian.org sometime in the next 2 weeks. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8

Bug#635197: python-llfuse: FTBS on mips/mipsel

severity 635197 important thanks On 12/12/2011 11:35 AM, Jakub Wilk wrote: * Nikolaus Rath nikol...@rath.org, 2011-07-23, 13:29: Severity: serious Tags: upstream Justification: fails to build from source gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict- prototypes

Bug#632330: found in 2.30.0-3

close 632330 thanks Issue still present in gnome-screensaver 2.30.0-3: Sorry, I should have looked at more than just the debian revision. Is there any way to work around this bug, so that I can compile a debugging version on testing? I don't have the gold linker installed. Best,

Bug#632330: found in 2.30.0-3

reopen 632330 found 632330 2.30.0-3 thanks Issue still present in gnome-screensaver 2.30.0-3: $ DEB_BUILD_OPTIONS=noopt nostrip dpkg-buildpackage -us -uc [...] libtool: link: gcc -g -O0 -g -O0 -Wall -Wl,-z -Wl,defs -Wl,-O1 -Wl,--as-needed -o gnome-screensaver-dialog gnome-screensaver-dialog.o

Bug#635196: python-llfuse: Fails to build on kFreeBSD i386 amd64

Package: python-llfuse Version: 0.33-1 Severity: serious Justification: fails to build from source gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict- prototypes -g -O2 -fPIC -g -I/usr/include/python2.7 -c src/llfuse.c -o

Bug#635197: python-llfuse: FTBS on mips/mipsel

Package: python-llfuse Version: 0.33-1 Severity: serious Tags: upstream Justification: fails to build from source gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict- prototypes -g -O2 -fPIC -g -I/usr/include/python2.7 -c src/llfuse.c -o build/temp.linux-mips-2.7/src/llfuse.o

Bug#635197: dev_t and (struct stat).st_rdev

tag 635197 = help confirmed thanks I don't really understand what's going on here. llfuse.c is generated by Cython, so it's not that easy to read, but the the assignment that gcc complains about is really just this: static PyObject *__pyx_f_6llfuse_fill_c_stat(PyObject *__pyx_v_attr, struct

Bug#630192: Confirm

I can confirm this problem. -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#630605: python-llfuse: Documentation is not built from source

On 06/15/2011 10:22 AM, Didier Raboud wrote: Source: python-llfuse Version: 0.32-1 Severity: serious Justification: DFSG-freeness -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, as the changelog mentions and as the debian/rules file confirms, the documentation shipped in

Bug#630605: python-llfuse: Documentation is not built from source

On 06/15/2011 11:16 AM, Alexander Reichle-Schmehl wrote: Hi! Am 15.06.2011 17:05, schrieb Nikolaus Rath: I believe that the consensus on this is that it's nice to have, but not a policy violation: http://lists.debian.org/debian-devel/2010/08/msg00095.html In the very same thread

Bug#630605: Update

Hi, A new sphinx release with the required backport is going to be uploaded on Sunday. I already prepared an updated python-llfuse package as well, just need to find someone to sponsor the upload. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP

Bug#632330: gnome-screensaver: Fails to build undefined reference to symbol 'xkl_engine_get_instance'

Package: gnome-screensaver Version: 2.30.0-3 Severity: serious Justification: fails to build from source Building on testing, with sources from unstable: $ sudo apt-get build-dep gnome-screensaver [...] $ DEB_BUILD_OPTIONS=nostrip noopt fakeroot apt-get -b source gnome- screensaver [...]

Bug#632473: pcp

I agree, next release of S3QL will ship with pcp as parallel-cp (unless someone has a better suggestion). Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to

Bug#652751: your mail

On 12/27/2011 01:00 PM, Stefano Rivera wrote: tag 652751 - pending thanks The committed fix isn't going to work. Why not? If the correct argparse version is installed, distribute shouldn't be trying to download anything anymore. Best, -Nikolaus -- »Time flies like an arrow, fruit

Bug#701350: Processed: your mail

Hi Michael, What does the experimental tag mean? I just removed the sid tag on behest of the release team, so I'm not sure that this one is appropriate either. Note that even though the unit tests only fail with libc 2.17, both the woody and sid S3QL versions contain the buggy code. Best,

Bug#705314: tomboy-latex: Not usable with tomboy 0.10

Package: tomboy-latex Version: 0.5-3 Severity: grave Justification: renders package unusable Tomboy-latex 0.5 is not compatible with Tomboy 0.10 (the only version in wheezy). The currently packaged version of tomboy-latex is therefore unusable. Note that the current upstream version (0.7) is

Bug#731299: python-pytest: Broken because of pkg_resources.VersionConflict

Package: python-pytest Version: 2.2.4-2 Severity: grave Justification: renders package unusable With latest python3-pytest from sid, I get # py.test-3.3 Traceback (most recent call last): File /usr/bin/py.test-3.3, line 5, in module sys.exit(load_entry_point('pytest==2.4.2',

Bug#755358: s3ql: FTBFS on kfreebsd-* + s390x: test failures

I have no idea why the test would time out on s390x. Especially since it's unchanged since the last release - which built just fine on s390x. I will fix the kFreeBSD bugs and hope that the s390x problem was a fluke that's going to disappear on the next build without me doing anything. -- To

Bug#746908: bla

severity 746908 normal bye Setting severity to normal, because it builds just fine for me. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a

Bug#745243: (no subject)

reassign 745243 python-dugong thanks The build actually works fine. The unit tests fail, but this is because the python3-dugong package is not kFreeBSD compatible. -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

Bug#746908: updated build log

The recent builds (e.g. https://buildd.debian.org/status/fetch.php?pkg=s3qlarch=amd64ver=2.8.1%2Bdfsg-1%2Bb1stamp=1401360556file=log) actually build the s3ql application just fine. What fails is building the documentation and running the unit tests: Running html builder... creating

Bug#758013: s3ql autopkg test regression

On 08/13/2014 03:18 AM, Matthias Klose wrote: http://ci.debian.net/data/packages/unstable/amd64/s/s3ql/20140811_044901.autopkgtest.log === FAILURES === __ NewerMetadataTest.test_all

Bug#769250: python-dugong: FTBFS in jessie/i386: dh_auto_test: pybuild --test -i python{version} -p 3.4 --dir . returned exit code 13

On 11/12/2014 10:42 AM, Andrey Rahmatullin wrote: On Wed, Nov 12, 2014 at 11:22:55AM +0100, Lucas Nussbaum wrote: === FAILURES === _ test_httpcat _ Traceback

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

On 11/29/2014 09:49 AM, Shannon Dealy wrote: Package: s3ql Version: 2.11.1+dfsg-1 Severity: critical Justification: causes serious data loss Dear Maintainer, While running rsync to backup data to an s3ql file system mounted from Amazon's S3 services, the internet connection failed,

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

On 11/29/2014 01:36 PM, Shannon Dealy wrote: On Sat, 29 Nov 2014, Nikolaus Rath wrote: On 11/29/2014 09:49 AM, Shannon Dealy wrote: Package: s3ql Version: 2.11.1+dfsg-1 Severity: critical Justification: causes serious data loss Dear Maintainer, While running rsync to backup data

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

On 11/29/2014 03:54 PM, Nikolaus Rath wrote: 1. mount.s3ql not coping well with a failed internet connection (a no route to host failure, to be precise, it copes quite well with other failures) This one is actually a bug in python-dugong. I have just fixed this in https://bitbucket.org

Bug#771452: s3ql: fsck.s3ql on crashed file system results in uncaught exception

On 11/29/2014 03:54 PM, Nikolaus Rath wrote: 2. fsck.s3ql not being able to fix the local database This one is more interesting. The traceback looks as if the backend (aka S3) reports two objects with the same name (which I think should be impossible). Since S3QL is using the object names

Bug#771452: Copied bucket

On 11/30/2014 12:50 AM, Shannon Dealy wrote: I suspect this is because you copied the objects into a new bucket, but did not include the associated metadata. Which tool did you use to do the copy, and how did you call it? I used the AWS command line tools: aws s3 sync

Bug#771452: Duplicate object check

On 11/30/2014 01:07 AM, Shannon Dealy wrote: Attached is the object_list.txt file from running fsck using your patch. Seems a little peculiar that the exception occurs at the 10 object mark, though it may simply be chance and mean nothing: ..processed 10 objects so far..

Bug#771452: Copied bucket

On 11/30/2014 12:03 PM, Shannon Dealy wrote: Poking around, it appears that the metadata was lost only on the s3ql_metadata files, so I deleted them and ran the aws s3 sync command again. The new files again were missing the metadata, so I just copied the 13 s3ql_metadata files using

Bug#771452: Duplicate object check

On 11/30/2014 07:07 PM, Nikolaus Rath wrote: On 11/30/2014 01:07 AM, Shannon Dealy wrote: Attached is the object_list.txt file from running fsck using your patch. Seems a little peculiar that the exception occurs at the 10 object mark, though it may simply be chance and mean nothing

Bug#771452: Duplicate object check

On 12/01/2014 02:04 AM, Shannon Dealy wrote: On Sun, 30 Nov 2014, Nikolaus Rath wrote: On 11/30/2014 07:07 PM, Nikolaus Rath wrote: On 11/30/2014 01:07 AM, Shannon Dealy wrote: Attached is the object_list.txt file from running fsck using your patch. Seems a little peculiar

Bug#771452: Duplicate object check

On 12/01/2014 02:31 PM, Shannon Dealy wrote: On Mon, 1 Dec 2014, Nikolaus Rath wrote: [snip] I think at this point I can probably write you a patch to get the file system functional again, but I'd very much like to find out what's happening here. Would you be able to run fsck

Bug#771452: Duplicate object check

severity -1 normal retitle -1 fsck.s3ql sporadically crashes when checking objects thanks Retitling this bug and lowering severity for now. I don't think that the mount.s3ql crash is related to the fsck.s3ql crashes, or that there is any data corruption. Best, -Nikolaus -- GPG encrypted emails

Bug#771969: s3ql: mount.s3ql throws exception and hangs file system

severity 771969 important thanks Thanks for the report! I'll set the severity to important for now, because the package still works nicely for many other users. Not sure why it's making so much trouble for you.. but I notice that (like the last bug you found) this seems related to the handling of

Bug#781652: python3-llfuse-dbg: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python3/dist-packages/llfuse/capi.cpython-34dm-x86_64-linux-gnu.so

On Apr 01 2015, Andreas Beckmann a...@debian.org wrote: Preparing to unpack .../python3-llfuse-dbg_0.40+dfsg-1_amd64.deb ... Unpacking python3-llfuse-dbg (0.40+dfsg-1) over (0.40-2+b2) ... dpkg: error processing archive /var/cache/apt/archives/python3-llfuse-dbg_0.40+dfsg-1_amd64.deb

Bug#790525: FBTFS: No module named 'llfuse.capi'

Hi, I just noticed that in your previous emails you tested with 'python3-dbg', but listed the contents of the 'python3-llfuse' package. However, in order to import llfuse in python3-dbg, you need to have the python3-llfuse-dbg package installed. But I assume that is the case? According to the

Bug#790525: FBTFS: No module named 'llfuse.capi'

Alright, I figured it out. s3ql is actually missing a build-dependency on python3-llfuse-dbg. It is probably pulled in indirectly in some circumstances. Thanks for the report! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#790525: FBTFS: No module named 'llfuse.capi'

sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com ... python3 setup.py build_cython running build_cython /usr/lib/python3/dist-packages/Cython/Compiler/Main.py:514: UserWarning: got unknown compilation options, please remove: recursive, warning_errors

Bug#790525: FBTFS: No module named 'llfuse.capi'

On Jun 30 2015, Martin Michlmayr t...@hp.com wrote: * Nikolaus Rath nikol...@rath.org [2015-06-29 21:02]: # python3-dbg Python 3.4.3+ (default, Jun 2 2015, 14:09:35) [GCC 4.9.2] on linux Type help, copyright, credits or license for more information. import llfuse import llfuse.capi

Bug#794056: python-llfuse: python3-llfuse FTBFS in unstable

control: tags -1 +pending On Jul 30 2015, Steve Langasek steve.langa...@canonical.com wrote: While preparing the python3.5 transition in Ubuntu, we found that python-llfuse would fail to build from source. Where previously the package could be built against cython alone, it's now necessary to

Bug#788161: python-llfuse-dbg, python3-llfuse-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

On Jun 09 2015, Andreas Beckmann a...@debian.org wrote: For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 29 2015, Sam Hartman hartm...@debian.org wrote: Hi. I attempted the following: * Built with the patch applied on a jessie chroot * installed s3ql * On a wheezy system mkfs.s3ql, mount and add some data. unmount. * On my patched jessie system run s3qladm upgrade So far so good.

Bug#792685: Unable to upgrade from wheezy to jessie

Note to self: S3QL versions prior to 2.10 (and all of the 1.x versions) did not read the object metadata on object copy and object rename. Therefore, the unsafe pickle could have been there for quite some time. However, this still does not explain why the object survived the upgrade without being

Bug#788161: python-llfuse-dbg, python3-llfuse-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

On Jul 30 2015, Andreas Beckmann a...@debian.org wrote: On 2015-07-30 05:23, Nikolaus Rath wrote: Am I missing something? Or is this bug only about the transition from directory to symlink? It's only about the transition which must be handled with special care. But the problem I noticed

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 29 2015, Sam Hartman hartm...@debian.org wrote: Then run fsck.s3ql. It looks like it has trouble with the old metadata: Backing up old metadata... Uncaught top-level exception: Traceback (most recent call last): [...] Could you please post the complete traceback? The one you included

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 30 2015, Sam Hartman hartm...@debian.org wrote: I'll try and reproduce this in the next day or so and give you access to a failing example. No need, I just managed to reproduce it locally with a filesystem freshly created in wheezy. I'll look into it. Best, -Nikolaus -- GPG encrypted

Bug#792685: Updated package

Hi, I uploaded an updated package to mentors for easier testing (and also for someone to sponsor the upload if we've sorted out all problems, I'm not a DD): https://mentors.debian.net/package/s3ql http://mentors.debian.net/debian/pool/main/s/s3ql/s3ql_2.11.1+dfsg-3.dsc Best, -Nikolaus -- GPG

Bug#792685: Unable to upgrade from wheezy to jessie

Hi, Alright, I figured this one out. First, the reason you're having an s3ql_metadata_bak_0 object right after the upgrade is that the upgrade itself backups up the metadata *after* having added the _pre21 suffix to the existing backups. Secondly (and contrary to what I said before), this

Bug#792685: Unable to upgrade from wheezy to jessie

control: tags -1 +pending I've just uploaded a new package to mentors that should fix the issue with the unsafe metadata backup. If this works for you too, I think this is suitable for stable-updates. I'm not sure what the procedure is to get a package in there, so please let me know if I can do

Bug#794056: python-llfuse: python3-llfuse FTBFS in unstable

On Jul 30 2015, Steve Langasek steve.langa...@ubuntu.com wrote: On Thu, Jul 30, 2015 at 05:26:17AM -0700, Nikolaus Rath wrote: control: tags -1 +pending On Jul 30 2015, Steve Langasek steve.langa...@canonical.com wrote: While preparing the python3.5 transition in Ubuntu, we found

Bug#794918: cython is uninstallable in unstable

Package: cython Version: 0.22.1-1 Severity: serious As of today in a clean sid chroot: # apt install cython Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfuse2

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 17 2015, Sam Hartman hartm...@debian.org wrote: I have a filesystem that I can easily mount and fsck in wheezy, but when I try to run the jessie s3qladm upgrade command I get: Getting file system parameters.. File system revision too old to upgrade! [...] It's critical that there be

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 17 2015, Sam Hartman hartm...@debian.org wrote: If a package is not going to provide an upgrade from one debian release to the next, it should not generally be in the Debian release. It would be fine for it to continue to be in unstable. We need to figure out if someone is willing to

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 19 2015, Nikolaus Rath nikol...@rath.org wrote: Looking at the debian news file, the only announced upgrade is at version 2.5 between 1.11 and 2.11.1. Oh. Obviously my memory has failed me completely here. You are right. I just checked, all that is needed is one interim version

Bug#792685: Unable to upgrade from wheezy to jessie

On Jul 19 2015, Sam Hartman hartm...@debian.org wrote: Nikolaus I agree. There shouldn't have been an s3ql package in Nikolaus Wheezy. This was when I was young and inexperienced with Nikolaus Debian packaging. However, the situation is different for Nikolaus Jessie. Now that

Bug#792685: Unable to upgrade from wheezy to jessie

Hi, Could you give the attached patch for Jessie's S3QL a try? It should allow to upgrade from wheezy file systems. (Try it with a test file system first) Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E

Bug#799261: s3ql-dbg: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/s3ql/s3ql/deltadump.cpython-34dm-x86_64-linux-gnu.so

On Sep 17 2015, Andreas Beckmann wrote: > A file in /usr/lib/s3ql does not belong into a -dbg package at all! I believe it most certainly does. Why do you think otherwise? It's common practice for Python extensions to ship the extension for the debug interpreter in the -dbg

Bug#821793: python-llfuse: FTBFS in testing

Your build system is missing /etc/mtab (should be a symlink to /proc/mounts). At the moment I consider this a bug in your system, not in the package. But I'm willing to be convinced by suitably convincing references :-). Best, -Nikolaus -- GPG encrypted emails preferred. Key id:

Bug#851724: python-llfuse: FTBFS (failing tests)

On Jan 22 2017, Santiago Vila <sanv...@unex.es> wrote: > On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote: > >> Are you able to reproduce this with Python 3.5? > > I don't know. I'm just building the package from source. > > The package currently build-

Bug#851724: python-llfuse: FTBFS (failing tests)

On Jan 17 2017, Santiago Vila wrote: > Exception in thread Thread-1 (most likely raised during interpreter shutdown): > Traceback (most recent call last): > File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner > File "/usr/lib/python2.7/threading.py",

Bug#837254: @pytest.skip outside test gives error

Control: reassign 837254 pytest On Sep 10 2016, Lucas Nussbaum wrote: >> collecting ... >> ERRORS >> >> __ ERROR collecting test_examples.py >> ___ >> Using

Bug#844931: python-dugong: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13

On Nov 19 2016, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. [...] >> Traceback (most recent call last): >> File "/usr/lib/python3.5/ssl.py", line 799, in read >> return self._sslobj.read(len, buffer) >> File

Bug#844931: python-dugong: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13

Control: reassign 844931 python3 Control: affects 844931 +python-dugong thanks I think this is actually a bug in Python 3 - and might be caused by the recent OpenSSL transition. Unless I'm mistaken, reading from an SSLSocket should not raise OSErrors with errno 0. For example: >> File

Bug#850469: dgit: Can't push: corrupted object

On Jan 06 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Control: forcemerge 849041 -1 > > Nikolaus Rath writes ("Bug#850469: dgit: Can't push: corrupted object"): >> remote: dgit-repos-server: reject: corrupted object >> 1bc3c1e2d353386487d7d

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

> Steps to reproduce: > > $ echo foo > "Kieran Daycare Contract.pdf" > $ echo bar > "Kieran Daycare 2.pdf" > $ tar cJvf "Kieran Daycare Contract.pdf.tar.xz" "Kieran Daycare > Contract.pdf" > Kieran Daycare Contract.pdf > > $ xarchiver Kieran\ Daycare\ Contract.pdf.tar.xz > # Select Action->Add

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

Package: xarchiver Version: 1:0.5.4-1+deb8u1 Severity: critical Justification: causes serious data loss As far as I can tell, using xarchiver to add additional files to a .tar.xz file will destroy the existing data. Steps to reproduce: $ echo foo > "Kieran Daycare Contract.pdf" $ echo bar >

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

On May 20 2017, Markus Koschany wrote: > Am 19.05.2017 um 23:23 schrieb Chris Lamb: >> tags 862593 + patch >> thanks >> >> The archive gets overwritten as the test to see whether it already exists >> (to determine whether to create a new one or simply add a new file) uses >> an

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

On May 20 2017, Markus Koschany <a...@debian.org> wrote: > On Fri, 19 May 2017 16:26:03 -0700 Nikolaus Rath <nikol...@rath.org> wrote: >> On May 20 2017, Markus Koschany <a...@debian.org> wrote: >> > Am 19.05.2017 um 23:23 schrieb Chris Lamb: &g

Bug#979137: s3ql: Update to newest upstream release

Package: s3ql Severity: serious Justification: N/A There is a new upstream release that fixes a number of bugs against the Debian package. However, it is blocked on a dependency on the python3-pyfuse3 module that is not in Debian. Uploading python3-pyfuse3 and the newest S3QL release would make

Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

Control: severity 959117 important thanks Hi Graham, This package is up for adoption. The only that's needed to get it in shape again is to upgrade to the newest upstream release. However, this requires packaging the new python3-pyfuse3 dependency first. I'm also downgrading the severity,

Bug#994171: elpa-jedi-core incompatible with python3-jedi in bullseye

Package: elpa-jedi-core Version: 0.2.8-1 Severity: grave The elpa-jedi-core package in bullseye is incompatible with the python3-jedi package shipped in bullseye, thus rendering this package mostly useless (justifying 'grave' severity). I hope that maybe the problem can be solved with a