Package: sponsorship-requests
Severity: important

Dear mentors,

I received a RC bug for improper packaging for workflow. I have corrected the mistakes and ensured the package is lintian clean.  Workflow has been in Debian for several months.

To follow the Debian process for shared libraries, I had to make a new package (libworkflow0) and thus need this to go through the NEW queue.

As this is a RC bug (for not having SONAME/SOVERSION) and workflow is currently marked for removal in ~1 month, I would appreciate it if someone could review and sponsor this upload.

I am looking for a sponsor for my package "workflow":

 * Package name    : workflow
   Version         : 0.10.1-1
   Upstream Author : Li Yingxin <liyingxin@sogou-inc.com>
 * URL             : https://github.com/sogou/workflow
 * License         : Apache-2.0, zlib, BSD-2-Clause
 * Vcs             : https://salsa.debian.org/debian/workflow
   Section         : libs

The source builds the following binary packages:

  libworkflow0 - Parallel computing and asynchronous web server engine
  libworkflow-dev - Parallel computing and asynchronous web server engine

To access further information about this package, please visit the following URL:

https://mentors.debian.net/package/workflow/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/w/workflow/workflow_0.10.1-1.dsc

Changes since the last upload:

 workflow (0.10.1-1) unstable; urgency=medium
 .
   * Update to version 0.10.1
   * d/control: Bump standards to 4.6.1
   * d/copyright: Update years to 2022
   * Fixed SONAME/SOVERSION issues. Closes: #1012544

Regards,

Please fix the piuparts issue in
https://salsa.debian.org/debian/workflow/-/jobs/2904048

Please read https://www.debian.org/doc/debian-policy/ch-relationships.html for that.

Also, please push the upstream/0.10.1 tag.
I have reset the pristine-tar branch by 1 unnecessary commit that added the file that the orig tarball linked to.

Hello Bastian,

I really don't know how to fix this. I read the documentation. The piuparts issue is that the libworkflow1 package (which now no longer exists) has a conflict over libworkflow.a. There was an error in the way the package was structured and libworkflow1 should have never provided libworkflow.a (it should only be in -dev).

I tried to submit a control file change to say that libworkflo0 replaced libworkflow1 but the error prevents this replacement from being effective.

I don't know how to specify that piuparts should remove libworkflow1/libworkflow-dev and re-install this new version of the package. That's essentially what I want to do.

Done.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

Hello Bastian,

I really don't know how to fix this. I read the documentation. The piuparts issue is that the libworkflow1 package (which now no longer exists) has a conflict over libworkflow.a. There was an error in the way the package was structured and libworkflow1 should have never provided libworkflow.a (it should only be in -dev).

I tried to submit a control file change to say that libworkflo0 replaced libworkflow1 but the error prevents this replacement from being effective.

I don't know how to specify that piuparts should remove libworkflow1/libworkflow-dev and re-install this new version of the package. That's essentially what I want to do.

Done.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

Am 21.06.22 um 16:38 schrieb Lance Lin:

Hi Bastian,

I've tried to search on my own and look at Debian resources: https://wiki.debian.org/PackageTransition

I've tried:
Breaks/Replaces: (<= libworkflow1 0.9.10) - the previous version
Breaks/Replaces: (<< libworkflow1 0.9.10-1)
Breaks/Replaces: (<< libworkflow1 0.9.10~)
Breaks/Replaces: (<< libworkflow1 0.9.10)

And none of it seems to work.  What am I missing? I will still have this problem on SRPC that will need to be fixed before it is uploaded as well.


If you have a website/resource/example, I would greatly appreciate it.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

Hi Bastian,

I've tried to search on my own and look at Debian resources: https://wiki.debian.org/PackageTransition

I've tried:
Breaks/Replaces: (<= libworkflow1 0.9.10) - the previous version
Breaks/Replaces: (<< libworkflow1 0.9.10-1)
Breaks/Replaces: (<< libworkflow1 0.9.10~)
Breaks/Replaces: (<< libworkflow1 0.9.10)

And none of it seems to work.  What am I missing? I will still have this problem on SRPC that will need to be fixed before it is uploaded as well.


If you have a website/resource/example, I would greatly appreciate it.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F

How are you testing this?
And where are you adding these fields? libworkflow0 or libworkflow-dev?

How are you testing this?
And where are you adding these fields? libworkflow0 or libworkflow-dev?

Am 22.06.22 um 17:05 schrieb Andrey Rahmatullin:

Just fixed it for you. You need it on both the libraries because you also moved the .a to the -dev, which
I did not notice beforehand.

Uploaded with Breaks/Replaces added.

Also, I have rewritten git history for upstream and debian branches because you missed the upstream/0.9.10 commit and
tag in the upstream branch. Please clone a fresh copy to continue work.

Thank you, Bastian.

This is very helpful, I really appreciate it.

I also just updated SRPC (and tagged in Salsa) with similar fixes for piuparts and package architecture issues as I based SRPC off of Workflow.

Lance Lin <lqi254@protonmail.com>
GPG Fingerprint:  8CAD 1250 8EE0 3A41 7223  03EC 7096 F91E D75D 028F