From: Elliott Mitchell <ehem+xen@m5p.com>
To: Roman Shaposhnik <roman@zededa.com>
Cc: J??rgen Gro?? <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Roger Pau Monn?? <roger.pau@citrix.com>, Wei Liu <wl@xen.org>,
George Dunlap <george.dunlap@citrix.com>
Subject: Re: Linux DomU freezes and dies under heavy memory shuffling
Date: Wed, 24 Feb 2021 20:47:52 -0800 [thread overview]
Message-ID: <YDcr+Dd2hz9IK6BT@mattapan.m5p.com> (raw)
In-Reply-To: <CAMmSBy91csJ3MGrV8CPYX-fNdkFu6P12zEr2LjCbchvAeEsTKA@mail.gmail.com>
On Wed, Feb 24, 2021 at 08:30:45PM -0800, Roman Shaposhnik wrote:
> Right -- but that's not what distro builders use, right? I mean they do
> the whole sdeb -> deb business.
>
> In fact, to stay as faithful as possible -- I'd love to:
> 1. unpack SDEB
> 2. add a single patch to the set of sources
> 3. repack SDEB back
> 4. do whatever it is they do to go SDEB -> DEB
Oh, that close to the original distribution package. For
Debian-derivatives, install the package "dpkg-dev".
Generally the distribution will have a page somewhere where you can get
the files, but often it is handiest to run `apt-get source <package>` (I
believe `apt source <package>` also works, but I'm used to `apt-get`).
This will grab the tarballs for the source and unpack them.
Go into the unpacked directory and run `dpkg-buildpackage -b`
(optionally, patch first). This creates the package in the starting
directory.
The tarballs left behind in the starting directory can be nuked or saved.
If saved, the build directory can be recreated by running
`dpkg-source -x <src-package-name>_<ver>.dsc`. This lets you reset the
build directory to original state.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
next prev parent reply other threads:[~2021-02-25 4:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 20:03 Linux DomU freezes and dies under heavy memory shuffling Roman Shaposhnik
2021-02-16 20:34 ` Stefano Stabellini
2021-02-17 6:47 ` Jürgen Groß
2021-02-17 8:12 ` Roman Shaposhnik
2021-02-17 8:29 ` Jürgen Groß
2021-02-18 5:21 ` Roman Shaposhnik
2021-02-18 9:34 ` Jürgen Groß
2021-02-23 13:17 ` Jürgen Groß
2021-02-25 3:06 ` Roman Shaposhnik
2021-02-25 3:44 ` Elliott Mitchell
2021-02-25 4:30 ` Roman Shaposhnik
2021-02-25 4:47 ` Elliott Mitchell [this message]
2021-03-12 21:33 ` Roman Shaposhnik
2021-03-13 7:18 ` Jürgen Groß
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=YDcr+Dd2hz9IK6BT@mattapan.m5p.com \
--to=ehem+xen@m5p.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=roman@zededa.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).