Re: J.H.M. Dassen (Ray) in <[EMAIL PROTECTED]>
> I intend to orphan xkeycaps.
>
> If you are interested in taking over this package, do let me know.
I'm using this package and I'd take it.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
On Sunday 20 February 2005 23:57, Dirk Eddelbuettel wrote:
> Clint Byrum spamaps.org> writes:
> But then it doesn't matter anymore. These days, Debian is
> "infrastructure". We no longer make releases. We provide the basis from
> which others make releases -- Ubuntu, Prodigy, Knoppix, Custom debi
On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
> Clint Byrum spamaps.org> writes:
> > Now, can someone please tell me how messages like the one below, and
> > others, aren't indicative that debian should drop s390, mipsel, and
> > maybe hppa from the list of architectures? How
On Sun, Feb 20, 2005 at 05:21:50PM -0800, Brian Nelson wrote:
> Also, really huge stuff, like KDE, cannot be uploaded as frequently as
> perhaps the maintainers would like because it kills the slower buildd's
> for a few days.
Hypothetical daily KDE builds would also insanely increase the amount o
On Mon, Feb 21, 2005 at 12:09:16AM -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 20 Feb 2005, Brian Nelson wrote:
> > Also, really huge stuff, like KDE, cannot be uploaded as frequently
> > as perhaps the maintainers would like because it kills the slower
> > buildd's for a few days.
>
> The
Le Lun 21 Février 2005 11:38, Wouter Verhelst a écrit :
> On Sun, Feb 20, 2005 at 05:21:50PM -0800, Brian Nelson wrote:
> > Also, really huge stuff, like KDE, cannot be uploaded as frequently
> > as perhaps the maintainers would like because it kills the slower
> > buildd's for a few days.
>
> Hypo
Wouter Verhelst wrote:
> On Sun, Feb 20, 2005 at 05:21:50PM -0800, Brian Nelson wrote:
> > Also, really huge stuff, like KDE, cannot be uploaded as frequently as
> > perhaps the maintainers would like because it kills the slower buildd's
> > for a few days.
>
> Hypothetical daily KDE builds would a
On Mon, Feb 21, 2005 at 12:04:37PM +0100, Pierre Habouzit wrote:
> I know this raises practical problems (the worst of it not beeing able
> to construct the same packages that are on the archive when starting
> from source+diff). But if one day BW is critical, there is a path to
> explore here.
[Thiemo Seufer]
> Those would need to go into experimental, where no buildd problem
> exists by definition.
I'm told there are some autobuilders for experimental, and believe
your definition of experimental need some adjustment. :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
In article <[EMAIL PROTECTED]> you wrote:
> Hypothetical daily KDE builds would also insanely increase the amount of
> network traffic being used by the mirror pulse and people upgrading
> their home boxes, so it isn't just a buildd problem.
Perhaps it helps, if the buildds for slow systems introd
On Mon, 21 Feb 2005, Wouter Verhelst wrote:
> That would require cross-compilers on the other hosts in the distcc
Not from what I know of dist-cc. You just need dist-cc, and nothing else.
dist-cc just offloads the number-crunching, so it uses no data from the
non-master node. AFAIK anyway (which
On Sat, 2005-02-19 at 23:06 -0600, Micah Anderson wrote:
>#957: dpkg 957 802533782 open [EMAIL PROTECTED] wishlist
>
Do I get a medal when I fix this in the next week or two? :) I've been
working on an implementation over the weekend that's to my liking.
Scott
--
Have you ever, ever felt like t
Petter Reinholdtsen wrote:
> [Thiemo Seufer]
> > Those would need to go into experimental, where no buildd problem
> > exists by definition.
>
> I'm told there are some autobuilders for experimental,
And how would missing builds there be a problem?
> and believe your definition of experimental n
* Petter Reinholdtsen ([EMAIL PROTECTED]) [050221 12:30]:
> [Thiemo Seufer]
> > Those would need to go into experimental, where no buildd problem
> > exists by definition.
> I'm told there are some autobuilders for experimental, and believe
> your definition of experimental need some adjustment. :
> There are a few reasons why we usually avoid cross-compilers for buildd
> purposes. For one, as one cannot as easily test a cross-compiler by
> running a test suite, it may have been miscompiled -- but you wouldn't
> notice; this would result in strange, hard to debug behaviour by the
> resulting
[Peter 'p2' De Schrijver]
> This can be solved by using emulation tools (like
> qemu). Unfortunately qemu doesn't support m68k as a target yet. It
> would not only help for cross buildd's, but also allow maintainers
> to debug arch specific problems in their package on their laptop :)
For m68k, th
On Mon, Feb 21, 2005 at 11:49:46AM +0100, Thiemo Seufer wrote:
> Wouter Verhelst wrote:
> > On Sun, Feb 20, 2005 at 05:21:50PM -0800, Brian Nelson wrote:
> > > Also, really huge stuff, like KDE, cannot be uploaded as frequently as
> > > perhaps the maintainers would like because it kills the slower
On Mon, Feb 21, 2005 at 12:16:38PM +0100, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > Hypothetical daily KDE builds would also insanely increase the
> > amount of network traffic being used by the mirror pulse and people
> > upgrading their home boxes, so it isn't just a
On Mon, 2005-02-21 at 13:36 +0100, Wouter Verhelst wrote:
> On Mon, Feb 21, 2005 at 12:16:38PM +0100, Bernd Eckenfels wrote:
> > In article <[EMAIL PROTECTED]> you wrote:
[snip]
> The problem with s390 is that you can't just go to eBay and buy yourself
> an s390; or even if you could, that you woul
On Mon, Feb 21, 2005 at 12:33:24AM +0100, Goswin von Brederlow wrote:
> Dropping some archs would only have one benefit. There would be mirror
> space to include amd64.
Well, that's quite a compelling reason. It's embarassing that amd64 won't
be official in sarge.
Hamish
--
Hamish Moffatt VK3SB
[Steve Langasek]
> The four most common porting problems for software are endianness
> (differs between i386/amd64 and powerpc), word size (differs between
> i386/powerpc and amd64), char signedness (differs between i386/amd64
> and powerpc), and use of non-PIC code in shared libs (which is a
> pr
[Henrique de Moraes Holschuh]
> Not from what I know of dist-cc. You just need dist-cc, and nothing
> else. dist-cc just offloads the number-crunching, so it uses no data
> from the non-master node. AFAIK anyway (which is NOT much on dist-cc
> matters).
Right. distcc runs the C preprocessor o
[Pierre Habouzit]
> I mean that you have no way to say for huge source packages : you
> only need to build this , this, this and this pacakge. since the
> changes I've made won't affect the others.
As far as mirror bandwidth goes (including end user bandwidth *from*
the mirrors), that's a problem
Le Lun 21 Février 2005 14:13, Peter Samuelson a écrit :
> [Pierre Habouzit]
>
> > I mean that you have no way to say for huge source packages : you
> > only need to build this , this, this and this pacakge. since the
> > changes I've made won't affect the others.
>
> As far as mirror bandwidth goes
[Pierre Habouzit]
> > As far as mirror bandwidth goes (including end user bandwidth *from*
> > the mirrors), that's a problem for rsync/zsync to solve.
>
> 1- binary backages do not have the same name (so rsync/apt-get are lost)
It's still a problem for rsync/zsync to solve. I didn't mean to sa
> The main problem with distcc across architectures is the FUD
> surrounding whether gcc-as-cross-compiler spits out the same code as
> gcc-as-native-compiler. The gcc team seem to be very hesitant to make
> any guarantees about that, as it's not something they test much.
> Without better inform
On Mon, Feb 21, 2005 at 07:25:02AM -0600, Peter Samuelson wrote:
> zsync already reaches inside a gzip file and effectively rsyncs the
> uncompressed version. No reason it couldn't be made a bit smarter so
> as to look inside the components of a .deb ar file. This being a
> fairly interesting use
On Mon, Feb 21, 2005 at 11:00:03 +0100, Christoph Berg wrote:
> I'm using this package and I'd take it.
Thank you Christoph, it's yours.
Ray
--
"My golden rule of computing is reboot your system every morning."
Jon C.A. DeKeles, Technical Director, ZDNet AnchorDesk
in http://www.
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> But at the moment, there are very few problems with the autobuilders,
> it seem. The packages with missing builds on some archs are listedon
> http://developer.skolelinux.no/info/cdbygging/distdiff-all.html.gz>,
> and it is not bad compared to ear
Package: wnpp
Severity: wishlist
Owner: Grzegorz Bizon <[EMAIL PROTECTED]>
* Package name: tarp
Version : 0.9
Upstream Author : Michal Kwiatkowski <[EMAIL PROTECTED]>
* URL : http://joker.linuxstuff.pl
* License : GPL
Description : small script adding pro
Wouter Verhelst <[EMAIL PROTECTED]> writes:
> On Mon, Feb 21, 2005 at 12:09:16AM -0300, Henrique de Moraes Holschuh wrote:
>> On Sun, 20 Feb 2005, Brian Nelson wrote:
>> > Also, really huge stuff, like KDE, cannot be uploaded as frequently
>> > as perhaps the maintainers would like because it kill
Peter Samuelson <[EMAIL PROTECTED]> writes:
> [Pierre Habouzit]
>> > As far as mirror bandwidth goes (including end user bandwidth *from*
>> > the mirrors), that's a problem for rsync/zsync to solve.
>>
>> 1- binary backages do not have the same name (so rsync/apt-get are lost)
>
> It's still a p
Robert Lemmen <[EMAIL PROTECTED]> writes:
> On Mon, Feb 21, 2005 at 07:25:02AM -0600, Peter Samuelson wrote:
>> zsync already reaches inside a gzip file and effectively rsyncs the
>> uncompressed version. No reason it couldn't be made a bit smarter so
>> as to look inside the components of a .deb
Thiemo Seufer <[EMAIL PROTECTED]> writes:
> Those would need to go into experimental, where no buildd problem
> exists by definition.
>
>
> Thiemo
Except for the 11 archs with experimental buildds.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
Hi,
A new version of the zaptel package can be found in experimental, it
tries to fix various bugs, I would appreciate any help to test it.
Thanks a lot,
--
Santiago Ruano RincÃn
Grupo GNU/Linux Universidad del Cauca
Avatar LTDA.
Llave pÃblica GPG ID = 6FECCDE0
Huella digital = 3821 4FB5 774A
Quoting Hendrik Frenzel <[EMAIL PROTECTED]>:
> Provides: pack-gui-lang-de, pack-gui-lang
> Conflicts: pack-gui-lang-de
Adding the following line to the ones above should do it:
Replaces: pack-gui-lang-de
--
$400 million in gold bullion Honduras president radar [Hello to all my
fans in d
Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]> you wrote:
>> Hypothetical daily KDE builds would also insanely increase the amount of
>> network traffic being used by the mirror pulse and people upgrading
>> their home boxes, so it isn't just a buildd problem.
>
> Per
Scott James Remnant <[EMAIL PROTECTED]> writes:
> On Sat, 2005-02-19 at 23:06 -0600, Micah Anderson wrote:
>
>>#957: dpkg 957 802533782 open [EMAIL PROTECTED] wishlist
>>
> Do I get a medal when I fix this in the next week or two? :) I've been
> working on an implementation over the weekend that'
Petter Reinholdtsen wrote:
[snip]
> But at the moment, there are very few problems with the autobuilders,
> it seem. The packages with missing builds on some archs are listedon
> http://developer.skolelinux.no/info/cdbygging/distdiff-all.html.gz>,
> and it is not bad compared to earlier.
>
> Mi
Re: Grzegorz Bizon in <[EMAIL PROTECTED]>
> * Package name: tarp
> * URL : http://joker.linuxstuff.pl
> Description : small script adding progress bar support for GNU tar
>
> Simple perl script adding progress bar support
> for GNU tar.
Hi,
I'd say this is way to small to
[EMAIL PROTECTED] wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Grzegorz Bizon <[EMAIL PROTECTED]>
>
>
>* Package name: tarp
> Version : 0.9
> Upstream Author : Michal Kwiatkowski <[EMAIL PROTECTED]>
>* URL : http://joker.linuxstuff.pl
>* License : GPL
> Descr
Hi all,
I have a local mirror of sarge here at work for making custom install
cds. My mirror is a copy of the mirror at heanet (ftp.ie.debian.org). I
have noticed incorrect checksums on 8 packages and I am posting the
details here in case this is a serious problem. Hopefully someone more
knowle
Marek Habersack wrote:
> It's just a simple question/request. Would it be possible to include
> custom headers in the messages sent to debian-devel-changes that would
> contain the package name, version and distribution, like so:
>
> X-Debian-Package: foo
> X-Debian-PackageVersion: 1.2.3-1
>
On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> Bernd Eckenfels <[EMAIL PROTECTED]> writes:
>
> > In article <[EMAIL PROTECTED]> you wrote:
> >> Hypothetical daily KDE builds would also insanely increase the amount of
> >> network traffic being used by the mirror pulse and
#include
* Christoph Berg [Mon, Feb 21 2005, 04:13:09PM]:
> > Simple perl script adding progress bar support
> > for GNU tar.
>
> Hi,
>
> I'd say this is way to small to justify a package for it. Did you try
> to contact the tar maintainer to get it included there?
Agreed. However, I though
Re: Eduard Bloch in <[EMAIL PROTECTED]>
> Agreed. However, I though about writting cp/mv versions that display
> progress bars and allow interactive "resuming" of copy operations. I
> think such things together with ptar could go into some kind of
> "interactive-command-line-tools" package.
rsync
On Mon, Feb 21, 2005 at 03:28:10AM +, Henning Makholm wrote:
> Scripsit Bill Allombert <[EMAIL PROTECTED]>
> > Actually, there might be no need for virtual packages, since the tool
> > will be run at compile time and can look up which libc is in use.
>
> Libc would not be the only thing decide
Ben Armstrong wrote:
I question, then, the integrity of ftp.ie.debian.org or your own mirror.
Just checking one of my own packages, I obtained a copy from my local
mirror, and this is the result:
$ extract -H md5 xpilot-client-nosound_4.5.5beta.20031222-1_i386.deb
MD5 - 3cfe83e6a25995d17d568737c3c
John,
On Mon, 2005-02-21 at 15:24 +, John O'Sullivan wrote:
> My mirror is a copy of the mirror at heanet (ftp.ie.debian.org). I
> have noticed incorrect checksums on 8 packages and I am posting the
> details here in case this is a serious problem.
I question, then, the integrity of ftp.ie.
Thats pretty much what the guy in HEAnet just said to me but the length
of the files is the same. He says that the tcp checksums aren't accurate
enough for 100% correctness.
I'm emailing him some details now.
cheers,
johno
Ben Armstrong wrote:
John,
Have you considered the possibility that the p
John,
Have you considered the possibility that the packages are corrupt due to
truncation which may have happened because you (or your mirror) ran out
of space at some point in the past while downloading these packages?
The package names are late in the alphabet, which might account for why
only t
John O'Sullivan <[EMAIL PROTECTED]> writes:
> Ben Armstrong wrote:
>
>>I question, then, the integrity of ftp.ie.debian.org or your own mirror.
>>
>>Just checking one of my own packages, I obtained a copy from my local
>>mirror, and this is the result:
>> $ extract -H md5 xpilot-client-nosound_4.5
We thank you for contacting us. We will be answering your question and/or
concern just as soon as
possible. We do our best to answer on the same day, but it can take up to 48
hours, so if you need
immediate assistance, please call us at 954-585-6114. In the meantime, please
visit our eBay Stor
Sorry for the false alarm. Those files were only corrupted. HEAnet have
resynced them now and all is good. Sorry for wasting ppls time.
johno
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> > In article <[EMAIL PROTECTED]> you wrote:
> What would help save many hours on slow systems is having a script
> automatically set "Dep-Wait: libbfoo (>> 1.2-3)" for all new sourc
On Sun, 2005-02-20 at 19:16 -0600, David Moreno Garza wrote:
> Package: wnpp
> Severity: wishlist
> Owner: David Moreno Garza <[EMAIL PROTECTED]>
>
>
> * Package name: xchat-systray
> Version : 2.4.5
> Upstream Author : Patrizio Bassi <[EMAIL PROTECTED]>
> * URL : http
Package: wnpp
Severity: wishlist
Owner: Guillaume Pellerin <[EMAIL PROTECTED]>
* Package name: qoscc
Version : 0.2.0
Upstream Author : tincan
* URL : http://www.svenqueisser.de/qoscc.html
* License : GPL
Description : a highly flexible software oscillosc
On Mon, 2005-02-21 at 17:31 +, John O'Sullivan wrote:
> Sorry for the false alarm. Those files were only corrupted. HEAnet have
> resynced them now and all is good. Sorry for wasting ppls time.
I'm just happy that people are looking for this sort of thing. It is
encouraging that if were a re
#include
* Christoph Berg [Mon, Feb 21 2005, 04:46:14PM]:
> Re: Eduard Bloch in <[EMAIL PROTECTED]>
> > Agreed. However, I though about writting cp/mv versions that display
> > progress bars and allow interactive "resuming" of copy operations. I
> > think such things together with ptar could go in
On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
> On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
> > But a total of eleven is insane.
>
> It is sometimes hard to get them all to work, yes.
>
> It also vastly increases the quality of the Free Software in our
>
On Mon, 2005-02-21 at 11:13 -0800, Brian Nelson wrote:
> On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
> > On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
> > > But a total of eleven is insane.
> >
> > It is sometimes hard to get them all to work, yes.
> >
>
Brian Nelson writes:
> That's an overstatement. Simply having two architectures (i386 and ppc)
> would be enough to reveal nearly all portability bugs.
It required several architectures to uncover all of the portability bugs in
Chrony. ppc was not one of them.
--
John Hasler
--
To UNSUBSCRIB
Am Sonntag, den 20.02.2005, 11:02 +0100 schrieb Goswin von Brederlow:
> Hendrik Frenzel <[EMAIL PROTECTED]> writes:
> > If I have a source pack-1.1 from which some packages including
> > pack-gui-lang-de-1.1_2 (Provides: pack-gui-lang) are build.
> >
> > Now i want to build the languages in sepera
Brian Nelson wrote:
> On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
> > On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
> > > But a total of eleven is insane.
> >
> > It is sometimes hard to get them all to work, yes.
> >
> > It also vastly increases the qual
Peter Samuelson <[EMAIL PROTECTED]> writes:
> [Steve Langasek]
>> The four most common porting problems for software are endianness
>> (differs between i386/amd64 and powerpc), word size (differs between
>> i386/powerpc and amd64), char signedness (differs between i386/amd64
>> and powerpc), and u
Welcome to Americas newest insurance referral network.
We offer term-life coverage at up to 70% off.
Just cl.ck here: http://www.up6.org/link.php?id=erci&ID=11
We survey the top life-insurance companies and provide the
best-rates available today.
Smokers will qualify for special rates. - Cl.ck
Eduard Bloch <[EMAIL PROTECTED]> writes:
> #include
> * Christoph Berg [Mon, Feb 21 2005, 04:46:14PM]:
>> Re: Eduard Bloch in <[EMAIL PROTECTED]>
>> > Agreed. However, I though about writting cp/mv versions that display
>> > progress bars and allow interactive "resuming" of copy operations. I
>>
John Hasler <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>> That's an overstatement. Simply having two architectures (i386 and ppc)
>> would be enough to reveal nearly all portability bugs.
>
> It required several architectures to uncover all of the portability bugs in
> Chrony. ppc was no
On Mon, 2005-02-21 at 11:13 -0800, Brian Nelson wrote:
>On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
>> On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
>> > But a total of eleven is insane.
>>
>> It is sometimes hard to get them all to work, yes.
>>
>> It al
Package: wnpp
Severity: wishlist
* Package name: libcgi-simple-perl
Version : 0.077
Upstream Author : Dr James Freeman <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/~jfreeman/Cgi-Simple-0.077/
* License : Perl Artistic License
Description : simple to
Hi all,
This is just a note for anyone who's looking for a project. I was just
trying to compile some software, and it bombed out because I didn't have the
right ClanLib version installed. I looked into the matter a little, and
found a nearly two-year-old bug (#188449) asking for the libr
Jim Gettys <[EMAIL PROTECTED]> writes:
> On Mon, 2005-02-21 at 11:13 -0800, Brian Nelson wrote:
>> On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
>> > On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
>> > > But a total of eleven is insane.
>> >
>> > It is somet
On Friday 31 December 2021 08:38 am, Eduardo Marcel Macan wrote:
I call dibs on his time machine ;-)
Daniel
--
/--- Daniel Burrows <[EMAIL PROTECTED]> --\
| Microsoft, n: |
| A comp
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> John Hasler <[EMAIL PROTECTED]> writes:
>
>> Brian Nelson writes:
>>> That's an overstatement. Simply having two architectures (i386 and ppc)
>>> would be enough to reveal nearly all portability bugs.
>>
>> It required several architectures to un
On Mon, 2005-02-21 at 16:12 -0800, Brian Nelson wrote:
> Yeah, definitely. If our goal is making our software as portable and
> bug-free as possible, we'd be better off running fewer arches but with a
> greater variety of compilers.
>
> Now if there were only any viable free alternatives to GCC..
Package: wnpp
Severity: wishlist
Owner: Eike Dehling <[EMAIL PROTECTED]>
* Package name: spin
Version : 4.2.4
Upstream Author : Bell-Labs <[EMAIL PROTECTED]>
* URL : http://www.spinroot.com/
* License : Free(as in, no license) for non-commercial use, commercial
On Tue, Feb 22, 2005 at 02:31:03AM +0100, Eike Dehling wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Eike Dehling <[EMAIL PROTECTED]>
>
>
> * Package name: spin
> Version : 4.2.4
> Upstream Author : Bell-Labs <[EMAIL PROTECTED]>
> * URL : http://www.spinroot.com
Brian Nelson debian.org> writes:
> On Mon, Feb 21, 2005 at 11:33:35AM +0100, Wouter Verhelst wrote:
> > On Sun, Feb 20, 2005 at 10:57:47PM +, Dirk Eddelbuettel wrote:
> > > But a total of eleven is insane.
> >
> > It is sometimes hard to get them all to work, yes.
> >
> > It also vastly incr
On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> What would help save many hours on slow systems is having a script
> automatically set "Dep-Wait: libbfoo (>> 1.2-3)" for all new sources
> according to Build-Depends to prevent useless buildd attempts and
> failures and manual
On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote:
> But to the best of my knowledge, Marco's (blog) post from a few months
> ago which showed download from ftp.it.debian.org by architecture stands
> undisputed: essentially all users are on i386 clearly dominating all other
> ar
On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote:
> undisputed: essentially all users are on i386 clearly dominating all other
> arches, with a fraction of users in maybe two, three, four other arches ---
> and comparitively nobody in the other fringe arches we keep around for n
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> Brian Nelson debian.org> writes:
>> And for the more obscure architectures, virtually all of the testing
>> comes from the build of the package. How many people out there are
>> actually using e.g. KDE on mips enough to actually find any portabilit
Find yerself a queen on real soon
http://underpartnerbrachycatalectic.com/sse/
rm0ve : underpartnerbrachycatalectic.com/yap/
The metalliferous adiabatic ks comeback .
She rev blackball anton luke dextrose .
likewise sse woeful loft accolade diane .
amp apprentice chou bater .
The beo
Matthew Palmer debian.org> writes:
> On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote:
> > undisputed: essentially all users are on i386 clearly dominating all other
> > arches, with a fraction of users in maybe two, three, four other arches ---
> > and comparitively nobody in
On Mon, Feb 21, 2005 at 04:30:27PM +0100, Wouter Verhelst wrote:
> On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> > Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> >
> > > In article <[EMAIL PROTECTED]> you wrote:
> > >> Hypothetical daily KDE builds would also insanely incr
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> But to the best of my knowledge, Marco's (blog) post from a few months
> ago which showed download from ftp.it.debian.org by architecture stands
> undisputed: essentially all users are on i386 clearly dominating all other
> arches, with a fractio
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> I was quoting a post with actual download numbers that actually demonstrate
> that the vast majority of users are on i386: see http://blog.bofh.it/id_66.
But that doesn't show what you said you believe, which is that
supporting other archs slows th
Marc Singer <[EMAIL PROTECTED]> writes:
> It does seem prudent to find a way to permit a release on x86 and
> ppc before all architectures are complete. Especially if this
> tactic will give Debian the ability to release more often. Is it so
> bad to allow the smaller architectures to lag as lon
On Mon, Feb 21, 2005 at 08:56:27PM -0800, Thomas Bushnell BSG wrote:
> Marc Singer <[EMAIL PROTECTED]> writes:
>
> > It does seem prudent to find a way to permit a release on x86 and
> > ppc before all architectures are complete. Especially if this
> > tactic will give Debian the ability to relea
On Tue, Feb 22, 2005 at 04:39:22AM +, Dirk Eddelbuettel wrote:
> Matthew Palmer debian.org> writes:
> > On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote:
> > > undisputed: essentially all users are on i386 clearly dominating all
> > > other
> > > arches, with a fraction of
Matthew Palmer debian.org> writes:
[ a lot of stuff but omitting one critical argument of mine ]
Thanks for cutting and completely ignoring the part where I demonstrated
the lack of usage beyond i386 and maybe four or five other arches.
I rest my case. These arches have little benefit, but as
On Tue, 22 Feb 2005, Dirk Eddelbuettel wrote:
> Thanks for cutting and completely ignoring the part where I
> demonstrated the lack of usage beyond i386 and maybe four or five
> other arches.
You used package download results from one (1!) debian mirror to
demonstrate the supposed lack of usage. H
On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote:
> But to the best of my knowledge, Marco's (blog) post from a few months
> ago which showed download from ftp.it.debian.org by architecture stands
> undisputed: essentially all users are on i386 clearly dominating all other
> a
On 21 Feb 2005 20:54:36 -0800, Thomas Bushnell BSG <[EMAIL PROTECTED]>
wrote:
>Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
>> - security response time (more builds to do)
>
>Which DSAs came out later than they should have because of this
>supposed delay? Nor could this possibly slow release.
Th
On Tue, Feb 22, 2005 at 02:29:33PM +1100, Hamish Moffatt wrote:
> On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> > What would help save many hours on slow systems is having a script
> > automatically set "Dep-Wait: libbfoo (>> 1.2-3)" for all new sources
> > according to Bu
On Tue, Feb 22, 2005 at 05:24:28AM +, Dirk Eddelbuettel wrote:
> Matthew Palmer debian.org> writes:
> [ a lot of stuff but omitting one critical argument of mine ]
> Thanks for cutting and completely ignoring the part where I demonstrated
> the lack of usage beyond i386 and maybe four or five
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> Thanks for cutting and completely ignoring the part where I demonstrated
> the lack of usage beyond i386 and maybe four or five other arches.
"lack of usage" here means "much rarer usage" of course. .001 is not
zero.
And your point was supposedly
On Mon, Feb 21, 2005 at 11:40:07AM +, Scott James Remnant wrote:
> On Sat, 2005-02-19 at 23:06 -0600, Micah Anderson wrote:
>
> >#957: dpkg 957 802533782 open [EMAIL PROTECTED] wishlist
> >
> Do I get a medal when I fix this in the next week or two? :) I've been
> working on an implementation
On Mon, Feb 21, 2005 at 07:10:36AM -0600, Peter Samuelson wrote:
> The main problem with distcc across architectures is the FUD
> surrounding whether gcc-as-cross-compiler spits out the same code as
> gcc-as-native-compiler. The gcc team seem to be very hesitant to make
> any guarantees about tha
99 matches
Mail list logo
