Hello,

this is about the "xlsxwriter" package [1] and this one year old bug
report about defect "homepage" url [2].

I am new in the neighborhood and think this is a good issue to learn
something about the Debian internals.

So where does the "homepage" url in the "link" box on the right side of
the tracker page comes from. And how can I fix it?

Or is it extracted from the meta data of the last package and only a
new package can fix this?

btw: I am not sure if this list is the right place. But the DPMT is
named as "uploaders" of that package. And I am confused about that the "maintainer" is a ubuntu-list (Team?).

Kind
Christian

[1] -- <https://tracker.debian.org/pkg/xlsxwriter>
[2] -- <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966164>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2021-09-15 15:46, Neil Williams wrote:

https://tracker.debian.org/media/packages/x/xlsxwriter/control-1.1.2-0.2

The package does not seem to have a current version control repository.

That would be a good start. There doesn't seem to be a project in salsa.debian.org and it would make things a lot easier when asking for
help with packaging changes, to have a URL in Salsa.

There seems to be a project for xlsxwriter:

https://salsa.debian.org/python-team/packages/xlsxwriter

However, I am not sure whether this one corresponds to the package on tracker.debian.org, it also would be great to make sure whether it does.

Best,
Andrius

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 15 Sep 2021, Andrius Merkys wrote:

https://tracker.debian.org/media/packages/x/xlsxwriter/control-1.1.2-0.2

The package does not seem to have a current version control repository.

That would be a good start. There doesn't seem to be a project in
salsa.debian.org and it would make things a lot easier when asking for
help with packaging changes, to have a URL in Salsa.

There seems to be a project for xlsxwriter:

https://salsa.debian.org/python-team/packages/xlsxwriter

However, I am not sure whether this one corresponds to the package on tracker.debian.org, it also would be great to make sure whether it does.

To answer your original question, yes, a new upload is required to update
the 'Homepage' URL which is defined in debian/control.

It seems that this package should probably be fully moved and adopted into
the Debian Python Team - it seems to have been partially done.

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 15 Sep 2021 11:58:24 +0000
<c.buhtz@posteo.jp> wrote:

Hello,

this is about the "xlsxwriter" package [1] and this one year old bug
report about defect "homepage" url [2].

I am new in the neighborhood and think this is a good issue to learn something about the Debian internals.

So where does the "homepage" url in the "link" box on the right side
of the tracker page comes from. And how can I fix it?

https://tracker.debian.org/media/packages/x/xlsxwriter/control-1.1.2-0.2

The package does not seem to have a current version control repository.

That would be a good start. There doesn't seem to be a project in salsa.debian.org and it would make things a lot easier when asking for
help with packaging changes, to have a URL in Salsa.

Or is it extracted from the meta data of the last package and only a
new package can fix this?

btw: I am not sure if this list is the right place. But the DPMT is
named as "uploaders" of that package. And I am confused about that the "maintainer" is a ubuntu-list (Team?).

Yes, checkbox-devel - you should at least introduce yourself there.

https://lists.ubuntu.com/mailman/listinfo/Checkbox-devel

See also https://mentors.debian.net/ - a lot of help and information
for people who are new to packaging.


--
Neil Williams
=============
https://linux.codehelp.co.uk/

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEf3HB6ceOc10DYMbM8WfkPIFDtoIFAmFB6x0ACgkQ8WfkPIFD toITGxAAqhTaOsQNZC6Tk6GFui3wYJhuCbovMsDFqenzz/odCXKiilcsTItnXmIf /hLyI4uwMdrqtZW5cW9BSgx964Ex5tnM+BgMt3IQekkY63K0ckhUWeKRziD0xCdR g6xf+QVNXRB0+C6tBZxmTB2m8symFcVzUOKdKiYv4gfrrARnxT9AJnqzCfHyIAJA ZCbZdx1GocfqmAYiK9JUrPtTwJ4etHE2pAhq2dYHBI9OpQfnrpqJBfQKifGLt4fv Q/FuKi8BW9PPvuInVflvX5lQPWxjnMZ2hCRr2n/U2JtsAbWOfhLeyFQZbvkHwJ+5 im0gXQ2lrAd0nRM1aUU3YGgyGdRCM0rZm7hkZnAb3JWsKV1fCBjHeQlfJNRCv3Un BwticIzMdwKeGT2lYv9wVm4l8Hjf/PYgJyw7XG4Q5D97dPY/oS1KKNKdHDgcgnqY srLTiUx7jeaGIeODPlW6bZ0YaccF9UN/G2OWEJbWoYHFUpP8YVF4nOsBEidFDCvC jAdbLl96fjA+mK6af7UIsVhCzz+SgsrnpN6bCFcT3Yc6X2yqguF5+eCOJ8HqlYfV WrUVpZyPInRRex2HqX+ycg8EsZn5MMFwYHj1PaKESpZM1p09aALcF5fWjn7F6J9b 2sAVuZqDa3+9L/OUB0KXonYFJJm/J3ate5WyNu828wjuwR8acBk=
=RnMp
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 15 Sep 2021, c.buhtz@posteo.jp wrote:

It seems that this package should probably be fully moved and adopted
into the Debian Python Team - it seems to have been partially done.

I would say the salsa project is outdated because the version number
in setup.py does not fit to upstream.

https://salsa.debian.org/python-team/packages/xlsxwriter/-/blob/master/setup.py#L31

I asked about the Debian package on the Checkbox-Mailinglist https://lists.ubuntu.com/archives/checkbox-devel/2021-September/000489.html

Well, I think what Andrius meant was to check whether the salsa project
matches what is currently uploaded to Debian.

The salsa project does however seem to be mismatched with what's currently uploaded in Debian unstable.

Salsa has 0.9.3-0.1 + some unreleased changes whereas unstable had
uploads of 0.9.6-0.1, 1.1.2-0.1, and 1.1.2-0.2 after 0.9.3-0.1, so that
would need to be sorted out.

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thanks for the reply's.

On 2021-09-15 09:02 Scott Talbert <swt@techie.net> wrote:

It seems that this package should probably be fully moved and adopted
into the Debian Python Team - it seems to have been partially done.

I would say the salsa project is outdated because the version number
in setup.py does not fit to upstream.

https://salsa.debian.org/python-team/packages/xlsxwriter/-/blob/master/setup.py#L31

I asked about the Debian package on the Checkbox-Mailinglist https://lists.ubuntu.com/archives/checkbox-devel/2021-September/000489.html

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Scott

On 2021-09-15 10:59 Scott Talbert <swt@techie.net> wrote:

so that would need to be sorted out.

This sounds like a task that should be taken by someone more
experienced then me.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello everybody,

This sounds like a task that should be taken by someone more
experienced then me.

Looking in the salsa repo [0], it is very old. And that shouldn't happen. I
can updated
to the last unstable version tonight/tomorrow. If There's no objections.
Or, perhaps
Christian (the initial of this thread) can/want to do it (Christian, write
to me if you
need help)?

So where does the "homepage" url in the "link" box on the right side of
the tracker page comes from. And how can I fix it?

You need to modify the debian/control file on the "Homepage" key.

btw: I am not sure if this list is the right place. But the DPMT is
named as "uploaders" of that package. And I am confused about that the "maintainer" is a ubuntu-list (Team?).

That would be great, but I would leave it to the current maintainer to do
that, also seems
to be a group ¿?. I cc to the maintainer(s).


[0] https://salsa.debian.org/python-team/packages/xlsxwriter

Cheers,
Emmanuel

<div dir="ltr">Hello everybody, <div><br></div><div>&gt; This sounds like a task that should be taken by someone more</div>&gt; experienced then me.<div><br></div><div>Looking in the salsa repo [0], it is very old. And that shouldn&#39;t happen. I can
updated</div><div>to the last unstable version tonight/tomorrow. If There&#39;s no objections. Or, perhaps</div><div>Christian (the initial of this thread) can/want to do it (Christian, write to me if you</div><div>need help)?</div><div><br></div><div>&
gt; So where does the &quot;homepage&quot; url in the &quot;link&quot; box on the right side of<br>&gt; the tracker page comes from. And how can I fix it?<br></div><div><br></div><div>You need to modify the debian/control file on the &quot;Homepage&quot;
key.</div><div><br></div><div>&gt; btw: I am not sure if this list is the right place. But the DPMT is<br></div><div>&gt; named as &quot;uploaders&quot; of that package. And I am confused about that the<br>&gt; &quot;maintainer&quot; is a ubuntu-list (
Team?).<br></div><div><br></div><div>That would be great, but I would leave it to the current maintainer to do that, also seems</div><div>to be a group ¿?.  I cc to the maintainer(s). </div><div><br></div><div><br></div><div>[0] <a href="https://
salsa.debian.org/python-team/packages/xlsxwriter">https://salsa.debian.org/python-team/packages/xlsxwriter</a></div><div><br></div><div><div>Cheers, </div><div>Emmanuel</div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Emmanuel,

Am 15.09.2021 21:36 schrieb Emmanuel Arias:

Looking in the salsa repo [0], it is very old. And that shouldn't
happen. I
can updated to the last unstable version tonight/tomorrow.

Just to improve my knowledge about Debian processes: What does it mean
to update the salsa repo to the current upstream? Is it the same as
create a new package? Or is it just one step into creating a new
package?

Or, perhaps Christian (the initial of this thread) can/want to do it (Christian,
write to me if you need help)?

Not yet, thanks. I am to fresh and will focus on one package only ("feedparser") to improve my learning.
But I will look at "xlsxwriter" and learn.

btw: I am not sure if this list is the right place. But the DPMT is
named as "uploaders" of that package. And I am confused about that the
"maintainer" is a ubuntu-list (Team?).

That would be great, but I would leave it to the current maintainer to
do
that, also seems to be a group ¿?. I cc to the maintainer(s).

They still answered my question on their own list: https://lists.ubuntu.com/archives/checkbox-devel/2021-September/000491.html

They do not want to maintain anymore. And they asked about open a WNPP
for it.

This would have been my question, too. If we do not create a new package version now how could we document the new information's about the maintainership somewhere for someone in the future?

As a newcomer, I am taking a step back so as not to cause more trouble.
;) I would like to suggest that someone from the experienced DD here
answer the maintainer direct what the next steps should be and who
should do them. Would be nice if you could put me into CC.

Kind
Christian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Christian,

c.buhtz@posteo.jp writes:

Dear Emmanuel,

Am 15.09.2021 21:36 schrieb Emmanuel Arias:

Looking in the salsa repo [0], it is very old. And that shouldn't
happen. I
can updated to the last unstable version tonight/tomorrow.

Just to improve my knowledge about Debian processes: What does it mean
to update the salsa repo to the current upstream? Is it the same as
create a new package? Or is it just one step into creating a new
package?

I didn't look at the packages in question, but as a matter of team
policy, the Debian Python Team uses git-buildpackage repositories, with pristine-tar, and a repo's layout is as follows:

1. Pristine-tar branch (upstream tarball is imported here)
2. Upstream branch (upstream tarball is unpacked here)
3. Debian packaging branch (name varies)
* https://dep-team.pages.debian.net/deps/dep14/ is the standardisation
effort the DPT has adopted.
* another key phrase is a "patches unapplied" packaging branch.

`gbp import-orig --pristine-tar --uscan` downloads the latest tarball
and puts it in #1, then unpacks it to #2, then creates an
upstream/new_version tag on this upstream branch, then merges that tag
to #3. One then needs update the version of the current changelog entry
(if UNRELEASED), or create a new one with `dch
-v$new_upstream_version-1`. Finally, one may need to use `gbp pq` to
import, rebase, and export an existing quilt patch series onto the new
upstream release.

https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#git-procedures
https://wiki.debian.org/Python/FAQ
https://wiki.debian.org/Python/GitPackaging

Other teams/individuals have different policies and practises.


'hope that helps!
Regards,
Nicholas

--=-=-Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE4qYmHjkArtfNxmcIWogwR199EGEFAmFDvnkQHHN0ZW5AZGVi aWFuLm9yZwAKCRBaiDBHX30QYdM9D/9aCcd2jgjgHTin0rKyAEY8zO0eIjHbrQjL KNsEmSa6FXypVxtEXzz8wdJJRzf5V/O+FwcuZEa5pXke3TxhWRHGQBVrsPHk1c8N AYWybz8iT4n8c/NLciZt0o5I1ilXbHEyYEmxl0+CZxzXleWPy6d4EZICkv7o96gL QhWjFPhwpLrNY2moKgJVfIifDJdDrDGnlcKUHUZmnA21TIoyiEhhZZPSYOvE6euc PpWswp73q868m32OziNOoS3pZtoJ5RjX18gx8AzbU91oFzLOhnHcTYu6PrF6HocX FM7aH9o4ujIiEQaBfvLvyr3Lgrhd86woei2AQ7IFtBcH31ZSJjggooPZRtZvIr3r M03/SF9IDgm7yYq3RUUQ4nLKVD0h5Cjj7dtp6Jvh1gRPyFSSK+LA+U0Z6S6xRjkR 0NQ0lko3TyXHfBqo+Qq67mLDYj4D/rOypV+RZEnSitWhqlvxbKitviaRei+rXiVD gD8g9Asv1r3PzhUdv/Og2cxRDR0iA7KNf9bm9IzEW7dIwH7Qa+QXJcm6PazlQg8Z 8d1vz36rNA3jdd7Boyo9tLYzxqdyRsaNxAjuRJXk6+tFm5cgBSDfedJwpc89WQSH h/Nsva21OBZySwGAR/RnkuZQpdFvQoEKx6Z57pTkIgzIL4z8AjEOm1kubUY5FTRv
Ie7YmQ8a8g=ª+1
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 16 Sep 2021, Nicholas D Steeves wrote:

Am 15.09.2021 21:36 schrieb Emmanuel Arias:

Looking in the salsa repo [0], it is very old. And that shouldn't
happen. I
can updated to the last unstable version tonight/tomorrow.

Just to improve my knowledge about Debian processes: What does it mean
to update the salsa repo to the current upstream? Is it the same as
create a new package? Or is it just one step into creating a new
package?

I didn't look at the packages in question, but as a matter of team
policy, the Debian Python Team uses git-buildpackage repositories, with pristine-tar, and a repo's layout is as follows:

1. Pristine-tar branch (upstream tarball is imported here)
2. Upstream branch (upstream tarball is unpacked here)
3. Debian packaging branch (name varies)
* https://dep-team.pages.debian.net/deps/dep14/ is the standardisation
effort the DPT has adopted.
* another key phrase is a "patches unapplied" packaging branch.

`gbp import-orig --pristine-tar --uscan` downloads the latest tarball
and puts it in #1, then unpacks it to #2, then creates an upstream/new_version tag on this upstream branch, then merges that tag
to #3. One then needs update the version of the current changelog entry
(if UNRELEASED), or create a new one with `dch
-v$new_upstream_version-1`. Finally, one may need to use `gbp pq` to
import, rebase, and export an existing quilt patch series onto the new upstream release.

https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#git-procedures
https://wiki.debian.org/Python/FAQ
https://wiki.debian.org/Python/GitPackaging

Other teams/individuals have different policies and practises.

I'm working on updating this package.

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 17 Sep 2021, Scott Talbert wrote:

Looking in the salsa repo [0], it is very old. And that shouldn't
happen. I
can updated to the last unstable version tonight/tomorrow.

Just to improve my knowledge about Debian processes: What does it mean
to update the salsa repo to the current upstream? Is it the same as
create a new package? Or is it just one step into creating a new
package?

I didn't look at the packages in question, but as a matter of team
policy, the Debian Python Team uses git-buildpackage repositories, with
pristine-tar, and a repo's layout is as follows:

1. Pristine-tar branch (upstream tarball is imported here)
2. Upstream branch (upstream tarball is unpacked here)
3. Debian packaging branch (name varies)
* https://dep-team.pages.debian.net/deps/dep14/ is the standardisation
effort the DPT has adopted.
* another key phrase is a "patches unapplied" packaging branch.

`gbp import-orig --pristine-tar --uscan` downloads the latest tarball
and puts it in #1, then unpacks it to #2, then creates an
upstream/new_version tag on this upstream branch, then merges that tag
to #3. One then needs update the version of the current changelog entry
(if UNRELEASED), or create a new one with `dch
-v$new_upstream_version-1`. Finally, one may need to use `gbp pq` to
import, rebase, and export an existing quilt patch series onto the new
upstream release.

https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#git-procedures
https://wiki.debian.org/Python/FAQ
https://wiki.debian.org/Python/GitPackaging

Other teams/individuals have different policies and practises.

I'm working on updating this package.

Package has been updated to version 3.0.1 and brought up to current
standards. :)

Scott

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)