[PALUDIS] Support thread (current v. 0.22.2) - Part 2

Message

BlackEdder · Post by **BlackEdder** » Sat Jan 27, 2007 12:05 am

slycordinator wrote:http://en.wikipedia.org/wiki/Tact
Maybe you'll learn something too.

Conan clearly is Ciaran's new alias

Conan · Post by **Conan** » Sat Jan 27, 2007 12:54 am

tact is a silly concept. It masks the true intent of what one is saying and makes people be less bothered.

zxy · Post by **zxy** » Sat Jan 27, 2007 2:11 am

Paludis-hooks

Ebuilds are converted to doins, dodir....
ask hook (1.2) now installs in .../hooks/common and symlinks are created in two subfolders.

Any complaints?

-------------------------------------------------------------
Monolithic ebuild will not be maintained any more and will be deleted from an overlay in a few days.

Conan · Post by **Conan** » Sat Jan 27, 2007 4:36 am

SRC_URI being use-flag dependant.

Follow the logic if one of the hooks was installed without the flag being set (installed without the meta-ebuild that is).

zxy · Post by **zxy** » Sat Jan 27, 2007 7:41 am

Conan wrote:SRC_URI being use-flag dependant.

Follow the logic if one of the hooks was installed without the flag being set (installed without the meta-ebuild that is).

Only the meta.ebuild is flag dependat, others are not.

Earthwings · Post by **Earthwings** » Sat Jan 27, 2007 8:32 am

Conan wrote:http://devmanual.gentoo.org : it was written by ciaran, so i'm sure you will obtain at least a few orgasms while reading

Please change your tone. [topic=525]Guidelines[/topic]: All posts must be professional and courteous. You are free to disagree with your fellow community members. You are not free to attack, degrade, troll or malign them.

krisse · Post by **krisse** » Sat Jan 27, 2007 12:25 pm

In the earlier thread ciaran said that

paludis --uninstall sys-apps/portage will work, but it's probably not wise to do that unless you're using conf-update or some other etc-update replacement. You might want to keep Portage around for a bit anyway just to compare output if you ever run into build problems.

(my emphasis)

I'm thinking of switching to paludis, and I use dispatch-conf, so I'm wondering what the above means. If I should be worried or not.

(I've read the paludis FAQ, migration guide, browsed the wiki and stuff, but haven't seen the above mentioned anywhere else?)

mark_alec · Post by **mark_alec** » Sat Jan 27, 2007 12:53 pm

If you wish to continue using dispatch-conf, you will need to keep portage installed as it provides dispatch-conf.

Conan · Post by **Conan** » Sat Jan 27, 2007 4:33 pm

zxy wrote:
Conan wrote:SRC_URI being use-flag dependant.

Follow the logic if one of the hooks was installed without the flag being set (installed without the meta-ebuild that is).
Only the meta.ebuild is flag dependat, others are not.

Sorry then, the last time I Looked (yesterday) they were all conditional.

I'm still wondering how you managed to test on all those different archs though

luqas · Post by **luqas** » Sun Jan 28, 2007 2:00 am

What hooks directory will activate a hook during the pre portion of say paludis -pi world? Does that even exist?

I have tried putting one in install_all_pre, install_pretend_pre, and install_pre with no luck on it firing off.

Phenax · Post by **Phenax** » Sun Jan 28, 2007 4:23 am

Dryre wrote:What hooks directory will activate a hook during the pre portion of say paludis -pi world? Does that even exist?

I have tried putting one in install_all_pre, install_pretend_pre, and install_pre with no luck on it firing off.

install_ stuff is used for after compilation when it's actually installing the compiled files!

ebuild_fetch_pre and ebuild_nofetch_pre for right after it calculates dependencies
ebuild_init_pre for right after it downloads + checks digests

there might be one for before dependency calculation, but I'm in a rush to respond right now..

krisse · Post by **krisse** » Sun Jan 28, 2007 12:33 pm

mark_alec wrote:If you wish to continue using dispatch-conf, you will need to keep portage installed as it provides dispatch-conf.

Well that much, I understand. What I was wondering about, was that I understood the quote below saying that uninstalling portage isn't advisable unless you're using etc-update or some such. But it seems, then, that I understood something wrong, and that I can go on using dispatch-conf just as before? Even though I'd merge stuff with paludis, and not emerge.

not wise to do that unless you're using conf-update or some other etc-update replacement.

truc · Post by **truc** » Sun Jan 28, 2007 1:10 pm

ok, since the previous thread is looked, I can't edit my post with portage-utils changelog, so here it goes:

Code: Select all

== version 20070128 ==

# portage-utils now also support the repository_defaults.conf file 
it can read the cache, write_cache, and format keys
# little fix in the 'palsearch' script



== version 20070126 ==

# fix a little bug with the 'profiles/categories' file. This new version also
comes with a really small script: palsearch commented here:
 http://tinyurl.com/youn2x

for the whole changelog, just go here or if text file doesn't scare you, then here

And for those who doesn't know yet Ticket 8 : default configuration for repositories
and... changeset : 2308

Keep in mind that you can't set things like names_cache= ${location}/.cache/names, because location is only(should only be) defined in the repository configuration file. But it works pretty well with keys such as, distdir, eclassdirs, profiles, write_cache, format

bobobo · Post by **bobobo** » Sun Jan 28, 2007 2:36 pm

It means etc-update is part of portage. So if you uninstall portage, etc-update is uninstalled. thus you need a replacement.

floffe · Post by **floffe** » Sun Jan 28, 2007 3:13 pm

krisse wrote:Well that much, I understand. What I was wondering about, was that I understood the quote below saying that uninstalling portage isn't advisable unless you're using etc-update or some such. But it seems, then, that I understood something wrong, and that I can go on using dispatch-conf just as before? Even though I'd merge stuff with paludis, and not emerge.

In short: If you're using conf-update or something else, you can uninstall portage (even if it can be handy to have should something bad happen. Or you need to report a bug. Or... )
If you use etc-update or dispatch-conf, paludis places the config files in same place and naming scheme as portage, so they work just as before.

krisse · Post by **krisse** » Sun Jan 28, 2007 5:50 pm

floffe wrote:If you use etc-update or dispatch-conf, paludis places the config files in same place and naming scheme as portage, so they work just as before.

That's what I wanted to know! Thanks. (I figured as much, but wanted to be sure nevertheless.)

octoploid · Post by **octoploid** » Sun Jan 28, 2007 7:08 pm

Just got this error while syncing:

Code: Select all

gentoox2 xeffects # paludis -s xeffects
Sync xeffects
D    /usr/portage/local/layman/xeffects/x11-plugins/compiz-extra
svn: Failed to add directory '/usr/portage/local/layman/xeffects/profiles': object of the same name already exists

Sync error:
  * In program paludis -s xeffects:
  * When performing sync action from command line:
  * When executing sync task:
  * When syncing repository 'xeffects':
  * When syncing repository 'xeffects':
  * sync of '/usr/portage/local/layman/xeffects' from 'svn+http://svn.gentoo-xeffects.org/xeffects/trunk' failed

Sync xeffects failed

zxy · Post by **zxy** » Sun Jan 28, 2007 7:14 pm

If you are trying to sync for the first time and you want paludis to create the overlay, then you must add "x-" in front of the overlay name (no space between), like in your case

Code: Select all

# paludis -s x-xeffects

You must have a .conf file for the overlay in the /etc/paludis/repositories folder.

octoploid · Post by **octoploid** » Sun Jan 28, 2007 7:29 pm

zxy wrote:If you are trying to sync for the first time and you want paludis to create the overlay, then you must add "x-" in front of the overlay name (no space between), like in your case
Code: Select all
# paludis -s x-xeffects 
You must have a .conf file for the overlay in the /etc/paludis/repositories folder.

No. (It did always work for me until today)
They created new files in the /profiles directory (and the directory itself) today. See: http://svn.gentoo-xeffects.org/xeffects ... /ChangeLog

I solved the problem by moving the /profiles directory to a temporary location.
Then I ran layman -s xeffects and after that I copied the files from the temp location
back to /usr/portage/local/layman/xeffects/profiles .

luqas · Post by **luqas** » Sun Jan 28, 2007 7:35 pm

Is anyone using Paludis with the E17 overlay? The reason I ask is because when I have any of the E17 packages in my world file, the are masked from Paludis due to EAPI (which from my understanding is the way the ebuild is written). Thus when I try to paludis -pi world I get errors and cannot update.

If I install them via emerge --oneshot then paludis --uninstall-unused labels them as wanting to uninstall. The best way is the emerge --oneshot since doing the --uninstall-unused isn't used near as much as the -pi world

I was just curious if someone else was using it and maybe I am missing something.

If not, no biggie, as I do have workarounds.

Lance · Post by **Lance** » Sun Jan 28, 2007 8:09 pm

How to do something like

Code: Select all

emerge -uDav world

with paludis?

Thanks!

dleverton · Post by **dleverton** » Sun Jan 28, 2007 8:43 pm

Dryre wrote:Is anyone using Paludis with the E17 overlay? The reason I ask is because when I have any of the E17 packages in my world file, the are masked from Paludis due to EAPI (which from my understanding is the way the ebuild is written). Thus when I try to paludis -pi world I get errors and cannot update.

The E17 ebuilds work fine for me. I haven't tried them all, but e itself, e_modules, entropy and their deps (most of them CVS versions) seem OK. Any more specific errors? Does it show anything relevant with --log-level debug?

luqas · Post by **luqas** » Sun Jan 28, 2007 9:49 pm

dleverton wrote:
Dryre wrote:Is anyone using Paludis with the E17 overlay? The reason I ask is because when I have any of the E17 packages in my world file, the are masked from Paludis due to EAPI (which from my understanding is the way the ebuild is written). Thus when I try to paludis -pi world I get errors and cannot update.
The E17 ebuilds work fine for me. I haven't tried them all, but e itself, e_modules, entropy and their deps (most of them CVS versions) seem OK. Any more specific errors? Does it show anything relevant with --log-level debug?

This is what I get with the straight paludis -pi world.

Code: Select all

Building target list... 
Building dependency list...
Query error:
  * In Building target list... 
Building dependency list...
Query error:
  * In program paludis -pi world:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepAtom 'x11-wm/e':
  * All versions of 'x11-wm/e' are masked. Candidates are:
    * x11-wm/e-0.16.999.037::enlightenment: Masked by EAPI ( UNKNOWN ) (probably a broken ebuild)
    * x11-wm/e-9999::enlightenment: Masked by EAPI ( UNKNOWN ) (probably a broken ebuild)program

I didn't see anything stand out with --log-level debug, but I will post the last few sections that showed.

Code: Select all

  ... When adding install target 'e':
  ... When disambiguating package name 'e':
  ... When looking in repository 'virtuals':
  ... When finding category names containing package 'e':
  ... When loading names for virtuals repository:
  ... When loading virtual packages for repository 'gentoo'
  ... When loading category names for gentoo:
  ... need_category_names
paludis@1170020691: [DEBUG] In program paludis -pi --log-level debug e:
  ... When performing install action from command line:
  ... When adding install target 'e':
  ... When disambiguating package name 'e':
  ... When looking in repository 'virtuals':
  ... When finding category names containing package 'e':
  ... When loading names for virtuals repository:
  ... When loading virtual packages for repository 'gentoo'
  ... Loaded 64 virtual packages for repository 'gentoo'

Building dependency list...paludis@1170020691: [DEBUG] In program paludis -pi --log-level debug e:
  ... When performing install action from command line:
  ... When executing install task:
  ... When adding PackageDepAtom 'x11-wm/e':
  ... When fetching versions of 'x11-wm/e' in installed:
  ... When loading VDBRepository entries for 'x11-wm' from '/var/db/pkg':
  ... VDB load entries for 'x11-wm' started
paludis@1170020691: [DEBUG] In program paludis -pi --log-level debug e:
  ... When performing install action from command line:
  ... When executing install task:
  ... When adding PackageDepAtom 'x11-wm/e':
  ... When fetching versions of 'x11-wm/e' in enlightenment:
  ... When loading versions for 'x11-wm/e' in enlightenment:
  ... need_version_names 'x11-wm/e'

Query error:
  * In program paludis -pi --log-level debug e:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepAtom 'x11-wm/e':
  * All versions of 'x11-wm/e' are masked. Candidates are:
    * x11-wm/e-0.16.999.037::enlightenment: Masked by EAPI ( UNKNOWN ) (probably a broken ebuild)
    * x11-wm/e-9999::enlightenment: Masked by EAPI ( UNKNOWN ) (probably a broken ebuild)

Thanks for the help.

dleverton · Post by **dleverton** » Sun Jan 28, 2007 10:09 pm

Dryre wrote:...

Oh, I think I see what might be the problem. In your /etc/paludis/repositories/enlightenment.conf, make sure you set the eclassdirs, something like

Code: Select all

eclassdirs = /usr/portage/eclass

(or /var/paludis/repositories/gentoo/eclass, or wherever you have the main Gentoo tree).

luqas · Post by **luqas** » Sun Jan 28, 2007 10:35 pm

I really appreciate all your help on this. Here is my enlightenment.conf. I noticed that eclass thing earlier today as it was pointed to /ebuilds or something like that. I changed it, but the problem still exists.

Code: Select all

location = ${ROOT}/usr/portage/local/layman/enlightenment
sync = svn+http://overlays.gentoo.org/svn/dev/vapier/enlightenment
profiles = ${ROOT}/usr/portage/profiles/default-linux/x86/2006.1/desktop
eclassdirs = /usr/portage/eclass
distdir = /usr/portage/distfiles
format = ebuild
names_cache = ${location}/.cache/names
write_cache = /var/cache/paludis/metadata