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 ... 254
General Support / Re: 10 gig log files
« on: April 19, 2018, 02:43:09 PM »
Seems to have been a one off.. I cannot reproduce this again... very strange, but that's the life of SID

General Support / 10 gig log files
« on: April 19, 2018, 01:57:39 AM »
My syslog and daemon.log both grew to 10 gig a piece and basically froze me out of a log in due to the file system running out of space.. after I cleared the logs I could get back in.. Both were too big to open with any editor (TWSS) so I have no idea what caused it.. This is a new install (reinstall) of the build system that had only been up for a day.. I am going to log back in and see if they begin to grow again, but so far they have not and I am at a loss.. never have I seen anything remotely close to this one.. On searches for solutions on google, there have been many instances of the syslog and kernel.log growing and on most there seemed to be an SSD involved which is what I am installed on

Any ideas?

Artwork & Screenshots / Re: April 2018 screenshot thread
« on: April 16, 2018, 06:08:04 PM »
Definitely a rescue club..  ::)

Artwork & Screenshots / Re: April 2018 screenshot thread
« on: April 14, 2018, 01:51:39 PM »
Simple VSIDO Fluxbox


Conky / Re: conky - Gmail new email information (bash version)
« on: April 07, 2018, 02:16:43 AM »
I built it using your github page here

I also had to:

Code: [Select]
sudo apt-get install build-essentials libcurl4-openssl-dev
Very clean and nice app, thank you!

One should also know that the ACC needed is just the name.. NOT the included

VSIDO Discussions / Re: Debian Bullshit
« on: March 25, 2018, 04:32:46 AM »
It was a mess.. it took several removals and the right sequence to first uninstall and then reinstall them in a specific order..

Here is what is interesting... When I put the dmo repo back, the 3 files that were the issue were updated from that dmo repo.. and in the process 15MiB of data was freed.. I can live with a repo that provides the same (and most time better files) AND cuts the debian cruft out .. I like that a lot

In the end, VSIDO and people who use the dmo wins

VSIDO Discussions / Re: Debian Bullshit
« on: March 25, 2018, 04:23:35 AM »
Thanks DeepDayze.. it turned out to be a patience issue on my part.. If I had waited one day the DMO side would have caught up to the Debian Sid repos and all would have been fine.. I know these things happen time to time as we live on the edge and I completely understand it

It is fixed and the DMO repos are now back in the builds

What pissed me off was as the end user being told I was basically an idiot for using anything other than PURE DEBIAN

Just old bullshit.. tiresome and unnecessary.. It could easily be the way the developer communicates..

Artwork & Screenshots / Re: March 2018 Screenshot Thread
« on: March 23, 2018, 11:11:55 PM »
^ As always it looks epic Jedi..

Glad to see you on your feet, out and about and getting healthy

How To's / Re: How To: Building the VSIDO Installer
« on: March 23, 2018, 10:46:34 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

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

How To's / Re: How To: Building the VSIDO Installer
« on: March 22, 2018, 10:21:55 PM »
I did everything exactly as you did in git, the build and made sure it was 6.0.3 in the build..

Code: [Select]
apt-cache policy keeptalking
clearly shows 6.0.3~trios1 is installed in the build and in the installs

git branch = trios-master and the grep output is exactly the same:

Code: [Select]
grep cns11643 ./keeptalking/Locale/
if "translit" in _file or "iso14651_t1" in _file or "POSIX" in _file or "cns11643_stroke" in _file: continue

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 file

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

This is a strange one.. I'm not sure what has happened but it has...  ::)

  • Corrected an issue with the installer with the help of Filip. Removed dependencies on Debian-MultiMedia repo
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

Artwork & Screenshots / Re: March 2018 Screenshot Thread
« on: March 21, 2018, 02:43:54 AM »
ISO's built, tested and uploading

Still 2:30 for an install.. impressive


VSIDO Discussions / Debian Bullshit
« on: March 21, 2018, 01:55:54 AM »
So I filed this bug report today

Straight forward, an update killed the ability to run any kind of apt-get update, dist-upgrade or install of any kind.. apt was broken

The response and closing of the bug makes it pretty clear where Debian is still stuck up their own asses

That's because you use packages from Debian Multimedia (dmo), which
breaks the dependency/file replacement resolution process of apt by
unnecessarily increasing the version number (1:1.12 > 1.14).

I resolved it by pretty much eliminating the multimedia repos and reinstalled the gstreamer stuff from SID

It did not sit well with me today... I never have understood the need to place blame on the end user when reporting an obvious bug

How To's / Re: How To: Building the VSIDO Installer
« on: March 20, 2018, 10:41:11 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/ 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 file and added the changes, rebuilt the ISO and it the install worked flawlessly

Need anything else, please let me know

How To's / Re: How To: Building the VSIDO Installer
« on: March 19, 2018, 08:20:54 PM »
I rebuilt today and the same issue is there.. I have uploaded that ISO as well

Pages: [1] 2 3 ... 254