Hi Gert,
I applied your patch but in my unstable chroot (and this is where the
problem occures) the error remains the same. IMHO the problem is not
that the third party copy of libbz2 is built but rather that a -L
option
Hi Ghislain,
On Mon, Oct 21, 2013 at 02:54:50PM +0100, Ghislain Vaillant wrote:
Just a short update on this RFS,
Following your advice, I have moved the package over to debian-science
and followed the debian-science policy. It now hosted on
Hello Andreas,
well, for me in the Debian-unstable VM I use for package preparation the
error stays the same like I reported yesterday, i.e. the build
terminates in the dh_install phase and not unexpected, because there
are o directories mod??/* (see below)
best regards,
Gert
gcc
-o
On Tue, 2013-10-22 at 08:42 +0200, Andreas Tille wrote:
Hi Ghislain,
On Mon, Oct 21, 2013 at 02:54:50PM +0100, Ghislain Vaillant wrote:
Just a short update on this RFS,
Following your advice, I have moved the package over to debian-science
and followed the debian-science policy. It
Package: sponsorship-requests
Severity: important
Dear mentors and games team members,
I am looking for a sponsor for my package scorched3d
* Package name: scorched3d
Version : 43.3+dfsg-1
Upstream Author : Gavin Camp
* URL : http://scorched3d.co.uk/
* License
Hi Juhani,
I'd consider sponsering the package regarding my Sponsering of Blends
effort at
https://wiki.debian.org/DebianPureBlends/SoB
but the package is not listed inside the Debian Games tasks.
Kind regards
Andreas
On Tue, Oct 22, 2013 at 03:22:05PM +0300, Juhani Numminen wrote:
Hi Andreas,
Tue, 22 Oct 2013 14:44:43 +0200
Andreas Tille andr...@an3as.eu kirjoitti:
Hi Juhani,
I'd consider sponsering the package regarding my Sponsering of Blends
effort at
https://wiki.debian.org/DebianPureBlends/SoB
but the package is not listed inside the Debian Games tasks.
Hi Juhani,
On Tue, Oct 22, 2013 at 04:28:29PM +0300, Juhani Numminen wrote:
Hi Andreas,
Tue, 22 Oct 2013 14:44:43 +0200
Andreas Tille andr...@an3as.eu kirjoitti:
Hi Juhani,
I'd consider sponsering the package regarding my Sponsering of Blends
effort at
Hi Gert,
On Tue, Oct 22, 2013 at 11:40:54AM +0200, Gert Wollny wrote:
Hello Andreas,
well, for me in the Debian-unstable VM I use for package preparation the
error stays the same like I reported yesterday, i.e. the build
terminates in the dh_install phase and not unexpected, because there
I think, it will be on the next release.
I prefer stabilize the 1.2.12 with the first few changes.
But I will change quickly after, I promise ;)
On Mon, Oct 21, 2013 at 9:05 PM, Eriberto eribe...@eriberto.pro.br wrote:
Hey,
The 1.2.13 is available. Please, consider it.
Regards,
Eriberto
Your message dated Tue, 22 Oct 2013 16:27:39 +
with message-id e1vyenz-0003tg...@quantz.debian.org
and subject line closing RFS: qgit/2.5-2 [RC]
has caused the Debian Bug report #726835,
regarding RFS: qgit/2.5-2 [RC]
to be marked as done.
This means that you claim that the problem has been
Hi mentors,
I have a package [1] that builds its doc using sphinx [2] and the
intersphinx extension [3].
Intersphinx attempts to download objects.inv files to generate links
to external documentation.
Packages should be self-contained so trying to access the net can be
considered a polycy
Hi,
I have to say that I am new to the world of Linux and am on a very steep
learning curve as I have to package a shared library which I have written
in 'C' as well as a Python package. I have successfully created a deb file
today which has taken much work. However, it appears it's empty and so
On Wed, Oct 23, 2013 at 1:58 AM, Andrew Bakin wrote:
1) Should I be trying to use the build.sh script at all? If not, I need a
mechanism for copying some files in the deb package (a udev rule). I know I
can do this in debian/rules - more reading required.
If build.sh is the upstream supported
On Tue, Oct 22, 2013 at 06:58:43PM +0100, Andrew Bakin wrote:
1) Should I be trying to use the build.sh script at all?
I don't know what does this script actually do. If it's the only way to
compile the library then it's much better to provide a sane build system
like a Makefile instead.
If
Hi,
On Tue, Oct 22, 2013 at 03:37:35PM +0200, Andreas Tille wrote:
Hi Gert,
On Tue, Oct 22, 2013 at 11:40:54AM +0200, Gert Wollny wrote:
Hello Andreas,
well, for me in the Debian-unstable VM I use for package preparation the
error stays the same like I reported yesterday, i.e. the
+++ Andrew Bakin [2013-10-22 18:58 +0100]:
Hi,
I have to say that I am new to the world of Linux and am on a very steep
learning curve as I have to package a shared library which I have written
in 'C' as well as a Python package. I have successfully created a deb file
today
Hi,
I got an old Debian source package that is no longer exist in the repo any
more, and want to pick up from there. I.e., apply all the patches then remove
them for debian/patches. That's what I did, but when I tried to build it via
pbuilder, I get:
make clean
dh_quilt_unpatch
Patch
Hi!
Faré fah...@gmail.com writes:
I am looking for a sponsor for the new version 3.22.1-1
of my package cl-launch.
It builds these binary packages:
cl-launch - uniform frontend to running Common Lisp code from the shell
The package appears to be lintian clean.
The package can be found
On 10/22/2013 03:45 PM, Tong Sun wrote:
I got an old Debian source package that is no longer exist in the
repo any more, and want to pick up from there. I.e., apply all the
patches then remove them for debian/patches. That's what I did, but
when I tried to build it via pbuilder, I get:
make
debian/source/format likely still has quilt as the package format.
No, the package is so old that it doesn't even have the debian/source/format
file.
Hmmm... maybe I should start all over from scratch?
But, but, but.. why are you removing the patch system and manually
patching the upstream
On 10/22/2013 04:59 PM, Tong Sun wrote:
No, the package is so old that it doesn't even have the
debian/source/format file. Hmmm... maybe I should start all over
from scratch?
Perhaps.
The package was removed because the upstream was long gone. I want
to pick it up and become the upstream.
That quilt error may be from a .pc directory still in the build tree?
BINGO!
Removing the .pc directory solved the problem.
Thanks!!!
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hi,
Multiple pbuilders setting from pbuilder User's Manual doesn't seem to work
for me.
The FAQ section 8 from pbuilder User's Manual
(http://www.red-bean.com/doc/pbuilder/pbuilder-doc.html#ENVVARDISTRIBUTIONSWITCH)
describes briefly a way to setup and use multiple pbuilder setups by
Le Tue, Oct 22, 2013 at 08:43:05PM +0200, Andreas Tille a écrit :
I have done the changes needed to build sra-sdk in an unstable chroot
manually. It remains totally unclear to me why the build fails with
pbuilder but works in a minimal unstable chroot anyway.
Charles, if you can build the
Hi,
I've already removed the Dm-Upload-Allowed entry from my *downloaded* .dsc
file, but it still shows up in the *built* .dsc file.
What's the proper way to fix it?
thx
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, Oct 22, 2013 at 6:31 PM, Tong Sun mlist4sunt...@yahoo.com wrote:
Hi,
I've already removed the Dm-Upload-Allowed entry from my *downloaded* .dsc
file, but it still shows up in the *built* .dsc file.
What's the proper way to fix it?
Remove the DMUA entry from debian/control.
Hi,
Is it OK to have compile warnings when building a package? If not,
how can I fix the following:
dial.c: In function 'main':
dial.c:273:8: warning: ignoring return value of 'write', declared with
attribute warn_unused_result [-Wunused-result]
write(fd, buf, bufidx);
I got a bunch of
On Wed, Oct 23, 2013 at 9:41 AM, Tong Sun wrote:
Is it OK to have compile warnings when building a package? If not,
It is fairly normal to have compile warnings since GCC gets stricter over time.
how can I fix the following:
dial.c: In function 'main':
dial.c:273:8: warning: ignoring
On 22/10/13 18:41, Tong Sun wrote:
Hi,
Is it OK to have compile warnings when building a package?
Although sometimes the compiler is just noisy, I don't like ignoring
compiler warnings. They may be a hint of an omission, a bug, or in the
worst case, a security issue.
I prefer to shut the
Dear mentors,
I'm still doing the debian packaging for ASDF at this point in time
for the new upstream maintainer Robert Goldman.
This brand new ASDF release received a lot of testing, and
fixes a shameful bug in previous recent releases
that affects usability under debian (#723977).
Can one of
31 matches
Mail list logo
