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.
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.
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?).
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
It seems that this package should probably be fully moved and adopted
into the Debian Python Team - it seems to have been partially done.
so that would need to be sorted out.
This sounds like a task that should be taken by someone more
experienced then me.
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?
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?).
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.
Or, perhaps Christian (the initial of this thread) can/want to do it (Christian,
write to me if you need help)?
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).
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?
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.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 84:08:28 |
Calls: | 8,091 |
Files: | 13,069 |
Messages: | 5,851,128 |