Re: bug #292231 - fixed in upstream, pending 412 days

[Vincent Bernat]

OoO En  cette fin  de nuit blanche  du mardi  05 août 2008,  vers 06:43,
jaromil <[EMAIL PROTECTED]> disait :

> the manpage was fixed about 400 days ago and communicated to mantainer
> (also in cc:). mantainer Christian stated he would fix it but doesn't,
> still  now he  is  too busy.   i  am in  contact  with another  debian
> neo-mantainer  Luca (also  in  cc:)  and myself  i  can co-mantain  as
> upstream author,  we offered to  Christian to add us  as co-mantainers
> and he agrees but then cannot do it.

> we are  blocked as he  cannot add us  apparently for no time,  even if
> received  clear instructions  from  Luca. how  we  proceed from  that?
> package hasciicam is dropping out of lenny because of this.

Ask for  sponsorship on [EMAIL PROTECTED] For  a RC fix,  you will surely
find a sponsor.
-- 
BOFH excuse #155:
Dumb terminal


pgp159fZupmsq.pgp
Description: PGP signature

bug #292231 - fixed in upstream, pending 412 days

[jaromil]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


re all,

scroll down for bug references, here it follows human written desc:

the manpage was fixed about 400 days ago and communicated to mantainer
(also in cc:). mantainer Christian stated he would fix it but doesn't,
still  now he  is  too busy.   i  am in  contact  with another  debian
neo-mantainer  Luca (also  in  cc:)  and myself  i  can co-mantain  as
upstream author,  we offered to  Christian to add us  as co-mantainers
and he agrees but then cannot do it.

we are  blocked as he  cannot add us  apparently for no time,  even if
received  clear instructions  from  Luca. how  we  proceed from  that?
package hasciicam is dropping out of lenny because of this.

thanks for your kind help

- - Forwarded message from DDPOMail robot <[EMAIL PROTECTED]> -

From: DDPOMail robot <[EMAIL PROTECTED]>
To: Denis Rojo <[EMAIL PROTECTED]>
Subject: Possible problems in your Debian packages

=== hasciicam: (you are subscribed on the PTS)
= 1 bug(s) that should be fixed for the next Debian release:
- - #292231 
  [NONFREE-DOC:GFDL1.1] making the entire manpage invariant is not consistent 
with the DFSG
= Not in testing for 412 days.
  If things don't change, it won't be part of lenny!
  See 

- - End forwarded message -

- -- 
  Jaromil, dyne.org developer, http://jaromil.dyne.org

GPG: 779F E8B5 47C7 3A89 4112  64D0 7B64 3184 [ B534 0B5E ]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIl9pye2QxhLU0C14RAi/nAJ0dO/OEcQ7HT5DP7mm979sXIRX+dwCg37bD
y//q7NKEiyrPfUj1viWB3F0=
=oO+h
-END PGP SIGNATURE-


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

Re: Please test syslinux 3.71+dfsg-1

[Daniel Baumann]

Adeodato Simó wrote:
> Hi! In order to make life of new release asistants easier, we'd like a
> filter that works as seen below. Thanks.

This mail was explicically requested from Luk who was going through the
diff[0] with me this afternoon, in order to get as much feedback as
possible to the syslinux bugfix release. Please keep your not funny
jokes for yourself next time rather than to piss off people with good
intentions, thanks.

Regards,
Daniel

[0]
http://git.debian.net/?p=syslinux.git;a=commitdiff;h=e8f8522db8153e02fc48e7ef33b4a0153de20344;hp=fc1829af40aacccd6c625ffab0f34f2ad4402b2c

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: Please test syslinux 3.71+dfsg-1

[Roberto C . Sánchez]

On Tue, Aug 05, 2008 at 12:04:36AM +0100, Adeodato Simó wrote:
> Package: filters-ai
> Severity: wishlist
> 
> Hi! In order to make life of new release asistants easier, we'd like a
> filter that works as seen below. Thanks.
> 
> Input:
> 
>   | From: Daniel Baumann
>   | 
>   | Hi,
>   | 
>   | new syslinux bugfix only release was uploaded to unstable. Most
>   | prominently, it fixes some stuff with pxelinux and serial console access
>   | parameters, as well as with general chainloading when using logical
>   | partitions.
>   | 
>   | I did test the version on most common usage cases and found no
>   | regression compared to 3.70+dfsg-3.
>   | 
>   | Please test it as i intend to ask for freeze exception when it has aged
>   | 10 days in unstable.
>   | 
>   | Regards,
>   | Daniel
> 
> Output:
> 
>   |  plz test my pkgs so I can has leverage against the release 
> team, kthxbye
> 

I don't get it.  Isn't the amount of testing received one of the points
the release team considers when deciding whether or not grant an
exception?  If it were not, I would be quite surprised.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Marco d'Itri]

On Aug 05, Russ Allbery <[EMAIL PROTECTED]> wrote:

> I disagree.  The Release file in the archive is a configuration file that
> is part of the software interface to the archive.  The terminology that it
> uses refers to capabilities within the archive maintenance software and
> within the software that downloads files from a Debian archive.  It does
> not have anything to do with legal, administrative, or focus decisions
> taken by the Debian project.
Agreed. Let's stop this idiocy/trolling/whatever.

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Re: Please test syslinux 3.71+dfsg-1

[Adeodato Simó]

Package: filters-ai
Severity: wishlist

Hi! In order to make life of new release asistants easier, we'd like a
filter that works as seen below. Thanks.

Input:

  | From: Daniel Baumann
  | 
  | Hi,
  | 
  | new syslinux bugfix only release was uploaded to unstable. Most
  | prominently, it fixes some stuff with pxelinux and serial console access
  | parameters, as well as with general chainloading when using logical
  | partitions.
  | 
  | I did test the version on most common usage cases and found no
  | regression compared to 3.70+dfsg-3.
  | 
  | Please test it as i intend to ask for freeze exception when it has aged
  | 10 days in unstable.
  | 
  | Regards,
  | Daniel

Output:

  |  plz test my pkgs so I can has leverage against the release team, 
kthxbye

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Joaquín Sabina - Rebajas de enero


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Russ Allbery]

Giacomo Catenazzi <[EMAIL PROTECTED]> writes:
> Russ Allbery wrote:

>> I recommend not attributing such judgements to the configuration files
>> of software packages.

> Sorry???

> It is more that a configuration file, and BTW the same notation it is
> also used by apt. Archive and its format are an area of ftp-master.

I disagree.  The Release file in the archive is a configuration file that
is part of the software interface to the archive.  The terminology that it
uses refers to capabilities within the archive maintenance software and
within the software that downloads files from a Debian archive.  It does
not have anything to do with legal, administrative, or focus decisions
taken by the Debian project.

Mixing the terminology used for a software package with the terminology
used for the founding organizational documents of the project is a
mistake, in my opinion.  The Debian archive software is general software
that could be used for any project, even with an entirely different use of
the component feature that has nothing to do with licensing.  We happen to
use it for licensing and to separate things that are part of the
distribution from things that are not, but this is not in any way inherent
to the component concept within the archive software.

> The bug is only relevant to policy, but as stated by policy team,
> debian/copyright, interpretation of DFSG, archive sections ("devel",
> "libs", "mail"), etc. are areas outside policy, but they are in
> ftp-master hands.  So IMHO what "Debian" means (linked to DFSG) and what
> Lenny means (archive) is outside debian-policy (and outside of the cited
> bug).

> This is unfortunate.

I don't agree that this is the case to the extent that you describe, or
that it follows from that bug or from other Policy discussions, although I
agree that thet Constitution and Social Contract have more to say about
this than Policy does.

-- 
Russ Allbery ([EMAIL PROTECTED])   


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

Bug#493794: ITP: goocanvasmm -- C++ bindings for GooCanvas

[Iain Lane]

Package: wnpp
Severity: wishlist
Owner: Iain Lane <[EMAIL PROTECTED]>


* Package name: goocanvasmm
  Version : 0.9.0
  Upstream Author : The gtkmm development team
* URL : http://ftp.gnome.org/pub/gnome/sources/goocanvasmm/
* License : GPL
  Programming Lang: C++
  Description : C++ bindings for GooCanvas

 GooCanvas is a canvas widget for GTK+ that uses the cairo 2D library for 
 drawing. It has a model/view split, and uses interfaces for canvas items and 
 views, so you can easily turn any application object into canvas items.
 goocanvasmm is the C++ wrapper for GooCanvas

I already have a building and working package awaiting review at REVU[0]. After 
this is reviewed and accepted into Intrepid, I'll seek sponsorship in Debian.

Thanks,
Iain

[0] http://revu.ubuntuwire.com/details.py?package=goocanvasmm

-- System Information:
Debian Release: lenny/sid
  APT prefers hardy-updates
  APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, 
'hardy-proposed'), (500, 'hardy-backports'), (500, 'hardy')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-19-generic (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



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

Re: Bug#493645: ITP: nostromo -- small, simple, fast and secure httpd

[Ben Hutchings]

On Sun, 2008-08-03 at 21:09 +0100, Kai Hendry wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Kai Hendry <[EMAIL PROTECTED]>
> 
> * Package name: nostromo
>   Version : 1.8.6
>   Upstream Author : Marcus Glocker <[EMAIL PROTECTED]>
> * URL : http://www.nazgul.ch/dev.html
> * License : MIT
>   Programming Lang: C
>   Description : small, simple, fast and secure httpd

"Secure"?  Even though it allows parent directory traversal?  As has
been said time and time again, Debian doesn't need yet another tiny
httpd that inevitably turns out to have such flaws.

It doesn't get URI decoding right either.

Ben.

-- 
Ben Hutchings
Nothing is ever a complete failure; it can always serve as a bad example.


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

Re: Statically linking against bundled libagg

[Dominic Hargreaves]

On Mon, Aug 04, 2008 at 01:42:47AM +0200, Rene Engelhard wrote:

> You want -fPIC, both for your lib and agg. Try -lagg_pic if it exists
> (when I maintained agg I created it - OOo once used agg too and still
> has agg 2.4 in the code - unused by distros, though)

Ah, that's the clue that I needed to answer my main point. Thanks!

On Sun, Aug 03, 2008 at 04:46:55PM -0700, Russ Allbery wrote:

> It looks like libagg is only available as a static library and not as a
> shared library?  If so, to link it into a shared library, it must be built
> position-independent (-fPIC) on almost every platform except i386.  This
> error message, if libagg isn't PIC on any architecture, will likely result
> in FTBFS on many architectures, such as amd64.
> 
> Ideally, libagg should provide a shared library.  Otherwise, any package
> that links against the existing library would require a rebuild for any
> security vulnerabilities in the library.
> 
> Policy 10.2 covers this somewhat.

There seems to be some discussion of why no shared library is built in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377270

Cheers,
Dominic.

-- 
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Giacomo Catenazzi]

Russ Allbery wrote:
> Robert Millan <[EMAIL PROTECTED]> writes:
> 
>> Therefore Lenny is not Debian, but a superset of it?
>>
>> This is troubling.  Do you have any suggestions on how to address this?
> 
> I recommend not attributing such judgements to the configuration files of
> software packages.

Sorry???

It is more that a configuration file, and BTW the same notation it is
also used by apt. Archive and its format are an area of ftp-master.

And BTW the terminology was not important, and debian policy should
agree with the same reasoning:
Debian distribution is main (explicit written in policy, chapter 2).

"stable" has something called "main", "contrib" and "non-free"
(terminology changes, but not important in this case).
So "stable" is a super set of Debian distribution (aka "main").
"Judgement" was on such reasoning, not on the dak terminology.

"Debian distribution" is also used with other meanings,
but not relevant to the initial question.

I used "Release" file, because in 6 lines, DDs see the problem of
terminology of different "divisions" in Debian, and because it
is one of the few places where we find the name "lenny", which
was the initial problem.


> I'm looking for review of http://bugs.debian.org/473439, which tries to
> help clarify terminology in this area.  If you have a chance and care,
> please review that bug and second or discuss the proposed change in that
> bug.

The bug is only relevant to policy, but as stated by policy team,
debian/copyright, interpretation of DFSG, archive sections ("devel",
"libs", "mail"), etc. are areas outside policy, but they are in
ftp-master hands.
So IMHO what "Debian" means (linked to DFSG) and what Lenny means
(archive) is outside debian-policy (and outside of the cited bug).

This is unfortunate.

The terminology and the area of competences should be cleared defined
by debian project, and probably result to a common document
(with addition to all bureaucratic things, no to pass on other foot).

IMHO the Debian project should give developers (and users) more
importance, i.e. we need a single and consistent document.
Only internally Debian should defines the edit right of different
team (and in which area).

Unfortunately now it is done in the other direction:
actually the priority is on relevant teams and not to developers,
so DDs should check is few places new rules.
But this means also that teams doesn't coordinate and we have
different and confusing terminologies.

ciao
cate


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

Bug#493773: ITP: kvkbd -- Virtual keyboard for KDE

[Torsten Werner]

Package: wnpp
Severity: wishlist
Owner: Torsten Werner <[EMAIL PROTECTED]>

* Package name: kvkbd
  Version : 0.4.8
  Upstream Author : Todor Gyumyushev <[EMAIL PROTECTED]>
* URL : http://pan4os.info/main/index.php
* License : GPL-2
  Programming Lang: C++
  Description : Virtual keyboard for KDE

 Virtual keyboard for KDE for use with accessibility. Application contains
 a systray widget as well as a dockwidget.

(copied from the Ubuntu package)


Cheers,
Torsten



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

Re: Available papersizes vs. default papersizes

[Aaron M. Ucko]

Frank Küster <[EMAIL PROTECTED]> writes:

> I would like to solve a long-standing bug and finally make TeX aware of
> libpaper and its system-wide paper size setting.

Thanks; I, for one, would greatly appreciate that.

> However, taking the intersection of paper sizes the different program's
> configuration files accept as default, I end up with a4paper and letter.

AFAICT, those are also the only two sizes that standard locales use,
so I don't think supporting any others is particularly crucial (though
Johannes's suggestions are worth considering if you want to widen the
set slightly).

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[EMAIL PROTECTED]


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Russ Allbery]

Robert Millan <[EMAIL PROTECTED]> writes:

> Therefore Lenny is not Debian, but a superset of it?
>
> This is troubling.  Do you have any suggestions on how to address this?

I recommend not attributing such judgements to the configuration files of
software packages.

I'm looking for review of http://bugs.debian.org/473439, which tries to
help clarify terminology in this area.  If you have a chance and care,
please review that bug and second or discuss the proposed change in that
bug.

-- 
Russ Allbery ([EMAIL PROTECTED])   


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

Re: Available papersizes vs. default papersizes

[Frank Küster]

Johannes Wiedersich <[EMAIL PROTECTED]> wrote:

>> Some argued that every paper which can be fed to a printer on the
>> market might be used as default size on a particular system.
>
> If you'd like to use a different default, how difficult is the
> implementation for the user/administrator of the box in question?

It's quite straightforward to add new sizes to the configuration files
by hand, and also to make the the default size. Therefore it doesn't do
much harm when this has to be done by the local admin.  

And from the point of view of writing packaging scripts it isn't hard,
either: I can simply ignore sizes not available in the upstream scripts
(should I give a warning on stdout?).  

>> Do you have any suggestions?
>
> I forwarded your question to d-u. Maybe some 'users' over there have
> some suggestions of what they use/require... [3]

Thank you, good idea!

Regards, Frank

-- 
Frank Küster
Debian Developer (TeXLive)
ADFC Miltenberg
B90/Grüne KV Miltenberg


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Giacomo Catenazzi]

Robert Millan wrote:
> On Mon, Aug 04, 2008 at 03:18:24PM +0200, Giacomo A. Catenazzi wrote:
>> : Origin: Debian
>> : Label: Debian
>> : Suite: testing
>> : Codename: lenny
>> : Date: Mon, 04 Aug 2008 08:39:59 UTC
>> : Architectures: alpha amd64 arm armel hppa i386 ia64 mips mipsel 
>> powerpc s390 sparc
>> : Components: main contrib non-free
>> : Description: Debian x.y Testing distribution - Not Released
>>
>> So lenny is made from main (Debian), contrib and non-free.
> 
> Therefore Lenny is not Debian, but a superset of it?
> 
> This is troubling.  Do you have any suggestions on how to address this?

It is complex :-(

Debian is a distribution ("Origin" in dak terminology), which
has some distributions (stable, testing, unstable; "Suite" in dak
terminology, sometime named "archive" on apt).
But "Debian GNU/Linux distribution: build from the main category"
(note that "category" sometime is named "segment" or "area" or
"component") so we have an additional definition for distribution
and for Debian.

There are so many overloaded terms in Debian. So I agree
that it is confusing.

How to address? It is simple! Ask to the relevant people.
The original case was about "lenny" release/installation.
So ask to RM or d-i what lenny means on these groups (teams
or cabals or mailing-list or roles or ...)

;-)

ciao
cate


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

Please test syslinux 3.71+dfsg-1

[Daniel Baumann]

Hi,

new syslinux bugfix only release was uploaded to unstable. Most
prominently, it fixes some stuff with pxelinux and serial console access
parameters, as well as with general chainloading when using logical
partitions.

I did test the version on most common usage cases and found no
regression compared to 3.70+dfsg-3.

Please test it as i intend to ask for freeze exception when it has aged
10 days in unstable.

Regards,
Daniel

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  [EMAIL PROTECTED]
Internet:   http://people.panthera-systems.net/~daniel-baumann/


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Robert Millan]

On Mon, Aug 04, 2008 at 08:46:36PM +0200, Julien Cristau wrote:
> On Mon, Aug  4, 2008 at 20:36:17 +0200, Robert Millan wrote:
> 
> > This is troubling.  Do you have any suggestions on how to address this?
> 
> Stop trolling about utterly uninteresting details?

I think it's you who are trolling.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Julien Cristau]

On Mon, Aug  4, 2008 at 20:36:17 +0200, Robert Millan wrote:

> This is troubling.  Do you have any suggestions on how to address this?

Stop trolling about utterly uninteresting details?

HTH,
Julien


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

Re: Should the X packages pre-depend on awk?

[Johannes Wiedersich]

On 2008-08-02 22:28, Steve Langasek wrote:
> On Sat, Aug 02, 2008 at 04:48:14PM +, Jörg Sommer wrote:
>> Steve Langasek <[EMAIL PROTECTED]> wrote:
>>> On Thu, Jul 31, 2008 at 09:27:10AM +, Jörg Sommer wrote:
[snip]

 So, must these packages pre‐depend on awk?
> 
>>> No, but I think we may have a bug in base-files here that no one's ever
>>> noticed before.
> 
>> Should I send a bug report for base-files?
> 
> I've reassigned the existing bug report.

I've found another one:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469552

I have already reassigned and merged accordingly. ;-)

Johannes



signature.asc
Description: OpenPGP digital signature

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Robert Millan]

On Mon, Aug 04, 2008 at 03:18:24PM +0200, Giacomo A. Catenazzi wrote:
> : Origin: Debian
> : Label: Debian
> : Suite: testing
> : Codename: lenny
> : Date: Mon, 04 Aug 2008 08:39:59 UTC
> : Architectures: alpha amd64 arm armel hppa i386 ia64 mips mipsel 
> powerpc s390 sparc
> : Components: main contrib non-free
> : Description: Debian x.y Testing distribution - Not Released
> 
> So lenny is made from main (Debian), contrib and non-free.

Therefore Lenny is not Debian, but a superset of it?

This is troubling.  Do you have any suggestions on how to address this?

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


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

Re: Shouldn't tar 1.20-1 be in testing?

[Joey Hess]

Theodore Tso wrote:
> I'm guessing that perhaps since tar is probably used by d-i

d-i uses busybox's implementation of tar.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon

[Hendrik Sattler]

Am Montag, 4. August 2008 13:49:09 schrieb Guus Sliepen:
> What is missing here is whether or not mobile-manager comes with a GUI
> component to interact with the daemon.

...and how it can maybe interact with network-manager. There is not so much 
special about a GPRS/whatever device apart from the few AT chatting that 
handles PIN/PUK and the dial commands. The world was using pppd for that.
I vote for all three working together...

HS


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

ITP: cairo-dock-themes -- A collection of themes for cairo-dock

[Nobuhiro Iwamatsu]

Package: wnpp
Owner: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
Severity: wishlist

*** Please type your report below this line ***

* Package name: cairo-dock-themes
  Version : 1.6.1.2
  Upstream Author : Fabrice Rey <[EMAIL PROTECTED]>
* URL : http://www.cairo-dock.org/
* License : GPLv2
  Programming Lang: C
  Description : A collection of themes for cairo-dock

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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]

ITP: cairo-dock-plugins -- A collection of official plug-ins and applets for cairo-dock

[Nobuhiro Iwamatsu]

Package: wnpp
Owner: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
Severity: wishlist

*** Please type your report below this line ***

* Package name: cairo-dock-plugins
  Version : 1.6.1.2
  Upstream Author : Fabrice Rey <[EMAIL PROTECTED]>
* URL : http://www.cairo-dock.org/
* License : GPLv2
  Programming Lang: C
  Description : A collection of official plugins and applets for cairo-dock

 A collection of official plugins and applets for cairo-dock.
 This package supports many software's control plugin.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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]

ITP: cairo-dock -- An light eye-candy fully themable animated dock for any Linux desktop

[Nobuhiro Iwamatsu]

Package: wnpp
Owner: Nobuhiro Iwamatsu <[EMAIL PROTECTED]>
Severity: wishlist

*** Please type your report below this line ***

* Package name: cairo-dock
  Version : 1.6.1.2
  Upstream Author : Fabrice Rey <[EMAIL PROTECTED]>
* URL : http://www.cairo-dock.org/
* License : GPLv2
  Programming Lang: C
  Description : An light eye-candy fully themable animated dock for any 
Linux desktop

 This has a family-likeness with OSX dock, but with more options.
 Uses cairo to render nice graphics, and Glitz to use hardware acceleration.
 It's fully configurable and can be a taskbar too.
 You can easily plug applets into it.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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: Shouldn't tar 1.20-1 be in testing?

[Theodore Tso]

On Mon, Aug 04, 2008 at 03:43:51PM +0200, Julien Cristau wrote:
> On Mon, Aug  4, 2008 at 15:34:40 +0200, Vincent Lefevre wrote:
> 
> > tar 1.20-1 entered unstable on 2008-04-17, so several months before the
> > freeze.
> 
> The essential toolchain was frozen before the rest of the archive.

Yes, but there have been exceptions made; I'm not sure that lzma
support would be good and sufficient reasons to sway the release-team,
but Julien should try sending that note to debian-release, and see
what they say.

I'm guessing that perhaps since tar is probably used by d-i, the tar
maintainer needed to explicitly request that tar get manually pushed
to testing, and that didn't happen back in May/June?

- Ted


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

Re: Bits from the Debian Eee PC team, summer 2008

[Andreas Tille]

On Sun, 3 Aug 2008, Ben Armstrong wrote:


On Sun, 3 Aug 2008 13:53:54 +0200
Robert Millan <[EMAIL PROTECTED]> wrote:

Lenny is Debian.  non-free is not part of Debian.  Check the Social Contract.


In light of the point of that follows this one, is it perhaps not too
far of a stretch to imagine that I understand this, and expected my
readers to understand this?


... and probably there is no point in asking a long time fellow
DD to check Social Contract.  It is better style to make a small
side note that the announcement might be perhaps trigger some
missunderstanding by people not so deeply involved.

Ben, thanks for the nice work - I'll perhaps profit from it
really soon

Andreas.

--
http://fam-tille.de


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

Re: Available papersizes vs. default papersizes

[Johannes Wiedersich]

On 2008-08-03 18:44, Frank Küster wrote:
> I would like to solve a long-standing bug and finally make TeX aware
> of libpaper and its system-wide paper size setting.

Good!

> However, taking the intersection of paper sizes the different
> program's configuration files accept as default, I end up with
> a4paper and letter.

From Wikipedia [1] it appears that ISO-A and the north American system
are the only widespread systems around the world:
"By 1977 A4 was the standard letter format in 88 of 148 countries, and
today only the U.S. and Canada have not adopted the system. "

I guess, that a default respecting A4 and letter is already a nice
improvement. Additionally you might consider including A3, A5 and legal,
though I don't expect there will be much demand for it. Those with these
requirements will rather likely have the skills to adjust it themselves.

> On the upstream list, the discussion which papers would make sense as
> a system-wide default paper did not lead anywhere. Some said that
> only a4paper and letter make sense (my question whether asian or
> african countries use nothing else stayed unanswered).

If no one steps in to promote different, more exotic formats, I guess
these could be left to bug reports. Actually, I don't think there will
be any significant demand for other formats as a default *system* paper
size [2].

> Some argued that every paper which can be fed to a printer on the
> market might be used as default size on a particular system.

If you'd like to use a different default, how difficult is the
implementation for the user/administrator of the box in question?

> Do you have any suggestions?

I forwarded your question to d-u. Maybe some 'users' over there have
some suggestions of what they use/require... [3]

Cheers,
Johannes

[1] http://en.wikipedia.org/wiki/Paper_size

[2] I've done a quick survey on some colleagues from China and Egypt and
they confirm that they've never seen a printer's paper size different
from A4 or letter in their home countries, while letter is rather rare
in Egypt and absent in China.

[3] http://lists.debian.org/debian-user/2008/08/msg00229.html



signature.asc
Description: OpenPGP digital signature

Re: Shouldn't tar 1.20-1 be in testing?

[Julien Cristau]

On Mon, Aug  4, 2008 at 15:34:40 +0200, Vincent Lefevre wrote:

> tar 1.20-1 entered unstable on 2008-04-17, so several months before the
> freeze.

The essential toolchain was frozen before the rest of the archive.

Cheers,
Julien


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

Shouldn't tar 1.20-1 be in testing?

[Vincent Lefevre]

According to

  http://packages.qa.debian.org/t/tar.html

tar 1.20-1 entered unstable on 2008-04-17, so several months before the
freeze. And http://release.debian.org/migration/testing.pl?package=tar
gives no good reasons for which tar is not in testing yet:

  * trying to update tar from 1.19-3 to 1.20-1 (candidate is 109 days old)
  * tar is in freeze; contact debian-release if update is needed 

The first point isn't a reason at all. Concerning the second point,
tar 1.20-1 should have entered testing before the freeze.

If I understand correctly[*], tar 1.20-1 has been installed on every arch
since 2008-05-19.

[*] http://buildd.debian.org/pkg.cgi?pkg=tar

tar 1.20-1 contains an important addition: lzma support. And developers
are starting to use lzma-compressed tarballs instead of bzip2 (see e.g.
texinfo). Though there are workarounds, they have drawbacks, and it would
be quite annoying to have an obsolete version of tar in lenny.

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)


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

Re: confusion about non-free (Re: Bits from the Debian Eee PC team, summer 2008)

[Giacomo A. Catenazzi]

Robert Millan wrote:

[ adding debian-project ]

On Sun, Aug 03, 2008 at 01:53:54PM +0200, Robert Millan wrote:

On Sun, Aug 03, 2008 at 08:28:19AM -0300, Ben Armstrong wrote:

Earliest Eee models fully supported in Lenny

   Lenny will release with the atl2 ethernet driver and the non-free
   madwifi-source now works with the earliest Eee models as well,

Hi Ben

Lenny is Debian.  non-free is not part of Debian.  Check the Social Contract.


I wonder what is it that we do wrong to spread this confusion so much that it
affects even Debian developers themselves.

What is this to blame?  Would it be the FTP archive layout?  Perhaps having an
unified BTS?


There are some problem with terms/words: they are inconsistent, sometime 
also along the same documentation file.

BTW I'm trying to document it: http://wiki.debian.org/PolicyGlossary

Anyway:
From policy: "The main category forms the Debian GNU/Linux
distribution."

But I'm not sure that Lenny is only Debian:
From http://ftp.de.debian.org/debian/dists/lenny/Release
(thus using 'dak' terminology):

: Origin: Debian
: Label: Debian
: Suite: testing
: Codename: lenny
: Date: Mon, 04 Aug 2008 08:39:59 UTC
: Architectures: alpha amd64 arm armel hppa i386 ia64 mips mipsel 
powerpc s390 sparc

: Components: main contrib non-free
: Description: Debian x.y Testing distribution - Not Released

So lenny is made from main (Debian), contrib and non-free.

ciao
cate


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

Re: Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon

[Guus Sliepen]

On Mon, Aug 04, 2008 at 12:12:33PM +0200, Juan Manuel Garcia Molina wrote:

> * Package name: mobile-manager
[...]
>   Description : mobile manager GPRS/3G daemon
> 
>  Mobile Manager is a GPRS/3G daemon developed by Telefonica. 
>  This daemon cover the GPRS/3G functions for develop and work
>  over GPRS/3G

Is this similar to "wader" (see ITP bug #492875)? If so, perhaps you
should make the upstreams work together.

As for the description in your ITP, it doesn't really tell me what it is
doing except that it has something to do with GPRS/3G. On the website,
there is a very clear description, you should use it as a basis for the
description of your package:

 Mobile Manager is a D-Bus service to control and use mobile data devices
 in Linux-based platforms. Mobile Manager provides a unified API to
 govern the following aspects of the GPRS/3G devices attached to the
 system:
 .
 * Plug & Play device support.
 * PIN/PUK management.
 * Device information and status.
 * Connection establishment and traffic monitoring. 

What is missing here is whether or not mobile-manager comes with a GUI 
component to
interact with the daemon.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen <[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Re: Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon

[Yves-Alexis Perez]

On Mon, Aug 04, 2008 at 12:12:33PM +0200, Juan Manuel Garcia Molina wrote:
> * URL : http://mobilemanager.openmovilforum.com

I guess you meant http://mobilemanager.movilforum.com?
-- 
Yves-Alexis


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

Bug#493697: ITP: mobile-manager -- mobile manager GPRS/3G daemon

[Juan Manuel Garcia Molina]

Package: wnpp
Severity: wishlist
Owner: Juan Manuel Garcia Molina <[EMAIL PROTECTED]>

* Package name: mobile-manager
  Version : 0.7
  Upstream Author : Telefonica Moviles Spain, S.A.U. <[EMAIL PROTECTED]>
* URL : http://mobilemanager.openmovilforum.com
* License : LGPL
  Programming Lang: Python
  Description : mobile manager GPRS/3G daemon

 Mobile Manager is a GPRS/3G daemon developed by Telefonica. 
 This daemon cover the GPRS/3G functions for develop and work
 over GPRS/3G

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)



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

Bug#493691: ITP: liboauth-php -- open protocol to allow secure API authentication

[Daniel Watkins]

Package: wnpp
Severity: wishlist
Owner: Daniel Watkins <[EMAIL PROTECTED]>


* Package name: liboauth-php
  Version : 0.0~svn620
  Upstream Author : Andy Smith <[EMAIL PROTECTED]>
* URL : http://oauth.net/
* License : MIT
  Programming Lang: PHP
  Description : open protocol to allow secure API authentication

OAuth is a simple way to publish and interact with protected data.  It allows
the User to grant access to their private resources on one site (the Service
Provider), to another site (the Consumer, not to be confused with the User).
While OpenID is all about using a single identity to sign into many sites, OAuth
is about giving access to your stuff without sharing your identity at all (or
its secret parts).

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)



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

Bug#493690: ITP: libxmpp-php -- PHP library allowing communication with XMPP servers

[Daniel Watkins]

Package: wnpp
Severity: wishlist
Owner: Daniel Watkins <[EMAIL PROTECTED]>


* Package name: libxmpp-php
  Version : 0.1~beta-r50
  Upstream Author : Nathan Fritz
* URL : http://code.google.com/p/xmpphp/
* License : GPL
  Programming Lang: PHP
  Description : PHP library allowing communication with XMPP servers

XMPPHP is the successor to Class.Jabber.PHP. Taking advantage of PHP5, it is an
elegant solution with a direct approach.

Some of the features include:
  * Connect to any XMPP 1.0 server (Google Talk, LJ Talk, jabber.org, etc)
  * Supports TLS encryption
  * Several XML processing approaches and supported styles (process
indefinitely, processUntil an event, processTime for a number of seconds),
waiting on events or map them, etc.
  * Persistent connections (AJAX Web client anyone?)

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)



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

Request to check for /dev/.static/dev in /etc/blkid.tab

[Theodore Ts'o]

Hi all,

Apparently udev 0.125-3 is going to be in Lenny (it's not yet in
Lenny, but apparently the release-team will be giving an exemption to
let it in despite the freeze).  One of the changes in udev 0.125-3 is
that /dev/.static/dev is going to be going away.  (Rightly so, it's a
hack).  However, this interacts poorly with a bug in the blkid library
which will fail to get rid of stale /dev/.static/dev entries in
/etc/blkid.tab.  (See Bug#493216)

The fix is fairly simple, but I'm trying to get a sense of how
many Debian users have this problem and will get bitten when they
upgrade to Lenny.  So, if folks could type the following command into a
terminal window: "grep /dev/.static /etc/blkid.tab", and if you see any
output, could you drop me a quick e-mail with the results of the grep
command?

If you do find any output, I'd appreciate knowing when/how your
system was installed, and if you may have ever explicitly typed a
command such as "blkid /dev/.static/dev/sda1".  I can't see a situation
where a /dev/.static/dev entry would get into the blkid.tab file,
except by explicit user action, but the submitter of bug #493216 claims
he's never done this.

The workaround to this problem is fairly simple: "rm 
/etc/blkid.tab" or "blkid -g" as root will do it; but if it turns out
there are large numbers of users suffering from this problem, I'd like
to so I can petition the release-team for my own freeze window exception
to get in a very simple patch to fix this bug before Lenny ships.

Thanks, regards,

- Ted


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