Trying to upgrade python-pysam for Debian
Hi, I tried to upgrade the Debian package of python-pysam to the latest upstream version but realised two major problems: 1. We would like to link against the Debian packaged copy of htslib but it seems the code copy inside python-pysam relies on symbols only available in version 0.0.1 while Debian currently has 0.2.0. This is discussed on our mailing list here[1]. 2. Even if I try to ignore the Debian packaged version and use the internal code copy the test suite fails as well since the file TestUtils-py seems to be missing: PYTHONPATH=/tmp/buildd/python-pysam-0.8.0/.pybuild/pythonX.Y_2.7/build python2.7 ./tabix_test.py Traceback (most recent call last): File ./pysam_test.py, line 15, in module from TestUtils import checkBinaryEqual ImportError: No module named TestUtils Any help to solve this issues would be appreciated. Kind regards and thanks for providing pysam as free software Andreas. [1] https://lists.debian.org/debian-med/2014/08/msg00091.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827065030.gc23...@an3as.eu
Re: packaging UCSC kent tools for debian-med
Hi Hiram, I hope you don't mind if I'm putting Debian Med list in the discussion which I would like you to do in pure technical discussion as well. On Wed, Aug 27, 2014 at 12:00:59AM -0700, Hiram Clawson wrote: Good Evening Andreas: I'm curious if there would be a way to fit this building procedure into the Debian-Med project: http://genome-source.cse.ucsc.edu/gitweb/?p=kent.git;a=blob;f=src/userApps/README Note steps 1, 2, 3 near the top of the README after the 'System Requirements' discussion. I fully realize this isn't they way packages are supposed to work, but at this time, this is the best we have. Simply from reading the README I can not see anything unusual. Step 1 (fetching the tarball) is totally normal workflow, step 2 is cd-ing to the unpackaged dir and call make is also pretty normal except that this make call is done by the debhelper tools. The only difference is step 3 where we do not move files to /usr/local but rather into /usr/bin inside the Debian package. Perhaps there could be a way to encapsulate these first three steps into some kind of building/packaging business that would satisfy the standard build and packaging procedures ? Yes, for sure. That's the day job of a Debian packager. Do you want to learn how to do this? If yes we could offer mentoring in the so called Mentoring of the Month[1] effort. While there is right now the September slot occupied I would try hard to help you as well since if we want to get these tools included (and I would really love to see this) we need to start right now. So are you able to invest some time slots into the packaging and want to work together with us please subscribe this mailing lists (links should be given on the Wiki page[1]) and ask for help here in case of trouble or if you need some kickstart help. Thanks for your interest in Debian Med Andreas. [1] https://wiki.debian.org/DebianMed/MoM -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827085235.gb25...@an3as.eu
Re: packaging UCSC kent tools for debian-med
Hi again, please see my additions inline! On Wed, Aug 27, 2014 at 10:52:35AM +0200, Andreas Tille wrote: Hi Hiram, I hope you don't mind if I'm putting Debian Med list in the discussion which I would like you to do in pure technical discussion as well. On Wed, Aug 27, 2014 at 12:00:59AM -0700, Hiram Clawson wrote: Good Evening Andreas: I'm curious if there would be a way to fit this building procedure into the Debian-Med project: http://genome-source.cse.ucsc.edu/gitweb/?p=kent.git;a=blob;f=src/userApps/README Note steps 1, 2, 3 near the top of the README after the 'System Requirements' discussion. I fully realize this isn't they way packages are supposed to work, but at this time, this is the best we have. Simply from reading the README I can not see anything unusual. Step 1 (fetching the tarball) is totally normal workflow, Some correction to what I said here: Please provide a *versioned* tarball! Every tarball should have a version to be able to detect updates. Moreover once I have checked the tarball I realised that the problematic license which was discussed previously[0] remains. So *if* this software should be distributed by Debian this needs to be fixed first. step 2 is cd-ing to the unpackaged dir and call make is also pretty normal except that this make call is done by the debhelper tools. The only difference is step 3 where we do not move files to /usr/local but rather into /usr/bin inside the Debian package. Perhaps there could be a way to encapsulate these first three steps into some kind of building/packaging business that would satisfy the standard build and packaging procedures ? Yes, for sure. That's the day job of a Debian packager. Do you want to learn how to do this? If yes we could offer mentoring in the so called Mentoring of the Month[1] effort. While there is right now the September slot occupied I would try hard to help you as well since if we want to get these tools included (and I would really love to see this) we need to start right now. So are you able to invest some time slots into the packaging and want to work together with us please subscribe this mailing lists (links should be given on the Wiki page[1]) and ask for help here in case of trouble or if you need some kickstart help. Thanks for your interest in Debian Med Andreas. [1] https://wiki.debian.org/DebianMed/MoM [0] http://lists.alioth.debian.org/pipermail/debian-med-packaging/2014-March/025520.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827090413.gc25...@an3as.eu
Re: r17823 - in trunk/packages/arb/trunk/debian: . conf patches source
Hi Elmar,
On Tue, Aug 26, 2014 at 07:37:38PM +0200, Elmar Pruesse wrote:
pdebuilder funktioniert bei mir nicht wirklich. Er meckert ueber
haufenweise dependencies die er aus mir nicht erfindlichen Gruenden
nicht installieren kann/will:
[short translation: pbuilder does not work for Elmar when he tries to
build arb]
Elmar, I admit I have never seen this. Could you perhaps try
apt-get source hello
cd hello-*
pdebuild
If this also does not work we have another problem to solve first.
Kind regards
Andreas.
dpkg-source: info: building arb using existing ./arb_6.0.2.orig.tar.gz
dpkg-source: info: building arb in arb_6.0.2-1.debian.tar.gz
dpkg-source: info: building arb in arb_6.0.2-1.dsc
dpkg-genchanges -S ../arb_6.0.2-1_source.changes
dpkg-genchanges: including full source code in upload
dpkg-source --after-build arb_6.0.2
dpkg-source: info: using options from arb_6.0.2/debian/source/options:
--extend-diff-ignore=PERL_SCRIPTS/test/test.stamp
dpkg-buildpackage: full upload (original source is included)
W: /home/epruesse/.pbuilderrc does not exist
I: using fakeroot in build.
I: Current time: Tue Aug 26 19:29:42 CEST 2014
I: pbuilder-time-stamp: 1409074182
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
- Attempting to satisfy build-dependencies
- Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team pbuilder-ma...@lists.alioth.debian.org
Description: Dummy package to satisfy dependencies with aptitude -
created by pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: chrpath, debhelper (= 9), freeglut3-dev | libglu-dev,
libbio-perl-perl, libglew-dev, libglib2.0-dev, libglw1-mesa-dev,
libglu1-mesa-dev, libmotif-dev, libpng-dev, libtiff-dev, libxaw7-dev,
libxml2-utils, libxpm-dev, lynx, time, perl-doc, xsltproc, xutils-dev
dpkg-deb: building package `pbuilder-satisfydepends-dummy' in
`/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11775 files and directories currently installed.)
Unpacking pbuilder-satisfydepends-dummy (from
.../pbuilder-satisfydepends-dummy.deb) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but
configuring anyway as you requested:
pbuilder-satisfydepends-dummy depends on chrpath; however:
Package chrpath is not installed.
pbuilder-satisfydepends-dummy depends on debhelper (= 9); however:
Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on freeglut3-dev | libglu-dev;
however:
Package freeglut3-dev is not installed.
Package libglu-dev is not installed.
pbuilder-satisfydepends-dummy depends on libbio-perl-perl; however:
Package libbio-perl-perl is not installed.
pbuilder-satisfydepends-dummy depends on libglew-dev; however:
Package libglew-dev is not installed.
pbuilder-satisfydepends-dummy depends on libglib2.0-dev; however:
Package libglib2.0-dev is not installed.
pbuilder-satisfydepends-dummy depends on libglw1-mesa-dev; however:
Package libglw1-mesa-dev is not installed.
pbuilder-satisfydepends-dummy depends on libglu1-mesa-dev; however:
Package libglu1-mesa-dev is not installed.
pbuilder-s
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
The following NEW packages will be installed:
apparmor-easyprof{a} bsdmainutils{a} chrpath{a} debhelper{a}
dh-apparmor{a} dh-python{a} file{a} freeglut3{a} freeglut3-dev{a}
gettext{a} gettext-base{a} groff-base{a} intltool-debian{a}
libasprintf-dev{a} libasprintf0c2{a} libcroco3{a} libdrm-dev{a}
libdrm-intel1{a} libdrm-nouveau2{a} libdrm-radeon1{a} libexpat1{a}
libffi6{a} libgettextpo-dev{a} libgettextpo0{a} libgl1-mesa-dev{a}
libgl1-mesa-glx{a} libglapi-mesa{a} libglib2.0-0{a} libglu1-mesa{a}
libglu1-mesa-dev{a} libice-dev{a} libice6{a} libkms1{a} libmagic1{a}
libpciaccess0{a} libpipeline1{a} libpthread-stubs0{a}
libpthread-stubs0-dev{a} libpython3-stdlib{a} libpython3.3-minimal{a}
libpython3.3-stdlib{a} libsm-dev{a} libsm6{a} libssl1.0.0{a}
libunistring0{a} libx11-6{a} libx11-data{a} libx11-dev{a}
libx11-xcb-dev{a} libx11-xcb1{a} libxau-dev{a} libxau6{a}
libxcb-dri2-0{a} libxcb-dri2-0-dev{a} libxcb-glx0{a} libxcb-glx0-dev{a}
libxcb1{a} libxcb1-dev{a} libxdamage-dev{a} libxdamage1{a}
[MoM] Packaging Camp for Debian
Hi Andreas ! I began to try to package Camp, and I've some questions : - I've compressed the sources of Camp in camp-0.7.1.tar.gz, and next I've copied it under the name of camp_0.7.1.orig.tar.gz. Then I've put the directory debian/* into camp-0.7.1 and run pdebuild. Is it the right process ? - The .deb file has been well created but, when I install it (with apt-get install camp), the size of the built library (libcamp.so) is small than the one built with the classic way (cmake - make) : 1800 Ko vs 356 Ko. Have you ever seen something like that ? - Then on the wiki page of MoM, there is a link to a git repository for my project, but I'm asking if I have a writing access on it ? And first, does this repository already exist ? Because I can't clone it for now, and I don't see it anywhere... - About debian/watch : The problem is there are some forks from it, and the more recent is one year old. Does one of forks could be used ? (Knowing that they look like that : https://github.com/tegesoft/camp). - The organization of the Git repository doesn't include the different version, like it by example : http://sourceforge.net/projects/vxl/files/vxl/ What do you think about it ? - I've opened a new thread on https://lists.debian.org/debian-devel/2014/08/msg00845.html . Does it seem all right for you ? - In this thread, as Upstream Author, I put the name of the last person I know who worked on Camp. Is it ok ? Thank you for your help! Corentin -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53fdd859.3000...@gmail.com
Re: [MoM] Packaging Camp for Debian
Hi Corentin, On Wed, Aug 27, 2014 at 03:08:41PM +0200, Corentin Desfarges wrote: I began to try to package Camp, and I've some questions : - I've compressed the sources of Camp in camp-0.7.1.tar.gz, Question: How did you obtained these sources before compressing them. and next I've copied it under the name of camp_0.7.1.orig.tar.gz. Then I've put the directory debian/* into camp-0.7.1 and run pdebuild. Is it the right process ? In principle yes (I need to know the answer to my get sources question above to be sure). - The .deb file has been well created but, when I install it (with apt-get install camp), the size of the built library (libcamp.so) is small than the one built with the classic way (cmake - make) : 1800 Ko vs 356 Ko. Have you ever seen something like that ? I'd call this normal since binaries are stripped (man dh_strip). - Then on the wiki page of MoM, there is a link to a git repository for my project, but I'm asking if I have a writing access on it ? You need to create an account on alioth.debian.org first and ask for becoming added to the Debian Med team. And first, does this repository already exist ? Because I can't clone it for now, and I don't see it anywhere... This repository does not yet exist ... I just invented this string for the moment. :-) - About debian/watch : The problem is there are some forks from it, and the more recent is one year old. Does one of forks could be used ? (Knowing that they look like that : https://github.com/tegesoft/camp). We are packaging the source which is mentioned in d/watch (this is connected to my get sources question). If *you* (as an educated person about the code) decide to package a fork for whatever reason this for should be fetched with d/watch and you should document the reasons for this in the file debian/README.source. - The organization of the Git repository doesn't include the different version, like it by example : http://sourceforge.net/projects/vxl/files/vxl/ What do you think about it ? I'm afraid I do not understand this question. (BTW, I just uploaded vxl to unstable.) - I've opened a new thread on https://lists.debian.org/debian-devel/2014/08/msg00845.html . Does it seem all right for you ? Yes, it is. (Just for the wording: I would have said here in this mail s/I've opened a new thread on/I filed an ITP bug/ ... and I would not refer to the thread on debian-devel but rather to #759244) - In this thread, as Upstream Author, I put the name of the last person I know who worked on Camp. Is it ok ? The ITP bug is not really relevant for this since once the package the bug is closed and forgotten. Please make sure you document things properly inside the package (README.source). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827144722.gi25...@an3as.eu
Re: r17823 - in trunk/packages/arb/trunk/debian: . conf patches source
Elmar, I admit I have never seen this. I needed to set COMPONENTS in ~/.pbuilderrc and run sudo pbuilder update --override-config. My assumption had been that pbuilder would create a sensible environment automagically, i.e. deducing from ARB being non-free that it'd need non-free packages. But I'm running Ubuntu and how would pbuilder know about universe... Elmar -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53fdffc5.2090...@pruesse.net
Re: r17823 - in trunk/packages/arb/trunk/debian: . conf patches source
Hi! The package now builds cleanly with pbuilder on my machine. Elmar -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53fe182c.7080...@pruesse.net
Re: r17823 - in trunk/packages/arb/trunk/debian: . conf patches source
Hi Elmar, On Wed, Aug 27, 2014 at 05:56:53PM +0200, Elmar Pruesse wrote: Elmar, I admit I have never seen this. I needed to set COMPONENTS in ~/.pbuilderrc and run sudo pbuilder update --override-config. My assumption had been that pbuilder would create a sensible environment automagically, i.e. deducing from ARB being non-free that it'd need non-free packages. But I'm running Ubuntu and how would pbuilder know about universe... Good to hear that you was able to solve your problem (as you said in your other mail). If you can provide a patch to our policy document in the line Hints for Ubuntu users to setup a working build environment this would possibly help other contributors who consider Ubuntu easier to use (which I personally start doubting when hearing more and more reports like this). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827183253.ga7...@an3as.eu
Re: Updating the fis-gtm package to V6.1-000
Hi Amul, On Wed, Aug 27, 2014 at 03:44:44PM -0400, Amul Shah wrote: Folks, I'm working towards updating the fis-gtm package. I have several TODOs for this: - Incorporate the updated sources - Refresh existing and apply new patches, quilt is just awesome - Update the virtual package fis-gtm depends to V6.1-000 - Use the ARCH settings (https://groups.google.com/d/msg/comp.lang.mumps/mH9mdI8ozQ0/n752Z_8jlJYJ) for 64bit (x86_64) and 32bit (i586) builds - Test - I had problems with this last time and may need help Sounds like a sensible plan. The first question I have is what repository should I work from? For now, I cloned https://alioth.debian.org/anonscm/git/debian-med/fis-gtm.git That's annonymous. You should rather clone (or set remote origin to): ssh://git.debian.org/git/debian-med/fis-gtm.git Please use git import-orig --pristine-tar new_upstream_tarball (and nothing else) to do your first step (Incorporate the updated sources). If you then try `git push` you will see whether you have commit permissions. I have keys established on alioth which I used to access the SVN repositories. So you can ssh git.debian.org ? I started reading the Debian New Maintainers' Guide because I can't remember a single thing about this process other than git-buildpackage. You need to tweak the debian/ dir between git import-orig --pristine-tar and git-buildpackage The bare minimum is to dch -i to create a new changelog entry. Feel free to come up on this list with any question you might have. Kind regards and thanks for caring for fis-gtm Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140827204646.gc7...@an3as.eu
Re: Updating the fis-gtm package to V6.1-000
On 08/27/14 16:46, Andreas Tille wrote: Hi Amul, On Wed, Aug 27, 2014 at 03:44:44PM -0400, Amul Shah wrote: Folks, I'm working towards updating the fis-gtm package. I have several TODOs for this: - Incorporate the updated sources - Refresh existing and apply new patches, quilt is just awesome - Update the virtual package fis-gtm depends to V6.1-000 - Use the ARCH settings (https://urldefense.proofpoint.com/v1/url?u=https://groups.google.com/d/msg/comp.lang.mumps/mH9mdI8ozQ0/n752Z_8jlJYJk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=KgGzFmrpr0CH7A8VRCDGC05IrYOn9XWlNRvgNmiK%2BUg%3D%0Am=Gpqdn7yjtAWoCxI2Z%2FSz4JqQ68DJDvIxSgdNyq3HwK4%3D%0As=87c8999074bc2609dd6690067639fd59a3d105aa594d4222ffb18118a642bf83) for 64bit (x86_64) and 32bit (i586) builds - Test - I had problems with this last time and may need help Sounds like a sensible plan. The first question I have is what repository should I work from? For now, I cloned https://urldefense.proofpoint.com/v1/url?u=https://alioth.debian.org/anonscm/git/debian-med/fis-gtm.gitk=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0Ar=KgGzFmrpr0CH7A8VRCDGC05IrYOn9XWlNRvgNmiK%2BUg%3D%0Am=Gpqdn7yjtAWoCxI2Z%2FSz4JqQ68DJDvIxSgdNyq3HwK4%3D%0As=648d8cfbb56d7fbb08e87c29139afbec8be4c4de76c0f7440d7a9f55d9778557 That's annonymous. You should rather clone (or set remote origin to): ssh://git.debian.org/git/debian-med/fis-gtm.git Please use git import-orig --pristine-tar new_upstream_tarball (and nothing else) to do your first step (Incorporate the updated sources). If you then try `git push` you will see whether you have commit permissions. I have keys established on alioth which I used to access the SVN repositories. So you can ssh git.debian.org ? [amul:2] Looks like I can't from work. Doing it from home will be easier. I started reading the Debian New Maintainers' Guide because I can't remember a single thing about this process other than git-buildpackage. You need to tweak the debian/ dir between git import-orig --pristine-tar and git-buildpackage The bare minimum is to dch -i to create a new changelog entry. Feel free to come up on this list with any question you might have. Kind regards and thanks for caring for fis-gtm Andreas. [amul:2] Thanks for the pointers Andreas. I'm still working with the anon sources. I'll fix that later tonight. [amul:2] I read the mail about freeze dates (https://lists.debian.org/debian-devel-announce/2014/07/msg2.html), but didn't quite understand some terms. What is the drop dead date to get fis-gtm up to date? Best regards, Amul _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53fe5925.5040...@fisglobal.com
Re: Updating the fis-gtm package to V6.1-000
Hi Andreas, On Wed, Aug 27, 2014, at 04:46 PM, Andreas Tille wrote: On Wed, Aug 27, 2014 at 03:44:44PM -0400, Amul Shah wrote: Folks, I'm working towards updating the fis-gtm package. I have several TODOs for this: - Incorporate the updated sources - Refresh existing and apply new patches, quilt is just awesome - Update the virtual package fis-gtm depends to V6.1-000 - Use the ARCH settings (https://groups.google.com/d/msg/comp.lang.mumps/mH9mdI8ozQ0/n752Z_8jlJYJ) for 64bit (x86_64) and 32bit (i586) builds - Test - I had problems with this last time and may need help Sounds like a sensible plan. The first question I have is what repository should I work from? For now, I cloned https://alioth.debian.org/anonscm/git/debian-med/fis-gtm.git That's annonymous. You should rather clone (or set remote origin to): ssh://git.debian.org/git/debian-med/fis-gtm.git Please use git import-orig --pristine-tar new_upstream_tarball [amul:3] This step took a bit of trial and error until I got it to work. I'm going to step through the errors so I have a record of it and if I'm doing something incorrectly, it can be corrected. Here's the error that I started out with. instance1:~/fis-gtm-debmed.git git-import-orig --pristine-tar ~/Downloads/fis-gtm-V6.1-000.tar.gz -u 6.1-000 gbp:error: Repository does not have branch 'upstream' for upstream sources. If there is none see file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT on howto create it otherwise use --upstream-branch to specify it. [amul:3] The HTML doc link above indicated going to the initial source import. I tried that (see the bit about COMMIT_ID), but the merge resulted in numerous conflicts. I fired up gitk and saw prior upstream commits had already chained off the initial source import until the upstream/6.0-003. I used the commit ID of the upstream/6.0-003 below. git clone ssh://git.debian.org/git/debian-med/fis-gtm.git fis-gtm-debmed.git cd fis-gtm-debmed.git git branch upstream d883233f4018839ce9f3da6faa57a5de8e2de98f git-import-orig --pristine-tar ~/Downloads/fis-gtm-V6.1-000.tar.gz -u 6.1-000 commit dch -v 6.1-000 commit rm -rf .pc mv ~/Downloads/fis-gtm-V6.1-000.tar.gz ../fis-gtm_6.1.orig.tar.gz git-buildpackage [amul:3] I ended up hitting the same error that stopped me in my tracks last time. Here's the error. I'll try to correct it tomorrow. Finished running lintian. Now signing changes and any dsc files... signfile fis-gtm_6.1-000.dsc Amul Shah amul.s...@fisglobal.com gpg: directory `/home/shaha/.gnupg' created gpg: new configuration file `/home/shaha/.gnupg/gpg.conf' created gpg: WARNING: options in `/home/shaha/.gnupg/gpg.conf' are not yet active during this run gpg: keyring `/home/shaha/.gnupg/secring.gpg' created gpg: keyring `/home/shaha/.gnupg/pubring.gpg' created gpg: skipped Amul Shah amul.s...@fisglobal.com: secret key not available gpg: /tmp/debsign.BbZPAaF6/fis-gtm_6.1-000.dsc: clearsign failed: secret key not available debsign: gpg error occurred! Aborting debuild: fatal error at line 1271: running debsign failed gbp:error: debuild -i -I returned 29 gbp:error: Couldn't run 'debuild -i -I' [amul:3] When I tried to push I hit yet another problem. instance1:~/fis-gtm-debmed.git git push Counting objects: 1229, done. Delta compression using up to 2 threads. Compressing objects: 100% (652/652), done. Writing objects: 100% (653/653), 786.83 KiB, done. Total 653 (delta 577), reused 0 (delta 0) remote: Sending notification emails to: debian-med-com...@lists.alioth.debian.org To ssh://git.debian.org/git/debian-med/fis-gtm.git 3a6c8c0..c8316bd master - master ! [rejected]pristine-tar - pristine-tar (non-fast-forward) ! [rejected]upstream - upstream (non-fast-forward) error: failed to push some refs to 'ssh://git.debian.org/git/debian-med/fis-gtm.git' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes (e.g. 'git pull') before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details. instance1:~/fis-gtm-debmed.git git pull Already up-to-date. [amul:3] Searches revealed some quick answers (below), but those didn't resolve the reject messages. I cloned into another directory and saw that my changes made it to the master branch. What am I doing wrong, and do I need to correct this? git pull origin upstream git pull origin pristine-tar [amul:3] Where I am right now: I committed my changes, but could not test them. If someone else could give it a try that would be a great help. I also have a git push error that I don't understand. I try doing some more searches tomorrow. Thanks for the help, Amul -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
