launchpad-users team mailing list archive

["Chris Good" <chris.good@xxxxxxxxxxxxxx>]

Hi Jorg & Gianfranco ,

 

Thanks very much for your help.

 

Jorg,

 

Thanks for your link to https://wiki.ubuntu.com/PbuilderHowto.

 

I actually tried to build the source  package by following

http://packaging.ubuntu.com/html/fixing-a-bug.html :

 

                4.6. Testing the fix

 

                To build a test package with your changes, run these commands:

 

                $ bzr builddeb -- -S -us -uc

                $ pbuilder-dist <release> build ../<package>_<version>.dsc

 

                This will create a source package from the branch contents (-us -uc will just omit the step to sign the source package) and     pbuilder-dist will build the package from source for whatever release you choose.

 

I did :

 

                pbuilder-dist trusty build ../netkit-rwall_0.17-8ubuntu2.dsc

 

rather than (as PbuilderHowto says):

 

                Rebuilding a package

                ...

                Now build the package using your chroot cleanroom you created with the command: 

                    sudo pbuilder build *.dsc

 

                Once the packages are successfully built, the binary and source packages will be stored in /var/cache/pbuilder/result/

 

The packages were built under ~/pbuilder/trusty_result rather than /var/cache/pbuilder/result.

I didn't know at the time that there should have been source packages created and a *source.changes file created.

(I didn't know what a source package should look like...)

 

Apparently the source package was not created as it is not there now.

Are these 2  methods just different way of doing the same thing?

Any idea why a source package was not created?

 

Gianfranco:

 

I tried:

 

cgood@goodi7:/home/cgood/netkit-rwall/netkit-rwall.dev

$ dpkg-buildpackage -S -sa 

dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security

dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=2

dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security

dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2

dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-functions -Wl,-z,relro

dpkg-buildpackage: source package netkit-rwall

dpkg-buildpackage: source version 0.17-8ubuntu2

dpkg-buildpackage: source changed by Chris Good <chris.good@xxxxxxxxxxxxxx>

dpkg-source --before-build netkit-rwall.dev

fakeroot debian/rules clean

dh_testdir

dh_testroot

[ ! -f MCONFIG ] || /usr/bin/make distclean

dh_clean

find: `./trusty/root': Permission denied

find: `./trusty/home/cgood/.gnupg': Permission denied

find: `./trusty/home/cgood/.ssh': Permission denied

find: `./trusty/var/spool/cron/crontabs': Permission denied

find: `./trusty/var/spool/rsyslog': Permission denied

find: `./trusty/var/cache/ldconfig': Permission denied

rm: cannot remove `./trusty/etc/apt/trusted.gpg~': Permission denied

dh_clean: find .  \( \( -type f -a \

                        \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \

                                -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \

                                -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \

                                -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \

                                \) -exec rm -f {} \; \) -o \

                                \( -type d -a -name autom4te.cache -prune -exec rm -rf {} \; \) \) returned exit code 1

make: *** [clean] Error 2

dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

 

Should I have tried to install and build the source package in my chroot trusty environment?

(I'm working in precise).

 

I don't understand how the chroot is supposed to work.

I have seen https://wiki.ubuntu.com/DebootstrapChroot

 

Looking at http://packaging.ubuntu.com/html/chroots.html 

 

                10.1. Creating a Chroot:

                You can then work inside the chroot:

                $ sudo chroot trusty

 

After this, of course I am root, and the source package I had set up previously, doesn't exist in the chroot.

Should I hardlink the source directory structure into the chroot?

Should I be working as myself (user cgood) instead of root? If so, do I 'su - cgood' before starting?

Will the chroot still be in effect if I do?

 

Sorry for all these newbie questions.

 

Regards, 

Chris Good

 

> -----Original Message-----

> From: Jörg Frings-Fürst [mailto:ubuntu@xxxxxxxxxxxxxxxxxx]

> Sent: Friday, 18 April 2014 10:12 PM

> To: Chris Good

> Subject: Re: [Launchpad-users] FW: [PPA chris-good-rwall-ppa] netkit-

> rwall_0.17-8ubuntu2_amd64.changes rejected

> 

> Am Freitag, den 18.04.2014, 13:50 +0200 schrieb Jörg Frings-Fürst:

> > Hi Chris,

> >

> > Am Freitag, den 18.04.2014, 19:51 +1000 schrieb Chris Good:

> > > Hi Jorg,

> > >

> [...]

> 

> > do you build with

> > (see mail from Gianfranco)

> >

> > dpkg-buildpackage -S -sa

> >

> >

> > Or follow [1] for a clean buildsystem.

> >

> >

> > Jörg

> >

> 

> Hi

> sorry for the missing link:

> 

> [1]   <https://wiki.ubuntu.com/PbuilderHowto> https://wiki.ubuntu.com/PbuilderHowto

> 

> 

> Jörg

> 

> --

> pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E pgp

> Key: BE581B6E CAcert Key S/N: 0E:D4:5A

> 

> Jörg Frings-Fürst

> D-54526 Niederkail

> 

> Member of Ubuntu BugSquad

> 

> IRC: j_f-f@freenode

> 

> 

> 

> 

>

Attachment: smime.p7s
Description: S/MIME cryptographic signature