Your message dated Sat, 28 Dec 2024 03:00:12 +0000
with message-id <[email protected]>
and subject line Bug#1088370: Removed package(s) from unstable
has caused the Debian Bug report #1088370,
regarding RM: webcomponentsjs-custom-element-v0.js -- RoQA; outdated, 
obsolete(?), QA issue, low popcon
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 [email protected]
immediately.)


-- 
1088370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088370
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
User: [email protected]
Usertags: remove
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:webcomponentsjs-custom-element-v0.js

Forwarding
  <dr4azui5dsvtwsh6ngmfynvlgjcwfuumk6p5vzo75ises6n...@tarta.nabijaczleweli.xyz>
from [email protected],
because I also CCed the pacakger/uploader Timothy Potter <[email protected]>
and got "User Unknown (in reply to DATA command)"
and also forwarded the message to his other @hp.com address
and got "Invalid Recipient".

webcomponentsjs-custom-element-v0.js fell out of the dh-buildinfo
removal query (#1068809).

It saw one upload in 2016, there's a new upstream version since 2018,
it ships a fork of
  https://github.com/webcomponents/webcomponentsjs
which is archived, and had migrated to
  
https://github.com/webcomponents/polyfills/tree/master/packages/webcomponentsjs
where targets spec v1 now.

I don't see any rdeps and the popcon graph peaked on upload and
tailed off to the current figure of around inst=3 (nofiles=3) by 2018.

This package looks best-served by a RM instead of trying to resuscitate it.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libjs-webcomponentsjs-custom-element-v0 |  1.0.1-1.1 | all
webcomponentsjs-custom-element-v0.js |  1.0.1-1.1 | source

------------------- Reason -------------------
RoQA; outdated, obsolete(?), QA issue, low popcon
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected].

The full log for this bug can be viewed at https://bugs.debian.org/1088370

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].

Debian distribution maintenance software
pp.
Paul Richards Tagliamonte (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to