Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make deb error #7

Closed
AlexUhde opened this issue Oct 16, 2013 · 4 comments · Fixed by #8
Closed

Make deb error #7

AlexUhde opened this issue Oct 16, 2013 · 4 comments · Fixed by #8

Comments

@AlexUhde
Copy link

Hello,

I tired compling the configshell-fb for Debian 7.2 and got the Error that the versionnumber does not start with a number.

original Error in german:
parsechangelog/debian: Warnung: debian/changelog(l1): Version »v1.1.fb9.6.gdccc4ed« ist ungültig: Versionsnummer beginnt nicht mit einer Ziffer
LINE: configshell (v1.1.fb9.6.gdccc4ed) unstable; urgency=low
dpkg-buildpackage: Quellpaket configshell
dpkg-buildpackage: Quellversion v1.1.fb9.6.gdccc4ed
dpkg-buildpackage: Fehler: Versionsnummer beginnt nicht mit einer Ziffer

@JonnyJD
Copy link
Contributor

JonnyJD commented Oct 16, 2013

What tools did you use to build and why did that tool think taking the full tag as version number is the way to go?

The changelog (where the version number is taken from) isn't part of this repository, but created by some tool you used. So my guess would be this is a problem with that tool.

Using v<version number> as the tag is somewhat a standard way of tagging versions.

@AlexUhde
Copy link
Author

Hello Jonny,

I use Debian:
Linux avaNAS 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64

I followed the instructions on: http://www.linux-iscsi.org/wiki/Downloads#Installation
in short:
Install prerequisites: python-epydoc python-urwid python-simpleparse python-ipaddr python-netifaces python-configobj libreadline6 python-dev make dpkg-dev git-core debhelper
Clone Git and "make deb"

Thanks,
Alex

@JonnyJD
Copy link
Contributor

JonnyJD commented Oct 16, 2013

Oh, I completely forgot about that Makefile.

In that case it is the repo's fault and should be fixed. Thanks for providing the details.

I can reproduce it and it should be easy to fix. Hopefully there won't be many more problems.

@JonnyJD
Copy link
Contributor

JonnyJD commented Oct 16, 2013

Should be fixed with #8. Please test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants