Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - VastOne

Pages: [1] 2 3 ... 257
1
It only worked for me in V-Box by completely removing the drives in gparted and recreating them in gparted.. Once I did BOTH and only both then they both showed up

It kept failing if I did only one drive so if you are not in a V-Box make sure you have only what drive you want to use installed

This is the Ugly Stick approach to an install until this issue is resolved

Thanks RatMan for the feedback and help

2
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 18, 2019, 11:33:40 PM »
Nice 5.02 Kernel there Jedi...

Anyone heard anything about when it will hit Debian Repos?

4
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 18, 2019, 12:56:33 AM »
^ Yes Obi-Wan, Yes

5
On the python questions, I have no idea.. seems backwards compatibility has taken a backseat in the Debian world and seems more a question for the developers of the installer

mtools is stock installed in VSIDO

I am not sure on the gpt question, if I understand it all you would have to wipe everything to go to a gpt partition table so if you have to do the same with an msdos table, why would you?  As to if I am missing a msdos partition table, these machines and V-Box setup have always had the exact same msdos partition tables from the beginning...

The solution (create a msdos partition table while in LiveCD) seems as if that is the issue, but how is that possible if there always was a partition table and the April 2018 ISO's no doubt see the partitions and partition table

 ??? ??? ???

6
This is the complete error when trying to install.. Note that it is a call from python 2.7 to the python parted partition script

Code: [Select]
File "/usr/share/linstaller/linstaller/modules/partdisks/front/glade/__init__.py", line 2643, in manual_frame_creator
    elif name and part.name:
  File "/usr/lib/python2.7/dist-packages/parted/partition.py", line 135, in get_name
    return self.getPedPartition().get_name()
_ped.PartitionException: msdos disk labels do not support partition names.

7
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 02:23:03 PM »
I am saying I have what I need to check on build levels and nothing new has happened in development..

Sorry for the mass confusion

In the end I think this is a kernel issue but I cannot confirm it yet

8
Nothing new with the installer development at all.. I am stuck back at square one as to why or how this is possible or to fix

'I threw my hands in the air and said show me something'

Rihanna - Stay


9
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 02:17:47 PM »
I ended up  having the files after all and they have not changed

10
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 02:16:59 PM »
See my edit please.. 

11
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 01:59:24 PM »
EDITED

It doesn't matter at this point anyway filip.. nothing has changed in the installer that would address the issue we are having covered here where no drives are showing up to be installed to in the gparted section unless you completely wipe everything before installing

12
How To's / Re: How To: Building the VSIDO Installer
« on: March 16, 2019, 12:10:49 PM »
Hey Filip I hope all is well with you

I am getting the following error trying to build the latest

Code: [Select]
dpkg-buildpackage -uc -us
dpkg-buildpackage: error: cannot open file debian/changelog: No such file or directory

It looks like it may be due to Debian changing it's folder names from debian to debianpkg?

Just spitballing, I am not sure and Google isn't much help

Thanks

13
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 16, 2019, 01:32:23 AM »
Great looking enviros Jedi and RatMan

14
I believe there will be an update to the installer that has this resolved and I will dig into that this weekend

15
Success but at a price


 


Was able to install after I completely wiped both drives on the V-Box setup

So in order to install VSIDO you have to destroy everything?

Nahhhhh

There has to be a better solution...

Pages: [1] 2 3 ... 257