Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13520 > unrolled thread

xlsxwriter: How to change homepage url

Back to article view | Back to linux.debian.maint.python

Contents

  xlsxwriter: How to change homepage url <c.buhtz@posteo.jp> - 2021-09-15 14:00 +0200
    Re: xlsxwriter: How to change homepage url Neil Williams <codehelp@debian.org> - 2021-09-15 14:50 +0200
      Re: xlsxwriter: How to change homepage url Andrius Merkys <merkys@debian.org> - 2021-09-15 15:00 +0200
        Re: xlsxwriter: How to change homepage url Scott Talbert <swt@techie.net> - 2021-09-15 15:10 +0200
          Re: xlsxwriter: How to change homepage url <c.buhtz@posteo.jp> - 2021-09-15 16:50 +0200
            Re: xlsxwriter: How to change homepage url Scott Talbert <swt@techie.net> - 2021-09-15 17:00 +0200
              Re: xlsxwriter: How to change homepage url <c.buhtz@posteo.jp> - 2021-09-15 17:30 +0200
                Re: xlsxwriter: How to change homepage url Emmanuel Arias <eamanu@yaerobi.com> - 2021-09-15 21:40 +0200
                  Re: xlsxwriter: How to change homepage url c.buhtz@posteo.jp - 2021-09-16 16:20 +0200
                    Re: xlsxwriter: How to change homepage url Nicholas D Steeves <sten@debian.org> - 2021-09-17 00:10 +0200
                      Re: xlsxwriter: How to change homepage url Scott Talbert <swt@techie.net> - 2021-09-17 16:30 +0200
                        Re: xlsxwriter: How to change homepage url Scott Talbert <swt@techie.net> - 2021-09-17 18:10 +0200

#13520 — xlsxwriter: How to change homepage url

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>

[toc] | [next] | [standalone]

#13521

[Multipart message — attachments visible in raw view] — view raw

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/

[toc] | [prev] | [next] | [standalone]

#13522

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

[toc] | [prev] | [next] | [standalone]

#13523

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

[toc] | [prev] | [next] | [standalone]

#13525

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

[toc] | [prev] | [next] | [standalone]

#13526

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

[toc] | [prev] | [next] | [standalone]

#13527

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.

[toc] | [prev] | [next] | [standalone]

#13528

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#13531

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

[toc] | [prev] | [next] | [standalone]

#13539

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#13540

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

[toc] | [prev] | [next] | [standalone]

#13541

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web