Woof at Github

Message

Ibidem · #76 Post by **Ibidem** » Sun 17 Nov 2013, 21:36

Karl Godt wrote:
commit 99b66de00ce8956ffa2d4c261d4474181e9724be
Author: mavrothal <mavrotal@yahoo.com>
Date: Wed Nov 13 15:58:06 2013 +0200

Revert "Replace EMPTYDIRMARKER with .gitignore"

This reverts commit d1adca562538de8b3fd38bdedc698c02b17a7e85.
git --version
git version 1.6.4.1

git checkout 99b66d
ignoring REUC extension
Note: moving to '99b66d' which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
git checkout -b <new_branch_name>
HEAD is now at 99b66de... Revert "Replace EMPTYDIRMARKER with .gitignore"

This would be a "total" reset .. ?

Yes and no...
Each commit is a repository state.
Each branch is a series of commits; the last commit in a branch is its tip/head.
git checkout switches between branches or commits; checking out a branch is the same as checking out its tip.
You can always switch back to a branch or commit the same way you switched from it: git checkout ...

In git syntax, a reset is something different: it means losing work that's in progress. And that is done with "git reset".

git checkout -b upstream
Switched to a new branch 'upstream'

Finally -b option works -> seems my new git is buggy .. ?

If you copy-pasted your previous post from terminal messages, you used a dash instead of a hyphen, which wouldn't work.

In any case, git checkout -r <remote>/<remote-branch> would have been appropriate there; ie

Code: Select all

git checkout -r puppylinux-woof-CE/master
git checkout -b upstream

"should work"--but we all know how that goes...

(I'm basing that on the fact that you added the remote "puppylinux-woof-CE" already.)

git pull https://github.com/puppylinux-woof-CE/woof-CE
error: The requested URL returned error: 403 Forbidden while accessing https://github.com/puppylinux-woof-CE/woof-CE/info/refs

fatal: HTTP request failed

Try using

Code: Select all

git pull -u puppylinux-woof-CE master

Or try repeating it (yes, that does sometimes solve the problem; network states vary).
Or try using git://github.com/puppylinux-woof-CE/woof-CE.git as the url.
Or try getting a newer git version (github isn't too great with git 1.6).

Karl Godt · #77 Post by **Karl Godt** » Mon 18 Nov 2013, 01:04

Ibidem : Today I encountered such :

[puppypc]# git checkout quirky-testing
Gewechselt zu Branch 'quirky-testing'

[puppypc]# git branch
master
puppy
puppy-testing
puppy-tmp
quirky
* quirky-testing
quirky-tmp
shutdown
testing
urgs

[puppypc]# git log

[ .. ]

[puppypc]# git checkout 99b66de
Note: checking out '99b66de'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b new_branch_name

HEAD ist jetzt bei 99b66de... Revert "Replace EMPTYDIRMARKER with .gitignore"

[puppypc]# git branch
* (losgelöst von 99b66de)
master
puppy
puppy-testing
puppy-tmp
quirky
quirky-testing
quirky-tmp
shutdown
testing
urgs

I was able to get where I wanted to get finally, mostly by using the "urgs" directory as a buffer switching to it and git branch [-d|-D] quirky-testing deleting and recreating it several times .

My physical HEAD is still detached

Ibidem · #78 Post by **Ibidem** » Mon 18 Nov 2013, 17:06

Karl, check out a branch.

Code: Select all

git checkout master

Or whichever branch you want.

zigbert · #79 Post by **zigbert** » Mon 18 Nov 2013, 18:05

Things are getting more exiting.....

I see the CE-3 build of Wanderer includes pSeries apps that are really old. I guess those is fetched from the Quirky repo, and I have no possibility to update those. I guess they also have to be updated in Woof as well. This rise the question?

Should the apps be included in Woof?
As Micko stated earlier in this thread, this might not be the best solution. Maybe we could include the small ones that does not rely on big dependencies. Ie. pClock, pTiming, pSchedule.
pprocess, pFilesearch, pFind has been replaced in several puplets, so these might best stay outside.
pMusic and pBurn are the big brothers that some think fattens their build too much. It must be said that pBurn does not rely on ffmpeg, - only to support Audio-CD/Video-disc.

Maybe a better solution would be to open a repo where app-makers can upload and then add a pull-request to Woof. Or to add our repos to woof.

Sigmund

mavrothal · #80 Post by **mavrothal** » Mon 18 Nov 2013, 20:14

zigbert wrote: Maybe a better solution would be to open a repo where app-makers can upload and then add a pull-request to Woof. Or to add our repos to woof.

Actually there is no reason for any of the pets/apps to be included in the woof. They could be downloaded and installed as any other pet.
I guess some are in woof for historical reasons.
What is really needed is a repo. Probably clone puppy-common somewhere else and add/modify as needed.

01micko · #81 Post by **01micko** » Mon 18 Nov 2013, 21:09

As far as repo's goes, I have asked ibiblio for an account. Haven't heard back yet but I guess they get a heap of mail.

One possible solution to P-apps is to state the version number in DISTRO_PKGS_SPECS. This is quite easy as I do it all the time with different kernel_headers packages. (look at the one provided in ~/.packages in any slacko for an example).

When my account does get approved it might be time to reduce dependency on Barry's Quirky repo, then we can move pet_packages-common, pet_packages-noarch (etc) to the Puppy repo. Of course we don't want to touch BK's stuff in the Quirky repo.

Of course pet_packages-{precise,dpup(?squeeze,wheezy?),mageia} etc would need to be set up too.

It's early days, we'll get to these things in due course.

ally · #82 Post by **ally** » Mon 18 Nov 2013, 21:19

I have just starting uploading a mirror of the common packages from ibiblio here:

http://archive.org/details/Puppy_Linux_ ... Repository

I will add no-arch in response to micko's comments

unfortunately I could not have additional accounts added for uploading (?) but anyone can upload and then ask to have the files moved to the appropriate page

in the mean time files can emailed to me and I can put them up

anything else you needed let me know if I can help....

ally

edit http://archive.org/details/Puppy_Linux_ ... Repository

mavrothal · #83 Post by **mavrothal** » Tue 19 Nov 2013, 05:00

01micko wrote: It's early days, we'll get to these things in due course.

Very true.
But having control over your repo is vital for the building process and its rationale and the maintenance/update of the packages/pets.

The second reason is that building from other distros or even LFS can really generate problems and bloat (I'm playing with compiling these days

), so we will need puppy-specific packages by capable compilers (where are they these days?

)

go2null · #84 Post by **go2null** » Wed 20 Nov 2013, 15:57

01micko wrote:Probably a good idea to set up and configure git.

In the short term:
Code: Select all
git config --global http.sslVerify false
That should work.

Other wise, go to the site and grab the tarball.

Didn't really want to disable SSL Verification, so did a google and found this:
http://derekmolloy.ie/fixing-git-and-cu ... bone-blac/

After installing ca-certificates_20130119 with PPM, git still complained.

This was fixed by going to http://packages.ubuntu.com/raring/all/c ... s/filelist and found the reference to /usr/sbin/update-ca-certificates.

After running this, was able to clone successfully.

*NOTE*: Running git from the console didn't work off the bat. A quick reinstall of git_1.8.1.2-1 with PPM fixed that.

[EDIT] Fixed missing leading "/" in "/usr..."

pemasu · #85 Post by **pemasu** » Wed 20 Nov 2013, 16:51

This fix is valid for git ssl error:
http://murga-linux.com/puppy/viewtopic. ... 154#713154

oldyeller · #86 Post by **oldyeller** » Fri 22 Nov 2013, 09:21

Hello Everyone,

I have gotten OVPrecise 5.8 and OVPrecise-retro 5.8 Finalized

You all can find it here http://www.murga-linux.com/puppy/viewto ... 641#738641.

Have fun!

vicmz · #87 Post by **vicmz** » Fri 22 Nov 2013, 18:08

mavrothal wrote:So we (me, 01micko and pemasu - we welcome new members in the team) just opened a project on Github to host woof as derived from Barry's repo on November 11, 2013.

Then all the effort for multilingual support in Puppy Linux will remain and can be further enhanced, and all Puppies made from Woof-CE will be compatible with the existing language packs, meaning that newer Puppies will not go back to English-only but will be international from the beginning. Great!

Is it possible to have an initrd that includes a basic set of popular languages to choose from at first, so that users are able to read boot messages in their language (practical for live-CDs) and then install the langpack when they get the desktop?

mavrothal · #88 Post by **mavrothal** » Fri 22 Nov 2013, 19:06

vicmz wrote: Is it possible to have an initrd that includes a basic set of popular languages to choose from at first, so that users are able to read boot messages in their language (practical for live-CDs) and then install the langpack when they get the desktop?

"Gettexting" the init script is not a good idea as it would require a number of additional libraries in the initrd. However BK's init accepts the "plang" boot parameter (example: de_DE.UTF-8 ) and looks for the corresponding init in /locale/${PLANG%.*}/init (ie /locale/es/init or /locale/es-ES/init )
It also looks for a /PUPPYLANG file that contains the plang argument, in case you want to build a puppy with a different default language. The init script has 60 text messages so is not too much work to do. The only ¨problem¨ is that the language changes must be provided as a series of sed commands in the /locale/${PLANG%.*}/init file

You may want to add as an "enhancement" in the woof-CE/issues and then start working on the translation of the init script!

zigbert · #89 Post by **zigbert** » Fri 22 Nov 2013, 21:08

I have done some initial testing of gui enhancements in woof.
My guidelines

Only touch gtkdialog code
Take advantages of the recent gtkdialog features
Allow scaling of window
Clean up gui
Make gui code more human readable
Change gtkdialog3/4 to gtkdialog

Is this something for 'zigbert winter of code'?

Iguleder · #90 Post by **Iguleder** » Fri 22 Nov 2013, 21:11

Good to have one of our gtkdialog experts on the woof-CE board

mavrothal · #91 Post by **mavrothal** » Fri 22 Nov 2013, 21:38

zigbert wrote:I have done some initial testing of gui enhancements in woof.
My guidelines
Only touch gtkdialog code

Take advantages of the recent gtkdialog features

Allow scaling of window

Clean up gui

Make gui code more human readable

Change gtkdialog3/4 to gtkdialog

Make it touch friendly ?

BarryK · #92 Post by **BarryK** » Sat 23 Nov 2013, 02:20

This is a great initiative!

I kept very quiet for sometime, wondering if something like this would spontaneously emerge, and it has!

Created and supported by long-time rock-solid guys too!

Yes, there are many who will now get a more direct input to the evolution of Woof and Puppy, than before, when everything channeled through me.

I have announced woof-CE in my new blog:

http://bkhome.org/news/?viewDetailed=00002

I wish you guys great success.

Let me know when a pup distro gets to release status and I'll announce it on my blog and at Distrowatch.

puppyluvr · #93 Post by **puppyluvr** » Sat 23 Nov 2013, 02:47

Hello,
Great project to provide Woof with a future.
Great to see the Puppy Master on board!

shinobar · #94 Post by **shinobar** » Sat 23 Nov 2013, 03:37

Great!

01micko · #95 Post by **01micko** » Sat 23 Nov 2013, 05:19

Slacko -testing, woof-CE (testing branch).

Reports here please.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Woof at Github

How to fix SSL CA Certificate issue

Re: Woof at Github

Re: Woof at Github

Re:Woof-CE