Override component to main
frr 8.1-1 in jammy amd64: universe/net/optional/100% -> main
frr 8.1-1 in jammy arm64: universe/net/optional/100% -> main
frr 8.1-1 in jammy armhf: universe/net/optional/100% -> main
frr 8.1-1 in jammy ppc64el: universe/net/optional/100% -> main
frr 8.1-1 in jammy
Archive Admin, please promote src:frr and these binary packages to main:
frr
frr-pythontools (pulled in by frr via Recommends)
Note libyang2 will be pulled in as well, and its MIR (#1958293) was
completed and ACKed.
Leave in universe:
frr-snmp
frr-rpki-rtrlib (uses a library that is still in
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu-seeds/+git/platform/+merge/415918
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage
The libyang2 MIR[1] got an ACK from security
1. https://bugs.launchpad.net/ubuntu/+source/libyang2/+bug/1958293
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage
Everything resovled - in the MIR meeting we decided today that for this special
case no security re-review is needed.
Setting to "in progress" to reflect that it is ready.
But it has to wait on libyang2 still to fully be ready.
** Changed in: frr (Ubuntu)
Assignee: Didier Roche (didrocks)
Seeding is here:
$ grep -Hrn quagga platform-git ubuntu-git/
platform-git/supported-misc-servers:175: * quagga #
RobertCollins
Therefore this is what we will change to promote FRR and demote quagga
at the same time.
--
You received this bug notification because you are a
This is requested by security to be in Jammy for reasonable long term support
of the routing daemon.
Setting prio critical and milestone to jammy-FF
** Changed in: frr (Ubuntu)
Milestone: ubuntu-22.01 => ubuntu-22.04-feature-freeze
** Changed in: frr (Ubuntu)
Importance: Undecided =>
At least it's fixed upstream.
I'll address the remaining points next week, as I'm on +1 maintenance
this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage
Yeah, I don’t think that worths a delta. My general annoyance with this
is that when you start having some warnings/errors in a project during
build, you start accepting more and more of them until it’s not readable
and you miss a valid concern. This is why, I tend to patch and add
either linter
I wonder if it's worth adding a delta with debian for this strncmp()
fix, though.
The upstream patch switches to strcmp(), arguing that these buffers are
always null terminated. In that case, even the incorrect size_t
parameter for strncmp() (source of the warning) won't matter, as the
comparison
For the strncmp() warnings, I filed an upstream bug[1] and it was
promptly fixed. I also filed a LP bug for me to fix it in Ubuntu, and
forward to Debian.
1. https://github.com/FRRouting/frr/issues/10484
2. https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1959896
** Bug watch added:
> specified bound depends on the length of the source argument
[-Wstringop-truncation]
I believe the strncpy warning can be ignored because the buffer was
reallocated using that size just before:
static void str_append(char **buf, const char *repr)
{
if (*buf) {
*buf = realloc(*buf,
> * It is on the lto-disabled list. Fix, or the work-around should be
directly in the package.
Good catch.
I checked and it was incorrectly added to that list, and filed a bug to
remove it:
https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1959838
--
You received this bug notification
[Summary]
Thanks a lot Andreas for the detailed and high quality MIR, with
relevant researches and background information.
I was first tempted to diff between quagga and frr to do a quick
assessement. However, there are too many differences to avoid doing a
full package checks. Here are my
** Changed in: frr (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage notifications about this bug go
** Description changed:
[Availability]
The package frr is already in Ubuntu universe.
The package builds for the architectures it is designed to work on.
It currently builds and works for architetcures: amd64, arm64, armhf,
ppc64el, s390x, riscv64
Link to package:
** Changed in: frr (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: frr (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- placeholder for MIR
-
- - frr has its roots in quagga
- - quagga is unmaintained upstream:
+ [Availability]
+ The package frr is already in Ubuntu universe.
+ The package builds for the architectures it is designed to work on.
+ It currently builds and works for
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage notifications about this bug go to:
** Changed in: frr (Ubuntu)
Milestone: None => ubuntu-22.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage notifications about this bug go to:
** Changed in: frr (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951834
Title:
[MIR]: frr
To manage notifications about this bug go to:
21 matches
Mail list logo
