Hello!
Checkout from CVS.
Run ./configure or equal.
Run 'make tar' or 'make package' or 'make rpm' or 'make dist' or
whatever the corresponding target in makefile is named.
Then rename the produced tar.gz / bz2 to orig.tar.gz / bz2
Cheers,
Björn.
2012/2/2 Jerome BENOIT :
> Hello List:
>
> what
How about doing it like it's done with the unrar package:
According to packages.debian.org there are two pkgs.
unrar
unrar-free
So I'd suggest name the free one slalib and the other one
slalib-nonfree or vice versa (like the unrar example).
Cheers,
Björn
2012/2/8 Olе Streicher :
> Hi,
>
> the
/libblocxx/libblocxx_2.1.0-1.dsc
Regards,
Björn Esser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iF4EAREIAAYFAk9LyxkACgkQ3u1SIc8s7PWgIAD/Q2eyOBwvJ+H6tYYLhw0+dB35
EIoss2MUNzWUJjMZfjMBAMX2R+EF89ZlOuOVORCmMe6hd9811rfzV9iPBihw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
*** UPDATE ***
Added a symbols-file for libblocxx6.
Added a dbg-pakage:
* libblocxx-dbg - BloCXX debugging symbols
Regards,
Björn Esser
Am 27.02.2012 19:27, schrieb Björn Esser:
> Package: sponsorship-requests Severity: wishlist
>
amd64
arches.
Thanks for your help in advance.
BR,
Björn Esser
[1] people.debian.org/~aurel32/qemu/
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.or
Am 15.03.2012 00:07, schrieb Benoît Knecht:
Hello Benoît,
> Can't you just grab and unpack one of the prebuilt debian kernels from the
> archive? qemubuilder can load an initrd image, so even if ipv6 and ext3 are
> not built-in, it should work just fine.
The prebuild kernels don't ship any initr
Am 16.03.2012 12:31, schrieb Benoît Knecht:
> Well, that might not be the fastest way, but the following works just
> fine to generate the initrd; all you need is debootstrap, binfmt-support
> and qemu-user-static installed (I will assume you want and armel
> kernel/initrd in this example, but the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
*** UPDATE ***
New version from svn trunk (544~svn).
Documentation (html + LaTeX) is now included in build-process.
* Package name: libblocxx
Version : 544~svn-1
It builds those binary packages:
libblocxx-dbg - BloCxx debuggi
ch: change BloCxx version to 544svn
* add patch: fix path to dot in Doxyfile.in
* add patch: exclude testsuite from documentation
* add patch: don't build autogenerated manpages
Regards,
Björn Esser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: U
n in build
* add patch: use default automake
* add patch: fix path to dot in Doxyfile.in
* add patch: exclude testsuite from documentation
* add patch: don't build autogenerated manpages
Regards,
Björn Esser
Am 19.04.2012 10:47, schrieb Igor Pashev:
> 19.04.2012 12:30,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Try something like:
version=3
http://www.bioconductor.org/packages/release/bioc/src/contrib/qvalue_([\d\.]+)\.tar\.gz
`wget
http://www.bioconductor.org/packages/release/bioc/src/contrib/qvalue_1.30.0.tar.gz`
works fine for me.
Cheers,
Björn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ok, so here we go again correcting some issues:
*** UPDATE ***
New version from svn trunk (2.3.0~svn544 replaces 2.1.0).
Documentation (html + LaTeX) is now included in build-process.
Dear mentors,
I am looking for a sponsor for my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The fixed and rebuild package has correctly uploaded to mentors now.
Am 19.04.2012 11:16, schrieb Björn Esser:
> Ok, so here we go again correcting the issues:
>
> Severity: wishlish
>
> *** UPDATE *** New version from svn trun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Boris!
I just investigated a bit inside the source-tar doing this:
cd doc
qmake
make
./doxyfilter -g
sed -i -e's/GENERATE_LATEX.*= NO/GENERATE_LATEX = YES/'\
- -e's/GENERATE_MAN.*= NO/GENERATE_MAN = YES/' ./Doxyfile
doxygen ./Doxyfile
cd ..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As stated in my previous message, this is the way to generate the
needed Doxyfile:
cd doc (inside the tarball-basedir )
qmake ( produce Makefile )
make ( build ./doxyfilter )
./doxyfilter -g ( generates Doxyfile )
after this some sed-magic to enabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 19.04.2012 16:16, schrieb Boris Pek:
> Thanks all for answers.
You're welcome.
> I was searching for: /doxyfilter -g This command generates Doxyfile
> which is necessary for Doxygen.
>
>> However I can't find anywhere in the Policy that it's an
e to ITS, since as long it was on mentors no one
was intended to.
Best Regards,
Björn Esser
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMS3
Hello!
Why does dh >= 9 (in paticular the latest version in sid) put the
debugging-symbols in
usr/lib/debug/.build-id/$(2-Byte-Random)/$(Random).debug when building
a lib with multi-arch-support?
The package uses straight debhelper. No tweaks in debian/rules, but
some usual override_*-indep and o
> See #642158, for an explanation. The short story is, it's easier to
> support build-id (from a gdb PoV) than N+1 multi-arched paths.
>
> It should not cause any issues.
Thanks for your answer.
So everything is fine as it gets done then, I think.
BR,
Björn Esser
--
To UNSU
he package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/y/yast2-devtools/yast2-devtools_2.21.6-1.dsc
I would be glad if someone could help me on further questions about
packaging for debian and, when entirely finished, uploaded this
package for me.
Kind regar
-dev, libany-doc, etc.). I hope someone would and could
help me doing so. If it would be someone with German as native (not
restricted to this, but my English is not that elaborated in rather
special technical-terms), it would be great.
Thanks to you in advance.
Best Regards,
Björn Esser
n the meantime here
> are some useful links (which should have more than enough information
> to get you started if you're already familiar with packaging):
>
> 2011/11/7 Björn Esser :
>> how to write/create man-pages
>
> See https://wiki.ubuntu.com/PackagingGuide/Supplemen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
What shall I do, when there's already a debian-dir inside the .orig.tar,
e.g. when upstream already package his/her program for ubuntu?
Can I safely remove the existing debian-dir from the .orig.tar?
What else can I do?
BR,
Björn
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everybody!
When I'm running lintian on my almost finished package, it tells me:
E: jailkit: duplicate-updaterc.d-calls-in-postinst jailkit
E: jailkit: duplicate-updaterc.d-calls-in-postrm jailkit
But why? I do not see anything duplicate ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks a lot. This fixed it.
I'm using add-shell now, too.
Am 10.11.2011 01:48, schrieb Michael Tautschnig:
>> Hello everybody!
>>
>> When I'm running lintian on my almost finished package, it tells me:
>>
>> E: jailkit: duplicate-updaterc.d-calls-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
I'm just working on packaging. When I build on source into 2 pkgs.
Theese are the two packages:
jailkit -- here go all the c-binaries
jailkit-common -- here go python-scripts, manpages, other no-arch
After building the pkg, lintian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
I'm just working on packaging. When I build on source into 2 pkgs.
Theese are the two packages:
jailkit -- here go all the c-binaries
jailkit-common -- here go python-scripts, manpages, other no-arch
After building the pkg, lintian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> "Newer" versions of lintian (around 2.5.1 or so) will check direct
> dependencies (that are built from the same source) if said dependencies
> are processed together.
>
> So if you placed your manpage correctly in jailkit-common and jailkit
> dep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
lintian -V shows me: Lintian v2.4.3+squeeze1
It's the one which is shipped on default with Squeeze.
Am 10.11.2011 10:58, schrieb Alexander Reichle-Schmehl:
> Hi!
>
> Am 10.11.2011 10:37, schrieb Björn Esser:
>
>>> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 10.11.2011 12:08, schrieb Arno Töll:
> On 10.11.2011 11:42, Ansgar Burchardt wrote:
>> I'm just curious: what is this used for? Isn't YaST only used by SuSE?
YaST was licensed under GPLv2 somewhen in 2004/2005. So it can be used
by anyone and ins
ernatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/j/jailkit/jailkit_2.14-1.dsc
I would be glad if someone uploaded this package for me.
Kind regards,
Björn Esser
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linu
e/create those overrides?
Thanks to all in advance.
BR,
Björn Esser
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iF4EAREIAAYFAk7YoqgACgkQ3u1SIc8s7PXfwQD/fbSFwAayBwrv2/H7
me.
Kind regards,
Björn Esser
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iF4EAREIAAYFAk7aQGMACgkQ3u1SIc8s7PWmKAEAiv6rU9PQtCDK1JN22FJ7frZW
URllzE1nWN3A7iZTz8kBANqb88Mt/592mCvNX1mjqLeDVXC1Dtd1B4wmJmme4QAy
=dbhn
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 03.12.2011 22:54, schrieb Andreas Moog:
> I'm not a DD so I can't sponsor your package.
I hope there will be some DD to sponsor my package, somewhen...
>> * Package name: libblocxx Version : 2.2.0-1 Upstream
>> Author : Kevin Harri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just uploaded an improved version of this package to mentors (see
below).
I hope there will be some sponsor for my package.
Am 03.12.2011 22:54, schrieb Andreas Moog:
> On 12/03/2011 04:29 PM, Björn Esser wrote:
>
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
How shall software be handled, when it needs
- huge modifactions
- scripts to be replaced by 'debianized' ones
- to be extended by custom scripts or progs
when packaging it for debian?
Shall the custom / replaced stuff be pl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
I just wanted to ask how mature Package-format 3.0 (git) became until now.
BR,
Björn.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iF4EAREIAAYFAk8Une4AC
37 matches
Mail list logo
