[bug#71196] Mentoring for Mixxx package update

[Olivier Rojon <o.rojon@posteo.net>]

"jgart" <jgart@dismail.de> writes:

Hej,

I've taken the time to build the dependencies output by `./pre-inst-env guix refresh -L
$PKG` (where $PKG was one of `hidapi` and `soundtouch`).  This was my process:

1) I created a new branch to which I applied the three patches sent in over here.
Unexperienced working with git branches, I compared if, when in `master`, mixxx-2.3.6 gets
build, while in my testing branch `mixxx-update`, mixxx-2.4.1. gets built, to see how the
`mixxx-update` branch was affected by those patches while `master` isn't.

2) I created a union of the output of `./pre-inst-env guix refresh -L` for `hidapi` and
`soundtouch`.

3) I mass-built the dependencies using a `for`-loop within `guix shell -CPW` and with
`./pre-inst-env`, also these lines:
for pkg in LONG-PKG-LIST; do ./pre-inst-env guix build $PKG; done

4) I checked for built failures.

5) In case of build failures, I switched to the `master` branch, to check if building
overe there is successful.

Of the 246 dependencies in LONG-PKG-LIST, 233 built successfully.  Most of the failures
also failed on the `master`-branch, while some dependencies were discarded as "unknown
package".  Find the list of packages where the build failed below:
  - gnome-meta-core-utilities (unknown package)
  - gnome-essential-extras (unknown package)
  - gnome-meta-core-shell (unknown package)
  - ledger-agent (also fails on master)
  - giara (also fails on master)
  - sequeler (also fails on master)
  - eog-plugins (also fails on master)
  - nomad (also fails on master)
  - chatty (also fails on master)
  - memphis (also fails on master)
  - emacsy (also fails on master)
  - dvdstyler (also fails on master)
  - mate (also fails on master)

How to proceed?

Have a good day :)

>> Just to be sure: if I want my changes merged sooner or later, I have to build all the
>> package depending upon soundtouch and hidapi successfully within `guix shell -CPW` and
>> `pre-inst-env`, correct?
>
> Yes, that's correct.
>  
>> Is there anything additional that I need to keep in mind when doing that?
>
> Not that I'm aware of.
>
> all best,
>
> jgart