Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-15 14:23:25)
> Because I put it in my business, I was looking for a quick fix. But
> there isn't a quick fix here. It needs serious help from multiple DMs.
Just multiple persons - requires only one "Debian insider".
The only thing that re
Jonas,
My expectations and understanding of how things work in Debian were way off.
My frustration and entitlement were loud and misdirected and I apologize for
that, you've been extremely patient.
It is very easy for a person to use Debian software for years without
understanding anything that
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-14 22:51:05)
> I think I understand now. I would like do what is needed for asterisk. My
> current focus is the asterisk bug tracker, as you have mentioned.
Sounds good.
And again: Sorry if I come across as brutal and/or stubborn - I am n
I think I understand now. I would like do what is needed for asterisk. My
current focus is the asterisk bug tracker, as you have mentioned.
Thanks again,
Martin
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-14 04:19:03)
> > Why later? Whay not now?
>
> My efforts to close this bug have failed.
The goal of this bug is not to have it closed, but to establish routines
that makes it unlikely for this bug to need reopening.
> I have already said
> Why later? Whay not now?
My efforts to close this bug have failed.
I have already said the same thing as Marco: That I would do it, and stated my
use case as he did. I can only assume his offer was deemed reliable because he
has a proven track record within the Debian community, which I don't h
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-13 22:30:43)
> Regarding how to resolve this bug, see #1030669 which has the same demand
> and was closed by a promise from Marco d'Itri. If you don't look him up or
> already know who he is, he says "I manage about 150 instances of Varnish
Jonas,
Regarding how to resolve this bug, see #1030669 which has the same demand
and was closed by a promise from Marco d'Itri. If you don't look him up or
already know who he is, he says "I manage about 150 instances of Varnish,
so let's just assume that I have the experience needed and some moti
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-13 02:17:00)
> It is my assumption that this bug opened because the security team was
> left with a stable package that nobody on the pkg-voip-team was
> maintaining, so I understand why they don't want that to happen again,
> especially wi
It is my assumption that this bug opened because the security team was left
with a stable package that nobody on the pkg-voip-team was maintaining, so I
understand why they don't want that to happen again, especially with a package
with as many CVEs as asterisk. Please correct me if I'm wrong ab
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-12 22:41:16)
> Jonas,
>
> Will you close #1031046 if I file a bug with the tracker
> pseudo-package?
> If no, what do you need for this bug to close?
First, I am not sure it is for me or for us or for the security team to
close the bugrep
Jonas,
Will you close #1031046 if I file a bug with the tracker pseudo-package?
If no, what do you need for this bug to close?
Martin
Quoting Martin Rampersad via Pkg-voip-maintainers (2024-12-12 18:23:50)
> The tracker (https://tracker.debian.org/pkg/asterisk) states that
> there are three security issues in bookworm, but I have not been able
> to figure out how to address these. There is no asterisk package in
> bookworm, there
Hi Moritz,
I have joined the pkg-voip-team and I am willing to backport/test security
fixes across the three year lifecycle for asterisk.
Is there some action you need us to take to allow this bug to close?
The tracker (https://tracker.debian.org/pkg/asterisk) states that there are
three secu
Source: asterisk
Version: 1:20.1.0~dfsg+~cs6.12.40431414-1
Severity: serious
Asterisk should only be included in Bookworm with a reliable commitment
by the maintainers to backport/test security fixes across the typical
three year life cycle (two years of stable-security and one year of
oldstable-s
15 matches
Mail list logo
