Layman-2.0 development testing

dol-sen · Posted: Sat May 07, 2011 6:51 pm Post subject: Layman-2.0 development testing

I've recently taken over maintaining and developing layman. I have been working on replacing the high level api with one better suited for consumer apps use. I've also changed the cli to use the new api and that has resulted in about a 20-35% speed increase for the testing I've done.

I've also been extending the mid level api a little so that it is more flexible for use as a lib in other applications. It does not require an overlay definition be input via xml file only. It can now accept a python dictionary to define an overlay or for that matter any VCS be it a development checkout, etc.., also it's location can be anywhere in the filesytem. That is something portage/pkgcore or a layman gui might use, it is not intended for the cli interface.

Some notable changes:

So those that would like to help test:

jbouzan · Tux's lil' helper Joined: 23 Nov 2007 Posts: 134

Never used live ebuilds before. IIRC, they get updated only when you explicitly put them in the emerge list, right? How often should we be doing that if testing?

dol-sen · Posted: Sun May 08, 2011 1:37 pm Post subject:

How often will depend on how many bugs are found and fixed. I will post here for any more major bugs that are found and fixed. A general rule might be once a week if you don't find a bug.

You can also watch the commit logs here if you like. I have tested it quite well, so hopefully not much will be found. But as a general rule it takes many more users with different use patterns to test it thoroughly.

If you use a number of the live ebuilds, there is app-portage/smart-live-rebuild which checks the commits and only rebuilds them when there have been commits since it was last merged.

But also report here if it is all working for you and you don't find anything.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

hedmo · l33t Joined: 29 Aug 2009 Posts: 736 Location: halmstad

dol-sen

i can not add or dell overlays.i can add them but portage dont se them.layman adds it but thats all

avx · Veteran Joined: 21 Jun 2004 Posts: 1831

hedmo · l33t Joined: 29 Aug 2009 Posts: 736 Location: halmstad

jepp.when i upgraded the first time,make.conf blocked the install because that.now i just downgrade,upgrade if i want to add or del

about adding and removing.when i add,it adds and it is in the dir=/var/lib/layman/......
and portage dont see it

when i remove.i get the remove note in the terminal but when i check in /var/lib/layman/
the overlay is still there

i am using

layman -a
and
layman -d

dol-sen · Posted: Sat May 14, 2011 12:50 pm Post subject:

That is very strange. I can understand a simple bug or 2 being there, but not the kind of problem you are seeing.

I am unable to duplicate any of your problems.

John R. Graham · Posted: Sat May 14, 2011 12:55 pm Post subject:

don-sen, how soon do you think this is going to go into the testing branch? There's a small bug in the current stable layman that I was planning on developing and submitting a patch for and would rather contribute to something someone isn't already refactoring.

- John
_________________
Yoda: "Intentionally left blank, this space is."

dol-sen · Posted: Sat May 14, 2011 1:12 pm Post subject:

ok, fixed in commit 6dbd30b42a513437e4219446f34997610b351353

Please re-emerge layman-9999 and continue testing.
John R. Graham what was the bug? I may have fixed it in 1.4.2-r2 or the development branch already.

As for layman-2.0_rc1 being released, that will depend on how many bugs people help me find. This last one I failed to spot myself.

Thank you hedmo
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

John R. Graham · Posted: Sat May 14, 2011 1:34 pm Post subject:

Good point: you might want to know that. :wink:

Not all output you would expect to go to stdout does go to stdout; some going to stderr instead. If you grep the output of "layman -L", you see some bare output from layman and some of the grep output interspersed.

I'm currently running stable right now, so this is with layman-1.4.1.

- John
_________________
Yoda: "Intentionally left blank, this space is."

dol-sen · Posted: Sat May 14, 2011 4:16 pm Post subject:

Yeah, this development version has a completely new message class. That should be fixed for this version already, but if you could test it

to be sure. I'd appreciate that.

If you want to keep stable installed, you can get a git clone of the repo and set the testpath from the example in the checkout, then source that testpath in a terminal. The checkout can then be run from that terminal.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

John R. Graham · Posted: Sat May 14, 2011 4:36 pm Post subject:

By "development" version, you mean the -9999 version, right?

- John
_________________
Yoda: "Intentionally left blank, this space is."

dol-sen · Posted: Sat May 14, 2011 6:26 pm Post subject:

Yes.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

myceliv · Apprentice Joined: 29 Nov 2007 Posts: 178

I am very happy to see this work going on. Being a g-cran user I've been using/testing layman-9999 for many weeks now and finding everything worked smoothly so far.

I do have a g-cran manifest issue (the generated ones are wrong format); where should g-cran issues get reported or tracked?

dol-sen · Posted: Sun May 15, 2011 3:10 pm Post subject:

g-cran issues should be reported on bugzilla since it was a last years gsoc project. Also, the last time I talked with the student and mentor about it, there was a couple bugs that needed fixing before it is moved to the portage tree.

Once that happens, We will add the g-common use flag to layman, adding g-cran as a runtime dep. So, g-common/g-cran support is built-in to layman, so it will be usable without need to re-emerge layman if g-cran in installed after layman.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Wed May 18, 2011 5:49 am Post subject:

I've pushed another couple small commits that fix the success reporting for add/delete when an overlay is already/not installed. Add a message stating so.

I am pleased, there have been very few reported bugs, and those have been easy to fix.

I'll give it another week or so, then maybe release a layman-2.0_rc1.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Fri Jun 03, 2011 8:53 pm Post subject:

Ok, last call for bugs against the current layman-9999. I haven't had a single one this last few weeks,

so will do a -2.0_rc1 this weekend.

Thank you all that have tested it.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

hedmo · l33t Joined: 29 Aug 2009 Posts: 736 Location: halmstad

works super now.thanks dol-sen real nice job :wink:

regards hedmo

dol-sen · Posted: Tue Jun 07, 2011 5:46 am Post subject:

OK, I've pushed a layman-2.0.0_rc1.ebuild to our gentoo-guis overlay. If there are no problems with it. It should get into the main tree in a few days.

_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Wed Jun 08, 2011 2:04 pm Post subject:

Shoot, I have a minor bug to track down and fix in it reporting success after a failure in adding an overlay.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Tue Jul 12, 2011 8:10 pm Post subject:

Ok, I've finally made some time to fix the bug. I've bumped the ebuild in the gentoo-guis overlay to -r1 which applies the patch to fix the issue.

If all is well, I'll have the ebuild put in the main tree very soon.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sun Jul 17, 2011 11:52 pm Post subject:

Layman-2.0.0_rc1-r1 is in the tree now.

So please test it and report any problems/bugs you come across.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sat Jul 23, 2011 2:18 pm Post subject:

for those running layman-9999. I've pushed a number of commits that fix all the tests. There were a couple small potential bugfixes in there as well. I want to create some more tests for the new api before I release the next rc.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

dol-sen · Posted: Sat Aug 06, 2011 7:10 pm Post subject:

There has been several small bugfixes committed. Today I've pushed several should fix some failed error reporting that might have been the cause of layman not syncing for a couple people, bug 377401. I have also modified the way it handles multiple tasks. It now will not stop at the first task if it fails. It also now identifies the repeated error messages as coming from the CLI interace. It does this for the same reasons portage repeats emerge messages at the end of an emerge run, the original may have scrolled past.

Please re-emerge & test layman-9999 and report any bugs. If all is well, I'll release rc2 with all the bugfixes.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch...

Etal · Veteran Joined: 15 Jul 2005 Posts: 1580

Small nitpick, but could you please fix it if you haven't already - could you change the green "*" so that there's a space before it, like in everything else?