Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Martin Jansa <martin.jansa@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd: Upgrade to 199
Date: Fri, 29 Mar 2013 01:18:56 -0700	[thread overview]
Message-ID: <D8B28775-1426-427F-B7CB-E10164FAF197@gmail.com> (raw)
In-Reply-To: <A54391FA-3CD5-4290-A92B-EE3477A2EEAE@dominion.thruhere.net>


On Mar 29, 2013, at 1:12 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:

> 
> Op 29 mrt. 2013, om 06:28 heeft Khem Raj <raj.khem@gmail.com> het volgende geschreven:
> 
>> 
>> On Mar 28, 2013, at 5:21 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> 
>>> On Thu, Mar 28, 2013 at 12:48:29AM -0700, Khem Raj wrote:
>>>> udevadm is now moved from /usr/bin to /bin so account for that
>>>> bash completions for udevadm should be packages with udev-utils
>>>> since thats where udevadm itself is, they were in systemd package
>>>> which is not correct location for it
>>>> 
>>>> Backport patches for readahead fixes on spinning disks
>>>> and to tackle error reported on missing /etc/sysctl.conf
>>> 
>>> Looks like it creates few new (empty) directories:
>>> 
>>> WARNING: QA Issue: systemd: Files/directories were installed but not
>>> shipped
>>> /etc/kernel
>>> /etc/kernel/install.d
>>> /usr/lib/kernel
>>> /usr/lib/kernel/install.d
>> 
>> 
>> OK I have created a new package called systems-kernel-install and these dirs along with
>> kernel-install binary are moved into the new package and updated the pull request.
> 
> There's a new releases, 200, mostly bugfixes and some hwdp and  keymap updates. Your 199 patch has the most important fixes, so I'm not sure if it's worth to respin to 200 or get this in and update to 200 (or 201) later.


yeah lets stay at 199 for some time and cherry pick fixes we need. 





  reply	other threads:[~2013-03-29  8:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  7:48 [PATCH 0/1] Upgrade systemd to 199 Khem Raj
2013-03-28  7:48 ` [PATCH 1/1] systemd: Upgrade " Khem Raj
2013-03-28 12:21   ` Martin Jansa
2013-03-29  5:28     ` Khem Raj
2013-03-29  8:12       ` Koen Kooi
2013-03-29  8:18         ` Khem Raj [this message]
2013-03-29 12:50           ` Andreas Müller
2013-03-29 12:56             ` Andreas Müller
2013-04-01 13:54             ` Colin Walters
2013-04-11 23:11               ` Andreas Müller
2013-04-12 10:06                 ` Burton, Ross
     [not found]                   ` <CALbNGRRCFyiD+6eY1xMe6o8dqtpuyf6YAEa7xKZ=f8wBv262uA@mail.gmail.com>
     [not found]                     ` <CAJTo0Ladru_hAgyL32SX8bDet3euSFz9Jf=jiJxBJqiNv8eseQ@mail.gmail.com>
     [not found]                       ` <CALbNGRQ+BqGarZWxmtj50S4rJbDtNPGqB=eWvotBVdVAcviedQ@mail.gmail.com>
2013-04-17  7:47                         ` Andreas Müller
2013-04-17  8:12                           ` Richard Purdie
2013-04-17  9:06                             ` Andreas Müller
2013-04-17 18:21                             ` Khem Raj
2013-03-29 16:07         ` Khem Raj
2013-03-28 13:24   ` Richard Purdie
2013-03-28 13:32     ` Koen Kooi
2013-04-02 10:58   ` Erik Botö
2013-04-02 14:08     ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D8B28775-1426-427F-B7CB-E10164FAF197@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox