Page MenuHomeSolus

[RFC] Needs New Maintainer: yad
Closed, WontfixPublic


Repo: R3292 yad

As part of a sweeping effort I am doing to reduce outdated package count, begin regularly enforcing maintainership file inclusion in old(er) repos, and increase the likelihood of a package having a maintainer (should it be required, outside of those being handled by Core Team and Global Maintainers), this task is being created to effectively "notify" the current maintainer of the package that it needs to be updated or modified to indicate its maintainership and ensure it is regularly maintained. In the event there is no specific maintainer, either one may be specified that has regularly updated it in the past, or this task shall also be considered an RFC for a new maintainer.

During the patch submission process, the file should be included if it is not already, and have the following content (replace REPLACEME with the correct value):

This file is used to indicate responsibility for the maintenance of this package. Individuals on this list should be the sole modifiers of the package, excluding cases where the Solus Team may need to perform necessary rebuilds, upgrades, or security fixes. This list should not be used for any direct contact usage. If you believe this package requires a package update, follow documentation from In the event this package no longer becomes sufficiently maintained, Core Team reserves the right to request a new maintainer or remove this package from the repository.

  - Email: REPLACEME

Unless the updating of the package or claiming of maintainership is being blocked by other items in the stack, 30 days shall be provided to update the package or claim maintainership. Should the package not see an update by either the maintainer or an individual volunteering to become the maintainer, Core Team reserves the right to remove it from the repository. Please note that simply volunteering for maintainership without providing a patch is not an accepted "solution" to resolving this task or preventing deprecation.

Event Timeline

Herald triaged this task as High priority. · View Herald TranscriptNov 10 2020, 7:50 PM

This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.

If you wish to become the dedicated package maintainer for this package, please bear in mind that this package has been marked as a result of being either poorly integrated or maintained. If you are intent on becoming the maintainer for this package, please do so with:

  1. The expectation that you will be responsible for actively maintaining and integrating this package into the rest of the Solus software stack.
  2. The expectation that you will need to respond to issues related to this package in a timely manner.
  3. The expectation that you will be or already are actively using this package as part of your workflow, whether on a irregular or regular basis.

In the event you wish to become a package maintainer for this, please comment that you will be stepping forward to do so. This way, a Core Team member, or a member of the Triage Team, can remove the Planned Deprecation tag.

JoshStrobl moved this task from Backlog to Update Requested on the Software board.Nov 10 2020, 7:50 PM

I'm updating it right now to 7.3 version 19, I might need a mentor but I'm all for it if someone could answer questions if they arise.

@GnomeBook glad you are taking over the maintaining, if you have any question you should join us on IRC in the #solus-dev channel

@GnomeBook glad you are taking over the maintaining, if you have any question you should join us on IRC in the #solus-dev channel

Thank you!

I'm having some trouble building this, I've tried using different hash's. and its the same error. I've googled the error and tried everything that i seen.
I am able to build v5.0 that @JoshStrobl maintained. I'm very sorry for not posting on #solus-dev as @Girtablulu suggested but i just don't have the time to get re-aquainted with the commands at the moment. I have some free time waiting for clear coat to dry on some cabinets.

This is my package.yml{F6805207}

Here is my structure
devel@linux ~/repository $ ls
common Makefile Makefile.common Makefile.iso yad

And source folder
devel@linux ~/repository/yad $ ls
abi_used_libs package.yml yad-5.0-8-1-x86_64.eopkg
Makefile pspec_x86_64.xml yad-devel-5.0-8-1-x86_64.eopkg

mount: /var/cache/solbuild/unstable-x86_64/yad/union/home/build/YPKG/sources/v7.3.tar.gz: mount point does not exist.
ERRO[16:53:24] Failed to bind mount source                   error="exit status 32" target="/var/cache/solbuild/unstable-x86_64/yad/union/home/build/YPKG/sources/v7.3.tar.gz"
ERRO[16:53:24] Cannot continue without sources              
ERRO[16:53:24] Failed to build packages                     
make[1]: Leaving directory '/home/devel/repository/yad'
make abireport
make[1]: Entering directory '/home/devel/repository/yad'
abireport -p abi_ -D `dirname package.yml` scan-packages `dirname package.yml`
make[1]: Leaving directory '/home/devel/repository/yad'
algent added a subscriber: algent.EditedDec 7 2020, 10:25 PM

I tried to update it to 7.3 and everything it is going fine. For that message "mount point does not exist.", I think it means that sha2sum is incorrect.

You have to use the correct command to update the source.

/usr/share/ypkg/ 7.3

As the result release number and the source will be upated to:

release    : 9
source     :
    - : 5768ffacc29903f6735d397883eeb9f049061978b78e5a8b4be5c273a06193dc

I recommend you to check our IRC #Solus-Dev on freenode channel. So you can ask questions there.

EDIT: typo

GnomeBook added a comment.EditedDec 7 2020, 10:28 PM

Thank you very much, all is working great now! after this week i will get on IRC.

JoshStrobl closed this task as Wontfix.Jan 10 2021, 5:45 PM

Closing due to a maintainer not stepping up to provide and address any issues with patches.