Le Sat, Oct 22, 2011 at 10:34:09PM -0700, Russ Allbery a écrit :
I see those two issues as linked because of how version numbering works,
which is the key difference in using the native format. With a native
package, you only have a single version number, not a version with a
Debian
Charles Plessy ple...@debian.org writes:
I think that I am missing documentation on that topic.
Yes, I seem to recall there's an open Policy bug for the fact that native
and non-native packages aren't particularly well-documented.
The Policy §3.2 mentions ‘remember that hyphen (-) cannot be
On Sun, Oct 23, 2011 at 01:32:16PM +0800, Wen-Yen Chuang wrote:
Hi,
I am looking for a sponsor for the new version 0.5.0-1
of my package evilvte. (Programming language: C)
Uploaded, thanks.
Sven
--
And I don't know much, but I do know this:
With a golden heart comes a rebel fist.
[
Dear Michael and other mentors,
An annoying bug in the upstream source of fizsh version 1.0.4 has been
discovered, and fixed. Therefore, upstream has released a new bug-fix
version 1.0.5.
This is why I withdraw this RFS, which is related to the version
1.0.4. I will upload a packaged version of
Dear Michael, and other mentors,
I am looking for a sponsor for my package fizsh.
* Package name: fizsh
Version : 1.0.5-1
Upstream Author : Guido van Steen (myself)
* URL : http://sourceforge.net/projects/fizsh/
* License : Modified BSD License
Section
Hello Ole,
Le mardi 18 octobre 2011 à 19:06 +0200, Ole Streicher a écrit :
Dear mentors,
I am looking for a sponsor for my package python-pywcs.
[...]
I would be glad if someone uploaded this package for me.
I am willing to sponsor your package. However, I would like to know
first if you
What should you do if you have a dependency which can either use one
package or two (or more) different packages. For example, roxterm's man
pages can be built either with xmltoman, xmlto or xsltproc, but xsltproc
additionally requires docbook-xsl. I don't think control file syntax
supports
[...]
Build-Depends: xsltproc | xmltoman | xmlto, docbook-xsl | xmltoman | xmlto
This would be a correct rewrite to CNF, but ...
Or would it be better to choose one and stick to that for the sake of
consistency?
... there isn't much of a point doing it here for Build-Depends. The
On Sun, 23 Oct 2011 21:23:41 +0200
Michael Tautschnig m...@debian.org wrote:
[...]
Build-Depends: xsltproc | xmltoman | xmlto, docbook-xsl | xmltoman
| xmlto
This would be a correct rewrite to CNF, but ...
Or would it be better to choose one and stick to that for the sake
of
I tried to correct a ITP by sending email to 646...@bugs.debian.org but the
email was rejected.
Delivery to the following recipient failed permanently:
646...@bugs.debian.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
Paul,
On Sun, Oct 23, 2011 at 9:34 PM, Paul Elliott
pelli...@blackpatchpanel.com wrote:
I tried to correct a ITP by sending email to 646...@bugs.debian.org but the
email was rejected.
Delivery to the following recipient failed permanently:
646...@bugs.debian.org
Technical details of
Fernando Lemos fernando...@gmail.com writes:
Paul Elliott pelli...@blackpatchpanel.com wrote:
This is a small family domain. I control it. It goes thru google
email. only 2 accounts in domain. All the computers on it use linux. It
is extremely unlikely any spam has ever been sent from this
On Sun, 23 Oct 2011, Paul Elliott wrote:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient
domain. We recommend contacting the other email provider for further
information about the cause of this error. The error that the
13 matches
Mail list logo
