-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 506888 + moreinfo
thanks
Are you still seeing this on wheezy? Can you try running blkid -p
/dev/cdrom?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
retitle 656228 util-linux: missing upstream changelog
tags 656228 - pending
thanks
It seems the changelog is now missing entirely, not just out of date.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: src:lvm2
It has been over a year since the last upgrade and upstream has had
several new releases with new features and bug fixes, so please upgrade.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 559317 e2fsprogs
thanks
I believe this belongs in a helper program.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSj7krAAoJEJrBOlT6nu75SCgIAKQ4v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> The suggested switch of cfdisk to libslang had been done 2.17.2-3
> but reverted later due to the lack of a ncurses udeb. Upstream's
> build system does not offer to build two versions of cfdisk, one
> with slang and one with ncurses, to be address
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
What is there to explain? The operation is not supported.
On 11/22/2013 06:48 PM, jida...@jidanni.org wrote:
> The user reads the fstrim man page.
>
> The user tries it.
>
> The user gets that odd message.
>
> The user refers back to the man pag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/19/2014 12:23 AM, Nigel Horne wrote:
> Package: util-linux Version: 2.20.1-5.7 Severity: normal File:
> /sbin/cfdisk
>
> Dear Maintainer,
>
> I've tried three versions of Debian and all fail to correctly
> detect the disks on my new machine.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hddtemp
It seems that this project has been dead for several years and this
package continues to bit rot. It seems it is time to remove it. Do
you have thoughts on this Aurelien?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: tags -1 + moreinfo
I'm afraid this isn't enough information to go on. Can you check for
more detailed errors in syslog? The fix for that bug in Ubuntu has
been applied in debian as well for some time.
On 03/27/2014 08:39 PM, Fox F wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: tags -1 - moreinfo
> I'm afraid this isn't enough information to go on. Can you check
> for more detailed errors in syslog? The fix for that bug in Ubuntu
> has been applied in debian as well for some time.
Sorry, I only skimmed the bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/29/2014 03:29 AM, Arthur Marsh wrote:
> Package: gparted Version: 0.18.0-1 Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
> appropriate ***
>
> * What led up to the situation?
>
> ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/2/2014 2:32 AM, Daniel Baumann wrote:
> after another two months of inactivity on this bug and total of
> more than 2 years of lacking behind, debian-qa might want to
> consider doing something about it, such an important package like
> util-linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I believe this is caused by the loop label changes I backported, which
depend on fat and ntfs probing, which crashes for non 512 byte sector
size disks. I have backported the required changes to fix that and
sent the patch to Colin Watson to apply.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/29/2014 9:24 AM, Arthur Marsh wrote:
> (gpartedbin:11550): glibmm-CRITICAL **: unhandled exception (type
> Glib::Error) in signal handler: domain: g_convert_error code : 1
> what : Invalid byte sequence in conversion input
>
> The older gparte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/3/2014 6:34 PM, Jan Christoph Uhde wrote:
> Package: mount Version: 2.20.1-5.7 Severity: wishlist
>
> Dear Maintainer,
>
> it would be great if mount would provide some dummy mount options
> for systemd.
>
> mount -o systemdRequires= ...
>
> T
On 5/5/2014 1:01 PM, Jan Christoph Uhde wrote:
> Hey Phillip,
>
> would you please give me some documentation
> for reference. I could not find something
> about 'x-' on
>
> https://www.kernel.org/doc/Documentation/kernel-parameters.txt
> or
> man mount
>From man mount:
> x-*All options pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 8:18 AM, Arthur Marsh wrote:
> (gpartedbin:15278): glibmm-CRITICAL **: unhandled exception (type
> Glib::Error) in signal handler: domain: g_convert_error code : 1
> what : Invalid byte sequence in conversion input
>
> * What was the o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 10:08 AM, Arthur Marsh wrote:
> Is there any way to pinpoint where in the program the error is
> occuring?
Yes, if you can run it under gdb and set a breakpoint in g_log, that
is where these messages are printed. If you can capture a sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like the problem may have originated in one of the other
threads, and only is being displayed by the main thread. Could you
use the info threads command to list the other threads and use the
thread command to switch to each, and grab a bt the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 12:17 PM, Arthur Marsh wrote:
> (gdb) bt #0 0xb7fffa80 in __kernel_vsyscall () #1 0x4102dc5b in
> pthread_cond_wait@@GLIBC_2.3.2 () at
> ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
>
>
#2 0x413cd8e0 in g_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I thought of something else to try. Can you run it under gdb but
*without* setting a breakpoint? It seems this error should result in
the program terminating but you originally said it just hung, so the
question is whether gdb sees a SIGTRAP, and als
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/22/2014 1:34 PM, Arthur Marsh wrote:
> fsck.fat 3.0.26 (2014-03-07) Checking we can access the last sector
> of the filesystem Boot sector contents: System ID "MSWIN4.1" Media
> byte 0xf8 (hard disk) 512 bytes per logical sector 4096 bytes per
> c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ok, I have been able to reproduce this and diagnose the problem. Your "3 1/2
inch floppy link" file contains the "1/2" character, which in code page 437 (
the original IBM PC character set ) is 0xBD. In UTF-8, this is an incomplete
multi byte se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/27/2014 4:27 AM, Aurelien Jarno wrote:
> That is wrong. 0xBD in CP437 or CP850 page code is '╜' which
> corresponds to character U+255C as iconv says.
Not according to the table listed on
http://en.wikipedia.org/wiki/Code_page_437.
According to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/27/2014 10:05 AM, Phillip Susi wrote:
> On 5/27/2014 4:27 AM, Aurelien Jarno wrote:
>> That is wrong. 0xBD in CP437 or CP850 page code is '╜' which
>> corresponds to character U+255C as iconv says.
>
> Not a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure why this conversation got dragged over to the wrong bug
#, but I'm putting it back and closing it. I realized finally that I
was just looking at the table wrong and the value I was looking at was
in fact, the UTF-16 value for the characte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, now that I've gotten all of the confusion cleared up, fixing this
should be as simple as changing gparted to use LANG=C.UTF-8 rather
than LANG=C when running dosfsck. It seems that the former causes
dosfsck to disable its normally correct UTF-8 co
0
@@ -1,3 +1,11 @@
+multipath-tools (0.5.0-2) unstable; urgency=low
+
+ * Split kpartx initramfs bits part of multipath-tools-boot
+into kpartx-boot for dmraid
+ * Split kpartx out of multipth-tools-udeb into kpartx-udeb
+
+ -- Phillip Susi Mon, 09 Jun 2014 11:45:08 -0400
+
multipath-tools (0.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 3:52 AM, Guido Günther wrote:
| Do we really need a kpartx-boot for that? Wouldn't it be sufficient to
| split out kpartx and let the initramfs hooks of dmraid and mp handle
| the rest? I don't think there's a usecase yet where one wants
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 2:39 PM, Guido Günther wrote:
| MP needs the hook to update the initramfs but kpartx doesn't. So I
| think there should be a separate kpartx package, no kpartx-boot needed
| or am I missing something?
| -- Guido
dmraid needs the hook t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 748407 + fixed-upstream
retitle 748407 mount passes extended mount options to fuse
thanks
Confirmed, this is fixed by upgrading util-linux to 2.24.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/10/2014 4:09 PM, Guido Günther wrote:
| Doesn't dmraid need an initramfs hook by itself already?
| Cheers,
Hrm.. it does... I suppose it wouldn't hurt to duplicate the hooks code there,
so I guess you could drop the kpartx-boot part. Would you
.
=== modified file 'debian/changelog'
--- debian/changelog2014-03-09 16:52:09 +
+++ debian/changelog2014-06-11 14:05:33 +
@@ -1,3 +1,9 @@
+multipath-tools (0.5.0-2) unstable; urgency=low
+
+ * Split kpartx out of multipth-tools-udeb into kpartx-udeb
+
+ -- Phillip Susi Mon, 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: pbuilder
Version: 0.215
The default pbuilderrc file sets a keyring override when running
debootstrap which prevents it from honoring the keyring setting
specified in the suite script. This breaks the creation of a pbuilder
for ubuntu since t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/11/2014 05:16 PM, Thorsten Glaser wrote:
| Phillip Susi dixit:
|
|> specified in the suite script. This breaks the creation of a pbuilder
|> for ubuntu since the keyring is forced back to debian's.
|
| It doesn;t because you;re
would block out some paid time to do that so I have been waiting
for that for several weeks now.
On 6/12/2014 1:31 PM, Andreas Henriksson wrote:
> Hello Phillip Susi!
>
> While looking over bugs in the util-linux Debian package I noticed
> you've been active on the bug tria
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: ntfs-3g
Version: 1:2014.2.15AR.1-1
/bin/ntfsck ( not ntfsfix ) has no man page, nor does it provide usage
when invoked with -h, --help, or no arguments.
Some comments I found on the Internet indicate this is a long
abandoned program that is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/12/2014 9:34 AM, Colin Watson wrote:
> I think it would be very helpful to split up the logical chunks of
> this.
>
> Moving ext2 support means that we need to make sure that
> partman-basicfilesystems and partman-ext3 land in unstable and
> tes
* Remove check_swap, as there is no such thing as fscking swap
+ * Use dosfstools to format and check fat filesystems rather than
+libparted.
-- Phillip Susi Wed, 12 Feb 2014 15:56:24 -0500
diff --git a/debian/control b/debian/control
index f326b28..82f7288 100644
--- a/debian/control
is no
+longer supported in parted3.
+ * Remove check_swap, as there is no such thing as fscking swap
+
+ -- Phillip Susi Wed, 12 Feb 2014 15:56:24 -0500
+
partman-basicfilesystems (90) unstable; urgency=low
[ Updated translations ]
--
1.8.3.2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ian/changelog
index 8a8fc5b..16790bf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,7 @@ partman-basicfilesystems (91) UNRELEASED; urgency=low
* Remove check_swap, as there is no such thing as fscking swap
* Use dosfstools to format and check fat filesystems rather than
libparted.
+ * Use mke2fs instead of libparted
-- Phillip Susi Wed, 12 Feb 2014 15:56:24 -0500
--
1.8.3.2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
5268..edf0382 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+partman-efi (40) UNRELEASED; urgency=low
+
+ * Switch to using mkdosfs instead of libparted
+
+ -- Phillip Susi Fri, 14 Feb 2014 15:44:22 -0500
+
partman-efi (39) unstable; urgency=low
[ Updated translations ]
dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/16/2014 08:58 AM, David Suárez wrote:
> Hi,
>
> During a rebuild of all packages in sid, your package failed to
> build on amd64.
>
> On new readline versions old-style function typedefs have been
> deprecated.
Yes, this was recently fixed u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/16/2014 02:03 PM, Bjarni Ingi Gislason wrote:
> Source: util-linux Version: 2.24.1
There is no 2.24.1 in debian. Did you mean 2.20.1-5.6?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: ntfs-3g
Version: 1:2013.1.13AR.1-2
Running mkfs.ntfs -V exits with status 1 ( failure ).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBCgAGBQJTJ5l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Package: jfsutils
Version: 1.1.15-2.1
Running mkfs.jfs on a file issues an are you sure prompt. Redirecting
stdin to /dev/null should suppress this prompt but instead crashes
with SIGABRT.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 741992
thanks
> it is up to the invididual liking of upstreams if displaying help
> or version information exits with 0 and 1 in their programs,
> there's no consensus or standard.
No, it is not. The standard is that an exit status other than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/20/2014 1:22 PM, Daniel Baumann wrote:
> there's no standard saying that how --version should be handled,
> and thus this case is handled differently by every tool, there are
> many that return 0 but there as many that return 1.
The standard says
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/20/2014 3:35 PM, Daniel Baumann wrote:
> again, which "standard"? again, i'm not argueing about the non
> --version|--help|--usage and so on options, i only disagree for
> those 'special' options. so far, you're only claiming things
> without ref
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/23/2014 7:00 PM, Julian Gilbey wrote:
> OK, I've got one. I formatted a 2TB disk using cfdisk, and
> attached is what cfdisk reports.
Ok, so fdisk is correct here. Basically cfdisk is a long unmaintained
POS that you should not use until upstre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/24/2014 3:01 PM, Julian Gilbey wrote:
> OK thanks. But this then indicates that cfdisk should be removed
> entirely or replaced by a script which says "cfdisk has been
> removed due to it being unmaintained and error-ridden. Please use
> ... i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I recently ran into this myself. Wish I had checked the bug lists
before debugging and solving it myself. Can this patch get applied
already?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - htt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Were you running gparted on a loopback device, or directly on a file?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ9F7BAAoJEJrBOlT6nu75e5MH/R+41A8W55GgG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe parted has had full support for non 512 byte sectors for
some time now. Is there a reason this bug report should not be closed?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://ww
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/15/2013 2:43 PM, Steve Langasek wrote:
> They are mapped at runtime; essentially you would see /dev/sda1
> (/dev/sda3? whatever) as an alias to /dev/sda.
Linux won't allow this, so the best thing parted will be able to do is
ignore the partition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 475224 + moreinfo
thanks
What was the error you kept getting? Choosing cancel should have
stopped the command rather than keep going and reporting more errors.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/2013 02:33 PM, martin f krafft wrote:
> That is true. In my case, I need to add a drive to an existing
> RAID setup and unless I align the partition at 8k, I don't have
> enough blocks to join the RAID. That is because the RAID was
> created u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/20/2013 07:35 PM, Daniel Kahn Gillmor wrote:
> Package: parted Version: 2.3-11 Severity: normal
>
> (parted) print
> Backtrace has 14 calls on stack: 14:
> /lib/i386-linux-gnu/libparted.so.0(ped_assert+0x29) [0xb76912a9]
> 13: /lib/i386-linux-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2013 08:04 PM, Daniel Kahn Gillmor wrote:
> Assertion (head_size <= 63) at ../../../libparted/labels/dos.c:662
> in function probe_partition_for_geom() failed.
This bug has already been reported. It has been fixed in Ubuntu some
time ago and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 619330 + patch
thanks
This was fixed in Ubuntu by remove-dev_t-dep.patch, which should be
merged to debian.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why?
Parted already aligns partitions to 1 MiB by default, so it doesn't
really matter that WD's firmware fails to report the correct hw sector
size.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve, could you explain this a bit? How can overlapping partitions
not be an error? Is it something like extended partitions overlapping
logical partitions, but that's ok since the extended is just a
container and not mapped at runtime?
How can I r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The filesystem code was badly broken and so was removed from upstream
parted years ago, so this won't be fixed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 606168 + moreinfo
thanks
Is there a problem with the original disk, or only on the truncated image?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ7G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 469842 + moreinfo
thanks
This looks like it was just a corrupted filesystem. Are you still
able to reproduce this?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags 671293 + moreinfo
thanks
Presumably you will want to use the partition after creating it, for
instance, to mkfs on it, thus, it is a failure to not inform the
kernel of the changes.
The question is, why is it failing to inform the kernel? Would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: gparted
Version: 0.12.1-1
Users get a popup reporting internal errors/bugs relating to oddly
named raid arrays that do not exist. There was a module that probed
for mdadm devices by running mdadm --examine --scan to scan all disks
for raid me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/12/2013 08:05 AM, Andrew Buckeridge wrote:
> Parted expects protective MBR to have a single entry for GPT (the
> GPT itself contains the partitions). However, gptsync also has MBR
> point to partitions after the GPT. Note that partitions are off
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm confused. My understanding is that partman was already using
external utilities for everything besides fat, hfs, and ext2 resize,
and that there were already bug reports covering the lack of progress
indication with those. Parted3 appears to have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I have trouble believing that this is going to be easier than
> patching the most common utilities to add an option for a
> machine-readable progress indicator.
Not too long ago I was looking at patching gparted to support this and
while it did not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You have to use logical partitions. Deleting a logical partition
results in the remaining ones being renumbered, thus, the next time
you run parted, it checks the wrong partition number for being used.
Parted clearly tells you that you should reboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm pretty sure this was fixed *ages* ago and should be closed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ21Z5AAoJEJrBOlT6nu752nwIAIm6I1ey6mr6/hZtd5Pwq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like the problem here is that you specified that the
partition should run to the last sector ( -1s ), but this is not
possible with gpt since the backup copy is at the end of the disk.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (Min
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was fixed in Ubuntu with 16-dos-partitions.patch:
From: Phillip Susi
Subject: Fix > 16 dos partitions
Description: The msdos partition table claimed a maximum partition
count of 16 but would allow you to go beyond that. This resulted
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your partition table is corrupt, though parted should handle this a
little more gracefully.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ22PQAAoJEJrBOlT6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was fixed in Ubuntu with fix-head-size-assertion.patch which
should be backported to debian.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJQ22YuAAoJEJ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a bug in the kernel so should be reassigned to linux instead
of util-linux.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQo7iPAAoJEJrBOlT6nu75GioH+Q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/27/2012 6:35 AM, Eike wrote:
> Package: gparted Version: 0.12.1-1
>
> --- Please enter the report below this line. ---
>
> Hello!
>
> gparted doesn't start up for me as well. I'm using wheezy/sid,
> fresh installation.
>
> When I'm starting g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What kind of raid setup are you using, and are you still able to
reproduce this? If so, can you check the output of "ls /dev/sd*"
after running gparted?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is fixed in Ubuntu by fix-head-size-assertion.patch. Please
apply in debian.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPFeA+AAoJEJrBOlT6nu758QEH/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: wnpp
Severity: wishlist
Owner: Phillip Susi
* Package name: e2defrag
Version : 0.79
Upstream Author : Phillip Susi
* URL : http://launchpad.net/e2defrag
* License : GPL
Programming Lang: C
uthors and rotting
for many years. I have taken over maintainership of it and would like to get
it back into
the archive.
* Package name: e2defrag
Version : 0.80
Upstream Author : Phillip Susi
* URL : http://launchpad.net/e2defrag
* License : GPL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/23/2012 07:27 PM, Dmitrijs Ledkovs wrote:
> The ITP was not sent to the debian-devel mailing list. Please use
> report-bug in the future or add pseudo-header:
> X-Debbugs-CC: debian-de...@lists.debian.org
>
> Please forward your ITP to debian-de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 12:00 PM, Roger Leigh wrote:
> Have you taken over upstream maintainership as well?
Yes.
> This was always a tool which needed to be used with great caution,
> and was removed for good reason. Is this safe to use with all
> ext2, ext3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 05:25 PM, Eugene Paskevich wrote:
> I wasn't very cautious to preserve any data before or after the defrag,
> even more I've killed the file system already.
> Sorry, I won't be useful in debugging.
How about at least an overview of the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 04:36 PM, Eugene Paskevich wrote:
> Just my 2 cents...
> Tried to use it on my non-critical ext3 FS. The FS structure was corrupted,
> fsck recovered some data (about 1%) into lost+found, 80% of data is lost w/o
> any trace.
> Well, it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 07:40 PM, Dmitrijs Ledkovs wrote:
> Let me rephrase.
>
> Is upstream aware of the above bugs which affected the last version of
> defrag in debian, which were not fixed in the upstream code?
They appear to fall into 3 categories: ftbs,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/24/2012 07:41 PM, Dmitrijs Ledkovs wrote:
>> There is already an ext4-specific (depends on creation with -O extent)
>> e4defrag
>> tool in e2fsprogs since 1.42~WIP-2011-07-02-1. Is there a reason you would
>> use
>> one tool over the other?
>>
On 6/25/2012 4:25 AM, Dmitrijs Ledkovs wrote:
Your decision whether you upload into Debian experimental or unstable
should not be affected by other derivative distribution policies. You
can request syncing packages from experimental into Ubuntu, but the
package will still land in Ubuntu's new que
I found a bug that corrupted files with holes in them and am preparing
to upload a new release with the fix.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/11/2012 7:15 AM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Adding BIOS driver for this screws things up. And the scam is
> adding this to mobo features as a "RAID" and an attempt to make
> this pass as if it was a hardware RAID. GRUB currentl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/1/2012 6:41 PM, Filipus Klutiero wrote:
> Executing GParted by running gparted-pkexec in a console works,
> but there is interactivity due to a password request:
That's how it is supposed to work.
> Furthermore, the Debian menu item, which uses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/21/2012 08:50 PM, David Smith wrote:
> I can confirm this problem also exists on Debian Wheezy in KDE 4.8.4.. When
> I select "gparted" from the KDE menu, the "busy" cursor appears but gparted
> fails to start. When I go into the menu editor, fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/31/2013 4:17 PM, Marc Haber wrote:
> The following patch introduces an --include-early option which
> allows to introduce eatmydata early enough:
Is this intended to be applied instead of, or on top of my initial
patch? If the former ( which I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This was not fixed; the incorrect rule file is still in the debian
directory and being packaged, though the rule in the upstream sources
is correct. Probably should remove the rules file in the debian
directory and package the upstream one instead.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/23/2013 11:11 AM, Len Sorensen wrote:
> Package: parted Version: 2.3-12 Severity: normal Tags: upstream
>
> If you try to create a partition starting at 1MiB and ending at the
> end of the disk by doing:
>
> mkpart primary 1MiB -1s
>
> You can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/31/2013 11:46 AM, Colin Watson wrote:
> This would need to be reassigned to ftp.debian.org if you want it
> to happen; though it'd be good if the maintainer could confirm or
> deny it.
Yep, that's why I assigned it to the package first. Hopefull
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: preload
Version: 0.6.4-2
If preload fails to open its log file in preload_log_init(), it
crashes when calling g_logv(). This is easily replicated with a
read-only /var, or using the -l switch to redirect it to use a log
file somewhere you mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: debootstrap
Version: 1.0.46
Debootstrap is very, very slow. I watched a server install crawl by
for something like an hour at a rate of about 1 package per second. A
simple debootstrap chroot takes 10 minutes to setup, with a
predownloaded ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This simple two line patch does the trick:
- --- sid 2013-02-15 11:03:15.384977238 -0500
+++ sid.orig2013-02-15 10:50:23.381293976 -0500
@@ -16,7 +16,7 @@
esac
work_out_debs () {
- - required="$(get_debs Priority: required) eatmydata"
+
101 - 200 of 398 matches
Mail list logo
