Project

General

Profile

Housekeeping #3025

[libwebsockets] Package update is affecting to Ardour

eliotime3000 - over 1 year ago - . Updated over 1 year ago.

Status:
not-a-bug
Priority:
broken
Assignee:
% Done:

0%


Description

This bug report is being posted for complement the bug report that is publised in Arch Linux bug report.

This error appears when a package update is executed.

:: instalando libwebsockets (4.2.0-1) se rompe la dependencia con «libwebsockets.so=17-64», necesaria para el paquete ardour

Thanks.

History

#1

Updated by eliotime3000 over 1 year ago

For more explained discussion, please follow the Arch Linux bug report page page (please block any further comment and/or reply on this thread).

#2

Updated by bill-auger over 1 year ago

  • Assignee set to bill-auger
  • Status changed from open to forwarded upstream
#3

Updated by eschwartz over 1 year ago

  • Status changed from forwarded upstream to open

Very confused by this bug, since it is not an Arch bug, and both packages are Arch packages.

extra/libwebsockets 4.2.0-1
community-testing/ardour 6.6-2

were built together and meant for each other. But in Arch, they both got moved from testing to stable at the same time (18 hours ago, within seconds of each other) so I do not know why ardour is still in the parabola testing repos.

This seems like a problem with the parabola daily sync service.

#4

Updated by bill-auger over 1 year ago

  • Priority changed from bug to freedom issue

eliotime3000 - generally, parabola users should not report bugs to arch, not unless you have arch installed, and have verified that the bug also exists in arch - if the bug exists in arch, then there would be no reason to reference the parabola bug report in the arch bug report - you do not need to do that though - we would gladly do it for you

probably, the reason this happened, is because parabola syncs the 'packages' and 'community' repos only once per day, 8 hours apart - if the situation is as eli described, then the conflict will resolve itself within some hours

we are planning to tighten that loop soon; which should mostly eliminate this class of bug report

#5

Updated by bill-auger over 1 year ago

  • Priority changed from freedom issue to broken
#6

Updated by bill-auger over 1 year ago

  • Status changed from open to not-a-bug

Also available in: Atom PDF