What are the different “types” of dependencies?

Forum Forums New users New Users and General Questions What are the different “types” of dependencies?

  • This topic has 20 replies, 7 voices, and was last updated Aug 25-12:57 am by stevesr0.
Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #87596
    Member
    stevesr0
      Helpful
      Up
      1
      ::

      Edit: Uh-duh, antiX-22 isn’t available yet. I will use antiX-21 and remove libelogind0 (which also removes elogind).

      stevesr0

      Hi anticapitalista,

      Thanks for your confidence in me <g>.

      I note that doing a simulated apt remove of libelogind0 on my current Sid system with libelogind0, removes ibapt-pkg5.0, libapt-inst2.0, at-spi2-core and gir1.2-wp-0.4, in addition to pipewire/wireplumber related packages and elogind and libpam-elogind.

      Notably, on my install libwireplumber-0.4-dev is listed as dependent upon gir1.2-wp-0.4. In addition, gir1.2-wp-0.4 is listed as dependent upon libwireplumber-0.4. Does this mean that a new version of gir1.2-wp-0.4 is needed?

      Since my current Sid install has libelogind0, I will make a new install of Sid based upon antiX-22 to see if this works.

      stevesr0

      • This reply was modified 8 months, 2 weeks ago by stevesr0.
      #87610
      Member
      iznit
        Helpful
        Up
        1
        ::

        assume that the .dev version contains everything in the “regular version”, so

        No, that would create a conflict. Package manager insists that only one package “owns” a file [[[the package which installed a given file]]]. Other packages are forbidden to tamper with files “owned” by other packages. Upon attempting to install an already present, duplicate pathed, file….. package installation would fail.

        duplicate = same filename, same /path/to/filename
        non-duplicate example: /usr/doc/packageA/changelog vs /usr/doc/packageB/changelog

        #87614
        Member
        stevesr0
          Helpful
          Up
          0
          ::

          Hi iznit,

          Thanks for the correction.

          I checked and the packages are very different with only one source file, a copyright and two changelog files in common.

          I will send a message to anticapitalista requesting clarification about the missing non-dev libwireplumber package.

          stevesr0

          #87626
          Forum Admin
          anticapitalista
            Helpful
            Up
            0
            ::

            I also uploaded 32 bit debs.
            As far as i can tell.there is nothing missing.

            Philosophers have interpreted the world in many ways; the point is to change it.

            antiX with runit - leaner and meaner.

            #87632
            Member
            marcelocripe
              Helpful
              Up
              0
              ::

              P.S. This thread is about dependencies; Pipewire is just a reasonable example to talk about the complexities of dependencies.

              Hello stevesr0.
              Although this is not a specific topic about PipeWire, the problems related to this program’s dependencies are good examples of the problems that are expected to increase in the long term due to SystemD.
              This weekend I installed some antiX on different computers. On one of the computers, after updating the antiX 21 full 64-bit SysVinit, I needed to install Winehq-staging with the Package Installer and I couldn’t install it at all, even though I changed the repositories. After a few unsuccessful attempts to install Winehq-staging with Package Installer, I tried to install installing Wine with Synaptic and it worked successfully, but Wine from Synaptic is not the same as Winehq-staging from Package Installer. Afterwards, I tried installing Wine32-preloader, but it complained about missing dependencies. And since I was on a computer that was going to be delivered to the end user, I couldn’t test and try to do something that I’m not sure would work, otherwise it could damage the end user’s antiX.

              I’m glad more people are participating in this thread, as the other Pipewire without systemd thread didn’t develop as we expected.

              Thanks for starting another important topic.
              marcelocripe

              (Original text in Brazilian Portuguese)

              – – – – –

              P.S. This thread is about dependencies; Pipewire is just a reasonable example to talk about the complexities of dependencies.

              Olá stevesr0.
              Mesmo não sendo um tópico específico sobre o PipeWire, os problemas relacionados com as dependências deste programa são bons exemplos dos problemas que deverão aumentar a longo prazo devido ao SystemD.
              Este fim de semana eu instalei alguns antiX em computadores diferentes. Em um dos computadores, após atualizar o antiX 21 full de 64 bits SysVinit, eu precisei instalar o Winehq-staging com o Package Installer e não consegui instalar de forma alguma, mesmo eu mudando os repositórios. Depois de algumas tentativas sem sucesso de instalar o Winehq-staging com o Package Installer, eu tentei instalar instalar o Wine com o Synaptic e funcionou com sucesso, mas o Wine do Synaptic não é igual ao Winehq-staging do Package Installer. Depois, eu tentei instalar o Wine32-preloader, mas reclamava de dependências desencontradas. E como eu estava em um computador que seria entregue para o usuário final, eu não podia fazer testes e tentar fazer algo que eu não tenho certeza que iria funcionar, ao contrário, poderia danificar o antiX deste usuário final.

              Eu fico contente que mais pessoas estejam participando deste tópico, já que o outro tópico Pipewire without systemd não teve o desenvolvimento que nós esperávamos.

              Obrigado por iniciar mais um importante tópico.

              marcelocripe
              (Texto original em idioma Português do Brasil)

              #87662
              Member
              stevesr0
                Helpful
                Up
                0
                ::

                (N.B. I think this conversation should be continued on the Pipewire without Systemd thread; I will post a notice about the posts on this thread, and start posting there with notices here for a while to let anyone interested switch over.)

                Hi all,

                This is a report on my first steps in trying to use the elogind/libelogind0 free Pipewire packages in an antiX-21 Sid live USB.

                On first running tonight, I am not getting sound and alsa doesn’t list Pipewire as a choice (unlike the install on my old Sid install with elogind/libelogind0).

                When I first installed Pipewire on the old system, I was able to launch it by using separate terminals for pipewire, pipewire-pulse and wireplumber.  That didn’t work tonight on the live usb.

                I see an error message about a missing file (module-rt.c in libwireplumber-module-logind.so) and an error in m-lua-scripting in ../modules/modules-rt.c.

                So, I will have to look to see if anyone on the internet has dealt with this.

                I didn’t set up persistence, so I haven’t rebooted.

                Pavucontrol does display the available inputs and outputs, but I cannot use it to switch output.

                If anyone else is working on getting these packages working, I would like to hear from you.

                stevesr0

                • This reply was modified 8 months, 2 weeks ago by stevesr0.
              Viewing 6 posts - 16 through 21 (of 21 total)
              • You must be logged in to reply to this topic.