Help patching rest_dbus.py
guhan balasubramanian
guhan.sac at gmail.com
Thu Jul 19 04:57:01 AEST 2018
Hi Brad,
Thanks for getting back.
We were trying to prototype the use of the bottle web application to
POST/PUT a text/diff file to BMC, apart from the image. This is similar to
the octet-stream http request used for the image upload.
Regarding upstreaming, not sure what would be the interest for this to the
others.
Thanks,
Guhan
On Wed, Jul 18, 2018 at 6:22 AM Brad Bishop <bradleyb at fuzziesquirrel.com>
wrote:
>
> > On Jul 17, 2018, at 2:10 PM, guhan balasubramanian <guhan.sac at gmail.com>
> wrote:
> >
> > Hi,
> >
> > We are trying to make some custom changes to the phosphor web
> application.
>
> Can you describe what the custom changes are? Maybe upstreaming your
> changes
> is possible and you don’t need a bbappend at all.
>
> > Since the web application is present in meta-phosphor, we were trying to
> patch the web application from our own meta layer.
> >
> > From the tmp/work/ directory, I was able to create a git patch for the
> rest_dbus.py file in phosphor-gevent and phosphor-rest.
> >
> > But since the source is not included directly, I get a quilt error
> saying that there is no file to patch.
> >
> > The web (bottle) application I see, is included through the following
> variable:
> > SYSTEMD_ENVIRONMENT_FILE_${PN} += "obmc/wsgi_app"
> >
> > Can someone please help with what I am missing or the best way to go
> about this?
> >
> > -----
> > bash-4.2$ tree phosphor-rest/
> > phosphor-rest/
> > ├── phosphor-rest
> > │ └── 0001-rest-dbus-test.patch
> > └── phosphor-rest.bbappend
> >
> > 1 directory, 2 files
> > bash-4.2$ cat phosphor-rest/phosphor-rest.bbappend
> > FILESEXTRAPATHS_prepend := "${THISDIR}/phosphor-rest:"
> > SRC_URI += " \
> > file://0001-rest-dbus-test.patch \
> > "
> > bash-4.2$
> > -------
> >
> >
> > Thanks,
> > Guhan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20180718/e68913d1/attachment.html>
More information about the openbmc
mailing list