Re: localhost.localdomain

[Peter Samuelson]

  [Joey Hess]
> > So far, this thread has not yeilded anything I can trust to that degree.

[Christoph Haas]
> IIRC it yielded the fact that localhost.localdomain is has been added
> to fix applications

Not that I've noticed.  Maybe I just missed it, but *what* applications
or *what* problems does .localdomain fix?  I don't remember hearing so
far that it does anything positive at all.

If anybody knows anything at all about a problem .localdomain solves, I
would love to hear about it.  Never mind the alleged applications that
break, I'm more interested in whether there are even two sides to this
story in the first place.


signature.asc
Description: Digital signature

Re: Effort to change IETF's copying conditions for RFCs

[Luca Capello]

Hello!

On Fri 07 Oct 2005 10:30 +0200, Simon Josefsson wrote:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>
>> Wesley J Landaker <[EMAIL PROTECTED]> writes:
>>> On Thursday 06 October 2005 06:57, Simon Josefsson wrote:
>>
 I know the copying conditions of IETF RFC's has been a concern
 for Debian in the past, and that the RFCs has been removed from
 the official archive (?),
>>
>> If they haven't been yet, they will have to be for etch, at least
>> all of the RFCs that are under the standard IETF IPR policy.  They
>> don't allow modification and redistribution of modified versions,
>> and therefore do not meet DFSG#3.
>
> Yes.  I couldn't find them when I did a 'apt-cache search' so I
> assume they were gone.  I recall a series of packages, rfc1-499,
> rfc500-999 or similar before.

`apt-cache search doc-rfc`, they are in unstable/non-free.

Thx, bye,
Gismo / Luca


pgpNL72k7mlO2.pgp
Description: PGP signature

Re: force jack-audio-connection-kit into testing ?

[Free Ekanayaka]

|--==> Junichi Uekawa writes:

  JU> Hi,
  >>I just tried to figure out why the jack-audio-connection-kit can't go
  >>into testing, and after some investigation I came to the conclusion
  >>that it might never go in without help. [1]
  >>
  >>Is there someone who shares this opinion or am I missing something ?
  >>For my part, I would be happier if all my packages depending on jackd get 
  >>thrown out of testing in order to reenter later. With all the changes that
  >>go on everywhere it is almost impossible to keep all the packages that
  >>have to go with jack reasonably bugfree for a long enough time.

  JU> I think jack was one of those packages that always needed a manual 
  JU> kick; and we really need a freeze to get testing up to shape.

  JU> I agree that at this stage it might be good enough just to kick a few 
  JU> packages out of testing to let it propagate.

As far as I understand jack-audio-connection-kit is blocked by libarts
which is in turned blocked by qt-x11-free, which FTBFS on hppa:

http://people.debian.org/~igloo/status.php?email=&packages=qt-x11-free&arches=

would   fixing the compilation make the   whole  thing move cleanly to
testing? Or am I missing more complex issues?

Cheers,

Free


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

Bug#333081: ITP: libpam-abl -- PAM module to blacklist hosts/users with many login failures

[Nicolai Ehemann]

Package: wnpp
Severity: wishlist
Owner: Nicolai Ehemann <[EMAIL PROTECTED]>


* Package name: libpam-abl
  Version : 0.2.2
  Upstream Author : Andy Armstrong <[EMAIL PROTECTED]>
* URL : http://www.hexten.net/pam_abl/
* License : BSD or GPL
  Description : PAM module to blacklist hosts/users with many login failures

This PAM module automatically adds hosts and/or users with many
authentication failures in pre-defined time intervals to a temporary
blacklist. While blacklisted, any authentication attempt will
silently
fail, pretending the given authentication credentions are wrong.
After
the pre-defined blacklist interval, the host/user will be unbanned
again.

Thus, this module provides effective protection against the
password
guessing attacks agaings ssh servers seen lastly in the
internet.
 


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

Re: force jack-audio-connection-kit into testing ?

[Adeodato Simó]

* Free Ekanayaka [Mon, 10 Oct 2005 10:54:01 +0100]:

> would   fixing the compilation make the   whole  thing move cleanly to
> testing? Or am I missing more complex issues?

  With the current implementation of testing, qt-x11-free has to go into
  testing together with a lot of packages, including all of KDE.

  Cheers,

-- 
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?


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

Re: time seen at top of /var/log/boot

[Christoph Berg]

Re: Frans Pop in <[EMAIL PROTECTED]>
> On Sunday 09 October 2005 00:49, John Hasler wrote:
> > Interesting that the two lines differ by 1 second in the wrong
> > direction.
> 
> That would be easily explained by ntp-date or something such syncing the 
> time...

Or skew corrected by /etc/adjtime.

Christoph
-- 
[EMAIL PROTECTED] | http://www.df7cb.de/


signature.asc
Description: Digital signature

Re: Bug#332858: ITP: cvsup -- The CVS-Optimized General-Purpose Network File Distribution System

[Javier Fernández-Sanguino Peña]

On Sun, Oct 09, 2005 at 01:03:38PM +0300, George Danchev wrote:
> On Sunday 09 October 2005 03:10, Henning Makholm wrote:
> --cut--
> > > The CVSup requires Modula-3 compilator to build, so also I'm
> > > planning to package Ezm3 - An Easier Modula-3 Distribution, which is
> > > designated to compile CVSup only.
> >
> > Best of luck with that. Torsten might still be interested, too.
> 
> CVSync [1] is a possible alternative to CVSup, not compatible with it, but 
> written in plain C.

That one looks interesting, I did not find it when I was googling for
alternatives to CVSup. I would love to see something like this packaged so
that we could distribute copies of our CVS worlwide and not have issues if
we have any issues with the servers holding our CVS in the future.

Regards

Javier


signature.asc
Description: Digital signature

Re: [Pbuilder-maint] Bug#333107: pbuilder: Cannot install python2.3-dev

[Junichi Uekawa]

reassign python2.3
severity 333107 serious
thanks

python2.3 seems to depend on libssl0.9.7 which no longer exists in archive.


But this is a bit wild, isn't it?
(from http://ftp-master.debian.org/removals.txt)

=
[Date: Sat, 08 Oct 2005 10:03:15 -0700] [ftpmaster: Jeroen van Wolffelaar]
Removed the following packages from unstable:

libccscript3-0.8-0 |0.8.1-2 | alpha, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libcrypto0.9.7-udeb |   0.9.7g-2 | hurd-i386
libcrypto0.9.7-udeb |   0.9.7g-3 | alpha, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libsmpeg0c2 | 0.4.5+cvs20030824-1.3 | alpha, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, sparc
libsqlplus-dev | 1.7.9.sp4-5.1 | hurd-i386
libsqlplus-dev |   1.7.40-3 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, 
powerpc, s390, sparc
libsqlplus4 |   1.7.40-3 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, 
powerpc, s390, sparc
libssl0.9.7 |   0.9.7g-2 | hurd-i386
libssl0.9.7 |   0.9.7g-3 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, 
powerpc, s390, sparc
libssl0.9.7-dbg |   0.9.7g-3 | alpha, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc

--- Reason ---
[rene] NBS
--
=


At Mon, 10 Oct 2005 20:20:36 +0800,
LI Daobing wrote:
> 
> Package: pbuilder
> Version: 0.135
> Severity: normal
> 
> $ apt-get source qterm
> [snip]
> $ sudo pbuilder build qterm_0.4.0pre2.ds.3-2.dsc
> W: /home/nichloas/.pbuilderrc does not exist
> pbuilder-buildpackage/i386 $Id: pbuilder-buildpackage-funcs,v 1.20 2005/10/03 
> 23:59:06 dancer Exp $
> $Id: pbuilder-buildpackage,v 1.114 2005/07/13 22:02:20 dancer Exp $
> 
> Current time: Mon Oct 10 20:19:10 CST 2005
> pbuilder-time-stamp: 1128946750
> Building the build Environment
>  -> extracting base tarball [/var/cache/pbuilder/base.tgz]
>  -> creating local configuration
>  -> copying local configuration
>  -> mounting /proc filesystem
>  -> mounting /dev/pts filesystem
>  -> policy-rc.d already exists
>  -> created buildresult dir :/var/cache/pbuilder/result/
> Obtaining the cached apt archive contents
> Installing the build-deps
>  -> Attempting to parse the build-deps : pbuilder-satisfydepends,v 1.20 
> 2005/08/17 00:46:54 dancer Exp $
>  -> Considering  debhelper (>> 4.1.0)
>-> Trying debhelper
>  -> Considering  libqt3-mt-dev
>-> Trying libqt3-mt-dev
>  -> Considering  libqt3-compat-headers
>-> Trying libqt3-compat-headers
>  -> Considering  xutils
>-> Trying xutils
>  -> Considering  cdbs
>-> Trying cdbs
>  -> Considering  python2.3-dev
>-> Trying python2.3-dev
>-> Cannot install python2.3-dev; apt errors follow:
> Reading package lists... Done
> Building dependency tree... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   python2.3-dev: Depends: python2.3 (= 2.3.5-8) but it is not going to be 
> installed
> E: Broken packages
> E: Could not satisfy build-dependency.
> E: pbuilder-satisfydepends failed.
> Copying back the cached apt archive contents
>  -> unmounting dev/pts filesystem
>  -> unmounting proc filesystem
>  -> cleaning the build env
> -> removing directory /var/cache/pbuilder/build//1871 and its 
> subdirectories
> 
> 
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.12-1-686-smp
> Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
> 
> Versions of packages pbuilder depends on:
> ii  cdebootstrap  0.3.8  Bootstrap a Debian system
> ii  coreutils 5.2.1-2The GNU core utilities
> ii  debianutils   2.14.2 Miscellaneous utilities specific 
> t
> ii  gcc   4:4.0.1-3  The GNU C compiler
> hi  wget  1.10-1 retrieves files from the web
> 
> Versions of packages pbuilder recommends:
> hi  devscripts2.9.4  Scripts to make the life of a 
> Debi
> hi  fakeroot  1.2.4  Gives a fake root environment
> hi  sudo  1.6.8p9-2  Provide limited super user 
> privile
> 
> -- no debconf information
> 
> 
> ___
> Pbuilder-maint mailing list
> [EMAIL PROTECTED]
> http://lists.alioth.debian.org/mailman/listinfo/pbuilder-maint
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject 

ACT FAST

[MATTHEW IGBINIGIE]

  REV. MATTHEW O. IGBINIGIE
  CALVARY KINGDOM CHURCH
  PLOTS 53/54 ALAJA ROAD
  MEGIDA ESTATE,AYOBO
  IPAJA,LAGOS,NIGERIA.
 
Dear Beloved,
 
    Calvary greetings to you in the name of our Lord and Saviour Jesus Christ.
 
Please send me current informations about your one year courses for ministers.
 
    I am very serious about it,please act as soon as possible.
 
    Yours in his Service.
 
REV. MATTHEW O. IGBINIGIE
		To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.

Re: Bug#332858: ITP: cvsup -- The CVS-Optimized General-Purpose Network File Distribution System

[Piotr Roszatycki]

On Monday 10 of October 2005 15:45, Javier Fernández-Sanguino Peña wrote:
> On Sun, Oct 09, 2005 at 01:03:38PM +0300, George Danchev wrote:
> > On Sunday 09 October 2005 03:10, Henning Makholm wrote:
> > > > The CVSup requires Modula-3 compilator to build, so also I'm
> > > > planning to package Ezm3 - An Easier Modula-3 Distribution, which is
> > > > designated to compile CVSup only.
> > >
> > > Best of luck with that. Torsten might still be interested, too.
> >
> > CVSync [1] is a possible alternative to CVSup, not compatible with it,
> > but written in plain C.
>
> That one looks interesting, I did not find it when I was googling for
> alternatives to CVSup. I would love to see something like this packaged so
> that we could distribute copies of our CVS worlwide and not have issues if
> we have any issues with the servers holding our CVS in the future.

Personally I'm interesting in packaging the CVSup, because I'd like to mirror 
some archives which are distributed with CVSup only. There is no alternative 
for such repositories.

I've uploaded the ezm3 package to the Incoming queue. The packages are also 
available at `deb http://people.debian.org/~dexter ezm3 sid' so you can 
compile the CVSup for your own or wait for my cvsup package.

-- 
 .''`.Piotr Roszatycki, Netia SA
: :' :mailto:[EMAIL PROTECTED]
`. `' mailto:[EMAIL PROTECTED]
  `-

Bug#333120: ITP: icu4j -- International Components for Unicode for Java

[Seo Sanghyeon]

Package: wnpp
Severity: wishlist
Owner: Seo Sanghyeon <[EMAIL PROTECTED]>

* Package name: icu4j
  Version : 3.4
  Upstream Author : IBM
* URL : http://icu.sourceforge.net/
* License : MIT/X
  Description : International Components for Unicode for Java

 ICU4J provides Unicode and internalization support for Java.
 .
 ICU4J implements Unicode collation and normalization, character set
 detection, script transliteration, text boundary analysis (word and
 line breaks), and international calendars (Chinese, Hebrew, Islamic),
 among other things.
 .
 ICU4J team works together with Sun, and in some cases, part of ICU4J
 gets included in a later release of Java. However, the most current
 and complete version is found in ICU4J.
 .
 Homepage: http://icu.sourceforge.net/


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

Bug#333123: ITP: libcatalyst-plugin-static-simple-perl -- Make serving static pages in Catalyst painless

[Krzysztof Krzyzaniak (eloy)]

Package: wnpp
Severity: wishlist
Owner: "Krzysztof Krzyzaniak (eloy)" <[EMAIL PROTECTED]>

* Package name: libcatalyst-plugin-static-simple-perl
  Version : 0.09
  Upstream Author : Andy Grundman, <[EMAIL PROTECTED]>.
* URL : 
http://search.cpan.org/~agrundma/Catalyst-Plugin-Static-Simple-0.08/
* License : (perl: GPL, Artistic)
  Description : Make serving static pages in Catalyst painless

 The Static::Simple plugin is designed to make serving static content in your
 application during development quick and easy, without requiring a single
 line of code from you.
 
 It will detect static files used in your application by looking for file
 extensions in the URI. By default, you can simply load this plugin and it
 will immediately begin serving your static files with the correct MIME type.
 The light-weight MIME::Types module is used to map file extensions to
 IANA-registered MIME types.
   
-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)


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

Please help me with this script!

[Mihai Felseghi]

 Hello , my name is Mihai Felseghi and I am
interesed in becoming an Debian maintainer and for the start I want to
build some packages on my own machine and learning how to do it .
    One of these days I was reading the "Debian New
Maintainers' Guide" and found a script wich finds out what packages are
nedded for building another package  :
   
   strace -f -o /tmp/log ./configure
# or make instead of ./configure, if the package doesn t use autoconf
for x in  dpkg -S $(grep open /tmp/log|\
   
perl -pe 's!.* open\(\"([^\"]*).*!$1!' |\
   
grep "^/"| sort | uniq|\
   
grep -v "^\(/tmp\|/dev\|/proc\)" ) 2>/dev/null|\
   
cut -f1 -d":"| sort | uniq'; \
    do \
echo -n "$x (>=" 'dpkg -s $x|grep ^Version|cut -f2 -d":" ' "), "; \
done

but this does not work or maybe I don't know how to use it .

 So please help me with this issue , maybe you could give an
advice where to find such a script or what I have to modify to make
this work.
 
 Sincerely yours Mihai Felseghi !

Bug#333152: ITP: ruby-v4l -- An extension library for capture pictures in Ruby using Video4Linux.

[Takuo KITAME]

Package: wnpp
Severity: wishlist
Owner: Takuo KITAME <[EMAIL PROTECTED]>


* Package name: ruby-v4l
  Version : 0.1.2
  Upstream Author : Paulo Matias 
* URL : http://rubyforge.org/projects/ruby-v4l/
* License : LGPL
  Description : An extension library for capture pictures in Ruby using 
Video4Linux.

from README:
 Ruby-V4l is a Ruby extension library that provides a class for using
 Video4Linux Capture API.


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

apt-get wants to remove hotplug?

[Alejandro Bonilla]

Hi,

In Sid, apt-get wants to remove hotplug.

Is udev replacing it for good or this is just b0rken?

.Alejandro


The following packages will be REMOVED:
  hotplug libdb4.1-dev
The following NEW packages will be installed:
  libdb4.2-dev
The following packages will be upgraded:
  abiword-common abiword-gnome cpp dialog eject evolution
  evolution-data-server evolution-data-server-dev evolution-dev
  evolution-exchange evolution-plugins fdutils finger fluxbox gcc gimp
  gimp-data gkrellm-hdplop gnome-nettool libavcodeccvs libavutilcvs0
  libcamel1.2-0 libcamel1.2-dev libdirectfb-0.9-22 libebook1.2-3
  libebook1.2-dev libecal1.2-2 libecal1.2-dev libedata-book1.2-2
  libedata-book1.2-dev libedata-cal1.2-1 libedata-cal1.2-dev
  libedataserver1.2-4 libedataserver1.2-dev libedataserverui1.2-4
  libedataserverui1.2-dev libegroupwise1.2-5 libegroupwise1.2-dev libgimp2.0
  libgnome2-vfs-perl libneon23 liborbit2 liborbit2-dev libpango1.0-0
  libpango1.0-common libpango1.0-dev libpostproccvs0 libtext-charwidth-perl
  libtext-iconv-perl libtext-wrapi18n-perl libtiff4 mencoder-586
  module-init-tools mplayer-586 openssh-client openssh-server python-gtk-1.2
  ssh telnet udev wget
61 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 41.4MB of archives.
After unpacking 2359kB of additional disk space will be used.
Do you want to continue [Y/n]? 



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

Re: apt-get wants to remove hotplug?

[Jason Clinton]

On Monday 10 October 2005 01:37 pm, Alejandro Bonilla wrote:
> Hi,
>
> In Sid, apt-get wants to remove hotplug.
>
> Is udev replacing it for good or this is just b0rken?
>
> .Alejandro

Don't do it. See the previous thread titled 'udev'.

Your mouse will no longer work.

There's a new version of udev coming soon which can safely replace hotplug.

-- 
I use digital signatures and encryption. My key is stored at pgp.mit.edu key
ID code: "0x8DB3BF09". F: F628 D9D3 E57A C281 5EFE  7DF7 B52A A393 8DB3 BF09


pgprtM1Yw4kMQ.pgp
Description: PGP signature

Re: apt-get wants to remove hotplug?

[Armin Berres]

Alejandro Bonilla wrote:
> Hi,
> 
> In Sid, apt-get wants to remove hotplug.
> 
> Is udev replacing it for good or this is just b0rken?

It has been announced here:
http://lists.debian.org/debian-devel/2005/08/msg01454.html

Did it today and it works fine.


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

Re: apt-get wants to remove hotplug?

[Daniel Burrows]

On Mon, Oct 10, 2005 at 01:47:52PM -0500, Jason Clinton <[EMAIL PROTECTED]> was 
heard to say:
> On Monday 10 October 2005 01:37 pm, Alejandro Bonilla wrote:
> > Hi,
> >
> > In Sid, apt-get wants to remove hotplug.
> >
> > Is udev replacing it for good or this is just b0rken?
> >
> > .Alejandro
> 
> Don't do it. See the previous thread titled 'udev'.
> 
> Your mouse will no longer work.
> 
> There's a new version of udev coming soon which can safely replace hotplug.

  Hm, doesn't just manually loading mousedev (and putting it in
/etc/modules) get things working again?

  Daniel


signature.asc
Description: Digital signature

Re: apt-get wants to remove hotplug?

[James Vega]

On Mon, Oct 10, 2005 at 02:37:53PM -0400, Alejandro Bonilla wrote:
> Hi,
>
> In Sid, apt-get wants to remove hotplug.
>
> Is udev replacing it for good or this is just b0rken?

From udev's changelog (available online at
):

   * Added support for coldplug and merged the hotplug scripts left.
 Switched from udevstart to udevsynthesize. (Closes: #329226)
   * Added conflicts with hotplug and with module-init-tools releases without
 support for /etc/hotplug/blacklist.d/.

James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>


pgpyA3RafmiKk.pgp
Description: PGP signature

Re: apt-get wants to remove hotplug?

[Jason Clinton]

On Monday 10 October 2005 01:54 pm, Daniel Burrows wrote:
>   Hm, doesn't just manually loading mousedev (and putting it in
> /etc/modules) get things working again?

That's not the only problem:

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332905
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332898
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332946

-- 
I use digital signatures and encryption. My key is stored at pgp.mit.edu key
ID code: "0x8DB3BF09". F: F628 D9D3 E57A C281 5EFE  7DF7 B52A A393 8DB3 BF09


pgpLITuOQQVV9.pgp
Description: PGP signature

Re: apt-get wants to remove hotplug?

[Francesco Paolo Lovergine]

On Mon, Oct 10, 2005 at 11:54:11AM -0700, Daniel Burrows wrote:
>   Hm, doesn't just manually loading mousedev (and putting it in
> /etc/modules) get things working again?
> 

Mousedev, evdev and usbmouse here, to have a working setup for X with
a synaptics touchpad and an usb mouse.

-- 
Francesco P. Lovergine


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

Your premier source for all ATI powered gear.

[Clifford Barrera]

Your technology expert.
that will be accessing this feed.You are not allowed to access this page from 
this IP address.


The pure and simple truth is rarely pure and never simple.  
The ultimate test of a relationship is to disagree but hold hands. 

No pressure, no diamonds. 
Do what's right. Do it right. Do it right now.   

Crime does not pay ... as well as politics.
Our ability to delude ourselves may be an important survival tool.  



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

Re: apt-get wants to remove hotplug?

[Alejandro Bonilla]

On Mon, 10 Oct 2005 13:47:52 -0500, Jason Clinton wrote
> On Monday 10 October 2005 01:37 pm, Alejandro Bonilla wrote:
> > Hi,
> >
> > In Sid, apt-get wants to remove hotplug.
> >
> > Is udev replacing it for good or this is just b0rken?
> >
> > .Alejandro
> 
> Don't do it. See the previous thread titled 'udev'.
> 
> Your mouse will no longer work.
> 
> There's a new version of udev coming soon which can safely replace hotplug.

OK Clinton! ;-)

So, udev is replacing hotplug for good? I guess that I will give it a try
later on...

Also, did anyone try a ipw2100 or ipw2200 with this? Will
/etc/hotplug/firmware agent still work by loading the firmwares with no
additional action from the driver code?

.Alejandro


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

Re: removal of support for /etc/hotplug/usb/

[Shaun Jackman]

I haven't found a great sysfs node to use for Creative Labs devices.
This is the best I've found so far:
$ udevinfo -ap /sys/bus/usb/devices/1-2.3/1-2.3:1.0
...
  looking at class device '/sys/bus/usb/devices/1-2.3/1-2.3:1.0':
SUBSYSTEM="unknown"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="dc"
SYSFS{bInterfaceNumber}="00"
SYSFS{bInterfaceProtocol}="b0"
SYSFS{bInterfaceSubClass}="a0"
SYSFS{bNumEndpoints}="04"
SYSFS{modalias}="usb:v0471p0222d0100dcDCdsc00dp00ic*isc*ip*"

Is this the correct place from where to start writing a udev rule?

Cheers,
Shaun

2005/9/15, Marco d'Itri <[EMAIL PROTECTED]>:
> After having been deprecated for a long time, support for map files in
> the /etc/hotplug/usb/ directory will be removed from the udev-hotplug
...
> The affected packages are:
...
> libnjb-hotplug
...

Re: apt-get wants to remove hotplug?

[Jason Clinton]

On Monday 10 October 2005 02:27 pm, you wrote:
> Also, did anyone try a ipw2100 or ipw2200 with this? Will
> /etc/hotplug/firmware agent still work by loading the firmwares with no
> additional action from the driver code?

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332946

-- 
I use digital signatures and encryption. My key is stored at pgp.mit.edu key
ID code: "0x8DB3BF09". F: F628 D9D3 E57A C281 5EFE  7DF7 B52A A393 8DB3 BF09


pgpMf70AqNKht.pgp
Description: PGP signature

Re: When is the C++ transition needed?

[Daniel Jacobowitz]

On Thu, Oct 06, 2005 at 09:24:19PM -0400, Nathanael Nerode wrote:
> Brian Carlson wrote:
> >> You must not pass by reference with an extern "C" declaration, because C 
> >> doesn't support that.
> Dan Jacobowitz wrote:
> >Why not?  An extern C definition doesn't mean that it needs to be
> >usable from C.  It just means to use the C calling convention.
> Perhaps because there is no C calling convention for passing by reference?  
> How to pass arguments is part of the calling convention.  :-P  You can pass 
> C++-only objects, certainly, but you have to be able to pass them in a way 
> which is understood in the C calling convention.

That's incorrect.  The C++ ABI uses a defined convention for passing by
reference, and with a different prototype and some care, or from
assembly, you can duplicate the effect.

The primary effect of extern "C" is just disabling mangling.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


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

Re: removal of support for /etc/hotplug/usb/

[Shaun Jackman]

The udev rule I've written for the Creative Labs Nomad Jukebox looks like this:

SYSFS{modalias}="usb:v0471p0222*", NAME="njb%n", GROUP="audio", MODE="0666"

udevtest seems to indicate some success:

$ udevtest /sys/bus/usb/devices/1-2.3/1-2.3\:1.0/
version 056
looking at '/bus/usb/devices/1-2.3/1-2.3:1.0/'
opened class_dev->name='1-2.3:1.0'
configured rule in '/etc/udev/rules.d/nomad.rules[1]' applied,
'1-2.3:1.0' becomes 'njb%n'

When I plug the device in, the node doesn't actually seem to be created though:

$ find /dev /sys -name \njb*
$

I would like the /proc/bus/usb node to be symlinked to /dev/njb%d,
with the correct permissions applied, as well as loading the "fuse"
kernel module. Is this possible?

Cheers,
Shaun

2005/10/10, Shaun Jackman <[EMAIL PROTECTED]>:
...
> SYSFS{modalias}="usb:v0471p0222d0100dcDCdsc00dp00ic*isc*ip*"
>
> Is this the correct place from where to start writing a udev rule?
>
> Cheers,
> Shaun
>
> 2005/9/15, Marco d'Itri <[EMAIL PROTECTED]>:
> > After having been deprecated for a long time, support for map files in
> > the /etc/hotplug/usb/ directory will be removed from the udev-hotplug
> ...
> > The affected packages are:
> ...
> > libnjb-hotplug
> ...

Re: apt-get wants to remove hotplug?

[Marco d'Itri]

On Oct 10, Jason Clinton <[EMAIL PROTECTED]> wrote:

> On Monday 10 October 2005 02:27 pm, you wrote:
> > Also, did anyone try a ipw2100 or ipw2200 with this? Will
> > /etc/hotplug/firmware agent still work by loading the firmwares with no
> > additional action from the driver code?
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332946
Totally unrelated, this is usually only a cosmetic issue.
Firmware loading works fine, as long as firmwares are available at the
beginning of the boot process (so they cannot in /usr if it is a
different file system). This is documented in NEWS.Debian.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Re: apt-get wants to remove hotplug?

[Jason Clinton]

On Monday 10 October 2005 01:54 pm, Daniel Burrows wrote:
>   Hm, doesn't just manually loading mousedev (and putting it in
> /etc/modules) get things working again?

Also note that libgphoto2-2 (upon which much of the desktop metapackages 
depend) will conflict with the new udev-0.070-3 until a NMU can be processed 
as the maintainer is on vacation.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332936

-- 
I use digital signatures and encryption. My key is stored at pgp.mit.edu key
ID code: "0x8DB3BF09". F: F628 D9D3 E57A C281 5EFE  7DF7 B52A A393 8DB3 BF09


pgpfrNbjdnu4V.pgp
Description: PGP signature

Re: apt-get wants to remove hotplug?

[Marco d'Itri]

On Oct 10, Francesco Paolo Lovergine <[EMAIL PROTECTED]> wrote:

> Mousedev, evdev and usbmouse here, to have a working setup for X with
usbmouse is blacklisted, so it's not supposed to be loaded.
The driver for USB mice is usbhid.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Re: removal of support for /etc/hotplug/usb/

[Marco d'Itri]

On Oct 10, Shaun Jackman <[EMAIL PROTECTED]> wrote:

(I hope this fully covers the changes needed.)

> The udev rule I've written for the Creative Labs Nomad Jukebox looks like 
> this:
> 
> SYSFS{modalias}="usb:v0471p0222*", NAME="njb%n", GROUP="audio", MODE="0666"

It would work, but is wrong. If it were a block device you could use:

BUS=="usb", SYSFS{idVendor}=="0471", SYSFS{idProduct}=="0222", \
SYMLINK+="njb%n", GROUP="audio"

(There is no point in changing the group of a world-writeable device,
and the default is MODE="0660".)

> When I plug the device in, the node doesn't actually seem to be created 
> though:
> 
> $ find /dev /sys -name \njb*
> $

But it appears that your package is an user space driver which uses
libusb and the /proc/bus/usb/ interface:

> I would like the /proc/bus/usb node to be symlinked to /dev/njb%d,
> with the correct permissions applied, as well as loading the "fuse"
> kernel module. Is this possible?

There is no point in creating symlinks, because libusb does not care.
The current kernels only provide the /proc/bus/usb/ interface, so you
still need to use a script to change the file permissions:

ACTION=="add", BUS=="usb", SYSFS{idVendor}=="0471", SYSFS{idProduct}=="0222", \
RUN+="/etc/hotplug/usb/nomadjukebox"

2.6.14 kernels will provide real devices in /dev/bus/usb/, and udev will
be able to directly change their permissions:

SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0471", SYSFS{idProduct}=="0222", \
GROUP="audio"

I do not know what the fuse kernel driver is, but usually drivers
provide a module alias to be matched against the $MODALIAS value
provided by hotplug so they can be automatically loaded.
If they need special handling you can just add a RUN rule (do not forget
to match them on ACTION=="add").

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Bug#333211: ITP: xml-light -- mininal XML parser and printer for OCaml

[Sylvain LE GALL]

Package: wnpp
Severity: wishlist
Owner: Sylvain Le Gall <[EMAIL PROTECTED]>

* Package name: xml-light
  Version : 2.2
  Upstream Author : Nicolas Cannasse ([EMAIL PROTECTED])
* URL : http://tech.motion-twin.com/xmllight.html
* License : LGPL
  Description : mininal XML parser and printer for OCaml

 This is a XML parser and printer, designed to help parsing basic XML
 document into OCaml data structures and printing it back to a XML document.
 
 It also supports DTD.
 
 This package is a dependency of cameleon, another OCaml program.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.3-grand
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)


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

Automatically sending test suite results from buildds to upstream

[Florian Ragwitz]

Hello,

I'm the maintainer of the pugs package. It features a large testsuite
which is run when the package is built on the buildds. The informations
generated by this testsuite (in form of html smoke reports) are really
useful for upstream authors (that I belong to) to track down bugs,
especially on unusual architectures.

Therefor I'd like to automatically upload these results to
http://smoke.pugscode.org after the packages are built on the buildds.
Is it an acceptable behaviour of source packages to upload informations
to various places without asking the user for permission like the
polularity-contest package for example? Of course, it could be disabled
by default and may be activated using environment hooks or other hacks.
But that would prevent us from using the buildd results, that are
produced anyway, to improve the quality of the upstream software.

How should I proceed?


Regards,
Flo

-- 
BOFH excuse #199:
the curls in your keyboard cord are losing electricity.


signature.asc
Description: Digital signature

Bug#333222: ITP: libarchive -- Single libary to read/write tar, cpio, pax, zip, etc. files

[John Goerzen]

Package: wnpp
Severity: wishlist
Owner: John Goerzen <[EMAIL PROTECTED]>

* Package name: libarchive
  Version : 1.02.033
  Upstream Author : Tim Kientzle <[EMAIL PROTECTED]>
Part of FreeBSD
* URL : :pserver:[EMAIL PROTECTED]:/home/ncvs
* License : BSD
  Description : Single libary to read/write tar, cpio, pax, zip, etc. files

 The libarchive library provides a flexible interface for reading and
 writing streaming archive files such as tar and cpio.  The library is
 inherently stream-oriented; readers serially iterate through the archive,
 writers serially add things to the archive.  In particular, note that
 there is no built-in support for random access nor for in-place
 modification.
 .
 libarchive can read at least five tar formats, four cpio formats,
 ISO9660 CD/DVD images (including RockRidge extensions), and ZIP
 files.
 .
 libarchive can write two tar formats (ustar and pax), one cpio format
 (odc/POSIX), and two types of shar files (with and without uuencoding).


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-rc4-mm2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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

Re: Automatically sending test suite results from buildds to upstream

[Daniel Jacobowitz]

On Tue, Oct 11, 2005 at 01:35:06AM +0200, Florian Ragwitz wrote:
> Therefor I'd like to automatically upload these results to
> http://smoke.pugscode.org after the packages are built on the buildds.
> Is it an acceptable behaviour of source packages to upload informations
> to various places without asking the user for permission like the
> polularity-contest package for example? Of course, it could be disabled
> by default and may be activated using environment hooks or other hacks.
> But that would prevent us from using the buildd results, that are
> produced anyway, to improve the quality of the upstream software.
> 
> How should I proceed?

Another option is to either leave the information in the buildd log
files (i.e. send it to stdout), or to include test results in the .deb
files and retrieve them after the build.  That latter is what the GCC
packages do.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


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

Re: Automatically sending test suite results from buildds to upstream

[Florian Ragwitz]

On Mon, Oct 10, 2005 at 08:07:52PM -0400, Daniel Jacobowitz wrote:
> On Tue, Oct 11, 2005 at 01:35:06AM +0200, Florian Ragwitz wrote:
> > Therefor I'd like to automatically upload these results to
> > http://smoke.pugscode.org after the packages are built on the buildds.
> > Is it an acceptable behaviour of source packages to upload informations
> > to various places without asking the user for permission like the
> > polularity-contest package for example? Of course, it could be disabled
> > by default and may be activated using environment hooks or other hacks.
> > But that would prevent us from using the buildd results, that are
> > produced anyway, to improve the quality of the upstream software.
> > 
> > How should I proceed?
> 
> Another option is to either leave the information in the buildd log
> files (i.e. send it to stdout)

That's possible of course, but much more work for me, especially as I
plan to release much SVN snapshots in erperimental soon.

> or to include test results in the .deb files and retrieve them after
> the build.  That latter is what the GCC packages do.

I don't like that solution. Users of the package don't care about the
test results so it's useless to bloat the packages with them.


-Flo

-- 
BOFH excuse #169:
broadcast packets on wrong frequency


signature.asc
Description: Digital signature

Bug#333230: ITP: bsdtar -- tar(1) from FreeBSD, with read support for tar/zip/ISO9660/cpio using libarchive

[John Goerzen]

Package: wnpp
Severity: wishlist
Owner: John Goerzen <[EMAIL PROTECTED]>

* Package name: bsdtar
  Version : 1.02.034
  Upstream Author : [EMAIL PROTECTED]
* URL : http://people.freebsd.org/~kientzle/libarchive/
* License : BSD
  Description : tar(1) from FreeBSD, with read support for 
tar/zip/ISO9660/cpio using libarchive

 The bsdtar program has a number of advantages over previous tar
 implementations:
 .
 * Library. Since the core functionality is in a library, it can be
   used by other tools, such as pkg_add.
 .
 * Automatic format detection. Libarchive automatically detects the
   compression (none/gzip/bzip2) and format (old tar, ustar, gnutar,
   pax, cpio, iso9660, zip) when reading archives. It does this for
   any data source.
 .
 * Pax Interchange Format Support. This is a POSIX/SUSv3 extension to
   the old "ustar" tar format that adds arbitrary extended attributes
   to each entry. Does everything that GNU tar format does, only
   better.
 .
 * Handles file flags, ACLs, arbitrary pathnames, etc. Pax interchange
   format supports key/value attributes using an easily-extensible
   technique. Arbitrary pathnames, group names, user names, file sizes
   are part of the POSIX standard; libarchive extends this with
   support for file flags, ACLs, and arbitrary device numbers.
 .
 * GNU tar support. Libarchive reads most GNU tar archives. If there
   is demand, this can be improved further.
 .
 * BSD license. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-rc4-mm2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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

Bug#333226: ITP: dibbler -- portable, open DHCPv6 implementation (server, relay and client)

[Tomasz Mrugalski]

Package: wnpp
Severity: wishlist
Owner: Tomasz Mrugalski <[EMAIL PROTECTED]>


* Package name: dibbler
  Version : 0.4.1
  Upstream Author : Tomasz Mrugalski <[EMAIL PROTECTED]>
* URL : http://klub.com.pl/dhcpv6/
* License : GPL
  Description : portable, open DHCPv6 implementation (server, relay and 
client)

There will be 4 packages: -client, -server, -relay and -doc.

Package: dibbler-server
 This is a DHCPv6 server. It supports both stateful (i.e. IPv6 address
 granting) as well as stateless (i.e. options granting) autoconfiguration
 modes of DHCPv6 protocol. Relays are also supported. Install Dibbler
 server if you'd like to have IPv6 hosts automatically configured in
 your network.

Package: dibbler-client
 This is a DHCPv6 client. It supports both statefull (i.e. IPv6 address
 granting) as well as stateless (i.e. option granting) autoconfiguration
 modes of the DHCPv6 protocol. Besides basic capabilities, it supports
 various DHCPv6 extensions, e.g. option renewal. Install Dibber client if
 you want to obtain IPv6 addresses and options from DHCPv6 server.

Package: dibbler-relay
 This is a DHCPv6 relay. Relays are used as proxies between server and
 clients. Main advantage is the ability to support multiple remote links
 using only one server. Install Dibbler relay if you want to serve
 multiple not physically connected links with one DHCPv6 server.

Package: dibbler-doc
 User's Guide as well as Developer's Guide is included in this package.
 That documentation covers all aspects of Dibbler DHCPv6 implementation:
  - server, client and relay usage and configuration
  - various tips and frequently asked questions
  - internal structure/code description and hints for developers


-- System Information:
Debian Release: 3.0
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1-mipv6
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) (ignored: LC_ALL set to 
pl_PL)


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

ITP: adm8211-source -- GPL driver for ADMtek adm8211-based 802.11b wifi adapter

[Jean-Marc Ranger]

Package: wnpp
Severity: wishlist
Owner: "Jean-Marc Ranger" <[EMAIL PROTECTED]>

* Package name: adm8211-source
  Version : 0.0.20050620
  Upstream Author : Michael Wu <[EMAIL PROTECTED]>
* URL : http://aluminum.sourmilk.net/adm8211/
* License : GPL
  Description : GPL driver for ADMtek adm8211-based 802.11b wifi 
adapter


This package provides the source code for the adm8211 kernel modules. 
The Infineon-ADMtek ADM8211A, ADM8211B and ADM8211C chip can be found in 
the following PCI/mini-PCI/Cardbus 802.11b wiresless adapters:

Xterasys Cardbus XN-2411b
Blitz - NetWave Point PC
TrendNet 221pc
Belkin F5D6001
SMC 2635W
Linksys WPC11 v1
Fiberline FL-WL-200X
3com office connect card (3CRSHPW796)
Corega WLPCIB-11
SMC 2602W V2 EU
D-Link DWL-520 Revision C
Blitz BWP612
D-Link DWL-650 rev. L1

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.13.3
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)


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

Re: Automatically sending test suite results from buildds to upstream

[Steinar H. Gunderson]

On Tue, Oct 11, 2005 at 01:35:06AM +0200, Florian Ragwitz wrote:
> Therefor I'd like to automatically upload these results to
> http://smoke.pugscode.org after the packages are built on the buildds.

Make your package building fail whenever a test in the testsuite fails? The
FTBFS bugs and the buildd logs are sure to tell you what test went wrong.
Having a known-bad package built is a generally bad thing anyhow, so you
won't really lose much on failing it :-)

/* Steinar */
-- 
Homepage: http://www.sesse.net/


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

Gary Gray is out of the office indefinitely.

[Gary . Gray]

I will be out of the office starting  2005/09/09 and will not return until
2010/01/28.

For all enquiries please contact:
Michael Van Alphen @ 519-888-3900 x7461
or
Paul Sergi @ 519-888-3900 x7815

---
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure.  If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---
Le présent message électronique (y compris les pièces qui y sont annexées,
le cas échéant) s'adresse au destinataire indiqué et peut contenir des
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le
destinataire de ce document, nous vous signalons qu'il est strictement
interdit de le diffuser, de le distribuer ou de le reproduire. Si ce
message vous a été transmis par erreur, veuillez en informer l'expéditeur
et le supprimer immédiatement.
---

Re: Automatically sending test suite results from buildds to upstream

[Jeroen Massar]

On Tue, 2005-10-11 at 02:13 +0200, Florian Ragwitz wrote:
> On Mon, Oct 10, 2005 at 08:07:52PM -0400, Daniel Jacobowitz wrote:

> > or to include test results in the .deb files and retrieve them after
> > the build.  That latter is what the GCC packages do.
> 
> I don't like that solution. Users of the package don't care about the
> test results so it's useless to bloat the packages with them.

Stick the debug files into a seperate -debug package, which nobody will
install anyway and just consumes some archive space.

Greets,
 Jeroen



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