Package updated to same version

Tags

dpkg

Operating Systems Linux Debian Package updated to same version

05-10-2009

Registered User

37, 0

Join Date: Apr 2009

Last Activity: 1 October 2009, 8:44 PM EDT

Posts: 37

Thanks Given: 0

Thanked 0 Times in 0 Posts

Package updated to same version

Hi,

I recently did slight modifications to the basename utility from the coreutils package.
I downloaded the source by typing "apt-get source coreutils", added a new option to the program, updated the respective manpage, build and installed it using "dpkg-buildpackage -uc -b && dpkg -i ../coreutils*.deb".

All that works perfectly. Now what's strange about it, is that my aptitude cronjob is updating the coreutils package from the repositories to the same but unmodified release that is already installed.

I could set the package status to "hold" but that would prevent the package from getting real updates.

Can anybody shed some light on that?

Thanks a lot,
Gunther

Gunther

View Public Profile for Gunther

Find all posts by Gunther

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Redhat check when package was updated

Is there a way to check when a package was updated on your redhat system?

2. Shell Programming and Scripting

Package version testing script

I was wondering if anyone already had a script to check rpm packages versions x.x.x or greater. so I could do a: # CheckRpmVersion Somepackage-1.2.3 And would output: whether the package is installed or not and if it was equal to or greater than the version 1.2.3. I know I can pull out...

3. UNIX for Dummies Questions & Answers

package version

hi, I have this problem. I run a script to check which version of a given package is installed and I need something returning a meaningfull answer also if the installation was done with the sources. Let's say that, a priori, I do not know how the package was installed. So far I have...

LEARN ABOUT XFREE86

dpkg-scansources

dpkg-scansources(1)						    dpkg suite						       dpkg-scansources(1)

NAME

       dpkg-scansources - create Sources index files

SYNOPSIS

       dpkg-scansources [option...] binary-dir [override-file [path-prefix]] > Sources

DESCRIPTION

       dpkg-scansources scans the given binary-dir for .dsc files.  These are used to create a Debian source index, which is output to stdout.

       The  override-file,  if	given,	is used to set priorities in the resulting index records and to override the maintainer field given in the
       .dsc files.  The file can be compressed (since dpkg 1.15.5).  See deb-override(5) for the format of this file.  Note:  Since  the  override
       file  is  indexed  by binary, not source packages, there's a bit of a problem here. The current implementation uses the highest priority of
       all the binary packages produced by a .dsc file for the priority of the source package, and the override entry for the first binary package
       listed in the .dsc file to modify maintainer information. This might change.

       The  path-prefix, if given, is prepended to the directory field in the generated source index. You generally use this to make the directory
       fields contain the path from the top of the Debian archive hierarchy.

       Note: If you want to access the generated Sources file with apt(8) you will probably need to compress the file with gzip(1)  (generating  a
       Sources.gz file). apt ignores uncompressed Sources files except on local access (i.e.  file:// sources).

OPTIONS

       -n, --no-sort
	   Don't sort the index records. Normally they are sorted by source package name.

       -e, --extra-override file
	   Scan file to find supplementary overrides (since dpkg 1.15.4; the file can be compressed since dpkg 1.15.5).  See deb-extra-override(5)
	   for more information on its format.

       -s, --source-override file
	   Use file as the source override file (the file can be compressed since dpkg 1.15.5).  The default is the name of the override file  you
	   specified with .src appended.

	   The	source override file is in a different format from the binary override file. It contains only two whitespace separated fields, the
	   first is the source package name and the second is the section. Blank lines and comment lines are ignored in the normal  manner.  If  a
	   package appears in both files the source override takes precedence for setting the section.

       --debug
	   Turn debugging on.

       --help
	   Show the usage message and exit.

       --version
	   Show the version and exit.

SEE ALSO

       deb-override(5), deb-extra-override(5), dpkg-scanpackages(1).

1.19.0.5							    2018-04-16						       dpkg-scansources(1)

Debian