Your message dated Wed, 23 Apr 2025 10:35:25 +0000
with message-id <e1u7xrt-00cra7...@fasolo.debian.org>
and subject line Bug#1103485: Removed package(s) from unstable
has caused the Debian Bug report #1030774,
regarding ruby-omniauth-auth0: Update to new upstream version 3.1.0
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.)


-- 
1030774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-omniauth-auth0
Version: 2.0.0-1
severity: wishlist
Control: forwarded -1 https://github.com/auth0/omniauth-auth0/issues/162

One test is failing but can't figure out why yet, asking upstream at https://github.com/auth0/omniauth-auth0/issues/162
--- End Message ---
--- Begin Message ---
Version: 3.1.0-2+rm

Dear submitter,

as the package ruby-omniauth-auth0 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1103485

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note 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.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to