Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[caitlyn]

-  The package for 5.8.6 should've NEVER made it to the repo. It should be somewhere in a /veclinux-5.8.6-SOHO/packages/ (or something similar) directory, but that doesn't exist?? You repo guys aren't just putting the 5.8.6 packages inside the 5.8 SOHO or even the 5.8 standard repo's now are you? This way we could loose the original packages that were in there and have them be replaced by faulty ones (like this one).

- Why on earth wasn't this package built on a clean install of standard so everybody can enjoy it?

iu
I made precisely the same argument on the Packager's Board and was told that 5.8.6 was built mostly out of packages already in the 5.8 repository.  I was told that separate repositories weren't necessary.

The fact is that a lot of packages needed to be rebuilt to accommodate the new file structure used by X.org 7.x and Slackware 12.  Unless each and every one of these packages was tested against 5.8 Standard and SOHO the result we are seeing was inevitable.  This weekend I rebuilt two 5.8 font packages that were still in testing but I also tested the rebuilt versions against clean 5.8 builds.  I have several more packages I built that should get this treatment rather than depending on the symlinks for /usr/X11R6 that have been added to 5.8.6.

There is another issue:  Packagers now need THREE clean installs of VL in addition to their working/production updated VL install in order to do proper testing against 5.8 Standard, 5.8 SOHO, and 5.8.6 SOHO.  Also remember that 5.8.6 Standard is on the way.

Since 5.8.6 is still beta it's not too late for the developers and repository maintainers to change their minds and start new repositories and issue a new /etc/slapt-get/slapt-getrc file for VL 5.8.6 SOHO RC2.

[easuter]

I was told that separate repositories weren't necessary.

Yes, but only as long as all packages are built on VL 5.8 Standard.

Anything else will require a new repo... 

[caitlyn]

It's not just the Pidgin packages that Headacher referred to.  We've seen several others, haven't we?  Isn't this how a broken abiword-plugins package ended up in the repository?  (See: http://www.vectorlinux.com/forum2/index.php?topic=3699.0]]http://www.vectorlinux.com/forum2/index.php?topic=3699.0)  Isn't this why you (eauster) have been fixing a broken dillo package?

[easuter]

Well, the big problem in this particular case is that someone (ie: not me) has been adding packages directly into the main repositories without passing them through testing first 

Had they been announced/tested according to the repo maintenance rules layed out by JohnB316 all these cases would have been caught right from the start...

[blurymind]

well, i will wait for the full slack12 upgrade to come to vector and then upgrade myslef. 

[Dweeberkitty]

well, i will wait for the full slack12 upgrade to come to vector and then upgrade myslef. 

By then Slack 13 will probably be out. 

[rbistolfi]

I recently installed vl 5.8 std on an old box with a small hd. In the install process I choosed to not install x, to save the space of xfce, since it cant run on 64mb of ram. The owner of the machine still wants a desktop so I installed X and JWM with slapt-get, with no much hopeness. The X init scripts depends on xfce and the x server is too much for me to configure so I made a work around just upgrading the hd. I just wanted to share the experience  I am already reading the LFS book and some inet docs to understand the problem more deeply. I think there is an option in vasm to change the default desktop, may be is a way to fix this.
May be a separated option for X and the desktops can be done to make the installer more flexible. I see the x init files are now in the x11 package and needs to be hacked for the desired desktop, so looks like this has not a quick solution. I dont know if this can be done in any way, and if it is useful or desirable to change the way it works now.
Please note this is not a request, I just want to share the experience and bring the subject in to the consideration of the forum

[blurymind]

well, i will wait for the full slack12 upgrade to come to vector and then upgrade myslef. 

By then Slack 13 will probably be out. 

if i only knew the tune-up secrets the vec devs had made to this baby, i'd download slack 12 and make it work as much as possible like vector. I'll even try to install it some of vector linux's utilities. 

[uelsk8s]

blurymind,
you can get the VL version of slack12 here http://vectorlinux.osuosl.org/Uelsk8s/VL6.0-Pseudo-0.7.iso
the installer is quite ugly and slow but the installed system is pretty good.

uelsk8s

[blurymind]

blurymind,
you can get the VL version of slack12 here http://vectorlinux.osuosl.org/Uelsk8s/VL6.0-Pseudo-0.7.iso
the installer is quite ugly and slow but the installed system is pretty good.

uelsk8s

thank you. I am gonna test drive it tomorow at the laptop (i am still not willing to risk my main machine). what do you mean by ugly and slow? Does it have serious issues that i should be aware of? Please,pm if there are any... Its using the new gui installer? It would be nice if the future release has a gui installer,but also the option to use vl's good old non gui installer..

Also, can i be of any help by reporting bugs or building packages,or is it too early for that? ( i would like to build specially for the fully upgraded vl)

when i get free of work at the end of this month,i'll try my best to help out in any way possible.

[Joe1962]

Its using the new gui installer?

No, that's still at an early stage, though it's currently being worked on enthusiastically by several of our resident gambasians.

[blurymind]

Its using the new gui installer?

No, that's still at an early stage, though it's currently being worked on enthusiastically by several of our resident gambasians.

I recently started reading the gambas ebook that i found in eulsk8s' ftp where the pseudo vec6 is..I must say it amused me enough to get me started on something simple and nice. If i need help,i might try to pester some of the gambasians at the irc (ofcourse after asking google) 

[incognu]

There's a recent post about KDE packages, and given KDE 4 is on the way, it would be cool to synchronize the release of KDE4 with a VL release (maybe a 5.9.x?).

Don't you think we should at least wait for 4.0.2? AFAICT, this is a very major rewrite of KDE, bound to be buggy at first.

Just saw that the 4.0.0 release has been delayed:

We, The Release Team, hereby announce that we are extending the
KDE 4.0.0 schedule [1] 2 months by inserting an extra 2 Betas, as follows:

September 24: Beta3
October 22: Beta4
November 19: Total Release Freeze
November 21: RC1
December 5: RC2
December 20: 4.0.0 tagged

We feel that there are crucial elements of the release that need more
development time.  The feature freeze (less exemptions) remains in effect.

As usual, the dates are estimates and are subject to change.

http://lists.kde.org/?l=kde-devel&m=118856887429944&w=2

Not to be a wet blanket, but nothing I've read lately has changed my mind:  I still think we should hold off on 4 for a bit.

[easuter]

Well, seeing the path that the VL development is taking (holding off VL 6.0 and continuing the VL 5.8 series) KDE 4 may just be mature enough by the time VL 6.0 SOHO is released.
But even then, there will most certainly still be a fair amount of bugs to be ironed out....

[easuter]

On the subject of packages for VL 6.0, shouldn't the release tags be 1vl60 and not 1vl59? Otherwise when the final VL 6.0 goes gold, then there will probably still be packages shipped with vl59 release tags. Dunno if keeping the release tags as uniform as possible is important or not...