spin failed-compose no longer ping spin maintainer? #13389
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13389
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Looking at:
releng/compose-tracker-issues#9375
currently Livespin compose failure no longer notify the status to spin maintainer?
For example, Fedora-Xfce-Live compose is failing for more than 2 weeks:
https://koji.fedoraproject.org/koji/packageinfo?packageID=22089
But I am not sure if Xfce spin maintainers are aware of this.
CC: @maxamillion @kevin @nonamedotc do you folks know more about this? I can look at the failurers.
Okay, so I did my due diligence, the Fedora Xfce Live image build failed on both aarch64 and x86_64 architectures due to a missing dependency for the pragha package.
Package: pragha
Missing Dependency: libgrilo-0.3.so.0()(64bit)
Error Type: Dependency resolution failure
Error Details
Both architecture builds failed with identical errors:
aarch64 (Task 146734140):
x86_64 (Task 146734141):
But it should have pinged maintainers need to see if it happened because of migration or what
@jnsamyak
I have been inactive for a few months and expect to become active soon. So, I have not monitoring xfce stuff much
Yeah, I knew about this, but have had no time at all to look further as to fixes.
We need to:
a) Fix pragha
or
b) drop it from comps for xfce
I'll try and look soon, I just got back from flock and have a large backlog tho, so might be a bit.
Short term perhaps we just drop it from comps and re-add it when/if we fix it.
grilo is optional in pragha, so you just need to rebuild it without that BuildRequires. (Either that, or adopt and reinstate grilo.)
Given how dead pragha is upstream, I'm not really interested in continuing to maintain it. I orphaned it, so feel free to take it if you like.