[PALUDIS] Support thread (current v. 0.24.6) - Part 3

[KejPi]

Does it mean that there is no possibility? To use original quickpkg is not possible?

[kernelOfTruth]

Does it mean that there is no possibility? To use original quickpkg is not possible?

yeah, missing that feature too,

therefore I'm still using portage nearly full-time since installing apps with different dependencies due to paludis significantly slows down portage
in the meanwhile I also discovered pkgcore - a nice additional tool the portage-way

one "feature" I'm really missing with paludis is
emerge -e system
emerge -e world

now don't say this feature is broken by design which might be the truth - the fact is - pkgcore also support's it in some (other) way

so when can we await this "feature", mr. ciaranm, since this is the "killer feature" which might get me to move to paludis

don't say it's not necessary - how do you update your world after a major toolchain upgrade? re-install gentoo from scratch ?

response highly appreciated & if I'm missing the (already) existing feature - sorry for that "noise"

[zxy]

one "feature" I'm really missing with paludis is
emerge -e system
emerge -e world

now don't say this feature is broken by design which might be the truth - the fact is - pkgcore also support's it in some (other) way

so when can we await this "feature", mr. ciaranm, since this is the "killer feature" which might get me to move to paludis

don't say it's not necessary - how do you update your world after a major toolchain upgrade? re-install gentoo from scratch ?

response highly appreciated & if I'm missing the (already) existing feature - sorry for that "noise"

Code: Select all

paludis  -i world --dl-reinstall always

The same for system.

[Nick C]

Has anyone else tried using the novell (n4g) overlay on amd64 lately? Just tried to install groupwise and paludis has thrown this error at me:

Code: Select all

Unhandled exception:
  * In program paludis -ip novell-groupwise-gwclient:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepSpec 'net-mail/novell-groupwise-gwclient':
  * When adding package 'net-mail/novell-groupwise-gwclient-7.0.2_p20070606::n4g':
  * When parsing dependency string 'sys-libs/glibc sys-libs/libstdc++-v3 sys-devel/gcc system-jre? ( || (virtual/jdk virtual/jre) amd64? (app-emulation/emul-linux-x86-java) ) amd64? (app-emulation/emul-linux-x86-compat) ':
  * When lexing dependency string 'sys-libs/glibc sys-libs/libstdc++-v3 sys-devel/gcc system-jre? ( || (virtual/jdk virtual/jre) amd64? (app-emulation/emul-linux-x86-java) ) amd64? (app-emulation/emul-linux-x86-compat) ':
  * Bad dependency string 'sys-libs/glibc sys-libs/libstdc++-v3 sys-devel/gcc system-jre? ( || (virtual/jdk virtual/jre) amd64? (app-emulation/emul-linux-x86-java) ) amd64? (app-emulation/emul-linux-x86-compat) ': in lex phase: '(' should be followed by whitespace (paludis::DepStringLexError)

Any ideas as to the cause and if so should i report this as a bug to the paludis mailing list?

[zxy]

@Nick C: it's a borked ebuild. Spaces are needed on the places that paludis reported.

[kernelOfTruth]

Code:
paludis -i world --dl-reinstall always


The same for system.

well that was quick , thanks!

you actually tried that on your own system / world ? if yes, how did it work out?

[zxy]

Code:
paludis -i world --dl-reinstall always


The same for system.

well that was quick , thanks!

you actually tried that on your own system / world ? if yes, how did it work out?

I did it many times. It worked out as a full world recompile.

To recompile all packages do:

Code: Select all

paludis  -i everything --dl-reinstall always

[Nick C]

@Nick C: it's a borked ebuild. Spaces are needed on the places that paludis reported.

Cheers, just tried adding some and it seems to work, will report the problem to the n4g overlay

[slycordinator]

To recompile all packages do:

Code: Select all

paludis  -i everything --dl-reinstall always

One caveat:

That can upgrade stuff you don't want/need upgraded. Like if you install kde it'll install qt3. But if you do the command above it might upgrade qt to version 4 and you likely don't need that. Plus, since it's upgrading it'll remove the old version so then later when you try to upgrade something in kde it'll reinstall qt3 all over again.

[KejPi]

Does it mean that there is no possibility? To use original quickpkg is not possible?

yeah, missing that feature too,

therefore I'm still using portage nearly full-time since installing apps with different dependencies due to paludis significantly slows down portage

Seems to me that I have to return to portage too I like the speed of paludis and handling dependencies but I need this feature.

BTW: paludis messages could be more clear for people without knowledge of paludis internals. Sometimes I don't really understand where is the problem and take me some time to find it out

[kernelOfTruth]

is there another implementation of the resume command on the way ?

it seems a little ridiculous for me having to copy over a command with 1400 (!) packages on the console e.g. if a package fails during recompiling of world (== emerge -e world) - sometimes it's also not possible (e.g. if X is screwed & it "need" to scroll up output on tty - but how to do that ?)

for these cases a --skipfirst equivalent would be nice

[zxy]

is there another implementation of the resume command on the way ?

it seems a little ridiculous for me having to copy over a command with 1400 (!) packages on the console e.g. if a package fails during recompiling of world (== emerge -e world) - sometimes it's also not possible (e.g. if X is screwed & it "need" to scroll up output on tty - but how to do that ?)

for these cases a --skipfirst equivalent would be nice

And there is

Code: Select all

paludis --resume-command-template palres-XXXXXX -i some_package_or_whatever

^^ will create a file palres-XXXXXX where X-es will be substituted with random chars. That file will contain paludis's resume sommand.

[kernelOfTruth]

ah, well, thanks again zxy,

so I guess the steps are:

open saved resume-file, remove the "offending"/ failing package then resume via the file ?

does that mean execute the file?

sorry, system is heavy compiling right now so I can't test it at once

since when does paludis contain this feature?

all in all paludis looks feature-complete (TM)

[zxy]

....
since when does paludis contain this feature?
....

for a very loong time

ah, well, thanks again zxy,

so I guess the steps are:

open saved resume-file, remove the "offending"/ failing package then resume via the file ?

maybe instead of remove you can deal with why it failed (perhaps for example skip testing for that package or deal with it some other way, ...)

does that mean execute the file?

Yup

[Nick C]

im trying to get paludis to work with distcc, so far its closer to working than it was with portage however ive got one last thing to fix before all it well.
Ive set the permissions on /var/tmp/paludis as paludis says so but now distcc complains it cant access /var/tmp/paludis/.distcc, does anyone know the right way to set the correct permissions so distcc will work ok?

[slycordinator]

im trying to get paludis to work with distcc, so far its closer to working than it was with portage however ive got one last thing to fix before all it well.
Ive set the permissions on /var/tmp/paludis as paludis says so but now distcc complains it cant access /var/tmp/paludis/.distcc, does anyone know the right way to set the correct permissions so distcc will work ok?

Think it needs execute access inside just the .distcc directory.

Or if you have a regular portage install check it's distcc directory and see what kinds of permissions it has (and give /var/tmp/paludis/.distcc the same minus different owner).

[MageSlayer]

Hi, all!
I'm trying to install Lazarus from svn, but perhaps I don't know something.
So I registered lazarus repository (lazarus.conf):

Code: Select all

location = ${ROOT}/var/paludis/repositories/lazarus/
sync = svn+http://svn.freepascal.org/svn/lazarus/trunk
names_cache = ${location}/.cache/names
cache = ${ROOT}/var/empty
distdir = ${ROOT}/var/tmp/distfiles
write_cache = ${ROOT}/var/cache/paludis/metadata
format = ebuild
master_repository = gentoo

...made its directories. Synced it with:

Code: Select all

paludis --sync x-lazarus

Everything checked out ok. Now its time for ebuild? Svn does not contain any ebuilds.
Here are the questions:

1. Can I use Portage previous version ebuilds for Lazarus or svn ebuilds are somewhat different?
2. Are svn ebuilds automatically plug into paludis or I need register them?
3. Maybe some faq on paludis+svn already exists? Any links?

Thanks.

[pussi]

svn ebuilds are usually masked by missing keywod
try paludis -pi =dev-lang/lazarus-9999

[MageSlayer]

# paludis -pi =dev-lang/lazarus-9999
gives ...

Code: Select all

Building target list...
Building dependency list...
Query error:
  * In program paludis -pi =dev-lang/lazarus-9999:
  * When performing install action from command line:
  * When executing install task:
  * When adding PackageDepSpec '=dev-lang/lazarus-9999':
  * No versions of '=dev-lang/lazarus-9999' are available

Would you give some more info on that fancy syntax (9999)?

[pussi]

Would you give some more info on that fancy syntax (9999)?

well.. 9999 version is used as version almost always with live-development ebuilds.

but now that I had a closer look at your lazarus.conf, it looks like you have misunderstood something here
with that lazarus.conf you're syncing the actual lazarus development code and not any repository that would contain ebuilds for lazarus.

if you want to install lazarus from svn with paludis you should either find repository containing live svn ebuild for lazarus and sync it with paludis, find the single ebuild somewhere and put it into your local repository, or create the ebuild yourself and put it into your local repository.

If you can't find any suitable repository or the ebuild, and you have no experience on creating ebuilds its probably easier to pull and complie the svn code by hand.

[paladin151]

im trying to get paludis to work with distcc, so far its closer to working than it was with portage however ive got one last thing to fix before all it well.
Ive set the permissions on /var/tmp/paludis as paludis says so but now distcc complains it cant access /var/tmp/paludis/.distcc, does anyone know the right way to set the correct permissions so distcc will work ok?

Try changing ownership to paludisbuild:paludisbuild and also make sure the directory exists.

[tekknokrat]

Hi all,

What I want to do is to use suspend2-sources or xen-sources (from marineam) as my one and only kernel sources.

Problem is that gentoo-sources is the default sources in server/desktop profile and is emerged on module packages / X / some other libs as dep.

In portage I can use profile/package-provided to tell it on update world to ignore updating / re-emerging of gentoo-sources.

How do I do that in paludis? Masking gentoo-sources byversion / completely would not be an solution.

Do I need to create a new / modify an existing profile file?

BTW. is there any effort that ebuilds will take generic kernels as a dependency (independent of package name virtual/kernel) or is it yet done in this way?

[slycordinator]

Hi all,

What I want to do is to use suspend2-sources or xen-sources (from marineam) as my one and only kernel sources.

Problem is that gentoo-sources is the default sources in server/desktop profile and is emerged on module packages / X / some other libs as dep.

In portage I can use profile/package-provided to tell it on update world to ignore updating / re-emerging of gentoo-sources.

There is absolutely no need to use package.provided to get what you want (even using portage).

All you have to do is install whatever kernel sources you want before trying to install those modules.

For instance, lets say I want to use the current alsa-driver instead of what's provided in kernel AND I want suspend2-sources.

I just do

Code: Select all

paludis -i suspend2-sources

Then later I do

Code: Select all

paludis -i alsa-driver

BTW. is there any effort that ebuilds will take generic kernels as a dependency (independent of package name virtual/kernel) or is it yet done in this way?

WTF are you talking about? virtual/kernel IS A GENERIC KERNEL.

Every properly written kernel source ebuild has that package providing virtual/kernel. So if a package depends on virtual/kernel it's taken as meaning "All I care about is that ANY kernel source is installed."

So once you install any kernel source you also have virtual/kernel. It just happens that if you DON'T install a kernel source, then try to install something that depends on virtual/kernel it defaults to gentoo-sources.

[tekknokrat]

thanks for enlighten me.

Quote:
BTW. is there any effort that ebuilds will take generic kernels as a dependency (independent of package name virtual/kernel) or is it yet done in this way?

WTF are you talking about? virtual/kernel IS A GENERIC KERNEL.

I missed an as in the brackets so independent of packages name as e.g. virtual/kernel.
I now had a look in some ebuild the correct name of the virtual package is virtual/linux-source

[slycordinator]

I missed an as in the brackets so independent of packages name as e.g. virtual/kernel.
I now had a look in some ebuild the correct name of the virtual package is virtual/linux-source

I have no idea what your first sentence means. It seems that you were originally asking if we could make it take a kernel as a dependency independent of both package names and virtual/linux-sources.

And yes, every kernel's ebuild provides virtual/linux-sources

Code: Select all

$ grep linux-sources /usr/portage/eclass/kernel-2.eclass 
        PROVIDE="virtual/linux-sources"