mercurial-importorig(1)

💖 mercurial-importorig 💖

okay bestie, so this is a page from the User Commands manual — it's the mercurial-importorig page and it's literally your new fave for shoving upstream tarballs into a Mercurial repo. iykyk 💅

---

🌸 NAME 🌸

mercurial-importorig — imports upstream source code tarballs into a .deb package Mercurial repository. that's the whole job. she does one thing and she ate. ✨

---

🦋 SYNOPSIS 🦋

mercurial-importorig [option] ... tarball [tarball] ...

---

✨ DESCRIPTION ✨

so what she does is: import upstream source tarballs into a Mercurial repository. 🫶

okay and here's the part you cannot skip, no cap — the first tarball must be the main tarball, check dpkg-source(1) for the deets. the upstream sources get incorporated into the upstream branch, and then merged into the default branch. main character behavior fr fr 👑

and yes, you can absolutely run mercurial-importorig multiple times to import several versions — but they have to be imported sequentially, starting with the earliest version. no skipping around, babe, the timeline is the timeline. 💀

okay so listen: for dpkg-source(1) format 3.0 (quilt), all patches are removed before the import, and you must manually reapply and refresh the patches. and then finally you must commit the fully patched source, including the .pc directory. not optional. that's just the rules bestie 😭

---

🎀 OPTIONS 🎀

• --version, -V — spits out the version and dips. that's it, that's the whole thing. bye 👋
• --verbose, -v — turns the verbosity up a notch. and guess what, you can stack it — use it several times for maximum yapping 📢
• --no-merge, -n — nope out of merging the imported upstream source into the default branch. you'll have to do a manual hg merge upstream later at some point instead. and remember to unapply all patches before the merge — seriously, don't forget 🙈

---

🌈 EXAMPLES 🌈

mercurial-importorig ../mypack_1.2.orig.tar.bz2
../mypack_1.2.orig-plugin.tar.gz

this one imports upstream source from two tarballs into the repository sitting in your current directory. and for that to work, the package has to be in dpkg source package format 3.0 (quilt) — again, see dpkg-source(1) 🫶. after the import, both the upstream branch and the default branch will have the tag mypack_1.2. slay. ⭐

---

👑 AUTHOR 👑

Jens Peter Secher <jpsecher@gmail.com> — the icon who made this 💜

---

💖 THANKS 💖

the ideas for this package originate from John Goerzen's hg-buildpackage. giving credit where credit is due, we love to see it 🎀

---

🔥 SEE ALSO 🔥

• mercurial-importdsc(1)
• mercurial-buildpackage(1)
• mercurial-tagversion(1)
• mercurial-pristinetar(1)
• mercurial-port(1)

---

mercurial-importorig version 0.10.1, dating all the way back to December 2009 🌸 — and that's the whole page bestie, go import some tarballs, you got this 💅✨🦋