Bug#1081022: ITP: libcurlfs -- mounts remote HTTP/HTTPS URLs as a FUSE filesystem

2024-09-06 Thread наб
Package: wnpp Severity: wishlist Owner: наб X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: libcurlfs Version : 0 Upstream Contact: наб * URL : https://sr.ht/~nabijaczleweli/libcurlfs * License : 0BSD Programming Lang: C++ Description

Bug#1059761: ITP: snappy-tools -- Snappy, a fast compressor/decompressor ‒ program

2023-12-31 Thread наб
Package: wnpp Severity: wishlist Owner: наб X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: snappy-tools Version : 0 Upstream Contact: наб * URL : https://sr.ht/~nabijaczleweli/snappy-tools * License : 0BSD Programming Lang: C++ Description

Re: Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-10-20 Thread наб
On Sun, Oct 20, 2024 at 11:39:36PM +0200, Ben Hutchings wrote: > On Sun, 2024-10-20 at 20:03 +0200, наб wrote: > > I'd like to use an epoch so I'm asking for consensus per policy 5.6.12. > > > > As part of the Salvage Team's trixie view-os removal plan ‒ >

Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-10-20 Thread наб
https://github.com/alperakcan/fuse-ext2 instead of src:fuse-umfuse-ext2. The current version of src:fuse-umfuse-ext2 in sid is 0.4-1.5, and the current version of https://github.com/alperakcan/fuse-ext2 is 0.0.11, so src:fuse-ext2 would need to be version 1:0.0.11-1 to update right.

Bug#1085590: ITP: fuse-ext2 -- File System in User Space - Module for ext2

2024-10-20 Thread наб
Package: wnpp Severity: wishlist Owner: наб X-Debbugs-Cc: debian-devel@lists.debian.org Control: block -1 by 1085457 * Package name: fuse-ext2 Version : 0.0.11 Upstream Contact: Alper Akcan * URL : https://github.com/alperakcan/fuse-ext2 * License : GPL-2

Re: Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-10-22 Thread наб
Hi! On Tue, Oct 22, 2024 at 02:08:47PM +0200, Guillem Jover wrote: > On Tue, 2024-10-22 at 00:00:21 +0200, Ben Hutchings wrote: > > On Mon, 2024-10-21 at 00:49 +0200, наб wrote: > > > On Sun, Oct 20, 2024 at 11:39:36PM +0200, Ben Hutchings wrote: > > > > On Sun,

Re: Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-10-24 Thread наб
On Thu, Oct 24, 2024 at 10:44:46AM -0400, Theodore Ts'o wrote: > On Thu, Oct 24, 2024 at 02:13:05PM +0200, наб wrote: > > I've implemented this but can't test it fully because > > https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git > > is missing an up-to-d

Re: Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-10-24 Thread наб
On Wed, Oct 23, 2024 at 10:53:29PM -0400, Theodore Ts'o wrote: > On Tue, Oct 22, 2024 at 04:56:05PM +0200, наб wrote: > > ...but now that I look at this there's fuse2fs, > > which is naturally better than some third-party implementation. > > > > The int

Has anyone seen Yann Amar (src:bilibop)?

2024-10-25 Thread наб
imed after https://github.com/cybernoid/archivemount/issues/29 but early 2021 is not much different to excess deaths from late 2020 :/). Has anyone seen Yann Amar? наб signature.asc Description: PGP signature

Multiple copies of fatfs in the archive?

2024-11-08 Thread наб
hing material. I started writing this to propose some sort of hoisting, but this no longer appears feasible. Ah well. Best, наб signature.asc Description: PGP signature

Is there a point to retaining src:pth?

2024-11-16 Thread наб
Hi! src:pth has been gone from testing since August. There are no rdeps and no rbuilddeps, and only FTBFS bugs since like 2012. I can hardly imagine a point to Pth at all in 2024 (or any time after ubiquitous pthread support), so it reads to me like an easy QA removal. But, this seems incongruent

Re: Is there a point to retaining src:pth?

2024-11-17 Thread наб
On Sun, Nov 17, 2024 at 11:21:00AM +0100, Ben Hutchings wrote: > On Sun, 2024-11-17 at 03:22 +0100, наб wrote: > > src:pth has been gone from testing since August. > > There are no rdeps and no rbuilddeps, > > and only FTBFS bugs since like 2012. > > I can hardly imagi

Re: Epoch for src:fuse-ext2 to replace src:fuse-umfuse-ext2's fuseext2 binary

2024-11-29 Thread наб
On Fri, Nov 29, 2024 at 07:29:19AM -1000, Theodore Ts'o wrote: > On Thu, Oct 24, 2024 at 05:37:59PM +0200, наб wrote: > > idk if you got a notification (the confirmation mail would indicate > > otherwise?), but the patch is at #1085590. I've tested it to behave > >

Re: Do we need three-and-a-half nigh-identical X compositors ‒ xcompmgr, compton, picom, unagi?

2024-12-13 Thread наб
On Fri, Dec 13, 2024 at 09:30:09AM -0600, Aaron Rainbolt wrote: > It's worth noting that Lubuntu is currently shipping Picom by default. > I don't think you're proposing getting rid of it, but if that ends up > being considered, I'd prefer if it could be kept around or if the > Lubuntu team could a

Do we need three-and-a-half nigh-identical X compositors ‒ xcompmgr, compton, picom, unagi?

2024-12-13 Thread наб
Hi! We seem to be shipping 3.5 standalone compositors (maintainers in CC): 1. xcompmgr ‒ the upstream's effectively finished (we have 1.1.8, the two releases since changed nothing of substance) last maintainer upload 2019-07 popcon inst=852 vote=171 2. co