Re: Maintainers, porters, and burden of porting

2011-09-11 Thread Andreas Barth 
* Kurt Roeckx (k...@roeckx.be) [110910 15:38]:
> We changed this some time ago and made $arch readable by anybody,
> the mbox's are at:
> buildd.debian.org:/org/buildd.debian.org/mbox/
> 
> We've ask the security team to use wb-t...@buildd.debian.org
> instead, which is not public available.

Ok with me as well. We should have however documented that somewhere.  ;)



Andi


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110911084644.gd4...@mails.so.argh.org

Bug#641183: ITP: qfsodbusxml2cpp -- qdbusxml2cpp utility modified by fso

2011-09-11 Thread Rico Rommel 
Package: wnpp
Severity: wishlist
Owner: Rico Rommel 

* Package name: qfsodbusxml2cpp
  Version : 0.7.0
  Upstream Author :
   2011 Simon Busch 
   2011 Radek Polak 
   2008-2009 Nokia Corporation and/or its subsidiary(-ies).
   1994-2008 Trolltech ASA.

* URL : http://www.freesmartphone.org/
* License : LGPL
  Programming Lang: C++
  Description :
  qfsodbusxml2cpp is a utility to create qt4-bindings from fso-specs. It is a
modified version of the qdbusxml2cpp utility from the qt4-sdk.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110911092344.14748.69974.reportbug@pinguin.deutsches-haus

Wine status

2011-09-11 Thread Cesare Leonardi 

Hi all.

I'd like to know if someone has more info on the Wine package status.
From the outside and after searching from time to time on the internet, 
it's still not clear to me what's the reason why this package is so old.


Upstream is 1.2.3 (stable) and 1.3.28 (development) and they looks like 
quite active releasing new versions.


In Debian we have two Wine packages:
-  wine 1.0.1 (1.1.24 in experimental)
-  wine-unstable 1.1.35

Looking from sourceforge:
-  1.0.1 was released on 2008-10-17
-  1.1.35 was released on 2009-12-18

In the past, the more detailed informations i've found regarding the 
Wine delay were this:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557783
But now it's seem superceded.

During the past years i've used opensuse Factory packages, converted to 
deb using alien, and that worked quite well. They are regularly updated:

http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Factory/i586/

In the recent past upstream site started to advertise this as Wine 
Debian package:

http://dev.carbon-project.org/debian/wine-unstable/
These are deb package that upgrades wine-unstable and that you have to 
install with dpkg. In these days i've tested them and seem to work well.

The person that make them is Kai Wasserbäch, a Debian developer.

I'm really confused.
Why doesn't Kay packages can't be the official Debian packages?
What's the problem behind Wine: technical, time, license?

It will be really appreciated if someone can share more info about that.

Cesare.


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e6c9f2b.7040...@gmail.com

Re: Wine status

2011-09-11 Thread Paul Wise 
On Sun, Sep 11, 2011 at 1:44 PM, Cesare Leonardi wrote:

> I'd like to know if someone has more info on the Wine package status.
> From the outside and after searching from time to time on the internet, it's
> still not clear to me what's the reason why this package is so old.

It is probably a better idea to contact the maintainers and Kai
Wasserbäch himself than debian-devel.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HcfZvtVS=_3Bn7HbNzt1rFVD+pBJhc-=8p+gezqoy...@mail.gmail.com

Re: Wine status

2011-09-11 Thread Ove Kåven 
Den 11. sep. 2011 13:44, skrev Cesare Leonardi:
> Upstream is 1.2.3 (stable) and 1.3.28 (development) and they looks like
> quite active releasing new versions.

Of course.

> In Debian we have two Wine packages:
> -  wine 1.0.1 (1.1.24 in experimental)
> -  wine-unstable 1.1.35

It's slightly newer now, but not new enough yet.

> Looking from sourceforge:
> -  1.0.1 was released on 2008-10-17
> -  1.1.35 was released on 2009-12-18
> 
> In the past, the more detailed informations i've found regarding the
> Wine delay were this:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557783
> But now it's seem superceded.

Because of the work and time needed for compliance with Debian's strict
DFSG requirements (in addition to having to package a full mingw
toolchain to compile it, upstream's Gecko package had to undergo a
repackaging for DFSG compliance, plus a complete license audit; no small
task, many thanks to Stephen Kitt for doing that), this issue was only
resolved like a month ago. Not in time for me to have enough summer
hacking time left to do a lot of updates.

> I'm really confused.
> Why doesn't Kay packages can't be the official Debian packages?

I suspect he always meant it to be temporary - letting users have
*something*, even if the packages may not be perfect and may not even
have been allowed into Debian at the time. He hasn't offered to be a
comaintainer.

> What's the problem behind Wine: technical, time, license?

With the license issues recently resolved, it's mostly time now. The
packaging still needs some revisions in order to become
multiarch-compatible. I have plans to make the wine packages use the
alternatives system more extensively, both for handling Wine's 64-bit
support and for making wine and wine-unstable coinstallable. All this
takes time, which I haven't had much of the last couple of weeks. I hope
to have more time in October (and I really hope to have it before next
Debian release, at least...)

For the time being, you may have to stick with Kai's stuff, I suppose.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e6cb018.5000...@arcticnet.no

Re: Wine status

2011-09-11 Thread Cesare Leonardi 

On 11/09/2011 14:56, Ove Kåven wrote:

Because of the work and time needed for compliance with Debian's strict
DFSG requirements (in addition to having to package a full mingw
toolchain to compile it, upstream's Gecko package had to undergo a
repackaging for DFSG compliance, plus a complete license audit; no small
task, many thanks to Stephen Kitt for doing that), this issue was only
resolved like a month ago.

[...]

Many thanks Ove for all these detailed updates.
Really, really, really appreciated.

Keep up the good work.

Cesare.


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e6cb619.1000...@gmail.com

making encrypted $HOME as easy and convenient as possible

2011-09-11 Thread Jon Dowland 
I like encrypted $HOME and making the use of them as easy for people
as possible.

On creation of the first user, Ubuntu's installer offers a checkbox
labelled something like "Encrypt the user's files".  That's it: just
one check-box. If set, upon login, a PAM module unlocks and mounts a
loopback device over the user's $HOME location, transparently.

On Debian I have achieved this for some time using dm-crypt/LUKS + the
excellent support for the two (and LVM) in d-i.  I then supplant that
with libpam-mount.  The result works,  but has drawbacks:  manual
configuration of libpam-mount;  unpredictable fscks with no visual
feedback; some bugs with concurrent logins; unreliable
unmount-on-logout; etc.

One difference between these two schemes is that Ubuntu's scheme is
orthogonal to whether /home or /home/foo is a distinct partition from
/.  This, IMHO, is a good thing:  novice users need not enter the
(sometimes confusing) world of partitioning: legacy DOS partition
table limitations; or schemes like LVM.  Sometimes I don't care to
have $HOME separate from / myself (except to achieve encryption).

I think it would be wonderful to have such ease-of-use $HOME
encryption in Debian.  Ubuntu's scheme uses ecryptfs.  Before I begin
looking into how best I might help work towards this, I was wondering
if experienced people could weigh in with advice on whether ecryptfs
is likely to be the most sensible way to achieve the desired result,
or is something else worthy of consideration?


Thanks,

-- 
Jon Dowland


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110911132337.GA5608@pris

Re: Wine status

2011-09-11 Thread Kai Wasserbäch 
Dear Cesare, dear Ove,
Ove Kåven schrieb am 11.09.2011 14:56:
> Den 11. sep. 2011 13:44, skrev Cesare Leonardi:
>> In the recent past upstream site started to advertise this as Wine Debian 
>> package: http://dev.carbon-project.org/debian/wine-unstable/

I had nothing to do with that, I actually wasn't even informed in advance and
just started to notice a lot more traffic on my site from one day to the other.

>> These are deb package that upgrades wine-unstable and that you have to
>> install with dpkg. In these days i've tested them and seem to work well.
>> The person that make them is Kai Wasserbäch, a Debian developer.

I know, that many, including some DDs, want me to provide a APT archive, but I'm
not really happy with that, as it might encourage people to use third party
packages without a second thought (like: Can I trust the provider?)

>> I'm really confused. Why doesn't Kay packages can't be the official Debian 
>> packages?
> 
> I suspect he always meant it to be temporary - letting users have 
> *something*, even if the packages may not be perfect and may not even have 
> been allowed into Debian at the time.

This. (It actually served as a place where I could make the builds, I used for
filing bugs, available to upstream; then it was named by winehq.org as the
primary source for Debian.) You might even read that on my page (e.g. [0] or
[1]) too. Though, of course, my blog is not mandatory reading. ;)

> He hasn't offered to be a comaintainer.

TBH I never intended to maintain Wine, though I'm doing this now, to some
extent, anyway. ;) I used Wine and, when I reported upstream bugs to upstream,
was asked to try the latest Git or release with some patches applied. Thus I
needed to build them and also make the builds available to the upstream devs.
(@Ove: I've already a multiarch-ready branch on my system which uses a
significantly simplified debian/rules. If you are interested in that, let me
know and I put it up somewhere.)

Kind regards,
Kai Wasserbäch


[0]

[1] 



-- 

E-Mail: cu...@debian.org
IRC: Curan
Jabber: dri...@debianforum.de
URL: http://wiki.debian.org/C%C3%B9ran
GnuPG: 0xE1DE59D2  0600 96CE F3C8 E733 E5B6 1587 A309 D76C E1DE 59D2



signature.asc
Description: OpenPGP digital signature

Bug#641205: ITP: sdp-s -- Semidefinite relaxations solver

2011-09-11 Thread TUDURI Benoît 
Package: wnpp
Severity: wishlist
Owner: "TUDURI Benoît" 


* Package name: sdp-s
  Version : 1.1
  Upstream Author : Frederic Roupin 
* URL : http://deptinfo.cnam.fr/~roupinf/SDPS/
* License : GPL
  Programming Lang: C, C++
  Description : Semidefinite relaxations solver

 SDP_S is a stand-alone program which formulates mechanically and solves
 semidefinite relaxations for any 0-1 quadratic problem.



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110911142754.6232.57124.reportbug@debian.localdomain

Bug#641207: ITP: ordereddict -- drop-in substitute for collections found in Python 2.7

2011-09-11 Thread FladischerMichael 
Package: wnpp
Severity: wishlist
Owner: fladischermich...@fladi.at

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: ordereddict
  Version : 1.1
  Upstream Author : Raymond Hettinger 
* URL : http://pypi.python.org/pypi/ordereddict/
* License : MIT
  Programming Lang: Python
  Description : drop-in substitute for collections found in Python 2.7

Drop-in substitute for Py2.7's new collections.OrderedDict. It has big-oh 
performance that matches regular dictionaries (amortized O(1) 
insertion/deletion/lookup and O(n) iteration/repr/copy/equality_testing).
..
Ordered dictionaries are just like regular dictionaries but they remember the 
order that items were inserted. When iterating over an ordered dictionary, the 
items are returned in the order their keys were first added.


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5s1D8ACgkQeJ3z1zFMUGYF2wCfRM2oq8PUYuZKL6/ZrCx+Buws
KWoAnjIW2Nz79cSx/VbSzfs9y2eQOWzK
=ut+J
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110911153118.10374.83150.report...@server.home.fladi.at

Re: Bug#641207: ITP: ordereddict -- drop-in substitute for collections found in Python 2.7

2011-09-11 Thread James Vega 
On Sun, Sep 11, 2011 at 05:31:18PM +0200, fladischermich...@fladi.at wrote:
> * Package name: ordereddict
>   Version : 1.1
>   Upstream Author : Raymond Hettinger 
> * URL : http://pypi.python.org/pypi/ordereddict/
> * License : MIT
>   Programming Lang: Python
>   Description : drop-in substitute for collections found in Python 2.7

There was already an ITP for this (#637849) and it was cancelled due to
the planned removal of Python 2.6.

-- 
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega 


signature.asc
Description: Digital signature

Re: Wine status

2011-09-11 Thread Ove Kåven 
Den 11. sep. 2011 16:00, skrev Kai Wasserbäch:
> (@Ove: I've already a multiarch-ready branch on my system which uses a
> significantly simplified debian/rules. If you are interested in that, let me
> know and I put it up somewhere.)

Not really. I always try to keep the packages possible to build without
changes on older systems (easy backports), which means I'm probably not
going to simplify the rules much, especially if such simplified rules
rely on new features like multiarch. Besides, the current rules can
already handle multiarch, there are just a few other things to work on
before I'll dare turning multiarch on. (And given that, last I heard,
the dpkg in testing/unstable still don't handle multiarch, well...)

Still, anyway, thanks for your efforts.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e6cdf4c.4060...@arcticnet.no

Re: Bug#641207: ITP: ordereddict -- drop-in substitute for collections found in Python 2.7

2011-09-11 Thread Jakub Wilk 

* James Vega , 2011-09-11, 12:10:

* Package name: ordereddict
  Version : 1.1
  Upstream Author : Raymond Hettinger 
* URL : http://pypi.python.org/pypi/ordereddict/
* License : MIT
  Programming Lang: Python
  Description : drop-in substitute for collections found in Python 2.7


There was already an ITP for this (#637849) and it was cancelled due to 
the planned removal of Python 2.6.


To be honest, I don't expect Python 2.6 to go away any time soon. (For 
the simple reason that apparently nobody works on making 2.7 the 
default...)


--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110911172419.ga2...@jwilk.net

Processed: Re: Bug#641221: Debian Squeeze problem with firewire_core (DV camera over FireWire)

2011-09-11 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 641221 general
Bug #641221 [firewire_core] Debian Squeeze problem with firewire_core (DV 
camera over FireWire)
Warning: Unknown package 'firewire_core'
Bug reassigned from package 'firewire_core' to 'general'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
641221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131576939224698.transcr...@bugs.debian.org

Re: making encrypted $HOME as easy and convenient as possible

2011-09-11 Thread intrigeri 
Hi,

Jon Dowland wrote (11 Sep 2011 13:23:37 GMT) :
> I like encrypted $HOME and making the use of them as easy for people
> as possible.

So do I.

However, before we go deep into implementation details, I need to ask
what kind of usecase(s) and threat model(s) you have in mind and are
trying to solve.

When discussing such matters, one needs to be aware of the drawbacks
of encrypting $HOME only; one of these drawbacks can be summed up as:

  any data stored in your encrypted $HOME has non neglictible chances
  to be written in cleartext on the disk at some point, and stay
  there, recoverable by standard forensics tools, during a more or
  less long time.

E.g. data may be written in cleartext swap, in hibernation images,
temporary data may be written at various places on disk that are not
in $HOME: cups spool, /var/tmp, etc.

The d-i already supports easy *full* system encryption, swap included.
In some threat models, this offers a much greater protection than
encrypting $HOME only. I think the specific usecases and threat models
that make $HOME -only encryption more fit and desirable should be
clearly defined before we look for a solution. What do you think?

Bye,
-- 
  intrigeri 
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
  | Do not be trapped by the need to achieve anything.
  | This way, you achieve everything.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/85wrdeq026@boum.org

Bug#641221: Debian Squeeze problem with firewire_core (DV camera over FireWire)

2011-09-11 Thread Ben Hutchings 
On Sun, 2011-09-11 at 21:12 +0200, matpro_fhkoeln wrote:
> Package: firewire_core
> 
> Hello Ladies and Gentlemen,
> 
> It seems, that one can't help anymore:
> http://www.linux-archive.org/debian-user/573831-debian-squeeze-problem-firewire_core-dv-camera-over-firewire.html
> 
> Is this the right address?
> Any ideas concerning this problem?

This may be a bug in the firewire_ohci driver.

Please send the output of 'lspci -vnn', the output of
'cat /proc/version', and a summary of the information you sent to the
debian-user list.

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein


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

Processed: reassign 641221 to linux-2.6, tagging 641221

2011-09-11 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 641221 linux-2.6
Bug #641221 [general] Debian Squeeze problem with firewire_core (DV camera over 
FireWire)
Bug reassigned from package 'general' to 'linux-2.6'.
> tags 641221 + moreinfo
Bug #641221 [linux-2.6] Debian Squeeze problem with firewire_core (DV camera 
over FireWire)
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
641221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.131577713130098.transcr...@bugs.debian.org

Re: making encrypted $HOME as easy and convenient as possible

2011-09-11 Thread martin f krafft 
also sprach intrigeri  [2011.09.11.2246 +0200]:
> The d-i already supports easy *full* system encryption, swap
> included.

I think this is what people should be using, not a high-level hack
like ecryptfs.

However, I suppose you can only set this up during installation, and
converting a system later is not trivially possible. Or is it?

-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
"the strength of women comes from the fact
 that psychology cannot explain us.
 men can be analyzed, women merely adored."
-- oscar wilde


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Mīļais, pagaršo sarkanos ikrus jau tagad

2011-09-11 Thread Klavins Valdis 
Kad Tu pirms tam ēdi melnos ikrus? 

Protams - sen.. tāpēc, ka diezgan dārgi sanāk, pareizi? 

Bet biezuči tos gardu muti ēd katru mīļu dienu - jo tas tak ir lieliski un 
gardi..

He, Tu neesi tik turīgs? 

Nepārdzīvo, skaties, kā biezuci tādu var kļūt: 

http://www.klapki.net/images/biezucis.php  

Kerane Manefa 

 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110912000732.ga22...@mail13a.oemgrp.com