Computation Team
pkg-scicomp-de...@lists.alioth.debian.org
Changed-By: Falk Hueffner f...@debian.org
Description:
glpk - linear programming kit
glpk-doc - linear programming kit - documentation files
glpk-utils - linear programming kit - utility files
libglpk-dev - linear programming kit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 26 Aug 2006 21:35:17 +0200
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.11-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
On Fri, Jun 16, 2006 at 02:39:26PM -0700, Philip Brown wrote:
On Fri, Jun 16, 2006 at 11:15:32PM +0200, Falk Hueffner wrote:
Henning Makholm wrote:
Another related bug type that I found lurking in my packages when I
investigated the warnings in this list, is trying to format a size_t
On Fri, Jun 16, 2006 at 07:06:06PM -0500, Ron Johnson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Falk Hueffner wrote:
On Thu, Jun 08, 2006 at 07:58:23AM +0200, Bastian Blank wrote:
long is not appropriate to save pointers, you need to use intptr_t or
uintptr_t.
C90
On Sat, Jun 17, 2006 at 02:17:23AM +0200, Goswin von Brederlow wrote:
Falk Hueffner [EMAIL PROTECTED] writes:
So in summary, if you don't care about portability to 64-bit windows,
assuming sizeof(void*) == sizeof(long) is just fine.
Unless you compile with range checking pointers
Goswin von Brederlow [EMAIL PROTECTED] writes:
Falk Hueffner [EMAIL PROTECTED] writes:
On Sat, Jun 17, 2006 at 02:17:23AM +0200, Goswin von Brederlow wrote:
Falk Hueffner [EMAIL PROTECTED] writes:
So in summary, if you don't care about portability to 64-bit windows,
assuming sizeof(void
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 17 Jun 2006 09:06:24 +0200
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.10-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
On Thu, Jun 08, 2006 at 07:58:23AM +0200, Bastian Blank wrote:
On Wed, Jun 07, 2006 at 11:53:24PM +0100, Darren Salt wrote:
The others are trivially fixable; of these, the one in libavcodec is already
fixed in CVS. I've committed the rest (they're basically s/int/long/) and am
forwarding
Henning Makholm wrote:
Another related bug type that I found lurking in my packages when I
investigated the warnings in this list, is trying to format a size_t
value with a %u or %d format string, which will break if size_t is 64
bits (unless the actual number is small and it is the last
Aurelien Jarno [EMAIL PROTECTED] writes:
On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
On Alpha the problem is:
{standard input}: Assembler messages:
{standard input}:341: Error: macro requires $at register while noat in effect
{standard input}:374: Error: macro requires $at
Aurelien Jarno [EMAIL PROTECTED] writes:
Falk Hueffner a écrit :
Aurelien Jarno [EMAIL PROTECTED] writes:
On arm, ia64 and alpha the glibc fails to build with gcc-4.1.
On Alpha the problem is:
{standard input}: Assembler messages:
{standard input}:341: Error: macro requires $at register
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 10 Apr 2006 09:39:44 +0200
Source: craft
Binary: craft
Architecture: source alpha
Version: 3.5-12
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 13 Mar 2006 23:13:38 +0100
Source: qvwm
Binary: qvwm
Architecture: source alpha
Version: 1:1.1.12-4
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 4 Mar 2006 12:15:12 +0100
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.9-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 11 Jan 2006 16:21:01 +0100
Source: xskat
Binary: xskat
Architecture: source alpha
Version: 4.0-2
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 17 Dec 2005 15:42:07 +0100
Source: craft
Binary: craft
Architecture: source alpha
Version: 3.5-11
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 17 Dec 2005 17:28:09 +0100
Source: qvwm
Binary: qvwm
Architecture: source alpha
Version: 1:1.1.12-3
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
Steve Langasek [EMAIL PROTECTED] writes:
On Mon, Mar 21, 2005 at 09:51:25PM +0100, Falk Hueffner wrote:
Matthew Garrett [EMAIL PROTECTED] writes:
* the release architecture must be publicly available to buy new
Avoids a situation where Debian is keeping an architecture alive.
I don't
Matthew Garrett [EMAIL PROTECTED] writes:
* the release architecture must be publicly available to buy new
Avoids a situation where Debian is keeping an architecture alive.
I don't understand this. What is the problem with Debian is keeping an
architecture alive? What problem are you trying
Nikita V. Youshchenko [EMAIL PROTECTED] writes:
-int mailpop3_retr(mailpop3 * f, uint32_t index, char ** result,
+int mailpop3_retr(mailpop3 * f, unsigned int index, char ** result,
size_t * result_len);
That is, 'uint32_t' was changed to 'unsigned int'.
Does this break
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 13 Feb 2005 17:00:35 +0100
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.8-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
GOTO Masanori [EMAIL PROTECTED] wrote:
Marcelo E. Magallon [EMAIL PROTECTED] wrote:
Mesa upstream uses -mcpu=ev5 -mieee on alpha. Is that ok? Where does
this belong into? /usr/lib/ev5?
IIRC, alpha does not define any hwcaps.
There's a patch for this, which works fine, but wasn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 2 Dec 2004 13:53:49 +0100
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.7-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 6 Aug 2004 21:15:46 +0200
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.6-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 6 Aug 2004 18:08:27 +0200
Source: qvwm
Binary: qvwm
Architecture: source alpha
Version: 1:1.1.12-2
Distribution: unstable
Urgency: medium
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 28 Jun 2004 21:21:55 +0200
Source: craft
Binary: craft
Architecture: source alpha
Version: 3.5-10
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 25 May 2004 21:05:13 +0200
Source: xskat
Binary: xskat
Architecture: source alpha
Version: 4.0-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 17 Jan 2004 12:35:13 -0500
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.4-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
.tar.bz2
The man page was slightly updated (spell checking, formatting, SEE ALSO).
Closes: #173620
Applied a patch from Falk Hueffner [EMAIL PROTECTED]
to get_fat_entry in srmbootfat/srmbootfat.c to make it portable
* Stole patches from CVS HEAD/[EMAIL PROTECTED] for USB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 16 Nov 2003 15:43:08 +0100
Source: zile
Binary: zile
Architecture: source alpha
Version: 1.7beta2-1
Distribution: experimental
Urgency: low
Maintainer: Nicolas Duboc [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 30 Jun 2003 12:23:52 +0200
Source: qvwm
Binary: qvwm
Architecture: source alpha
Version: 1:1.1.12-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 26 Sep 2003 15:02:02 +0200
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 4.1-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
Ralf Treinen [EMAIL PROTECTED] writes:
E2tools is a simple set of GPL'ed utilities to read, write, and
manipulate files in an ext2/ext3 filesystem.
please excuse my ignorance - what would be the advantage of these
tools over the core file utilities which use the VFS layer?
You don't need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 8 May 2003 17:58:22 +0200
Source: zile
Binary: zile
Architecture: source alpha
Version: 1.6.2-1
Distribution: unstable
Urgency: low
Maintainer: Nicolas Duboc [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
Benj. Mako Hill [EMAIL PROTECTED] writes:
On Fri, Jun 27, 2003 at 12:32:59AM +0100, Millis Miller wrote:
Package: wnpp
Version: N/A; reported 2003-06-27
Severity: wishlist
* Package name: email
I understand that email is the name of the upstream client but I'd
like to urge you
Nathanael Nerode [EMAIL PROTECTED] writes:
Oddly, it looks like GCC doesn't currently ever generate
486-specific instructions; they are only (currently) of benefit to
assembly programmers. (Hmm... maybe I should see if there's an
enhancement opportunity to GCC there.)
I have a patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 19 Oct 2002 02:01:21 +0200
Source: glpk
Binary: glpk
Architecture: source alpha
Version: 3.2.2-1
Distribution: unstable
Urgency: low
Maintainer: Falk Hueffner [EMAIL PROTECTED]
Changed-By: Falk Hueffner [EMAIL PROTECTED
Sam Vilain [EMAIL PROTECTED] writes:
On Fri, 5 Jan 2001 19:08:38 +0200
[EMAIL PROTECTED] (Sami Haahtinen) wrote:
Or, can rsync sync binary files?
hmm.. this sounds like something worth implementing..
rsync can, but the problem is with a compressed stream if you insert
or alter data
Brederlow [EMAIL PROTECTED] writes:
It would be a great idea to have source dependencies. I compile all
sources on my debian mirror and most fail because of missing
files. One then has to search the package and install that before
compiling again.
A very simple way to improve in this area
.xssession? Maybe a .window-manager? I think that would be
useful, since there are many people who insist on a particular window
manager, but don't want to change anything else.
Falk Hueffner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
Hello,
I intend to apply as a maintainer (as soon as I find somebody to scan
my passport ;) and package:
- ras (http://dspace.dial.pipex.com/nc/)
Ras is a small utility that adds m extra files to a set of n files,
such that the contents of the n original files can be regenerated from
any n of
Michael Alan Dorman [EMAIL PROTECTED] writes:
Bdale Garbee [EMAIL PROTECTED] writes:
As maintainer of gzip for Debian, I do not agree that having gzip
fork a bzip2 when it sees a bzip2 magic number is a good idea. If
we want to support multiple compression engines, I believe this
should
Joel Klecker [EMAIL PROTECTED] writes:
At 14:16 +0200 1998-04-18, Brederlow wrote:
I think it would be a good idea to teach tar to unpack bzip2 files via
the -z option, just as if it would be gzip. Alternativly one could
teach gzip to use bzip2 for .bz2 archives or teach dpkg to distinguish
.x versions?
Falk Hueffner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wed, 8 Apr 1998 01:01:46 +0200, Marcus Brinkmann
[EMAIL PROTECTED] wrote:
It's related to the fact that egcs does exception handling - add
-fno-exceptions to your CFLAGS, and you'll get a shorter binary.
I think this is not the right way to think of C++ programming. If you don't
use
45 matches
Mail list logo
