Re: Is there a way to preserve pbuilder chroot environment?
Can you elaborate a bit on what you mean by having to build a package multiple times before it builds successfully? With pbuilder, your package should be able to be built with a single invocation of pbuilder (given a .dsc) or pdebuild (when unpacked). Anything more than that and the ftpmasters will probably consider your package to FTBFSIASW (fail to build from source in a sane way). I mean that I'm new to it, and I'm making lots of mistakes, and rebuilding the chroot environment each time doesn't help much. I'll check the cowbuilder tool and maybe it will prove to be useful. signature.asc Description: PGP signature
Re: Is there a way to preserve pbuilder chroot environment?
Pbuilder also supports that using hooks, e.g.: # ln -s /usr/share/doc/pbuilder/examples/C10shell /var/cache/pbuilder/hooks/C10shell ...and the next time your build fails, pbuilder will dump you in the chroot with a shell. I checked this solution, but I'm wondering how to resume pbuilder after it dumps me in the chroot? Let's say I fixed everything that should be fixed, and what next? signature.asc Description: PGP signature
Re: Is there a way to preserve pbuilder chroot environment?
sbuild also has lots of nifty extra features. One I use a lot is the ability to locally build a stack of related packages against each other[1]. You can do that in pbuilder (https://wiki.debian.org/PbuilderTricks ; also allows testing locally-built packages in a pbuilder --login session), but be aware that this method leaves the locally-built packages available until explicitly removed, so if you decide not to upload the new version of the library, don't forget to remove it before building anything that uses it. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53119ef7.4010...@bham.ac.uk
Re: Is there a way to preserve pbuilder chroot environment?
+++ Barry Warsaw [2014-02-28 16:42 -0500]: On Feb 28, 2014, at 10:52 AM, Mikhail Morfikov wrote: I'm new to building packages by using pbuilder tool, and I have to build a package multiple times before it builds successfully, or in the way I prefer. This is one of the reasons why I prefer to use sbuild for most of my local builds. I swapped from pbuilder to sbuild some years ago. sbuild integrates with schroot in a really nice way. You can schroot in to the same chroots that sbuild will use and stay in for multiple builds. I use tarball chroots for clean builds which always revert to the initial state and plain chroots for other general testing. This is how I normally deal with mikhail's issue - develop in a plain chroot until I think things are working then test with clean builds in a tarball or lvm chroot. sbuild supports cross-building too which I find handy. I must admit I'm surprised so many people still use pbuilder, although I do agree that the syntax is a bit simpler for a 'standard upload' build. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301092020.gv18...@stoneboat.aleph1.co.uk
Re: Is there a way to preserve pbuilder chroot environment?
On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote: I must admit I'm surprised so many people still use pbuilder, although I do agree that the syntax is a bit simpler for a 'standard upload' build. I still use cowbuilder because schroot doesn't support cowdancer for copy-on-write chroots and I found tarball mode in pbuilder to be way too slow. The one time I used sbuild, interrupting the build gave me a completely broken chroot that I had to reinstall. I don't think that failure mode should be the default, hope it isn't any more. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6EyJ6J4fTtDqo-oNBHF-WFTK0zm1KC7=r0q0usn+yl...@mail.gmail.com
Re: RFS: cl-launch (updated package)
Hi! Faré fah...@gmail.com writes: you did well to procrastinate on my cl-launch 4.0.0-1, for after a round of bug fixes, here is 4.0.1-1. Thus, I am looking for a sponsor for the new version 4.0.1-1 of my package cl-launch. It builds these binary packages: cl-launch - uniform frontend to running Common Lisp code from the shell The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/cl-launch - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/cl-launch/cl-launch_4.0.1-1.dsc 4.0.1.1-3 should be on the way in a few minutes Christoph -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8761ny2l84@mitoraj.siccegge.de
Bug#740422: RFS: osgearth/2.5.0+dfsg-1~exp1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package osgearth Package name: osgearth Version : 2.5.0+dfsg-1~exp1 Upstream Author : Glenn Waldron URL : http://osgearth.org/ License : LGPL-3 Section : devel It builds those binary packages: libosgearth-dev- osgEarth development files libosgearth3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (shared library) libosgearthannotation3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthAnnotation) libosgearthfeatures3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthFeatures) libosgearthqt3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthQts) libosgearthsymbology3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthSymbology) libosgearthutil3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthUtil) osgearth - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (binaries) osgearth-data - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (data) openscenegraph-plugin-osgearth - OpenSceneGraph plugins for osgEarth To access further information about this package, please visit the following URL: http://mentors.debian.net/package/osgearth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/osgearth/osgearth_2.5.0+dfsg-1~exp1.dsc More information about osgEarth can be obtained from http://osgearth.org/. Changes since the last upload: * Don't use -0 revision, shlibs depends use upstream version only. * Don't use git-pbuilder by default in gpb.conf. * Update symbols for armel, armhf, kfreebsd-amd64, kfreebsd-i386 mipsel. Regards, Sebastiaan Couwenberg -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301125140.11553.74907.report...@osiris.linuxminded.xs4all.nl
Re: Is there a way to preserve pbuilder chroot environment?
On Sat, Mar 1, 2014 at 4:17 AM, Paul Wise p...@debian.org wrote: If you can convince the pbuilder and sbuild maintainers to work together to merge all the missing parts of pbuilder/cowbuilder/qemubuilder into sbuild, That would be a great adventure! -- regards, Mattia Rizzolo GPG Key: 4096R/B9444540 http://goo.gl/I8TMB more about me: http://mapreri.org Launchpad User: https://launchpad.net/~mapreri Ubuntu Wiki page: https://wiki.ubuntu.com/MattiaRizzolo -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cahkymevzugact_9yfc_pcu687-36zv43ruwejy0mmjszmee...@mail.gmail.com
Bug#740390: marked as done (RFS: tinyows/1.1.0-4 [ITP])
Your message dated Sat, 01 Mar 2014 13:42:28 +0100 with message-id 5311d5b4.4070...@xs4all.nl and subject line RFS: tinyows/1.1.0-4 [ITP] [uploaded] has caused the Debian Bug report #740390, regarding RFS: tinyows/1.1.0-4 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package tinyows Package name: tinyows Version : 1.1.0-4 Upstream Author : Barbara Philippot, Olivier Courtin and the MapServer team. URL : http://www.mapserver.org/tinyows/ License : MIT/X11 Section : web It builds those binary packages: tinyows- lightweight and fast WFS-T server To access further information about this package, please visit the following URL: http://mentors.debian.net/package/tinyows Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/t/tinyows/tinyows_1.1.0-4.dsc More information about TinyOWS can be obtained from http://www.mapserver.org/tinyows/. Changes since the last upload: * Upload for Debian closes: #723700. * Include OGC Software Notice in copyright, used for OGC schemas. * Move to non-free due to inclusion of OGC works (schemas and CITE tests). * Add gpb.conf to use pristine-tar by default. * Enable parallel builds. * Drop lintian override for debian-watch-may-check-gpg-signature, shouldn't override pedantic tags. * Add patch to remove config.log from the source tree before building. Regards, Sebastiaan Couwenberg ---End Message--- ---BeginMessage--- Thanks to Andreas Tille for sponsoring the upload. The package is currently in NEW waiting for FTP master review. Kind Regards, Bas---End Message---
Re: Is there a way to preserve pbuilder chroot environment?
Paul Wise p...@debian.org writes: On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote: I must admit I'm surprised so many people still use pbuilder, although I do agree that the syntax is a bit simpler for a 'standard upload' build. I still use cowbuilder because schroot doesn't support cowdancer for copy-on-write chroots and I found tarball mode in pbuilder to be way too slow. I use sbuild (actually, schroot under the hood) with btrfs-snapshot chroots. Creating a new build environment really is a snap. The one time I used sbuild, interrupting the build gave me a completely broken chroot that I had to reinstall. By default, the snapshot is destroyed when sbuild finishes in any way. No chance to damage the origin chroot this way. -- Regards, Feri. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvn2100w@lant.ki.iif.hu
RE: Is there a way to preserve pbuilder chroot environment?
I use a hook withs give me root access to build env when a build is failed Added this line to .pbuilderrc HOOKDIR=/var/cache/pbuilder/hook.d And placed the file C10shell in there with this content: #!/bin/sh # invoke shell if build fails. apt-get install -y --force-yes vim less bash nano cd /tmp/buildd/*/debian/.. /bin/bash /dev/tty /dev/tty 2 /dev/tty With this give you access to build enverement If you want to copy stuff out of the env you can the do by accessing your build directory and copy the stuff y -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/8c48efc8d3fd4db3b7f14d1cfb895441@srv04.dikkenberg.local
Re: Is there a way to preserve pbuilder chroot environment?
On Sat, Mar 1, 2014 at 10:11 PM, Ferenc Wagner wrote: I use sbuild (actually, schroot under the hood) with btrfs-snapshot chroots. Creating a new build environment really is a snap. Personally I wouldn't feel comfortable using btrfs on my main system yet and I don't have a separate system just for builds. By default, the snapshot is destroyed when sbuild finishes in any way. No chance to damage the origin chroot this way. If you aren't using any of the snapshot-capable mechanisms it will. For many people none are suitable so that could be common. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6fseiqm+admufjvvzycxj7wtpsmybyytkeuo-u1ib6...@mail.gmail.com
Bug#740442: RFS: par2cmdline/0.6.5-1 [ITA] -- PAR 2.0 compatible file verification and repair tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for par2cmdline: Package name: par2cmdline Version : 0.6.5-1 Upstream Author : Ike Devolder et al. URL : https://github.com/BlackIkeEagle/par2cmdline License : GPL-2+ Section : utils It builds a single binary package: par2 - PAR 2.0 compatible file verification and repair tool Mentors URL: http://mentors.debian.net/package/par2cmdline Download with dget: dget -x http://mentors.debian.net/debian/pool/main/p/par2cmdline/par2cmdline_0.6.5-1.dsc Changes since last upload: * New upstream release: (Closes: #655334) + Switch sources to Github-based fork; the original project (on Sourceforge) has been inactive for almost a decade. + Remove all patches: included upstream. * New maintainer (Closes: #673225). * Switch to 3.0 (quilt) source format. * Set priority to optional. * Bump standards-version to 3.9.5 (from 3.8.3). * Switch debian/rules to dh sequencer with autoreconf. * Update build-deps: + Add dh-autoreconf, automake1.11. + Remove cdbs, autotools-dev, automake1.9 (Closes: #724427). + Set debhelper version and compat level to 9. * Docs: + Replace PORTING and ROADMAP files with README. + Install upstream changelog. * Man page: + Fix numerous instances of hyphens used as minus signs. + Install links to a single manpage instead of keeping around multiple copies in the packaging. * Refresh copyright: + List new upstream developers. + Add myself as a copyright holder for the packaging. + Switch to machine-readable format. * Add Vcs-* fields. Regards. signature.asc Description: PGP signature
Re: Is there a way to preserve pbuilder chroot environment?
+++ Ferenc Wagner [2014-03-01 15:11 +0100]: Paul Wise p...@debian.org writes: On Sat, Mar 1, 2014 at 5:20 PM, Wookey wrote: I must admit I'm surprised so many people still use pbuilder, although I do agree that the syntax is a bit simpler for a 'standard upload' build. I still use cowbuilder because schroot doesn't support cowdancer for copy-on-write chroots and I found tarball mode in pbuilder to be way too slow. I use sbuild (actually, schroot under the hood) with btrfs-snapshot chroots. Creating a new build environment really is a snap. btrfs (and LVM) snapshots are great, but they only help if you have a btrfs or LVM volume to hand to work on. cowbuilder has the significant advantage that it works on any filesystem. In my experience the sbuild maintainer is very open to improvements and is happy for people to integrate new features on git branches then ask for a merge. (I had to learn git to do this for the cross-support - it was painful!) I would also make the comment that sbuild is very well written and designed. So fixes usually only have to be done in one place. It's nice to work with. I have no idea how easy general cow support would be to add to sbuild/schroot. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301152819.ga18...@stoneboat.aleph1.co.uk
Re: Is there a way to preserve pbuilder chroot environment?
+++ Paul Wise [2014-03-01 23:17 +0800]: On Sat, Mar 1, 2014 at 10:11 PM, Ferenc Wagner wrote: By default, the snapshot is destroyed when sbuild finishes in any way. No chance to damage the origin chroot this way. If you aren't using any of the snapshot-capable mechanisms it will. For many people none are suitable so that could be common. I have done an astonishing number of builds (and crossbuilds) in sbuild. I have killed many of them in mid-build for many reasons. It has a nice cleanup-mechanism which spots such interruptions and tidies up. I have never managed to currupt my chroot doing this, so I think you were very unlucky. It _is_ quite easy to get a lot of schroot mounts left lying about if you often kill terms or screen/tmux sessions or X sessions or machines running them. A nice feature of schroot is that you can resume such chroots and carry on from whatever state it was in (at the filesystem level). Again, I've never seen corruption doing this. You can also run commands on multiple chroots in parallel (whcih is a bit scary, but it works :-). Handy for doing builds for several suites at once. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301153354.gb18...@stoneboat.aleph1.co.uk
Re: Is there a way to preserve pbuilder chroot environment?
* Wookey woo...@wookware.org, 2014-03-01, 15:28: I still use cowbuilder because schroot doesn't support cowdancer for copy-on-write chroots and I found tarball mode in pbuilder to be way too slow. I use sbuild (actually, schroot under the hood) with btrfs-snapshot chroots. Creating a new build environment really is a snap. btrfs (and LVM) snapshots are great, but they only help if you have a btrfs or LVM volume to hand to work on. sbuild supports also aufs chroots, which don't require any specific underlying fs, and are reasonably fast. The only problem is that aufs is semi-unsupported in Debian. But I still trust it more than cowdancer… -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301162734.ga5...@jwilk.net
Bug#740452: RFS: qgis/2.2.0-1~exp1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package qgis Package name: qgis Version : 2.2.0-1~exp1 Upstream Author : qgis-develo...@lists.osgeo.org URL : http://qgis.org/ License : GPL-2+ Section : science It builds those binary packages: libqgis-analysis2.2.0- QGIS - shared libraries (libqgis-analysis) libqgis-core2.2.0- QGIS - shared libraries (libqgis-core) libqgis-gui2.2.0 - QGIS - shared libraries (libqgis-gui) libqgis-networkanalysis2.2.0 - QGIS - shared libraries (libqgis-networkanalysis) libqgisgrass2.2.0- QGIS - shared libraries (libqgisgrass) libqgispython2.2.0 - QGIS - shared libraries (libqgispython) libqgissqlanyconnection2.2.0 - QGIS - shared libraries (libqgissqlanyconnection) libqgis-dev - QGIS - development files python-qgis - Python bindings to QGIS python-qgis-common - Python bindings to QGIS - architecture-independent files qgis - Geographic Information System (GIS) qgis-api-doc - QGIS API documentation qgis-common - QGIS - architecture-independent data qgis-mapserver - QGIS mapserver qgis-plugin-globe- OSG globe plugin for QGIS qgis-plugin-globe-common - OSG globe plugin for QGIS - architecture-independent data qgis-plugin-grass- GRASS plugin for QGIS qgis-plugin-grass-common - GRASS plugin for QGIS - architecture-independent data qgis-providers - collection of data providers to QGIS qgis-providers-common- collection of data providers to QGIS - architecture-independent files qgis-sqlanywhere - QGIS sql anywhere plugin and provider To access further information about this package, please visit the following URL: http://mentors.debian.net/package/qgis Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/q/qgis/qgis_2.2.0-1~exp1.dsc More information about QGIS can be obtained from http://qgis.org/. Changes since the last upload: * Require at least osgEarth version 2.5.0. * Don't use -0 revision, shlibs depends use upstream version only. * Update symbols for armel, kfreebsd-amd64, kfreebsd-i386 mipsel. * Add patches for changes from upstream release_2.2 branch. * Add path to limit the dot graph for the QGIS API documentation. Regards, Sebastiaan Couwenberg -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140301185722.437.95107.report...@osiris.linuxminded.xs4all.nl
Re: Is there a way to preserve pbuilder chroot environment?
On Sat, Mar 1, 2014 at 12:18 AM, Mikhail Morfikov mmorfi...@gmail.com wrote: Pbuilder also supports that using hooks, e.g.: # ln -s /usr/share/doc/pbuilder/examples/C10shell /var/cache/pbuilder/hooks/C10shell ...and the next time your build fails, pbuilder will dump you in the chroot with a shell. I checked this solution, but I'm wondering how to resume pbuilder after it dumps me in the chroot? Let's say I fixed everything that should be fixed, and what next? If you want to continue fixing issues as you go along, just keep spamming 'fakeroot debian/rules binary' in your shell (assuming your end goal is to produce binary .deb packages). You can of course try running other targets in d/rules to narrow down and solve specific issues that you want to fix. Regards, Vincent -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caczd_td2ycxtqlxgduph12txhmu3qetct2pzj6gpvao67on...@mail.gmail.com
Re: Maintainer scripts: execute command as another user: use sudo or su?
On 02/27/2014 03:37 PM, David Kalnischkies wrote: On Wed, Feb 26, 2014 at 04:07:35PM +0100, Emilien Klein wrote: In the pre- and postinst scripts, a command has to be performed as that user (e.g. make a backup of the database). […] I am wondering what the best way is to fix this. I see 2 solutions: 1. Depend on sudo 2. Use su --command instead Beside what others already said: As you said it is run in preinst scripts you would need to pre-depend on sudo – and you would need to discuss this first on debian-devel@ as strongly recommend by debian-policy (§3.5 and §7.2). The outcome of this discussion would probably be that you should use su… su on the other hand is 'free' to use as it is provided by the essential login package, so no dependency is needed at all. I have made the switch to su instead of sudo. One minor challenge that I faced is that I couldn't get the commands to run using su. With the help of Karsten Hilbert I understood that the issue was that the user being a system user, she didn't have a shell (default shell for new system users is /bin/false). Running the commands as su --shell /bin/sh -c COMMAND USERNAME works as expected. Thanks Andreas, Karsten, David and Thibaut for your input. +Emilien signature.asc Description: OpenPGP digital signature
Test builds in gbp patch-queue branch [was: Re: Is there a way to preserve pbuilder chroot environment?]
On 03/01/2014 10:46 PM, Vincent Cheng wrote: On Sat, Mar 1, 2014 at 12:18 AM, Mikhail Morfikov mmorfi...@gmail.com wrote: Pbuilder also supports that using hooks, e.g.: # ln -s /usr/share/doc/pbuilder/examples/C10shell /var/cache/pbuilder/hooks/C10shell ...and the next time your build fails, pbuilder will dump you in the chroot with a shell. I checked this solution, but I'm wondering how to resume pbuilder after it dumps me in the chroot? Let's say I fixed everything that should be fixed, and what next? If you want to continue fixing issues as you go along, just keep spamming 'fakeroot debian/rules binary' in your shell (assuming your end goal is to produce binary .deb packages). You can of course try running other targets in d/rules to narrow down and solve specific issues that you want to fix. Regards, Vincent Thank you all, this has been a useful thread for me. But it hasn't yet given me the exact answer I needed (but some clues!). And maybe my question will also be useful to others. Many times I have used 'gbp pq import' to create a patch queue and try out some crazy patches to the source code there. I have used the options to tell gbp where the debian upstream branches are, but 'gbp buildpackage' fails because it detects altered files in the source code. I have tried several times to find solution in the man pages for gbp, pbuilder and dpkg-buildpackage etc. Now you have all helped me to realise that I can spam with 'debian/rules build' to test if it fixes a FTBFS, or 'fakeroot debian/rules binary' to go all the way to a 'deb' which I can try installing. But if I don't want to install all the build dependencies on the machine I am using, how can I pass these commands to pbuilder? Or can I override gbp buildpackage (with pbuilder as an option) in some way so that it ignores the fact that there are altered files? Hoping someone can solve a regular frustration of mine. Regards, Ross -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53126122.1060...@the-gammons.net
Re: Test builds in gbp patch-queue branch [was: Re: Is there a way to preserve pbuilder chroot environment?]
On Sat, 01 Mar 2014 23:37:22 +0100, Ross Gammon wrote: 'gbp buildpackage' fails because it detects altered files in the source code. Or can I override gbp buildpackage (with pbuilder as an option) in some way so that it ignores the fact that there are altered files? Yes, you can: == excerpt from ~/.gbp.conf == [buildpackage] ... export = WC Ah, here it is in the manpage: --git-export=treeish Instead of exporting the current branch head, export the treeish object treeish. The special name INDEX exports the current index whereas the special name WC exports the current working copy as is. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Don McLean: The Carnival Is Ended signature.asc Description: Digital signature
Re: Maintainer scripts: execute command as another user: use sudo or su?
On Sat, 01 Mar 2014 22:55:20 +0100, Emilien Klein wrote: One minor challenge that I faced is that I couldn't get the commands to run using su. With the help of Karsten Hilbert I understood that the issue was that the user being a system user, she didn't have a shell (default shell for new system users is /bin/false). That's what Russ already mentioned in https://lists.debian.org/debian-mentors/2014/02/msg00499.html :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Beatles signature.asc Description: Digital signature
Bug#734522: marked as done (RFS: optparse-js/1.0.5-1 [ITP: #733763])
Your message dated Sun, 02 Mar 2014 04:26:30 + with message-id e1wjxyw-cs...@quantz.debian.org and subject line closing RFS: optparse-js/1.0.5-1 [ITP: #733763] has caused the Debian Bug report #734522, regarding RFS: optparse-js/1.0.5-1 [ITP: #733763] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 734522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package optparse-js * Package name: optparse-js Version : 1.0.5-1 Upstream Author : Johan Dahlberg * URL : https://github.com/jfd/optparse-js * License : Expat Section : web It builds those binary packages: libjs-optparse - Command-line option parser for JavaScript applications To access further information about this package, please visit the following URL: http://mentors.debian.net/package/optparse-js Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/optparse-js/optparse-js_1.0.5-1.dsc More information about optparse-js can be obtained from http://github.com/jfd/optparse-js Changes since the last upload: * Initial release. (Closes: #733763) Regards, Tonnerre Lombard ---End Message--- ---BeginMessage--- Package optparse-js has been removed from mentors.---End Message---
Bug#740422: marked as done (RFS: osgearth/2.5.0+dfsg-1~exp1)
Your message dated Sun, 02 Mar 2014 04:26:30 + with message-id e1wjxyw-cy...@quantz.debian.org and subject line closing RFS: osgearth/2.5.0+dfsg-1~exp1 has caused the Debian Bug report #740422, regarding RFS: osgearth/2.5.0+dfsg-1~exp1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package osgearth Package name: osgearth Version : 2.5.0+dfsg-1~exp1 Upstream Author : Glenn Waldron URL : http://osgearth.org/ License : LGPL-3 Section : devel It builds those binary packages: libosgearth-dev- osgEarth development files libosgearth3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (shared library) libosgearthannotation3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthAnnotation) libosgearthfeatures3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthFeatures) libosgearthqt3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthQts) libosgearthsymbology3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthSymbology) libosgearthutil3 - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (osgEarthUtil) osgearth - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (binaries) osgearth-data - Dynamic 3D terrain rendering toolkit for OpenSceneGraph (data) openscenegraph-plugin-osgearth - OpenSceneGraph plugins for osgEarth To access further information about this package, please visit the following URL: http://mentors.debian.net/package/osgearth Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/o/osgearth/osgearth_2.5.0+dfsg-1~exp1.dsc More information about osgEarth can be obtained from http://osgearth.org/. Changes since the last upload: * Don't use -0 revision, shlibs depends use upstream version only. * Don't use git-pbuilder by default in gpb.conf. * Update symbols for armel, armhf, kfreebsd-amd64, kfreebsd-i386 mipsel. Regards, Sebastiaan Couwenberg ---End Message--- ---BeginMessage--- Package osgearth version 2.5.0+dfsg-1~exp1 is in experimental now. http://packages.qa.debian.org/osgearth---End Message---
Re: Test builds in gbp patch-queue branch [was: Re: Is there a way to preserve pbuilder chroot environment?]
On 03/02/2014 12:38 AM, gregor herrmann wrote: On Sat, 01 Mar 2014 23:37:22 +0100, Ross Gammon wrote: 'gbp buildpackage' fails because it detects altered files in the source code. Or can I override gbp buildpackage (with pbuilder as an option) in some way so that it ignores the fact that there are altered files? Yes, you can: == excerpt from ~/.gbp.conf == [buildpackage] ... export = WC Ah, here it is in the manpage: --git-export=treeish Instead of exporting the current branch head, export the treeish object treeish. The special name INDEX exports the current index whereas the special name WC exports the current working copy as is. Cheers, gregor Thanks Gregor, but I was already aware of --git-export=WC --git-ignore-new. I have used this when I wanted to test changes to e.g. d/rules before committing the fix. What I was probably not clear about, was that I meant changes made outside the debian directory. For example, make a simple change to a working package by adding #Ross is a berk to setup.py. gbp buildpackage with the pbuilder option and --git-export --git-ignore-new still fails: dpkg-source: info: building gramps using existing ./gramps_4.0.3+dfsg.orig.tar.gz dpkg-source: info: local changes detected, the modified files are: gramps-4.0.3+dfsg/setup.py dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gramps_4.0.3+dfsg-3.diff.8Ha2F5 dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-buildpackage: error: dpkg-source -b gramps-4.0.3+dfsg gave error exit status 2 gbp:error: Couldn't run 'git-pbuilder': git-pbuilder returned 2 But anyway, studying this error a bit harder with a clear head in the morning, and then studying the man page for dpkg-source, I solved it. Adding the option -i.* to gbp successfully got passed to dpkg-source, and it built. Cheers, Ross PS: now I had better remove that change before I forget ;-) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5312dfde.3060...@the-gammons.net
