On 30/01/2010 13:13, Roger Leigh wrote:
On Sat, Jan 30, 2010 at 09:11:25AM +0100, Vincent Danjean wrote:
My reason for this behavior was that I want
1) doc installed by mercurial-common in its name-space (ie in
/usr/share/doc/mercurial-common)
2) doc easy to find by mercurial users in /us
On Sat, Jan 30, 2010 at 12:41:46AM +0100, Stefan Fritsch wrote:
> On Saturday 30 January 2010, Ben Finney wrote:
> > So, the version was upgraded to ‘1.2.1-1+b1’, but there latest
> > entry in the changelog is still only ‘1.4.1-1’. There is no entry
> > describing the changes in the latest releas
Vincent Danjean writes:
> Hi,
>
> On 30/01/2010 01:19, Russ Allbery wrote:
>> Goswin von Brederlow writes:
>>
>>> The +b suffix on the version is indeed a binNMU. That means that the
>>> source was recompiled without any changes to the source. The changelog
>>> is the one from the source so i
On Sat, Jan 30, 2010 at 09:11:25AM +0100, Vincent Danjean wrote:
> My reason for this behavior was that I want
> 1) doc installed by mercurial-common in its name-space (ie in
>/usr/share/doc/mercurial-common)
> 2) doc easy to find by mercurial users in /usr/share/doc/mercurial
>
> The symlink
Hi,
On 30/01/2010 01:19, Russ Allbery wrote:
Goswin von Brederlow writes:
The +b suffix on the version is indeed a binNMU. That means that the
source was recompiled without any changes to the source. The changelog
is the one from the source so it only has the source version as top
entry.
"Adam D. Barratt" writes:
> On Sat, 2010-01-30 at 10:20 +1100, Ben Finney wrote:
> > =
> > $ PACKAGE=mercurial
> >
> > $ dpkg-query -W -f 'Version: ${Version}\n' $PACKAGE
> > Version: 1.4.1-1+b1
> >
> > $ zcat /usr/share/doc/$PACKAGE/changelog.Debian.gz | dpkg-parsechangelog
> > -l- | grep
On Saturday 30 January 2010, Ben Finney wrote:
> So, the version was upgraded to ‘1.2.1-1+b1’, but there latest
> entry in the changelog is still only ‘1.4.1-1’. There is no entry
> describing the changes in the latest release of the package, as
> specified in policy §4.4.
>
> How does this occ
Goswin von Brederlow writes:
> The +b suffix on the version is indeed a binNMU. That means that the
> source was recompiled without any changes to the source. The changelog
> is the one from the source so it only has the source version as top
> entry.
binNMUs also modify the changelog in the pac
Ben Finney writes:
> Howdy all,
>
> Occasionally I notice a package upgrade on a host, but the Debian
> changelog for the package has no corresponding changelog entry for the
> new release.
>
> The most recent example is âmercurialâ:
>
> =
> $ PACKAGE=mercurial
>
> $ dpkg-query -W -f 'Ver
On Sat, 2010-01-30 at 10:20 +1100, Ben Finney wrote:
> Occasionally I notice a package upgrade on a host, but the Debian
> changelog for the package has no corresponding changelog entry for the
> new release.
>
> The most recent example is ‘mercurial’:
>
> =
> $ PACKAGE=mercurial
>
> $ dpkg-
Howdy all,
Occasionally I notice a package upgrade on a host, but the Debian
changelog for the package has no corresponding changelog entry for the
new release.
The most recent example is ‘mercurial’:
=
$ PACKAGE=mercurial
$ dpkg-query -W -f 'Version: ${Version}\n' $PACKAGE
Version: 1.4.1-1
11 matches
Mail list logo
