QA: Cannot run Portage trigger for equo,entropy [Solved]

Anything that pertains to Entropy, Equo or Sulfur

Moderator: Moderators

QA: Cannot run Portage trigger for equo,entropy [Solved]

Postby ReemZ » Thu Aug 20, 2009 23:40

After a successful 'equo update', here's what happened:

Code: Select all
Sm0kerZ-ParadiZe ~ # equo --version
Equo: v0.98.2.4
(I always check version before installing a new Entropy)

Code: Select all
Sm0kerZ-ParadiZe ~ # equo install equo --ask
>>
>>
>>  !!! Please update the following critical packages:
>>      # >=sys-apps/entropy-0.98.0.2
>>  !!! You should install them as soon as possible
>>
Update entropy-0.98.0.2? It's actually 0.98.2.4-r2 (prior to update, obviously) :lol:
Anyway, the story continues:
Code: Select all
>>
>>  @@ These are the chosen packages:
>>    # (1/1) app-admin/equo-0.98.4.2 >>> Sabayon Linux Official Repository
>>      Versions:        0.98.2.4 / NoTag / 0 ===> 0.98.4.2 / NoTag / 0
>>      Action:          Upgrade
>>  @@ Packages involved: 1
     Would you like to continue with dependencies calculation ? [Yes/No] y
>>  @@ Calculating dependencies ...
>>  @@ These are the packages that would be installed:
>>  ## [U] [sabayonlinux.org] sys-apps/entropy-0.98.4.2|0   [0.98.2.4-r2|0]
>>  ## [U] [sabayonlinux.org] app-admin/equo-0.98.4.2|0   [0.98.2.4|0]
>>  @@ Packages needing to be installed/updated/downgraded: 2
>>  @@ Packages needing to be removed: 0
>>  @@ Packages needing to be installed: 0
>>  @@ Packages needing to be reinstalled: 0
>>  @@ Packages needing to be updated: 2
>>  @@ Packages needing to be downgraded: 0
>>  @@ Download size: 677.1kB
>>  @@ Used disk space: 127.9kB
>>  @@ You need at least: 1.4MB of free space
     Would you like to execute the queue ? [Yes/No] y
>>  :: (1/2) >>> sys-apps/entropy-0.98.4.2
>>    ## Downloading archive: sys-apps:entropy-0.98.4.2~0.tbz2
>>    ## ( mirror #1 ) Downloading from: na.mirror.garr.it
>>    ## ( mirror #1 ) Successfully downloaded from: na.mirror.garr.it at 486.4kB/second
>>    ## Package checksum matches: sys-apps:entropy-0.98.4.2~0.tbz2
>>       : SHA1 matches
>>       : SHA256 matches
>>       : SHA512 matches
>>  :: (2/2) >>> app-admin/equo-0.98.4.2
>>    ## Downloading archive: app-admin:equo-0.98.4.2~0.tbz2
>>    ## ( mirror #1 ) Downloading from: na.mirror.garr.it
>>    ## ( mirror #1 ) Successfully downloaded from: na.mirror.garr.it at 0.0b/second
>>    ## Package checksum matches: app-admin:equo-0.98.4.2~0.tbz2
>>       : SHA1 matches
>>       : SHA256 matches
>>       : SHA512 matches
>>  ++ (1/2) >>> sys-apps/entropy-0.98.4.2
>>    ## Unpacking package: sys-apps:entropy-0.98.4.2~0.tbz2
>>    ## Ebuild: pkg_preinst()
>>    ## QA: Cannot run Portage trigger for sys-apps/entropy-0.98.4.2. Please report it. Attach this: /var/log/entropy/spm.log
>>    ## Ebuild: pkg_postrm()
Traceback (most recent call last):
  File "/usr/lib/entropy/libraries/entropy/client/interfaces/trigger.py", line 873, in trigger_ebuild_postremove
    portage_tmpdir = etpConst['entropyunpackdir']+"/"+portage_atom
  File "/usr/lib/entropy/libraries/entropy/spm.py", line 1598, in spm_doebuild
    return self._portage_doebuild(myebuild, mydo, tree, cpv, portage_tmpdir, licenses)
  File "/usr/lib/entropy/libraries/entropy/spm.py", line 1700, in _portage_doebuild
    mysettings["PORTDIR"] = portdir
  File "//usr/lib/portage/pym/portage/__init__.py", line 2845, in __setitem__
    raise ValueError("Invalid type being used as a value: '%s': '%s'" % (str(mykey),str(myvalue)))
ValueError: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/sys-apps/entropy-0.98.2.4-r2/portdir'
>>    ## QA: Cannot run Portage trigger for sys-apps/entropy-0.98.2.4-r2. Please report it. Attach this: /var/log/entropy/spm.log
>>    ## Installing package: sys-apps/entropy-0.98.4.2
>>    ## [Official Sabayon Linux Package Manager library]
>>    ## Protecting config file: /etc/entropy/fsdirsmask.conf
>>    ## Automerging config file, never modified: /etc/entropy/fsdirsmask.conf
>>    ## Protecting config file: /etc/entropy/packages/package.keywords.example
>>    ## Automerging config file, never modified: /etc/entropy/packages/package.keywords.example
>>    ## Updating database: sys-apps/entropy-0.98.4.2
>>    ## Cleaning old package files...
>>    ## Ebuild: pkg_postinst()
>>    ## QA: Cannot run Portage trigger for sys-apps/entropy-0.98.4.2. Please report it. Attach this: /var/log/entropy/spm.log
>>    ## Updating {conf.d,init.d} mtime ...
>>    ## Updating environment ...
>>    ## Cleaning: sys-apps/entropy-0.98.4.2
>>  ++ (2/2) >>> app-admin/equo-0.98.4.2
>>    ## Unpacking package: app-admin:equo-0.98.4.2~0.tbz2
>>    ## Ebuild: pkg_postrm()
Traceback (most recent call last):
  File "/usr/lib/entropy/libraries/entropy/client/interfaces/trigger.py", line 873, in trigger_ebuild_postremove
    )
  File "/usr/lib/entropy/libraries/entropy/spm.py", line 1598, in spm_doebuild
    # cpv = atom
  File "/usr/lib/entropy/libraries/entropy/spm.py", line 1700, in _portage_doebuild

  File "//usr/lib/portage/pym/portage/__init__.py", line 2845, in __setitem__
    raise ValueError("Invalid type being used as a value: '%s': '%s'" % (str(mykey),str(myvalue)))
ValueError: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/app-admin/equo-0.98.2.4/portdir'
>>    ## QA: Cannot run Portage trigger for app-admin/equo-0.98.2.4. Please report it. Attach this: /var/log/entropy/spm.log
>>    ## Installing package: app-admin/equo-0.98.4.2
>>    ## [Official Sabayon Linux Package Manager Client]
>>    ## Updating database: app-admin/equo-0.98.4.2
>>    ## Cleaning old package files...
>>    ## Ebuild: pkg_postinst()
>>    ## QA: Cannot run Portage trigger for app-admin/equo-0.98.4.2. Please report it. Attach this: /var/log/entropy/spm.log
>>    ## Cleaning: app-admin/equo-0.98.4.2
>>  @@ Installation complete.
>>  @@ Caching complete.
Hmm, now there's a message new to me, Portage.......trigger........?
Better check if Entropy and equo were actually updated...
Code: Select all
Sm0kerZ-ParadiZe ~ # equo --version
Equo: v0.98.4.2

>>      @@ Package: app-admin/equo-0.98.4.2             branch: 4
>>        Available:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0
>>        Installed:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0

>>      @@ Package: sys-apps/entropy-0.98.4.2           branch: 4
>>        Available:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0
>>        Installed:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0


As you can see, Entropy and equo have been properly updated, and I realize that above messages could very well fall in the same category as 'You should run revdep-rebuild' (i.e.: ignore-this-if-using-entropy), but I'm not absolutely sure and would like to check.

I would have attached /var/log/entropy/spm.log, had it existed on my system, but the only file in /var/log/entropy is equo.log, of which todays entry is this:
Code: Select all
* [23:34:32 20/08/2009 CEST] [ INFO ] [client] Unpacking package: sys-apps/entropy-0.98.4.2
* [23:34:33 20/08/2009 CEST] [ INFO ] [client] [PRE] ATTENTION Cannot run Gentoo preinst trigger for sys-apps/entropy-0.98.4.2!! <type 'exceptions.Exception'>: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/packages/x86/4/sys-apps:entropy-0.98.4.2~0.tbz2/portdir'
* [23:34:33 20/08/2009 CEST] [ INFO ] [client] [PRE] ATTENTION Cannot run Gentoo postremove trigger for sys-apps/entropy-0.98.2.4-r2!! <type 'exceptions.Exception'>: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/sys-apps/entropy-0.98.2.4-r2/portdir'
* [23:34:33 20/08/2009 CEST] [ INFO ] [client] Installing package: sys-apps/entropy-0.98.4.2
* [23:34:34 20/08/2009 CEST] [ INFO ] [client] Protecting config file: /etc/entropy/fsdirsmask.conf
* [23:34:34 20/08/2009 CEST] [ INFO ] [client] Protecting config file: /etc/entropy/packages/package.keywords.example
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Remove old package: sys-apps/entropy-0.98.2.4-r2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Removing Entropy and Spm database entry for sys-apps/entropy-0.98.2.4-r2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Removing package: sys-apps/entropy-0.98.2.4-r2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Removing from Spm: sys-apps/entropy-0.98.2.4-r2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Installing new Spm database entry: sys-apps/entropy-0.98.4.2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] Not updating Portage world file for: sys-apps/entropy-0.98.4.2
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] [POST] ATTENTION Cannot run Portage trigger for sys-apps/entropy-0.98.4.2!! <type 'exceptions.Exception'>: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/packages/x86/4/sys-apps:entropy-0.98.4.2~0.tbz2/portdir'
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] [POST] Updating {conf.d,init.d} mtime...
* [23:34:37 20/08/2009 CEST] [ INFO ] [client] [POST] Running env-update
* >>>  Purging current Entropy cache
* >>>  WARN: postinst
* >>>  No files to compile!
* [23:34:38 20/08/2009 CEST] [ INFO ] [client] Unpacking package: app-admin/equo-0.98.4.2
* [23:34:38 20/08/2009 CEST] [ INFO ] [client] [PRE] ATTENTION Cannot run Gentoo postremove trigger for app-admin/equo-0.98.2.4!! <type 'exceptions.Exception'>: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/app-admin/equo-0.98.2.4/portdir'
* [23:34:38 20/08/2009 CEST] [ INFO ] [client] Installing package: app-admin/equo-0.98.4.2
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] Remove old package: app-admin/equo-0.98.2.4
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] Removing Entropy and Spm database entry for app-admin/equo-0.98.2.4
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] Removing package: app-admin/equo-0.98.2.4
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] Removing from Spm: app-admin/equo-0.98.2.4
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] Installing new Spm database entry: app-admin/equo-0.98.4.2
* [23:34:39 20/08/2009 CEST] [ INFO ] [client] [POST] ATTENTION Cannot run Portage trigger for app-admin/equo-0.98.4.2!! <type 'exceptions.Exception'>: Invalid type being used as a value: 'PORTDIR': '/var/tmp/entropy/packages/x86/4/app-admin:equo-0.98.4.2~0.tbz2/portdir'


Googled, found nothing useful.
Is there anything else I should look into, or can I simply ignore that message (I'm not calling it an error as I'm not sure that it is one) and live on?
Last edited by ReemZ on Mon Sep 21, 2009 21:41, edited 1 time in total.
Handtekening? Zeg...ik ga niet op m'n monitor schrijven!
ReemZ
Old Dear Hen
 
Posts: 701
Joined: Mon Oct 27, 2008 10:50
Location: Here! No, here! Over heeeeeeere!

Re: QA: Cannot run Portage trigger for equo,entropy

Postby albfneto » Fri Aug 21, 2009 23:18

This is, because if you mixed the installers, entropy and portage..
entropy suggests DOWNGRADED packages as update.
For solve this, you can sincronize portage with entropy..., then update portage first and entropy after, and not USE PORTAGE FOR INSTALL ENTROPY.
make these commands, following their sequence:

Code: Select all
su
gedit (or kwrite, nano, an editor) /etc/entropy/client.conf
in last line of the file, in wich you see.... dowgrades etc....
substitute "disable" by "enable" and save the file.. then made:

su
emerge --sync
emerge -s portage (for see the last version)
emerge -av portage
emerge layman
layman -d sabayon
layman -a sabayon
layman -S
equo update
equo install equo ( never use emerge equo)
equo install entropy sulfur magneto
equo search entropy
equo database gentoosync


after all running... you may check using:

Code: Select all
emerge -s equo && equo search equo
the versions should be the same....
emerge -s portage && equo search portage
the versions of portage in equo and portage itself may be the same or the EQUO VERSION NEWER

(because some very new portage versions of the portage itself are HARDMASKED in Portage!)


the equivalent of "rev-dep rebuild" command of the Portage is in Entropy: equo deptest && equo libtest.
ALBERTO FEDERMAN NETO
albfneto
[email protected]
Favorite Distros: Sabayon, Gentoo, Mageia and OpenSUSE
User avatar
albfneto
Sagely Hen
 
Posts: 1728
Joined: Fri Nov 16, 2007 1:15
Location: Ribeirão Preto City, São Paulo State, Brazil

Re: QA: Cannot run Portage trigger for equo,entropy

Postby ReemZ » Sat Aug 22, 2009 0:25

albfneto wrote:This is, because if you mixed the installers, entropy and portage..
entropy suggests DOWNGRADED packages as update.
For solve this, you can sincronize portage with entropy..., then update portage first and entropy after, and not USE PORTAGE FOR INSTALL ENTROPY.
make these commands, following their sequence:

I've only mixed them once, for one package, no dependencies, and that was a month or two ago, with both Portage and Entropy updated, after which I did an 'equo database gentoosynch' which was successful.
I 'equo update' every day, as soon as a new version of Entropy/equo is available I install it, and I don't update/upgrade anything else. Ow, and I never installed/updated Entropy/equo via Portage, always use equo.
Can't see how this would be the cause...

albfneto wrote:
Code: Select all
su
gedit (or kwrite, nano, an editor) /etc/entropy/client.conf
in last line of the file, in wich you see.... dowgrades etc....
substitute "disable" by "enable" and save the file.. then made:

This one:
Code: Select all
ignore-spm-downgrades|disable
?

albfneto wrote:
Code: Select all
su
emerge --sync
emerge -s portage (for see the last version)
emerge -av portage
emerge layman
layman -d sabayon
layman -a sabayon
layman -S
equo update
equo install equo ( never use emerge equo)
equo install entropy sulfur magneto
equo search entropy
equo database gentoosync

I'll check into this tomorrow, thanks ;)
Sidenote: I won't install Sulfur or Magneto, as I never use a graphical package manager and I don't need the nuisance of a notification applet (since I normally do not update applications unless absolutely necessary)

albfneto wrote:after all running... you may check using:

Code: Select all
emerge -s equo && equo search equo
the versions should be the same....

emerge -s portage && equo search portage
the versions of portage in equo and portage itself may be the same or the EQUO VERSION NEWER

(because some very new portage versions of the portage itself are HARDMASKED in Portage!)


Without editing /etc/entropy/client.conf or running the Entropy/Portage update routine:
Code: Select all
*  app-admin/equo
      Latest version installed: 0.98.4.2
      Homepage:      http://www.sabayon.org
      Description:   Official Sabayon Linux Package Manager Client
      License:       GPL-2


>>  @@ Searching...
>>   #1 Sabayon Linux Official Repository
>>      @@ Package: app-admin/equo-0.98.4.2             branch: 4
>>        Available:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0
>>        Installed:            version: 0.98.4.2 ~ tag: NoTag ~ revision: 0
>>        Slot:                 0
As you can see, perfectly up-to-date.

Code: Select all
*  sys-apps/portage
      Latest version available: 2.1.6.13
      Latest version installed: 2.2_rc14
      Size of files: 732 kB
      Homepage:      http://www.gentoo.org/proj/en/portage/index.xml
      Description:   Portage is the package management and distribution system for Gentoo
      License:       GPL-2


>>  @@ Searching...
>>   #1 Sabayon Linux Official Repository
>>      @@ Package: sys-apps/portage-2.2_rc33           branch: 4
>>        Available:            version: 2.2_rc33 ~ tag: NoTag ~ revision: 0
>>        Installed:            version: 2.2_rc14 ~ tag: NoTag ~ revision: 0
>>        Slot:                 0
>>        Homepage:             http://www.gentoo.org/proj/en/portage/index.xml
>>        Description:          Portage is the package management
>>                              and distribution system for Gentoo
>>        License:              GPL-2
Seems a bit messy, but it shouldn't be a problem as I *never* use Portage anyway.
Just to check:
Code: Select all
Sm0kerZ-ParadiZe reemz # emerge --version
 * Overlay eclass overrides eclass from PORTDIR:
 *
 *   '/usr/local/portage/layman/sabayon/eclass/mozcoreconf-2.eclass'
 *
 * It is best to avoid overriding eclasses from PORTDIR because it will
 * trigger invalidation of cached ebuild metadata that is distributed with
 * the portage tree. If you must override eclasses from PORTDIR then you
 * are advised to add FEATURES="metadata-transfer" to /etc/make.conf and to
 * run `emerge --regen` after each time that you run `emerge --sync`. Set
 * PORTAGE_ECLASS_WARNING_ENABLE="0" in /etc/make.conf if you would like to
 * disable this warning.
Portage 2.2_rc14 (default/linux/x86/2008.0/desktop, gcc-4.3.2, glibc-2.8_p20080602-r1, 2.6.27-sabayon i686)


albfneto wrote:the equivalent of "rev-dep rebuild" command of the Portage is in Entropy: equo deptest && equo libtest.

I know, that wasn't the question, it was an example of messages in equo that are actually Portage-messages, which should be ignored when using equo, as I do ;)

Simply put, my question is this:
Is 'QA: Cannot run Portage trigger for ...' a Portage message (meaning I can ignore it) or not?
Handtekening? Zeg...ik ga niet op m'n monitor schrijven!
ReemZ
Old Dear Hen
 
Posts: 701
Joined: Mon Oct 27, 2008 10:50
Location: Here! No, here! Over heeeeeeere!

Re: QA: Cannot run Portage trigger for equo,entropy

Postby ReemZ » Wed Sep 16, 2009 4:08

Exactly the same BS today, could anyone please confirm to me I can ignore that message?
Handtekening? Zeg...ik ga niet op m'n monitor schrijven!
ReemZ
Old Dear Hen
 
Posts: 701
Joined: Mon Oct 27, 2008 10:50
Location: Here! No, here! Over heeeeeeere!

Re: QA: Cannot run Portage trigger for equo,entropy

Postby albfneto » Thu Sep 17, 2009 21:36

Yo carried out the modifications in make conf, that were suggested by the Portage messages?
With the new versions of Portage and Entropy, you continue to have the problem?
ALBERTO FEDERMAN NETO
albfneto
[email protected]
Favorite Distros: Sabayon, Gentoo, Mageia and OpenSUSE
User avatar
albfneto
Sagely Hen
 
Posts: 1728
Joined: Fri Nov 16, 2007 1:15
Location: Ribeirão Preto City, São Paulo State, Brazil

Re: QA: Cannot run Portage trigger for equo,entropy

Postby ReemZ » Fri Sep 18, 2009 19:16

albfneto wrote:Yo carried out the modifications in make conf, that were suggested by the Portage messages?

Of course not. I did not, do not, and will not, use Portage.

albfneto wrote:With the new versions of Portage and Entropy, you continue to have the problem?

My question actually is: IS it a problem?
And, yes.
Handtekening? Zeg...ik ga niet op m'n monitor schrijven!
ReemZ
Old Dear Hen
 
Posts: 701
Joined: Mon Oct 27, 2008 10:50
Location: Here! No, here! Over heeeeeeere!

Re: QA: Cannot run Portage trigger for equo,entropy

Postby ReemZ » Mon Sep 21, 2009 21:39

Just asked Joost in IM, not a problem if you use equo, it'll be filtered out soon.

Equo users: you can ignore the QA-message! :alien:
Handtekening? Zeg...ik ga niet op m'n monitor schrijven!
ReemZ
Old Dear Hen
 
Posts: 701
Joined: Mon Oct 27, 2008 10:50
Location: Here! No, here! Over heeeeeeere!


Return to Entropy|Equo|Rigo Package Managers

Who is online

Users browsing this forum: No registered users and 2 guests