Ángel Luis writes:
> I am trying to package |numpy 1.12.1| into deb package.
The creation of a Debian package is — quite deliberately — not an
automated process [0]. There are many human decisions to be made, in
order to work well with the rest of Debian, and to conform with Debian
Policy.
> Ho
On Wed, Mar 22, 2017 at 11:15:06PM +0100, Ángel Luis wrote:
> I am trying to package |numpy 1.12.1| into deb package.
testing, unstable and jessie-backports contain 1.12.0.
If you really need 1.12.1 you should start with the existing package and
update it, not write all the packaging from scratch.
I am trying to package |numpy 1.12.1| into deb package. In order to do
that first I run
|dh_make -f ../numpy1.12.1.tar.gz|
and it generates a |debian| directory, in the |control| file generated
it shows |numpyBROKEN|, I change that to numpy1.12.1 and edit
|debian/rules| to tell that this pack
Christopher Hoskin writes:
> I've made a mistake, and kombu has got uploaded to unstable instead of
> experimental. (I had experimental in the changelog, but didn't pass
> "-d experimental" to sbuild on the final build). I'm very sorry about
> this. What is the best way to resolve this? Should I
I've made a mistake, and kombu has got uploaded to unstable instead of
experimental. (I had experimental in the changelog, but didn't pass
"-d experimental" to sbuild on the final build). I'm very sorry about
this. What is the best way to resolve this? Should I file a bug
against the ftp.debian.org
5 matches
Mail list logo
