amarok-engine-yauap-trinity depends on non-existent package yauap #29

Closed
opened 3 years ago by mgb · 7 comments
mgb commented 3 years ago
Collaborator

Basic information

  • TDE version: R14.0.11 [DEVELOPMENT]
  • Distribution: Debian Bullseye 11.1
  • Hardware: amd64

Description

There doesn't seem to be a yauap package in Debian all the way from Stretch to Experimental. Ubuntu Universe seems to have one but it's dated 2012. Debian looks like it had one up until about 2012 also.

Steps to reproduce

amarok-engine-yauap-trinity version 4:14.0.11~pre20-0debian11.0.0+2

Screenshots

<!-- This is a comment. Please fill in the required fields below. The comments provide instructions on how to do so. Note: You do not need to remove comments. --> ## Basic information - TDE version: R14.0.11 [DEVELOPMENT] - Distribution: Debian Bullseye 11.1 - Hardware: amd64 <!-- Use SL/* labels to set the severity level. Please do not set a milestone. --> ## Description There doesn't seem to be a yauap package in Debian all the way from Stretch to Experimental. Ubuntu Universe seems to have one but it's dated 2012. Debian looks like it had one up until about 2012 also. ## Steps to reproduce amarok-engine-yauap-trinity version 4:14.0.11~pre20-0debian11.0.0+2 ## Screenshots <!-- If it seems useful, please provide provide one or more screenshots. -->
Owner

Yes, yauap has been missing for long time in debian, it's a known thing 😄

@SlavekB I guess after R14.0.11 we could probably drop building this package in debian and similar distros? What do you think?

Yes, yauap has been missing for long time in debian, it's a known thing :smile: @SlavekB I guess after R14.0.11 we could probably drop building this package in debian and similar distros? What do you think?
mgb commented 3 years ago
Poster
Collaborator

Makes sense to me. I had never even heard of yauap.

Makes sense to me. I had never even heard of yauap.
Owner

Yes, definitely, it is a package suitable for removal.

Yes, definitely, it is a package suitable for removal.
Owner

Should we consider dropping it for R14.0.11 or after that?

Should we consider dropping it for R14.0.11 or after that?
Owner

Should we consider dropping it for R14.0.11 or after that?

Because I intend to adjust Amarok packaging for R14.0.11 – see #28, I think it is also a good time to remove the amarok-engine-yauap-trinity package.

> Should we consider dropping it for R14.0.11 or after that? > Because I intend to adjust Amarok packaging for R14.0.11 – see #28, I think it is also a good time to remove the amarok-engine-yauap-trinity package.
Owner

Sounds good to me :-)

Sounds good to me :-)
Owner

Fixed by the commits in TDE/tde-packaging mentioned above.

Fixed by the commits in TDE/tde-packaging mentioned above.
SlavekB closed this issue 3 years ago
SlavekB added this to the R14.0.11 release milestone 3 years ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/amarok#29
Loading…
There is no content yet.