Sponsored Content
Top Forums Shell Programming and Scripting Getting data with unstable space Post 302919714 by Akshay Hegde on Friday 3rd of October 2014 09:51:39 AM
Old 10-03-2014
OR else something like this might help

Code:
 date | awk '{split($0,d,/[^[:space:]]*/); printf("%s%s%s\n",$2,d[3],$3)}'

I am bit confused , forgive me if I misunderstood your requirement.
This User Gave Thanks to Akshay Hegde For This Post:
 

7 More Discussions You Might Find Interesting

1. Programming

appending space in binary data in c

Hi ... I am having a string in the buffer .. It is binary data it may contain space . When i try to append a space in using strcpy it is taking the inbetween \n as the end and appending space .. How to append space in the binary data in C ?? please let me know Thanks in advance, Arun. (2 Replies)
Discussion started by: arunkumar_mca
2 Replies

2. Shell Programming and Scripting

Delete all data before first space occurence

Hi Guyz, Can anyone help me in the following:- I want to delete all that is there in my file that occures before the first space comes. Eg. My file InputFile conatins the following: 123 12345678 87654 Hello 09867 09876654 34567 Happy I want the data occuring before the occurence... (3 Replies)
Discussion started by: DTechBuddy
3 Replies

3. Shell Programming and Scripting

Calculate total space, total used space and total free space in filesystem names matching keyword

Good afternoon! Im new at scripting and Im trying to write a script to calculate total space, total used space and total free space in filesystem names matching a keyword (in this one we will use keyword virginia). Please dont be mean or harsh, like I said Im new and trying my best. Scripting... (4 Replies)
Discussion started by: bigben1220
4 Replies

4. Shell Programming and Scripting

Export data from DB2 table to .txt file(space delimited)

Hi I need help on this. Its very urgent for me.. please try to help me out.. I have data in tables in DB2 database. I would like to export the data from DB2 tables into a text file, which has to be space delimited. so that I can carry out awk, grep operations on that file. I tried to export... (2 Replies)
Discussion started by: ss3944
2 Replies

5. Shell Programming and Scripting

Processing data that contains space and quote delimiters

I need to write a Bash script to process a data file that is in this format: 1 A B C D E 2 F G "H H" I J As you can see, the data is delimited by a space, but there are also some fields that contain spaces and are surrounded by double-quotes. An example of that is "H H". I wrote... (7 Replies)
Discussion started by: RickS
7 Replies

6. Shell Programming and Scripting

Converting variable space width data into CSV data in bash

Hi All, I was wondering how I can convert each line in an input file where fields are separated by variable width spaces into a CSV file. Below is the scenario what I am looking for. My Input data in inputfile.txt 19 15657 15685 Sr2dReader 107.88 105.51... (4 Replies)
Discussion started by: vharsha
4 Replies

7. Shell Programming and Scripting

Insert space or pattern between columns in a data file

I have a data file where three data sets are written in three columns. Can I increase the space between the columns without reading them? Also can I insert particular patterns, say comma between 1st and 2nd column and colon between 2nd and 3rd column? (13 Replies)
Discussion started by: hbar
13 Replies
deb-changelog(5)						    dpkg suite							  deb-changelog(5)

NAME
       deb-changelog - dpkg source packages' changelog file format

SYNOPSIS
       changelog

DESCRIPTION
       Changes in the packaged version of a project are explained in the changelog file debian/changelog.  This includes modifications made in the
       source package compared to the upstream one as well as other changes and updates to the package.

       The format of the debian/changelog allows the package building tools to discover which version of the package is being built and  find  out
       other release-specific information.

       That format is a series of entries like this:

       package (version) distributions; metadata
		 [optional blank line(s), stripped]
	 * change-details
	   more-change-details
		 [blank line(s), included in output of dpkg-parsechangelog(1)]
	 * even-more-change-details
		 [optional blank line(s), stripped]
	-- maintainer-name <email-address>  date

       package and version are the source package name and version number.

       distributions  lists  one or more space-separated distributions where this version should be installed when it is uploaded; it is copied to
       the Distribution field in the .changes file.

       metadata is a comma-separated list of keyword=value items.  The only keywords currently supported by  dpkg  are	urgency  and  binary-only.
       urgency's  value  is  used for the Urgency field in the .changes file for the upload.  binary-only with a yes value, is used to denote that
       this changelog entry is for a binary-only non-maintainer upload (an automatic binary rebuild with  the  only  change  being  the  changelog
       entry).

       The  change  details  may  in  fact be any series of lines starting with at least two spaces, but conventionally each change starts with an
       asterisk and a separating space and continuation lines are indented so as to bring them in line with the start of the  text  above.   Blank
       lines may be used here to separate groups of changes, if desired.

       If  this  upload  resolves bugs recorded in the distribution bug tracking system, they may be automatically closed on the inclusion of this
       package into the distribution archive by including the string:
	 Closes: Bug#nnnnn
       in the change details (the exact Perl regular expression is /closes:s*(?:bug)?#?s?d+(?:,s*(?:bug)?#?s?d+)*/i).  This information is
       conveyed via the Closes field in the .changes file.

       The  maintainer	name and email address used in the changelog should be the details of the person who prepared this release of the package.
       They are not necessarily those of the uploader or usual package maintainer.  The information here will be copied to the Changed-By field in
       the .changes file, and then later might be used to send an acknowledgement when the upload has been installed in the distribution archive.

       The date has the following format (compatible and with the same semantics of RFC2822 and RFC5322, or what <<date -R>> generates):

	      day-of-week, dd month yyyy hh:mm:ss +zzzz

       where:

       day-of-week
	      Is one of: Mon, Tue, Wed, Thu, Fri, Sat, Sun.

       dd     Is a one- or two-digit day of the month (01-31).

       month  Is one of: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

       yyyy   Is the four-digit year (e.g. 2010).

       hh     Is the two-digit hour (00-23).

       mm     Is the two-digit minutes (00-59).

       ss     Is the two-digit seconds (00-60).

       [+-]zzzz
	      Is  the time zone offset from Coordinated Universal Time (UTC).  '+' indicates that the time is ahead of (i.e., east of) UTC and '-'
	      indicates that the time is behind (i.e., west of) UTC.  The first two digits indicate the hour difference from UTC and the last  two
	      digits indicate the number of additional minutes difference from UTC.  The last two digits must be in the range 00-59.

       The  first  "title" line with the package name must start at the left hand margin.  The "trailer" line with the maintainer and date details
       must be preceded by exactly one space.  The maintainer details and the date must be separated by exactly two spaces.

       Any line that consists entirely (i.e., no leading whitespace) of # or /* */ style comments, RCS keywords,  Vim  modelines  or  Emacs  local
       variables should be ignored.

       Ancient changelog entries with other formats at the end of the file should be accepted and preserved on output, but their contents might be
       otherwise ignored and parsing stopped at that point.

       The entire changelog must be encoded in UTF-8.

FILES
       debian/changelog

EXAMPLES
       dpkg (1.17.18) unstable; urgency=low

	 [ Guillem Jover ]
	 * Handle empty minimum versions when initializing dependency versions,
	   as the code is mapping the minimum version 0 to '' to avoid outputting
	   useless versions. Regression introduced in dpkg 1.17.17. Closes: #764929

	 [ Updated programs translations ]
	 * Catalan (Guillem Jover).

	 [ Updated dselect translations ]
	 * Catalan (Guillem Jover).
	 * German (Sven Joachim).

	-- Guillem Jover <guillem@debian.org>  Sun, 12 Oct 2014 15:47:44 +0200

SEE ALSO
       deb-version(7), deb-changes(5), dpkg-parsechangelog(1).

1.19.0.5							    2018-04-16							  deb-changelog(5)
All times are GMT -4. The time now is 07:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy