Acknowledgement sent
to Paul Gevers <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian Python Team <[email protected]>.
(Sun, 03 Dec 2023 21:09:04 GMT) (full text, mbox, link).
Source: hypercorn
Version: 0.14.4-1
Severity: serious
Control: close -1 0.15.0-1
Tags: sid trixie
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package src:hypercorn has been trying to migrate for
33 days [2]. Hence, I am filing this bug. The version in unstable has a
Depends on an RC buggy package: node-mermaid.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and trixie, so
it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=hypercorn
Acknowledgement sent
to Nilesh Patra <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Wed, 18 Sep 2024 13:45:03 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new
Dependency not in testing
Date: Wed, 18 Sep 2024 13:43:53 +0000
Hi Michael, Andrej,
New versions of hypercorn have not made it to testing in more than an
year. It has a dep on node-mermaid (stalling migration)
which I intend to remove, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080267
Please remove the dep on mermaid.
$ rmadison hypercorn
debian:
hypercorn | 0.11.2-1 | oldstable | source
hypercorn | 0.13.2-3 | stable | source
hypercorn | 0.14.4-1 | testing | source
hypercorn | 0.17.3-1 | unstable | source
--
Bug #1057351:
Source: hypercorn
Version: 0.14.4-1
Severity: serious
Control: close -1 0.15.0-1
Tags: sid trixie
User: [email protected]
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in
testing [1]. Your package src:hypercorn has been trying to migrate for
33 days [2]. Hence, I am filing this bug. The version in unstable has a
Depends on an RC buggy package: node-mermaid.
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.
This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and trixie, so
it doesn't affect (old-)stable.
If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.
Paul
[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=hypercorn
Acknowledgement sent
to Michael Fladischer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Wed, 18 Sep 2024 20:27:01 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new
Dependency not in testing
Date: Wed, 18 Sep 2024 21:57:23 +0200
Hi Nilesh,
Am 18.09.2024 um 15:43 schrieb Nilesh Patra:
> Please remove the dep on mermaid.
this will cause lintian warnings about the mermaid library loaded from a
CDN. As I have settled with uvicorn as my preferred ASGI server a while
ago, I would remove myself from uploaders. See if someone still deems it
worth to either fix the documentation build without mermaid or just drop
the python-hypercorn-doc package.
Otherwise I would just RM the package because of its low popcon.
Regards,
Michael
Acknowledgement sent
to "Andrej Shadura" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Wed, 18 Sep 2024 21:06:02 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new Dependency
not in testing
Date: Wed, 18 Sep 2024 22:37:03 +0200
Hi all,
On Wed, 18 Sep 2024, at 21:57, Michael Fladischer wrote:
Am 18.09.2024 um 15:43 schrieb Nilesh Patra:
>> Please remove the dep on mermaid.
>
> this will cause lintian warnings about the mermaid library loaded from a
> CDN. As I have settled with uvicorn as my preferred ASGI server a while
> ago, I would remove myself from uploaders. See if someone still deems it
> worth to either fix the documentation build without mermaid or just drop
> the python-hypercorn-doc package.
>
> Otherwise I would just RM the package because of its low popcon.
Please no RMs. I’m using hypercorn myself. I’ll fix it.
However, I’m still not sure why mermaid was removed in the first place, it’s quite useful to have it in Debian.
--
Cheers,
Andrej
Acknowledgement sent
to Nilesh Patra <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Thu, 19 Sep 2024 13:06:23 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new
Dependency not in testing
Date: Thu, 19 Sep 2024 13:02:33 +0000
On 2024-09-19 02:07, Andrej Shadura wrote:
> Hi all,
>
> On Wed, 18 Sep 2024, at 21:57, Michael Fladischer wrote:
> Am 18.09.2024 um 15:43 schrieb Nilesh Patra:
>>> Please remove the dep on mermaid.
>>
>> this will cause lintian warnings about the mermaid library loaded from a
>> CDN. As I have settled with uvicorn as my preferred ASGI server a while
>> ago, I would remove myself from uploaders. See if someone still deems it
>> worth to either fix the documentation build without mermaid or just drop
>> the python-hypercorn-doc package.
>>
>> Otherwise I would just RM the package because of its low popcon.
>
> Please no RMs. I’m using hypercorn myself. I’ll fix it.
> However, I’m still not sure why mermaid was removed in the first place, it’s quite useful to have it in Debian.
Hmm. How exactly?
Generally one would want to package JS libs for end-user applications.
Thus far only one package uses it that too just
for its documentation binary package. mermaid is also lying in a bad
state for 2+ years with little to no maintenance.
It's also not straightforward to maintain this (complicated with
multiple deps) package, keep up with new versions
and also fixup CVEs as they come.
Given that it has low popcon, only 1 reverse-dep (in ~5 years) that too
only for documentation and high cost of maintenance, I am
not really sure as to why this would be useful.
If you feel like, you are extremely welcome to take over the maintenance
of mermaid, close all the RC bugs with a new
upload/release and also close the RM bug provided you realistically have
the time/cycles. Otherwise I suggest
to release hypercorn with mermaid removed as a dep.
If you have any thoughts/opinions, please let me know.
Have a nice day! :)
Thank you
Nilesh
Acknowledgement sent
to "Nilesh Patra" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Sat, 26 Oct 2024 16:03:01 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new
Dependency not in testing
Date: Sat, 26 Oct 2024 21:16:32 +0530
On Thu Sep 19, 2024 at 2:07 AM IST, Andrej Shadura wrote:
> Hi all,
>
> On Wed, 18 Sep 2024, at 21:57, Michael Fladischer wrote:
> Am 18.09.2024 um 15:43 schrieb Nilesh Patra:
> >> Please remove the dep on mermaid.
> >
> > this will cause lintian warnings about the mermaid library loaded from a
> > CDN. As I have settled with uvicorn as my preferred ASGI server a while
> > ago, I would remove myself from uploaders. See if someone still deems it
> > worth to either fix the documentation build without mermaid or just drop
> > the python-hypercorn-doc package.
> >
> > Otherwise I would just RM the package because of its low popcon.
>
> Please no RMs. I’m using hypercorn myself. I’ll fix it.
It is now out of testing[1]. Popcon is not so high as well.
If there's lack of time to keep this, does it make sense to RM?
https://tracker.debian.org/news/1575732/hypercorn-removed-from-testing/
Thanks
Nilesh
Acknowledgement sent
to "Nilesh Patra" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Sat, 26 Oct 2024 16:36:01 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new
Dependency not in testing
Date: Sat, 26 Oct 2024 22:02:22 +0530
On Sat Oct 26, 2024 at 9:16 PM IST, Nilesh Patra wrote:
> On Thu Sep 19, 2024 at 2:07 AM IST, Andrej Shadura wrote:
> > Hi all,
> >
> > On Wed, 18 Sep 2024, at 21:57, Michael Fladischer wrote:
> > Am 18.09.2024 um 15:43 schrieb Nilesh Patra:
> > >> Please remove the dep on mermaid.
> > >
> > > this will cause lintian warnings about the mermaid library loaded from a
> > > CDN. As I have settled with uvicorn as my preferred ASGI server a while
> > > ago, I would remove myself from uploaders. See if someone still deems it
> > > worth to either fix the documentation build without mermaid or just drop
> > > the python-hypercorn-doc package.
> > >
> > > Otherwise I would just RM the package because of its low popcon.
> >
> > Please no RMs. I’m using hypercorn myself. I’ll fix it.
>
> It is now out of testing[1]. Popcon is not so high as well.
> If there's lack of time to keep this, does it make sense to RM?
I have removed the dep on mermaid for this package and just uploaded.
Feel free to implement a better solution if I missed it.
> https://tracker.debian.org/news/1575732/hypercorn-removed-from-testing/
>
> Thanks
> Nilesh
Source: hypercorn
Source-Version: 0.17.3-2
Done: Nilesh Patra <[email protected]>
We believe that the bug you reported is fixed in the latest version of
hypercorn, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra <[email protected]> (supplier of updated hypercorn package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 26 Oct 2024 21:40:58 +0530
Source: hypercorn
Architecture: source
Version: 0.17.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Nilesh Patra <[email protected]>
Closes: 1057351
Changes:
hypercorn (0.17.3-2) unstable; urgency=medium
.
* Team Upload.
* Partially Revert "Use local mermaid.js file instead of the
CDN one to prevent a privacy breach." (Closes: #1057351)
Checksums-Sha1:
1a3b62fb64c386e937a432e11555bf8975c8ac03 2053 hypercorn_0.17.3-2.dsc
d97178912ff2c827e9009478562f1b470a990633 5016 hypercorn_0.17.3-2.debian.tar.xz
f7fb5954bd888aabb8ea5edfaae7f45d01d659bc 9234 hypercorn_0.17.3-2_amd64.buildinfo
Checksums-Sha256:
99c7512b8aab70b60607f7e377e23f3e59eb69e28cd3bd170d0e59f682d5997a 2053 hypercorn_0.17.3-2.dsc
b9d5c4dacccbe81307ced6255aea811fc72254c3b07b37f93608f16b4d321cf9 5016 hypercorn_0.17.3-2.debian.tar.xz
3598d21cd13bfa5e4f878829d44ee4c8e5e1384508744c7668e67c8de457c645 9234 hypercorn_0.17.3-2_amd64.buildinfo
Files:
6a56bebb0833c245a0ef44c4d01cfd9e 2053 python optional hypercorn_0.17.3-2.dsc
5693258b2037d1ae850ff8ad746bd25b 5016 python optional hypercorn_0.17.3-2.debian.tar.xz
6a6b33f9a132ee6dde754dc067e49eb8 9234 python optional hypercorn_0.17.3-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIgEARYIADAWIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZx0ZiRIcbmlsZXNoQGRl
Ymlhbi5vcmcACgkQKieQS9ckPtpawwD/eAuXXmIfUZM80TVskxPdtI1G/x0rpLXY
2z95j4f7an0BAKeOEY//axnwrb4lCjbG3ow/fee9K9dYf4dH6UE5ID0E
=jAJD
-----END PGP SIGNATURE-----
Acknowledgement sent
to "Andrej Shadura" <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Python Team <[email protected]>.
(Sat, 26 Oct 2024 17:18:01 GMT) (full text, mbox, link).
Subject: Re: src:hypercorn: fails to migrate to testing for too long: new Dependency
not in testing
Date: Sat, 26 Oct 2024 18:41:47 +0200
Hi,
On Sat, 26 Oct 2024, at 17:46, Nilesh Patra wrote:
>> > Otherwise I would just RM the package because of its low popcon.
>>
>> Please no RMs. I’m using hypercorn myself. I’ll fix it.
>
> It is now out of testing[1]. Popcon is not so high as well.
> If there's lack of time to keep this, does it make sense to RM?
Please no RMs, just as I mentioned above.
--
Cheers,
Andrej