Re: Unaddressed use cases for machine-readable debian/copyright files
On Saturday, 25 March 2017 16:25:38 CEST Guillem Jover wrote: > Personally I have no issue with coalescing > copyright notices, as long as they are all for the same license, etc. > I even coalesce copyright years for the same owner. Coalescing copyright notices and years is also done when running "cme update dpkg-copyright" See [1] for more details. HTH [1] https://github.com/dod38fr/config-model/wiki/Managing-Debian-packages-with-cme#update-a-package -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Re: A media type for the machine-readable copyright format ?
On Thursday 30 August 2012 01:25:28 Charles Plessy wrote: I am therefore considering to submit to the IANA a new media type, for instance text/vnd.debian.copyright, for the machine-readable copyright files following the format at http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/. What do you think ? Linux foundation is working on a standard named SPDX [1] which provides similar information (and a lot others). May be you should check with them before pushing dep-5 to an official organisation. Hope this helps [1] http://spdx.org/ -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201209031723.11263@debian.org
Re: [DEP5] Format of Copyright header
On Thursday 15 December 2011 18:58:25 Russ Allbery wrote: That isn't the extra space that Steve is referring to. The space that indicates a continuation is taken for granted; Steve's point is that the examples in DEP 5 space the continuation lines over by several more spaces, which in a free-form field indicates unwrappable text (just as in the Description field for a package). Hmm.. You're right. Must have popped a neuron there. sorry about the noise. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112160905.54385@debian.org
Re: [DEP5] Format of Copyright header
On Wednesday 14 December 2011 08:31:17 Steve Langasek wrote: On the other hand, while a formatted text field type may be reflowed for display, is there any software doing that today wrt DEP5? config-edit doe not. Maybe it's enough to rely on the absence of such formatting in DEP5 parsers for the time being; if and when something starts to care about formatting the Copyright field, we can always scan the archive to detect files that look like they'll wind up formatted poorly. And of course, anyone who cares about formatting to this degree can always add that extra space at the front of the line. I notice, in fact, that all our examples of multi-line Copyright: fields in the draft already do this. Current parser relies on this extra space to distinguigh between a copyright continuation and extra fields. For instance, a parser will fail if a copyright field is written this way: Copyright: 2008: John Smith 2009: Angela Watts because a parser cannot decide if 2009: is a copyright continuation or an extra field. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201112151007.26240@debian.org
Re: Bug#633797: copyright-format: with keywords exception underspecified
On Wednesday 16 November 2011 03:08:25 Steve Langasek wrote: I have no objection to this for 1.0, provided we at the same time clarify that if more than one exception is in use, you need to use a custom shortname instead of an ORed or ANDed list of licenses. Is there a consensus for this position? Makes sense to me. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20171046.26613@debian.org
Re: Using corporate accounts when posting to Debian mailing lists
Le mercredi 11 mai 2011 23:10:49, Florian Weimer a écrit : I wonder if this is the result of corporate pressure, or if this is somehow encouraged by the de-facto list policy. Corporate policy. I'm asked not to use corporate e-mail address for open- source stuff. I do not kwow why there's such a policy... Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105181142.42065.domi.dum...@free.fr
Re: About logo copyright in http://www.jveloso.cl/?
[ I fixed OP's grammar issues to make this thread more clear] On Saturday 12 March 2011 21:38:52 Kanibal v wrote: I just saw this site http://www.jveloso.cl/ that is using Debian logo here in Chile, I would like to ask you if this enterprise is [allowed] to use the logo or if the logo copyrigth [allows] this. Logo license is specified there: http://www.debian.org/logos/ IANAL, but I don't think http://www.jveloso.cl/ usage of Debian logo is allowed by the license as it does not refer to Debian project. So, if you need any help locally please let me know. Let's assume this is an oversight from the aforementioned web site. I guess that a polite e-mail in Spanish mentioning Debian logo's license should be a good first step. That said, I am not a Debian developer, so Debian old timers may have a different opinion. Hope this helps Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103141153.38321.dominique.dum...@hp.com
Re: New version of DEP-5 parser
Le dimanche 23 janvier 2011 15:26:46, Jonas Smedegaard a écrit : For instance, this DEP-5 file is valid, since Maintainer field is accepted as an unknown parameter and Upstream-Contact is optional: Format: http://dep.debian.net/deps/dep5/ Maintainer: foo@bar Files: * Copyright: (c) me License: GPL-2+ This program is free software; you can redistribute it and/or modify it [snip] In this case, is this an error or a DD who does not like the Upstream-Contact keyword ? How about emit a warning in unknown-but-likely-error cases like this. ...and perhaps optionally be invasive as is now the default. Err, correct me if I'm wrong, but that's already the case whether you run with -save option or not. E.g. on the example above, you can have the warnings without modifying copyright file: $ cp debian/copyright debian/copyright.bak $ config-edit -appli dpkg-copyright -ui none Element 'Maintainer' of node 'Debian::Dpkg::Copyright' is deprecated $ diff debian/copyright debian/copyright.bak And you can have the invasive behavior with the -save option $ config-edit -appli dpkg-copyright -ui none -save Element 'Maintainer' of node 'Debian::Dpkg::Copyright' is deprecated $ diff debian/copyright debian/copyright.bak 2,3c2,3 Upstream-Contact: foo@bar Source: --- Maintainer: foo@bar Is this the behavior you're thinking of ? All the best [ note to self: fix fishy behavior with the empty Source line ] Dominique PS: Note to all: I'm slowing down on DEP-5 parser development because I'm busy preparing FOSDEM -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101261120.38707.domi.dum...@free.fr
Re: New version of DEP-5 parser
Le vendredi 21 janvier 2011 22:18:18, Steve Langasek a écrit : Not having looked at the code, I'm wondering: do you apply these translations to all files regardless of the Format/Format-Specification field's value, or are you selective about only applying these upgrades to fields that were considered valid at the time? It's not selective. The model [1] that defines the behavior during the upgrade is purely declarative. Config::Model was designed to handle configuration files where the concept of unknown parameter does not apply. I don't think, for instance, that a file that has a declaration of Format: http://dep.debian.net/deps/dep5/ [1] should have 'Maintainer' fields auto-upgraded to 'Upstream-Contact', but that this should instead be treated as an unknown field. Like others, the history of this parameter is complicated. It was required, then deprecated, and now legal (but with a possibly different semantic content). If you factor in the possibility of human error (e.g. modern format, but forgotten Maintainer field), having a DEP-5 validated file may not mean much. For instance, this DEP-5 file is valid, since Maintainer field is accepted as an unknown parameter and Upstream-Contact is optional: Format: http://dep.debian.net/deps/dep5/ Maintainer: foo@bar Files: * Copyright: (c) me License: GPL-2+ This program is free software; you can redistribute it and/or modify it [snip] In this case, is this an error or a DD who does not like the Upstream-Contact keyword ? Note that the debian policy is respected since the upstream info is provided. But the original objective of DEP5 (facilitate automated checking and reporting of licenses for packages and sets of packages) is in jeopardy. If the consensus is that such a Maintainer field should be left as is, one solution would be to keep the current model with its upgrade capability and provide another pure dep-5 model. Then the user would to choose between: - the dep-5-model-with-upgrade (and a few drawbacks like deprecated Maintainer fields) - a pure dep-5 without migration I'll provide the latter if people ask for it for actual use. All the best Dominique [1] http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.230/lib/Config/Model/models/Debian/Dpkg/Copyright.pl -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101231509.01093.domi.dum...@free.fr
New version of DEP-5 parser
Hello I've fixed upstream [1] most (hopefully all) the issues regarding the DEP5 parser based on Config::Model that were mentioned on these lists or in the BTS. The new version is already (thanks gregoa) available on Debian/Sid in libconfig-model-perl 1.230 I've updated the parser so as to upgrade older version of copyright file (even pre DEP-5 versions) into the current format. All old keywords are translated into new keywords (except the old keywords I do not know yet about :-p ) For those who missed the previous thread, you can find more details in my blog [2]. Last but not least, I'll present Config::Model and its applications (including OpenSsh config and DEP-5 copyright) in the cross-distro dev room at FOSDEM in 2 weeks. Feel free to come by and let's discuss DEP5 or other possible applications. All the best Dominique [1] http://search.cpan.org/dist/Config-Model/ [2] http://ddumont.wordpress.com/2011/01/13/debian-copyright-dep5-parsereditorvalidatormigrator-is- released/ -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101212116.59690.domi.dum...@free.fr
Re: DEP5: Format example patch
On Thursday 20 January 2011 09:42:38 Stefano Zacchiroli wrote: An additional advantage of using a placeholder is that DEP5 implementation can easily detect that the placeholder is not a well-formed URL (Dominique: does your current implementation do that, by the way?). Currently, any url beginning with 'http://svn' is replaced by the DEP-5 approved URL. Any other field is accepted. I can easily change it to replace '.*' with the DEP-5 URL. I can also enforce a valid URL to be specified for other cases (are there any other cases ?) All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101201340.11181.d...@komarr.gre.hp.com
Re: DEP5: CANDIDATE and ready for use in squeeze+1
On Saturday 15 January 2011 14:03:39 Lars Wirzenius wrote: I went with the patch below. Thanks Zack, Charles, Andrei. Index: dep5.mdwn === --- dep5.mdwn (revision 161) +++ dep5.mdwn (working copy) @@ -149,12 +149,17 @@ will usually be written as a list of RFC5322 addresses or URIs. * **`Source`** - * Required + * Required, unless there is no upstream From a parser point of view, this requirement cannot be verified unless there's a way to know if a package is native or not. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101171014.04404.d...@komarr.gre.hp.com
DEP5 CANDIDATE parser/editor/validator/migrator is released in libconfig-model-perl
Hello
The new version of libconfig-model-perl 1.229 is now available in Sid. This
new version provides a model of DEP-5 updated according to the CANDIDATE
version. (Among other features [1], like editor/validator for debian/control).
The DEP-5 editor must be run in the source package directory (I'll provide an
example below) with the following command:
config-edit -application dpkg-copyright options
Features:
* check copyright file (with option -ui none)
* migrate from old format to new format ( with option -ui none -save)
* graphical editor (no option, but libconfig-model-tkui-perl must be installed)
Known issues:
- some keywords from older versions of DEP-5 specs may have been missed.
In this case, feel free to send a mail to config-model-users mailing
list or to log a bug in BTS.
- the update of the content of the format string is silent. This behavior
is a bit cavalier. This will change in the next version.
Example:
The copyright file of libconfig-model-backend-augeas-perl need to be updated:
Here's the original copyright file (slightly edited to protect my mail box
and save electrons) :
$ cat debian/copyright
Format-Specification:
http://wiki.debian.org/Proposals/CopyrightFormat?action=recallrev=196
Upstream-Maintainer: Dominique Dumont (ddumont at cpan.org)
Upstream-Source: http://search.cpan.org/dist/Config-Model-Backend-Augeas/
Upstream-Name: Config-Model-Backend-Augeas
Copyright: 2008-2009, Dominique Dumont (ddumont at cpan.org)
License: LGPL-2+
Files: debian/*
Copyright: 2009, Dominique Dumont dominique.dumont at hp.com
License: LGPL-2+
License: LGPL-2+
This program is free software; you can redistribute it and/or
[snip]
First, let's just check issues:
$ config-edit -application dpkg-copyright -ui none
Element 'Upstream-Maintainer' of node 'Debian::Dpkg::Copyright' is deprecated
Element 'Upstream-Source' of node 'Debian::Dpkg::Copyright' is deprecated
Element 'Upstream-Name' of node 'Debian::Dpkg::Copyright' is deprecated
Missing 'Files:' specification at top of section number 2. Adding 'Files: *'
spec
Then, let's see what's config-edit can fix all by itself:
$ config-edit -application dpkg-copyright -ui none -save
[ same warnings displayed ]
Let's check the result of the migration:
$ config-edit -application dpkg-copyright -ui none
[ good: no more warnings ]
And here's the content of the upgraded file (drum rolls, please):
$ cat debian/copyright
Format: http://dep.debian.net/deps/dep5/
Upstream-Name: Config-Model-Backend-Augeas
Upstream-Contact: Dominique Dumont (ddumont at cpan.org)
Source: http://search.cpan.org/dist/Config-Model-Backend-Augeas/
Files: *
Copyright: 2008-2009, Dominique Dumont (ddumont at cpan.org)
License: LGPL-2+
Files: debian/*
Copyright: 2009, Dominique Dumont dominique.dumont at hp.com
License: LGPL-2+
License: LGPL-2+
This program is free software; you can redistribute it and/or
[snip]
You can see that:
- keywords were changed while keeping the correct content
- Format: was updated with the right URL
- Files: * line was added in the right place
Please provide feedback!
If you have problem migrating DEP5 files, yell, and we'll fix them.
If this migration works fine, don't be shy, please say so.
Under the hood:
Most of the migration work is specified in DEP-5 model [2]. Using
config-model's GUI [3] to update DEP-5 model, about one hour was
spent to:
- flag old parameters as deprecated
- introduce new parameters from candidate version (mostly done by
cut'n'paste old parameters into their new name, done within the
model editor GUI )
- cut'n'paste the doc bits from the web page into the model editor GUI
- specify migrate_from instruction to copy semantic content from old
parameters to new ones. (*)
This shows one important feature of Config::Model: maintenance and evolution
of a model is not a huge task. Even though copyright files are not configuration
files, the same approach can be used to specify model and migration of other
configuration files.
Now comes the question of the migration as seen by the user. Well, it's your
turn now.
Try it and tell us how it works!
Hopefully, encouraged by your feedback, other people will apply config-model to
other
specifications or other configuration.
All the best
[1] http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.229/ChangeLog
[2]
http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.229/lib/Config/Model/models/Debian/Dpkg/Copyright.pl
[3] config-model-edit -model Debian::Dpkg::Copyright provided by
libconfig-model-iteslf-perl
http://freshmeat.net/projects/config-model-itself/
(*) E.g, in the text format produced by the model editor GUI:
'Upstream-Contact',
{
'value_type' = 'string',
'migrate_from' = {
'formula' = '$old_maintainer',
'variables' = {
'old_maintainer' = '- Maintainer'
}
},
'type' = 'leaf
Re: DEP5: CANDIDATE and ready for use in squeeze+1
Le vendredi 7 janvier 2011 11:09:59, Dominique Dumont a écrit : I'll update DEP5 description (aka Debian::Dpkg::Copyright model [1]) as soon as I've stabilised the latch batch of modifications in config-model. I've taken a stab at implementing the new specification. I've a new description matching the CANDIDATE DEP-5. (the new model is able to parse the new example, but I still need to polish the non-reg tests) As a bonus, Config::Model will be able to migrate copyright files from older specification to the new spec. One question: if the File: * line in the first File paragraph is missing (*), should it be added automatically ? This will be released in libconfig-model-perl 1.229. ETA end of this week. All the best Dominique (*) the examples shown in http://dep.debian.net/deps/dep5/ page are lacking a File: * line in the first File paragraph. -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101092042.30053.domi.dum...@free.fr
Re: DEP5: CANDIDATE and ready for use in squeeze+1
On Friday 07 January 2011 10:41:46 Stefano Zacchiroli wrote: Also, we should probably send out a sort of call for implementation of the present draft, as it would be nice to have working code, as well as policy integration, before moving DEP5 to ACCEPTED. In this case, working code should probably look like parsers and/or generators. AFAIR we used to have at least 2 such implementations for DEP5: - a config-model DEP5 description I'll update DEP5 description (aka Debian::Dpkg::Copyright model [1]) as soon as I've stabilised the latch batch of modifications in config-model. As always, comments and feedback on this implementation are welcome :-) All the best [1] http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.226/lib/Config/Model/models/Debian/Dpkg/Copyright.pl http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.226/lib/Config/Model/models/Debian/Dpkg/Copyright/Content.pl http://cpansearch.perl.org/src/DDUMONT/Config-Model-1.226/lib/Config/Model/models/Debian/Dpkg/Copyright/License.pl Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101071110.00439.dominique.dum...@hp.com
Re: dep5, whats the status? Re: DEP5: reasons for not pushing Bazaar changes to Subversion
On Thursday 23 December 2010 12:51:59 Lars Wirzenius wrote: I, personally, think it would be better to wait for the first version of DEP5 that is marked CANDIDATE, which I intend to announce on debian-devel-announce. Hopefully that will happen quite soon. Those who already use some revision, such as pkg-perl, should stick to what they are using now. Agreed. I'm waiting for this CANDIDATE version to update the DEP-5 parser provided by libconfig-model-perl. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012231432.01404.dominique.dum...@hp.com
Re: DEP5: Extra fields without ‘X-’ prefix?
On Monday 15 November 2010 17:47:26 Jonas Smedegaard wrote: Indeed. But people using extra fields will get warnings, so they will ignore them. Then, they will also ignore warnings triggered by typos in standard fields. True. But I see it as a challenge of parsers rather than a flaw of the format: it could be handled similar to lintian overrides (i.e. silence specific non-standard fields you yourself choose to use). How about calling DEP-5 parser from lintian and let lintian handle the overrides ? IMO this is sliding away from DEP5: feel free to move the conversation to the Config::Model mailinglist if you agree (readers are hereby warned). :-) I'd suggest to nail the use case here. All other implementations details will be discussed in Config::Model mailinglist. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201011221004.06823.dominique.dum...@hp.com
Re: DEP5: Extra fields without ‘X-’ prefix?
On Sunday 14 November 2010 12:13:32 Lars Wirzenius wrote: Extra fields can be added to any paragraph. No prefixing is necessary. Future versions of the `debian/copyright` specification will attempt to avoid conflicting specifications for widely used extra fields. Without prefixing, parsers won't be able to detect typos in field names. So validation of copyright files will be harder. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201011151428.18313.d...@komarr.gre.hp.com
Re: DEP5: Extra fields without ‘X-’ prefix?
On Monday 15 November 2010 15:26:17 Jonas Smedegaard wrote: Without prefixing, parsers won't be able to detect typos in field names. So validation of copyright files will be harder. Isn't your newly implemented warning feature suitable for handling this, Dominique? Indeed. But people using extra fields will get warnings, so they will ignore them. Then, they will also ignore warnings triggered by typos in standard fields. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201011151602.30939.d...@komarr.gre.hp.com
Config::Model: added editor for Debian package control files
Hello The new set of Config::Model packages released this week enable Debian developer to use Config::Model to edit and validate some of the files required to create Debian packages. Namely the control files and copyright files now have their model. You can now use the following commands to edit control or copyright files: - config-edit-dpkg-copyright - config-edit-dpkg-control Other noticeable changes are: * Config::Model::Itself 1.219 : Added warn_* parameters provided by Config::Model 1.212. Added allow_keys_matching parameter provided by C::M 1.207 * Config::Model::TkUi 1.315: Display configuration warnings provided by Config::Model 1.212. Bug fixes and usability improvements. *Config::Model 1.215 : DEP-5 is renamed in copyright (editor is config-edit- dpkg-copyright). Added Debian control model (editor is config-edit-dpkg- control). Can now specify warnings in model, i.e. warnings are shown to user according to conditions specified in configuration model. Read and writes correctly UTF-8 files. Cleaned up API. All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201010211801.20091.dominique.dum...@hp.com
Re: DEP5 parser is available in Debians/Sid
Le mercredi 22 septembre 2010 18:23:39, Jonas Smedegaard a écrit : Configuration item 'Debian::Dep5 License id' has a wrong value: Unexpected key 'PGL-1'. Key must match ^(?i:Apache|Artistic|BSD| FreeBSD|ISC|CC-BY|CC-BY-SA|CC-BY-ND|CC-BY-NC|CC-BY-NC-SA|CC-BY-NC-ND|CC0|C DDL| CPL|Eiffel|Expat|GPL|LGPL|GFDL|GFDL-NIV|LPPL|MIT|MPL|Perl|PSF|QPL|W3C- Software|ZLIB|Zope|other)[\d\.\-]*\+?$ Hmm - I believe you are being too restrictive above. Syntax for license field says that an arbitrary short name may be assigned which I can only interpret to the following regex: ^\w+$ Hmm, I may have interpreted too literally the 'other' specification ;-) Yes, standardized short names are encouraged, but not mandatory. Yet another challenge for your tool ;-) Well, it depends on what you want. Just relaxing the restriction above is trivial. But if you want a warning while allowing unknown licenses, then yes, I'll have to perform more extensive modifications to Config::Model( and on its various user interfaces to display properly the warnings...) Would such a warning be a great addition or should we just provide the license list in the doc ? All the best Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009231849.51504.domi.dum...@free.fr
DEP5 parser is available in Debians/Sid
Hello Thanks to gregoa's sponsorship, the new parser for DEP5 is available in libconfig-model-perl 1.209. To run it, use the command config-edit-dep5. For instance: $ dh-make-perl --cpan Dancer [snip] $ cd Dancer-1.1812/ $ config-edit-dep5 -ui none $ sed -i 's/GPL/PGL/' debian/copyright $ config-edit-dep5 -ui none Configuration item 'Debian::Dep5 License id' has a wrong value: Unexpected key 'PGL-1'. Key must match ^(?i:Apache|Artistic|BSD| FreeBSD|ISC|CC-BY|CC-BY-SA|CC-BY-ND|CC-BY-NC|CC-BY-NC-SA|CC-BY-NC-ND|CC0|CDDL| CPL|Eiffel|Expat|GPL|LGPL|GFDL|GFDL-NIV|LPPL|MIT|MPL|Perl|PSF|QPL|W3C- Software|ZLIB|Zope|other)[\d\.\-]*\+?$ '-ui none' option is specified to skip user interfaces. Feel free to send feedback to improve this parser. All the best -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009221405.53690.domi.dum...@free.fr
First explanations on DEP-5 parser
Hello As discussed on Lars' blog [1], I've written an explanation [2] on the creation of a DEP-5 parser using Config::Model. I'll release the code soon first on CPAN, then in Debian's libconfig-model- perl package. All the best [1] http://blog.liw.fi/posts/debian-plans/ [2] http://ddumont.wordpress.com/2010/09/14/119/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009141313.18529.dominique.dum...@hp.com
