Control: tags 1030047 + patch
Control: tags 1030047 + pending
Dear maintainer,
I've prepared an NMU for ruby-sanitize (versioned as 6.0.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru ruby-sanitize-6.0.0/debian/changelog
Processing control commands:
> tags 1030047 + patch
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Added tag(s) patch.
> tags 1030047 + pending
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Added tag(s) pending.
--
1030047: https://bugs.debian.org/cgi-bin/bugrepo
Thank you for your contribution to Debian.
Mapping bullseye to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 07 Feb 2023 10:33:52 +0100
Source: vagrant
Architecture: source
Version: 2.2.14+dfsg-2
Distribution: bullse
vagrant_2.2.14+dfsg-2_source.changes uploaded successfully to localhost
along with the files:
vagrant_2.2.14+dfsg-2.dsc
vagrant_2.2.14+dfsg-2.debian.tar.xz
vagrant_2.2.14+dfsg-2_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
_
ruby-sanitize_6.0.0-1.1_source.changes uploaded successfully to localhost
along with the files:
ruby-sanitize_6.0.0-1.1.dsc
ruby-sanitize_6.0.0-1.1.debian.tar.xz
ruby-sanitize_6.0.0-1.1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing commands for cont...@bugs.debian.org:
> severity 1030047 grave
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1030047: https://bugs.debian.org/cgi-b
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 20 Feb 2023 11:27:14 -0500
Source: trocla
Architecture: source
Version: 0.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Jérôme C
trocla_0.5.1-1_source.changes uploaded successfully to localhost
along with the files:
trocla_0.5.1-1.dsc
trocla_0.5.1.orig.tar.gz
trocla_0.5.1-1.debian.tar.xz
trocla_0.5.1-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
__
Processing commands for cont...@bugs.debian.org:
> retitle 606982 redmine: needs a way to run as a separate user per instance
Bug #606982 [redmine] redmine: fails to upgrade all instances
Bug #606983 [redmine] run redmine as the redmine user
Changed Bug title to 'redmine: needs a way to run as a s
On 20/02/2023 16:23, Jakob Haufe wrote:
Control: tag -1 + help
On Mon, 20 Feb 2023 15:57:23 +0100
Andre Heider wrote:
Adding "gem 'thin'" to /usr/share/redmine/Gemfile fixes it for me.
I've no idea about ruby stuff, so that's probably not an appropriate
solution. Does this need to be fixed o
Your message dated Mon, 20 Feb 2023 16:26:42 +0100
with message-id <20230220162642.46679909@beer>
and subject line Re: Bug#1015796: bullseye backport
has caused the Debian Bug report #1015796,
regarding bullseye backport
to be marked as done.
This means that you claim that the problem has been dea
Processing control commands:
> tag -1 + help
Bug #1031685 [redmine] redmine doesn't work as thin instance
Added tag(s) help.
--
1031685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
_
Control: tag -1 + help
On Mon, 20 Feb 2023 15:57:23 +0100
Andre Heider wrote:
> Adding "gem 'thin'" to /usr/share/redmine/Gemfile fixes it for me.
>
> I've no idea about ruby stuff, so that's probably not an appropriate
> solution. Does this need to be fixed or can I solve that without
> modi
This can be closed, a backport is available now.
Thanks!
Andre
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 20 Feb 2023 19:51:05 +0530
Source: redmine
Binary: redmine redmine-mysql redmine-pgsql redmine-sqlite
Architecture: source all
Version: 5.0.4-4~bpo11+1
Distribution: bull
Package: redmine
Version: 5.0.4-2~bpo11+1
I've a ~3 year old redmine+thin+nginx oldstable setup which I couldn't
use since upgrading to bullseye. Now that there's a backport (many
thanks for finally having one!), I tried to get that old instance
working again.
It seems the packages have been
redmine_5.0.4-4~bpo11+1_amd64.changes uploaded successfully to localhost
along with the files:
redmine_5.0.4-4~bpo11+1.dsc
redmine_5.0.4.orig.tar.xz
redmine_5.0.4-4~bpo11+1.debian.tar.xz
redmine-mysql_5.0.4-4~bpo11+1_all.deb
redmine-pgsql_5.0.4-4~bpo11+1_all.deb
redmine-sqlite_5.0.4-4~b
Your message dated Mon, 20 Feb 2023 14:39:24 +
with message-id
and subject line Bug#1031308: fixed in redmine 5.0.4-4
has caused the Debian Bug report #1031308,
regarding redmine FTBFS: test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 20 Feb 2023 19:31:13 +0530
Source: redmine
Architecture: source
Version: 5.0.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Utkarsh
redmine_5.0.4-4_source.changes uploaded successfully to localhost
along with the files:
redmine_5.0.4-4.dsc
redmine_5.0.4.orig.tar.xz
redmine_5.0.4-4.debian.tar.xz
redmine_5.0.4-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
20 matches
Mail list logo