Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23

Thread: Update - uknown role type

  1. #11
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Update - uknown role type

    On 2014-11-29 14:16, wolfi323 wrote:
    >
    > robin_listas;2679567 Wrote:


    > True, and at the moment too much is blocked.
    > I.e. you can't use YaST/zypper if packagekitd is running without doing
    > anything.
    > But that's no new problem, that was the case in earlier versions as
    > well.


    I know, it is an old problem. And it is not only with those applets.

    For instance, when I have yast sw-single module running, thinking about
    what to do, I may want to run an rpm query to find some thing - and it
    refuses. A query! Not an install.

    I have to exit YaST, on which I may already have marked files for
    action, run the query, then start yast, remember my actions to re-select
    them (no, telling yast to "save" instead tries to apply the actions, not
    save them for later), then add new actions considering the query results
    which I have now on a file.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  2. #12
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,762

    Default Re: Update - uknown role type

    I think the problem that used to come up with packagekit is that it did not quit is a reasonable time or at all frame thus blocked things . Now it quits too fast and we don't get a really chance to view the remarks on installs via appr. (don't know why they can t reconnect when a comment is asked to expand. Seems obvious to me I don't always get a chance to look at the list in the first 15 seconds arrrgh ) In any case I have not run into the problem of packagekit blocking for several versions. Yes you can get a block if you try to run appr+yast+zypper but that should be by design to maintain data integrity.

  3. #13
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Update - uknown role type

    On 2014-11-29 18:06, gogalthorp wrote:
    >
    > I think the problem that used to come up with packagekit is that it did
    > not quit is a reasonable time or at all frame thus blocked things . Now
    > it quits too fast and we don't get a really chance to view the remarks
    > on installs via appr. (don't know why they can t reconnect when a
    > comment is asked to expand. Seems obvious to me I don't always get a
    > chance to look at the list in the first 15 seconds arrrgh ) In any case
    > I have not run into the problem of packagekit blocking for several
    > versions. Yes you can get a block if you try to run appr+yast+zypper but
    > that should be by design to maintain data integrity.


    Rather a miss-design. Nobody thought that anybody would want *read*
    access to the rpm database from two or more apps at the same time. This
    is possible to do, but you have to design the database and tools for
    that from the start. Not simple, but doable: multiuser databases do it
    all the time.

    It is write access which should block, not read access. Not queries.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  4. #14

    Default Re: Update - uknown role type

    Yes, that makes perfect sense. Why both of them shouldn't work if they only need read access?
    Someone here suggested using only yast for updates when needed, however my Yast updater does not show any new update, whereas the applet shows dozens of them.

  5. #15
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Update - uknown role type

    On 2014-11-30 15:16, pumrel wrote:
    >
    > Yes, that makes perfect sense. Why both of them shouldn't work if they
    > only need read access?
    > Someone here suggested using only yast for updates when needed, however
    > my Yast updater does not show any new update, whereas the applet shows
    > dozens of them.


    Yes, it does, but you have to know how.

    This is for the QT flavour.

    Select the view by repository type. Then select a repository, and on the
    right hand panel with the rpm list, right click, all on this list (I'm
    going from memory, wording might be different), then select "update if
    newer".

    That is equivalent to a "zypper up". If you select "update
    unconditionally" then it is similar to a "dup".

    An alternative is to select the pseudo repo that displays all packages,
    then update if newer. I prefer doing it repo by repo, though.

    The advantage to zypper is that you can solve conflicts with the mouse,
    and investigate a bit.


    Also, you have to be careful on the packman repo, because sometimes they
    go back in the version number of some packages, so the update doesn't
    happen. You have to browse the list watching for red packages, and use
    the mouse to force the "update", aka "degrade".


    Another operation is change the filter to display "unmaintained
    packages" and possibly remove them.


    On the GTK (Gnome) YaST flavour the operation would be different, and I
    can not describe it. It is unfamiliar to me.


    I prefer this procedure to using apper.


    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  6. #16

    Default Re: Update - uknown role type

    Quote Originally Posted by robin_listas View Post
    That is equivalent to a "zypper up". If you select "update
    unconditionally" then it is similar to a "dup".
    Not exactly.
    "Update Unconditionally" will re-install the package even if there is no other version available, whereas "zypper dup" will not.

    Also, you have to be careful on the packman repo, because sometimes they
    go back in the version number of some packages, so the update doesn't
    happen. You have to browse the list watching for red packages, and use
    the mouse to force the "update", aka "degrade".
    "Update Unconditionally" will also do a downgrade if only a lower version/revision is available.

  7. #17
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Update - uknown role type

    On 2014-11-30 19:26, wolfi323 wrote:
    >
    > robin_listas;2679850 Wrote:
    >>
    >> That is equivalent to a "zypper up". If you select "update
    >> unconditionally" then it is similar to a "dup".

    > Not exactly.


    That's why I said "similar" ;-)


    >> Also, you have to be careful on the packman repo, because sometimes they
    >> go back in the version number of some packages, so the update doesn't
    >> happen. You have to browse the list watching for red packages, and use
    >> the mouse to force the "update", aka "degrade".

    > "Update Unconditionally" will also do a downgrade if only a lower
    > version/revision is available.


    True.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  8. #18

    Default Re: Update - uknown role type

    Thank you very much for the info Although I must say that it could have been more straightforward.

  9. #19
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Update - uknown role type

    On 2014-11-30 21:16, pumrel wrote:
    >
    > Thank you very much for the info Although I must say that it could
    > have been more straightforward.


    YaST development has stalled for some years. They have removed features
    for lack of developers, so improving or adding features seems out of the
    question, unless really needed...

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  10. #20
    josephkk NNTP User

    Default Re: Update - uknown role type

    On Sat, 29 Nov 2014 18:43:06 GMT, "Carlos E. R."
    <robin_listas@no-mx.forums.opensuse.org> wrote:

    >On 2014-11-29 18:06, gogalthorp wrote:
    >>
    >> I think the problem that used to come up with packagekit is that it did
    >> not quit is a reasonable time or at all frame thus blocked things . Now
    >> it quits too fast and we don't get a really chance to view the remarks
    >> on installs via appr. (don't know why they can t reconnect when a
    >> comment is asked to expand. Seems obvious to me I don't always get a
    >> chance to look at the list in the first 15 seconds arrrgh ) In any case
    >> I have not run into the problem of packagekit blocking for several
    >> versions. Yes you can get a block if you try to run appr+yast+zypper but
    >> that should be by design to maintain data integrity.

    >
    >Rather a miss-design. Nobody thought that anybody would want *read*
    >access to the rpm database from two or more apps at the same time. This
    >is possible to do, but you have to design the database and tools for
    >that from the start. Not simple, but doable: multiuser databases do it
    >all the time.
    >
    >It is write access which should block, not read access. Not queries.


    +2 Hugely agreed.

    ?-)


Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •