Re: Using standardized SI prefixes
On Thu, Jun 21, 2007 at 01:11:52PM +1000, Hamish Moffatt wrote: > I think Ben's point is that we don't know. > > You seem to claim that binary units (ie powers of 2) are natural > everywhere related to computers, but I disagree. It's natural for > memory and structures like it, but not for bitstream quantities like > network traffic. But they don't use powers of 10 any more than they do powers of 10. While bps speeds are an oft-quoted case that "always" use powers of 10, the connection I got here is guaranteed min=max 1Mbps which as far as I can measure it goes right at 1048576 bits per second, rain or sleet. And the ISP is one of the most despicable, cheating, greedy ones you can imagine -- for example our company pays for that 1Mbps more than in a civilised place you would pay for 100Mbps, so if they seen a place to overadvertise something, they would. And as far as I know, usually 1Mbps stands for 1024x1000 bits where network speeds are concerned, to be wrong by both the correct and yours interpretation :p -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Self healing Debian ISO downloads with multiple fallback URLs (mirrors & checksums)
Hi, I've posted about this before, but Metalinks are available for Debian 4.0 ISOs now thanks to Manuel @ ftp.iasi.roedu.net. Metalinks contain checksums, mirror lists, and other metadata in an XML format. They're used by around 13 download programs such as download managers. http://download.packages.ro/metalink/debian/ http://download.packages.ro/metalink/debian/collections/ (Collection metalinks contain all the ISOs for an architecture). The best metalink client is aria2 (apt-get install aria2, http://aria2.sourceforge.net/ ) because it uses the chunk checksums to repair files. Nightly builds (use at own risk) of DownThemAll!, a Firefox extension, are convenient but only check full file checksums and can't repair downloads. In this screenshot, the icon/logo, description, publisher, license, OS/arch, & other info are taken from the metalink. http://code.downthemall.net/maierman/metaselect4.png http://bugs.code.downthemall.net/trac/wiki/NightlyBuilds -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429914: ITP: openfire -- XMPP/Jabber server written in Java
Package: wnpp Severity: wishlist Owner: Lucas Nussbaum <[EMAIL PROTECTED]> * Package name: openfire Version : 3.3.1 Upstream Author : Jive Software <[EMAIL PROTECTED]> * URL : http://www.igniterealtime.org/projects/openfire/ * License : mostly GPL, but there are nice license issues Programming Lang: Java Description : XMPP/Jabber server written in Java Openfire is an XMPP/Jabber server written in Java. It is very easy to setup and to administer. There's a preliminary package available at (with svn) http://svn.igniterealtime.org/svn/repos/openfire/trunk/build/debian but it still need some work. There's an entry in IgniteRealtime's issue tracker where the discussion happens: http://www.igniterealtime.org/issues/browse/JM-765 Lucas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429913: ITP: oar -- resource manager (batch scheduler) for HPC clusters
Package: wnpp Severity: wishlist Owner: Lucas Nussbaum <[EMAIL PROTECTED]> * Package name: oar Version : 2.0 Upstream Author : Nicolas Capit <[EMAIL PROTECTED]> * URL : http://oar.imag.fr/ * License : GPL Programming Lang: Perl mostly Description : resource manager (batch scheduler) for HPC clusters OAR is a batch scheduler for high performance computing clusters. It serves the same purposes as software like PBS, Torque, LSF, Sun Grid Engine, ... There's a preliminary package available at svn://scm.gforge.inria.fr/svn/oar/Debian/trunk/ , but it still needs a lot of work, since the package is quite complex (lots of non-trivial interactions with a lot of stuff). Comaintainers are totally welcomed. in fact, it could be a nice opportunity to create a HPC/Grid team... Lucas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Using standardized SI prefixes
Dear Friends and colleagues, I am a newbie on this list and Linux but an oldie when it comes to IT industry. Can i highlight that the main attraction of ubuntu amongst all other Linux derivates is its accessibility to end users. For this feature to continue to flourish it is best if everything from the bottom up is standardise towards the final goal of presenting it to the ordinary end user. In today's world unfortunately presentation does matter a great deal more than its worth, but that is the reality. Kind Regards Farjad http://www.checknetworks.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sam Morris Sent: Thursday, June 21, 2007 2:27 AM To: [EMAIL PROTECTED] Cc: debian-devel@lists.debian.org Subject: Re: Using standardized SI prefixes On Wed, 20 Jun 2007 20:11:23 -0400, Ivan Jager wrote: > How many packages can you name that measure bytes in powers of 10? Are > there any? debian-installer does so (unless you are creating LVM Logical Volumes, in which case the units that you specify volume sizes in are base-2, but the units that volume sizes are displayed in remain baase-10)... :) -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- Ubuntu-devel-discuss mailing list [EMAIL PROTECTED] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Archive rebuild with improved dpkg-shlibdeps
Hello, Lucas just rebuilt the archive with my new dpkg-shlibdeps and the symbols file that I provided him (http://people.debian.org/~hertzog/symbols.tar.bz2) and that I auto-generated. The resulting Packages file is here: http://people.debian.org/~hertzog/Packages.gz (it contains only binary-i386 and not the binary-all packages). The build logs of this rebuild are available on gluck: http://people.debian.org/~lucas/logs/2007/06/19/sym/ You can check the build log of your packages and maybe you'll see warnings like those: dpkg-shlibdeps: warning: debian/a2ps/usr/bin/fixnt shouldn't be linked with libpaper.so.1 ( it uses none of its symbols). -> you could fix the build process so that it doesn't include "-lpaper" ace-of-penguins_1.2-8_sid32.buildlog:dpkg-shlibdeps: warning: Symbol [EMAIL PROTECTED] used by debian/ace-of-penguins/usr/lib/libcards.so.1.0.0 found in none of the libraries. -> here's you have the opposite problem, this library uses symbols from another library without being linked with it. You need to the appropriate "-l" flag (in this case -lX11). If you encounter any strangeness, please report it so that we can check. Those warnings could be the base of some mass-bug filings althought we might want to start with the second one (those are real bugs, while the other are not creating any technical problem (except useless dependencies)). Cheers, PS: Those who don't understand what this is about, check out http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#429888: networking broken after install
Processing commands for [EMAIL PROTECTED]: > reassign 429888 general Bug#429888: networking broken after install Warning: Unknown package 'unknown' Bug reassigned from package `unknown' to `general'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429941: ITP: grandr -- gtk interface to xrandr
Package: wnpp Severity: wishlist Owner: David Nusinow <[EMAIL PROTECTED]> Package name: grandr Version : 0.1 Upstream Author : Intel Corporation, hosted at X.org URL : http://www.x.org/ License : MIT/X11 Programming Lang: C Description : gtk interface to xrandr A simple gtk interface to the X Resize And Roate (XRandR) extension. This allows you change the resolution and frequency of your monitor dynamically using a simple interface. For drivers that support it, it can also configure the relative positioning of multiple monitors. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-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: Archive rebuild with improved dpkg-shlibdeps
[Raphael Hertzog] > If you encounter any strangeness, please report it so that we can > check. Those warnings could be the base of some mass-bug filings > althought we might want to start with the second one (those are real > bugs, while the other are not creating any technical problem (except > useless dependencies)). Please do not file bugs for unnecessary linking _except_ where this actually changes the Depends line. In many cases upstream might link several binaries against a fixed list of libraries, where not every binary needs every library. This is generally quite annoying to "fix", and is not worth the trouble, since it doesn't affect package relationships or install/remove/upgrade scenarios. Also, please omit @Base from the log messages, it adds visual clutter without adding information. -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ signature.asc Description: Digital signature
Re: Archive rebuild with improved dpkg-shlibdeps
On Thu, Jun 21, 2007 at 09:59:53AM +0100, Raphael Hertzog wrote: > Hello, > > Lucas just rebuilt the archive with my new dpkg-shlibdeps and the symbols > file that I provided him > (http://people.debian.org/~hertzog/symbols.tar.bz2) and that I > auto-generated. > > The resulting Packages file is here: > http://people.debian.org/~hertzog/Packages.gz (it contains only > binary-i386 and not the binary-all packages). > > The build logs of this rebuild are available on gluck: > http://people.debian.org/~lucas/logs/2007/06/19/sym/ > > You can check the build log of your packages and maybe you'll see warnings > like those: > dpkg-shlibdeps: warning: debian/a2ps/usr/bin/fixnt shouldn't be linked with > libpaper.so.1 ( it uses none of its symbols). > -> you could fix the build process so that it doesn't include "-lpaper" > > ace-of-penguins_1.2-8_sid32.buildlog:dpkg-shlibdeps: warning: Symbol [EMAIL > PROTECTED] used by debian/ace-of-penguins/usr/lib/libcards.so.1.0.0 found in > none of the libraries. > -> here's you have the opposite problem, this library uses symbols from > another library without being linked with it. You need to the appropriate > "-l" flag (in this case -lX11). This seems to do simular things as checklib (http://rerun.lefant.net/checklib/), which gives simular warnings and errors. It could be useful to compare those results. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#429950: ITP: sieve-connect -- A client for the MANAGESIEVE protocol
Package: wnpp Severity: wishlist Owner: Andrew Pollock <[EMAIL PROTECTED]> * Package name: sieve-connect Version : 0.33 Upstream Author : Phil Pennock <[EMAIL PROTECTED]> * URL : http://people.spodhuis.org/phil.pennock/software * License : BSD Programming Lang: Perl Description : A client for the MANAGESIEVE protocol This is sieve-connect. A client for the MANAGESIEVE protocol, as implemented by timsieved in Cyrus IMAP. . sieve-connect is designed to be both a tool which can be invoked from scripts and also a decent interactive client. It should also be a drop-in replacement for "sieveshell", as supplied with Cyrus IMAP. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Nexuiz 2.3
someone who prefers to remain anonymous writes:
> Reinhard Tartler wrote:
>> Sorry? Nexuiz 2.3 is already package by the debian games team, uploaded
>> to unstable and requested to be synced to gutsy by my, and available in
>> both distros. What are you exactly requesting?
>
> I'm on X86, 32-bit, Debian, Lenny.
That information would have been helpful in the first email
> Ok, there are three packages to Nexuiz.
> Nexuiz
> Nexuiz-data
> Nexuiz-music
>
> In unstable, all of these packages have the version 2.3-1
> In testing, the nexuiz-data and nexuiz-music packages have the version
> 2.3-1, *however* the nexuiz package in testing is at version 2.2.3-1
>
> The nexuiz package itself is quite important as it installs a 'bin' file
> which contains the game engine, so this version in testing is not at
> 2.3-1, it's still at 2.2.3-1
>
> Look here if you'd like to check the repository site.
> http://packages.debian.org/cgi-bin/search_packages.pl?keywords=nexuiz&searchon=names&subword=1&version=all&release=all
>
> Put simply, the game engine of v2.3 isn't in testing, it looks like a
> mistake on the packaging side. The nexuiz package has a bin file, and
> that's at v2.2.3-1. Can you check this out?
Yes. Generally, I recommend people running debian testing to have both
testing and unstable in their sources.list, and pin apt to testing. In
this particular case:
[EMAIL PROTECTED]:~ $ grep-excuses nexuiz
grep-excuses nexuiz
nexuiz (2.2.3-1 to 2.3-1)
Maintainer: Debian Games Team
13 days old (needed 10 days)
out of date on sparc: nexuiz, nexuiz-server (from 2.2.3-1)
Not considered
Depends: nexuiz curl
Both packages have been uploaded at the same time, and I could not
forsee that it has still not been built and uploaded on sparc on time. I
think to avoid this situation in the future the correct way was to use
a versioned "Breaks" field on nexuiz-data:
Breaks: nexuiz (<< 2.3)
apt now has support for breaks, dpkg will get it on the next upload I
think, I'm not sure if britney needs to be extended for this as well.
CC'ing debian-{games,[EMAIL PROTECTED] for comments if I'm right here.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
pgpzoD60WcPGG.pgp
Description: PGP signature
Re: Bug#429801: ITP: libclass-accessor-grouped-perl -- build groups of accessors
On Wed, Jun 20, 2007 at 08:53:24PM +1000, Hamish Moffatt wrote: > On Wed, Jun 20, 2007 at 11:55:33AM +0200, Krzysztof Krzyzaniak (eloy) wrote: > > Package: wnpp > > Severity: wishlist > > Owner: "Krzysztof Krzyzaniak (eloy)" <[EMAIL PROTECTED]> > > > > > > * Package name: libclass-accessor-grouped-perl > > Version : x.y.z > > URL : http://www.cpan.org/ > > * Upstream Author : Matt S. Trout <[EMAIL PROTECTED]> > > Christopher H. Laco <[EMAIL PROTECTED]>. > > * License : Perl: Artistic/GPL > > Programming Lang: Perl > > Description : build groups of accessors > > > > Class::Accessor::Grouped lets you build groups of accessors that will call > > different getters and setters. > > Are all these weird and whacky new Perl module packages in aid of > something, ie are they about to become reverse dependencies of some new > package? > Do they have to be? I know that I would personally prefer to apt-get install some Perl module, rather than install it myself from CPAN or some other source. It makes life much easier when one manages many machines. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Nexuiz 2.3
On Thu, Jun 21, 2007 at 01:39:41PM +0100, [EMAIL PROTECTED] wrote: > Both packages have been uploaded at the same time, and I could not > forsee that it has still not been built and uploaded on sparc on time. I > think to avoid this situation in the future the correct way was to use > a versioned "Breaks" field on nexuiz-data: > > Breaks: nexuiz (<< 2.3) I might have completely missed your point, but if you have nexuiz-data Depends on nexuiz (2.3), then it wouldn't get installed, would it ? Or is there a problem to have nexuiz Depends nexuiz-data (2.3) and nexuiz-data Depends on nexuiz (2.3) ? Regards, Vincent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Nexuiz 2.3
On 21/06/2007 [EMAIL PROTECTED] wrote: > On Thu, Jun 21, 2007 at 01:39:41PM +0100, [EMAIL PROTECTED] wrote: > > Both packages have been uploaded at the same time, and I could not > > forsee that it has still not been built and uploaded on sparc on time. I > > think to avoid this situation in the future the correct way was to use > > a versioned "Breaks" field on nexuiz-data: > > > > Breaks: nexuiz (<< 2.3) > > I might have completely missed your point, but if you have nexuiz-data > Depends on nexuiz (2.3), then > it wouldn't get installed, would it ? Or is there a problem to have nexuiz > Depends nexuiz-data (2.3) > and nexuiz-data Depends on nexuiz (2.3) ? This sounds like it would introduce circular dependencies, which tend to break upgrades. Using a Breaks: header should be the right thing to do. ... jonas -- "In post-historical society, the rulers have ceased to rule, but the slaves remain slaves." - Perry Anderson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ITP: mumble -- Voice chat client
Package: wnpp Severity: wishlist * Package name: mumble Version : 0.9.4 Upstream Authors: Thorvald Natvig <[EMAIL PROTECTED]> * URL : http://mumble.sourceforge.net/ * License : GNU GPL Description : Voice chat client This is a low-latency, high quality voice chat software primarily intended for use while gaming. It features noise cancellation and voice activation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ITP: vtp -- Virtual Terrain Project
Package: wnpp Severity: wishlist * Package name: vtp Version : 070331 Upstream Authors: Ben Discoe <[EMAIL PROTECTED]> * URL : http://www.vterrain.org/ * License : see below Description : Virtual Terrain Project Software for the creation of tools for easily constructing any part of the real world in interactive, 3D digital form. License: The source code and data in this distribution are Copyright (c) 2001-2006 Virtual Terrain Project. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#429941: ITP: grandr -- gtk interface to xrandr
On Thu, 21 Jun 2007, David Nusinow wrote: > Package: wnpp > Severity: wishlist > Owner: David Nusinow <[EMAIL PROTECTED]> > > Package name: grandr FYI grandr is also the name of the Gnome applet in gnome-randr-applet. This conflict is somewhat confusing (at least it was for me when I first discovered this application while watching over jcristau's shoulder). I think it would be interesting to somehow merge both. (If you have the will to discuss with both upstream's) Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#429941: ITP: grandr -- gtk interface to xrandr
On Thu, Jun 21, 2007 at 05:05:45PM +0100, Raphael Hertzog wrote: > On Thu, 21 Jun 2007, David Nusinow wrote: > > Package: wnpp > > Severity: wishlist > > Owner: David Nusinow <[EMAIL PROTECTED]> > > > > Package name: grandr > > FYI grandr is also the name of the Gnome applet in gnome-randr-applet. > This conflict is somewhat confusing (at least it was for me when I first > discovered this application while watching over jcristau's shoulder). > > I think it would be interesting to somehow merge both. (If you have the > will to discuss with both upstream's) Ok, I'll grab keithp aside and we'll discuss it. Thanks for the heads up! - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Parsing of dpkg status file considered harmful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guillem Jover wrote:
> On Thu, 2007-05-31 at 14:51:00 +0200, Josselin Mouette wrote:
>> Le mercredi 30 mai 2007 à 07:53 +0300, Guillem Jover a écrit :
>>> If you need to retrieve the conffile info, which is why most of those
>>> packages are poking at the status file, please use something like:
>>>
>>> $ dpkg-query -W -f='${Conffiles}' docbook-xml
>>>
>>> which is also cleaner. If there happens to be any reentrancy problem
>>> in dpkg-query, that will be considered a bug and fixed, so this should
>>> be considered the standard api for maintainer scripts.
>> Could you please fix the wiki page with proper functions you recommend?
>
> Sure, done.
FWIW the new documentation on the wiki [1] regarding dpkg-query was not entirely
correct. It missed to strip of the "obsolete" keyword. I updated the wiki
accordingly.
Cheers,
Michael
[1] http://wiki.debian.org/DpkgConffileHandling
- --
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGerKrh7PER70FhVQRAvrFAJ9z6An10Xn3niFddCPwHXEknGelagCeNEp5
jVYWw2eBQjgc3W1h07dx3J8=
=1gj8
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Parsing of dpkg status file considered harmful
Michael Biebl <[EMAIL PROTECTED]> wrote: > FWIW the new documentation on the wiki [1] regarding dpkg-query was not > entirely > correct. It missed to strip of the "obsolete" keyword. I updated the wiki > accordingly. Ah, yes. Where is the meaning of that keyword documented? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
transition of packages into testing
Hi I am trying to figure out why texmacs has not entered into testing. I visited http://bjorn.haxx.se/debian/testing.pl?package=texmacs but there I was not able to find any useful information. All it says is * trying to update texmacs from 1:1.0.6-11 to 1:1.0.6.10-1 (candidate is 31 days old) * texmacs is not yet built on hppa: 1:1.0.6.9-4 vs 1:1.0.6.10-1 (missing 1 binary: texmacs) * texmacs is not yet built on ia64: 1:1.0.6-11 vs 1:1.0.6.10-1 (missing 1 binary: texmacs) Since candidate is 31 (> 10)days old, it should be fine to enter testing. Right? Can someone please explain? thanks raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: transition of packages into testing
On to, 2007-06-21 at 14:40 -0400, Kamaraju S Kusumanchi wrote: > I am trying to figure out why texmacs has not entered into testing. I > visited http://bjorn.haxx.se/debian/testing.pl?package=texmacs but there I > was not able to find any useful information. All it says is > > * trying to update texmacs from 1:1.0.6-11 to 1:1.0.6.10-1 (candidate is 31 > days old) > * texmacs is not yet built on hppa: 1:1.0.6.9-4 vs 1:1.0.6.10-1 (missing 1 > binary: texmacs) > * texmacs is not yet built on ia64: 1:1.0.6-11 vs 1:1.0.6.10-1 (missing 1 > binary: texmacs) > > Since candidate is 31 (> 10)days old, it should be fine to enter testing. > Right? Can someone please explain? It must be at least ten days old, but that is not the only criterion. Another criterion is that it's built on all the architectures the previous version in testing is built on. It seems it's missing builds on hppa and ia64. You could check the buildd logs on buildd.debian.org to see if there's any problems. -- Fundamental truth #2: Attitude is usually more important than skills. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: GSASL Maintainer Missing in Action?
On Wed, Jun 13, 2007 at 11:20:53PM -0300, [EMAIL PROTECTED] wrote: > Does anyone know the whereabouts of Yvan? May I consider him missing in > action? > It's a good think to CC [EMAIL PROTECTED] in those cases for tracking. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using standardized SI prefixes
On Thu, 21 Jun 2007, Hamish Moffatt wrote: On Wed, Jun 20, 2007 at 08:11:23PM -0400, Ivan Jager wrote: On Wed, 20 Jun 2007, Ben Finney wrote: The problem is that *many* cases are incorrect; we can't say that *all* of them are. That uncertainty is not amenable to a mindless text substitution without judgement of each case. The solution can only be for humans to find those cases where the units presented do not match the quantities, and to file bugs against those packages asking for the mistake to be corrected. The other solution can be for humans to find those few (if any) packages that say MB when they mean 1,000,000 and fix only those. Then we'd have a consistent system conforming to the standards most CS people expect. How many packages can you name that measure bytes in powers of 10? Are there any? People tell me I am making an argument from ignorance, and that I think Ben's point is that we don't know. You seem to claim that binary units (ie powers of 2) are natural everywhere related to computers, but I disagree. Not everywhere related to computers. Only when the unit is bytes. It's natural for memory and structures like it, but not for bitstream quantities like network traffic. Yes, for network traffic both are just as natural. Hard disks are different again; I don't know that there is any particular reason for them to have 2^n byte sectors (and at the hardware level perhaps they don't). Page sizes are powers of two. Filesystem block sizes are multiples of the sector sizes, and it's very convenient when they can be aranged nicely in pages. CD-ROMs have 2304 byte raw sectors. 2048 + 256 for ECC, both of which are powers of two. Even if you use the 2304 raw bytes, that is a multiple of 2^8 bytes, and not even divisible by 10^1. Most NAND FLASH chips have 2062 byte blocks, which even throws the memory device argument out the window. I have no idea about this, but I would expect http://www.google.com/search?hl=en&q=2062+flash+nand&btnG=Search to have more results where the 2062 is a block size... You forgot about ECC SDRAM which is 72 bits wide. So when you buy a 1GB (72x128M) DIMM, you're actually getting 1207959552 bytes of raw storage. But even then, the powers of two are more natural than the powers of 10. Ivan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: transition of packages into testing
Lars Wirzenius wrote: > On to, 2007-06-21 at 14:40 -0400, Kamaraju S Kusumanchi wrote: >> I am trying to figure out why texmacs has not entered into testing. I >> visited http://bjorn.haxx.se/debian/testing.pl?package=texmacs but there >> I was not able to find any useful information. All it says is >> >> * trying to update texmacs from 1:1.0.6-11 to 1:1.0.6.10-1 (candidate is >> 31 days old) >> * texmacs is not yet built on hppa: 1:1.0.6.9-4 vs 1:1.0.6.10-1 (missing >> 1 binary: texmacs) >> * texmacs is not yet built on ia64: 1:1.0.6-11 vs 1:1.0.6.10-1 (missing 1 >> binary: texmacs) >> >> Since candidate is 31 (> 10)days old, it should be fine to enter testing. >> Right? Can someone please explain? > > It must be at least ten days old, but that is not the only criterion. > Another criterion is that it's built on all the architectures the > previous version in testing is built on. It seems it's missing builds on > hppa and ia64. You could check the buildd logs on buildd.debian.org to > see if there's any problems. > Thanks for the reply. After posting the question, to my embarrassment, I found out that this criterion is explained in developers-reference. I have two other related questions. The page shows that it is not yet built for hppa and ia64. However the last builds on ia64 is on Apr 18, and on hppa is on May 21. 1) How can I request for a new build on ia64? or will it happen automatically? 2) How can I test the packages for these architectures when I dont have access to machines with these processors? I have access only to i386 machines. Should I just wait till some kind soul does the grunt work of fixing the problem? or is there anyway to debug and fix the problem from a pentium processor machine? thanks raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Automated mails to maintainers of packages with serious problems
Hi, During my talk today at debconf, I discussed the idea of sending mails to maintainers of packages with serious problems. The audience welcomed the idea, so I will send the first mails soon. You will receive a mail: * if one of your packages has RC bugs older than 30 days in unstable * if one of your packages has not been in testing for more than 180 days * if one of your packages has failed to migrate to testing for more than 360 days You will only receive one mail (per e-mail address), listing the problems in all your packages, not one mail per package. If all your packages are OK (according to the criterias above), you won't receive anything. If you co-maintain packages with problems, you won't receive anything (the "main" maintainer will), unless a mail is sent to you because of another package (in that case, it will also include info about co-maintained packages). I plan to send such mails on a monthly basis. Depending on how well it is received, the criterias will be enlarged to include more packages, while staying reasonable. The mails will mention: - an unsubscribe mechanism - an ignore mechanism, to ignore specific packages So the annoyance should be minimal: if you don't like it, just unsubscribe, and you won't receive those mails again. The main problem is with packages that have dummy RC bugs to prevent them from migrating to testing (see #395332 for example). Such packages are difficult to detect, and, for packages that have been in that case for a long time, one might question if the package should not be simply removed or uploaded to experimental. But you can simply ignore that package, so again, the annoyance should be minimal. With the criterias listed above, 244 mails would be sent, which is quite a lot. But reviewing some of the individual mails makes me think that most of them are about real issues. Any comments before I send the mails? For those interested, the slides from my talk are available on http://blop.info/bazaar/dc7slides.pdf . Interesting slides are pages 25-31. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automated mails to maintainers of packages with serious problems
Hi, * Lucas Nussbaum <[EMAIL PROTECTED]> [2007-06-22 00:17]: > During my talk today at debconf, I discussed the idea of sending mails > to maintainers of packages with serious problems. The audience > welcomed the idea, so I will send the first mails soon. That sounds good to me! > You will receive a mail: > * if one of your packages has RC bugs older than 30 days in unstable [...] > I plan to send such mails on a monthly basis. Depending on how well it > is received, the criterias will be enlarged to include more packages, > while staying reasonable. [...] > You will only receive one mail (per e-mail address), listing the > problems in all your packages, not one mail per package. If all your > packages are OK (according to the criterias above), you won't receive > anything. I propose to change this a bit for RC bugs. Assume you get a mail on 2nd of a month and get an RC bug on the 3rd day. Then you get the mail for the RC bug nearly after 2 months since it is not 30 days old on the 2nd of next month. But the service seems to be a great service for maintainers in my opinion. Cheers Nico -- Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpHG0cqaRffn.pgp Description: PGP signature
Re: Automated mails to maintainers of packages with serious problems
Lucas Nussbaum wrote: > Hi, Hi Lucas > The main problem is with packages that have dummy RC bugs to prevent > them from migrating to testing (see #395332 for example). Such > packages are difficult to detect, and, for packages that have been in > that case for a long time, one might question if the package should > not be simply removed or uploaded to experimental. But you can simply > ignore that package, so again, the annoyance should be minimal. You should usertag these dummy RC bugs and ignore these when sending mails. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Automated mails to maintainers of packages with serious problems
On 22/06/07 at 00:37 +0200, Luk Claes wrote: > Lucas Nussbaum wrote: > > Hi, > > Hi Lucas > > > The main problem is with packages that have dummy RC bugs to prevent > > them from migrating to testing (see #395332 for example). Such > > packages are difficult to detect, and, for packages that have been in > > that case for a long time, one might question if the package should > > not be simply removed or uploaded to experimental. But you can simply > > ignore that package, so again, the annoyance should be minimal. > > You should usertag these dummy RC bugs and ignore these when sending mails. Well, if someone has an usertag for that already, I could use it. But if not, I'll just wait for maintainers' ignore requests, I think. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Using standardized SI prefixes
On Thu, Jun 21, 2007 at 09:32:09AM +0200, Adam Borowski wrote: > On Thu, Jun 21, 2007 at 01:11:52PM +1000, Hamish Moffatt wrote: > > I think Ben's point is that we don't know. > > > > You seem to claim that binary units (ie powers of 2) are natural > > everywhere related to computers, but I disagree. It's natural for > > memory and structures like it, but not for bitstream quantities like > > network traffic. > > But they don't use powers of 10 any more than they do powers of 10. While > bps speeds are an oft-quoted case that "always" use powers of 10, the > connection I got here is guaranteed min=max 1Mbps which as far as I can > measure it goes right at 1048576 bits per second, rain or sleet. > And the ISP is one of the most despicable, cheating, greedy ones you can > imagine -- for example our company pays for that 1Mbps more than in a > civilised place you would pay for 100Mbps, so if they seen a place to > overadvertise something, they would. > > And as far as I know, usually 1Mbps stands for 1024x1000 bits where network > speeds are concerned, to be wrong by both the correct and yours > interpretation :p The raw network transports (eg Ethernet and SONET) *are* quoted in powers of 10, and they mean it. Gigabit ethernet is really a billion bits (10^9) per second. OC-3 is really 155,520,000 bits per second. Powers of 10 are perfectly natural in this case (imho). They are what we humans are used to as the default. For computer memory structures where an N bit address bus means you have 2^N bits of storage, powers of 2 make some sense, but not in the general case. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: transition of packages into testing
On to, 2007-06-21 at 17:01 -0400, Kamaraju S Kusumanchi wrote: > 1) How can I request for a new build on ia64? or will it happen > automatically? This is outside my area of expertese, but I would assume that the buildds don't automatically re-try a failed build. Instead, they'll wait for the package to change, hopefully for the better. Most problems are due to bugs in the package. Automatic re-trying would make sense for problems in the buildds themselves, but those are fortunately pretty uncommon. The thing to do, then, is to figure out what the actual problem is, and then either fix it in the package or ask the buildd admins to re-try the build. > 2) How can I test the packages for these architectures when I dont have > access to machines with these processors? If you're a DD, you should have access to all or most architectures we support. (In theory, all of them, but sometimes we fall short of that goal.) If you're not, then see http://db.debian.org/machines.cgi if there are any machines of the desired architectures that are accessible by non-DDs, or ask here or on one of the architecture specific lists if someone can provide access to one. Or see if there's an emulator available you could run on your own system. -- Maailma olisi parempi paikka, jos kaikilla olisi häntä kertomassa mitä kuuluu. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Proposed new release goal: Dependency/file list predictability
[Please keep discussion on -devel; -release is not a discussion list and I'm not subscribed to -qa :-)] Hi, As discussed during DebConf, I'd like to propose a new release goal: Packages should not only build in clean chroots, but also in non-clean environments. Specifically, adding extra packages from the archive into the build environment (that are not in Build-Conflicts) should not affect the resulting package in any noticeable way. To this end, I've set up the "build daemon from Hell" (BDFH) on my machine, currently doing script testing. (Joey Hess has kindly promised to donate CPU time on a four-CPU machine so we can push through the entire archive at reasonable speeds at regular intervals; the setup will be moved there as soon as it's stable.) The idea is to build a package both in a pbuilder and in a really filled chroot -- it currently contains 18GB of packages, which is most of the "devel" and "libdevel" sections. What is compared is: - The list of Depends. - The list of Recommends. - The list of filenames. (Actually, it is first built in the "dirty" chroot, and if it matches what's in the archive already, the script won't bother doing the pbuilder test, under the assumption that it's going to be the same anyway. I don't expect this to miss many bugs, but it will save many lengthy rebuilds, especially for packages that have been built recently and thus depend on the newest libc6 etc.) Differences between the two versions will be counted as a bug, which I hope can get status as a release goal under the usertag "unpredictable-build-result". Also, packages that just plain FTBFS under the messy chroot (assuming it is not something _wrong_ in the build environment or something, of course), should be tracked, hopefully under the same release goal, but with the usertag "unpredictable-build-failure". I intend to start mass filing for such bugs in a few weeks, whether it's approved as a release goal or not (but in that case, with normal severity and a different usertag), but I'll send appropriate warning to -devel first. The correct fix for almost all such packages would be adding --disable flags to the autoconf script (it is believed that most such bugs would stem from autoconf finding and using some library); Build-Conflicts are possible, but less than ideal for several reasons. Comments would be appreciated. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Proposed new release goal: Dependency/file list predictability
Hi, Steinar H. Gunderson schrieb: > To this end, I've set up the "build daemon from Hell" (BDFH) on my machine, > currently doing script testing. Would it make sense to run the build under auto-apt, to see whether it tries to access some file in another package? That would obviously not be a replacement for the BDFH, since some particularly nasty tools install stuff into .d directories (so unless they are installed, they are never accessed), and it might generate a few false positives, but it could be another data source. Also, you could look at the atimes of the other packages after the build to see whether stuff has been used. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Work-needing packages report for Jun 22, 2007
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: 396 (new: 12) Total number of packages offered up for adoption: 83 (new: 0) Total number of packages requested help for: 40 (new: 2) Please refer to http://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: airsnort (#429507), orphaned 3 days ago Description: WLAN sniffer Installations reported by Popcon: 1170 datefudge (#429467), orphaned 3 days ago Description: Fake the system date Installations reported by Popcon: 98 fdflush (#429468), orphaned 3 days ago Description: Flush out-of-date disk buffers Installations reported by Popcon: 781 fmit (#429756), orphaned 2 days ago Description: Free Music Instrument Tuner Installations reported by Popcon: 145 gscanbus (#429559), orphaned 3 days ago Description: scan IEEE1394 (firewire/i.link) bus Installations reported by Popcon: 342 hx (#429371), orphaned 4 days ago Description: The Unix client for Hotline Installations reported by Popcon: 16 kforth (#429469), orphaned 3 days ago Description: Small Forth Interpreter Written in C++ Installations reported by Popcon: 27 libraw1394 (#429752), orphaned 2 days ago Description: library for direct access to IEEE 1394 bus (aka FireWire) Reverse Depends: blender coriander dvgrab ffmpeg2theora gnash gnash-tools gnusound gscanbus gstreamer0.10-plugins-good kcontrol (32 more omitted) Installations reported by Popcon: 38208 netdude (#429513), orphaned 3 days ago Description: NETwork DUmp data Displayer and Editor for tcpdump trace files Reverse Depends: netdude netdude-dev Installations reported by Popcon: 110 pmidi (#429755), orphaned 2 days ago Description: A command line midi player for ALSA Reverse Depends: songwrite Installations reported by Popcon: 882 tcpick (#430030), orphaned today Description: TCP stream sniffer and connection tracker Installations reported by Popcon: 225 workbone (#429178), orphaned 5 days ago Description: A simple text-based CD player Installations reported by Popcon: 152 384 older packages have been omitted from this listing, see http://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 83 packages are awaiting adoption. See http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: [NEW] foo2zjs (#429872), requested yesterday Installations reported by Popcon: 553 [NEW] kradio (#429873), requested yesterday Description: Comfortable Radio Application for KDE Installations reported by Popcon: 234 aboot (#315592), requested 728 days ago Description: Alpha bootloader: Looking for co-maintainers Reverse Depends: aboot aboot-cross dfsbuild ltsp-client-core Installations reported by Popcon: 111 apt-build (#365427), requested 418 days ago Description: Need new developer(s) Installations reported by Popcon: 771 apt-cacher (#403584), requested 185 days ago Description: caching proxy system for Debian package and source files Installations reported by Popcon: 351 apt-show-versions (#382026), requested 317 days ago Description: lists available package versions with distribution Installations reported by Popcon: 2685 athcool (#278442), requested 968 days ago Description: Enable powersaving mode for Athlon/Duron processors Installations reported by Popcon: 287 cdw (#398252), requested 221 days ago Description: Tool for burning CD's - console version Reverse Depends: cdw gcdw Installations reported by Popcon: 251 cvs (#354176), requested 483 days ago Description: Concurrent Versions System Reverse Depends: bonsai crossvc cvs-autoreleasedeb cvs-buildpackage cvs2cl cvs2html cvschangelogbuilder cvsconnect cvsd cvsdelta (17 more omitted) Installations reported by Popcon: 18036 dpkg (#282283), requested 943 days ago Description: dselect: a user tool to manage Debian packages Reverse Depends: alien alsa-source apt-build apt-cross apt-src backuppc build-essential bzr-builddeb clamsmtp crosshurd (85 more omitted) Installations reported by Popcon: 54234 gentoo (#422498), requested 46 days ago Description: a fully GUI-configurable, two-pane X file manager Installations reported by Popcon: 274 gpsdrive (#406522), requested 161 days ago Desc
