Re: Bug#479440: ITP: funpidgin -- A pidgin fork

2008-05-05 Thread Joachim Breitner
Hi,

Am Montag, den 05.05.2008, 01:19 -0400 schrieb Kevin Mark:
> On Sun, May 04, 2008 at 11:28:40PM +0100, Ben Hutchings wrote:
> > On Sun, 2008-05-04 at 23:24 +0300, Mohammed Sameer wrote:
> > > Package: wnpp
> > > Severity: wishlist
> > > Owner: Mohammed Sameer <[EMAIL PROTECTED]>
> > > 
> > > * Package name: funpidgin
> > >   Version : 2.4.1
> > >   Upstream Author : A lot. Can't be listed here!
> > > * URL : http://funpidgin.sourceforge.net
> > > * License : GPL
> > >   Programming Lang: C
> > >   Description : graphical multi-protocol instant messaging client 
> > > based on pidgin
> > > 
> > > Funpidgin is a graphical, modular Instant Messaging client capable of 
> > > using
> > > AIM/ICQ, Yahoo!, MSN, IRC, Jabber, Napster, Zephyr, Gadu-Gadu, Bonjour,
> > > Groupwise, Sametime, SILC, and SIMPLE all at once.
> > > It has all the features offered by pidgin plus:
> > > * "Entry area manual sizing" a plugin by that allows manual resizing of 
> > > the entry area.
> > > * An option to set the size of the buddy icons displayed in the chat 
> > > window.
> > > * An option to let the window manager place new windows.
> > > * Two different ways of seeing that your buddies are typing.
> > > * An optional send button for Tablet PC users.
> > 
> > Maybe you could wait to see whether this fork lasts, and adds some
> > *substantial* features, before adding it?
> > 
> > Ben.
> > 
> 
> my understanding is that this is a 'protest' fork made to add a feature
> that the upstream did not want(the resizing). So as long as the upstream
> resists, it should survive.

Could we, as the Debian distribution, not make the decision what variant
we want to distribute? We can take the useful patches from funpidgin, if
they are good, and add them to “our” pidgin. That might be the best for
our users and in the spirit of free software, although it might be bad
for our relationship with upstream pidgin.

In any case I suggest that the maintainers of pidgin and funpidgin try
to work together to keep the packages in debian compatible as possible,
e.g. when it comes to plugins and the like.

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


Re: Bug#479440: ITP: funpidgin -- A pidgin fork

2008-05-05 Thread William Pitcock
Hi,

On Mon, 2008-05-05 at 09:10 +0200, Joachim Breitner wrote:
> Hi,
> 
> Am Montag, den 05.05.2008, 01:19 -0400 schrieb Kevin Mark:
> > On Sun, May 04, 2008 at 11:28:40PM +0100, Ben Hutchings wrote:
> > > On Sun, 2008-05-04 at 23:24 +0300, Mohammed Sameer wrote:
> > > > Package: wnpp
> > > > Severity: wishlist
> > > > Owner: Mohammed Sameer <[EMAIL PROTECTED]>
> > > > 
> > > > * Package name: funpidgin
> > > >   Version : 2.4.1
> > > >   Upstream Author : A lot. Can't be listed here!
> > > > * URL : http://funpidgin.sourceforge.net
> > > > * License : GPL
> > > >   Programming Lang: C
> > > >   Description : graphical multi-protocol instant messaging client 
> > > > based on pidgin
> > > > 
> > > > Funpidgin is a graphical, modular Instant Messaging client capable of 
> > > > using
> > > > AIM/ICQ, Yahoo!, MSN, IRC, Jabber, Napster, Zephyr, Gadu-Gadu, Bonjour,
> > > > Groupwise, Sametime, SILC, and SIMPLE all at once.
> > > > It has all the features offered by pidgin plus:
> > > > * "Entry area manual sizing" a plugin by that allows manual resizing of 
> > > > the entry area.
> > > > * An option to set the size of the buddy icons displayed in the chat 
> > > > window.
> > > > * An option to let the window manager place new windows.
> > > > * Two different ways of seeing that your buddies are typing.
> > > > * An optional send button for Tablet PC users.
> > > 
> > > Maybe you could wait to see whether this fork lasts, and adds some
> > > *substantial* features, before adding it?
> > > 
> > > Ben.
> > > 
> > 
> > my understanding is that this is a 'protest' fork made to add a feature
> > that the upstream did not want(the resizing). So as long as the upstream
> > resists, it should survive.
> 
> Could we, as the Debian distribution, not make the decision what variant
> we want to distribute? We can take the useful patches from funpidgin, if
> they are good, and add them to “our” pidgin. That might be the best for
> our users and in the spirit of free software, although it might be bad
> for our relationship with upstream pidgin.
> 

Pidgin and Funpidgin are clearly two different projects, although not
much rebranding has yet happened. While this seems like a good solution,
it is likely not:
 * some users will likely prefer Pidgin as it is over Funpidgin;
 * Funpidgin has features (MSN P14/Pecan support) that cannot easily be
   integrated into Pidgin without ugly patchsets.

A solution, provided that the public plugin API isn't changed in
Funpidgin could be to install pidgin-plugins to a shared location, and
patch both clients to load plugins from that directory as well as their
native locations.

> In any case I suggest that the maintainers of pidgin and funpidgin try
> to work together to keep the packages in debian compatible as possible,
> e.g. when it comes to plugins and the like.
> 

Having talked with upstream (and now joined upstream), funpidgin is
becoming more of a refactoring project of pidgin's code, as well as
readding features which were removed.

As such, while funpidgin will likely try to maintain the public
interface, there will be reasons to run funpidgin over pidgin and
vice-versa.

In my view, funpidgin will probably be more valuable to the Debian user
community than pidgin (even with patching) due to planned improvement of
i18n-related issues (character set transcoding, etcetera) and an overall
improved and refactored codebase.

William


signature.asc
Description: This is a digitally signed message part


Re: Is master unsuitable to receive mail from lists.debian.org?

2008-05-05 Thread Colin Watson
On Sun, May 04, 2008 at 04:57:10PM -0500, Adam Majer wrote:
> Colin Watson wrote:
> > Yes, I've been seeing the same thing. It's usually just an irritation,
> > but I guess some day I'll hit a threshold and get unsubscribed from a
> > bunch of lists.
> 
> Wouldn't it be possible to configure the mail server to filter the mail
> based on the header content? That is,
> 
>  * Is it spam? => Yes => Now do the following:

In this case, master should simply trust lists.debian.org to have done
spam checking and not repeat it. After all they're in the same
administrative domain.

-- 
Colin Watson   [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Bug#479440: ITP: funpidgin -- A pidgin fork

2008-05-05 Thread Mohammed Sameer
On Mon, May 05, 2008 at 09:10:07AM +0200, Joachim Breitner wrote:
> Hi,
> 
> Am Montag, den 05.05.2008, 01:19 -0400 schrieb Kevin Mark:
> > On Sun, May 04, 2008 at 11:28:40PM +0100, Ben Hutchings wrote:
> > > On Sun, 2008-05-04 at 23:24 +0300, Mohammed Sameer wrote:
> > > > Package: wnpp
> > > > Severity: wishlist
> > > > Owner: Mohammed Sameer <[EMAIL PROTECTED]>
> > > > 
> > > > * Package name: funpidgin
> > > >   Version : 2.4.1
> > > >   Upstream Author : A lot. Can't be listed here!
> > > > * URL : http://funpidgin.sourceforge.net
> > > > * License : GPL
> > > >   Programming Lang: C
> > > >   Description : graphical multi-protocol instant messaging client 
> > > > based on pidgin
> > > > 
> > > > Funpidgin is a graphical, modular Instant Messaging client capable of 
> > > > using
> > > > AIM/ICQ, Yahoo!, MSN, IRC, Jabber, Napster, Zephyr, Gadu-Gadu, Bonjour,
> > > > Groupwise, Sametime, SILC, and SIMPLE all at once.
> > > > It has all the features offered by pidgin plus:
> > > > * "Entry area manual sizing" a plugin by that allows manual resizing of 
> > > > the entry area.
> > > > * An option to set the size of the buddy icons displayed in the chat 
> > > > window.
> > > > * An option to let the window manager place new windows.
> > > > * Two different ways of seeing that your buddies are typing.
> > > > * An optional send button for Tablet PC users.
> > > 
> > > Maybe you could wait to see whether this fork lasts, and adds some
> > > *substantial* features, before adding it?
> > > 
> > > Ben.
> > > 
> > 
> > my understanding is that this is a 'protest' fork made to add a feature
> > that the upstream did not want(the resizing). So as long as the upstream
> > resists, it should survive.
> 
> Could we, as the Debian distribution, not make the decision what variant
> we want to distribute? We can take the useful patches from funpidgin, if
> they are good, and add them to “our” pidgin. That might be the best for
> our users and in the spirit of free software, although it might be bad
> for our relationship with upstream pidgin.
> 
> In any case I suggest that the maintainers of pidgin and funpidgin try
> to work together to keep the packages in debian compatible as possible,
> e.g. when it comes to plugins and the like.

Let me clarify my POV a bit.
The resizing part is already implemented as a plugin. If the fork doesn't 
survive then
it can be "extracted" and shipped alone.

However, checking the list of improvements in their svn leads me to think that 
they already
started to implement a lot of changes.

The MSN protocol probably can be handled, pidgin and pidgin-experimental 
packages for
example (But it needs Robert McQueen, the current pidgin maintainer to agree).

My intention is to contact him and see if we can work together or at least 
reuse the
specific pidgin debian patches he wrote/maintain. Maybe even setup a team if he 
agrees.

But I'd say wait a bit and see what will happen, I guess the funpidgin 
developers will
be synching with pidgin but I don't know how it will happen.

point is, everything is easy as long as the plugins API is similar but if 
funpidgin drifts
then we can't share a lot.

At the moment, funpidgin can't be installed along with pidgin. I'm still 
waiting for the
new release to see what will happen (And they are planning to solve this ASAP).

Cheers,

-- 
GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F  280E CB66 8E29 A3FD 0DF7
Debian User and Developer.
Homepage: www.foolab.org


signature.asc
Description: Digital signature


Re: Bug#479440: ITP: funpidgin -- A pidgin fork

2008-05-05 Thread Paul Wise
On Mon, May 5, 2008 at 6:13 PM, Mohammed Sameer <[EMAIL PROTECTED]> wrote:

>  However, checking the list of improvements in their svn leads me to think 
> that they already
>  started to implement a lot of changes.

Anyone know if they plan telepathy integration/support?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: [OT] Need old Packages.gz and Release Files

2008-05-05 Thread Michelle Konzack
Am 2008-04-28 20:21:34, schrieb Goswin von Brederlow:
> > If you have for example the ORIGINAL CDs/DVD's of 3.1r4 I can build  the
> > package tree from there since I have all original packages I only do not
> > know which packages went included in the releases...
> 
> Did anyone mention http://archive.debian.org/README yet?

Yes, but the lists are not complete.

> If you get the Packages.gz, Release and Release.gpg files from a
> CD/DVD set then you can verify them individually with the debian
> archive key from that time and then merge them into a full list and
> sign with your own key. You don't have to download anything from
> archive.debian.net if you have those index file.

As I have written, I have nearly  20 TByte  of  Debian  packages  on  my
mirror and only accidently killet the /debian/dists/ directory with  all
its Packages.gz, Sources.gz, Release and releases.gpg files.

I have all downloaded I  have  found  and  arround  16%  of  the  mirror
(generaly the last releses) restored.  What I am missing, are the  LISTS
of the packages from the Sub-Releases like r0, r1, ...

Since I have ONLY original Debian packages and trust them because it  is
a private Non-Public mirror (up to now) I need only the Lists  with  the
files with its version numbers which went in the Sub-Releases to  create
the Symlinks and generate the NEW Packages.gz and Sources.gz files.

Since I can not use the original GPG-Key I sign the Release  files  with
MY GPG-Key to be sure, no one else after me has modified it.

OK, there are peoples using my  mirror,  BUT THEY TRUST MY KEY  even  if
they have not signed it, because we have never meet us personaly.

Note:   If I do bad things, peoples will find it out very fast,
and my business is ancien history...

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


Bug#479553: ITP: thinkcspy2 -- free Python book for beginning programmers

2008-05-05 Thread FFM__
Package: wnpp
Severity: wishlist
Owner: FFM__ <[EMAIL PROTECTED]>


* Package name: thinkcspy2
  Version : 2.0.0
  Upstream Author : Jeff Elkner <[EMAIL PROTECTED]>=
* URL : http://openbookproject.net/thinkCSpy/
* License : GFDL
  Programming Lang: Lore, Python
  Description : free Python book for beginning programmers

 How to Think Like A Computer Scientist is a free programming tutorial written
 for the Python language

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-6-xen-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: [OT] Need old Packages.gz and Release Files

2008-05-05 Thread Jens Seidel
On Thu, May 01, 2008 at 05:20:32PM +0200, Michelle Konzack wrote:
> As I have written, I have nearly  20 TByte  of  Debian  packages  on  my
> mirror and only accidently killet the /debian/dists/ directory with  all
> its Packages.gz, Sources.gz, Release and releases.gpg files.
> 
> I have all downloaded I  have  found  and  arround  16%  of  the  mirror
> (generaly the last releses) restored.  What I am missing, are the  LISTS
> of the packages from the Sub-Releases like r0, r1, ...

You can use the jigdo files such as debian-40r2-i386-DVD-1.jigdo from
http://www.debian.co.il/debian-cd/4.0_r2/i386/jigdo-dvd/ or
http://ftp.pwr.wroc.pl/debian-iso/4.0_r1/i386/jigdo-dvd/debian-40r1-i386-DVD-1.jigdo
to extract this information. jigdo files are just gzipped text files.

At least for the 4.0 release you should be able to find jigdo files ...
I think I can send you also some older releases such as Woody in a
private mail. Have to dig ...

Jens


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: building a package two times

2008-05-05 Thread Adeodato Simó
* Marco d'Itri [Sun, 04 May 2008 00:46:32 +0200]:

> On May 03, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:

> > FLAVORS := std
> > ifeq ((findstring $(DEB_HOST_ARCH),amd64 ia64 ppc64 s390x),)
> > FLAVORS += lfs
> > endif

> > Like this?
> AFAICT this will match also if DEB_HOST_ARCH=s390.

  ifeq (,$(filter $(DEB_HOST_ARCH),amd64 ... s390x))

Just thought I'd mention.

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
Don't be irreplaceable, if you can't be replaced, you can't be promoted.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Bug#479553: ITP: thinkcspy2 -- free Python book for beginning programmers

2008-05-05 Thread Evgeni Golov
On Mon, 05 May 2008 08:52:42 -0400 FFM__ wrote:

> * License : GFDL
>   Description : free [...]

As far as I understand, GFDL is non-free for Debian :(

Cheers,
Evgeni


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: [pkg-boost-devel] Bug#473752: Bug#473752: Bug#473752: Boost 1.35 has been released

2008-05-05 Thread Domenico Andreoli
On Sat, May 03, 2008 at 12:15:39AM -0500, Steve M. Robbins wrote:
> On Tue, Apr 29, 2008 at 01:14:45PM +0200, Domenico Andreoli wrote:
> > On Tue, Apr 29, 2008 at 12:22:24AM -0500, Steve M. Robbins wrote:
> > > 
> > > In contrast, the alternative strategy of having all the libfoo-dev
> > > (1.34.1) packages conflict with libfoo1.35.0-dev packages has just a
> > > single negative: that you can't develop simultaneously with 1.34.1 and
> > > 1.35.0.  On the positive side, however, you can install the 1.35 -devs
> > > and the existing build scripts will work because the include path and
> > > the simplified link library names are preserved.
> > > 
> > > So unless anyone (Domenico?) has a strong preference for the
> > > first option, I'm planning to pursue the second.
> > 
> > second option, absolutely.
> 
> Good.  I'm planning to assume that the 1.35.x releases are all
> approximately API-compatible, so I'm naming the packages
> libboost-foo1.35-dev.  Any objection to that?
> 
> 
> My headache now is that there are 13 -dev packages in Boost.  One
> (libboost1.35-dev) contains 60+ header-only libraries, while the
> others each contain 1 library that happens to build a shared object.
> 
> This overhead creates a nonnegligible amount of complexity and
> generates bugs (e.g. #457654, #478782).  Is there any value to this
> granularity?  I can't see any.  If there are no objections, I'm
> leaning towards collapsing all the -dev packages into libboost1.35-dev
> -- and rolling bcp into it, as well.  I'll probably keep
> libboost-python1.35-dev separate (with pyste rolled into it).
> 
> Your thoughts?

please, proceed.

ciao,
Domenico

-[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50


signature.asc
Description: Digital signature


Re: Bug#479553: ITP: thinkcspy2 -- free Python book for beginning programmers

2008-05-05 Thread Eugene V. Lyubimkin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Evgeni Golov wrote:
>> * License : GFDL
>>   Description : free [...]
> 
> As far as I understand, GFDL is non-free for Debian :(
Does it (thinkcspy2) contain unmodificable sections?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIHzMBchorMMFUmYwRAkmtAJ0Spy5xqgjYn1SGe3GU9gHKNzRHgACfYGiM
PP6za4WCNNxlxifImWJrJhw=
=jyTe
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Is master unsuitable to receive mail from lists.debian.org?

2008-05-05 Thread Simon Huggins
On Sun, May 04, 2008 at 11:05:31AM -0700, Don Armstrong wrote:
> On Sun, 04 May 2008, Santiago Vila wrote:
> > Executive summary: master.debian.org, where I receive debian email,
> > has stronger spam filtering than lists.debian.org, as master seems
> > to use some kind of "content filtering". As a result, some spam
> > messages distributed by lists.debian.org are rejected by
> > master.debian.org.
> The problem is that the filtering is differential; master.debian.org
> should be reconfigured to either just accept these messages from
> lists, or discard them.

> As listmaster has nothing to do with the mail configuration on master,
> there's not much listmaster can do about it.

I'm not convinced that's really true.

You obviously have some system that generates the messages based on
bounces and that records which message bounced.  If many subscribers
bounce the same mail that's a good indication that it's spam.

Perhaps instead of sending these content-free notes that we're going to
be unsubscribed some time, after some undisclosed number of bounces,
listmasters could consider these messages as hints with which to adjust
the spam filter used.

-- 
--("Do you have a girl coming over?" - Scully)--
Simon ("What's a girl?" - Mulder ) Nomis
 Htag.pl 0.0.22


signature.asc
Description: Digital signature


Re: Is master unsuitable to receive mail from lists.debian.org?

2008-05-05 Thread Don Armstrong
On Mon, 05 May 2008, Simon Huggins wrote:
> Perhaps instead of sending these content-free notes that we're going to
> be unsubscribed some time, after some undisclosed number of bounces,
> listmasters could consider these messages as hints with which to adjust
> the spam filter used.

When we see spam getting through to the lists, we already adjust the
spam filters. If you think you can do a better job, the spamassassin
rules are all publicly available, and we gladly accept patches.


Don Armstrong

-- 
"There's no problem so large it can't be solved by killing the user
off, deleting their files, closing their account and reporting their
REAL earnings to the IRS."
 -- The B.O.F.H..

http://www.donarmstrong.com  http://rzlab.ucr.edu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Is master unsuitable to receive mail from lists.debian.org?

2008-05-05 Thread Simon Huggins
On Mon, May 05, 2008 at 11:30:45AM -0700, Don Armstrong wrote:
> On Mon, 05 May 2008, Simon Huggins wrote:
> > Perhaps instead of sending these content-free notes that we're going to
> > be unsubscribed some time, after some undisclosed number of bounces,
> > listmasters could consider these messages as hints with which to adjust
> > the spam filter used.
> When we see spam getting through to the lists, we already adjust the
> spam filters. If you think you can do a better job, the spamassassin
> rules are all publicly available, and we gladly accept patches.

I can't find the bit in there that stops you sending the contentless
bounce message?  Can you point me at it so I can send a patch to include
how close to the threshold I am and also patch it so that DDs can
disable it?

Thanks,

Simon.

-- 
[ "No, the radio works.  You don't" - Basil, Fawlty Towers ]


signature.asc
Description: Digital signature


Re: Bug#479553: ITP: thinkcspy2 -- free Python book for beginning programmers

2008-05-05 Thread Manoj Srivastava
On Mon, 5 May 2008 18:12:37 +0200, Evgeni Golov <[EMAIL PROTECTED]> said: 

> On Mon, 05 May 2008 08:52:42 -0400 FFM__ wrote:
>> * License : GFDL
>> Description : free [...]

> As far as I understand, GFDL is non-free for Debian :(

Stated unconditionally like that, I do not think that is
 accurate.  Packages licensed under the GFDL are already in Debian, as
 long as they do not contain any invariant parts.

manoj
-- 
Minnie Mouse is a slow maze learner.
Manoj Srivastava <[EMAIL PROTECTED]>   
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#479659: RFH: wine -- Windows API implementation

2008-05-05 Thread Ove Kaaven
Package: wnpp
Severity: normal

Since my time may be limited in the future, I am seeking comaintainers
for the Wine package in Debian, at least to ensure that new Wine releases
may continue to be uploaded in a timely fashion, and to keep the package's
bug count down. (And given that pretty much half the open bugs are "missing
manpage" bugs, documentation writers would also help...)

I have created a project for this on alioth.debian.org. I've loaded the
current packaging (all versions since etch) into a Git repository there, and
put up some instructions on http://pkg-wine.alioth.debian.org/

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Bug#479220: Additional information

2008-05-05 Thread Raphael Hertzog
On Mon, 05 May 2008, Niko Tyni wrote:
> On Mon, May 05, 2008 at 12:23:59PM +0200, Raphael Hertzog wrote:
> > On Mon, 05 May 2008, Niko Tyni wrote:
> > > # perl -le 'eval "use Locale::gettext"; print "got: $@" if $@; exit 0'; 
> > > echo $?
> > > perl: symbol lookup error: /usr/lib/perl5/auto/Locale/gettext/gettext.so: 
> > > undefined symbol: Perl_Istack_sp_ptr
> > > 127
> > > 
> > > No fix yet, but the only way out I see is having some
> > > package(s?) pre-depend on the new perl-base. Fixing the eval/dlopen
> > > interaction in perl is out of the question because this is happening
> > > when the old perl-base version is still installed.
> > > 
> > > Any help and ideas welcome.
> > 
> > I would suggest integrating liblocale-gettext-perl to perl-base. Maybe
> > that should be suggested upstream?
> 
> IMO deviating from the upstream core module list should only be a very
> last resort, and this should be fixable in another way. That said,
> getting Locale::gettext into the core upstream might be a worthy goal;
> please file a wishlist bug with some rationale if you care about it.

I think it makes sense in the long term at least. So I will submit the bug
report and hopefully you can bring up the discussion on p5p.

> I think making liblocale-gettext-perl Pre-Depend on ${perl:Depends}
> would fix this particular issue, but I'm worried that it's not the
> only one. The other two XS modules that debconf-i18n depends on,
> libtext-iconv-perl and libtext-charwidth-perl, come to mind first.

Indeed. CCing debian-devel to see if we have other solutions to avoid the
pre-dependency.

> What's stopping the prerm of a random package invoking a perl script
> on upgrades that needs yet another XS module package? If the script
> does the 'eval "use ..."' thing, the package won't even be listed as a
> dependency. How can we detect these short of waiting for bug reports?
> 
> Is there a more general way of solving this?

Another solution is to make sure that the eval construct copes well with
XS modules linked for another perl (ie if they fail at dlopen()). I don't
see a reason why this couldn't be a run-time failure like another one...

That would be the general solution.

Cheers,
-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



SAGE packages for Debian

2008-05-05 Thread Timothy G Abbott
I've been working on packaging for Debian SAGE (http://sagemath.org), a 
large free mathematics software conglomeration that is competing with 
proprietary mathematical software systems such as Mathematica, Matlab, 
Maple, and Magma (Debian bug #455292).


This has been a rather large effort because a major contribution of SAGE 
is providing an excellent ipython-base interface to a number of other free 
software mathematics libraries; the SAGE distribution comes with some 71 
dependencies, of which only around 2/3 are available in Debian already.


I currently have a working apt repository from which one can "apt-get 
install sagemath" (some details on the repository are available at 
) with some 26 source packages in it 
that I created for the SAGE dependencies.  The repository also contains 
modified versions of various Debian packages with quick workarounds for 
bugs #472392, #474080, #474083, #459200.


The packages are tested to the extent that I have run a full set of SAGE 
doctests against them with two different SAGE releases, and they largely 
seem to work (though there are definitely a number of bugs remaining).


However, while it is nice to have a repository that people who want to use 
SAGE can add to their sources.list, it would be far better for SAGE to be 
available in Debian (I think having SAGE packages ready for lenny is a 
reasonable goal).  The primary problem that makes my packages potentially 
unsuitable for uploading to Debian now is many of them may violate Debian 
library policy:

- shared libraries whose soname is 0.0.0 (suggesting the upstream may not 
actually be doing versioning)
- static libraries compiled with -fPIC (something strongly discouraged in the 
library packaging guide)
- shared libraries that don't have versioning at all (clearly a bug)

For the shared libraries that are missing sonames entirely, I am in 
contact with the upstream developers and they are working on getting some 
sort of shared library versioning implemented (the SAGE developers are 
very supportive of this effort and have offered to help the upstream 
developers with some of these library versioning issues).


Below I list new source packages categorized by roughly how ready they are 
for being uploaded to the Debian archive.  Many of them have 
"description-contains-homepage" and "out-of-date-standards-version 3.7.2" 
lintian warnings because I wrote most of the control files on etch, and 
several have slightly more serious "binary-without-manpage" warnings.



The secondary problem with getting these 26 source packages into Debian is 
that I simply don't have the time to responsibly maintain 26 source 
packages in Debian.  So, I'm looking for people and teams in Debian to 
adopt some of these SAGE dependencies and upload them in time for Lenny.


My guess is the right Debian protocol for coordinating this is for me to 
file RFP bugs for all the packages below, linking in each to my existing 
draft packaging and mark those RFP bugs as all blocking #455292.  But I'd 
appreciate feedback on this plan before I file 26 bug reports.


If you're interested in helping maintain SAGE and its dependencies in 
Debian, you should join us on the [EMAIL PROTECTED] mailing 
list (I have no objection to eventually migrating to a lists.debian.org 
list in the future, but that's what we've been using thus far).


Any feedback or suggestions would also be greatly appreciated.

-Tim Abbott

Packages with no problems worse than missing man pages:
python-arpack (from the scipy sandbox)
python-delaunay (from the scipy sandbox)
flintqs
genus2reduction
gfan [but depends on cddlib, see below]
palp
rubiks
sympow
lcalc
polybori

Packages with suspicious 0.0.0 sonames:
libfplll
iml
libm4ri [also needs description]
givaro
linbox-wrap

Packages with no shared library whose static library is compiled with -fPIC
linbox
symmetrica
tachyon
cddlib

Packages that have clear library policy issues:
eclib [no soname]
flint [no soname]
libzn-poly [no soname, though I've sent a patch for this upstream]
ntl [no soname, though I've sent a patch for this upstream]
singular [no soname]

Packages that have other oustanding issues:
guava [binaries under /usr/share/gap; also many lintian warnings will be fixed 
in the 3.5 upstream release]
sagemath [numerous isuses]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]