Re: git-dpm: ERROR: 'upstream' does not contain previously recorded revision
2015-10-24 1:02 GMT+02:00 Brian May <b...@debian.org>: > Ludovic Rousseau <ludovic.rouss...@gmail.com> writes: > > > I tried to update my package pykcs11 since the repository moved from SVN > to > > git. > > http://anonscm.debian.org/cgit/python-modules/packages/pykcs11.git/ > > > > I imported a new upstream .orig.tar.gz version as descibed in > > https://wiki.debian.org/Python/GitPackaging#New_upstream_release > > and could build and upload the package without problem. > > > > Now the command "git-dpm status" fails with: > > $ git-dpm status > > git-dpm: ERROR: 'upstream' does not contain previously recorded revision > > '8234fc2de2b89d65661233b357f922494590b5aa'! > > At a guess, it looks like you didn't push the upstream or the > prestine-tar branches to git.debian.org. git-dpm requires all branches > to be pushed, not just master. > > git push --all > Ah. Maybe this should be added in the documentation https://wiki.debian.org/Python/GitPackaging > i.e. pykcs11_1.3.0.orig.tar.gz isn't in prestine-tar, and the upstream > branch should point to the latest upstream import > '8234fc2de2b89d65661233b357f922494590b5aa' but doesn't. > pykcs11_1.3.0.orig.tar.gz is in pristine-tar but the new version 1.3.1 is/was not. However this shouldn't have caused you errors with your working > directory unless you deleted your working directory and cloned again > from git.debian.org. > I cloned again the repo from git.debian.org :-( I now just did: $ git-dpm import-new-upstream --ptc --rebase-patched ../pykcs11_1.3.1.orig.tar.gz git-dpm: ERROR: Cowardly refusing to run as 'upstream' differs from recorded '8234fc2de2b89d65661233b357f922494590b5aa'!. Use --ignore-unclean-branches to delete/ignore it. Or if you manually modified that branch to contain more history and want to incorporate that (and only then) use --use-strange-upstream-branch. And then I forced the command: $ git-dpm import-new-upstream --ptc --rebase-patched --ignore-unclean-branches ../pykcs11_1.3.1.orig.tar.gz git-dpm: WARNING: upstream was out of date, deleting first... Branche upstream supprimée (précédemment 171ade5). Created upstream with contents of pykcs11_1.3.1.orig.tar.gz and parents 8234fc2de2b89d65661233b357f922494590b5aa There were no patches recorded, so merging the new state directly (no git-dpm rebase-patched needed). git-dpm: WARNING: No parent commit specified. This means the upstream branch was created from the .orig.tar with only theold upstream branch as parent (but not any possible upstream git history). Use 'git config dpm.importWithoutParent true' to no longer show this warning. or 'git config dpm.importWithoutParent false' to make this an hard error. calling pristine-tar commit '../pykcs11_1.3.1.orig.tar.gz' '4cf2e546ad26235a581cb9b6cfa9bbea0b415b80'... pristine-tar: committed pykcs11_1.3.1.orig.tar.gz.delta to branch pristine-tar I now have commits in upstream and pristine-tar branches. And also a new (duplicate) commit in master "record new upstream branch created by importing pykcs11_1.3.1.orig.tar.gz and merge it" The good news: $ git-dpm status git-dpm: everything up to date > and also > > $ git-dpm tag > > git-dpm: ERROR: 'upstream' differs from recorded one! > > This is a known bug with git-dpm. See > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801548. > > Until it is fixed, the best work around seems to be to create the tags > manually, at least until you import a new upstream version. Then the > problem will go away. > With my changes above I now have: $ git-dpm tag Creating new tag 'upstream/1.3.1'... Creating new tag 'patched/1.3.1-1'... Creating new tag 'debian/1.3.1-1'... I looks like the repo is back in order. I will see if I have problems the next time I update the package. Thanks -- Dr. Ludovic Rousseau
git-dpm: ERROR: 'upstream' does not contain previously recorded revision
Hello, I tried to update my package pykcs11 since the repository moved from SVN to git. http://anonscm.debian.org/cgit/python-modules/packages/pykcs11.git/ I imported a new upstream .orig.tar.gz version as descibed in https://wiki.debian.org/Python/GitPackaging#New_upstream_release and could build and upload the package without problem. Now the command "git-dpm status" fails with: $ git-dpm status git-dpm: ERROR: 'upstream' does not contain previously recorded revision '8234fc2de2b89d65661233b357f922494590b5aa'! and also $ git-dpm tag git-dpm: ERROR: 'upstream' differs from recorded one! I think I missed something. I don't want to add more errors/problems in the git repository. I am very new to git-dpm process and I don't want to make the repository (more) unusable. Can someone tell me what I missed and fix the error? Or describe in detail how to fix the problem? Thanks -- Dr. Ludovic Rousseau
Re: Bug#623820: RM: python2.5
2011/4/23 Luca Falavigna dktrkr...@debian.org: Il 23/04/2011 12:53, Matthias Klose ha scritto: Please remove python2.5 from unstable There are still a lot of packages which require python2.5. I prepared an analysis to track them. I excluded alpha and hppa from the list, as per http://lists.debian.org/20110401205549.ga12...@hymers.org.uk. I'm sure I saw a mail saying autobuilders don't care about those architectures animore, but I can't find it right now. But anyway: == Require binNMUs == pykcs11: python-pykcs11 pyscard: python-pyscard I just uploaded a new version of this two packages of mine. Regards, -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlkticmeiqghlsksnmgzje4wa9jt...@mail.gmail.com
E: dh_python2:146: you most probably have to build extension for python2.5.
Hello,
I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The
conversion was easy. The version in unstable uses dh_python2.
I also wanted to move my debian/rules file from the heavy version
[2] to the minimal version using:
#!/usr/bin/make -f
%:
dh $@ --with python2
But I now get a warning and an error (complete log attached):
[...]
dh_python2
W: dh_python2:94: Python 2.6 should install files in
/usr/lib/python2.6/dist-packages/. Did you forget
--install-layout=deb?
E: dh_python2:146: you most probably have to build extension for python2.5.
make: *** [binary] Error 12
My package provides a binary extension so must be compiled for each
supported Python versions: 2.5 and 2.6 as of now.
My debian/control file [3] is:
Source: pykcs11
Priority: optional
Maintainer: Ludovic Rousseau rouss...@debian.org
Uploaders: Debian Python Modules Team
python-modules-t...@lists.alioth.debian.org, David Smith
davidsm...@acm.org
Build-Depends: debhelper (= 7.0.0), swig, python-all-dev (= 2.6.6-3)
Standards-Version: 3.9.1
Section: python
Vcs-Svn: svn://svn.debian.org/python-modules/packages/pykcs11/trunk
Vcs-Browser:
http://svn.debian.org/viewsvn/python-modules/packages/pykcs11/trunk/
Homepage: http://www.bit4id.org/trac/pykcs11/
Package: python-pykcs11
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
Provides: ${python:Provides}
Description: PKCS#11 wrapper for Python
PyKCS11 let you access to almost all PKCS#11 functions and data types using
any PKCS#11 library, such as the various modules supplied by smartcard
vendors.
.
The wrapper comes with 2 interfaces: a low level and very thin interface over
the original PKCS#11 API, generated using the SWIG compiler (designed for
library tests); and an high level interface that offers a simpler access (with
few limits) to the PKCS#11 APIs.
Is there an easy way to build for 2 versions of Python using dh?
Should I just care about the latest python 2.x version since we should
only have one python 2.x version in wheezy (2.7)?
I tried to change:
Build-Depends: [...], python-all-dev (= 2.6.6-3)
to
Build-Depends: [...], python-dev (= 2.6.6-3)
but I still have the same error.
I even tried to remove python2.5 but still the same error :-(
Any idea?
Thanks
[1] http://packages.debian.org/sid/python-pykcs11
[2]
http://svn.debian.org/viewsvn/python-modules/packages/pykcs11/trunk/debian/rules?view=markup
[3]
http://svn.debian.org/viewsvn/python-modules/packages/pykcs11/trunk/debian/control?view=markup
--
Dr. Ludovic Rousseau
origDir: ../../tarballs
Complete layout information:
buildArea=/home/rousseau/Sources/Debian/SVN/pykcs11/build-area
origDir=../../tarballs
tagsDir=/home/rousseau/Sources/Debian/SVN/pykcs11/tags
tagsUrl=svn+ssh://svn.debian.org/svn/python-modules/packages/pykcs11/tags
trunkDir=/home/rousseau/Sources/Debian/SVN/pykcs11/trunk
trunkUrl=svn+ssh://svn.debian.org/svn/python-modules/packages/pykcs11/trunk
dpkg-checkbuilddeps
UNRELEASED tag found - you don't want to release with it, do you?
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/pykcs11-1.2.3 exists,
renaming to
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/pykcs11-1.2.3.obsolete.0.654689672011049
mergeWithUpstream mode detected, looking for
../../tarballs/pykcs11_1.2.3.orig.tar.gz
I: mergeWithUpstream property set, looking for upstream source tarball...
tar --no-same-owner --no-same-permissions --extract --gzip --file
/home/rousseau/Sources/Debian/SVN/tarballs/pykcs11_1.2.3.orig.tar.gz
--directory
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/tmp-0.210841780386062
mv
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/tmp-0.210841780386062/PyKCS11-1.2.3
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/pykcs11-1.2.3
svn --force export /home/rousseau/Sources/Debian/SVN/pykcs11/trunk
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/pykcs11-1.2.3
Export complete.
rm -rf
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/tmp-0.210841780386062
chmod -R u+r+w+X,g+r-w+X,o+r-w+X --
/home/rousseau/Sources/Debian/SVN/pykcs11/build-area/pykcs11-1.2.3
dpkg-buildpackage -rfakeroot
dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor):
dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor):
dpkg-buildpackage: source package pykcs11
dpkg-buildpackage: source version 1.2.3-4
dpkg-buildpackage: source changed by Ludovic Rousseau rouss...@debian.org
dpkg-source --before-build pykcs11-1.2.3
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
dh clean --with python2
dh_testdir
dh_auto_clean
make[1]: Entering directory
`/home/rousseau/Sources/Debian/SVN/pykcs11
Re: E: dh_python2:146: you most probably have to build extension for python2.5.
2011/3/10 Jan Dittberner ja...@debian.org: On Thu, Mar 10, 2011 at 09:03:03PM +0100, Ludovic Rousseau wrote: Hello, I moved my package pykcs11 [1] from dh_pycentral to dh_python2. The conversion was easy. The version in unstable uses dh_python2. I also wanted to move my debian/rules file from the heavy version [2] to the minimal version using: #!/usr/bin/make -f %: dh $@ --with python2 But I now get a warning and an error (complete log attached): [...] dh_python2 W: dh_python2:94: Python 2.6 should install files in /usr/lib/python2.6/dist-packages/. Did you forget --install-layout=deb? E: dh_python2:146: you most probably have to build extension for python2.5. make: *** [binary] Error 12 you might want to add override_dh_auto_build: python setup.py install --root=$(CURDIR)/debian/python-pykcs11 --install-layout=deb override_dh_auto_install instead. This fixes the warning but not the error. Thanks -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTiksxq2x1E12o9O+kYT2whd=yytt6vwgmu3w8...@mail.gmail.com
Re: E: dh_python2:146: you most probably have to build extension for python2.5.
2011/3/10 Jakub Wilk jw...@debian.org: * Ludovic Rousseau ludovic.rouss...@gmail.com, 2011-03-10, 21:03: My package provides a binary extension so must be compiled for each supported Python versions: 2.5 and 2.6 as of now. ...your new debian/rules does *not* compile extensions for all supported versions. (The old one did.) And dh is not (yet) smart enough to do that for me? OK, I will continue to use my heavy rules file until python-all-dev provides only one version of Python. Thanks -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikbuwe7sdz7kux4oyuuysdvfo9pbl2pby706...@mail.gmail.com
Re: E: dh_python2:146: you most probably have to build extension for python2.5.
2011/3/10 Jakub Wilk jw...@debian.org: * Ludovic Rousseau ludovic.rouss...@gmail.com, 2011-03-10, 21:41: My package provides a binary extension so must be compiled for each supported Python versions: 2.5 and 2.6 as of now. ...your new debian/rules does *not* compile extensions for all supported versions. (The old one did.) And dh is not (yet) smart enough to do that for me? The upstream tarball contains both setup.py and Makefile. In such a case dh uses Makefile-based build system. And then, it cannot possibly know that the Makefile has anything to do with Python. Passing --buildsystem=python_distutils to dh might do the trick. Exact. Problem solved. Thanks. -- Dr. Ludovic Rousseau -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=0jwlsb9gpkkspoyhscdh-v63-sm3uuay7r...@mail.gmail.com
Re: Python 2.6 in unstable
2009/11/14 Jakub Wilk uba...@users.sf.net:
* Piotr Ożarowski pi...@debian.org, 2009-11-14, 01:29:
After rebuilding most packages that build depend on
python-all{,-dev,-dbg}[0], I reported few more bugs. Packages that
didn't FTBFS but ship files in /usr/local are now listed on that page as
well (with usr-local usertag).
If someone wants to help with checking build logs and reporting bugs,
please download failed.tar.xz from [1] and file bugs for packages
not listed on tiny.pl/hqwjz yet.
I've triaged most of these build failures.
1) These packages fail in sid, too:
clientcookie dynagen euca2ools pyspi python-bibtex python-clientform
python-dmidecode python-mechanize qtiplot wxwidgets2.8
Bugs are already filed. (Maybe we should usertag them python2.6 anyway?)
2) These packages failed because of (temporarily?) broken build-deps:
gnuradio libkate petsc4py pycg python-kde3 subversion
3) These packages failed likely because one of build-deps didn't support
python2.6:
babel jppy pyexiv2 pymvpa pysparse python-biopython python-edje
python-qt4 renpy tagpy creoleparser kaa-imlib2 pygtk pynifti pysvn
python-chaco python-enable python-scipy revelation twisted-calendarserver
freej kaa-metadata pyicu pyqwt3d pytables python-djvulibre python-evas
pyvorbis swftools html5lib necpp pykaraoke pyqwt5 pytagsfs python-ecore
python-qt3 qscintilla2 symeig
4) These are probably real python2.6-related failures:
4.1) These packages seems to hardcode a Python version somewhere:
boost1.38 boost1.39 boost1.40 distribute libkml polybori pykcs11
python-bsddb3 python-multiprocessing python-stdlib-extensions
pykcs11: fixed in 1.2.1-3 I just uploaded to unstable.
Bye
--
Dr. Ludovic Rousseau
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Python 2.6 in unstable
2009/11/14 Jakub Wilk uba...@users.sf.net:
* Piotr Ożarowski pi...@debian.org, 2009-11-14, 01:29:
After rebuilding most packages that build depend on
python-all{,-dev,-dbg}[0], I reported few more bugs. Packages that
didn't FTBFS but ship files in /usr/local are now listed on that page as
well (with usr-local usertag).
If someone wants to help with checking build logs and reporting bugs,
please download failed.tar.xz from [1] and file bugs for packages
not listed on tiny.pl/hqwjz yet.
I've triaged most of these build failures.
1) These packages fail in sid, too:
clientcookie dynagen euca2ools pyspi python-bibtex python-clientform
python-dmidecode python-mechanize qtiplot wxwidgets2.8
Bugs are already filed. (Maybe we should usertag them python2.6 anyway?)
2) These packages failed because of (temporarily?) broken build-deps:
gnuradio libkate petsc4py pycg python-kde3 subversion
3) These packages failed likely because one of build-deps didn't support
python2.6:
babel jppy pyexiv2 pymvpa pysparse python-biopython python-edje
python-qt4 renpy tagpy creoleparser kaa-imlib2 pygtk pynifti pysvn
python-chaco python-enable python-scipy revelation twisted-calendarserver
freej kaa-metadata pyicu pyqwt3d pytables python-djvulibre python-evas
pyvorbis swftools html5lib necpp pykaraoke pyqwt5 pytagsfs python-ecore
python-qt3 qscintilla2 symeig
4) These are probably real python2.6-related failures:
4.1) These packages seems to hardcode a Python version somewhere:
boost1.38 boost1.39 boost1.40 distribute libkml polybori pykcs11
python-bsddb3 python-multiprocessing python-stdlib-extensions
pykcs11: fixed in 1.2.1-3 I just uploaded to unstable.
Bye
--
Dr. Ludovic Rousseau
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Who is supposed to remove the .pyc files? (see #386211)
Hello, I received bug report #386211: Package: plucker Version: 1.8-16+b1 Severity: normal Upon update to this version the byte-compiled files in /usr/lib/python2.3/site-packages/PyPlucker/ were left behind. 1.8-16+b1 is generated for Python 2.4 so the installed files are now in /usr/lib/python2.4/site-packages/PyPlucker/ and /usr/lib/python2.3/site-packages/PyPlucker/ should be empty (and deleted). My problem is that the package does not provide the .pyc files. These files are generated when executing the Python script as _root_. Executing the Python scripts as a normal user does not create the .pyc (permission denied, of course). How am I supposed to manage this? Thanks, PS: I am not on the mailing list. Reply-to: set correctly. -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Help with #381343 (FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up)
Hello, I am _not_ a Python user/developper but maintain the plucker and plucker-desktop packages which are Python scripts. The warnings I get are: /usr/lib/python2.3/site-packages/PyPlucker/helper/gettext.py:131: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up if _lsbStrToInt(buffer[:4]) != 0x950412de: /usr/lib/python2.3/site-packages/PyPlucker/helper/gettext.py:176: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up f.write(_intToLsbStr(0x950412de))# magic number /usr/lib/python2.3/site-packages/PyPlucker/helper/prc.py:244: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up attr = (auid 0xff00) 24 /usr/lib/python2.3/site-packages/PyPlucker/helper/prc.py:876: FutureWarning: hex/oct constants sys.maxint will return positive values in Python 2.4 and up attr = (auid 0xff00) 24 What is the best way to solve these warnings and avoid possible problems with Python 2.4? Please cc: me on replies since I am not a subscriber of this list. Thanks, -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
