Bug 27034 - debug symbols for maintained packages (dbgsym)
debug symbols for maintained packages (dbgsym)
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: General
UCS 5.0
All Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
https://wiki.debian.org/AutomaticDebu...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-08 14:42 CEST by Philipp Hahn
Modified: 2021-02-24 08:56 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?: Yes
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, Further conceptual development, Troubleshooting
Max CVSS v3 score:


Attachments
univention-debug dbg-Paket (1.36 KB, patch)
2012-05-30 13:01 CEST, Philipp Hahn
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2012-05-08 14:42:10 CEST
An einigen Bugs (z.B. Bug #25868) hängen core-Dateien. Ohne genaue Angabe der Paketversion und den zugehörigen Debug-Symbolen sind diese allerdings recht nutzlos.
Wir sollte darüber nachdenken, ob wir nicht zumindest für unsere maintained-Pakete die Debug-Symbole aufheben und zumindest lokal vorhalten. Da diese oft ein Vielfaches der Größe des eigentlichen Pakets belegen, scheint mir das am sinnvollsten. Alternativ könnten diese aber auch unmaintained oder extra veröffentlicht werden.

dh_strip bietet bereits die Möglichkeit, die Debug-Symbole anstatt sie zu löschen in ein extra Paket zu verschieben. Das muß aber für jedes Paket angepasst werden (vgl. z.B. svn31534 für univention-directory-listener)

Für Debian gab es mal ein Projekt <http://wiki.debian.org/AutomaticDebugPackages>, das aber im Moment nicht mehr aktiv vorangetrieben zu werden scheint.
Ggf. wäre das auch mal ein interessantes Studenten-Projekt.
Comment 1 Philipp Hahn univentionstaff 2012-05-30 13:01:51 CEST
Created attachment 4410 [details]
univention-debug dbg-Paket

Für Bug #27335 erstellt.
Comment 2 Stefan Gohmann univentionstaff 2016-10-11 08:04:28 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please reopen.
Comment 3 Philipp Hahn univentionstaff 2016-10-12 09:18:02 CEST
We still don't have debug symbol packages with UCS-4.1.
Debian has managed that through "automatic debug packages".
Comment 4 Stefan Gohmann univentionstaff 2016-12-13 08:10:42 CET
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 5 Ingo Steuwer univentionstaff 2020-07-03 20:54:05 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
Comment 6 Philipp Hahn univentionstaff 2020-07-04 15:38:10 CEST
We still do not have a concept how to handle the dbgsym backages:
- we do not mirror them from Debian
- we release those for our own packages

We should not mirror them by default for UCS-5, but keep them internally for when the need arises.