Le Mon, Aug 10, 2009 at 10:58:04AM -0400, Jonathan Yu a écrit :
> On Mon, Aug 10, 2009 at 1:13 AM, Charles Plessy wrote:
> >
> > we just had a case in the Debian Med packaging team where the upstream
> > author
> > of software licensed under terms similar to the BSD license got upset to see
> > th
Package: wnpp
Severity: wishlist
Owner: Ian Campbell
Hi Mathieu,
Are you still planning to package congruity? I've just completed a rough draft
packaging before I found this ITP. I'm happy to hand over what I've got to you
or else perhaps you would consider sponsoring the package for me?
Cheers
On Mon, Aug 17, 2009 at 09:53:34AM -0700, Russ Allbery wrote:
> Yves-Alexis Perez writes:
> > On lun, 2009-08-17 at 13:01 +1000, Ben Finney wrote:
>
> >> So surely the best way to tell if a translated page is out of date is
> >> to compare these dates in the two documents, no?
>
> > And I guess
On Mon, Aug 17, 2009 at 07:10:00PM -0700, Russ Allbery wrote:
> Ben Finney writes:
>
> > What is the governing standard for Debian man pages, and what does it
> > say about the ‘TH’ command?
>
> I don't believe we have any standard other than "you should have one" and
> some guidelines about tra
Nicolas François writes:
> But I agree that if both the English and a translated manpages have a
> date in the format -MM-DD, and the date of the translated manpages
> has an older date, lintian could warn.
Well if we're dreaming up proposed tests (sans implementation) for
Lintian to perform
On Mon, Aug 17, 2009 at 01:01:34PM +1000, Ben Finney wrote:
> gregor herrmann writes:
>
> > An interesting question is how to detect outdated translated manpages;
>
> According to ‘man-pages(7)’, the TH command in the man page should have
> the date of the latest version of the document:
>
>
> This is just my own personal use of .TH in all my projects
> , using sbuild as an example:
>
> TH SCHROOT 1 "@RELEASE_DATE@" "Version @VERSION@" "Debian
> sbuild"
>
> where @RELEASE_DATE@ is the date of the release, which
> gets substituted in by autoconf's configure script
> (schroot.1.in -> s
Roger Leigh writes:
> On Mon, Aug 17, 2009 at 01:01:34PM +1000, Ben Finney wrote:
> > I assume we expect man pages to conform to the conventions in
> > ‘man-pages(7)’.
(I've now been disabused of that assumption.)
> I'm not sure we can have that expectation. If you look at
> groff_man(7), it sp
On 2009-08-18, Andrea Bolognani wrote:
> This also means localized manpages will always fail the simple
> date check, unless you use the same .TH line in every localized
> manpage. Doing so, however, would make it as impossible to know
> which manpages are outdated based on the .TH line.
And what
On Tue, Aug 18, 2009 at 08:13:20PM +1000, Ben Finney wrote:
> Roger Leigh writes:
>
> > On Mon, Aug 17, 2009 at 01:01:34PM +1000, Ben Finney wrote:
> > > I assume we expect man pages to conform to the conventions in
> > > ‘man-pages(7)’.
>
> (I've now been disabused of that assumption.)
>
> > I
On Tue, 18 Aug 2009 10:29:32 + (UTC), Philipp Kern
wrote:
>
> And what should we do if a localized manpage is in fact
> the authoriative one?
That doesn't change a thing: if the date in the .TH line is
supposed to be that of the last update (making a lintian
check based on that date would ot
It's only unambiguous if you know the convention being adopted /is/
ISO-8601. In an ideal world, we could have a standardised date format
which the man program can transform into the date representation of
the user's locale thus satisfying all requirements.
???
Thats what ISO-8601 is. There
On Tue, Aug 18, 2009 at 12:21:38PM +0100, Alastair McKinstry wrote:
>>>
>>
>> It's only unambiguous if you know the convention being adopted /is/
>> ISO-8601. In an ideal world, we could have a standardised date format
>> which the man program can transform into the date representation of
>> the u
On Tue, Aug 18, 2009 at 08:13:20PM +1000, Ben Finney wrote:
> Roger Leigh writes:
>
> > I, for example, use the date format '+%d %b %Y' (01 Aug 2009). The
> > manual pages are human readable documentation. I think that nicely
> > readable dates should be preferred here.
>
> This seems to falsely
Hi Charles:
On Tue, Aug 18, 2009 at 3:06 AM, Charles Plessy wrote:
> Le Mon, Aug 10, 2009 at 10:58:04AM -0400, Jonathan Yu a écrit :
>> On Mon, Aug 10, 2009 at 1:13 AM, Charles Plessy wrote:
>> >
>> > we just had a case in the Debian Med packaging team where the upstream
>> > author
>> > of softw
Hi all,
libgnomeprint/libgnomeprintui is going to be soon deprecated upstream.
The GtkPrint replacement (built in GTK+ itself) has been available for 3
years.
I’d like to remove it before the squeeze release. This can only be done
by getting rid of as much as possible of the reverse dependencies.
Josselin Mouette wrote:
Hi all,
libgnomeprint/libgnomeprintui is going to be soon deprecated upstream.
The GtkPrint replacement (built in GTK+ itself) has been available for 3
years.
I’d like to remove it before the squeeze release. This can only be done
by getting rid of as much as possible of
On Sat, 15 Aug 2009 20:21:47 +0200
Martin Zobel-Helas wrote:
> Package: gpe-expenses
> Version: 0.1.7-2+b1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of gpe-expenses_0.1.7-2+b1 on rem by sbuild/mipsel 99.999
There doesn't appear to
Hi,
in the Debian Pure Blends effort we were wondering about relations of packages
and what an "Enhances" relation actually means. Debian Policy says:
`Enhances'
This field is similar to Suggests but works in the opposite
direction. It is used to declare that a package
On Tue, Aug 18, 2009 at 09:13:42PM +0200, Andreas Tille wrote:
> What exactly means "similar". Assume package foo enhances package bar.
> Does this mean that in turn package bar should Suggest package foo or
> is this conclusion not really valid?
As I understand it, "A enhances B" has (more or le
Package: debian-policy
Version: 3.8.3.0
Severity: wishlist
User: debian-pol...@packages.debian.org
Usertags: normative issue
Hi,
Currently, there is some ambiguity in the areas of version
numbering, debian_revision, native packages, and requirement for a
diff.gz/orig.tar.gz files in a s
Ben Finney writes:
> I guess the question then becomes: since Policy describes supposed best
> practice for Debian, *should* we be more specific about the format of a
> man page? I think the conventions described in ‘man-pages(7)’ are a good
> basis for recommendations for all Debian man pages.
Philipp Kern writes:
> On 2009-08-18, Andrea Bolognani wrote:
>> This also means localized manpages will always fail the simple date
>> check, unless you use the same .TH line in every localized
>> manpage. Doing so, however, would make it as impossible to know which
>> manpages are outdated bas
Package: wnpp
Severity: wishlist
Owner: Jacob Peddicord
* Package name: commandeer
Version : 0.2.0
Upstream Author : Jacob Peddicord
* URL : https://launchpad.net/commandeer
* License : GPL2
Programming Lang: Vala
Description : application to lock the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
it is an old RFH, but I want to remind it:
We are needing help with the fglrx packaging.
The person who would apply for this job should require the following:
- - Using a radeon card > 2000 HD, which is supported by fglrx >= 9.4
- - Using uns
Mask to Protect from H1N1 virus
3 ply surgical face mask :
Detailed Product Description :
Surgical Mask
Material : PPSB + Meltblown
Model : 3 ply nonwoven swine flu face amsk
Colour : White
Apply : H1N1
Standard : EN149 : 2001
Stock : 1 500 000 pcs
Now we can offer you large quantit
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: libnet-trac-perl
Version : 0.14
Upstream Author : Jesse Vincent
* URL : http://search.cpan.org/dist/Net-Trac/
* License : Perl (Artistic | GPL-1+)
Programming Lang: Perl
Description
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: libnet-redmine-perl
Version : 0.08
Upstream Author : Kang-min Liu
* URL : http://search.cpan.org/dist/Net-Redmine/
* License : Perl (Artistic | GPL-1+)
Programming Lang: Perl
Descripti
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: libnet-github-perl
Version : 0.18
Upstream Author : Fayland Lam
* URL : http://search.cpan.org/dist/Net-GitHub/
* License : Perl (Artistic | GPL-1+)
Programming Lang: Perl
Description
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: librt-client-rest-perl
Version : 0.37
Upstream Author : Dmitri Tikhonov
* URL : http://search.cpan.org/dist/RT-Client-REST/
* License : GPL
Programming Lang: Perl
Description : RES
On Tue, 2009-08-18 at 22:36 +0300, Antti-Juhani Kaijanaho wrote:
> On Tue, Aug 18, 2009 at 09:13:42PM +0200, Andreas Tille wrote:
> > What exactly means "similar". Assume package foo enhances package bar.
> > Does this mean that in turn package bar should Suggest package foo or
> > is this conclus
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: libnet-hiveminder-perl
Version : 0.08
Upstream Author : Shawn Moore
* URL : http://search.cpan.org/dist/Net-Hiveminder/
* License : Perl (Artistic | GPL-1+)
Programming Lang: Perl
Desc
Package: wnpp
Severity: wishlist
Owner: Christine Spang
* Package name: libnet-google-code-perl
Version : 0.14
Upstream Author : sunnavy
* URL : http://search.cpan.org/dist/Net-Google-Code/
* License : Perl (Artistic | GPL-1+)
Programming Lang: Perl
Descri
Ben Hutchings writes:
> On Tue, 2009-08-18 at 22:36 +0300, Antti-Juhani Kaijanaho wrote:
> > As I understand it, "A enhances B" has (more or less) the same
> > effect as "B suggests A". Thus, the reverse Suggests relation would
> > be redundant.
>
> A plugin "enhances" the application it works in
Ben Finney wrote:
> Ben Hutchings writes:
>
>> On Tue, 2009-08-18 at 22:36 +0300, Antti-Juhani Kaijanaho wrote:
>>> As I understand it, "A enhances B" has (more or less) the same
>>> effect as "B suggests A". Thus, the reverse Suggests relation would
>>> be redundant.
>> A plugin "enhances" the a
James Westby writes:
> Ben Finney wrote:
> > Yet a package of a plugin should surely have a ‘Depends’
> > relationship to the application package. Adding an ‘Enhances’
> > relationship seems redundant in that case.
>
> No, there are plenty of packages which depend on another without
> enhancing t
X-Loop
ow...@bugs.debian.org: Resent-Date: Wed, 19 Aug 2009 04:03:02 +
Resent-Message-ID:
Resent-Sender: ow...@bugs.debian.org
X-Debian-PR-Message: report 542330
X-Debian-PR-Package: wnpp
X-Debian-PR-Keywords:
Received: via spool by sub...@bugs.debian.org id=B.125065431325718
(code
On Wed, Aug 19, 2009 at 01:44:49AM +0100, James Westby wrote:
> I see it as an almost bi-directional relationship, but one that allows
> you to add it to the package that "cares" about it more.
So the answers somehow draw a sketch about the concept behind the
Enhances field - but is it technically
On Friday 15 May 2009 06:26:00 Jiří Paleček wrote:
> > I am not yet comfortable with my security policy changing just
> > because a package is installed. So far, even the policy packages do not
> > install the new policy, letting the security officer audit and manually
> > install policy
On Tue, 18 Aug 2009, Russ Allbery wrote:
> Ben Finney writes:
>
> > I guess the question then becomes: since Policy describes supposed best
> > practice for Debian, *should* we be more specific about the format of a
> > man page? I think the conventions described in ‘man-pages(7)’ are a good
> >
Raphael Hertzog writes:
> On Tue, 18 Aug 2009, Russ Allbery wrote:
> > Given our limited success in getting people to provide man pages for
> > every binary to start with, I'm reluctant to ask package maintainers
> > to patch upstream man pages to do relatively inconsequential things
> > like add
41 matches
Mail list logo
