[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1005328: marked as done (RM: uglifyjs/2.8.29-8)

Your message dated Sat, 4 Mar 2023 17:11:40 +0100
with message-id <c8a860c4-cd90-e8d2-fb6a-511aa9ccda1d@debian.org>
and subject line Re: Bug#1005328: RM: uglifyjs/2.8.29-8
has caused the Debian Bug report #1005328,
regarding RM: uglifyjs/2.8.29-8
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 owner@bugs.debian.org
immediately.)


-- 
1005328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005328
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm
X-Debbugs-Cc: Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

uglifyjs v2 was last updated upstream in 2017, and has no real
maintainer in Debian since December 2020 - see bug#958117

The package should not be released with bookworm, but may still have
reverse (build-)dependencies, and I therefore request removal only from
testing for now.  Please advice if another approach is more sensible.

(I tried to get the package auto-kicked from testing by filing
release-critical bug#958117 but evidently that didn't work.)


 - Jonas

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

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIGQ8EACgkQLHwxRsGg
ASGcbw//TF1/n+bTOHNqo2UR5/PNAs818+b7CN2uKH+xFXSY3seSnyE95DEHng7K
2rNOTgo7Io2mOvQ2ND+vE0niPqm/p1wwFl70q1Owl0TQ4Dibw5MniXjc55wwQxX4
8wfJY3c4xlLneeiIr9+AskrqbafonDrRTxCC+NAtvTSQSBgsPdOUDPG15umHwSu3
/sx6bfsmH/LzSw6L6/yiskys3C4CfA4FYlcPdKZK+gWkmb+VWdhn1T4hRaUAN2I8
HCuJFGQns7ckb7O/RwSnOkC5ct9c00P8Y1O1kEUxkrGlBmMEq0mIvlCEP63t31Ud
ZtmJt/K4WQJ4G/IVfG4/dtcEomPGmZIn07CFEqOU9B1r++nubeCULiCa2Tc9WsmQ
eTziPFTcX24lRQ+O69ukg5G+N5WHKKu9uHYacZJa9jdS6qe5TKp07IH+BwTe4w9E
LyG8AegBAVjnJ8U68B+KWFXrdpAkcjv3En7IeU3vryUXNPsZr2b3go/Ac2XecdFX
268H9z2rlUiamWQ6bOUNW8DYRvHF7CFNlVJ0tfgyo1bLNNjKjEwCfkHsTSsXQOt5
8g0UkVc168m//PrXQlNWJLWUV4VT+p0QLQGoEC6ES6N61U0H8zVRBEu048b3DFs3
W0QBhZDHxyJUAm1MbiAnRGmzY4/dxkFs4uZmAXRU/zired3XnaM=
=40Qo
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Hi Jonas,

On 11-02-2022 18:23, Jonas Smedegaard wrote:

@Yadd: You did the mass-filing - can I ask you to please bump severity,
since the normal process of bumping _after_ a package releationship
changes to be a FTBFS cannot be used here because src:uglifyjs is
transitively a key package.  Maybe my post to bug#979886 is useful for
such followup mail.
This bumping either caused those bugs to be fixed, or the packages removed from bookworm. One *new* reverse Build Depends (tryton-sao) appeared (I just filed a bug for that: 1032353). I would appreciate it if you helped the maintainer to migrate (because it's late in the release). 

I have added a removal hint.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: