(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 30 Sep 2020, 04:42
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy
Moderators: Flash, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 259 of 283 [4236 Posts]   Goto page: Previous 1, 2, 3, ..., 257, 258, 259, 260, 261, ..., 281, 282, 283 Next
Author Message
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Thu 20 Nov 2014, 14:10    Post subject:  

Hi Toni,
Quote:
Me too Smile Just posting the problems I see now in case I forget them later.
Quote:
Sorry,I may have lost track on this, you think of making a package for gsu or gsudo and create maybe symlink to gksu?

I'm not sure yet what is the best option. Maybe adding official gksu dependency in DebianDog packages but then we need to add in status and available the information gsu provides gksu. Still inside every package that needs gsu we need to add symlink gsu pointing to gksu. Then for new packages we can use gsu=gksu if gksu is installed. Let me think a little bit more about this and I will make a suggestion.


It seems like you have more view on this matter than me.
But tell me if I can change the gsudo script, for example to basically something like:
If yad is installed then use yad, else use zenity if installed, if not, use gxmessage or (maybe even better) gtkdialog.

Quote:
I think the best way to go here is to make deb package with portable zenity and add new zenity version as conflicting package. Then installing the new one will uninstall portable zenity.


Yes, I will make it, can you put it on the changes list?

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Thu 20 Nov 2014, 16:51    Post subject:  

Hi, Fred.

Zenity deb package change included in next version fixes post.

The problem with gsu and other packages containing gsu line could be solved easy by changing gsu to gksu (or adding extra gksu line in case gsu is missing). But we have mirrored many old iso versions and this will make the new packages from section included incompatible with some of the previous DebianDog versions. But I'm sure we will find a way to fix this properly for the next update.

BTW I'm adding in fixes post again apt-get upgrade. I see wget is upgradable already and maybe other programs will need security updates too.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Fri 21 Nov 2014, 06:27    Post subject:  

Hi Toni,

Here's attached: different ktsuss, compiled with sudo enabled so it will work for user password.
The gsu script needs then changed to:
Code:
ktsuss -u root -m "Enter password for $USER" "$@"


Perhaps this helps solving the problem.

Edit: Removed attachment ktsuss-sudo, as it's really not working as expected.

Fred

Last edited by fredx181 on Mon 29 Dec 2014, 17:58; edited 2 times in total
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Fri 21 Nov 2014, 07:54    Post subject:  

fredx181 wrote:
Here's attached: different ktsuss, compiled with sudo enabled so it will work for user password.

Thank you, Fred, I will test it.

But I do not think it will solve the problem. Instead yad we will need available for reintsalling moded ktsuss and it must conflict with official debian ktsuss package. i think it is better to keep yad as dependency. it is already uploaded in section included on the site and if we make official DebianDog repository yad will be available there.

The main problem as I see it is adding gsu in the scripts and gsu is not available command in debian. We can change it to gksu in all scripts and create gksu package that conflicts with official debian gksu, but this will make the included packages (after we mod them) incompatible with previous DebianDog versions. And seems we have many old versions available for download (not only in my google-drive) here, here and here for example. We have also DevilDog that depends on DebianDog iso as a base and we could break something there changing already existing scripts.

For me the safe way is to keep the included packages and scripts in /opt/bin and to add symlink to /usr/local/bin line in postinst script only in the packages for reinstalling and mod them to prevent conflicts + adding all needed dependencies.

I'm testing some options here but it is too early to say it is the best way to fix the problem:
http://smokey01.com/saintless/DebianDog/Packages/Testing/tmp/
The gsu package for example contains yad dependency and creates symlink /opt/bin/gsu to /usr/local/bin/gsu. The gsu package does not conflict with gksu and both can be installed.
Yad is uploaded in section included and if we make it official DebianDog repository it will be added in sources list. The same can be done in standard Debian and yad and gsu will be installable with apt-get.
If gsu is installed it will create link /usr/local/bin/gsu pointing to /opt/bin/gsu
If other package (sfs-gets-smokey-get for example) is installed it has line in postinst to check for /usr/bin/gksu and if it is available will link it to /usr/local/bin/gsu. The package also contains dependency gsu or gksu. If gksu is already installed it will not install gsu but only create gksu symlink /usr/local/bin/gsu
We can use this method for the included packages but for not-yet-included and new packages we can change the location from /opt/bin to /usr/local/bin and even change the gsu line to search also gksu if gsu is not installed. Maybe we can also change the included scripts with gsu line to search for gksu also if it is available and this could prevent better some incompatibility troubles with old DebianDog versions but I'm not sure about this yet.

Edit: Maybe it seems not very important issue and we can continue further as it is, but this problem reminds me the multiuser and wrong permissions problem we had in the past. If we fix it now and make new DebianDog packages properly - the development will be much easier in the future.

Edit2: I'm starting to like more and more the idea to change the gsu line inside the included packages uploaded on the site. If we change it to use gksu if gsu not found then we can skip the symlinks to /usr/bin/gksu in the packages. And this should not break anything in the old iso versions. Reinstalling the included package in old DD version will still use gsu line and skip searching for gksu since gsu is available. I will make some tests in the next days.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
anikin

Joined: 10 May 2012
Posts: 1020

PostPosted: Sat 22 Nov 2014, 11:22    Post subject:  

Hi Toni, Fred et al,

Nice to see the whole DD crew is back in the sweatshop again!
Debian will never cease to surprise me, here's another little discovery. Debian's binaries by default are compiled as i386, unlike for example, Arch Linux with its default i686 architecture. This may look like a bit of disadvantage, but the situation isn't entirely hopeless, as Debian has a bit of everything for everyone. It has a GLIBC package optimized for i686. https://packages.debian.org/wheezy/libc6-i686
Quote:
This set of libraries is optimized for i686 machines, and will only be used on an i686 class CPU (check the output of `uname -m'). This includes Pentium Pro, Pentium II/III/IV, Celeron CPU's and similar class CPU's (including clones such as AMD Athlon/Opteron, VIA C3 Nehemiah, but not VIA C3 Ezra)
Great, let's perform a dangerous experiment. To celebrate Fred's comeback, I will do it on his DD, he will accept the blame in case of failure.
Quote:
root@dog:~# ldd --version
ldd (Debian EGLIBC 2.13-38+deb7u4) 2.13
root@dog:~#
Quote:
root@dog:~# apt-get install libc6-i686
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libc-bin libc6
Suggested packages:
glibc-doc locales
The following NEW packages will be installed:
libc6-i686
The following packages will be upgraded:
libc-bin libc6
2 upgraded, 1 newly installed, 0 to remove and 22 not upgraded.
Need to get 6301 kB of archives.
After this operation, 2716 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
...
Preconfiguring packages ...
(Reading database ... 31436 files and directories currently installed.)
Preparing to replace libc-bin 2.13-38+deb7u4 (using .../libc-bin_2.13-38+deb7u6_i386.deb) ...
Unpacking replacement libc-bin ...
Setting up libc-bin (2.13-38+deb7u6) ...
(Reading database ... 31437 files and directories currently installed.)
Preparing to replace libc6:i386 2.13-38+deb7u4 (using .../libc6_2.13-38+deb7u6_i386.deb) ...
Unpacking replacement libc6:i386 ...
Setting up libc6:i386 (2.13-38+deb7u6) ...
Selecting previously unselected package libc6-i686:i386.
(Reading database ... 31437 files and directories currently installed.)
Unpacking libc6-i686:i386 (from .../libc6-i686_2.13-38+deb7u6_i386.deb) ...
Setting up libc6-i686:i386 (2.13-38+deb7u6) ...

Done. We have a new directory created at /lib/i386-linux-gnu/i686/
Quote:
root@dog:~# ldd --version
ldd (Debian EGLIBC 2.13-38+deb7u6) 2.13
root@dog:~#
In theory DD should now run a bit faster and consume less power. Maybe future upgrades should have this package installed, what you think, guys?

Taking this opportunity, Fred, this DD is really nicely built, I fully agree with jrb. What I don't like though, the shutdown menu occupies almost the whole screen. It is disproportionately large. Nice to have the terminal in the bar, why is it also duplicated on the desktop?

edit I'm not sure, i386 is Debian's actual architecture. It might well be i486, or even a recent upgrade to i586 as seen mentioned somwehere. But it definitely is NOT i686.
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Sat 22 Nov 2014, 13:08    Post subject:  

Hi, Anikin.

Quick calculation shows libc6-i686 will add 832KB to the iso size.
Even less because for next version we will execute apt-get upgrade and this will free some space reading the terminal output:
Code:
root@debian:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages have been kept back:
  lame roxterm-gtk2
The following packages will be upgraded:
  apt apt-utils base-files ca-certificates curl debian-archive-keyring file
  libapt-inst1.5 libapt-pkg4.12 libc-bin libc6 libcurl3 libcurl3-gnutls
  libgcrypt11 libkeyutils1 libmagic1 libperl5.14 libssl1.0.0 libtasn1-3
  libxml2 live-config live-config-sysvinit multiarch-support openssl perl
  perl-base perl-modules rsyslog tzdata wget wpasupplicant
31 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 26.2 MB of archives.
After this operation, 1090 kB disk space will be freed.
Do you want to continue [Y/n]? y

I will add libc6-i686 in next version changes post (if Fred doesn't mind).

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Sun 23 Nov 2014, 03:09    Post subject:  

Hi, Fred.

Instead creating symlink gsu to /usr/bin/gksu in DD packages I think we can replace gsu line in the scripts from:
Code:
[ "`whoami`" != "root" ] && exec gsu ${0}

to
Code:
if [ -z `which gsu` ]; then
[ "`whoami`" != "root" ] && exec gksu ${0}
else
[ "`whoami`" != "root" ] && exec gsu ${0}
fi

Still we need to add "gsu | gksu" as dependency in packages with gsu line (existing and new packages).
Then:
We skip symlinking in postins script.
We do not need to change existing packages in DD (except the packages with conflicting files like frisbee and sns), but I think it is good to reinstall all moded packages anyway for next version.
All moded packages from included will be compatible with old DD versions (and with standard Debian if we add all needed dependencies inside Control file).
I think this is the best way to do it.
if you agree I will start editing and testing packages from section included in the next days and see if I can find something more missing in packaging method post.
We can change gsu line different way if you have better suggestion from the above example. The point is if gsu is not installed to make sure gksu will be used. Since "gsu | gksu" is added in Control we make sure the script will find the needed command.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Sun 23 Nov 2014, 18:18    Post subject:  

Quote:
Still we need to add "gsu | gksu" as dependency in packages with gsu line (existing and new packages).
Then:
We skip symlinking in postins script.
-----
......


Thanks, Toni!

It seems like you figured it out well, I don't understand all but I trust you Smile
Couldn't take the time last few days to test and think about these things.
So if you are sure the editing of the scripts with gsu line cannot be avoided, I agree with the way you proposed.
And libc6-i686 could give advantage maybe and since it's so small I don't mind.

Anikin, I'll reply later more, thanks for your suggestions!

Edit: could you send screenshot of the extremely large shutdown dialog?
I've never seen it like that, maybe it depends on the resolution of the screen, I have only at most 1024X768.

Fred
Back to top
View user's profile Send private message 
anikin

Joined: 10 May 2012
Posts: 1020

PostPosted: Sun 23 Nov 2014, 19:45    Post subject:  

Hi Toni, Fred et al,

Here's the screenshot.
shutdownmenu.jpeg
 Description   
 Filesize   32.64 KB
 Viewed   259 Time(s)

shutdownmenu.jpeg

Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Mon 24 Nov 2014, 03:44    Post subject:  

Hi, Fred.
fredx181 wrote:
So if you are sure the editing of the scripts with gsu line cannot be avoided, I agree with the way you proposed.

It can be avoided if we use symlink lines in postinst in every package that needs gsu.
But I think it is better to edit the gsu line instead creating symlinks in each package. This will make the scripts universal for debian based system.
And we nee to use the new gsu + gksu line in the future when we make scripts,
Note we do not need to edit gsu line in scripts already included in the iso.
We need to do it only in the scripts inside the packages uploaded on the site. And we can reinstall only the packages that have conflicting files from apt-check reports you made for the next update.

It will take some time and I will ask you for help for some packages. Maybe some better solution will come up later.

Edit: Fred, if you prefer not to use gsu + gksu line in new scripts in the future we can do it by adding symlink lines in the packages. This means some more work for each new package but I do not mind to use symlinking instead changing gsu line inside the packages. Both solutions will work.
On the other hand I suggest in the future not to use unique names for dependency scripts like gsu. Many scripts use gsu and this unique gsu name makes all scripts incompatible for other debian system.
No need to do it this way since we have gksu standard script and actually gsu is gksu alternative. We can try to avoid this in the future.
The best fix for me is to change gsu name to gksu and make package gksu-debdog addiing as conflicting package debian gksu. But it is too late for such fix now.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Mon 24 Nov 2014, 17:02    Post subject:  

Hi Toni,

Quote:
fredx181 wrote:
So if you are sure the editing of the scripts with gsu line cannot be avoided, I agree with the way you proposed.

It can be avoided if we use symlink lines in postinst in every package that needs gsu.
But I think it is better to edit the gsu line instead creating symlinks in each package. This will make the scripts universal for debian based system.
And we nee to use the new gsu + gksu line in the future when we make scripts,
Note we do not need to edit gsu line in scripts already included in the iso.
.....
.....


Ok, it's only for the packages, not the included scripts so all we have to do is change the gsu line in the existing packages and then reinstall them for next release. And there will be a 'gsu.deb' I suppose.
It's fine for me, did I summarize this well?
I suggest to use the gsudo script (change name to gsu), the yad version or the gsu version pointing to ktsuss-sudo (the one I uploaded few days ago) if it works for you well

Quote:
On the other hand I suggest in the future not to use unique names for dependency scripts like gsu. Many scripts use gsu and this unique gsu name makes all scripts incompatible for other debian system.
No need to do it this way since we have gksu standard script and actually gsu is gksu alternative. We can try to avoid this in the future.


Yes, good point.

About libc6-i686, are you sure it doesn't give problems for older computers? (you can test this better than me)

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Mon 24 Nov 2014, 17:18    Post subject:  

Hi, Fred.
fredx181 wrote:
Ok, it's only for the packages, not the included scripts so all we have to do is change the gsu line in the existing packages and then reinstall them for next release. And there will be a 'gsu.deb' I suppose.
It's fine for me, did I summarize this well?

Yes. There is gsu package (yad version) that contains your latest attached gsudo (renamed to gsu). It is here but maybe I will make some small changes inside Control file. Yad is also added in section included packages on the site.
We do not need to reinstall all moded packages, but I think it will be better to do it because of the new dependencies we will add in each package. It is good to update status file with the correct information for moded packages.

Quote:
I suggest to use the gsudo script (change name to gsu), the yad version or the gsu version pointing to ktsuss-sudo (the one I uploaded few days ago) if it works for you well

I will test ktsuss-sudo version more but instead yad it will need moded ktsuss package conflicting with debian ktsuss package. I think it is easier to use yad version.

Quote:
About libc6-i686, are you sure it doesn't give problems for older computers? (you can test this better than me)

I will test this properly but I think it is not a problem. The kernel for example is i686 reading the output from uname -a.

Toni

_________________
Farewell, Nooby, you will be missed...

Last edited by saintless on Mon 24 Nov 2014, 17:19; edited 1 time in total
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Mon 24 Nov 2014, 17:19    Post subject:  

Hi Anikin,

Looking at the screenshot you posted I see it's the same for me.
I thought for a while maybe the shutdown dialog icons are showing larger for you as for me.
I like the large icons, btw.

About duplicate launchers on desktop and panel I'm planning to clean things up for next release.
There are also lots of double entries in the menu (in different categories, though)
And the 'Accessories' category is to full.

Fred
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4481
Location: holland

PostPosted: Mon 24 Nov 2014, 17:26    Post subject:  

Toni wrote:
I will test ths ktsuss-sudo version more but instead yad it will need moded ktsuss package conflicting with debian ktsuss package. I think it is easier to use yad version.


There's only ktsuss package for SID, AFAIK.
A possibility maybe is to include the ktsuss-sudo in the gsu.deb, then you solve the problem of the yad dependency (since yad is not in Debian repo)

Fred
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2572
Location: In The Way

PostPosted: Mon 24 Nov 2014, 17:38    Post subject:  

Hi Fred, Saintless, Anikin

I too think that the shutdwn icons are too large, however I think that if the grey border was transparent it would look much better!

stemsee
Back to top
View user's profile Send private message MSN Messenger 
Display posts from previous:   Sort by:   
Page 259 of 283 [4236 Posts]   Goto page: Previous 1, 2, 3, ..., 257, 258, 259, 260, 261, ..., 281, 282, 283 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.3299s ][ Queries: 12 (0.2006s) ][ GZIP on ]