Re: Linux Future

2013-01-24 Thread Josselin Mouette 
Le mercredi 23 janvier 2013 à 21:03 +0100, Florian Weimer a écrit : 
> Unfortunately, a lot of this doesn't apply to the polkit version in
> experimental, which replaces .plka files with Javascript (which
> sort-of enforces that only system administrators can configure polkit,
> and not other packages).

AIUI the plan is to re-add support for .pkla files, if only for
compatibility, before the move to unstable.

-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-


--
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/1359015571.588.734.camel@pi0307572

Bug#698839: ITP: yubikey-ksm -- A YubiKey KSM written in PHP

2013-01-24 Thread Dain Nilsson 
Package: wnpp
Severity: wishlist
Owner: Dain Nilsson 

* Package name: yubikey-ksm
  Version : 1.9
  Upstream Author : Yubico Open Source Maintainers 
* URL : https://github.com/Yubico/yubikey-ksm
* License : BSD-2-clause
  Programming Lang: PHP
  Description : A YubiKey KSM written in PHP

The YubiKey Key Storage Module (YK-KSM) provides a AES key storage facility
for use with a YubiKey validation server. The YK-KSM is intended to be run on
a locked-down server. This separation allows third parties to keep tight
control of the AES keys for their YubiKeys, but at the same time allow
external validation servers (e.g., Yubico's) to validate OTPs from these
YubiKeys.

The YK-KSM was designed to work with yubikey-val-server-php.


-- 
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/20130124105355.6595.51329.reportbug@ubuntu

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread David Kalnischkies 
On Thu, Jan 24, 2013 at 6:39 AM, martin f krafft  wrote:
> I think we ought to revert this change and turn off
> ButAutomaticUpgrades for the backports archive (and update
> apt_preferences(5)).

You can find much of the same discussion in the bugreport requesting
implementation of this feature in APT: #596097

In short: If you followed the recommendations in previous releases you
were already used to this kind of behavior, so this flag just makes it
way easier to reach the recommend mode of operation.


Real world feedback over the years has convinced me this is a good mode
to have as default for backports, regardless of the drawbacks it has as the
alternative default is worse if not managed carefully.
(but as I said two years ago, not my decision either way)


Best regards

David Kalnischkies


-- 
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/caaz6_fawem6tkwltyr+-0oj5m-h+gaabqvecgg3v3+gkmp+...@mail.gmail.com

Bug#698843: ITP: brogue -- Roguelike game by Brian Walker

2013-01-24 Thread Etienne Millon 
Package: wnpp
Severity: wishlist
Owner: Etienne Millon 

* Package name: brogue
  Version : 1.7
  Upstream Author : Brian Walker 
* URL : https://sites.google.com/site/broguegame/
* License : GPL3+
  Programming Lang: C
  Description : Roguelike game by Brian Walker

Brogue is a direct descendant of Rogue, unlike other popular modern
roguelikes, and it favors simplicity over complexity, while trying to
ensure that the interactions between components will be interesting
and varied. It is possible to control it entirely with the keyboard or
entirely with the mouse.

---

I intend to maintain this package within the Games Team.

The only non-packaged dependency is libtcod which is released under a
BSD license :

http://doryen.eptalys.net/libtcod/

-- 
Etienne Millon


-- 
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/20130124122150.GA13767@klow

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread Simon McVittie 
On 24/01/13 07:48, martin f krafft wrote:
> also sprach Joerg Jaspert  [2013.01.24.2017
> +1300]:
>>> And say that a year later 2.3 comes out and it's the bee's
>>> knees because it fully replaces 1.1 except that the
>>> configuration cannot be automatically migrated, and all the
>>> power users on #debian-devel persuade you to backport it, what
>>> do you do?
>> 
>> Backport it. Thats one of the points backports is for. I would
>> actually ask wth 2.2 wasn't backported before.
> 
> Because 2.0 drops a feature you need and introduces some bugs.
> Also, the configuration needs a lot of manual work to
> migrate.

It sounds as though in this situation, you'd either want foo-1 and
foo-2 to be parallel-installable (in which case they could coexist in
backports), or something technically similar to an Ubuntu PPA,
containing foo 1.x backports?

S


-- 
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/51012fca.8010...@debian.org

Candidates for removal from testing (2013-01-24)

2013-01-24 Thread Niels Thykier 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

We are considering removing the following packages from testing as
they have unfixed RC bugs filed against them. The packages can be
found in the attached dd-list.  The bugs that put them on this list
can be found in the removals file (also attached) just above the
package name.

The packages have been selected based on the following criteria:
 * The package had at least one RC bug without activity for the past
   14 days.
 * If a bug is assigned to multiple packages, both packages will be
   affected.
 * The RC bug affects both unstable and testing.
 * The affected package does not have any reverse dependencies in
   testing.

If the relevant RC bugs in the affected packages are not dealt with
/before/ Thursday the 31th of Jan., the packages will be removed from
testing.  Note that "dealt with" may also include downgrading a
severity-inflated bug or fixing affected versions in the BTS.

Please remember to file unblock bugs for packages fixed via uploads to
unstable (and tpu bugs for requests to fix the package via a tpu
upload).

Should you need a bit more time than given, please do not hesitate to
contact us.  It is also easier for us if we can avoid having to
reintroduce a removed package.

We will check the DELAYED queues before activing the removal hints, so
NMUs in the DELAYED queues will be given a chance to reach unstable.

Thanks,
Niels (on behalf of the Release Team)

The bugs were found using the tools from:
  svn://svn.debian.org/svn/collab-qa/rc-buggy-leaf-packages


http://release.debian.org/wheezy/freeze_policy.html

  --8<8<-- dd-list --8<8<--
Debian Java Maintainers 
   jenkins

Debian QA Group 
   bzr-gtk

James Page 
   jenkins (U)

Pierre Chifflier 
   glpi

Romain Beauxis 
   lastfmproxy

Wouter Verhelst 
   pmw

  --8<8<-- end of dd-list --8<8<--

  --8<8<-- removals --8<8<--
# #697402
remove bzr-gtk/0.103.0+bzr792-3

# #694642
remove glpi/0.83.31-1

# #696816
remove jenkins/1.447.2+dfsg-2

# #694589
remove lastfmproxy/1.3b-2

# #696844
remove pmw/1:4.24-1

  --8<8<-- end of removals --8<8<--
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRAUhvAAoJEAVLu599gGRCdKoP/AouibtJnE4H4MGdGNxU4rJE
G4kJaeqpR/aeKBiti30eXdUwKLfMNGE2dFqbrp0Wgp/YSE+vr22JyqyC43AHoKkD
dLhpqcnFVKfQe97MvsdbVel6Ox5x45wwGFqkO5HwT6M5cLc9RClCm7sA0XyCsinQ
dmq3nR0tJW9pfnTm97bwCRmisJ9DwVxtgjKqr082sfQFsUOkZP7OpM2q0ZDtwC84
X4/P+7rHSOor8Evj8lE75fN4rXu0e4bjq98yRprRuHHyWLSmqpuvFpniBlQFmsI3
kdMv2r5WL6NU3bT6IGDhjcx4gq8FouRbKYyTybhua2J8Ez9bkp4gbR5VMh3nmIrI
e7BI0UEWIeYz2TmyclSp/1DCjQY+Rl9NmTJpklcJuAUgtDHt2pZCnVemz/iEvkjv
mZbVhynfNeZrnlR0KQGQXdshm2K2amF0WoF9as71vU9EqMUI2DXiD8fDTgtQa2+B
YuP1Pk5hEko5A9c9tAjSNfEOjnLaFfbUfW1+5gCplzF7Vd4FcY5JTiAKzOliwPpD
lMrPL5XTgUDfz6d9sW2aGA2Iyk6ruhDk0d98YcpmviQE72aTyHuZ8m97zqhAprdt
eaCD56R3TJfr2DKRh6933Ccq7AtLcUx4asOCZV6myEFKSg4kMd5LEAyVlziNYxxx
Gp5OZE+O4xLtiMtU+MUy
=/0Pa
-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/20130124144708.58796200ff...@thykier.net

Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Filippo Rusconi 
Greetings, Fellow Debianists,

this is not actually a bug report but something that might concern us
all as a matter of Free Software use inside the Debian project:

The Debian logo file at http://www.debian.org/logos/openlogo.svg

fails to load in the much-respected SVG-based graphics editor Inkscape
(which I use daily and which works fine also for svg files not
produced by itself).

The error is this:

$ inkscape openlogo.svg
openlogo.svg:18: namespace warning : xmlns: URI &ns_svg; is not absolute
 xmlns="&ns_svg;" xmlns:xlink="&ns_xlink;" 
xmlns:a="http://ns.adobe.com/AdobeSV
 ^
openlogo.svg:22: namespace warning : xmlns: URI &ns_vars; is not absolute

^
openlogo.svg:25: namespace warning : xmlns: URI &ns_custom; is not absolute

  ^

Note that The Gimp seems to load the file just fine, although also
with an error message:

Execution error for procedure 'gimp-vectors-import-from-file':
Failed to import paths from 'openlogo.svg':
Error on line 17: Entity name 'ns_extend' is not known

Also, Iceweasel seems to load the file fine since it displays
correctly.

While I'm no expert in XML stuff, I see in the following lines at the
top of the file that the problems might relate to some Adobe-specific
namespace rules (or extensions, or whatever):




http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"; [
http://ns.adobe.com/Flows/1.0/";>
http://ns.adobe.com/Extensibility/1.0/";>
http://ns.adobe.com/AdobeIllustrator/10.0/";>
http://ns.adobe.com/Graphs/1.0/";>
http://ns.adobe.com/Variables/1.0/";>
http://ns.adobe.com/ImageReplacement/1.0/";>
http://ns.adobe.com/SaveForWeb/1.0/";>
http://ns.adobe.com/GenericCustomNamespace/1.0/";>
http://ns.adobe.com/XPath/1.0/";>
http://www.w3.org/2000/svg";>
http://www.w3.org/1999/xlink";>
]>

Because opening the file in The Gimp transforms the svg graphics
object into a raster graphics object, the vector benefits of svg are
lost and thus The Gimp cannot be used as a substitute of Inkscape.

We may want to make sure that this file loads fine in Free Software
graphics svg-based programs and maybe convert it to either a more
generic svg file, or at least something free (Inkscape might be a good
candidate for this).

Any thoughts ?
Cheers,
Filippo

-- 
Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
Researcher at CNRS and Debian Developer 
Author of ``massXpert'' at http://www.massxpert.org


signature.asc
Description: Digital signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Paul Tagliamonte 
On Thu, Jan 24, 2013 at 04:35:23PM +0100, Filippo Rusconi wrote:
> Greetings, Fellow Debianists,
> 
> this is not actually a bug report but something that might concern us
> all as a matter of Free Software use inside the Debian project:
> 
> The Debian logo file at http://www.debian.org/logos/openlogo.svg
> 
> fails to load in the much-respected SVG-based graphics editor Inkscape
> (which I use daily and which works fine also for svg files not
> produced by itself).
> 
> The error is this:
> 
> $ inkscape openlogo.svg
> openlogo.svg:18: namespace warning : xmlns: URI &ns_svg; is not absolute
>  xmlns="&ns_svg;" xmlns:xlink="&ns_xlink;" 
> xmlns:a="http://ns.adobe.com/AdobeSV
>  ^
> openlogo.svg:22: namespace warning : xmlns: URI &ns_vars; is not absolute
> 
> ^
> openlogo.svg:25: namespace warning : xmlns: URI &ns_custom; is not absolute
>  xmlns:v="&ns_vars;">   ^
> openlogo.svg:28: namespace warning : xmlns: URI &ns_sfw; is not absolute
> 
>   ^

Erm, it works here -- what version are you using? :\

> 
> Note that The Gimp seems to load the file just fine, although also
> with an error message:
> 
> Execution error for procedure 'gimp-vectors-import-from-file':
> Failed to import paths from 'openlogo.svg':
> Error on line 17: Entity name 'ns_extend' is not known
> 
> Also, Iceweasel seems to load the file fine since it displays
> correctly.
> 
> While I'm no expert in XML stuff, I see in the following lines at the
> top of the file that the problems might relate to some Adobe-specific
> namespace rules (or extensions, or whatever):
> 
> 
> 
> 
>  "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd"; [
> http://ns.adobe.com/Flows/1.0/";>
> http://ns.adobe.com/Extensibility/1.0/";>
> http://ns.adobe.com/AdobeIllustrator/10.0/";>
> http://ns.adobe.com/Graphs/1.0/";>
> http://ns.adobe.com/Variables/1.0/";>
> http://ns.adobe.com/ImageReplacement/1.0/";>
> http://ns.adobe.com/SaveForWeb/1.0/";>
> http://ns.adobe.com/GenericCustomNamespace/1.0/";>
> http://ns.adobe.com/XPath/1.0/";>
> http://www.w3.org/2000/svg";>
> http://www.w3.org/1999/xlink";>
> ]>
> 
> Because opening the file in The Gimp transforms the svg graphics
> object into a raster graphics object, the vector benefits of svg are
> lost and thus The Gimp cannot be used as a substitute of Inkscape.
> 
> We may want to make sure that this file loads fine in Free Software
> graphics svg-based programs and maybe convert it to either a more
> generic svg file, or at least something free (Inkscape might be a good
> candidate for this).
> 
> Any thoughts ?
> Cheers,
> Filippo
> 
> -- 
> Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
> Researcher at CNRS and Debian Developer 
> Author of ``massXpert'' at http://www.massxpert.org

Fondly,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Christoph Anton Mitterer 
On Thu, 2013-01-24 at 16:35 +0100, Filippo Rusconi wrote:
> fails to load in the much-respected SVG-based graphics editor Inkscape
> (which I use daily and which works fine also for svg files not
> produced by itself).
In mine it loads, version 0.48.3.1-1.3.

Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Stefano Zacchiroli 
On Thu, Jan 24, 2013 at 04:35:23PM +0100, Filippo Rusconi wrote:
> We may want to make sure that this file loads fine in Free Software
> graphics svg-based programs and maybe convert it to either a more
> generic svg file, or at least something free (Inkscape might be a good
> candidate for this).

Agreed.

> Any thoughts ?

How about "patches welcome"? :) This is not meant to be tongue-in-cheek,
but a very pragmatic suggestion. I'm no SVG expert either, but AFAICT
all the "source" info are indeed in that .svg file, it is "just" that
due to some minor syntactic issues (I speculate: due to the age of the
.svg in question) it doesn't work properly with current version of
popular FOSS SVG editors.

Let's "just" find SVG experts in our community and ask them to fix the
source code. Posting a call for help about this on -dekstop might
actually be a useful way forward.

Cheers.
-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »


signature.asc
Description: Digital signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Filippo Rusconi 
Hello Chris,

thanks for bothering :-)

On Thu, Jan 24, 2013 at 04:51:43PM +0100, Christoph Anton Mitterer wrote:
> On Thu, 2013-01-24 at 16:35 +0100, Filippo Rusconi wrote:
> > fails to load in the much-respected SVG-based graphics editor Inkscape
> > (which I use daily and which works fine also for svg files not
> > produced by itself).
> In mine it loads, version 0.48.3.1-1.3.

$ inkscape --version
Inkscape 0.48.3.1 r9886 (Dec 29 2012)

$ dpkg -l inkscape
ii  inkscape  0.48.3.1-1.3  amd64

So, I would say this is odd.


$ sha1sum openlogo.svg
f958ec1c5eaf8c8507e6830852292081fca1  openlogo.svg

could you confirm this on a file that you have 

wget http://www.debian.org/logos/openlogo.svg

Thanks, 

Filippo

-- 
Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
Researcher at CNRS and Debian Developer 
Author of ``massXpert'' at http://www.massxpert.org


-- 
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/20130124160824.GE5622@licorne

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Filippo Rusconi 
Hello Stefano,

On Thu, Jan 24, 2013 at 04:53:44PM +0100, Stefano Zacchiroli wrote:
> On Thu, Jan 24, 2013 at 04:35:23PM +0100, Filippo Rusconi wrote:
> > We may want to make sure that this file loads fine in Free Software
> > graphics svg-based programs and maybe convert it to either a more
> > generic svg file, or at least something free (Inkscape might be a good
> > candidate for this).
> 
> Agreed.
> 
> > Any thoughts ?
> 
> How about "patches welcome"? :) This is not meant to be tongue-in-cheek,
> but a very pragmatic suggestion. I'm no SVG expert either, but AFAICT
> all the "source" info are indeed in that .svg file, it is "just" that
> due to some minor syntactic issues (I speculate: due to the age of the
> .svg in question) it doesn't work properly with current version of
> popular FOSS SVG editors.

Investigating a bit, I found that 

http://www.adobe.com/AdobeSVGViewerExtensions/3.0/

gives a 404 in my browser. This url is at line 18 of the file.

Same for 

http://www.adobe.com/Extensibility/1.0/

> Let's "just" find SVG experts in our community and ask them to fix the
> source code. Posting a call for help about this on -dekstop might
> actually be a useful way forward.

We certainly need some experts knowing what they do :-)

By the way, is the author of this file known ? Maybe he/she could help?

Cheers,

Filippo

-- 
Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
Researcher at CNRS and Debian Developer 
Author of ``massXpert'' at http://www.massxpert.org


-- 
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/20130124161346.GF5622@licorne

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Paul Tagliamonte 
On Thu, Jan 24, 2013 at 05:08:24PM +0100, Filippo Rusconi wrote:
> Hello Chris,
> 
> thanks for bothering :-)
> 
> On Thu, Jan 24, 2013 at 04:51:43PM +0100, Christoph Anton Mitterer wrote:
> > On Thu, 2013-01-24 at 16:35 +0100, Filippo Rusconi wrote:
> > > fails to load in the much-respected SVG-based graphics editor Inkscape
> > > (which I use daily and which works fine also for svg files not
> > > produced by itself).
> > In mine it loads, version 0.48.3.1-1.3.
> 
> $ inkscape --version
> Inkscape 0.48.3.1 r9886 (Dec 29 2012)
> 
> $ dpkg -l inkscape
> ii  inkscape  0.48.3.1-1.3  amd64
> 
> So, I would say this is odd.
> 
> 
> $ sha1sum openlogo.svg
> f958ec1c5eaf8c8507e6830852292081fca1  openlogo.svg
> 
> could you confirm this on a file that you have 
> 
> wget http://www.debian.org/logos/openlogo.svg

I'm not Chris, but:

[tag@leliel:~/Downloads][11:19 AM]$ inkscape --version
Inkscape 0.48.3.1 r9886 (Jun 20 2012)

[tag@leliel:~/Downloads][11:19 AM]$ dpkg -l | grep inkscape
ii  inkscape  0.48.3.1-1.1

[tag@leliel:~/Downloads][11:19 AM]$ inkscape openlogo.svg 

[ it works ]

[tag@leliel:~/Downloads][11:19 AM]$ shasum openlogo.svg 
f958ec1c5eaf8c8507e6830852292081fca1  openlogo.svg

(amd64)

> 
> Thanks, 
> 
> Filippo
> 
> -- 
> Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
> Researcher at CNRS and Debian Developer 
> Author of ``massXpert'' at http://www.massxpert.org
> 
> 
> -- 
> 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/20130124160824.GE5622@licorne
> 

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Christoph Anton Mitterer 
On Thu, 2013-01-24 at 17:08 +0100, Filippo Rusconi wrote:
> $ sha1sum openlogo.svg
> f958ec1c5eaf8c8507e6830852292081fca1  openlogo.svg
> 
> could you confirm this on a file that you have 
> 
> wget http://www.debian.org/logos/openlogo.svg


Funny:

inkscape openlogo.svg
=> fails

inkscape http://www.debian.org/logos/openlogo.svg
=> works

^^

Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Matt Zagrabelny 
On Thu, Jan 24, 2013 at 9:51 AM, Christoph Anton Mitterer
 wrote:
> On Thu, 2013-01-24 at 16:35 +0100, Filippo Rusconi wrote:
>> fails to load in the much-respected SVG-based graphics editor Inkscape
>> (which I use daily and which works fine also for svg files not
>> produced by itself).
> In mine it loads, version 0.48.3.1-1.3.

Curious. I am using the same version (0.48.3.1-1.3) and get the
specified failure in the original post.

-mz


-- 
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/caolfk3xaumqe0eiq_0tfy5ryd0tsz6j8h_dgfrcg_oawyvt...@mail.gmail.com

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Jakub Wilk 

* Filippo Rusconi , 2013-01-24, 17:13:

Investigating a bit, I found that

http://www.adobe.com/AdobeSVGViewerExtensions/3.0/

gives a 404 in my browser. This url is at line 18 of the file.

Same for

http://www.adobe.com/Extensibility/1.0/


That's not a problem. Namespace names are only compared for equality, 
they are never dereferenced.



The problem is that the SVG file in question uses both DTD and 
namespaces, which are known not to play well together. (There might an 
libxml2 bug involved here too, I'm not sure.)


Anywhere, here's how to fix the SVG:

1) apt-get install libxml2-utils sgml-data
2) xmllint --noent openlogo.svg > openlogo-fixed.svg
(Yes it's "noent", not to be confused with "nonet".)
3) Optionally, remove the DTD declaration from the resulting file.

--
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/20130124164812.ga5...@jwilk.net

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Jakub Wilk 

* Jakub Wilk , 2013-01-24, 17:48:

here's how to fix the SVG:

1) apt-get install libxml2-utils sgml-data
2) xmllint --noent openlogo.svg > openlogo-fixed.svg
(Yes it's "noent", not to be confused with "nonet".)
3) Optionally, remove the DTD declaration from the resulting file.


The last two steps could be merged into one:

xmllint --dropdtd --noent openlogo.svg > openlogo-fixed.svg

--
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/20130124171737.ga5...@jwilk.net

Re: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Filippo Rusconi 
[ CC: debian-...@lists.debian.org ]

Greetings Jakub,

On Thu, Jan 24, 2013 at 06:17:37PM +0100, Jakub Wilk wrote:
> * Jakub Wilk , 2013-01-24, 17:48:
> >here's how to fix the SVG:
> >
> >1) apt-get install libxml2-utils sgml-data
> >2) xmllint --noent openlogo.svg > openlogo-fixed.svg
> >(Yes it's "noent", not to be confused with "nonet".)
> >3) Optionally, remove the DTD declaration from the resulting file.
> 
> The last two steps could be merged into one:
> 
> xmllint --dropdtd --noent openlogo.svg > openlogo-fixed.svg
> 

That did the trick ! Thanks a lot. In fact I had set out to remove the
DTD manually, but my first attempts failed. I can see that the DTD
specif went away in the fixed file.

For what it's worth, there is still some adobe-specific metadata cruft
that can be removed with no harm apparently:



http://ns.adobe.com/Variables/1.0/";>


http://ns.adobe.com/GenericCustomNamespace/1.0/"; 
xmlns:v="http://ns.adobe.com/Variables/1.0/"/>


http://ns.adobe.com/SaveForWeb/1.0/";>





Attached to this mail is a version saved with inkscape and edited to
remove any reference to adobe. This new file loads fine in Inkscape,
The Gimp, Iceweasel and... GNU Emacs!

Maybe the folks at debian-...@lists.debian.org might want to give it a
test and replace the old file with this one? Anyhow I now have my
Debian logo for my slides!

Thanks all for helping with this issue.

Cheers,
Filippo

-- 
Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
Researcher at CNRS and Debian Developer 
Author of ``massXpert'' at http://www.massxpert.org
<>

Bug#698872: Debian logo svg file is not loadable in Inkscape

2013-01-24 Thread Stefano Zacchiroli 
Package: www.debian.org

[ reporting this as a bug ]

Heya,
  Filippo Rusconi discovered the .svg of the Debian logo is not loadable
in (some versions of) Inkscape. With the help of Jakub Wilk, the .svg
has been fixed and it's attached to this mail. Can you please update the
published version, when you get around it?

See quoted mailed below, and corresponding thread on -devel [1], for
more information.

Thanks for maintaining www.d.o!
Cheers.

[1]: https://lists.debian.org/debian-devel/2013/01/msg00532.html

On Thu, Jan 24, 2013 at 06:44:13PM +0100, Filippo Rusconi wrote:
> Greetings Jakub,
> 
> On Thu, Jan 24, 2013 at 06:17:37PM +0100, Jakub Wilk wrote:
> > * Jakub Wilk , 2013-01-24, 17:48:
> > >here's how to fix the SVG:
> > >
> > >1) apt-get install libxml2-utils sgml-data
> > >2) xmllint --noent openlogo.svg > openlogo-fixed.svg
> > >(Yes it's "noent", not to be confused with "nonet".)
> > >3) Optionally, remove the DTD declaration from the resulting file.
> > 
> > The last two steps could be merged into one:
> > 
> > xmllint --dropdtd --noent openlogo.svg > openlogo-fixed.svg
> > 
> 
> That did the trick ! Thanks a lot. In fact I had set out to remove the
> DTD manually, but my first attempts failed. I can see that the DTD
> specif went away in the fixed file.
> 
> For what it's worth, there is still some adobe-specific metadata cruft
> that can be removed with no harm apparently:
> 
> 
>   
>   http://ns.adobe.com/Variables/1.0/";>
>   
>   
>xmlns="http://ns.adobe.com/GenericCustomNamespace/1.0/"; 
> xmlns:v="http://ns.adobe.com/Variables/1.0/"/>
>   
>   
>   http://ns.adobe.com/SaveForWeb/1.0/";>
>   
>height="144.133" bottomLeftOrigin="true"/>
>   
>   
> 
> Attached to this mail is a version saved with inkscape and edited to
> remove any reference to adobe. This new file loads fine in Inkscape,
> The Gimp, Iceweasel and... GNU Emacs!
> 
> Maybe the folks at debian-...@lists.debian.org might want to give it a
> test and replace the old file with this one? Anyhow I now have my
> Debian logo for my slides!
> 
> Thanks all for helping with this issue.
> 
> Cheers,
> Filippo
> 
> -- 
> Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
> Researcher at CNRS and Debian Developer 
> Author of ``massXpert'' at http://www.massxpert.org

-- 
Stefano Zacchiroli  . . . . . . .  z...@upsilon.cc . . . . o . . . o . o
Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o
Debian Project Leader . . . . . . @zack on identi.ca . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »
<>

signature.asc
Description: Digital signature

Bug#698875: ITP: libio-compress-lzma-perl -- modules for reading and writing lzma/xz files/buffers

2013-01-24 Thread gregor herrmann 
Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org

* Package name: libio-compress-lzma-perl
  Version : 2.055
  Upstream Author : Paul Marquess 
* URL : https://metacpan.org/release/IO-Compress-Lzma/
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : modules for reading and writing lzma/xz files/buffers

This package includes the following modules:

 * IO::Compress::Lzma - Write lzma files/buffers
 * IO::Compress::Xz - Write xz files/buffers
 * IO::Uncompress::UnLzma - Read lzma files/buffers
 * IO::Uncompress::UnXz - Read xz files/buffers


-- 
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/20130124192034.ga2...@jadzia.comodo.priv.at

Re: Candidates for removal from testing (2013-01-24)

2013-01-24 Thread Wouter Verhelst 
On Thu, Jan 24, 2013 at 03:47:08PM +0100, Niels Thykier wrote:
> We are considering removing the following packages from testing as
> they have unfixed RC bugs filed against them.
[...]
> Wouter Verhelst 
>pmw

I had overlooked the fact that "serious" means "release critical",
otherwise I'd have given this some more attention.

What happens here is that some pointer/int confusion causes incorrect
output, in the test suite, which causes the package to fail to build, on
a non-release architecture[1]. Since the test suite is run at compile
time, this means the bug does not manifest itself on the architectures
where the package did build, in casu our release architectures.

For that reason, I believe it makes more sense to downgrade the bug
rather than to kick it out of the release, so I've done that.

Having said that, I've contacted upstream; if a complete fix does
materialize before the release (Thorsten's patch only fixes one instance
of that bug, but the bug report hints there may be more), I'll still
upload that, with the hope it'll get accepted...?

[1] In casu, m68k. Yes, I know. Stop looking at me like that.

-- 
Copyshops should do vouchers. So that next time some bureaucracy requires you
to mail a form in triplicate, you can mail it just once, add a voucher, and
save on postage.


-- 
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/20130124212451.ga7...@grep.be

Bug#698887: ITP: tiarra -- IRC proxy, stationing, logger and bot program (pirc).

2013-01-24 Thread Hideki Yamane 
Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 
X-Debbugs-CC: debian-devel@lists.debian.org, debian-de...@lists.debian.or.jp, 
SAITO Naohiko 

   Package name: tiarra
Version: 2010
Upstream Author: Topia 
URL: http://www.clovery.jp/tiarra/
License: GPL-1+ or Artistic

Description: IRC proxy, stationing, logger and bot program (pirc).
 Tiarra can work as IRC proxy server, stationing on the IRC net with logging. 
 Also some bot plugins are included.


-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane


-- 
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/20130125080051.f8672a9f9d9a51b3628ae...@debian.or.jp

Re: Candidates for removal from testing (2013-01-24)

2013-01-24 Thread Andrew Starr-Bochicchio 
On Thu, Jan 24, 2013 at 9:47 AM, Niels Thykier  wrote:
> Debian QA Group 
>bzr-gtk

>   --8<8<-- removals --8<8<--
> # #697402
> remove bzr-gtk/0.103.0+bzr792-3

As jwilk has already mentioned in the bug report, [1] this should be
assigned elsewhere. Though, it is not exactly clear where.

To briefly summarize, the bug is that having bzr-gtk and python-gtk2
installed at the same time causes "pydoc -k foobarbaz" to crash. This
is because pydoc imports all packages in order to find out what
modules they contain. bzr-gtk imports gi.repository.Gtk. This loads
libgtk-3.so.0 and python-gtk2 obviously loads libgtk-2. Presumably any
other python package using GTK+3 would cause this crash, not just
bzr-gtk.

Any guidance would be appreciated.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697402#15

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


-- 
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/cal6k_axfpexdesgpmf2kgvpmphceynkw66wasax19qmef2r...@mail.gmail.com

Work-needing packages report for Jan 25, 2013

2013-01-24 Thread wnpp 
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 519 (new: 0)
Total number of packages offered up for adoption: 142 (new: 2)
Total number of packages requested help for: 63 (new: 0)

Please refer to http://www.debian.org/devel/wnpp/ for more information.



No new packages have been orphaned, but a total of 519 packages are
orphaned.  See http://www.debian.org/devel/wnpp/orphaned
for a complete list.



The following packages have been given up for adoption:

   qbankmanager (#698883), offered today
 Description: online banking program with graphical interface
 Installations reported by Popcon: 101

   salt (#698772), offered yesterday
 Description: remote manager to administer servers
 Installations reported by Popcon: 90

140 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list.



For the following packages help is requested:

   apt-xapian-index (#567955), requested 1088 days ago
 Description: maintenance tools for a Xapian index of Debian packages
 Installations reported by Popcon: 61421

   asymptote (#517342), requested 1427 days ago
 Description: script-based vector graphics language inspired by
   MetaPost
 Installations reported by Popcon: 4140

   athcool (#278442), requested 3012 days ago
 Description: Enable powersaving mode for Athlon/Duron processors
 Installations reported by Popcon: 65

   balsa (#642906), requested 487 days ago
 Description: An e-mail client for GNOME
 Installations reported by Popcon: 782

   bastille (#592137), requested 901 days ago
 Description: Security hardening tool
 Installations reported by Popcon: 178

   cardstories (#624100), requested 640 days ago
 Description: Find out a card using a sentence made up by another
   player
 Installations reported by Popcon: 8

   chromium-browser (#583826), requested 970 days ago
 Description: Chromium browser
 Installations reported by Popcon: 11907

   cloud-init (#693094), requested 73 days ago
 Description: configuration and customization of cloud instances
 Installations reported by Popcon: 7

   debtags (#567954), requested 1088 days ago
 Description: Enables support for package tags
 Installations reported by Popcon: 2443

   doc-central (#698273), requested 8 days ago
 Description: web-based documentation browser
 Installations reported by Popcon: 204

   fbcat (#565156), requested 1107 days ago
 Description: framebuffer grabber
 Installations reported by Popcon: 151

   flightgear (#487388), requested 1678 days ago
 Description: Flight Gear Flight Simulator
 Installations reported by Popcon: 809

   freeipmi (#628062), requested 609 days ago
 Description: GNU implementation of the IPMI protocol
 Installations reported by Popcon: 2141

   gnat-4.4 (#539633), requested 1745 days ago
 Description: backport bug fixes from trunk (GCC 4.5)
 Installations reported by Popcon: 2092

   gnat-gps (#496905), requested 1610 days ago
 Description: co-maintainer needed
 Installations reported by Popcon: 451

   gnokii (#677750), requested 222 days ago
 Description: Datasuite for mobile phone management
 Installations reported by Popcon: 2211

   gnupg (#660685), requested 339 days ago
 Description: GNU privacy guard - a free PGP replacement
 Installations reported by Popcon: 132162

   golang (#668870), requested 284 days ago
 Description: Go programming language compiler - metapackage
 Installations reported by Popcon: 459

   gpa (#663405), requested 320 days ago
 Description: GNU Privacy Assistant (GPA)
 Installations reported by Popcon: 512

   gradle (#683666), requested 175 days ago
 Description: Groovy based build system
 Installations reported by Popcon: 26

   grub2 (#248397), requested 3181 days ago
 Description: GRand Unified Bootloader
 Installations reported by Popcon: 123476

   hfsprogs (#557892), requested 1156 days ago
 Description: mkfs and fsck for HFS and HFS+ file systems
 Installations reported by Popcon: 1315

   horde4 (#686007), requested 150 days ago
 Description: web-based groupware and other applications

   hotkey-setup (#483107), requested 1703 days ago
 Description: auto-configures laptop hotkeys
 Installations reported by Popcon: 2965

   irssi-scripts (#663577), requested 318 days ago
 Description: collection of scripts for irssi
 Installations reported by Popcon: 1192

   isdnutils (#661110), requested 335 days ago
 Description: ISDN utilities
 Installatio

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread martin f krafft 
also sprach David Kalnischkies  [2013.01.25.0020 +1300]:
> You can find much of the same discussion in the bugreport requesting
> implementation of this feature in APT: #596097

Thanks for the pointer! I missed this discussion un^Wfortunately.
Anyway, it seems that most people are in favour of this change, and
your message pretty much sums up the reasons.

I'll rest my case and will work a solution into my configuration
management system.

-- 
 .''`.   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
 
"it is the mark of an educated mind
 to be able to entertain a thought
 without accepting it."
-- aristoteles


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

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread Alexander Wirt 
martin f krafft schrieb am Thursday, den 24. January 2013:

> Hey folks,
> 
> For a while now, the backports archive sets "ButAutomaticUpdates:
> yes" in its Release file, causing packages in the archive to be
> pinned with priority 100, rather than 1 (which was previously the
> case).
> 
> The effect of this is that once a backport package is installed and
> a new version appears in the backport archive, APT will treat it as
> an upgrade candidate. Cf. apt_preferences(5):
> 
>   100 <= P < 500
>   causes a version to be installed unless there is a version
>   available belonging to some other distribution or the
>   installed version is more recent
> 
> While this might seem like a good idea at first — like when
> a security fix reaches the backports archive — I think this actually
> counters our stable policy, and backports are destined for stable
> systems after all.
This mail would have been a target for the backports users mailinglist.

However backports is not stable and it was never intended to be stable.

> Our stable policy says that we don't upgrade packages with the
> exception of pure security fixes or other fixes that are guaranteed
> not to remove functionality or introduce big changes (and bugs).
> 
> Backports, however, may very well track a package in testing,
> especially if the backporter has a vested interest in keeping up to
> date with a package's releases even on a stable system, and
> introduce major changes. Therefore, backports hold no guarantee that
> they do not remove functionality or introduce gross new bugs.
> 
> In the past, you could always install a backport if you knew what
> you wanted (apt-get install -t etch-backports …), but if you
> actually wanted to get upgrades, you had to add a package pin
> ("release a=etch-backports"; priority:600). That is, the more you
> wanted to deviate, the more explicit steps you'd have to take.
And several users failed to upgrade the backports which is imho more harm.

> This behaviour has now been inverted: you can install a backport,
> but if you do *not* want to receive upgrades automatically, you have
> to install a pin. Put differently: to prevent automatic further
> deviation from stable, you have to take additional steps.
Now are some years... 

> I am sure we all agree that the
> deny-all-but-what-is-explicitly-allowed policy is the better one. So
> why did we make the switch?
Nope, I don't agree.

> Of course, once you install backports, you no longer have a stable
> system, and hence our stable packages guarantee no longer holds.
> However, many will agree that backports can augment a stable system
> in useful and sometimes even necessary ways. A later version might
> provide a required functionality, or a bug might only be fixed in
> testing, forcing the admin to install a backport without really
> wanting to give up the quality of the stable system.
> 
> The problem in the past was that security fixes to the package in
> stable may well never reach users with backports installed. This
> problem is actually not addressed, as security fixes might not
> appear in testing anytime soon, nor is it guaranteed that the
> backport will be upgraded.
It helps to read the policy, a security upgrade does not need to reach
testing.

> However, unless the admin takes additional steps (= does not forget
> to take additional steps), `apt-get upgrade` (no dist-upgrade
> necessary) might suddenly introduce major changes.
> 
> I think we ought to revert this change and turn off
> ButAutomaticUpgrades for the backports archive (and update
> apt_preferences(5)).
I don't think so. 

> 
> In the long run, maybe we need a stable-backports-security
> repository, which can be used to ensure that backport users don't
> miss out on security fixes without having to accept major changes.
> Ping me when the security team has 30 active members working 5 days
> a week on Debian and I'll look into writing the dak patches. ;)
If you want to maintain such a repo, go ahead. I don't think we have the
manpower to maintain another security branch.

Alex


--
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/20130125064922.ga3...@hawking.credativ.lan

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread Alexander Wirt 
martin f krafft schrieb am Thursday, den 24. January 2013:

> also sprach Joerg Jaspert  [2013.01.24.2017 +1300]:
> > > And say that a year later 2.3 comes out and it's the bee's knees
> > > because it fully replaces 1.1 except that the configuration cannot
> > > be automatically migrated, and all the power users on #debian-devel
> > > persuade you to backport it, what do you do?
> > 
> > Backport it. Thats one of the points backports is for. I would actually
> > ask wth 2.2 wasn't backported before.
> 
> Because 2.0 drops a feature you need and introduces some bugs. Also,
> the configuration needs a lot of manual work to migrate.
> 
> > > And yet, setting "ButAutomaticUpdates: yes" pretends that it's the
> > > other way around.
> > 
> > If you decide to install a backport - you do that. You decide to get
> > that most recent version. Which includes keeping it most recent.
> 
> Except ever since backports became more and more popular, causing
> NotAutomatic to be set at some point in time due to popular demand,
> it's been such that you decided to get the backport and if you
> wanted to keep it recent, you had to do an additional step.
> 
> Now you have to do the additional step to prevent that. Someone
> just changed it for no good reason. Both ways have pros and cons.
> Setting ButAutomaticUpdates certainly doesn't have enough pros to
> warrant this change, just like that. The way it was before does have
> a huge pro though: it's the way it's been for years. You know, never
> change a winning team…
the feature was introduced 08/2006 [1], which means is as old as backports 
without
the flag.

Alex

[1] http://thread.gmane.org/gmane.linux.debian.backports.general/2895/focus=2907


-- 
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/20130125070143.gb3...@hawking.credativ.lan

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread martin f krafft 
also sprach Alexander Wirt  [2013.01.25.2001 +1300]:
> > Setting ButAutomaticUpdates certainly doesn't have enough pros to
> > warrant this change, just like that. The way it was before does have
> > a huge pro though: it's the way it's been for years. You know, never
> > change a winning team…
> the feature was introduced 08/2006 [1], which means is as old as
> backports without the flag.

NotAutomatic was, but I was talking about ButAutomaticUpdates, which
was introduced more than four years later.

-- 
 .''`.   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
 
i'd give my right arm to be ambidextrous.


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

Re: Backports upgrade policy (ButAutomaticUpdates:yes)

2013-01-24 Thread Alexander Wirt 
martin f krafft schrieb am Friday, den 25. January 2013:

> also sprach Alexander Wirt  [2013.01.25.2001 +1300]:
> > > Setting ButAutomaticUpdates certainly doesn't have enough pros to
> > > warrant this change, just like that. The way it was before does have
> > > a huge pro though: it's the way it's been for years. You know, never
> > > change a winning team…
> > the feature was introduced 08/2006 [1], which means is as old as
> > backports without the flag.
> 
> NotAutomatic was, but I was talking about ButAutomaticUpdates, which
> was introduced more than four years later.
reminder to me: don't write mails before 09:00

Alex


--
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/20130125071124.gc3...@hawking.credativ.lan

Re: Candidates for removal from testing (2013-01-24)

2013-01-24 Thread Christian PERRIER 
Quoting Niels Thykier (ni...@thykier.net):

> Pierre Chifflier 
>glpi

I looked briefly at the RC bug for glpi (#694642). It seems that an
embedded Flash file provided with the package has a security issue.

I have no clue at all if this .swf file is of critical use for GLPI
(from the directory tree, it seems to be provided in a "resource"
directory, so maybe not of big importance).

Still, it would be sad to have GLPI disappear from Debian for this, as
this is one of the good free implementations of computer asset
management systems and quite widely popular in France.

Pierre, have you noticed that? I dont see any contribution of yours in
#694642, so you may have missed this release critical bug




signature.asc
Description: Digital signature