chiark
/
gitweb
/
~ianmdlvl
/
dgit.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
dgit: Improve some error messages about changes files
[dgit.git]
/
dgit-user.7.pod
diff --git
a/dgit-user.7.pod
b/dgit-user.7.pod
index c33cf300e36b096c7b9bd0717f6374b81ba91ef0..5713064b86a781cc116d41370df1661d5c32c54f 100644
(file)
--- a/
dgit-user.7.pod
+++ b/
dgit-user.7.pod
@@
-35,7
+35,7
@@
or L<dgit(1)> and L<dgit(7)>.
% curl 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28250;mbox=yes;msg=89' | patch -p1 -u
% git commit -a -m 'Fix libc lost output bug'
% gbp dch -S --since=dgit/dgit/sid --ignore-branch --commit
% curl 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=28250;mbox=yes;msg=89' | patch -p1 -u
% git commit -a -m 'Fix libc lost output bug'
% gbp dch -S --since=dgit/dgit/sid --ignore-branch --commit
- %
sudo apt-get build-dep glibc
+ %
mk-build-deps --root-cmd=sudo --install
% dpkg-buildpackage -uc -b
% sudo dpkg -i ../libc6_*.deb
% dpkg-buildpackage -uc -b
% sudo dpkg -i ../libc6_*.deb
@@
-288,15
+288,11
@@
a complete treatment is beyond the scope of this tutorial.
=over 4
=over 4
- %
sudo apt-get build-dep glibc
+ %
mk-build-deps --root-cmd=sudo --install
% dpkg-buildpackage -uc -b
=back
% dpkg-buildpackage -uc -b
=back
-apt-get build-dep installs the build dependencies according to the
-official package, not your modified one. So if you've changed the
-build dependencies you might have to install some of them by hand.
-
dpkg-buildpackage is the primary tool for building a Debian source
package.
C<-uc> means not to pgp-sign the results.
dpkg-buildpackage is the primary tool for building a Debian source
package.
C<-uc> means not to pgp-sign the results.
@@
-371,8
+367,9
@@
have enabled.
You'll need a chroot for each of the secondary architectures.
This is somewhat tiresome,
even though Debian has excellent tools for managing chroots.
You'll need a chroot for each of the secondary architectures.
This is somewhat tiresome,
even though Debian has excellent tools for managing chroots.
-C<sbuild-createchroot> from the sbuild package is a
-good starting point.
+C<sbuild-debian-developer-setup> from the package of the same name
+and C<sbuild-createchroot> from the C<sbuild> package are
+good starting points.
Otherwise you could deinstall the packages of interest
for those other architectures
Otherwise you could deinstall the packages of interest
for those other architectures