Override component to main
rpi-eeprom 11.3-1ubuntu1 in hirsute: multiverse/misc -> main
rpi-eeprom 11.3-1ubuntu1 in hirsute arm64: multiverse/misc/optional/100% -> main
rpi-eeprom 11.3-1ubuntu1 in hirsute armhf: multiverse/misc/optional/100% -> main
3 publications overridden.
** Changed in:
Override component to main
raspberrypi-userland 0~20200520+git2fe4ca3-0ubuntu3 in hirsute: universe/libs
-> main
libraspberrypi-bin 0~20200520+git2fe4ca3-0ubuntu3 in hirsute arm64:
universe/misc/optional/100% -> main
libraspberrypi-bin 0~20200520+git2fe4ca3-0ubuntu3 in hirsute armhf:
Set the states to be ready for the AAs per [1].
This should resolve soon'ish.
[1]:
https://wiki.ubuntu.com/MainInclusionProcess?action=show=MIRTeam#Process_states
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok clarified, and good - thanks Dave!
All former concerns are resolved AFAICS.
Therefore since all else was ready let use mark this ready for promotion (and
after all this also is one of the cases that we kind of "already support but
want to make official").
** Changed in: raspberrypi-userland
We have assigned doko to re-review, but he is too often lost in too
important bugs (e.g. today in
https://bugs.launchpad.net/ubuntu/+source/fakeroot/+bug/1915250). So I
want to help here by doing the re-review.
The builds of
** Changed in: raspberrypi-userland (Ubuntu)
Assignee: (unassigned) => Matthias Klose (doko)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895137
Title:
[MIR] rpi-eeprom; raspberrypi-userland
** Changed in: raspberrypi-userland (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895137
Title:
[MIR] rpi-eeprom; raspberrypi-userland
To manage
** Changed in: raspberrypi-userland (Ubuntu)
Status: Incomplete => 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/1895137
Title:
[MIR] rpi-eeprom; raspberrypi-userland
To manage
Comment #16 was inappropriately added due to the following in the linux-
firmware-raspi2 changelog:
* Replaced postinst with flash-kernel trigger (relates to LP: #1895137)
So please ignore it, sorry for the noise!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The userland packages in the following PPA should address all points
raised by doko in the review in comment #13:
https://launchpad.net/~waveform/+archive/ubuntu/userland
I'm happy to attach a debdiff if that's preferable, but given the scale
of the changes I'm not sure that'd be easier to
FYI in MIR meeting of today:
[16:44] waveform: I wanted to know if this is incomplete as in "ack
I'll do it at some point" or as in "we'll give u then"
[16:44] cpaelzer, that's basically done - I've just got to update
the bug
--
You received this bug notification because you are a member of
raspberrypi-userland:
things which have to be fixed:
- the debian/copyright is incomplete. an fgrep -ri copyright
shows missing copyright holders, although these might
not be extensive. Please also check for possible missing
copyright holders which are not covered by the simple
check
Thanks Seth,
> Security team ACK for promoting rpi-eeprom to restricted CONDITIONAL
> on another team stating that they will provide testing resources and
> periodically import updated versions as appropriate.
Foundations team will handle regular importing of updated versions, and
SRUing to all
I reviewed rpi-eeprom version 9.0-1ubuntu1 as checked into groovy. This
isn't a full security audit but a very quick gauge of maintainability.
Because this is an architecture-specific review, the usual tooling doesn't
work for this case. This is a slight problem for maintenance, because the
** Description changed:
+ = rpi-eeprom =
+
[Availability]
The package is in proposed, pending a correction to Architecture to permit it
to migrate to multiverse (LP: #1884748).
[Rationale]
The package is required for updating the boot EEPROM on the Raspberry Pi 4.
[Security]
I
Thanks Dave and Dimitri!
Former issues:
- subscription - done
- install in other places is now working fine
The service fails (split to bug 1898160), but that isn't too bad as at least
no half-installed packages are happening anymore.
- updated to the most recent version
- version depends on
Arr I forgot, we still wait for Securtity on rpi-eeprom.
But ok, the MIR Ack you have - it can go to Fix Committed as soon as they are
happy as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@christian updated rpi-eeprom is now in groovy, and it is now "done
right".
** Changed in: rpi-eeprom (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package rpi-eeprom - 9.0-1ubuntu1
---
rpi-eeprom (9.0-1ubuntu1) groovy; urgency=medium
* Ubuntu port (LP: #1884748), including changes for MIR (LP: #1895137)
* Added d/watch
* Added d/p/use_python3_no_env.patch to remove env from rpi-eeprom-config
*
> > - Please consider updating to a newer version before you SRU things to
> >=Focal
>
> Is it best at this point to fix the existing 7.8 upload, or reject that
> and fix all this in a new 9.0 upload? Happy to do whichever is easier
> from the MIR/security team's perspective.
IMHO cancel what is
> > - You refer to an empty VCS, having the changes commit-by-commit in this or
> > another one (depending where you push) woud be great. Please fix the VCS
> > entry to point at such a valid repo.
>
> Ah, I was under the misapprehension that the launchpad repo would be
> populated by the
> Just to clarify, is this suggesting it should install cleanly on non-pi
> arm hardware, but *then* refuse to work (with some appropriate error
> message) or should it refuse to install at all e.g. at dependency
> resolution time. I'd love to implement the latter but I've no idea how
> (is there
> This one is hard to decide as it has binary blobs in the form of
> the RPI firmware. Usually for normal package that would be a denial
> reason, but other microcode delivering packages work the same way.
Just a quick note on this one, in case it changes anything: as rpi-
eeprom is currently
FYI: Fused the thematically and use-case wise raspberry-userland MIR
with the bug here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895137
Title:
[MIR] rpi-eeprom
To manage notifications about
[Summary]
This one is hard to decide as it has binary blobs in the form of
the RPI firmware. Usually for normal package that would be a denial
reason, but other microcode delivering packages work the same way.
I'll need to discuss and co-ack with other MIR Team members and
also need security to
** Also affects: raspberrypi-userland (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Availability]
The package is in proposed, pending a correction to Architecture to permit it
to migrate to multiverse (LP: #1884748).
[Rationale]
The package is required
** Changed in: rpi-eeprom (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895137
Title:
[MIR] rpi-eeprom
To manage
27 matches
Mail list logo
