Override component to main
systemd-container 237-3ubuntu10.48 in bionic amd64:
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic arm64:
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic armhf:
universe/admin/optional/100% -> main
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152187
Title:
[MIR] systemd
To manage notifications about this bug
** Merge proposal linked:
https://code.launchpad.net/~utkarsh/ubuntu-seeds/+git/ubuntu-seeds/+merge/403505
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152187
Title:
[MIR] systemd
To manage
Hello,
> For the record, ack from the Ubuntu Security Team on promoting the
> systemd-container binary from universe to main in bionic.
Thank you, Steve! I'll work on doing the next steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yes, the systemd-container package will end up in main, likely for the
current package in bionic-updates, and thus will be reflected that way
in rmadison etc.
For the record, ack from the Ubuntu Security Team on promoting the
systemd-container binary from universe to main in bionic.
Thanks.
--
The usual way we determine if a package is in main or not is to check
the package lists; will the promotion step make the systemd-container
binary package visible to package lists or rmadison output?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
we usually don't require MIRs for new binary packages. Please just make
sure that the security team knows about the added binary in bionic, and
then we can promote it.
** Changed in: systemd (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are
Hello,
Revisiting this MIR since we (now) want to have systemd-container (from
src:systemd) from Bionic/universe in Bionic/main.
This package is to be included in the Google cloud images the public
cloud team builds, going back to Bionic. As cloud images are to ship
only packages from main, this
Ryan: the reason /etc/localtime isn't a symlink was always to support
/usr being on a separate partition. Reverting this will force
completion of the work to have the initramfs mount /usr, which AFAIK is
not yet done in raring.
--
You received this bug notification because you are a member of
zbyszek [2013-03-22 18:30 -]:
That is unexpected. Can you elaborate? At least on Debian/sid it
builds fine with PYTHON=python3.
Indeed, current master builds fine now. Thanks for pointing out!
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)
Martin Pitt (pitti) wrote on 2013-03-15:
Matthias Klose [2013-03-15 4:58 -]:
- is there a reason not to provide a python3-systemd package?
It doesn't currently build with PYTHON=python3.
That is unexpected. Can you elaborate? At least on Debian/sid it builds fine
with PYTHON=python3.
I've reviewed the review in comment #14 and looked over the code myself
as well as talking to Lennart.
Point-by-point:
- I don't understand why having /etc/localtime as a symlink is anything
but desirable other than that Debian didn't do it this way before. I do
notice that the symlink is not
I was asked to expand the audit I performed earlier (summarized in
comment #5 above). I reviewed version 198-0ubuntu0ppa2 from pitti's PPA.
Again, this is not intended to be a complete audit. Not everything I found
is a security issue, I'm just reporting things that looked surprising to me.
On Thu, Mar 14, 2013 at 8:18 PM, Michael Terry
michael.te...@canonical.com wrote:
Should keep a watch on Debian bug 701364, which says it ftbfs with gcc-4.8.
That bug has a link to upstream commit from 2012-11-14, which I
believe is included in systemd 198.
--
You received this bug
Hello Michael, Matthias,
thanks for the review!
Michael Terry [2013-03-14 16:18 -]:
* Existing bugs seem tolerable (most of them deal with the init
pieces anyway). Should keep a watch on Debian bug 701364, which
says it ftbfs with gcc-4.8.
I built current master and 198 with gcc-4.8,
systemd with enabled make check tests is in raring now. I had to
disable the unit-name test as it fails on the buildds (presumably they
don't have a /etc/hostname), the other 25 succeed now.
I also wrote autopkgtests for the three D-BUS services hostnamed, localed, and
timezoned, and fixed
Awesome, thanks Martin! Approved for the binary packages we need
(systemd-services and such; and obviously the udev packages which are
already in main).
** Changed in: systemd (Ubuntu)
Status: New = Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: Michael Terry (mterry) =
Thanks! I moved the source to main, and the libsystemd-* libraries, so
that component-mismatches will be happy. I keep systemd-services in
universe for now, as the FFE hasn't been approved yet.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug
- is there a reason not to provide a python3-systemd package?
- gcc-4.8 can be found in the ubuntu-toolchain-r ppa
- just want to clarify that the MIR is currently not done for the systemd
package,
which I assume will stay in universe.
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu)
Assignee: MIR approval team (ubuntu-mir) = Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152187
Title:
[MIR] systemd
To manage
And now for the packaging/maintainability review. I looked only at
version 198 in raring-proposed.
* Packaging is understandably complex. Not only are there lots of
vaguely-related components in this one source, but they are system-level core
bits.
* Builds cleanly.
* Has bug subscribers.
*
Seth already reviewed the version 198 packages in the PPA, but for the
record: 198 has landed in raring-proposed (after Seth's pre-approval on
IRC), and removed from the PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just installed the new udev (175-0ubuntu20) and all appropriate dependants.
However, now my 64-bit nvidia graphics card setup ends up in busybox.
I can go on with normal boot by commanding exit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I reviewed version 198-0ubuntu0ppa2 from pitti's PPA.
I confined my review primarily to src/logind/ and src/udevd/ directories,
as these are the largest of the components we intend to use. This should
not be considered a full security audit, but rather a quick and dirty
gauge of code cleanliness.
- Minimal tests; extensive global state would be difficult to test
Actually, upstream does quite extensive testing with automatically
building VM images and booting them in qemu-kvm:
http://cgit.freedesktop.org/systemd/systemd/tree/test ; but these are
not shipped in release tarballs. I think
@MIR team: We want to update systemd to the current version 198 instead
of releaseing raring with the old version 44. Some packages like gnome-
session require a newer version than 44, and we would thus not be able
to convert that to logind session tracking. So please feel free to
review the
** Changed in: systemd (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) = Seth Arnold (seth-arnold)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152187
Title:
[MIR] systemd
To manage
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152187
Title:
[MIR] systemd
To manage notifications about
For the record, if you want to play with this: https://launchpad.net
/~ubuntu-core-dev/+archive/logind . This also stages packages which
block on this MIR until we can upload them, like pulseaudio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
29 matches
Mail list logo
