layman-9999 users, last test push before 2.0.0 final

[dol-sen]

I've spent some time finally and fixed the remaining bugs (minus some enhancement requests) plus did some other code changes sort of needed.

The changes to layman-9999's ebuild should be available in the tree shortly.

I've now created a layman-updater script that performs the db rename from rc3, or for new installs creates an empty make.conf in layman's storage location and prints out what use to be the new install einfo/elog messages. So now those won't litter up your screen unless it is a new install.

Can you please run it through all it's paces so I can hopefully release it as 2.0.0 final and so it can be stabilized after the waiting period

Please report any bugs you find.

Thank you.

[kurly]

References to /etc/make.conf in layman-updater should probably be changed to /etc/portage/make.conf. (Both work, but the latter is the new 'correct' location.)

Also, simple spelling fix!

kurly@smile ~/source/layman $ grep occured -R .
./layman/cli.py: self.output.warn("CLI: Errors occured processing action"

occured -> occurred

Thanks for all the great work you do, and sorry for not filing formal bug reports. I've yet to file an official bug report, but I'd be happy to work with you if it'll help.

[dol-sen]

No problem reporting those here. I totally forgot to check for the make.conf locations listed. I need to update the man pages too.

[edit] fixed and pushed to the repo. [/edit]

[kurly]

doc/layman.8.txt still has "HANDLING /ETC/MAKE.CONF" on line 278

Otherwise looks good!

[dol-sen]

DOH! foiled by all uppercase on my search & replace.

OK, fixed, but won't push it just yet, I have some other stuff I'm working on. It looks like layman will need to start downloading a gpg signed list, so I'm working on code for it.

[dol-sen]

Well, I found a couple more things to add/update in the man page.

I have also decided to release this now as 2.0.0_rc4. There is a change coming in the next few weeks that will begin signing the repositories.xml list that layman downloads. I imagine that there will be an overlap period where both signed and unsigned lists are offered. But the unsigned one will likely be phased out for security reasons once 2.0.0 is stabilized.

[dol-sen]

Update. I've just released rc5 with all the recent bugfixes, a bit of code cleanup. It stops short of the initial gpg signed repositories.xml list support that is included in layman-9999 which I also released today.

For those that wish to test run the gpg-signed list. There are some non-updated lists floating around for initial testing. But they should not be used for production. I have uploaded a layman-test.cfg to my dev space. There is also a couple gpg-signed lists, one with a detached signature (the repositories.xml file is untouched) and a compressed, signed file which is only 13% the size. layman is capable of both types, but the detached sig type is what is destined for the main gentoo repositories list. That way older layman versions will just need the url to to be updated to the new location.

Just edit the layman-test.cfg and edit the storage location to a test directory you desire (no need to be root user) then run layman with the -c, --config option to use your layman-test.cfg. To verify the list signature you will need to manually add my gpg signature to your gpg keyring. public key id: 014F17CB

At present there are only 2 bugs left to fix.

• 1) an svn-upgrade needed detection and automatic run
  2) complete the gpg signed list feature.
  • a) add a layman gnupg keyring.
    
    b) add some tools to layman-updater for managing the keyring.
    Currently gpg must be run manually & there is not a layman-only keyring to use.
    
    c) Wait for the repositories.xml list url move to distfiles.gentoo.org and the
    detached-signature file generation to be automated. (should be by Dec. 2012)