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

Bug#1033194: marked as done (unblock: ruby-asciidoctor-include-ext/0.4.0-2)

Your message dated Tue, 4 Apr 2023 23:36:06 +0200
with message-id <ZCyYRuWZj/jQvu/J@ramacher.at>
and subject line Re: Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
has caused the Debian Bug report #1033194,
regarding unblock: ruby-asciidoctor-include-ext/0.4.0-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 owner@bugs.debian.org
immediately.)


-- 
1033194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033194
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: unblock
X-Debbugs-Cc: ruby-asciidoctor-include-ext@packages.debian.org
Control: affects -1 + src:ruby-asciidoctor-include-ext

Please unblock package ruby-asciidoctor-include-ext

[ Reason ]
This fixes a security issue CVE-2022-24803/#1009035 though it also includes an upstream update. This was uploaded to experimental on 2022-06-26 but missed reuploading to unstable as gitlab was using the versions directly from experimental (it was uploaded to experimental to not break the previos gitlab version before it switched to 0.4 version). Noticed this today in the rc bug list. 

[ Impact ]
Only reverse dependency is gitlab so it should not impact any other package in bookworm. 

[ Tests ]
gitlab in experimental was using it already for quite some time (upstream gitlab tests are fine) 

[ Risks ]
For bookworm it is a leaf package (only used by gitlab which is in unstable/experimental only) 

[ 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 ]
Since it has some other upstream changes, I have not included the debdiff. 

unblock ruby-asciidoctor-include-ext/0.4.0-2

--- End Message ---
--- Begin Message --- 
On 2023-03-19 17:48:16 +0530, Pirate Praveen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: ruby-asciidoctor-include-ext@packages.debian.org
> Control: affects -1 + src:ruby-asciidoctor-include-ext
> 
> Please unblock package ruby-asciidoctor-include-ext
> 
> [ Reason ]
> This fixes a security issue CVE-2022-24803/#1009035 though it also includes
> an upstream update.
> This was uploaded to experimental on 2022-06-26 but missed reuploading to
> unstable as gitlab was
> using the versions directly from experimental (it was uploaded to
> experimental to not break the
> previos gitlab version before it switched to 0.4 version). Noticed this
> today in the rc bug list.
> 
> [ Impact ]
> Only reverse dependency is gitlab so it should not impact any other package
> in bookworm.
> 
> [ Tests ]
> gitlab in experimental was using it already for quite some time (upstream
> gitlab tests are fine)
> 
> [ Risks ]
> For bookworm it is a leaf package (only used by gitlab which is in
> unstable/experimental only)
> 
> [ 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 ]
> Since it has some other upstream changes, I have not included the debdiff.
> 
> unblock ruby-asciidoctor-include-ext/0.4.0-2

not blocked: has successful autopkgtest

So there is nothing for us to do.

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: