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 - filip

Pages: [1] 2 3 ... 5
1
Hey, sorry for being MIA, had really no time to look further into the issue(s)... Hopefully this weekend I'll be able to dig into it :)

Regarding udev thing, looks to me it's either due to lvm, udev or grub itself.

Found another report here: https://forums.kali.org/showthread.php?38315-Problems-Dual-Booting-Kali-Linux-with-Windows-10-(No-signs-of-GRUB-bootloader)&p=75818

If you have time/make it before I do, it'd be good to at least eliminate grub by reinstalling it manually from an already installed system followed from live as well.Just do the usual mantra:
Code: [Select]
# live only: 
# mount the root partition at /mnt and then:
mount --bind /dev /mnt/devmount --bind /sys /mnt/sysmount --bind /proc /mnt/proc
# /live only


grub-install --recheck /dev/sdX #for BIOS, adapt for UEFI as usual
update-grub
If you don't get the timeouts, then it's probably not a grub issue :)


2
Code: [Select]
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000000 microseconds
Seems to be a grub/lvmetad issue. Is that on UEFI or regular BIOS?
If UEFI, there's a slight possibility that it's the GRUB complaining due to missing parameter for efi dir. I'll look into it...

https://bbs.archlinux.org/viewtopic.php?id=242689
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918590



@BIOS ISO installer crash:

Judging by the log, it can't find the squashfs image... Something is either wrong with the latest ISO or something changed with the live-build (or the buildsystem vsido uses), since the 17th March ISO does have:
Code: [Select]
/lib/live/mount/medium/live/filesystem.squashfswhile the 20th March one does not (thus the crash --> installer can't find the image to extract/unsquash). :)

3
I have little time to investigate what's the difference between partition label and partition name (since msdos disks obviously do support labels, so wtf!?) together with what changed in Debian that suddenly made this an issue.
So I've just taken a blunt approach and made the installer check if labels are supported, before trying to populate the UI with them.

See here: https://gitlab.com/Cofi/trios-installer/commit/90310e899dab429d5c62a95a10e92898225ae434

So the biggest potential "issue" if I got it wrong is that the labels won't show in the UI when they are actually supported.
If I get some time later today I'll go through the install fully (by mistake I booted into a VM I need/cannot format the disk), and burn the ISO on the flash and check it out on the metal... Right now it doesn't get stuck on the partition list screen.
With that said, until I get to it, I suggest testing in a VM only, just in case  :) Also, as usual, the fix is in the "testing" branch, so make sure you build the installer from it :)

4
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 02:21:03 PM »
I ended up  having the files after all and they have not changed
I'm not sure what are you saying? It builds now? :)
@EDIT:
I've looked at the posts about april ISO... Anyway, can't tell you much until I take a look in the VM. Will get back when I do :)

5
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 02:15:42 PM »
No "debian"  dir there. Maybe something went sideways with the "git clone" or you forgot to switch to "trios-master" branch?? :)

6
How To's / Re: How To: Building the VSIDO Installer
« on: March 17, 2019, 01:44:01 PM »
Hey,

Oh yeah, still kicking   8) ;D Albeit very little in the foss world :(

I'll try it out in a VM tonight/tomorrow, but before that, are you sure that you're in the right directory? That error usually comes out if your current dir is not one above "debian".
If the dir is correct, please post the "ls -la" output from there.


Didn't hear anything about "debian --> debianpkg", Google finds nothing, but anyway I doubt they'd make such a profound change now that the Buster freeze is ongoing.Which btw, has the coolest name so far  ;D


Cheers


7
How To's / Re: How To: Building the VSIDO Installer
« on: March 24, 2018, 06:51:19 PM »
^ Thanks man.. sorry I missed that on the earlier post... and all those deb files are there I just saw the first keeptalking deb and installed that and never looked past my mistake

Sorry that I was so obtuse Filip.. I appreciate your help on this
No problem at all!  :)

It's funny how most issues are staring you right in the face and you don't see them

I´d say it´s not much of a problem per se, however the frequency at which it occurs.....  :D ;D

8
How To's / Re: How To: Building the VSIDO Installer
« on: March 23, 2018, 01:45:14 PM »
I have attached the built .deb file created and what I used ... in looking at the included file keeptalking_6.0.3~trios1_all.deb (in gdebi and xarchiver) I do NOT see a Locale directory or the __init__.py file

I have also attached the keeptalking_6.0.3~trios1.tar.xz file and this DOES have the Locale directory and the __init__.py file

This is a strange one.. I'm not sure what has happened but it has...  ::)
Keeptalking source produces three packages, "keeptalking", "python-keeptalking" and "python-t9n":
Code: [Select]
[filip@stretch-K10][/tmp/keeptalking]$ ls ../ | grep .deb
keeptalking_6.0.3~trios1_all.deb
python-keeptalking_6.0.3~trios1_all.deb
python-t9n_6.0.3~trios1_all.deb
And "/Locale/__init__.py" belongs in the "python-keeptalking".  ;)
Thus, you need all three installed and at the same version. I'd bet that "apt-cache policy python-keeptalking" shows it's an older version compared to "keeptalking"!?

Like I've said previously, "keeptalking" should really have versioned depends on the other two, so apt would complain if there's a version mismatch between any of them.
In other words, if you have "python-keeptalking" v=6.0.0 installed, and try to update only "keeptalking" to v=6.0.3 apt would complain and requre you to update "python-keeptalking" and "python-t9n" to v=6.0.3 as well.

Anyhow that's fixed in latest git (v=6.0.3~trios2).  :)

So, clone --> dpkg-buildpackage and then:
Code: [Select]
cd ../ && sudo apt install ./keeptalking_6.0.3~trios2_all.deb ./python-keeptalking_6.0.3~trios2_all.deb ./python-t9n_6.0.3~trios2_all.deb

9
How To's / Re: How To: Building the VSIDO Installer
« on: March 22, 2018, 07:13:08 PM »
Hi Filip..  There seems to be issues with the 6.0.3 version of the keeptalking.. I built it and installed it with no issues but had the same results on the first build of the ISO.  I confirmed from that livcd session that the keeptalking/Locale/__init__.py had the original and did not have the fix:

Code: [Select]
if "translit" in _file or "iso14651_t1" in _file or "POSIX" in _file or "cns11643_stroke" in _file: continue
I then checked it also in the build environment and confirmed that both 6.0.3 was installed and the fix was not there either

I manually edited the __init__.py file and added the changes, rebuilt the ISO and it the install worked flawlessly

Need anything else, please let me know
It's most likely has something to do with the way you cloned git/built the package. I've just tested with the fresh clone, and the package (python-keeptalking) has the latest __init.py__ in question.

Steps I've followed ( on Stretch though, the issue you're having might also be Sid related ):
Code: [Select]
git clone https://gitlab.com/Cofi/keeptalking.git && cd keeptalking
Verify that we're on "trios-master" branch:
Code: [Select]
git branch  #should output: "* trios-master"
Double check the fix:
Code: [Select]
grep cns11643 ./keeptalking/Locale/__init__.py
#output:                  if "translit" in _file or "iso14651_t1" in _file or "POSIX" in _file or "cns11643_stroke" in _file: continue

Build:
Code: [Select]
dpkg-buildpackage -uc -us
Result (gdebi):
 

 :)

Also, do make sure that you actually included the 6.0.3 version of the "python-keeptalking" package in the ISO.
The reason I'm even mentioning this is that "keeptalking" package doesn't have versioned dependency on it, so you could install new "keeptalking" and keep the old "python-keeptalking" without apt complaining ( I should really fix this  :D )...
 

10
How To's / Re: How To: Building the VSIDO Installer
« on: March 20, 2018, 04:12:01 PM »
Meh, got it.  8) 
"/usr/share/i18n/cns11643_stroke" file appeared probably recently in Sid, causing "keeptalking" to stumble over it. It is now properly ignored, so the issue should be fixed.
All you need to do is build the updated "keeptalking" package(s), version 6.0.3~trios1, using the usual mantra, git clone --> dpkg-buildpackage...
https://gitlab.com/Cofi/keeptalking

11
How To's / Re: How To: Building the VSIDO Installer
« on: March 20, 2018, 03:35:43 PM »
"Keeptalking" module is at blame here.
Something is going wrong with locale list building. Probably something changed in Sid/locales making the keeptalking parser read garbage/lock itself in an endless loop.

I'll resume hunting tonight, hopefully having it by the head by the end of the day.  :)

12
How To's / Re: How To: Building the VSIDO Installer
« on: March 19, 2018, 03:24:49 PM »
From terminal the only thing showing is

Code: [Select]
REBUILDING LOCALE MODEL
Hmm, it's unusual for Python not to output any error(s), so it may actualy be somewhere outside...
But anyhow, it would be most helpful if you could upload the latest build/ISO somewhere for me to download and see what's up!?
Updating the live system is a pain and likely won't produce the same environment as the prebuilt one. :)

13
Hey filip...

On the first pass that seems to be the fix... testing the rest now

Thanks for the heads up!

Cheers!
Well, for a change, I guess it was ´bout time for an easy fix...  ::) ;D

The solution to this was installing python-debconf

The split broke python3-debconf which had already been installed and used since the beginning of VSIDO

Why the dev would not take into account both needs and make one or both a dependency is beyond me...

Laziness?

Thanks again to filip for the help
No idea, though the split seems uneccessary to me. After all, both packages install the very same "debconf.py" ( it´s compatible with both Py´s ), just to different locations...
Perhaps they wanted to drop Python dependencies from "debconf" package...  ::)

You´re welcome, anytime!  :)

14
I´m away from any PC running Debian ( including my own ), so going blind here.

There was a recent split of debconf package into Py2 & Py3 versions ( changelog ) so it´s most likely related to that.
Either the module was renamed ( thus the "import" fails ), or the package itself is not installed.

Hopefully:
Code: [Select]
apt install python-debconf... will fix the issue.  :)

15
General Support / Re: SpaceFM freezes
« on: July 21, 2017, 11:46:51 PM »
Thanks filip for that info.. have you tried SpaceFM-NG?
Yep, like I've said above, been running GTK2 build without any issues.  :)
Code: [Select]
[filip@stretch-K10][~]$ apt-cache policy spacefm && echo "" && ls -lh /var/lib/dpkg/info/spacefm.list
spacefm:
  Installed: 1.0.6
  Candidate: 1.0.6
  Version table:
 *** 1.0.6 100
        100 /var/lib/dpkg/status
     1.0.5-2 500
        500 http://httpredir.debian.org/debian stretch/main amd64 Packages

-rw-r--r-- 1 root root 4,7K Feb 16 16:09 /var/lib/dpkg/info/spacefm.list
                            ^^^^^^
Quote
IgnorantGuru is one of the best individuals I have had the pleasure knowing in this small FOSS community we all share

I couldn't agree more!
Too bad he stopped working on SpaceFM, though he's been on hiatus before ( keep the hope alive, eh ), and ofc there's the fork now... :)  :D

Pages: [1] 2 3 ... 5