On Wed, Jul 26, 2006, Thomas Bushnell BSG wrote:
> It is very confusing to me why lilypond should need either
> python-support or python-central at all. Can you explain?
Actually, it doesn't, I was wrong. I thought some sort of private or
public module was built, but the only bits seem to live
Le mercredi 26 juillet 2006 à 16:35 -0600, Bruce Sass a écrit :
> > The more circular depends there are the more likely such a failure
> > becomes. So wouldn't it be a good thing to remove all the circular
> > depends that are not neccessary?
>
> Sure, but an even better thing would be to fix liba
Le jeu 27 juillet 2006 05:02, Thomas Bushnell BSG a écrit :
> Stephen Gran <[EMAIL PROTECTED]> writes:
> > What is this, solution number 4 for Mr. BSG's complaints? I am
> > almost beginning to believe that he is more interested in
> > complaining than just fixing the problem.
>
> Solution? How a
I have requested an update to Packages-arch-specific for asis and other
packages, so that the buildds would try to build these packages on newly
supported architectures.
LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday
(2006-07-26), I uploaded asis again (2005-4), hoping to ha
Bruce Sass <[EMAIL PROTECTED]> writes:
> On Tue July 25 2006 05:38, Goswin von Brederlow wrote:
>> Except that libapt does NOT correctly handle dependency loops and can
>> split them between dpkg calls causing install failures.
>>
>> The more circular depends there are the more likely such a failu
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Le mercredi 26 juillet 2006 à 16:35 -0600, Bruce Sass a écrit :
>> > The more circular depends there are the more likely such a failure
>> > becomes. So wouldn't it be a good thing to remove all the circular
>> > depends that are not neccessary?
>>
>
Hi Ludovic,
On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote:
> I have requested an update to Packages-arch-specific for asis and other
> packages, so that the buildds would try to build these packages on newly
> supported architectures.
>
> LaMont Jones made the requested changes o
On Thursday 27 July 2006 14:26, Aurélien GÉRÔME wrote:
> Hi Ludovic,
>
> On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote:
> > I have requested an update to Packages-arch-specific for asis and other
> > packages, so that the buildds would try to build these packages on newly
> > suppo
On Wed, Jul 26, 2006, Thomas Bushnell BSG wrote:
> I believe the patch you sent was not against the current upstream
> release, unless you are referring to something different.
I am not the lilypond maintainer, I don't want to have to download an
upstream tarball or prepare a CVS snapshot or wha
Hi,
On Thu, Jul 27, 2006 at 03:06:25PM +0300, George Danchev wrote:
> AFAICT Packages-arch-specific is a quinn-diff [1] conffile, so probably
> bugreports should be filed against that package, but I'm not sure if
> autobuilders actually use that package though. Also it seems like
> dak/wanna-bu
On 27-Jul-06, 06:13 (CDT), Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> No harder than all the other apt operations are already. install,
> upgrade, dist-upgrade are all already NP-hard. And dpkg does handle
> cycles correctly so why shouldn't apt be able to? I don't buy that
> argument.
Dp
On Thursday 27 July 2006 15:55, Aurélien GÉRÔME wrote:
> Hi,
>
> On Thu, Jul 27, 2006 at 03:06:25PM +0300, George Danchev wrote:
> > AFAICT Packages-arch-specific is a quinn-diff [1] conffile, so probably
> > bugreports should be filed against that package, but I'm not sure if
> > autobuilders actu
Some of the ARM buildds are still not using G++ 4.1 as the default C++
compiler, nearly two months after the default was changed. I already
reported this over a month ago to [EMAIL PROTECTED], but it's
still unfixed. That is the correct address, isn't it?
Please could all the ARM buildds be upda
Ludovic Brenta <[EMAIL PROTECTED]> writes:
> I have requested an update to Packages-arch-specific for asis and other
> packages, so that the buildds would try to build these packages on newly
> supported architectures.
>
> LaMont Jones made the requested changes on 2006-07-23 [1]. Yesterday
> (20
Steve Greenland <[EMAIL PROTECTED]> writes:
> On 27-Jul-06, 06:13 (CDT), Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>> No harder than all the other apt operations are already. install,
>> upgrade, dist-upgrade are all already NP-hard. And dpkg does handle
>> cycles correctly so why shouldn't
Roger Leigh <[EMAIL PROTECTED]> writes:
> Some of the ARM buildds are still not using G++ 4.1 as the default C++
> compiler, nearly two months after the default was changed. I already
> reported this over a month ago to [EMAIL PROTECTED], but it's
> still unfixed. That is the correct address, is
Your enquiry has been received and will be dealth with by a
representative.
Thank you for contacting eConsulting.Net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
I've been following the directions here:
http://www.mobilab.unina.it/Resources/crosscompilerHOWTO.html
attempting to set up a cross-compiler toolchain for my ipod. So far,
I've run into a small quirk; half of the files get installed to
/usr/arm-linux, the other half
Hi,
[Please keep the CC to debian-devel, or please CC me, if yu
are replying to this on debian-python@lists.debian.org, since
I am not subscribed to that list]
I have been trying to ensure that my SELinux related packages
which have a python component are complian
On Thu, Jul 27, 2006 at 12:45:11PM +0200, Ludovic Brenta wrote:
> I have requested an update to Packages-arch-specific for asis and other
> packages, so that the buildds would try to build these packages on newly
> supported architectures.
> LaMont Jones made the requested changes on 2006-07-23 [1
Hello,
Pan[0] is currently undergoing a major rewrite, and being the maintainer, I am
currently considering what version of pan to include in etch. This mail[1] from
one of the pan mailing lists sums up the situation quite nicely.
Essentially, what it boils down to is this: Would it be prudent to
On Thu, Jul 27, 2006 at 06:31:01PM +0200, Goswin von Brederlow wrote:
> Roger Leigh <[EMAIL PROTECTED]> writes:
>
> > Some of the ARM buildds are still not using G++ 4.1 as the default C++
> > compiler, nearly two months after the default was changed. I already
> > reported this over a month ago
Hi,
I'd advise against more than one version, that'll make you support two
versions with very limited upstream support. Do ship the one you're
comfortable with supporting until etch+1 and security supporting
somewhat longer largely by yourself: Upstream will tell you 'not to use
beta software' for
Aaron M. Ucko <[EMAIL PROTECTED]> wrote:
> Tyler MacDonald <[EMAIL PROTECTED]> writes:
>
> > Has anybody else run into this? Is there something I can do that's
> > cleaner and closer to The Debian Way than manually making symlinks?
>
> Install the Debian toolchain-source package and go from t
Tyler MacDonald <[EMAIL PROTECTED]> writes:
> Has anybody else run into this? Is there something I can do that's
> cleaner and closer to The Debian Way than manually making symlinks?
Install the Debian toolchain-source package and go from there.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.e
Package: wnpp
Severity: wishlist
Owner: "Robert S. Edmonds" <[EMAIL PROTECTED]>
* Package name: ipset
Version : 2.2.9
Upstream Author : Jozsef Kadlecsik <[EMAIL PROTECTED]>
* URL : http://ipset.netfilter.org/
* License : GPL
Programming Lang: C
Description
Processing commands for [EMAIL PROTECTED]:
> reassign 379843 logrotate
Bug#379843: base: There are multiple ways to rotate logs, when it should be
centralised
Bug reassigned from package `base' to `logrotate'.
> reassign 223014 initscripts
Bug#223014: base: mount example bad when root dir gets m
On Thu, 27 Jul 2006 14:15:47 -0500, Joe Wreschnig <[EMAIL PROTECTED]> said:
> On Thu, 2006-07-27 at 11:56 -0500, Manoj Srivastava wrote:
>> Hi,
>>
>> [Please keep the CC to debian-devel, or please CC me, if yu are
>> replying to this on debian-python@lists.debian.org, since I am not
>> subscribe
Le jeu 27 juillet 2006 23:20, Manoj Srivastava a écrit :
> On Thu, 27 Jul 2006 14:15:47 -0500, Joe Wreschnig
<[EMAIL PROTECTED]> said:
> > Your confusion is due to an incorrect distinction. .py and .so
> > files are both modules; .so files are "extension modules" and .py
> > files are "pure Pytho
Warning, long email.
Executive summary.
==
* More consistent handling of SSL certs would be nice.
* The proposed ssl-cert package is not in good shape.
ssl-cert2 from http://jameswestby.net/debian/ssl-cert2-0.1.tar.gz
aims to
* Make it easier for package maintainers
Package: module-assistant
Version: 0.10.6
Hi,
> > #!/bin/sh
> > set -e
> >
> > SYSTEMMAP=/boot/System.map-_KVERS_
> >
> > if [ -f $SYSTEMMAP ] ; then
> > depmod -ae -F $SYSTEMMAP _KVERS_
> > elif [ "`uname -r`" = "_KVERS_" ] ; then
> > depmod -a &
> > fi
>
> As of debhe
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> it seems that guile 1.6.8 is buggy. people reported to have build
> lilypond with guile 1.6.7 and/or guile-1.8 correctly. And I suppose
> *HERE* is the real problem, which you failed to spot, because you
> didn't even TRIED to. I had that problem
Loïc Minier <[EMAIL PROTECTED]> writes:
> On Wed, Jul 26, 2006, Thomas Bushnell BSG wrote:
>> I believe the patch you sent was not against the current upstream
>> release, unless you are referring to something different.
>
> I am not the lilypond maintainer, I don't want to have to download an
>
Hi all,
I recently noticed that /usr/lib/perl5/XML/Parser on my
Debian/Stable (UltraSparc) seemed to be damaged.
~$ ls /usr/lib/perl5/XML/Parser
ls: /usr/lib/perl5/XML/Parser: Input/output error
And I failed to reinstall libxml-parser-perl_2.34-4_sparc.deb
with the same reason.
How can I fix th
This one time, at band camp, Atsuhito Kohda said:
> Hi all,
>
> I recently noticed that /usr/lib/perl5/XML/Parser on my
> Debian/Stable (UltraSparc) seemed to be damaged.
>
> ~$ ls /usr/lib/perl5/XML/Parser
> ls: /usr/lib/perl5/XML/Parser: Input/output error
>
> And I failed to reinstall libxml-
hey folks,
i have a bug report where the amd64 version of a libradiusclient-using
program segfaults, but works fine on i386. my guess is that
this is some kind of 64 vs 32-bit type casting gone wrong somewhere,
and i suspect it's within the radiusclient code itself and not
the plugin (i stumbled
As I understand it, buildds (or is it a separate set of servers?) are
now autocompiling packages in experimental. Where are the logs for
these builds?
Would it be possible to add the experimental build logs to the log pages
at http://buildd.debian.org/build.php ? That would be a really fine
ser
Hi Drew,
On Fri, Jul 28, 2006 at 03:28:13PM +1000, Drew Parsons <[EMAIL PROTECTED]>
wrote:
> As I understand it, buildds (or is it a separate set of servers?) are
> now autocompiling packages in experimental. Where are the logs for
> these builds?
http://experimental.debian.net
--
To UNSUBS
Drew Parsons wrote:
> As I understand it, buildds (or is it a separate set of servers?) are
> now autocompiling packages in experimental. Where are the logs for
> these builds?
http://experimental.ftbfs.de/
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
--
To UNSUBSCRIBE, em
Package: wnpp
Severity: wishlist
Owner: John Wright <[EMAIL PROTECTED]>
* Package name: deb822
Version : 0.1
Upstream Author : Dann Frazier <[EMAIL PROTECTED]>
* URL : http://free.linux.hp.com/~jswright/deb822/trunk
* License : GPL
Programming Lang: Python
On Fri, Jul 28, 2006 at 03:28:13PM +1000, Drew Parsons wrote:
> As I understand it, buildds (or is it a separate set of servers?) are
> now autocompiling packages in experimental.
Experimental is using a different buildd infrastructure than the official
buildds and so do sarge-backports, non-free,
The copyright file is broken. cf. #336982
> deb822 abstractifies the RFC822 format used in Debian's control files. You
> can use a deb822 object like a Python dictionary, referring to control fields
> as dictionary keys.
Is it really worth doing this?
Python readily has rfc822 parsing and the
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 346 (new: 25)
Total number of packages offered up for adoption: 80 (new: 3)
Total number of packages request
* Thomas Viehmann ([EMAIL PROTECTED]) [060728 08:36]:
> The copyright file is broken. cf. #336982
>
> > deb822 abstractifies the RFC822 format used in Debian's control files. You
> > can use a deb822 object like a Python dictionary, referring to control
> > fields
> > as dictionary keys.
>
>
On Fri, 2006-07-28 at 07:57 +0200, Thomas Viehmann wrote:
> Drew Parsons wrote:
> > As I understand it, buildds (or is it a separate set of servers?) are
> > now autocompiling packages in experimental. Where are the logs for
> > these builds?
> http://experimental.ftbfs.de/
>
Thanks for the lin
45 matches
Mail list logo