[Debian-med-packaging] Please upload gwyddion from SVN (was: Re: Processing of gwyddion_2.46-1_amd64.changes)

[Andreas Tille]

Hi Jan,

are you sure that SVN has a proper state of packaging?  I get:

$ pdebuild
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: Unmet build dependencies: libgtkglext1-dev libminizip-dev python-gtk2-dev libgtksourceview2.0-dev libgconf2-dev chrpath
W: Unmet build-dependency in source
dpkg-buildpackage: source package gwyddion
dpkg-buildpackage: source version 2.46-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Jan Beyer <jan at beathovn.de>
 dpkg-source -i.git -I.git --before-build gwyddion-2.46
dpkg-source: info: applying fix-manpage-section-for-debian.diff
dpkg-source: info: applying fix-rpath-issue.patch
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/fix-rpath-issue.patch/ --reject-file=- < gwyddion-2.46/debian/patches/fix-rpath-issue.patch gave error exit status 1
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?


Could you please check?

Thanks

      Andreas.


On Sat, Nov 05, 2016 at 09:58:21PM +0100, jan at beathovn.de wrote:
> Dear DDs in Debian Med,
> 
> could anybody please upload gwyddion 2.46-1 from Debian Med SVN?
> My GPG key expired recently and is still waiting to be renewed in the Debian
> keyring. Until then, I am not able to upload myself... Sorry for the
> inconvenience!
> 
> Thank you very much in advance!
> 
> Best regards,
> Jan
> 
> 
> Zitat von Joerg Jaspert <joerg at debian.org>:
> 
> >On 14481 March 1977, jan at beathovn.de wrote:
> >
> >>this (see below) is the third time in something like two weeks that I
> >>uploaded the new upstream release of gwyddion 2.46 (using dput ftp-eu)
> >>and as usual got the successfull-upload-confirmation mail. But up to
> >>now, I have neither received a REJECTED nor an ACCEPTED mail, which
> >>previously usually happened within a rather short timeframe.
> >>Accordingly, the new release did never show up in sid. Could you
> >>please help me out here and check, what might be wrong?
> >>I should mention, that the first upload (on Oct 17) happened, when my
> >>GPG key was expired. After noticing this, I extended the expiry date
> >>and submitted the key with the new expiry date to keyring.d.o. After
> >>waiting a few days, I re-uploaded, but still without ACCEPTance or
> >>REJECT. Might this be related somehow?
> >
> >And it will, again, not get accepted. Use a sponsor for now. Waiting a
> >few days does not help you, you have to wait until the keyring
> >maintainers actually incorporated your updated key into the keyring.
> >Which usually happens once a month.
> >
> >Check keyring.debian.org for how to find out when this happened. (hint:
> >rsync or git)
> >
> >--
> >bye, Joerg
> 
> 
> 
> 
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de