Bug#643255: proguard package
On 06/05/2013 09:24 PM, tony mancill wrote: > Hello Sam, > > Would you be opposed to an NMU of proguard to update it to a newer > version and to address the FTBFS error? Or perhaps to the packaging > being moved to collaborative maintenance under the Debian Java team? > > The current version is blocking the transition to OpenJDK7. If you have an NMU ready to go then please go ahead. I'm happy to take look today. If you think it makes sense to move to collaborative maintenance with the Java team I'd be happy to consider that. What exactly would be involved in doing that? > > Thank you, > tony > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668524: [NMU] dmucs: packaging format 3.0 and hardened build flags
On 05/10/2012 08:43 AM, Jari Aalto wrote: > I'm planning to NMU with changes listed in previous mail's patch to help > migrate away from deprecated dpatch. > > Please let me know if an update is alredy being worked on, or if the > previous patch needs adjustments, or if there is anything that should > delay the NMU. > > Thanks Jari, Your work in much appreciated. cheers, sam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635685: libc6-dev-i386 problems
I'm having the same problem (missing headers when compiling with -m32). I did have libasound2-dev install and my /usr/include/sys is indeed not a symlink. Is there a workaround to get a working -m32? Where should /usr/include/sys point? (I've now uninstalled libasound2-dev). cheers, sam -- sam clegg :: s...@superduper.net :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#592649: gcc-4.4: seemingly incorrect behaviour with switch on out-of-range enum value
Package: gcc-4.4
Version: 4.4.4-8
Severity: important
Running the following code with gcc-4.4 will print "A" even though the
value of bar in is actually 64 at runtime.
The correct behaviour is surely to print "invalid bar"?
As you can see from the code, adding a default case changes the
behaviour which I find even more strange.
Looking at the asm it seems that gcc is making as assumsion that
bar must be in the valid range of the enum.
This problem does not exist in gcc-4.3
#include
enum foo
{
A = 0,
B = 1
};
int main()
{
foo bar = (foo)64;
switch (bar)
{
case A: printf("A\n"); return 0;
case B: printf("B\n"); return 0;
// uncomment this line to stop A being printed!
//default: break;
}
printf("invalid bar\n");
return 1;
}
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gcc-4.4 depends on:
ii binutils 2.20.1-13 The GNU assembler, linker and bina
ii cpp-4.4 4.4.4-8The GNU C preprocessor
ii gcc-4.4-base 4.4.4-8The GNU Compiler Collection (base
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libgcc1 1:4.4.4-8 GCC support library
ii libgomp1 4.4.4-8GCC OpenMP (GOMP) support library
Versions of packages gcc-4.4 recommends:
ii libc6-dev 2.11.2-2 Embedded GNU C Library: Developmen
Versions of packages gcc-4.4 suggests:
ii gcc-4.4-doc 4.4.4.nf1-1 documentation for the GNU compiler
pn gcc-4.4-locales(no description available)
ii gcc-4.4-multilib 4.4.4-8 The GNU C compiler (multilib files
pn libcloog-ppl0 (no description available)
pn libgcc1-dbg(no description available)
pn libgomp1-dbg (no description available)
pn libmudflap0-4.4-dev(no description available)
pn libmudflap0-dbg(no description available)
pn libppl-c2 (no description available)
pn libppl7(no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#568418: [pkg-mad-maintainers] Bug#568418: Bug#568418: libmad0-dev: mpg321 compilation errors in mips and mipsel architectures.
On Mon, 2010-02-08 at 19:53 +0100, Kurt Roeckx wrote: > On Thu, Feb 04, 2010 at 02:48:36PM -0500, Nanakos Chrysostomos wrote: > > Package: libmad0-dev > > Version: 0.15.1b-4 > > Severity: important > > Justification: fails to build from source > > > > The new mpg321 version 0.2.11-1 has recently been uploaded (aims to close > > many bugs and provide new features) but fails to compile to mips and mipsel > > architectures. > > The problem seems to be in mad_f_mul function which reports an impossible > > constraint error in 'asm'. > > Below is the link [0] of the buildd log file from the mips architecture. It > > is the same for the mipsel also. > > > > Thanks in advance, > > Chris. > > > > > > [0]: > > https://buildd.debian.org/fetch.cgi?pkg=mpg321&ver=0.2.11-1&arch=mips&stamp=1263279405&file=log > > > > Can someone please take a look at this? I have no clue about > mips assembler. Hmm.. me neither. Do you know if this used to work in the recent past? I'm assuming its possible to setup a qemu environment in order to debug this? Or would you use on the to debian mips machine? > > > Kurt > > > > > _______ > pkg-mad-maintainers mailing list > pkg-mad-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-mad-maintainers -- sam clegg :: s...@superduper.net :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#407749: please apply that patch
I really hope this patch gets applied sooner rather than later. I use tree a lot and have had problems with utf8 filenames. -- sam clegg :: s...@superduper.net :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#534029: Please find attached the patch
On Fri, 2009-10-09 at 22:02 +0200, Niels Thykier wrote: > Hi Sam Clegg > > Any news or ETA on this one? It is almost a month ago you said you would > apply the patch from Onkar Shinde (which will also fix #548810). Thanks for the nudge Niels. My laptop was destroyed recently but with my new one just arrived I'm sure I can upload today. > > Thank you in advance, > ~Niels > -- sam clegg :: s...@superduper.net :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#534029: Please find attached the patch
Thanks Onkar. All changes look great. will apply and upload. On Fri, 2009-09-11 at 10:55 +0530, Onkar Shinde wrote: > Please find attached the patch that fixes this bug and improves the > packaging in general. > > > Cheers, > Onkar -- sam clegg :: s...@superduper.net :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#425609: opengrok
Are you planning on uploading this (at least to non-free?). I'm using it and would love a packaged version. Do you have preview of your package on the net somewhere? -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#425609: opengrok
Are you planning on uploading this (at least to non-free?). I'm using it and would love a packaged version. Do you have preview of your package on the net somewhere? -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#425609: opengrok
Are you planning on uploading this (at least to non-free?). I'm using it and would love a packaged version. Do you have preview of your package on the net somewhere? -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#369010: patch to enable C# support
tags 369010 patch
thanks
Here is a patch that enables CLI support and creates a new
libantlr2.7-cil packages.
This package installs the antlr dll files in the mono GAC at install
time and (I think) conforms to the debian CLI policy.
I've also used dh_install and dh_link to build this extra package.
Hope thats ok.
--
sam clegg
:: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369
$superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $
diff -Nurb antlr-2.7.7/debian/antlr-cil-2.7.pc antlr-2.7.7.new/debian/antlr-cil-2.7.pc
--- antlr-2.7.7/debian/antlr-cil-2.7.pc 1970-01-01 01:00:00.0 +0100
+++ antlr-2.7.7.new/debian/antlr-cil-2.7.pc 2008-01-19 13:21:02.0 +
@@ -0,0 +1,8 @@
+prefix=/usr
+exec_prefix=${prefix}
+libdir=${prefix}/lib/cli/antlr-2.7
+
+Name: Antlr
+Description: language tool for constructing recognizers, compilers etc
+Version: 2.7
+Libs: -r:${libdir}/antlr.runtime.dll -r:${libdir}/antlr.astframe.dll
diff -Nurb antlr-2.7.7/debian/antlr.snk.uue antlr-2.7.7.new/debian/antlr.snk.uue
--- antlr-2.7.7/debian/antlr.snk.uue 1970-01-01 01:00:00.0 +0100
+++ antlr-2.7.7.new/debian/antlr.snk.uue 2008-01-19 12:34:34.0 +
@@ -0,0 +1,17 @@
+begin 644 antlr.snk.uue
+M!P(D``!24T$R``0``!$```"_&Y7B2L#1&)Q;47.U2+]3=?2V!EK^_?U[
+M^1L]'<]N!L-)*7!66*)[X_%>H[$,:>W00EW)W$8]8EC\'@`E$T.""`-9#H)X
+MV8B&_FB3K#R(\+'TATB;[EMAIL PROTECTED]"E^I*4F=F5BE=!7UXSRZN4T7(H?ARY>L1Z
+M7X-3X[K72E+&H'V-JI$;FO9+%.`?:W7L(3[V5X[/1\BI'CL+=$Y?'N?
[EMAIL PROTECTED]"7P#H];EON(9&_\BTQ\!>8=D(I0"EEUT5:*SS3GP
[EMAIL PROTECTED]"[O;6$FKA,>VV%7EXGT1[[^<(L=2/_\\\O?MW[+PUD_B5`DIP\&W)
+M`<,9&)C8,;NR;8'G5H2U
+MQH0O'4P7R>HL"/>[EMAIL PROTECTED]@`
+`
+end
diff -Nurb antlr-2.7.7/debian/changelog antlr-2.7.7.new/debian/changelog
--- antlr-2.7.7/debian/changelog 2008-01-19 13:21:57.0 +
+++ antlr-2.7.7.new/debian/changelog 2008-01-19 12:35:12.0 +
@@ -1,3 +1,12 @@
+antlr (2.7.7-3) unstable; urgency=low
+
+ * enable building of cshart libs. Closes: #369010
+- add antrl.snk.uue key for signing CLI assemblies
+- use dh_installcligac to install assembiles in the GAC
+- replace \ with / in nant build file
+
+ -- Sam Clegg <[EMAIL PROTECTED]> Sat, 19 Jan 2008 12:35:09 +
+
antlr (2.7.7-2) unstable; urgency=low
* Removed Build-Depends pn libgcj-dev. Closes: #359727
diff -Nurb antlr-2.7.7/debian/control antlr-2.7.7.new/debian/control
--- antlr-2.7.7/debian/control 2008-01-19 13:21:57.0 +
+++ antlr-2.7.7.new/debian/control 2008-01-19 12:35:58.0 +
@@ -3,9 +3,8 @@
Priority: optional
Maintainer: Debian Java Maintainers <[EMAIL PROTECTED]>
Uploaders: Arnaud Vandyck <[EMAIL PROTECTED]>, John Leuner <[EMAIL PROTECTED]>, Michael Koch <[EMAIL PROTECTED]>, Barry Hawkins <[EMAIL PROTECTED]>
-Build-Depends: debhelper (>= 4), java-gcj-compat-dev, gcj, python, autotools-dev, python-all-dev (>= 2.3.5-11)
+Build-Depends: debhelper (>= 4), java-gcj-compat-dev, gcj, python, autotools-dev, python-all-dev (>= 2.3.5-11), nant, mono-mcs (>= 1.0) | c-sharp-compiler, sharutils
Build-Depends-Indep: python-support (>= 0.3)
-Build-Conflicts: mono-jit
Standards-Version: 3.7.3
Package: antlr
@@ -38,6 +37,18 @@
.
These are the static libraries for C++.
+Package: libantlr2.7-cil
+Section: libdevel
+Architecture: any
+Recommends: antlr
+Description: language tool for constructing recognizers, compilers etc
+ ANTLR, ANother Tool for Language Recognition, (formerly PCCTS) is
+ a language tool that provides a framework for constructing recognizers,
+ compilers, and translators from grammatical descriptions containing C++
+ or Java actions [You can use PCCTS 1.xx to generate C-based parsers].
+ .
+ This package contains the C# (CLI) libraries.
+
Package: cantlr
Section: devel
Architecture: any
diff -Nurb antlr-2.7.7/debian/libantlr2.7-cil.dirs antlr-2.7.7.new/debian/libantlr2.7-cil.dirs
--- antlr-2.7.7/debian/libantlr2.7-cil.dirs 1970-01-01 01:00:00.0 +0100
+++ antlr-2.7.7.new/debian/libantlr2.7-cil.dirs 2008-01-19 12:34:34.0 +
@@ -0,0 +1 @@
+usr/lib/antlr-2.7
diff -Nurb antlr-2.7.7/debian/libantlr2.7-cil.install antlr-2.7.7.new/debian/libantlr2.7-cil.install
--- antlr-2.7.7/debian/libantlr2.7-cil.install 1970-01-01 01:00:00.0 +0100
+++ antlr-2.7.7.new/debian/libantlr2.7-cil.install 2008-01-19 13:03:04.0 +
@@ -0,0 +1,3 @@
+debian/antlr-cil-2.7.pc /usr/lib/pkgconfig
+lib/antlr.astframe.dll /usr/lib/cli/antlr-2.7
+lib/antlr.runtime.dll /usr/lib/cli/antlr-2.7
diff -Nurb antlr-2.7.7/debian/libantlr2.7-cil.installcligac antlr-2.7.7.new/debian/libantlr2.7-cil.installcligac
--- antlr-2.7.7/debian/libantlr2.7-cil.installcligac 1970-01-01 01:00:00.0 +0100
+++ antlr-2.7.7.new/debian/libantlr2.7-cil.installcligac 2008-01-19 12:
Bug#458835: Breaks ABI with 0.8.0
On Thu, 2008-01-03 at 08:27 +0100, Sebastian Dröge wrote: > Package: boo > Version: 0.8.0.2730-1 > Severity: grave > > Hi, > boo 0.8.0 breaks ABI compared to the older versions and depending > packages, like banshee, fail to load the boo assemblies after an > upgrade. > > Please package the runtime libraries in a new, versioned binary package > or provide policy assemblies if only the assembly version has changed > and the ABI itself is in fact compatible. Sorry, I should have run apt-rdepends and tested banshee before uploading this version. I'm working on a solution right now. Most likely I will re-upload boo from the boo1 sources and create boo2 packages with seperate libbooX-cil and booX packages. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#454066: boo: new upstream versions 0.7.8, 0.7.9 and 0.8.0 available
On Sun, 2007-12-02 at 21:22 +0100, Mirco Bauer wrote: > Package: boo > Severity: wishlist > > Dear boo package maintainer, > > There are new upstream versions [0][1][2] of boo available. > One of my packages [3] need a newer version of boo in a new upstream > version. Please update boo to a new version, as it blocks my package > update [4] from entering debian. Sorry for the delay. I was planning on updating boo, but the last time I looked I think support for the mono 1.x was dropped, so only the 2.x packages can be made now. However, this is no reason not to upgrade so I will do so ASAP. > > If you don't have time to update boo, I am available to help via a NMU. > > [0] http://docs.codehaus.org/display/BOO/2007/06/23/Boo+0.7.8+is+Here%21 > [1] http://docs.codehaus.org/display/BOO/2007/09/01/Boo+0.7.9 > [2] http://docs.codehaus.org/display/BOO/2007/10/27/Boo+0.80 > [3] http://packages.qa.debian.org/m/monodevelop.html > > PS: I would like to see boo packaged part of pkg-cli-libs [4][5] in a > team fashion, if you are interested please tell me. > > [4] http://alioth.debian.org/projects/pkg-cli-libs/ > [5] http://svn.debian.org/wsvn/pkg-cli-libs/packages/ Sure, I think that probably makes sense. I'll do this with my next upload. Is the process more complicated than simply updating the maintainer field? I'll read up the website and hopefully get this done next week. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#450964: boo: typo in long description
On Mon, 2007-11-12 at 19:39 +0100, arno renevier wrote:
> Package: boo
> Severity: minor
>
> Hi,
> Long description of boo package tells:
>
> "The boo compiler and the programs it produces are 100% CIL and can be run on
> any compliant CLI virtual machine"
>
> I suppose it's a typo, and CIL should be replaced with CLI.
> If it's not a typo, it would be nice to explain what CIL means
Actually its not a typo but it may not be a perfect description.
CIL is "Common intermediate language", its the binary code format
produced when compiling, for example, C# or boo.
A CLI ("common language infrastructure") VM is one that run CIL
programs.
Does that made sense? Do you think I should expand these acronyms in
the description?
>
> arno.
>
> -- System Information:
> Debian Release: lenny/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.22custom
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages boo depends on:
> pn libmono-corlib1.0-cil (no description available)
> pn libmono-system1.0-cil (no description available)
> pn libmono1.0-cil (no description available)
> pn libmono2.0-cil (no description available)
> pn mono-runtime (no description available)
>
> boo recommends no packages.
>
>
signature.asc
Description: This is a digitally signed message part
Bug#407253:
Ok, my ITP was a dup of this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448756 I'm still happy to package this if nobody else has come forward. My packages are good to go already. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#448756: ITP: dmucs -- distributed compilation system for use with distcc
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: dmucs Version : 0.6.1 Upstream Author : Victor Norman <[EMAIL PROTECTED]> * URL : http://dmucs.sourceforge.net/ * License : GPL Programming Lang: C Description : distributed compilation system for use with distcc DMUCS is a system that allows a group of users to share a compilation farm. Each compilation request from each user will be sent to the fastest available machine, every time. The system has the following features: * Supports multiple users compiling simultaneously, and scales well to handle the new loads. * Supports multiple operating systems in the compilation farm. * Uses all processors of a multi-processor compilation host. * Makes best use of compilation hosts with widely differing CPU speeds. * Guarantees that a compilation host will not be overloaded by compilations. * Takes into account the load on a host caused by non-compilation tasks. * Supports the dynamic addition and removal of hosts to the compilation farm. * Works with distcc, which need not be altered in any way. You can get my initial package from here: http://superduper.net/downloads/debian/dmucs_0.6.1-1_i386.deb -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445866: ITP: perforce -- closed source revision control system
On Mon, 2007-10-08 at 14:42 -0700, Tyler MacDonald wrote: > Florian Weimer <[EMAIL PROTECTED]> wrote: > > Seems to me that this depends on Perforce. D'oh. > > > > (I don't know anything about Perforce. Perhaps it's really dangerous > > software. But perhaps it's just non-free.) > > Perforce is an absolutely *excellent* VCS with the unfortunate > distinction of being proprietary. SubVersion can do most (but not all) of > what it does, albeit 10 times slower. Still, I've migrated all of my stuff > over to subversion, because, well, subversion is free. Perforce is free (as > in "free beer") for open source developers, if you want more than 2 users on > one VCS server, you have to sign a contract, get a license, give the > perforce people full access to your repo, sign a new contract whenever you > server's IP address changes, and renew each year Slightly off topic, but you don't need to give the perforce people access to you repo (unless you really want them to come in a fix something) and you don't need to renew each year (unless you want support from them). signature.asc Description: This is a digitally signed message part
Bug#445866: ITP: perforce -- closed source revision control system
On Tue, 2007-10-09 at 05:41 +0300, Faidon Liambotis wrote: > Daniel Jacobowitz wrote: > > On Mon, Oct 08, 2007 at 03:41:21PM -0400, Roberto C. S?nchez wrote: > >> Given the great abundance of revision control systems already packaged > >> for Debian, what is the point of adding another? Especially when it is > >> non-free. > > > > How about "people use it"? There's plenty of installations of > > perforce; I think making it easier to use Debian with them is > > within the mandate for non-free. > I'd say upload only the client to non-free. > > We should provide users a way to use their existent preforce servers but > we should not encourage new installations of perforce. > > Sounds like a compromise to me :) Indeed, my primary aim was to make it easy for anyone wanting to run debian in an org that uses perforce (i.e. people like myself). I agree the server package is of less use in this respect, its simply there to make it easy for people to choose debian on the server side as well. Pending the legal conclusions I'll upload just the client package initially. signature.asc Description: This is a digitally signed message part
Bug#445866: ITP: perforce -- closed source revision control system
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: perforce Version : 2007.2-2 Upstream Author : Perforce Inc. <[EMAIL PROTECTED]> * URL : http://www.perforce.com/ * License : proprietary Programming Lang: binary only (with bindings in Perl, Python, etc.) Description : closed source revision control system closed source, centralised source control system akin to CVS and subversion. You'll need a license to run a server with more than two users. Free licenses are granted to open source projects. I'm in talks with perforce to get explicit permission to distribute in non-free. Current license discussions are here: http://lists.debian.org/debian-legal/2007/09/msg00184.html My packages are here: http://superduper.net/downloads/debian/ I've created two packages: 'perforce' for the client and 'perforce-server' for the server. The 'perforce-server' package is a 'fat' package that contains many server binaries (since the users license if normally limited to a given version). The server package contains debian-friendly init scripts, etc. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334681: very annoying dependancies.
This is really quite annoying. I just needed to install unixodbc-dev on a build machine. This machine only does compilation, nothing else. Why does this package then force me to install and extra 8 megs for libqt3-mt? I really don't see why this can't be split out into unixodbc-admin or some such. What has QT got to do with the fact taht I want compile against sql.h? signature.asc Description: This is a digitally signed message part
Bug#436239: [pkg-mad-maintainers] Bug#436239: Bug#436239: Bug#436239: libid3tag0-dev: header file "/usr/include/id3tag.h" does not contain definition for struct id3_file altough it references it
On Mon, 2007-08-06 at 21:31 +0200, Kurt Roeckx wrote:
> On Mon, Aug 06, 2007 at 04:07:51PM +0100, Sam Clegg wrote:
> > Looks to me like this is an opaque data type. Its only ever referenced
> > as a pointer type so the user of the API never needs to know what the
> > layout of the type really is.
>
> So just add a "struct id3_file;" at the top of the file somewhere.
The should be no need for this even.
You can use pointers to structs without declaring them ahead of time.
$ cat > main.cpp
struct i3d_file* bar()
{
return 0;
}
int main()
{
struct i3d_file* a = bar();
return 0;
}
$ make main
g++ main.cpp -o main
$
signature.asc
Description: This is a digitally signed message part
Bug#436239: [pkg-mad-maintainers] Bug#436239: libid3tag0-dev: header file "/usr/include/id3tag.h" does not contain definition for struct id3_file altough it references it
On Mon, 2007-08-06 at 15:07 +0200, Folkert van Heusden wrote: > Package: libid3tag0-dev > Version: 0.15.1b-10 > Severity: normal > > > See subject > libid3tag0-dev: header file "/usr/include/id3tag.h" does not contain > definition for struct id3_file altough it references it > > [EMAIL PROTECTED]:~/Personal/src/acpitail$ grep id3_file > /usr/include/id3tag.h | grep -v "^enum id3_file_mode" > struct id3_file *id3_file_open(char const *, enum id3_file_mode); > struct id3_file *id3_file_fdopen(int, enum id3_file_mode); > int id3_file_close(struct id3_file *); > struct id3_tag *id3_file_tag(struct id3_file const *); > int id3_file_update(struct id3_file *); > > as you can see some functions require this structure but it is not defined > anywhere Looks to me like this is an opaque data type. Its only ever referenced as a pointer type so the user of the API never needs to know what the layout of the type really is. signature.asc Description: This is a digitally signed message part
Bug#435808: incorrect jar contents (proguard/proguard/ hierarchy)
On Fri, 2007-08-03 at 12:25 +0200, Hans van Kranenburg wrote: > Package: proguard > Version: 3.7-1 > Severity: normal > Tags: patch > > > While using the proguard 3.7 source package to build a deb of proguard 4.0 > beta5 I discovered the proguard.jar and ant-proguard.jar files contain > an incorrect directory hierarchy: > > $ jar tvf /usr/share/java/proguard.jar | head > 0 Sat Jan 13 12:50:24 CET 2007 META-INF/ > 30 Sat Jan 13 12:44:36 CET 2007 META-INF/MANIFEST.MF > 0 Sat Jan 13 12:50:24 CET 2007 proguard/ > 0 Sat Jan 13 12:50:22 CET 2007 proguard/proguard/ > ^^ > 0 Sat Jan 13 12:50:22 CET 2007 proguard/proguard/shrink/ > 2927 Sat Jan 13 12:50:22 CET 2007 proguard/proguard/shrink/Shrinker.class > 19710 Sat Jan 13 12:50:22 CET 2007 proguard/proguard/shrink/UsageMarker.class > > The attached patch should fix this. Hmm, thanks for that. Any idea why this wasn't breaking proguard? signature.asc Description: This is a digitally signed message part
Bug#428611: boo: can't compile HelloWorld
On Wed, 2007-06-13 at 14:09 +0530, Kartik Mistry wrote: > Hi, > > In my case it works, without any problems! Indeed, works for my just fine on sid. Will try etch just to be sure. signature.asc Description: This is a digitally signed message part
Bug#426591: ide-cs segfaults insmod on load
I think this is a dup of #425458. Seems that insmod upstream has a segfault. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: This is a digitally signed message part
Bug#425112: [pkg-mad-maintainers] Bug#425112: madplay on sgi mips64 big endian
On Sat, 2007-05-19 at 10:15 +0200, Gürkan Sengün wrote: > Package: madplay > Version: 0.15.2b-4 > Severity: important > > madplay somevalid.mp3 just plays noise on my > indigo2. mpg321 gets it right. > > $ uname -a > Linux mips 2.6.20-1-r4k-ip22 #1 Tue Apr 24 23:33:09 UTC 2007 mips64 > GNU/Linux > Sounds like a potential endianess or wordsize issue. Probably for former as I'm sure we would know about it if madplay didn't work on other 64-bit archs. Is your machine littlendian? Has anyone else had experience using madplay in a littleendian archs?
Bug#423009: proguard: Adding Ant ProGuardTask to default package
On Wed, 2007-05-09 at 14:18 +0200, Emmanuel Fleury wrote:
> Package: proguard
> Version: 3.7-1
> Severity: wishlist
>
> As Ant is a required for the build-deps why wouldn't you add the support
> for the Ant Task for proguard (patch attached):
>
> --- proguard-orig/proguard-3.7/debian/rules 2007-05-09
> 12:37:48.0 +0200
> +++ proguard/proguard-3.7/debian/rules 2007-05-09 11:47:45.0 +0200
> @@ -13,6 +13,7 @@
> mkdir -p build
> mkdir -p lib
> ${JAVA_COMPILER} -d build/proguard -sourcepath src
> src/proguard/ProGuard.java
> + ${JAVA_COMPILER} -d build/proguard -sourcepath src -classpath
> /usr/share/ant/lib/ant.jar src/proguard/ant/ProGuardTask.java
> ${JAVA_COMPILER} -d build/retrace -sourcepath src
> src/proguard/retrace/ReTrace.java
> ${JAVA_COMPILER} -d build/proguardgui -cp build/proguard
> -sourcepath src src/proguard/gui/ProGuardGUI.java
> ${JAVA_COMPILER} -cp /usr/lib/java/ant-1.6.jar -d build
> -sourcepath src src/proguard/gui/ProGuardGUI.java
Sure.. I don't see why not
signature.asc
Description: This is a digitally signed message part
Bug#415526: python-cherrypy3: shouldn't the tuturial be in /usr/share/doc
Package: python-cherrypy3 Version: 3.0.0-1 Severity: wishlist It seems to me that the tutorial code should live in /usr/share/doc rather than /usr/share/python-support/python-cherrypy3/cherrypy/tutorial/ I could be wrong but thats where I expected to find it. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-cherrypy3 depends on: ii python2.4.4-2An interactive high-level object-o ii python-support0.5.6 automated rebuilding support for p python-cherrypy3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409387: apt-cross -u seems to be calling apt-get with incorrect arguments
Package: apt-cross Version: 0.0.5 Severity: important Line 380 of apt-cross seems to contain an incorrect invokation of apt-get. Seems to be passing "-update" rather than "update". On my system (if I remove the 2>&1) I get the following error: E: Command line option ‘p’ [from -update] is not known. Also, with the 2>&1 at the end of the line I don't see any output about the failure, since $result is never used. Also, there is a comment about using fakeroot but fakeroot does not seem to be used, which mean that "-u" requires root privs (which I guess it shouldn't). Aside from that apt-cross has saved me a lot of time. Thank you very much for such a useful tool! -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages apt-cross depends on: ii apt 0.6.46.4 Advanced front-end for dpkg ii binutils 2.17-3 The GNU assembler, linker and bina ii dpkg-cross1.34 tools for cross compiling Debian p ii dpkg-dev 1.13.25package building tools for Debian ii fakeroot 1.5.12 Gives a fake root environment ii libfile-homedir-perl 0.56-1.1 Get the home directory for yoursel ii libwww-perl 5.805-1WWW client/server library for Perl ii sudo 1.6.8p12-4 Provide limited super user privile apt-cross recommends no packages. -- no debconf information
Bug#393645: boo: FTBFS: 'Boo.Lang.Compiler.Steps.EmitAssembly': 'Object reference not set to an instance of an object'
This looks like it might be a CLR version issue. I notice in the AMD64 buildlog: [exec] Boo Compiler version 0.7.6.2237 (CLR v2.0.50727.42) Whereas on my x86 system: [exec] Boo Compiler version 0.7.6.2237 (CLR v1.1.4322.2032) I don't know how the 2.0 version of the CLR is being reported since it looks like all the mono packages being install are CLR1, eg: Unpacking mono-jit (from .../mono-jit_1.1.17.1-5_amd64.deb) ... -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#356791: xmms-mad: build bmp-flac
On Tue, Mar 14, 2006 at 02:11:01AM -0300, Rog??rio Brito wrote: > Package: xmms-mad > Severity: wishlist > > Please, would it be possible to have a mad (say, bmp-mad) plugin for > users of the "new generation" xmms, beep-media-player? > > I'm asking this because I'm leaving xmms unused and trying to migrate to > beep-media-player. One of the most important packages has already been > packaged, namely, beep-crossfade. > > I hope that yours soon becomes available for users. > > > Thanks, Rog?rio Brito. I'll certainly look into it. Its the first I've heard of BMP but if its API is similar I don't see why it shouldn't be an easy port. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#382700: CLR 1.1 vs 2.0 mess
On Sat, Aug 12, 2006 at 08:47:55PM +0200, Mirco Bauer wrote: > first I thought the compiler is broken, but then I saw CLR v2.0 which > means _bad_ things. > > I installed libmono2.0-cil which pulls the base CLR 2.0 packages in, and > then booc didn't fail with that error, but with another saying the libs > are not found. They libs are installed though, but since boo uses now > CLR 2.0 it wants the 2.0 version of those libs (instead of 1.1 as > before). > > So I installed the 2.0 versions, and the build was happy, but I am not. > > The resulting package depends on on the 2.0 runtime of Mono, because the > compiler linked it against 2.0 instead of 1.1 > Unluckily this is a problem now. > > I could add now the 2.0 stuff to monodevelop build deps but that is not > fixing the cause. Boo must be able to link against 1.1 or 2.0 somehow, > else all resulting libs or apps require 2.0 from now on. > > C# solved this by having mcs (C# 1.0) which links against CLR 1.1 and > gmcs (C# 2.0) which links against CLR 2.0 > > Also I noticed that boo is not correctly fetching the binary > dependencies with dh_clideps, but I guess that must be some CDBS problem > since no other package has the problem. Probably is the make target too > early or too late or something. Then you would not need to manually > depend on mono (which is btw a bad idea since its a meta-package with 2 > real deps). Well, to be honest, I only switched to gmcs (and therefore 2.0) because it seemed to be the default way for nant to build boo. I had a bug where nant failed to find gmcs. If you think its not a good time to be switching to 2.0 i'll look at ways of switching back or providing 2 version of boo, one built against 1.1 and other build againt 2.0. I suspect that the former will be good enough for now. I'll make sure I can build monodevelop before uploading. I'll certainly look into the dh_clideps problem, too. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#382700: more info
On Sun, Aug 13, 2006 at 07:08:54PM +0200, Mirco Bauer wrote: > Ok after more investigation and some talk with lluis the head of > MonoDevelop, I found that upstream boo is _not_ using 2.0 by default > now. > > The cause of the 2.0 change is nant, nant was built using 2.0 and thus > automagicly picks 2.0 as profile when building an application using > nant. And boo uses nant. > > So either boo should override the profile using -t:mono-1.0 or nant > should be fixed/patches to not use the 2.0 profile by default. Thanks for the info. I think I just do the former, and perhaps mail the nant maintainer to see what he thinks about the later. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#380132: Patch for RC bug
On Fri, Aug 04, 2006 at 12:01:35AM +0200, Arjan Oosting wrote: > tag 380132 patch > thanks > > I have prepared a patch which solves the FTBFS. The patch is attached. > > Greetings Arjan Thanks Arjan, but I already uploaded a fix for this bug (Looks like its in unstable as I write). cheers, -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#381138: FTBFS: error: ODBC header files and/or libraries not found
On Wed, Aug 02, 2006 at 03:49:26PM +0200, Roberto Pariset wrote: > Package: sqliteodbc > Version: 0.69-1 > Severity: serious > > Hi, > sqliteodbc_0.69-1 FTBFS with the following error: > > checking for sqlite_trace in -lsqlite... yes > checking for SQLite3 header and library... no > configure: warning: SQLite3 header files and/or library not found > checking for sqlite3_column_table_name in -lsqlite3... no > checking for ODBC headers and libraries... no > configure: error: ODBC header files and/or libraries not found > make: *** [config.status] Error 1 Oops, looks like i missed a build-depend. Will fix ASAP. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#380190: ITP: sqliteodbc -- ODBC driver for SQLite embedded database
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: sqliteodbc Version : 0.69 Upstream Author : Christian Werner <[EMAIL PROTECTED]> * URL : http://www.ch-werner.de/sqliteodbc/ * License : BSD-style Programming Lang: C Description : ODBC driver for SQLite embedded database This package allows you to connect to an SQLite database using ODBC, the Open Database Connectivity abstraction layer which is understood by a variety of database tools that may not be able to talk to SQLite directly. Experimental pacakge here: http://superduper.net/downloads/debian/libsqliteodbc_0.69-1_i386.deb Sources here: http://superduper.net/downloads/debian/sources/ (Include the long description here.) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334681: depends vs. reccomends
I'm afraid I have to agree here that there should be a GUI-free dev package available. I'm building DB applications against unixodbc on several headless servers and have no need of GUI tools to end the .ini files. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#368001: removing boo.lang
Sorry for the delay removing boo.lang. I'm about to upload a new 7.6 package that fixes this bug. cheers, sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: Digital signature
Bug#360115: should be architecture-independent
Peter Eisentraut wrote: > Package: proguard > Severity: normal > > This package does not seem to contain any architecture-specific components > and should therefore be "Architecture: all" (not "any"). > Hmm.. thanks for spotting that. How on earth did that happen! -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ signature.asc Description: OpenPGP digital signature
Bug#317710: boo: Missing dependency?
Mattia Belletti wrote: Package: boo Version: 0.7.5.2013-1 Followup-For: Bug #317710 I just installed the boo package, and when I lauch it against a simple boo source file I correctly get: [EMAIL PROTECTED]:~/prog/boo$ booi es1.boo env: /usr/bin/mono: No such file or directory [EMAIL PROTECTED]:~/prog/boo$ Just because the boo package doesn't bring in a package which installs the mono binary. Shouldn't do it? I think you're right. I can't see much use for boo without mono. Adding mono to Depends now. Thanks sam. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#287519: [pkg-mad-maintainers] Bug#287519: libmad assertion failure, repost
Justin Pryzby wrote: > Hello *, > > I wanted to bring your attention to a libmad assertion failure > experienced through mpg321. The bug report is at: > http://bugs.debian.org/287519 > > Glenn Maynard previously posted the problem to this list, but got no > response, so I wanted to send another ping since the problem still > exists. I'll try and reproduce this today and see if I can suggest a reasonable fix. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.13 2003/06/17 10:29:24 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348999: i had the same problem
I saw the same issue. Seems to be related to avahi-daemon. I stopped it and banshee started just fine. Strangly, once I started it again banshee was still able to start, so perhaps this is a workaround. Shame I can no longer reproduce it though :( sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340713: another one
I also have a bug showing as outstanding that isn't: #338355 -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340127: progress on this bug ? -- boo: New version doesn't work
Justin Pryzby wrote: Has there been any progress on this bug? http://bugs.debian.org/340127 Sorry no. I will try and deal with in on the 4th of Jan. Seems strange that the offiicial binary doesn't work either. I'll ask on the boo list if I don't find anything in the archives. cheers, sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#253735:
Any progress on getting this package into debian? I use it on several machines and it would be really useful. Also the unofficial package that I was using seems to have disappeared from http://debian.usefulinc.com/ If I can help then please let me know. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#329454: broken symlinks "/usr/bin/boo*"
H B wrote:
> Package: boo
> Version: 0.6.0.1858-1
> Severity: grave
> Justification: renders package unusable
>
> After installing boo with "apt-get -t unstable install boo" the expected
> executables "booi" and "booc" in "/usr/bin" are just broken symlinks
> to "cli-wrapper"
> which seems to be a file in package mono-common. mono-common isn't
> listed as a dependency of boo. Installing "mono-common"
> didn't seem to render the package useful. "booi
> .boo" didn't do anything.
OK, so mono-common needs to be a dependancy. But aside from that
booi seems to be working for me:
$ which booi
/usr/bin/booi
$ booi /usr/share/doc/boo/examples/xml.boo
http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
Homer
Simpson
Al. Foo
35
Al.Bar
14
Simpson, Homer
35, Al. Foo
14, Al.Bar
What is the output you get from running this?
--
sam clegg
:: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369
$superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#326434: proguard: Please Build-Depend on ant instaed of libant1.6-java
Michael Koch wrote: > Package: proguard > Severity: normal > > Please Build-Depend on ant instead of libant1.6-java to help with the > ant transition in Debian. libant1.6-java will get removed from the > archive soon as ant supplies everything needed. Please use > /usr/share/ant and not /usr/share/ant1.6 as ANT_HOME. > > > Michael Thanks for the heads up michael. Combined this with the new upstream release I just uploaded. sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317134: invalid boo.pc
Mirco Bauer wrote: > Package: boo > Severity: serious > > The included boo.pc in 0.5.6.1701-1 has an invalid prefix, it's set > to /usr/local which should be /usr. > This breaks compiling programs against boo (like MonoDevelop). > Thanks. Will fix ASAP. sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#316738: missing files (boo.pc and boo.lang)
OK, I'm about to upload a new upstream version and include those two files. Also, I've added the strings.resources. I'm not sure where the boo Nant dll should be installed. Presumably not in the GAC but in some Nant directory. Perhaps I should revert to using "nant install" rather than list everything in debian/install. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ signature.asc Description: OpenPGP digital signature
Bug#314639: proguard: FTBFS: jar: Command not found
Andreas Jochens wrote: > Package: proguard > Version: 3.2-2 > Severity: serious > Tags: patch > > When building 'proguard' in a clean chroot on amd64/unstable, > I get the following error: > > debian/rules binary > mkdir -p build > mkdir -p lib > jikes-classpath +E +Z0 -d build/proguard -sourcepath src > src/proguard/ProGuard.java > jikes-classpath +E +Z0 -d build/retrace -sourcepath src > src/proguard/retrace/ReTrace.java > jikes-classpath +E +Z0 -d build/proguardgui -cp build/proguard -sourcepath > src src/proguard/gui/ProGuardGUI.java > jikes-classpath +E +Z0 -cp /usr/lib/java/ant-1.6.jar -d build -sourcepath src > src/proguard/gui/ProGuardGUI.java > jar cfm lib/proguard.jar proguard.manifest -C build proguard > make: jar: Command not found > make: *** [binary-indep] Error 127 > Thanks for the patch. I just uploaded a new version that build-depends on fastjar. However I was assuming that fastjar provided the 'jar' command. Looks like i'll still need anther upload that uses the fastjar command explicitly. cheers, sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312024: proguard: ftbfs [sparc] cannot stat `./lib/proguard.jar': No such file or directory
Blars Blarson wrote: > Package: proguard > Version: 3.2-1 > Severity: serious > Tags: sid > Justification: fails to build from source > > proguard fails to build from source on sparc and all other buildds, > duplicated on sparc pbuilder. > > > dh_install -pproguard > cp: cannot stat `./lib/proguard.jar': No such file or directory > dh_install: command returned error code 256 > make: *** [binary-install/proguard] Error 1 > > I think this was fixed in an upload I made this morning. -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ signature.asc Description: OpenPGP digital signature
Bug#311942: python-tunepimp: no python2.4 package
Package: python-tunepimp Version: 0.3.0-3 Severity: wishlist Clearly this is a wishlist bug. I would like to use python-tunepimp with python2.4. Would it be difficult to add support for this? -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-tunepimp depends on: ii python2.3.5-2An interactive high-level object-o ii python2.3-tunepimp0.3.0-3libtunepimp Python 2.3 bindings -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310311: [pkg-mad-maintainers] Bug#310311: lost versioned shlibs in new version
Kurt Roeckx wrote: > tags 310311 + pending > thanks > > On Mon, May 23, 2005 at 02:16:04AM +0200, Frank Lichtenheld wrote: > >>Package: libmad >>Severity: serious >>Tags: sid >> >>Since version 0.15.1b-2, libmad0 has an unversioned shlibs. I guess >>this is an unintentional change during the conversion to cdbs? > > > Fixed in CVS. > > Sam, can you please upload the fixed libmad and libid3tag? > > It seems libid3tag's shlibs was set to 0.15.0b before the > conversion to cdbs (so the verison in sarge) while it should have > been 0.15.1b since the API was extended in 0.15.1b. > > Is that something that should get fixed in sarge? > > > Kurt Sorry kurt, i've been away for a few days in Paris (should have notified debian, i know). Will do the upload today. sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310634: libevent-dev: README.Debian contains out of date and incorrect information
Package: libevent-dev Version: 1.0b-1.1 Severity: minor The README.Debian is misleading: " Currently, libevent supports kqueue(2) and select(2). Support for poll(2) and /dev/poll is planned. " Also, "libevent - an asynchronous event notification library" Is libevent "asynchronous"? the website no longer claims this. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-iw3d Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages libevent-dev depends on: ii libevent1 1.0b-1.1 An asynchronous event notification -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310267: python-eyed3: would be great to support multiple python versions
Package: python-eyed3 Version: 0.6.5-1 Severity: wishlist Any chance of supporting multiple python versions. I would like a 2.4 package, for example. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-eyed3 depends on: ii python2.3.5-2An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#310044: ITP: proguard -- java class file shrinker, optimizer, and obfuscator
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: proguard Version : 3.2 Upstream Author : Eric Lafortune <[EMAIL PROTECTED] * URL : http://proguard.sourceforge.net/ * License : GPL Description : java class file shrinker, optimizer, and obfuscator ProGuard is a free Java class file shrinker, optimizer, and obfuscator. It can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions. Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer. This package builds just with jikes-classpath and runs with kaffe which are both in main. My provisional packages are available here: http://people.debian.org/~samo/experimental/ There is an archived ITP for proguard from over a year ago and I have checked with the original filer that he is no longer interested in this package. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309184: rar: Does not report error type when extracting files
Package: rar Version: 3.30-2 Severity: wishlist When "rar e" fails to write to or create an output file it does not give the reason. It simply outputs "Cannot create" or "Error writing" without telling you, for example, if you have no disk space or a permissions issue. I had to run it through strace to see the error code from write(2). Just a minor issue, clearly, but annoying none the less. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages rar depends on: ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libgcc11:4.0-0pre5 GCC support library ii libstdc++5 1:3.3.6-3.0.1 The GNU Standard C++ Library v3 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#304948: ITP: boo -- a python-like language and compiler for the CLI
Package: wnpp Severity: wishlist Owner: Sam Clegg <[EMAIL PROTECTED]> * Package name: boo Version : 0.5 Upstream Author : Rodrigo B. de Oliveira <[EMAIL PROTECTED]> * URL : http://boo.codehaus.org/ * License : Custom. DFSG Compatible. Description : a python-like language and compiler for the CLI Boo is considered ready for general usage and runs fine on mono. In fact mono its the primary target platform. The licence is custom but looks DFSG compatible. My initial boo package is here: http://people.debian.org/~samo/experimental/ Long Description: Boo is an object oriented statically typed programming language for the Common Language Infrastructure (CLI) with a Python inspired syntax and a special focus on language and compiler extensibility. . This package includes the Boo libraries as well as a compiler, interpreter and interactive shell. The boo compiler and the programs it produces are 100% CIL and can be run on any compliant CLI virtual machine. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11-1-686-smp Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#300095: madplay -- MPEG audio player in fixed point
Looks like I just missed this one. I would also like to adopt this package. I use it a lot and already maintain xmms-mad, the xmms plugin based on libmad. Kurt, since you got here first, you get the take the package I guess. I'd be happy to sponsor you. Are you in the NM queue? sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ signature.asc Description: OpenPGP digital signature
Bug#299192: python-pymad: pymad only available from python 2.3
Package: python-pymad Version: 0.5.2-1 Severity: wishlist Any chance we could get package build for python2.4/2.2? I personally need a 2.4 version. cheers, sam -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.11 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-pymad depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libmad0 0.15.1b-1MPEG audio decoder library ii python 2.3.5-1 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#297736: libmysqlclient10: does not report all reconnection errors
Steve Langasek wrote: > Sam, > > On Wed, Mar 02, 2005 at 03:55:32PM +0000, Sam Clegg wrote: > >>I found this problem while using the python bindings which set >>autocommit off by default. > > >>When not in autocommit mode (SET AUTOCOMMIT=0) the client will fail on >>reconnect and the nature of the error is not reported to the user. > > >>In the program below the final mysql_real_query() correctly returns >>-1 but mysql_error() incorrectly returns an empty string. > > > The libmysqlclient10 package is in legacy "maintenance mode", so this bug is > not likely to be fixed any time soon. Do you see the same problem with > libmysqlclient12 and/or libmysqlclient14? > I'd guessed that this might be true. The only reason I care is that the python bindings in sid are still linking against it. Perhaps I should ask thier maintainer to up the version? I'll see if I ge the same problem will 12/14. cheers, sam -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ signature.asc Description: OpenPGP digital signature
Bug#297736: libmysqlclient10: does not report all reconnection errors
Package: libmysqlclient10
Version: 3.23.56-2
Severity: normal
I found this problem while using the python bindings which set
autocommit off by default.
When not in autocommit mode (SET AUTOCOMMIT=0) the client will fail on
reconnect and the nature of the error is not reported to the user.
In the program below the final mysql_real_query() correctly returns
-1 but mysql_error() incorrectly returns an empty string.
#include
#include
#include
#include
int main()
{
int rtn;
char * query = "show tables";
char * autocommit = "SET AUTOCOMMIT=0";
MYSQL conn;
MYSQL* r = mysql_init(&conn);
printf("init done %p\n", r);
r = mysql_real_connect(&conn, "localhost", "airplay", "airplay", "Airplay",
0, NULL, 0);
printf("connect done %p\n", r);
rtn = mysql_real_query(&conn, autocommit, strlen(autocommit));
printf("query returned %d '%s'\n", rtn, mysql_error(&conn));
rtn = mysql_real_query(&conn, query, strlen(query));
printf("query returned %d '%s'\n", rtn, mysql_error(&conn));
MYSQL_RES *res = mysql_use_result(&conn);
mysql_free_result(res);
sleep(7);
rtn = mysql_real_query(&conn, query, strlen(query));
printf("query returned %d '%s'\n", rtn, mysql_error(&conn));
res = mysql_use_result(&conn);
mysql_free_result(res);
return 0;
}
The following patch seemed to fix this for me:
--- libmysql.c 2003-04-13 18:41:40.0 +0100
+++ libmysql.new2005-03-02 15:45:54.0 +
@@ -470,7 +470,11 @@
}
end_server(mysql);
if (mysql_reconnect(mysql))
+{
+ net->last_errno=CR_SERVER_GONE_ERROR;
+ strmov(net->last_error,ER(net->last_errno));
goto end;
+}
if (net_write_command(net,(uchar) command,arg,
length ? length : (ulong) strlen(arg)))
{
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-rc5
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages libmysqlclient10 depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii mysql-common4.0.23-7 mysql database common files (e.g.
ii zlib1g 1:1.2.2-4compression library - runtime
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#278891: libid3tag0 ignores v2 tag information if v1 tag is also present
I've had the same problem. Seems the patch is breaking the way the library is supposed to work (i.e. v2 tags take precidence over v1 tags). I have quite a few apps that use the feature and the are broken right now (i.e. xmms-mad). Can we get this patch removed for sarge? -- sam clegg :: [EMAIL PROTECTED] :: http://superduper.net/ :: PGP : D91EE369 $superduper: .signature,v 1.14 2005/01/19 13:21:14 sam Exp $ signature.asc Description: OpenPGP digital signature
