PPM2

[L18L]

Better yet a patch

Code: Select all

   #. /usr/lib/gtkdialog/box_yesno "$(gettext 'Last warning')" "$NEEDEDK $(gettext 'of the ') $AVAILABLE $(gettext ' available MB will be used to install the package(s) you selected.')" "<b>$(gettext 'It is NOT sufficent. Please exit now.')</b>"  "$(gettext 'However, if you are sure about the spep-by-step process, take a risk.')" "$(gettext 'Do you want to cancel installation?')"
   . /usr/lib/gtkdialog/box_yesno "$(gettext 'Last warning')" "$(eval echo `gettext '$NEEDEDK of the  $AVAILABLE available MB will be used to install your selected packages.'`)" "<b>$(gettext 'It is NOT sufficent. Please exit now.')</b>"  "$(gettext 'However, if you are sure about the spep-by-step process, take a risk.')" "$(gettext 'Do you want to cancel installation?')" 

pot file contains then:

Code: Select all

#: /usr/local/petget/installmodes.sh:307
#, sh-format
msgid "$NEEDEDK of the  $AVAILABLE available MB will be used to install your selected packages."
msgstr ""

Voila

[musher0]

Hello, all.

How does a user replace in PPM's the old ftp or http addresses for Ubuntu or Debian
distros whose depots have been moved? It would be a shame to ditch because of this
the excellent work of 666philb on vividpup, or of pemasu on UpupRaring and WheezyPup. .

Thanks in advance.

musher0

[mavrothal]

pot file contains then:

Got it. Thanks!
We'll do.
If you come other similar strings please let us know.

[mavrothal]

How does a user replace in PPM's the old ftp or http addresses for Ubuntu or Debian
distros whose depots have been moved?

Since the original, the repo addresses of the binary compatible distro are in /root/.packages/DISTRO_COMPAT_REPOS. Are part of the WOOF puppy building process and were never changed by PPM...

[musher0]

How does a user replace in PPM's the old ftp or http addresses for Ubuntu or Debian
distros whose depots have been moved?

Since the original, the repo addresses of the binary compatible distro are in /root/.packages/DISTRO_COMPAT_REPOS. Are part of the WOOF puppy building process and were never changed by PPM...

Thank you, Mr. Terse. If you'd kindly elaborate, we will be grateful..

[mavrothal]

If you'd kindly elaborate, we will be grateful..

I believe my answer is addressing your question.
You may want to ask a better question if you are not happy with the answers you are getting.

[musher0]

If you'd kindly elaborate, we will be grateful..

I believe my answer is addressing your question.
You may want to ask a better question if you are not happy with the answers you are getting.

Hello mavrothal.

It isn't, but I thank you nevertheless for at least the time you spent typing your insult.

One forum member has provided one answer, and others have offered either a
pointer to it, or some help as to the focus of the question, so I won't be bothering
you any further.

Here's the funny thing about questions: when they first pop up in your head, they're
often fuzzy. You may wish to think about that -- or not.

BFN.

musher0

[darry1966]

If I understand MusherO correctly he wants to know if you can edit PPM2 like apt-get sources list - pretty simple question.

Especially if sources change and they do, or you want a faster mirror.

[musher0]

Thanks for the moral support, darry1966.

I just put augras' solution to the test in upup-Raring-3.9.9.2. I did everything right, I
think, followed augras' instructions, updated the dB's, etc.

The PPM now lists the files from the http://old-releases.ubuntu.com/ubuntu/
site, but it doesn't download any of them because it can't get the filesize on my
system. Beats me.

In any case... patience is a virtue! We'll see this bug through, I'm sure.

I think it would be useful to have this feature in PPM because eventually all ubuntu-
based Pups will end up in this situation, which is no fun for the user. The user who
finds a Puppy distro (s)he likes will want to keep it as long as possible, so I think
(s)he would appreciate having this feature. (Provided by augras' pet or otherwise, it
doesn't really matter, IMO.)

Other distros have a longer life-cycle, but they'll end up in that situation too.

BFN.

musher0

[musher0]

Hello all.

I risked plucking Iguleder's edit of PPM2 for LibrePup out of librepup and grafting it in
UpupRaring (after proper back-up of the original UpupRaring PPM). It worked fine.

This version gave me more to go on than UpupRaring's original version. It seems
the problem is with the filesize determination on the ubuntu servers, not on my
system. (Please see screen capture.)

Iguleder's PPM2 provided me with enough info to go to the depot and download the
files I wanted. Not ideal, but better than nothing. Once there, I noted that the
old.releases.ubuntu.com server was slow as hell. So maybe their speed is causing the bug.

Anyway, this is not a complaint; it's intended to be a contribution, however
incomplete, towards solving a bug.

BFN.

musher0
~~~~~~~~~
P.S. As a result, I now have a .tar.lzo archive of Iguleder's PPM2 in librepup. If
anyone's interested, leave me a note? Cheers.

[mavrothal]

Iguleder's edit of PPM2
<snip>
Iguleder's PPM2
<snip>
Iguleder's PPM2

Boy, you are annoying!

Now, for the rest of the puppians, so they may not get into potential trouble:
Iguleder did and does many great things for puppy and among those was to rewrite recently the source of 3 binary files, debdb2pupdb, find_cat and printcols, that are used by woof during puppy building and PPM during database update, to process of downloaded database to a puppy understandable format.
So, besides a considerable speed up in the processing the the already downloaded databases during database update, there is no difference what so ever in PPM UI, download handling, or other inner workings from what is in woof-CE.

So unless you have a problem in your older system with the processing of the databases being slow after their download, I would suggest to save yourself the trouble.
If you do have a problem with the database processing speed, I would suggest to download the new 32 bit or 64 bit binaries of the above files from woof-CE directly to your system.
Better yet update to one of the upcoming puppies (libre or otherwise) with all the changes included.

[greengeek]

Hello, all.
How does a user replace in PPM's the old ftp or http addresses for Ubuntu or Debian
distros whose depots have been moved? It would be a shame to ditch because of this
the excellent work of 666philb on vividpup, or of pemasu on UpupRaring and WheezyPup. .
Thanks in advance.
musher0

I don't pretend to understand much of what is under the hood in Puppy, but I am trying to follow this conversation and as far as i can tell the clue is in the file mavrothal referred to:
/root/.packages/DISTRO_COMPAT_REPOS

Doesn't this file list the download url? Is it as simple as changing that file to make the PPM look elsewhere? Or have I missed the point?

My file contains the following:

Code: Select all

#PKG_DOCS_DISTRO_COMPAT
#where to download the compatible-distro pkgs databases from.
#first field is for testing the url.
#second field is full URI of the database file.
#third field is name of db file when local and after being processed into standard format
#PKG_DOCS_DISTRO_COMPAT='salix.enialis.net|http://salix.enialis.net/i486/slackware-14.0/PACKAGES.TXT|Packages-slackware-14.0-official salix.enialis.net|http://salix.enialis.net/i486/14.0/PACKAGES.TXT|Packages-slackware-14.0-salix repository.slacky.eu|http://repository.slacky.eu/slackware-14.0/PACKAGES.TXT|Packages-slackware-14.0-slacky salix.enialis.net|http://salix.enialis.net/i486/slackware-14.0/patches/PACKAGES.TXT|Packages-slackware-14.0-patches'
# NOTE added ftp.osuosl.org for patches as it's the official changelog site. It does not contain dependency info.
# The rationale behind this decision is that only security fixes are posted and they are compiled against the original libs where possible
# so any deps needed should already be in place. Have changed this to be first repo searched, that way at any time an up to date slacko is built.
PKG_DOCS_DISTRO_COMPAT='ftp.osuosl.org|ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/patches/PACKAGES.TXT|Packages-slackware-14.0-patches salix.enialis.net|http://salix.enialis.net/i486/slackware-14.0/PACKAGES.TXT|Packages-slackware-14.0-official salix.enialis.net|http://salix.enialis.net/i486/14.0/PACKAGES.TXT|Packages-slackware-14.0-salix repository.slacky.eu|http://repository.slacky.eu/slackware-14.0/PACKAGES.TXT|Packages-slackware-14.0-slacky'

#REPOS_DISTRO_COMPAT
#first field is for testing the url.
#second field is full URI of the repo
#third field is the name of db-file(s) associated with that repo. it may have glob wildcards.
REPOS_DISTRO_COMPAT='slackware.cs.utah.edu|http://slackware.cs.utah.edu/pub/slackware/slackware-14.0|Packages-slackware-14.0-official slackware.mirrors.tds.net|http://slackware.mirrors.tds.net/pub/slackware/slackware-14.0|Packages-slackware-14.0-official ftp.gwdg.de|http://ftp.gwdg.de/pub/linux/slackware/slackware-14.0|Packages-slackware-14.0-official ftp.isu.edu.tw|http://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-14.0|Packages-slackware-14.0-official salix.enialis.net|http://salix.enialis.net/i486/14.0|Packages-slackware-14.0-salix repository.slacky.eu|http://repository.slacky.eu/slackware-14.0|Packages-slackware-14.0-slacky slackware.cs.utah.edu|http://slackware.cs.utah.edu/pub/slackware/slackware-14.0|Packages-slackware-14.0-patches slackware.mirrors.tds.net|http://slackware.mirrors.tds.net/pub/slackware/slackware-14.0|Packages-slackware-14.0-patches ftp.gwdg.de|http://ftp.gwdg.de/pub/linux/slackware/slackware-14.0|Packages-slackware-14.0-patches ftp.isu.edu.tw|http://ftp.isu.edu.tw/pub/Linux/Slackware/slackware-14.0|Packages-slackware-14.0-patches'

#ftp://ftp.osuosl.org/pub/slackware/slackware-14.0/ChangeLog.txt

[mavrothal]

/root/.packages/DISTRO_COMPAT_REPOS

Doesn't this file list the download url? Is it as simple as changing that file to make the PPM look elsewhere?

Yes

[musher0]

Iguleder's edit of PPM2
<snip>
Iguleder's PPM2
<snip>
Iguleder's PPM2

Boy, you are annoying! *

Now, for the rest of the puppians, so they may not get into potential trouble:
Iguleder did and does many great things for puppy and among those was to rewrite recently the source of 3 binary files, debdb2pupdb, find_cat and printcols, that are used by woof during puppy building and PPM during database update, to process of downloaded database to a puppy understandable format.
So, besides a considerable speed up in the processing ** the the already downloaded databases during database update, there is no difference what so ever in PPM UI, download handling, or other inner workings from what is in woof-CE.

So unless you have a problem in your older system with the processing of the databases being slow after their download, I would suggest to save yourself the trouble.
If you do have a problem with the database processing speed, I would suggest to download the new 32 bit or 64 bit binaries of the above files from woof-CE directly to your system. ***
Better yet update to one of the upcoming puppies (libre or otherwise) with all the changes included. ****

For ease of reading, the asterisks below correspond to asterisks I introduced in
Mr. Terse's message above.

* At least you're uttering real words now, and they seem to have some logic to
them! Yes I said "logic" but qualified it with "some logic". Whether I condone your
logic or not is an enttirely different matter. As to my being annoying with you, you
can rest assured that I'm only starting!

** Of course a "considerable speed up in the processing" is of no interest to anyone.
Also, probably invisible to your eyes, Iguleder's version (have you even tried it?)
produced more usable info in its error reports than the PPM's originally provided with
UpupRaring-3.9.9.2 or even TahrPup.

*** I suppose there are huge diffs between those repos and what's in the existing
/usr/local/petget folder in LibrePup. No doubt Iguleder tele-ported the PPM he
included in LibrePup-6.0.2 from Mars.

**** Update to some still green and iffy Puppy that produces random errors, and lose
the functionalities of a Puppy that never failed? You have to be kidding. UpupRaring
should be the new Puppy benchmark. Also, to run comfortably, some new Puppies
require more modern machines than some of us can afford at this time. Finally, your
mentality about updates is too close to M$'s to be of any comfort in the Puppy
context.

Best regards.

musher0

[L18L]

Iguleder did and does many great things for puppy and among those was ...

There's no such thing - Librepup uses the latest PPM in woof-CE.

Just a friendly terse reminder.
Hope that helps

[L18L]

OK then.
Hopefully your script will work

Attached script will.

put it into /usr/local/petget
make it executable
click it

There is nothing specific to petget inside.
Should be fine for further usage.

Code: Select all

#!/bin/sh
# Change TEXTDOMAIN in each script of current directory $(pwd) to TEXTDOMAIN=$newTEXTDOMAIN.
# Merge exising translations
.
.
.
# /create mo files

echo "
That's it. Press ENTER key to close." 
read dummy
exit 0 

[mavrothal]

Attached script will.

Nice!
Was failing to change the TEXTDOMAIN of the scripts but the following changes fixes it

Code: Select all

--- a/single_textdomain	2015-10-18 12:38:59.000000000 +0300
+++ b/single_textdomain	2015-10-18 13:36:35.000000000 +0300
@@ -4,13 +4,13 @@
 
 die () { echo $1; exit 1;}
 
-PATTERN='^export TEXTDOMAIN='
+PATTERN='export TEXTDOMAIN='
 newTEXTDOMAIN="`basename $(pwd)`"
 TITLE="All scripts in $(dirname $0): change to TEXTDOMAIN=$newTEXTDOMAIN"
 
 [ -t 0 ] || exec rxvt -geometry "90x30" -title "$TITLE" encodings=eu+vn+jp+jp-ext+kr+zh+zh-ext -e "$0" "$@"
 
-grep -w "${PATTERN}${newTEXTDOMAIN}" * && { echo ; die "Sorry, default newTEXTDOMAIN ${newTEXTDOMAIN} alrady exists";}
+grep -w "^${PATTERN}${newTEXTDOMAIN}" * && { echo ; die "Sorry, default newTEXTDOMAIN ${newTEXTDOMAIN} alrady exists";}
 
 NUM=$(grep -n -m 1 "$PATTERN" * | wc -l)
 [ $NUM -eq 0 ] && die "nothing to do here, no '$PATTERN' found in $(pwd)." \
@@ -19,7 +19,7 @@
 script  : line number  : PATTERN
 --------------------------------"
 
-for f in * ; do grep -H -n -m 1 "$PATTERN" $f || continue ; done
+for f in * ; do grep -H -n -m 1 "^$PATTERN" $f || continue ; done
 echo "--------------------------------"
 echo "newTEXTDOMAIN is $newTEXTDOMAIN.
  Please make sure this is not yet in use.
@@ -45,12 +45,12 @@
 for f in *
 do
  [ -f $f ] || continue
- oldTEXTDOMAIN="`grep -m 1 "$PATTERN" $f `"
+ oldTEXTDOMAIN="`grep -m 1 "^$PATTERN" $f `"
  oldTEXTDOMAIN=${oldTEXTDOMAIN##*=} 
  [ "$oldTEXTDOMAIN" ] || continue
 
- echo sed -i "s/${PATTERN}${oldTEXTDOMAIN}/${PATTERN}${newTEXTDOMAIN}/" $f
- # sed -i "s/${PATTERN}${oldTEXTDOMAIN}/${PATTERN}${newTEXTDOMAIN}/" $f
+ #echo sed -i "s/${PATTERN}${oldTEXTDOMAIN}/${PATTERN}${newTEXTDOMAIN}/" $f
+  sed -i "s/^${PATTERN}${oldTEXTDOMAIN}/${PATTERN}${newTEXTDOMAIN}/" $f
 
  # from momanager
     # LANG=${ORIGLANG} xgettext -o ${ATEXTDOMAIN}.pot -j --from-code=UTF-8  --keyword=_ -L Shell --no-wrap -f ./xEXTRASCRIPTS >/dev/null # --keyword= is additional
@@ -67,7 +67,7 @@
 for f in *
 do
  [ -f $f ] || continue
- oldTEXTDOMAIN="`grep -m 1 "$PATTERN" $f `" && oldTEXTDOMAIN=${oldTEXTDOMAIN##*=} 
+ oldTEXTDOMAIN="`grep -m 1 "^$PATTERN" $f `" && oldTEXTDOMAIN=${oldTEXTDOMAIN##*=} 
  [ "$oldTEXTDOMAIN" ] || continue
  # for transLANG in de
  for transLANG in $(ls /usr/share/locale)

Attach the modified one.

Could be a nice base for generating .pot and .mo files from anything.
If it is made to accept arguments in addition to the defaults (ie run from within the folder) then

Code: Select all

single_textdomain [path_to_input] [new_text_domain] [path_to_output]

could do the job.

You may want to move it to its own thread if you decide to go that way.

[L18L]

Attached script will.

Nice!
Was failing to change the TEXTDOMAIN of the scripts but the following changes fixes it

It is intended to be used only by geeks who know this:

Code: Select all

#

Could be a nice base for generating .pot and .mo files from anything.

No.
For generating a .pot file from different sources see:

Code: Select all

xgettext --help

For generating a .mo file from a .po file see:

Code: Select all

msgfmt --help

This script was made just to help you continue debugging your ppm2.

[mavrothal]

This script was made just to help you continue debugging your ppm2.

I see. Thanks.
But,
a) PPM2 is far from mine
b) PPM2 has no bugs ( that I know of - report if otherwise)
c) I do not want to continue anything with PPM (but if #b in not true, I may try )

As a matter of fact the difficulties in translations were brought to my attention few days back by xanad (before of all the commotion here) and he was just declared it solved. (last famous words )

[L18L]

As for what you call "difficulties in translations"

I call it buggy intenationalization

The solution which I have demonstrated ("of the") was just one example. Hope you (or who is feeling responsible) find the other mis-coded messages.

cheers