[PALUDIS] Support thread (current v. 0.26.*) - Part 4

[nivw]

I am tring to install the tbz2 file of the coreutils

[Knute]

Manually installing a package means that you unpack the tbz2 (or whatever format the package is in), then manually compile and install it.

[slycordinator]

I'm confused as to how you were able to install a new version of coreutils with portage/emerge and have it leave the old version intact.

If you really have the newest version installed then you should be able to safely remove both the old version and mktemp (since everything that mktemp provides is part of the new coreutils).

And the fact that paludis segfaults is probably not related to this.

[tecknojunky]

Code: Select all

holy_fire ~ # ls /var/paludis/repositories/paludis-overlay/sys-apps/paludis 
files  paludis-0.24.6.ebuild  paludis-0.26.0_alpha13.ebuild  paludis-0.26.0_alpha14.ebuild  paludis-0.26.0_pre1.ebuild  paludis-scm.ebuild

Really. Its not there. Kill the manifest already.

That's strange. Here is what I have:

Code: Select all

$ ls /var/paludis/repositories/paludis-overlay/sys-apps/paludis/
files                  paludis-0.24.5.ebuild          paludis-0.26.0_alpha2.ebuild
Manifest               paludis-0.24.6.ebuild          paludis-0.26.0_alpha3.ebuild
paludis-0.22.1.ebuild  paludis-0.26.0_alpha13.ebuild  paludis-0.26.0_alpha4.ebuild
paludis-0.22.2.ebuild  paludis-0.26.0_alpha14.ebuild  paludis-0.26.0_pre1.ebuild
paludis-0.24.2.ebuild  paludis-0.26.0_alpha1.ebuild   paludis-scm.ebuild

[slycordinator]

Pretty much every file you listed there no longer exists in the official repository/overlay. How are you updating your overlay? It would seem you aren't using "paludis --sync" otherwise the files that aren't in the upstream repo would've been deleted already.

[sotn3m]

I don't really see the relation with my problem; I am not using paludis overlay, but portage version of paludis..

m4 package can't be installed still; I can't upgrade paludis or coreutils to do that, because they depend on m4 and the vicious circle ends...

[slycordinator]

I don't really see the relation with my problem; I am not using paludis overlay, but portage version of paludis..

No one implied that it was related to your problem.

We were responding to someone who said paludis complains that the new version of paludis isn't in the Manifest (when in reality the paludis overlay doesn't even have a Manifest).

m4 package can't be installed still; I can't upgrade paludis or coreutils to do that, because they depend on m4 and the vicious circle ends...

I believe a simple workaround would be:
1) Mask the new version of m4 (the version you can't get installed that has an lzma file).
2) Do "paludis -i1 coreutils" which should install the new version of coreutils that supports lzma.
3) Remove the mask from earlier
4) Upgrade m4

[phoenix_me]

I have a problem installing paludis from portage

Code: Select all

[ebuild  N    ] sys-apps/paludis-0.26.0_pre2  USE="bash-completion inquisitio python visibility -doc -glsa -pink -portage -qa -ruby -vim-syntax -zsh-completion" 0 kB ....

...checking for boost.python... no
configure: error: boost.python (http://www.boost.org/libs/python/doc/) is required

of course boost is installed

Code: Select all

emerge -vp boost

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] dev-libs/boost-1.34.1-r2  USE="-debug -doc -icu -pyste -tools" 0 kB 

Total: 1 package (1 reinstall), Size of downloads: 0 kB

[mikkoc]

I have a problem installing paludis from portage

Code: Select all

[ebuild  N    ] sys-apps/paludis-0.26.0_pre2  USE="bash-completion inquisitio python visibility -doc -glsa -pink -portage -qa -ruby -vim-syntax -zsh-completion" 0 kB ....

...checking for boost.python... no
configure: error: boost.python (http://www.boost.org/libs/python/doc/) is required

See page 11 of this thread

[Dr.Willy]

I recently noticed that my paludis has a little problem with some packages i have installed (or not)

Code: Select all

~ # paludis -r
Current state of the system

* dev-java/asm-3.0::installed NOT OK
    Not used by any package in world

* dev-java/javacc-4.0-r4::installed NOT OK
    Not used by any package in world

* dev-java/lucene-2.3.1:2.3::installed NOT OK
    Not used by any package in world

* dev-java/tomcat-servlet-api-6.0.16:2.5::installed NOT OK
    Not used by any package in world

Finished processing 644 packages. 4 errors.

~ # paludis --uninstall-unused
Building unmerge list... done

These packages will be uninstalled:

* dev-java/asm-3.0::installed
* dev-java/javacc-4.0-r4::installed
* dev-java/lucene-2.3.1:2.3::installed
* dev-java/tomcat-servlet-api-6.0.16:2.5::installed


Total: 4 packages

[...]

~ # paludis -pi everything
Building target list...
Building dependency list...

These packages will be installed:

* dev-java/asm :3 [S 3.0] <everything>
    -doc -source elibc: (-FreeBSD)
* dev-java/javacc [N 4.0-r4]
    Reasons: *dev-java/lucene-2.3.1:2.3::gentoo
    "Java Compiler Compiler - The Java Parser Generator"
    -doc -examples -source -test elibc: (-FreeBSD)
* dev-java/lucene :2.3 [S 2.3.1] <everything>
    -doc -source -test elibc: (-FreeBSD)
* dev-java/tomcat-servlet-api :2.5 [S 6.0.16] <everything>
    -source elibc: (-FreeBSD)

Total: 4 packages (1 new, 3 in new slots)

Does anyone have an idea what causes this behaviour and why paludis wants to pull them?

[slycordinator]

Because "paludis -i world" and "paludis -i everything" behave differently.

The former looks at the world file. The latter looks at everything installed in /var/db/pkg

So if you have some stuff installed that you don't need/want then using the everything set will guarantee that the stuff stays.

[Dr.Willy]

Because "paludis -i world" and "paludis -i everything" behave differently.

The former looks at the world file. The latter looks at everything installed in /var/db/pkg

So if you have some stuff installed that you don't need/want then using the everything set will guarantee that the stuff stays.

Ah, ok.
So I have say dev-java/asm installed as a dependency

Code: Select all

~ $ equery d dev-java/asm
[ Searching for packages depending on dev-java/asm... ]
dev-java/jarjar-0.9 (=dev-java/asm-2.0*)

then 'paludis -i everything' updates it to the newest version available and 'paludis --uninstall-unused' removes it again, because it is not needed ... right?

That brings up the question how I update world + all dependencies without installing useless packages. The paludis faq suggests setting --dl-installed-deps-pre to ... ?

[slycordinator]

That brings up the question how I update world + all dependencies without installing useless packages. The paludis faq suggests setting --dl-installed-deps-pre to ... ?

I use

Code: Select all

paludis -i world --dl-upgrade always --dl-reinstall if-use-changed --dl-installed-deps-pre pre-or-post

[phoenix_me]

I have a problem installing paludis from portage

Code: Select all

[ebuild  N    ] sys-apps/paludis-0.26.0_pre2  USE="bash-completion inquisitio python visibility -doc -glsa -pink -portage -qa -ruby -vim-syntax -zsh-completion" 0 kB ....

...checking for boost.python... no
configure: error: boost.python (http://www.boost.org/libs/python/doc/) is required

See page 11 of this thread

Thank you.
In my case it was gcc-4.3.0 (paludis don't like it ) and Python2.5, (looks like paludis need to have 2.4).

[Finswimmer]

Is it possible to stop showing this warning: [QA version_spec.too_long]

Thanks
Tobi

[phoenix_me]

Can someone tell me what is paludis equivalent for
emerge --resume --skip-first

//edit

already have answer

There is no such thing because --skipfirst is an utterly broken concept.

--continue-on-failure if-independent is miles better, but unfortunately its currently borken (there's an open ticket and its a blocker for 0.26 final).

[slycordinator]

Is it possible to stop showing this warning: [QA version_spec.too_long]

Thanks
Tobi

That probably will not be displayed when you specify "--log-level warning". Not sure though.

[phoenix_me]

I am using sajinet overlay. It sync ok, but in ./profiles directory there is no repo_name file. Because of that paludis is giving this repository a x-sajinet name.
But every time it sync an overlay it shows me:

Code: Select all

 * Done cleaning write cache for ebuild format repositories
paludis@1208627156: [QA e.repo_name.unusable] Couldn't open repo_name file in '/usr/portage/overlays/sajinet/profiles/', falling back to generated name 'x-sajinet' (ignore this message if you have yet to sync this repository).

I have 10 files *.conf (repositories configuration files) and this message is show to me 10 times after syncing.

Will it be enough if owner of the repository will add a repo_name file (in profiles dir) to his repository?

//edit

I ask the owner of overaly for creation of repo_name file, he did it and now paludis is not complain anymore.

[phoenix_me]

Isn't it an error of paludis.

Code: Select all

paludis -ip gentoo-sources

Building dependency list...

These packages will be installed:

* sys-kernel/gentoo-sources :2.6.25-r1 [S 2.6.25-r1] <target>
    -build symlink
    43.08 kBytes to download

Total: 1 package (1 in new slot), at most 43.08 kBytes to download

 * No unread news items found

As I read output in good way, paludis want to download 43.08 kBytes and install gentoo-sources 2.6.25-r1 which is already installed. While this is not true. Because last installed version it's gentoo-sources-2.6.25 which paludis was installed yesterday!

Code: Select all

ls -la /usr/src/
razem 7
drwxr-xr-x  8 root root  272 kwi 19 00:24 .
drwxr-xr-x 18 root root 4096 kwi 18 23:12 ..
-rw-r--r--  1 root root    0 lut 14  2006 .keep
lrwxrwxrwx  1 root root   19 kwi 19 00:24 linux -> linux-2.6.25-gentoo
drwxr-xr-x 19 root root 1200 kwi 19 00:20 linux-2.6.24-gentoo-r3
drwxr-xr-x 21 root root 1448 kwi 17 16:10 linux-2.6.24-gentoo-r5
drwxr-xr-x 21 root root  752 kwi 19 00:24 linux-2.6.25-gentoo
drwx------  2 root root   48 paź  7  2006 .reiserfs_priv
drwxr-xr-x  7 root root  168 cze  4  2007 rpm

[loftwyr]

It has to re-download the gentoo-patches file portion as they had to fix up a number of the patches to work with 2.6.25 properly.

[slycordinator]

Isn't it an error of paludis.

Code: Select all

paludis -ip gentoo-sources

Building dependency list...

These packages will be installed:

* sys-kernel/gentoo-sources :2.6.25-r1 [S 2.6.25-r1] <target>
    -build symlink
    43.08 kBytes to download

Total: 1 package (1 in new slot), at most 43.08 kBytes to download

 * No unread news items found

As I read output in good way, paludis want to download 43.08 kBytes and install gentoo-sources 2.6.25-r1 which is already installed. While this is not true. Because last installed version it's gentoo-sources-2.6.25 which paludis was installed yesterday!

Code: Select all

ls -la /usr/src/
razem 7
drwxr-xr-x  8 root root  272 kwi 19 00:24 .
drwxr-xr-x 18 root root 4096 kwi 18 23:12 ..
-rw-r--r--  1 root root    0 lut 14  2006 .keep
lrwxrwxrwx  1 root root   19 kwi 19 00:24 linux -> linux-2.6.25-gentoo
drwxr-xr-x 19 root root 1200 kwi 19 00:20 linux-2.6.24-gentoo-r3
drwxr-xr-x 21 root root 1448 kwi 17 16:10 linux-2.6.24-gentoo-r5
drwxr-xr-x 21 root root  752 kwi 19 00:24 linux-2.6.25-gentoo
drwx------  2 root root   48 paź  7  2006 .reiserfs_priv
drwxr-xr-x  7 root root  168 cze  4  2007 rpm

It would be helpful to show the output of the paludis command; maybe you're misunderstanding what it's displaying?

[creidiki]

The main tree has silent package changes, and paludis uses the tree ebuild when you do a -pi. Get used to it

[slycordinator]

The main tree has silent package changes, and paludis uses the tree ebuild when you do a -pi. Get used to it

I think what he's trying to say is that paludis CLAIMS the package (version 2.6.25-r1) is installed already when it is not (note how he said the latest version he installed was 2.6.25 and not 2.6.25-r1).

AFAIK,

1) There was no "silent add" of anything in this case
2) 2.6.25-r1 was created because 2.6.25 had a bad patch that failed on all x86/32-bit boxes

So again, phoenix_me show us the output of paludis

[firefly]

Isn't it an error of paludis.

Code: Select all

paludis -ip gentoo-sources

Building dependency list...

These packages will be installed:

* sys-kernel/gentoo-sources :2.6.25-r1 [S 2.6.25-r1] <target>
    -build symlink
    43.08 kBytes to download

Total: 1 package (1 in new slot), at most 43.08 kBytes to download

 * No unread news items found

As I read output in good way, paludis want to download 43.08 kBytes and install gentoo-sources 2.6.25-r1 which is already installed. While this is not true. Because last installed version it's gentoo-sources-2.6.25 which paludis was installed yesterday!

Huh, the output doesn't say that gentoo-sources-2.6.25-r1 is installed. The output say that this version gets installed in a different slot. There is a "S" (Slotted) instead a "R"(Reinstall) in the "[]"

[Rion]

i'm to lazy to read all 12 pages.. and i've not found answer in faq or bug tracker..

how to disable bunch of warnings i get on every time i use paludis

Code: Select all

Building target list... paludis@1208868056: [QA version_spec.too_long] In program paludis -i kwin:
  ... When performing install action from command line:                                           
  ... When adding install target 'kwin':                                                          
  ... When disambiguating package name 'kwin':                                                    
  ... When finding category names containing package 'kwin':                                      
  ... When loading names for virtuals repository:                                                 
  ... When finding provided packages for 'installed':                                             
  ... When loading VDB PROVIDEs map the slow way:                                                 
  ... When loading package names from '/var/db/pkg' in category 'media-libs':                     
  ... When parsing package dep spec '=media-libs/libcaptury-0.3.0_pre200712251':                  
  ... When parsing version spec '0.3.0_pre200712251':
  ... Number part '200712251' exceeds 8 digit limit permitted by the Package Manager Specification (Paludis supports arbitrary lengths, but other package managers do not)
paludis@1208868056: [QA version_spec.too_long] In program paludis -i kwin:
  ... When performing install action from command line:
  ... When adding install target 'kwin':
  ... When disambiguating package name 'kwin':
  ... When finding category names containing package 'kwin':
  ... When loading names for virtuals repository:
  ... When finding provided packages for 'installed':
  ... When loading VDB PROVIDEs map the slow way:
  ... When loading package names from '/var/db/pkg' in category 'media-libs':
  ... When parsing package dep spec '=media-libs/capseo-0.3.0_pre200712251-r1':
  ... When parsing version spec '0.3.0_pre200712251-r1':
  ... Number part '200712251' exceeds 8 digit limit permitted by the Package Manager Specification (Paludis supports arbitrary lengths, but other package managers do not)
paludis@1208868057: [QA version_spec.too_long] In program paludis -i kwin:
  ... When performing install action from command line:
  ... When adding install target 'kwin':
  ... When disambiguating package name 'kwin':
  ... When finding category names containing package 'kwin':
  ... When loading names for virtuals repository:
  ... When finding provided packages for 'installed':
  ... When loading VDB PROVIDEs map the slow way:
  ... When loading package names from '/var/db/pkg' in category 'sys-apps':
  ... When parsing package dep spec '=sys-apps/net-tools-1.60_p20071202044231-r1':
  ... When parsing version spec '1.60_p20071202044231-r1':
  ... Number part '20071202044231' exceeds 8 digit limit permitted by the Package Manager Specification (Paludis supports arbitrary lengths, but other package managers do not)

i know there are ebuilds with invalid names in portage and i don't want to see these warnings every time