FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 01-29-2010, 10:41 PM
Stefan Fritsch
 
Default Package upgrade in Debian without corresponding changelog entry

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 occur? A conversation on IRC suggested it might be
> related to binNMU upgrades, but I don't know enough about that
> aspect to judge.
>

/usr/share/doc/mercurial is a symlink to mercurial-common. And
mercurial-common is arch all and not rebuilt for binNMUs. So maybe a
(minor) bug in mercurial?


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-29-2010, 11:05 PM
Goswin von Brederlow
 
Default Package upgrade in Debian without corresponding changelog entry

Ben Finney <ben+debian@benfinney.id.au> 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 'Version: ${Version}
' $PACKAGE
> Version: 1.4.1-1+b1
>
> $ zcat /usr/share/doc/$PACKAGE/changelog.Debian.gz | dpkg-parsechangelog -l- | grep '^Version:'
> Version: 1.4.1-1
> =====
>
> 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 occur? A conversation on IRC suggested it might be related
> to binNMU upgrades, but I don't know enough about that aspect to judge.
>
> How can this be addressed so that changelog entries always accompany the
> binary package for any new release of a package? Is this a bug in some
> part of the system, and if so, where?

The +b<N> 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.

Package: mercurial
Architecture: amd64
Version: 1.4.1-1+b1
Source: mercurial (1.4.1-1)

Notice that the package metadata says the source for the binary package
mercurial 1.4.1-1+b1 is the source package mercurial 1.4.1-1.

This is no different to packages where the binary has a different verion
(and/or name) than the source. For example:

% dpkg-query -W -f 'Version: ${Version}
' gcc
Version: 4:4.4.2-3

% zcat /usr/share/doc/gcc/changelog.Debian.gz | head --lines 1
gcc-defaults (1.92) unstable; urgency=low

Package: gcc
Architecture: amd64
Version: 4:4.4.2-3
Source: gcc-defaults (1.92)

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-29-2010, 11:19 PM
Russ Allbery
 
Default Package upgrade in Debian without corresponding changelog entry

Goswin von Brederlow <goswin-v-b@web.de> writes:

> The +b<N> 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 package under normal
circumstances. The only reason why it didn't in this case is because this
package symlinks the doc directory to another package, as previously
pointed out.

(Another reason to question the usefulness of symlinking doc directories.)

--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-29-2010, 11:37 PM
Ben Finney
 
Default Package upgrade in Debian without corresponding changelog entry

"Adam D. Barratt" <adam@adam-barratt.org.uk> writes:

> On Sat, 2010-01-30 at 10:20 +1100, Ben Finney wrote:
> > =====
> > $ PACKAGE=mercurial
> >
> > $ dpkg-query -W -f 'Version: ${Version}
' $PACKAGE
> > Version: 1.4.1-1+b1
> >
> > $ zcat /usr/share/doc/$PACKAGE/changelog.Debian.gz | dpkg-parsechangelog -l- | grep '^Version:'
> > Version: 1.4.1-1
> > =====
>
> mercurial's changelog is symlinked to mercurial-common's.

Stefan Fritsch <sf@sfritsch.de> writes:

> /usr/share/doc/mercurial is a symlink to mercurial-common. And
> mercurial-common is arch all and not rebuilt for binNMUs. So maybe a
> (minor) bug in mercurial?

I think it's a bug *somewhere*, yes. The user installing a package
should not need to know the details of how the changelog is managed; she
should be able to look at the changelog for the binary package and see
for any released version, whether binNMU or not, a corresponding
changelog entry.

--
“We have to go forth and crush every world view that doesn't |
` believe in tolerance and free speech.” —David Brin |
_o__) |
Ben Finney


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-30-2010, 07:11 AM
Vincent Danjean
 
Default Package upgrade in Debian without corresponding changelog entry

Hi,

On 30/01/2010 01:19, Russ Allbery wrote:

Goswin von Brederlow<goswin-v-b@web.de> writes:


The +b<N> 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 package under normal
circumstances. The only reason why it didn't in this case is because this
package symlinks the doc directory to another package, as previously
pointed out.

(Another reason to question the usefulness of symlinking doc directories.)


[taking my hat of mercurial maintainer]

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 of /usr/share/mercurial (with a strict dependency) was the
easiest way for me to do the work. If there is a consensus it is not a
good idea, I can try to change and symlink the content of
/usr/share/doc/mercurial-common into /usr/share/doc/mercurial (but
changelog.Debian.gz, copyright, ... of course) instead.

Regards,
Vincent

--
Vincent Danjean GPG key ID 0x9D025E87 vdanjean@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-30-2010, 11:13 AM
Roger Leigh
 
Default Package upgrade in Debian without corresponding changelog entry

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 of /usr/share/mercurial (with a strict dependency) was the
> easiest way for me to do the work. If there is a consensus it is not a
> good idea, I can try to change and symlink the content of
> /usr/share/doc/mercurial-common into /usr/share/doc/mercurial (but
> changelog.Debian.gz, copyright, ... of course) instead.

If they aren't from the same source package, and hence contain
the same changelog, you shouldn't be symlinking the doc directories.
I see no issue with symlinks to the /contents/ of the mercurial-
common doc directory, but this can't include the changelog,
copyright README.Debian etc.


Regards,
Roger

--
.'`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
 
Old 01-30-2010, 11:17 AM
Goswin von Brederlow
 
Default Package upgrade in Debian without corresponding changelog entry

Vincent Danjean <vdanjean.ml@free.fr> writes:

> Hi,
>
> On 30/01/2010 01:19, Russ Allbery wrote:
>> Goswin von Brederlow<goswin-v-b@web.de> writes:
>>
>>> The +b<N> 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 package under normal
>> circumstances. The only reason why it didn't in this case is because this
>> package symlinks the doc directory to another package, as previously
>> pointed out.
>>
>> (Another reason to question the usefulness of symlinking doc directories.)
>
> [taking my hat of mercurial maintainer]
>
> 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 of /usr/share/mercurial (with a strict dependency) was the
> easiest way for me to do the work. If there is a consensus it is not a
> good idea, I can try to change and symlink the content of
> /usr/share/doc/mercurial-common into /usr/share/doc/mercurial (but
> changelog.Debian.gz, copyright, ... of course) instead.
>
> Regards,
> Vincent

Another option: Have mercurial-common install its examples into
/usr/share/doc/mercurial/examples and have no symlinks.

MfG
Goswin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-30-2010, 11:34 AM
Serafeim Zanikolas
 
Default Package upgrade in Debian without corresponding changelog entry

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 release of the package, as
> > specified in policy §4.4.
> >
> > How does this occur? A conversation on IRC suggested it might be
> > related to binNMU upgrades, but I don't know enough about that
> > aspect to judge.
> >
>
> /usr/share/doc/mercurial is a symlink to mercurial-common. And
> mercurial-common is arch all and not rebuilt for binNMUs. So maybe a
> (minor) bug in mercurial?

See also #524191 (severity: serious, as it's a violation of policy 12.7).
The bottomonline is all binary-dep packages must have their own copy of the
changelog (and by extension their own /usr/share/doc dir).

--
debtags-organised WNPP bugs: http://members.hellug.gr/serzan/wnpp


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 01-30-2010, 11:50 AM
Vincent Danjean
 
Default Package upgrade in Debian without corresponding changelog entry

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 /usr/share/doc/mercurial

The symlink of /usr/share/mercurial (with a strict dependency) was the
easiest way for me to do the work. If there is a consensus it is not a
good idea, I can try to change and symlink the content of
/usr/share/doc/mercurial-common into /usr/share/doc/mercurial (but
changelog.Debian.gz, copyright, ... of course) instead.


If they aren't from the same source package[...]


They are, of courses.

Regards,
Vincent

--
Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble
Tlphone: +33 4 76 61 20 11 ENSIMAG - antenne de Montbonnot
Fax: +33 4 76 61 20 99 ZIRST 51, avenue Jean Kuntzmann
Email: Vincent.Danjean@imag.fr 38330 Montbonnot Saint Martin


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 11:58 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org