Hi!
On Fri, 2015-06-26 at 10:56:58 +0200, Santiago Vila wrote:
> On Fri, Jun 26, 2015 at 04:40:58AM +0200, Guillem Jover wrote:
> > So given that the timezone name has never been accepted, many
> > time-parsing functions ignore it, it is redundant, declared obsolete
> > by RFC5322 and Debian polic
On Fri, Jun 26, 2015 at 04:40:58AM +0200, Guillem Jover wrote:
> So given that the timezone name has never been accepted, many
> time-parsing functions ignore it, it is redundant, declared obsolete
> by RFC5322 and Debian policy dropped an explicit reference to it due
> to bug 569174. I'd say we sh
Hi!
The other day, while fixing some dpkg code, I noticed that the Debian
changelog trailer regex intended to support a timezone name inside
parenthesis, like this:
-- Name Sat, 30 May 2015 03:18:43 +0200 (CEST)
is bogus (since its inception in dpkg 1.3.0, 1996-08), and it only
accepts one ch
Install the sources of the hello package and look at changelog, that's what
i did. Apparently the format is
() ;urgency=
*
*
--
with <..> to be replaced by the proper values.
Later,
Dominik
The text above is my personal opinion and does not reflect the official
position of my em
Could somebody please point me to the "changelog" file format? I'm trying
to build the new 'dftp' package but it keeps dieing on the changelog file.
Please respond by email since I _still_ have not been able to subscribe to
this list.
Is there a reason why dpkg-parsechangelog is so picky about the number of
blanks used? Does it really matter if I have one or two blanks between my
email address and the date? I think it could be a bit more user friendly.
Please keep in mind that not everyone uses emacs.
Michael
--
Michael Meskes
Ian Jackson <[EMAIL PROTECTED]> said:
> Bruce Perens writes ("Re: ChangeLog format "):
> > Please make sure, whatever [alternative] upload announcement [...]
>
> My format is suitable, except for one piece of information which it
> doesn't contain: t
to turn these tiny scripts
> into released software. Surely people who are building software for
> release and hacking debian.rules files and so forth can write a 5 or
> 10-line utility shellscript to fit their way of working ?
The point of Bruce's new Changelog format, which dchange
Ian Jackson <[EMAIL PROTECTED]>
> What precisely does dchanges take as input ?
I wondered why you'd ask this, until I discovered that the
dchanges packages wasn't umong the packages I'd downloaded.
After some searching around on ftp.debian.org, I located
it in project/experimental.
Here's a copy
Bruce Perens writes ("Re: ChangeLog format "):
> Please make sure, whatever [alternative] upload announcement format
> you design, that it is machine-readable so that it can be used to
> (at least partially) automate the FTP site administration
> process. The format should s
Please make sure, whatever alternate upload announcement format you design,
that it is machine-readable so that it can be used to (at least partially)
automate the FTP site administration process. The format should state
in an unambiguous-to-parse fashion the names of all files uploaded, the
size a
Bill Mitchell writes ("Re: ChangeLog format"):
> All this is a bit structured for maintainers with just a few
> packages, but I've got about 20.
I have a total of about 20 lines of script to do all of my changelog
generation, and I have about 10 packages.
I think there ar
Andrew Howell writes ("Re: ChangeLog format"):
> I like dchanges for the simple fact that it does the tiresome md5sum
> and size of file work for me, and it's standardised many of the package
> annoucements. If we switch to something else I'd want a similiar tool
I realised I didn't attach the scripts I use to my previous message.
---8<--- /usr/local/bin/822-date
#!/usr/bin/perl --
# I hereby place this in the public domain - Ian Jackson, 1995.
@ARGV && die "usage: 822-date\n";
$x=time; sub z { $_[1]+$_[2]*60; }; @l=localtime($x); $od=1440;
$d=&z(@l)-&z(gm
Bill Mitchell writes:
> Horrible, etc. seems a bit harsh. I'm not rabid about the dchanges
> format (which, after all, wasn't my idea in the first place), but I
> don't think it's all that bad. I think having the dchanges tool
> available to syntax check it before uploading is a big plus if
> it'
On Sun, 22 Oct 1995, Ian Jackson wrote:
> There are two things here: the Changelog format and the announcement
> format. I think it is probably valuable to separate them.
Yes. I've been following a practice of cutting my most recent
ChangeLog entry out and using it verbatim in
There are two things here: the Changelog format and the announcement
format. I think it is probably valuable to separate them.
The announcements should contain the Changelog entries since the last
announced version, and they also need to contain the MD5 checksums,
filenames and file sizes.
The
There's been some discussion of package announcement file format
recently. I have some observations on matters relating to this.
Observation #1: There are disconnects between package announcements
and the availability of packages in the distribution.
1. Packages are generally
> I'd like for all members of the Project to agree on a common format.
> Frankly, I don't like the one currently implemented in dchanges. I
> assume there are a few people who agree with me, as not everyone is
> using dchanges to write their announcements.
Well, I haven't adopted any particular f
On Sat, 21 Oct 1995, Ian Jackson wrote:
> Ian Murdock writes ("ChangeLog format"):
> > Personally, I like Ian J.'s ChangeLog format--I think it satifies
> > both goals of being human-readable and machine-readable.
>
> Would it be helpful if I wrote a spec.
Ian Murdock writes ("ChangeLog format"):
> Personally, I like Ian J.'s ChangeLog format--I think it satifies
> both goals of being human-readable and machine-readable.
Would it be helpful if I wrote a spec. saying what the format is, so
that people writing changelogs and p
t that is *both* machine-readable and
human-readable. The currently-used format is certainly machine-
readable, but it isn't human-readable at all. I don't think that
these are mutually-exclusive goals.
Personally, I like Ian J.'s ChangeLog format--I think it satifies
both goals of be
22 matches
Mail list logo
