[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Processed: [bts-link] source package zfs-linux



Processing commands for control@bugs.debian.org:

> #
> # bts-link upstream status pull for source package zfs-linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #     https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-link@lists.debian.org
Setting user to debian-bts-link@lists.debian.org (was debian-bts-link@lists.debian.org).
> # remote status report for #990130 (http://bugs.debian.org/990130)
> # Bug title: Problems when mounting ZFS datasets in wrong order
> #  * https://github.com/openzfs/zfs/issues/13674
> #  * remote status changed: (?) -> open
> usertags 990130 + status-open
There were no usertags set.
Usertags are now: status-open.
> # remote status report for #1057018 (http://bugs.debian.org/1057018)
> # Bug title: zfs-dkms: VERIFY3 failed; PANIC at range_tree.c:435; cause all operations to hang until hard reboot
> #  * https://github.com/openzfs/zfs/pull/14843
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1057018 + fixed-upstream
Bug #1057018 [zfs-dkms] zfs-dkms: VERIFY3 failed; PANIC at range_tree.c:435; cause all operations to hang until hard reboot
Added tag(s) fixed-upstream.
> usertags 1057018 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1059939 (http://bugs.debian.org/1059939)
> # Bug title: linux-image-6.1.0-17-rt-amd64: dkms will not build zfs module for rt-amd64
> #  * https://github.com/openzfs/zfs/issues/11097
> #  * remote status changed: (?) -> open
> usertags 1059939 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057018
1059939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059939
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems


Reply to: