Project

General

Profile

Feature #3699

merge Debian patches

Added by msuraev about 1 year ago. Updated 4 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/19/2018
Due date:
% Done:

90%

Spec Reference:

Description

There're numerous patches from Debian developers available via:
https://qa.debian.org/developer.php?email=Debian-mobcom-maintainers%40lists.alioth.debian.org
individual package links example:
https://sources.debian.org/patches/libosmo-sccp/0.10.0-2/
Relevant package version could be obtained from the first link.

Some of those patches are Debian-specific while others are generally relevant fixes. We should go over all packaged projects and submit all relevant patches to gerrit for review.

Note: Debian seems to have the most recent versions packaged compared to other repositories according to repology - see for example
https://repology.org/metapackage/libosmocore/versions


Related issues

Related to Cellular Network Infrastructure - Bug #3694: Fix lintian warnings in .deb packagesNew11/14/2018

Related to Cellular Network Infrastructure - Bug #3753: Update .deb to use dh_missingNew01/09/2019

History

#1 Updated by msuraev about 1 year ago

  • Related to Bug #3694: Fix lintian warnings in .deb packages added

#2 Updated by msuraev 11 months ago

  • Related to Bug #3753: Update .deb to use dh_missing added

#3 Updated by osmith 5 months ago

The links pointing to the patches from the description above are down. It seems that the libosmocore patches are located here now:

https://salsa.debian.org/debian-mobcom-team/libosmocore/tree/master/debian/patches

#4 Updated by Hoernchen 5 months ago

  • Assignee set to Hoernchen

#6 Updated by laforge 5 days ago

Hoernchen wrote:

This patch needs to be removed by the maintainer, it jeopardizes any use of libosmogb:
https://salsa.debian.org/debian-mobcom-team/libosmocore/raw/master/debian/patches/0001-Removed-illegal-pkg-config-directive.patch

can you be more specific why it jeopardizes any use of libosmogb? Also, was this reported as a debian bug? If not, why? If so, please include the reference to the debian bugtracker here. thanks!

Also, the issue is still marked as "new" and "0%" even thought some work was done months ago. I wuold have expected it to go from new->in_progress, then some percentage increase, and finally go to stalled when priorities changed to stop working on it.

#7 Updated by Hoernchen 4 days ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

All reasonable patches were merged.

As for the aliasing issue, this was added by you, and it has to be part of the cflags, since it concerns the headers and therefore other users of libosmocore, but the debian linter doesn't like such flags - see https://gerrit.osmocom.org/plugins/gitiles/libosmocore/+/ca0af8a3a862d5189915c02c2bc85461a3b33415 or https://gerrit.osmocom.org/c/libosmocore/+/1426 for a short explanation.

I've just filed a debian bug for that.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)