Package: zfs-linux
Version: 0.7.3
Severity: wishlist
--- Please enter the report below this line. ---
0.7.4 was released. I've pulled both spl and zfs, refreshed patches,
and included several bugfixes in
https://github.com/aerusso/pkg-zfsonlinux-zfs
and
The patch looks like it does three things:
1. Adds a dependency to zfs-zed
2. Corrects the path of zfs-zed in zfs-function
3. Installs zfs-import, zfs-mount, and zfs-zed as sysv startup scripts
1 should be submitted upstream to zfsonlinux, since this should be shared by
everyone. Once accepted
Package: src:zfs-linux
Version: 0.7.3-3
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Upstream has added several bugfixes and compatibility support,
including Linux 4.14, an NFS permission error (1030f807b), compressed
buffer handling (d7881a6dc), and the major,
Control: tag -1 patch
The referenced patch adds a breaks/replaces relationship with
most of the packages from upstream "make deb". This should ease
conversion between upstream DEBs and Debian's DEBs.
[1] github.com/aerusso/pkg-zfsonlinux-zfs.git
Commit 8c38f1fa Break/Replace upstream debs
Control: tag -1 patch
I've moved ztest into the new zfs-test package,
and added the conflicts to that package instead of
zfsutils-linux.
[1] github.com/aerusso/pkg-zfsonlinux-zfs.git
commit 0c27f909 Move testing framework to zfs-test
Package: spl-linux
Version: 0.7.3-1
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Upstream spl stable branch has advanced somewhat, most notably adding a Linux
4.14 compatibility patch.
I've personally been running this patchset [1] on a few machines. If you'd
The proposed patch has been included upstream, and should be reflected in the
current package.
Because mtab has "always" been linked to /proc/self/mounts, I'm not sure if
this report was "theoretical" or represented an observed problem that may
have a different root cause.
Could you please
Control: fixed -1 zfs-linux/0.7.3-1
I think support for this was added. The manual page lists
the -o and -x options under zfs receive (though I have not
tested it).
Please reopen this bug if the package still lacks this
functionality.
Control: found -1 zfs-linux/0.6.5.11-1
This problem is not new to 0.7.3, so to avoid blocking the migration,
I'm marking this as found in the old version too.
n Thu, Nov 30, 2017 at 06:56:47AM -0500, Antonio Russo wrote:
>
> Hi,
>
>> Control: fixed -1 zfs-linux/0.7.3-3
>>
>> Thanks for noticing there was a problem. I've closed this report since
>> you have said it was a duplicate of #881013 and #880709, which have
Control: fixed -1 zfs-linux/0.7.3-3
Thanks for noticing there was a problem. I've closed this report since
you have said it was a duplicate of #881013 and #880709, which have
been fixed.
Please reopen this if you still encounter this bug.
Antonio
Control: fixed -1 0.7.3-3
This should be fixed, along with 883008 and 883076. Thanks for pointing this
out!
The body of the last email interchanged > and < signs. The attached patch
does not have that mistake, but a double check of my understanding of the
Debian version comparison algorithm [1] might still be a good idea.
[1] http://www.fifi.org/doc/debian-policy/policy.html/ch-versions.html
pares less than the '.',
rather than requiring
the exact version ${source:Upstream-Version}, which will never be in the
archives.
commit cfb50102c8864ba59a67a25e772efe8d0c73e996
Author: Antonio Russo <antonio.e.ru...@gmail.com>
Date: Sun Nov 19 17:03:47 2017 -0500
Add maximum version dependency on
I've attached a very simple patch enforcing this constraint.
Antonio
commit cfb50102c8864ba59a67a25e772efe8d0c73e996
Author: Antonio Russo <antonio.e.ru...@gmail.com>
Date: Sun Nov 19 17:03:47 2017 -0500
Add maximum version dependency on spl-dkms
diff --git a/debian/control b/
All upstream testing and development is done with matching library and utility
versions.
I really don't see any advantage to making fine-grained dependencies that
expose Debian
users to unconventional configurations with some possibly non-matching library
versions.
Just my 2 cents.
Antonio
The package should also
Recommends: gir1.2-appindicator3-0.1
so that by default people can get a tray icon.
The two github repositories
https://github.com/aerusso/pkg-zfsonlinux-zfs
https://github.com/aerusso/pkg-zfsonlinux-spl
have upstream branches representing an import of the zfs/spl
sources, and a "proposed-updates" branch which includes now
a changelog entry. It builds, installs, and runs on a
my branch pulled into the alioth git, and what other
blockers there are for a debian 0.7.2 release.
Thanks,
Antonio Russo
Control: reassign -1 alsa-utils
The same changes should also be applied to
/lib/systemd/system/alsa-restore.service
/etc/init.d/alsa-utils
On 10/13/17 09:27, Felipe Sateler wrote:
> On Fri, Oct 13, 2017 at 9:58 AM, Antonio Russo
> <antonio.e.ru...@gmail.com> wrote:
>> On 10/13/17 07:30, Michael Biebl wrote:
>>>
>>> That seems like the wrong approach. sound.target does not have any
>>>
On 10/13/17 07:30, Michael Biebl wrote:
>
> That seems like the wrong approach. sound.target does not have any
> dependencies on /tmp.
> If anything, it's pulseaudio which should ensure that /tmp is mounted.
I agree, wholeheartedly. But getting this directory out of /tmp has
been a bug for 7
Package: systemd
Version: 234-3
Severity: normal
--- Please enter the report below this line. ---
I mount a filesystem over /tmp in /etc/fstab, but if I take a peek underneath,
> # mount --bind / /mnt
> # cd /mnt
> # ls -la
> total 16
> drwxrwxrwt 4 root root 4096 Oct 13 01:46 ./
> drwxr-xr-x
On 10/12/17 06:12, Fabian Grünbichler wrote:
>
> I would also suggest cherry-picking/backporting the following two
> upstream PRs on top of 0.7.2:
>
> #6616: send/recv compatibility with 0.6.5.x [1]
> #6695: receive_freeobjects() skips freeing some objects [2]
>
> the first (DISCLAIMER: written
support for powerpc,
mostly because I have no ability to test that platform (and the code around
that seemed to have quite a bit of churn). Also several patches were applied
upstream, so they also got removed.
How can I help out the packaging team on this? Who should I email?
Thanks,
Antonio Russo
Control: close -1
I don't know which version exactly fixed this bug, but I cannot reproduce it.
Package: mpi4py
Severity: normal
--- Please enter the report below this line. ---
Any attempt to import mpi4py.MPI induces many errors, beginning with:
mca_base_component_repository_open: unable to open mca_patcher_overwrite:
Package: apt-cacher-ng
Version: 3-4
Severity: normal
--- Please enter the report below this line. ---
The most visible symptom is a log message
[/lib/systemd/system/apt-cacher-ng.service:13] Unknown lvalue
'RequiresMountsFor' in section 'Service'
Moving that parameter into the Unit section
tags -1 + patch
Upstream has posted a patch for this issue. See the github thread:
https://github.com/cython/cython/issues/1538#issuecomment-263995994
Package: src:cython
Version: 0.25.2~b0-1
Severity: important
--- Please enter the report below this line. ---
The following cython file should emit -1/32 three times (up to a zero imaginary
component)
My machine produces a nan+nanj for the third.
b = -0.5+0j
e = 5
I'd like to point out that the patch submitted for this bug has been tested for
the last 8 months on my machine, and still applies cleanly.
I also experience a version of this bug, and similarly find the last working
version to be 45.2.0-3.
Building from the _Debian_ source (i.e., "apt-src install icedove ; apt-src
build icedove") produces perfectly functional debs.
This is also a workaround for people who need a functional
Sorry, there is no 0.6.5.8 release. The fix does exist in the master branch,
however.
(bc77ba7: OpenZFS 6513 - partially filled holes lose birth time)
Package: zfs-dkms
Version: 0.6.5.7-1
Severity: grave
--- Please enter the report below this line. ---
See ZoL bug report.
https://github.com/zfsonlinux/zfs/issues/4809
aka Illumos 6513
Short summary: Pools with hole_birth feature enabled are susceptible to
irreversible damage interfering
Unlike my previous, inaccurate claim, a patch resolving this bug
has now indeed been merged upstream:
https://github.com/collectd/collectd/pull/1553
https://github.com/collectd/collectd/commit/10b10a6718dbb87c6890d4bc821a6e21c8b7b527
Upstream has posted a patch which resolves this bug. Thanks for the guidance!
Forwarded upstream
https://bugzilla.gnome.org/show_bug.cgi?id=763388
I was mistaken. The bug is not resolved in git master. Moreover, my original
bug report is incomplete.
When my USB wifi device is removed and reinserting, networkmanager fails to
register it (somehow). I don't
know if it has anything to do with wext, contrary to my original remark.
A git
So, I rebuilt at git master with --with-wext=yes (which was a mistake, I don't
think it's needed),
and now everything works. Some bug must have been introduced between beta1 and
beta2, which has been
resolved as of b36d7215255f2adb43341c15d438609d4087cc32 . Assuming I read the
git history
On 03/08/16 08:19, Michael Biebl wrote:
> NetworkManager uses the Linux nl80211/cfg80211 interface by default, but
> also has wext as fallback.
Indeed, WEXT does appear to be enabled in this build:
> Mar 08 07:57:46 frost NetworkManager[6271]: [1457452666.584480]
> (wlan0): using WEXT for WiFi
Package: network-manager
Version: 1.1.91-1
Severity: important
--- Please enter the report below this line. ---
After upgrade to 1.1.91-1, my Realktek RTL8191SU (with driver r8712u, which I
believe is wext), is not visible at all to NetworkManager.
Reinstalling version 1.1.90-6 causes "nmcli
ways white. In inverted color schemes, this text can become difficult to
read, or invisible (in particular, in the
Breeze Dark High Contrast scheme shipped with KDE).
The color is chosen to be black, the same choice as made with the Y-labels.
Thanks,
Antonio Russo
--- System information. ---
Ar
The bug I originally was trying to report prevented the X server from
displaying anything on the screen. I am not able to reproduce that
behavior after a reboot. It's possible I did not wait long enough for the
display manager to start up.
That said, the reported error in the log is still
Package: xserver-xorg-legacy
Version: 2:1.17.3-2
Severity: important
--- Please enter the report below this line. ---
I've set needs_root_rights=yes in Xwrapper.config,
because the setup I have requires this.
I'm using SDDM.
--- System information. ---
Architecture: amd64
Kernel: Linux
ctl
output.
Thanks,
Antonio
On 10/08/15 23:52, Martin Pitt wrote:
> Control: tag -1 moreinfo
>
> Hello Antonio,
>
> Antonio Russo [2015-10-08 20:52 -0700]:
>> The machine in question has /var, /tmp on ZFS (/tmp is mounted
>> "legacy style"). Because these ar
Package: systemd
Version: 227-1
Severity: important
--- Please enter the report below this line. ---
I've downgraded all systemd components to 226-4 in the meantime.
The machine in question has /var, /tmp on ZFS (/tmp is mounted
"legacy style"). Because these are needed fairly early in the
boot
Package: collectd
Version: 5.5.0-2
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
This bug[1] results in many lines in syslog reading
"0 Success: 1 value has been dispatched."
and has already been resolved upstream:
I've also hit this bug, and so have others:
http://comments.gmane.org/gmane.comp.kde.devel.konsole/22762
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 06/20/2015 04:41 PM, Ben Hutchings wrote:
[...]
What is this 'newer version'?
I think somehow the ALX driver never got mainlined?
[...]
It did go into mainline in Linux 3.11.
Yes, you are absolutely correct. That unfortunately means
that the solution is going to be more complicated
Package: src:linux
Version: 4.0.5-1
Severity: normal
--- Please enter the report below this line. ---
The ALX driver drops out with fatal interrupt 0x400
after a short while. This apparently was known about
for a while [1] [2]. I _believe_ this problem was
fixed in the newer compat-drivers
Package: zodb
Severity: wishlist
--- Please enter the report below this line. ---
Just weighing in that there is interest in a Debian
package of ZEO (especially for Python 3). Sorry
if this is the wrong place for that.
--- System information. ---
Architecture: amd64
Kernel: Linux
Package: ipython
Version: 2.1.0-1
Severity: normal
--- Please enter the report below this line. ---
Hello,
The file
/usr/lib/python3/dist-packages/IPython/external/ssh/tunnel.py
includes a reference to xrange which is not part of python3
(it should just be range).
Moreover, this seems to just
Package: libwine-unstable:i386
Version: 1.7.14-4
Severity: grave
--- Please enter the report below this line. ---
I just upgraded from 1.7.14-2, installed libgstreamer1.0-0-plugins-base1.0-0,
(which _should_ be in the depends, right?) and now I get the error in the title
whenever calling the wine
Package: sshfs
Version: 2.4-1
Severity: important
Tags: patch
--- Please enter the report below this line. ---
In the event of a network failure, sshfs can become
network-starved, causing programs accessing the sshfs
mount to enter uninterruptible sleep. The solution is
to kill the sshfs
Package: libpam-tmpdir
Version: 0.09
Severity: normal
--- Please enter the report below this line. ---
Many applications (for example, the Nomachine NX client)
look for the .X11-unix directory in $TMP or $TMPDIR,
rather than /tmp. These applications work properly
if a symlink is created:
ln -s
Package: libcairo2
Version: 1.12.0-2
Severity: normal
--- Please enter the report below this line. ---
While using Icedove in an NX session, an immediate
crash occurs. It's probably the same bug as mentioned
on this Arch bug report:
https://bugs.archlinux.org/task/29257
Downgrading to 1.10.2-7
Package: sux
Version: 1.0.1-6
Severity: normal
--- Please enter the report below this line. ---
After upgrading to the newest login version (4.1.5-1), sending
Ctrl-C at any point to the terminal causes the su session to
die, reporting Session terminated, terminating shell...
E.g.,
Package: linux-2.6
Version: 2.6.32-7
Severity: normal
--- Please enter the report below this line. ---
This problems appears in 2.6.32-7; 2.6.32-6 is unaffected.
Every 32-bit program I have attempted to load (wine and
bash-static) fails with a segmentation fault and no output.
Attempts to debug
Package: libwine-alsa
Version: 1.1.19-1
Severity: normal
--- Please enter the report below this line. ---
Upgrade to Wine 1.1.19 fails to play sound with libasound2 1.0.19-1,
failing with
err:module:load_builtin_dll failed to load .so lib for builtin
Package: tspc
Version: 2.1.1-8
Severity: normal
--- Please enter the report below this line. ---
TSPC will intermittently fail to negotiate a tunnel from behind
an NAT, failing with 303 Unsupported tunnel mode.
This is exactly the same problem as mentioned here:
Package: kile
Version: 1:2.1.0~svn933829-1
Severity: normal
--- Please enter the report below this line. ---
Running kile with the command line
kile /tmp/somefile.tex --line 1
where /tmp/somefile.tex is a blank file,
causes the status bar to become corrupted.
In particular, it causes an
Package: kile
Version: 1:2.1.0~svn933829-1
Severity: normal
--- Please enter the report below this line. ---
Hello,
When I open the Configure Shortcuts dialog from the
Settings menu, the program freezes for tens of seconds,
pinning the CPU at ~100%.
Once the window comes up, it performs
Hello,
I can also confirm this behavior on 3.0.5-1. However, I have been able to
resolve this issue as follows:
1) Install iceweasel-gnome-support and desktop-file-utils.
2) Add x-directory/gnome-default-handler to the list of MimeTypes
supported by kfmclient_dir
(To do this, in
201 - 263 of 263 matches
Mail list logo
