Your message dated Thu, 17 Apr 2025 10:15:17 +0000
with message-id <e1u5mh7-005zvp...@respighi.debian.org>
and subject line unblock phing
has caused the Debian Bug report #1103404,
regarding unblock: phing/3.0.1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1103404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103404
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: unblock: phing/3.0.1-2
Package: release.debian.org
Control: affects -1 + src:phing
X-Debbugs-Cc: ph...@packages.debian.org
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: william...@wdes.fr
Severity: normal
Please unblock package phing
[ Reason ]
phing was part of bookworm.
[ Impact ]
Users using phing to automate tasks will be unable to use it.
There is no alternative software available.
[ Tests ]
DEP-8 tests where added to cover the code:
- unit tests
- testing the examples
- basic tests
And manual tests where run.
[ Risks ]
No alternatives.
The debdiff is not that big when you consider that most files where just
renamed.
I checked the full diff for breaking changes with git --minimal |
git-delta.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[-] attach debdiff against the package in testing
[ Other info ]
I only missed the fact that I should have let the previous version in
testing
to avoid this unblock situation.
unblock phing/3.0.1-2
--- End Message ---
--- Begin Message ---
Unblocked.
--- End Message ---
