Re: net-tools maintenance status

2007-04-06 Thread Olaf van der Spek

On 4/6/07, Martín Ferrari <[EMAIL PROTECTED]> wrote:

I'm copying Olaf, since he asked for it in the OP, and Bernd, since
he's the maintainer.


Thanks.


On 4/3/07, Michael Banck <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Tue, Apr 03, 2007 at 02:09:00PM +0200, Olaf van der Spek wrote:
> > On 8/2/05, Olaf van der Spek <[EMAIL PROTECTED]> wrote:
> > >What's the maintenance status of the net-tools package?
>
> Are you applying for co-maintenance?  If so, you should rather talk the


Not really, although I wouldn't mind working on some of the bugs,
especially the one for showing IPv6 addresses.


> the package maintainer, I think.  Alternatively, you could do some bug


Well, that's part of the problem, he's basically MIA and doesn't (want
to) talk about bugs.


> triaging and/or trying to reproduce the older bugs, if you haven't done
> so already.


I don't want to do that before there's someone to at least discuss
solutions / patches with.


Re: net-tools maintenance status

2007-04-06 Thread Martín Ferrari

Hi again,

On 4/5/07, Martín Ferrari <[EMAIL PROTECTED]> wrote:


I don't know if I will be able to apply for co-maint, but I started
working a little on triaging. Hope it helps.


I've spent a lot of hours working on net-tools bugs, 17 of them if I
don't miss anything. I usertagged them, so if any other is working on
it can see what I've done so far:
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]&tag=working-on-it


--
Martín Ferrari


Re: MySql broken on older 486 and other cpuid less CPUs. Does this qualify as RC?

2007-04-06 Thread Francesco P. Lovergine
On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
> Like I said, in practical terms, if a bug like this in a major server
> package goes unnoticed until 3 days before the release, we are not actually
> "supporting" 486.  We support the i386 architecture quite well, but it seems
> only honest to admit that as a project, we don't care about 486 enough to
> even get 486-specific problems marked as RC in time to do anything about
> them for a release.
> 

That could be fixed in R1, isn't it? I see no major problems on those
regards...

-- 
Francesco P. Lovergine


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



Re: MySql broken on older 486 and other cpuid less CPUs. Does this qualify as RC?

2007-04-06 Thread Andreas Barth
* Francesco P. Lovergine ([EMAIL PROTECTED]) [070406 12:33]:
> On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
> > Like I said, in practical terms, if a bug like this in a major server
> > package goes unnoticed until 3 days before the release, we are not actually
> > "supporting" 486.  We support the i386 architecture quite well, but it seems
> > only honest to admit that as a project, we don't care about 486 enough to
> > even get 486-specific problems marked as RC in time to do anything about
> > them for a release.
> > 
> 
> That could be fixed in R1, isn't it? I see no major problems on those
> regards...

Well, we can fix it - but are you sure that's the only package with an
issue on 80486? I think we should put somewhere into Lenny that our code
should still run on 80486, but it might not be QAed enough for all
subarches (but we can discuss that later, don't need to reach a
consensus now).


Cheers,
Andi
-- 
  http://home.arcor.de/andreas-barth/


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



Re: Modifying /etc/apt/sources.list in postinst ; determining the suite in postinst

2007-04-06 Thread Filippo Giunchedi
On Tue, Apr 03, 2007 at 04:28:06PM +0100, Neil Williams wrote:
[...]
> update-manager and netselect-apt already modify /etc/apt/sources.list
> but not in postinst.

netselect-apt writes sources.list to the current directory unless told so, and
makes a backup before writing if the said file exists.

filippo, with his netselect-and-pendant-maintainer hat on
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

To be learned in an art&C, the Theory is sufficient; to be a master of
it, both the Theory and practice are requisite.
-- Charles Hutton


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



Re: primary mirrors, emdebian-tools and Pre-Depends

2007-04-06 Thread Neil Williams
On Thu, 05 Apr 2007 23:22:50 +0200
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:

> > apt-cache policy already covers that output and it is easier to
> > parse - the code offered by Ben Hutchings adds to my own code by
> > supporting the priority figure specified in apt-cache policy, I was
> > already parsing the rest. Thanks Ben.
>
> But it lacks information:

The extra information isn't important UNLESS it means that the
available sources will not include any Packages content for arm or
whichever other architecture the user chooses to select to cross-build.

The parsing of apt-cache policy is only used to identify the suite - at
this stage of the process, the mirror in use for that suite is
irrelevant. The suite is then checked against the list of supported
suites for Emdebian to generate the emdebian repository source lines.

A later stage then has to work out if a source exists for the chosen
arch using the identified suite. If not, I'll need to add a primary
mirror to /etc/apt/sources.list.d/emdebian.sources.list

>  500 http://storage sid/main Packages
>  release o=Debian,a=unstable,l=Debian,c=main
>  origin ftp.de.debian.org
>
> Now is that
> http://storage/debian/sid/main/binary-amd64/Packages
> or
> http://storage/mirror/debian/sid/main/binary-amd64/Packages
> ?
>
> You just don't have all the info.

All that needs to give me is which suite has the highest priority for
main.

> > Am I right in thinking that normal d-i installations ensure that at
> > least one primary mirror is selected (or at least strongly advise
> > that one primary should exist)?
>
> Nothing wrong with picking ftp.debian.org from the mirror list if one
> is in us. D-I takes the full list, filters out mirrors that carry the
> requested arch and then tries to pick one from the country the locales
> are set to. Otherwise the user gets asked to pick one afaik.
>
> So nothing says the mirror you end up with on i386 will have arm
> packages.

So I'll need to adapt postinst to attempt to verify if there is a
suitable source available for cross-building. There's no point in
picking a mirror on the basis that it has packages for i386 and arm but
not amd64 or mips. I'm adding a mirror purely to support cross-building
with a toolset that can cross-build for any Debian arch, I need to
ensure that a primary mirror is available and add one if it is not.

I'll put a note in the manpage on how to optimise this:

"If emdebian-tools identifies that your available sources do not
contain at least one primary mirror, emdebian-tools will add the
ftp.uk.debian.org primary mirror
to /etc/apt/sources.list.d/emdebian.sources.list alongside the
Emdebian repository. If you prefer to use a closer/faster primary
mirror, please refer to the Debian Mirror List (href=) and add your
preferred primary mirror to /etc/apt/sources.list, then use
'dpkg-reconfigure emdebian-tools' to
update /etc/apt/sources.list.d/emdebian.sources.list. At least one
primary mirror, as defined on the DML page, *must* be available to use
emdebian-tools."

This only occurs if the existing installation does not already use a
primary. The added primary is only used when querying cache status of
$arch packages *during* cross-building because the existing source
always takes priority over sources in sources.list.d/. In this context,
I don't think I'll implement the extra workload of deciding which
primary to use, emdebian-tools can do what is necessary and leave the
user instructions on how to optimise it, if appropriate.

The question then follows: In order to calculate this situation, I'll
need to parse apt-cache policy *and* `apt-cache -o Apt::Architecture=
$arch pkgnames gcc` which requires that apt-get update has been run
or can be run - doesn't that mean I'll need to pre-depend on apt?

--


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpVfhYYjlYWv.pgp
Description: PGP signature


Re: Poll: Anybody using debpool?

2007-04-06 Thread Free Ekanayaka
|--==> Andreas Fester writes:

  AF> Hi Magnus,
  AF> Magnus Holmgren wrote:
  AF> [...]
  >>Since I liked it very much I immediately started adding and rewriting code 
and 

  AF> "me too" ;)

Count me in as well :)

  >>submitting my suggestions for improvement to the BTS, but unfortunately 
Joel 

  AF> Yes, I also sent him an email some time ago, asking if he is interested
  AF> in what I did, my but never got a reply.

And the same happened to me..

  AF> - Added support for multi arch archives (the .package files were
  AF>   not arch specific and therefore overwritten when an additional
  AF>   arch-specific package was uploaded)

Very good! This is a feature the official debpool really misses.

Me too have submitted a very simple patch (#350503) more than one year
ago, and I have another one lying around to support udebs as well. If
you are interested I can polish it up and submit it.

  AF> The package is at 
http://littletux.homelinux.org/debian/pool/main/d/debpool/

  >>I'd like to suggest, then, that a project be started on Alioth, let's 
  >>say "saving-debpool" or "debpool-2g". Or anything that is better.  :-) 

It seems there's currently no debpool project on Alioth, so why not
simply "debpool"? :)

  >>wanted to make clear that no one is "stealing" debpool or anything. 
  >>Discussion can then continue on an associated mailing list.

  AF> Great! I would be glad to contribute to this project!

Yeah!

Free


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



Re: net-tools maintenance status

2007-04-06 Thread Cesare Tensi

Good Work.

Especially to risolve and delete very older bugs. There are more than one
bug opened 4 year ago, for example.

If want to have some help, especially for testing and/or coding, I'm
available.

Happy Easter to anybody all!

Cheers

Cesare

On 4/6/07, Martín Ferrari <[EMAIL PROTECTED]> wrote:


Hi again,

On 4/5/07, Martín Ferrari <[EMAIL PROTECTED]> wrote:

> I don't know if I will be able to apply for co-maint, but I started
> working a little on triaging. Hope it helps.

I've spent a lot of hours working on net-tools bugs, 17 of them if I
don't miss anything. I usertagged them, so if any other is working on
it can see what I've done so far:

http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED]&tag=working-on-it


--
Martín Ferrari



Re: MySql broken on older 486 and other cpuid less CPUs. Does this qualify as RC?

2007-04-06 Thread Theodore Tso
On Fri, Apr 06, 2007 at 12:36:18PM +0200, Andreas Barth wrote:
> * Francesco P. Lovergine ([EMAIL PROTECTED]) [070406 12:33]:
> > On Thu, Apr 05, 2007 at 04:10:19PM -0700, Steve Langasek wrote:
> > > Like I said, in practical terms, if a bug like this in a major server
> > > package goes unnoticed until 3 days before the release, we are not 
> > > actually
> > > "supporting" 486.  We support the i386 architecture quite well, but it 
> > > seems
> > > only honest to admit that as a project, we don't care about 486 enough to
> > > even get 486-specific problems marked as RC in time to do anything about
> > > them for a release.
> > 
> > That could be fixed in R1, isn't it? I see no major problems on those
> > regards...
> 
> Well, we can fix it - but are you sure that's the only package with an
> issue on 80486? I think we should put somewhere into Lenny that our code
> should still run on 80486, but it might not be QAed enough for all
> subarches (but we can discuss that later, don't need to reach a
> consensus now).

The fact that we can't say for sure is a good reason to say that we
don't "support" 486.  That is to say, we can't guarantee that it will
work, because we don't have enough people who are testing on that
platform.  

There is a difference between "we won't consciously break 486, and
we'll apply patches when they are called to our attention, but we
won't hold up an entire release for it", and "support".  For all that
people like to beat up on Red Hat and Fedora for their supposed "lack
of quality", this is a concept which Red Hat and other commercially
supported enterprise distributions understand.  If they can't test on
a platform, they don't call it supported.  (And they do get help from
major system vendors to do a lot of very serious regression testing
before they say that it is supported on a particular platform.)  

If we are going to claim that Debian is stable enterprise system for
servers, so stable in fact that we must use an obsolete version of
glibc compared to RHEL and SLES (even though we are releasing later
than RHEL and SLES), then it would be wise for us to use at _least_ as
stringent set of QA gaurantees as Red Hat and Novell.  And if that
means that we can't say that we "support" the 486, then so be it.

- Ted


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



Re: Poll: Anybody using debpool?

2007-04-06 Thread Magnus Holmgren
On Thursday 05 April 2007 23:04, Andreas Fester wrote:
> Magnus Holmgren wrote:
> [...]
> > * You've indented the main loop in bin/debpool. While I think that's how
> > it should be, I also think it's best to undo it until we have merged all
> > contributions.
>
> Sure. I did this to make the main loop more readable, but for merging
> it might be better not to indent it at first. I think that
> the main loop is too large anyway and should be refactored to only call
> a few other functions.

I totally agree with that. I was going to suggest it myself.

> Did you already think about the further proceeding? Shall we register
> a debpool2, debpool-ng or whatsoever project on alioth?

I've created a package incorporating a number of minor or relatively minor 
changes, which I thought perhaps could be uploaded as an NMU or something 
(version 0.2.3.1 or 0.2.4). My idea is that we then base debpool2|debpool-ng 
on that.

My package is at ftp://ftp.kibibyte.se/debian/pool/main/d/debpool/
(ftp://ftp.kibibyte.se/debian/pool/main/d/debpool/debpool_0.2.3+mh1.dsc)

For more detail, look in my SVN repository at 
http://svn.kibibyte.se/debpool/branches/magnus (anonymous SVN to 
svn://svn.kibibyte.se/debpool/branches/magnus should work too).

I think that "not rejecting duplicate orig tarballs" is fairly minor too, but 
I'm not sure that it should simply overwrite any existing tarball. I think 
the MD5 checksum should be checked and if it matches, the duplicate should be 
ignored, like dinstall does. Otherwise the upload should be rejected, except 
perhaps if rollback is allowed. Binary packages not matching the source can 
be weird. To that end, all old binary packages should perhaps even be deleted 
if the source changes.

The same goes for the --verbose option, but I think its definition should be 
in Config.pm unless it's command line only, and maybe duplication the log 
output to stdout (or stderr) is better selected with some more 
general --logging option?

-- 
Magnus Holmgren[EMAIL PROTECTED]
   (No Cc of list mail needed, thanks)


pgpvWhGhZ298E.pgp
Description: PGP signature


Bug#418047: ITP: ncdu -- ncurses disk usage viewer

2007-04-06 Thread Luca Bedogni
Package: wnpp
Severity: wishlist
Owner: Luca Bedogni <[EMAIL PROTECTED]>


* Package name: ncdu
  Version : 1.0
  Upstream Author : Yoran Heling <[EMAIL PROTECTED]>
* URL : http://dev.yorhel.nl/ncdu
* License : MIT
  Programming Lang: C
  Description : ncurses disk usage viewer

ncdu is a ncurses-based du viewer. It allows to browse through the
directories and show percentages of disk usage.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20.1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)


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



Re: net-tools maintenance status

2007-04-06 Thread Bernd Eckenfels
please make sure to work with the latest cvs version from berlios.

Greetings
Bernd


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



Re: net-tools maintenance status

2007-04-06 Thread Bernd Eckenfels
On Fri, Apr 06, 2007 at 09:32:27AM +0200, Olaf van der Spek wrote:
> Well, that's part of the problem, he's basically MIA and doesn't (want
> to) talk about bugs.

thats not true, i will discuss about all bugs, especially those which are
tagged help needed. I just dont talk with ppl who dont help me.

Gruss
Bernd
-- 
  (OO) -- [EMAIL PROTECTED] --
 ( .. )[EMAIL PROTECTED],linux.de,debian.org}  http://www.eckes.org/
  o--o   1024D/E383CD7E  [EMAIL PROTECTED]  v:+497211603874  f:+49721151516129
(OO)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!


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



RFO: duplicity

2007-04-06 Thread Martin Wuertele
Hi!

Since I hardly use it myself and I currently have less time for debian
due to job change duplicity is up for adoption.

I have some patches that need a bit of adjustment closing most of the
open bugs but I currently lack the time to throw them all matching
togeather.

yours Martin
-- 
http://martin.wuertele.net/ -- Debian -- OFTC -- SPI -- [EMAIL PROTECTED]
Michelle, please meet http://www.google.com. Google, meet Michelle.
-- Steve Greenland, debian-devel@lists.debian.org


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



Re: net-tools maintenance status

2007-04-06 Thread Olaf van der Spek

On 4/6/07, Bernd Eckenfels <[EMAIL PROTECTED]> wrote:

On Fri, Apr 06, 2007 at 09:32:27AM +0200, Olaf van der Spek wrote:
> Well, that's part of the problem, he's basically MIA and doesn't (want
> to) talk about bugs.

thats not true,


You're not basically MIA? How do you explain the lack of uploads and
new upstream versions then?


i will discuss about all bugs, especially those which are
tagged help needed. I just dont talk with ppl who dont help me.


I wrote an entire patch...


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