Bug#1030924: linux-image-6.0.0-0.deb11.6-amd64: NFS3 client: spurious permission denied, 5.10 ok

2023-02-21 Thread Jakob Bohm
linux-image-5.19.0-0.deb11.2-amd64 is also affected. linux-image-5.10.0-21-amd64 is not affected Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may

Bug#1030924: linux-image-6.0.0-0.deb11.6-amd64: NFS3 client: spurious permission denied, 5.10 ok

2023-02-09 Thread Jakob Bohm
Package: src:linux Version: 6.0.12-1~bpo11+1 Severity: normal Dear Maintainer, When trying to cp a file from an NFS3 client running kernel 6.0.0 to a file server running 5.18.16 with nfs-kernel-server (both machines run bullseye), the cp command complains about "permission denied" and leaves

Bug#600430: linux-2.6: genorig.py does not handle 4-part versions

2010-10-17 Thread Jakob Bohm
On Sun, Oct 17, 2010 at 10:51:08AM +, Debian Bug Tracking System wrote: On Sun, Oct 17, 2010 at 06:39:35AM +0200, Jakob Bohm wrote: Since several years back, kernel.org has provided linux tarballs with both 3 part (e.g. 2.6.35) and 4 part (e.g. 2.6.35.7) version numbers

Bug#600430: linux-2.6: genorig.py does not handle 4-part tarball versions (e.g. 2.6.7.8)

2010-10-16 Thread Jakob Bohm
Source: linux-2.6 Version: 2.6.32-23 Severity: normal Since several years back, kernel.org has provided linux tarballs with both 3 part (e.g. 2.6.35) and 4 part (e.g. 2.6.35.7) version numbers in their filenames. But if genorig.py is run with a 4-part versioned tarball such as

Bug#600432: linux-2.6: debian/bin/genorig.py not marked as executable

2010-10-16 Thread Jakob Bohm
Source: linux-2.6 Version: 2.6.32-23 Severity: normal In the specified squeeze version of this package (2.6.32-23), debian/README.source tells the user to run debian/bin/genorig.py. Unfortunately, that file is not marked as executable in the freshly unpacked source package, requiring the user to

Bug#320042: linux-doc-2.6.12: Is there a bug # against kernel-package for this? Is there a workaround?

2005-08-15 Thread Jakob Bohm
Package: linux-doc-2.6.12 Version: 2.6.12-2 Followup-For: Bug #320042 Since some other people in the project are trying to force-feed 2.6.12 onto users machines, the inability to install the 2.6.12 docs along with prior docs for comparison is kind of a show-stopper. Are there any workarounds to