/fstransform/commit/1a935732abdd2ef998b8a3f172dc6d9548b49fab
Thanks!
--
Alexander E. Patrakov
Package: fstransform
Version: 0.9.3-2
Severity: critical
Tags: upstream
Justification: causes serious data loss
Dear Maintainer,
approximately 1.5 years ago I have discovered a reproducible case
of filesystem corruption by fstransform, and reported it upstream:
https://github.com/cosmos72/fstran
Stefan Fritsch :
> The rng should be initialized after the seed is loaded from disk.
This is false according to systemd developers. Its state is changed,
but it is still not initialized, because they think that the seed
might come from a gold master image.
--
Alexander E. Patrakov
y
upgrading an old system, or running debootstrap directly, or running old
debootstrap, or using major hacks during the install procedure.
--
Alexander E. Patrakov
installed during that five-month
period.
In other words, it's already too late to "minimize" the damage by
undoing the change, and there is no point in acting quickly. At least in
my opinion.
--
Alexander E. Patrakov
Are there any plans to produce a stable update containing this fix?
05.07.2015 21:43, Alexander E. Patrakov wrote:
I have hit this bug in a Jessie-based virtual machine that I created in
order to teach myself how to deal with MD RAID1.
In order to work around it, I have replaced initramfs-tools with dracut
(040+1-1). Result: the bug is still reproducible. The
some timeout, we cannot find all RAID
components, is missing.
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ds no packages.
Versions of packages rrdtool suggests:
pn librrds-perl (no description available)
-- no debconf information
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.5.9-4Apply a diff file to an
original
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
B-compliant RPM packages
must be documented somewhere under /usr/share/doc/lsb-rpm, or, better,
made the defaults for the "lsb-rpm" command.
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages lsb-rpm depends on:
ii rpm 4.4.1-14.1 Re
Package: ftp.debian.org
Version: unavailable
Severity: serious
Tags: security
There are two files named "file_4.17-5etch2_i386.deb" with different
md5sum, one at
http://ftp.debian.org/debian/pool/main/f/file/file_4.17-5etch2_i386.deb
and one at
http://security.debian.org/pool/updates/main/f/f
Joey Hess wrote:
Please file this as a separate bug on udev.
Done, see #405775.
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
eth0. Bug!
While it took us some special preparations to trigger this bug with two
identical network cards, I guess that this will happen by itself with 50%
probability if the network cards are not identical, due to random module
loading order.
7) This time, repeat step (5), using names &qu
Package: zinf
Version: 2.2.5-5.2
Severity: grave
Justification: renders package unusable
Every time I start zinf, it shows the filetype association dialog, and
then quits. If I start it from the console, I see the following error:
[EMAIL PROTECTED]:~$ zinf
(:2295): Gdk-WARNING **: Attempt to dr
CFLAGS, this is necessary to fix
slirp-1.0.16 and previous versions. In adiition, for slirp-1.0.16 for some
strange reason the mtu has to be set to value lower than 1500, but that's
probably a different bug.
--
Alexander E. Patrakov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
17 matches
Mail list logo
