Hugh McMaster writes:
> I didn't see a need to build-depend on libpolkit-gobject-1-dev, but
> I'm not overly familiar with gparted's requirements.
I think something changed in 1.5 that made it require a file that moved
to this package in trixie, so I had to add it to get it to build.
>
Hugh McMaster writes:
> Control: tags 1025568 + patch
> Control: tags 1025568 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for gparted (versioned as 1.3.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
I have an upload of 1.5 pending
Control: tag -1 pending
Hello,
Bug #1025568 in gparted reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: reopen -1
Ivo De Decker writes:
> This new upstream version doesn't remove the code masking the systemd units.
> It just changes it a little. So it doesn't fix this bug.
Woops... you're right.
John Paul Adrian Glaubitz writes:
> Hello!
>
> It looks like this particular issue has been fixed in gparted 1.2.0 which
> was just released a few days ago [1]:
>
>> - Don't try to mask non-existent Systemd \xe2\x97\x8f.service (#129, !64)
>
> Might be an idea to update gparted to version 1.2.0
Just wanted to note in this copy of the bug that the recommendation from
upstream systemd was that gparted should not be masking mounts but
instead should take a bsd lock on the device to prevent auto mounts.
Kyle B writes:
> (gpartedbin:11049): Gtk-WARNING **: 09:04:39.901: cannot open display:
What display server / desktop environment are you using?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/11/2016 02:13 PM, Mattia Rizzolo wrote:
> On Mon, Apr 11, 2016 at 11:52:32AM -0600, Curtis Gedak wrote:
>> If I recall correctly, libparted was not able to handle when
>> there was only one unallocated sector between logical partitions
>> (it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/22/2015 09:19 PM, Michael Biebl wrote:
>> Why? The BTS forwards the message automatically doesn't it?
>>
> No it doesn't.
Sigh... that's another absurd failling in debian bts that requires
constant workarounds... added to my list.
> And I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: reopen -1
On 12/22/2015 08:11 PM, Michael Biebl wrote:
> First, please CC the package when you re-assign a bug report.
Why? The BTS forwards the message automatically doesn't it?
> Second, please don't use inflated severities. Third,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: reopen -1
Control: affects -1 gparted
On Tue, 22 Dec 2015 19:29:39 +0530 =?UTF-> > And that's why udisks2
has a Recommends policykit-1.
>>
>> Closing the bug report.
>>
>> Not installing recommends means you need to know what you are
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: reassign -1 udisks2
On 12/21/2015 03:54 PM, shirish शिरीष wrote:
> Yup,
>
> get it here -
>
> [$] sudo /usr/lib/udisks2/udisks2-inhibit true [sudo] password for
> shirish: /var/lib/polkit-1/localauthority/90-mandatory.d does not
> exist.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/08/2015 04:49 AM, shirish शिरीष wrote:
> You would have to share the whole command, because I'm not so
> familiar with udisks2-inhibit. I tried to see if there was a
> manpage or something but came up nada :(
/usr/lib/udisks2/udisks2-inhibit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/07/2015 11:57 AM, shirish शिरीष wrote:
> Yup, have udisks2 installed.
Just to confirm, can you run /usr/lib/udisks2/udisks2-inhibit and
verify that you get that error?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/19/2015 2:24 PM, jnqnfe wrote:
Firstly, I am not running fdisk or parted on the raw member disks,
I am simply running generic 'fdisk -l' and 'parted -l' commands,
which return information about all disks. To simplify matters I
removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/20/2015 12:17 PM, jnqnfe wrote:
What? I very carefully went through every one of them before
sending to ensure that only information about the array (md126) and
the array members (sdb and sdc) were included. I have just checked
back over
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/18/2015 4:05 PM, jnqnfe wrote:
Background = I have a 'fake-raid' RAID0 array,
created from two HDDs using my motherboard firmware. This is not
used for root, just data.
FYI, unless you have to dual boot with windows, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/18/2015 05:15 PM, jnqnfe wrote:
Then you need to only manipulate md126 and ignore sdb and sdc.
Most of what you seem to be reporting involves looking directly
at the individual disks, which you must not do as that will
present a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/17/2014 6:27 PM, Daniel Baumann wrote:
On 12/17/14 23:50, Andreas Henriksson wrote:
I'd guess (without having looked) because live-tools diverts
update-initramfs?
no, it's about uptime.
What?
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't quite understand what's happening in this bug. How do we get
from calling update-initramfs to an error trying to execute
update-initramfs.orig.initramfs-tools instead?
For that matter, instead of directly executing update-initramfs,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/27/2014 7:49 PM, Colin Watson wrote:
It does? linux_open appears to just open read-write, and only
falls back to read-only if a read-write mount fails. I can't find
anything special that arranges to do read-only mounts when write
support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/19/2014 4:21 PM, Steven Chamberlain wrote:
snip
* opening O_RDWR and closing a disk device on FreeBSD, causes its
partition tables to be rescanned (so, a 'commit' is implied - this
also seems to be the cause of major slowness of partman in
-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: 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It also depends on ufsutils-udeb, which is only built on kfreebsd. It
seems to me that this package needs changed from all to kfreebsd only.
This prevents building d-i monolithic images.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You install grub to the disks, not the raid array. dpkg-reconfigure grub-pc
should have all of your disks checked, or at least the one your bios boots from.
I believe this can be closed as NOTABUG.
-BEGIN PGP SIGNATURE-
Version: GnuPG
-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
27 matches
Mail list logo
