Package: python-audit
Version: 1:2.8.4-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
The following operations fail due to a SWIG-related type error:
```
% sudo python
Python 2.7.16 (default, Apr 6 2019, 01:42:57)
[GCC 8.3.0] on linux2
Type "help", "co
Package: bareos
Version: 14.2.1+20141017gitc6c5b56-4
Severity: critical
Justification: causes serious data loss
In March 2015 bareos fixed a bug which caused silent corruption of
backups when the following conditions are met:
* backups are written to disk (tape backups are not affected)
* autol
Osamu Aoki wrote:
> Hi Michael,
>
> You are quick :-) Please understand I am all for removing this package.
And this is why I don't want to discuss this issue with you anymore.
>> *) gnu-fdisk is a tool which is an alternative to fdisk, closely
>> imitating it's interface, not hinting on any f
Osamu Aoki wrote:
> At least this bug should be important (or wishlist) severity bug if we
> consider only the bug reported here. But I am happy to keep this as RC.
> Here is the situation:
>
> Although some of the way gnu-fdisk works (bug#504099) is not something I
> like, this Bug #504747 beha
Robert Lemmen wrote:
> hi michael,
>
> could you explain how to create such a partition? i have created a small
> loopback with a GPT partition, but i don't see that behaviour...
Not using a loopback device but a plain file:
# create a sparse file, ~200GB in this case
dd if=/dev/zero of=fakedi
Package: gnu-fdisk
Version: 1.0-3+b1
Severity: grave
Justification: causes non-serious data loss
gnu-fdisk wipes out the Code Area in the MBR of a given device when modifying a
GPT partition. If this happens to be the boot device, this can cause serious
trouble.
The behaviour can be easily veri
6 matches
Mail list logo