fteproxy is marked for autoremoval from testing

[Debian testing autoremoval watch]

fteproxy 0.2.19-3 is marked for autoremoval from testing on 2018-09-26

It (build-)depends on packages with these RC bugs:
906041: python-fte: python dependencies are missing

Processed: severity of 816733 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 816733 normal
Bug #816733 [tracker.debian.org] tracker.d.o: doesn't understand RFS bugs
Severity set to 'normal' from 'wishlist'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
816733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#816733: PTS doesn't understand RFS bugs

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 tracker.d.o: doesn't understand RFS bugs
Bug #816733 [tracker.debian.org] tracker.debian.org: please show sponsorship 
requests
Changed Bug title to 'tracker.d.o: doesn't understand RFS bugs' from 
'tracker.debian.org: please show sponsorship requests'.

-- 
816733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#816733: PTS doesn't understand RFS bugs

[Paul Wise]

Control: retitle -1 tracker.d.o: doesn't understand RFS bugs


Control: severity -1 normal

On Tue, Aug 21, 2018 at 3:42 AM, Raphael Hertzog wrote:
> On Fri, 04 Mar 2016, Jakub Wilk wrote:
>> https://packages.qa.debian.org/o/openfst.html says:
>> > The WNPP database contains an entry for this package, but it is unclear
>> > what kind of entry it is. This is probably an error. Please see bug
>> > number #814852 for more information.
>>
>> But #814852 is not a wnpp bug, it's an RFS.
>
> I think this bug does not apply to tracker.debian.org.

Actually, it does (although the summary message is less severe):

RFS: The WNPP database contains an entry for this package.

The full details message is more like the PTS message:

The WNPP database contains an entry for this package, but it is
unclear what kind of entry it is. This is probably an error. Please
see bug number #906721 for more information.

For example:

https://tracker.debian.org/pkg/plowshare

> Thus changing this bug into a wishlist to actually show the sponsorship 
> requests.

They are already shown, see above.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#906778: guile-gnome-platform: FTBFS in buster/sid (makeinfo: command not found)

[Santiago Vila]

Package: src:guile-gnome-platform
Version: 2.16.4-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
set -e;   mv ./build-aux/config.guess ./build-aux/config.guess.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.guess ./build-aux/config.guess;
set -e;   mv ./build-aux/config.sub ./build-aux/config.sub.cdbs-orig; cp 
--remove-destination /usr/share/misc/config.sub ./build-aux/config.sub;
dh_autoreconf 
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: copying file 'build-aux/ltmain.sh'

[... snipped ...]

Making check in glib
make[4]: Entering directory '/<>/glib/doc/glib'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
rm -rf $backupdir && mkdir $backupdir && \
if (/bin/bash /<>/build-aux/missing makeinfo --version) >/dev/null 
2>&1; then \
  for f in guile-gnome-glib.info guile-gnome-glib.info-[0-9] 
guile-gnome-glib.info-[0-9][0-9] guile-gnome-glib.i[0-9] 
guile-gnome-glib.i[0-9][0-9]; do \
if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
cd "$am__cwd"; \
if /bin/bash /<>/build-aux/missing makeinfo   -I . \
 -o guile-gnome-glib.info guile-gnome-glib.texi; \
then \
  rc=0; \
  CDPATH="${ZSH_VERSION+.}:" && cd .; \
else \
  rc=$?; \
  CDPATH="${ZSH_VERSION+.}:" && cd . && \
  $restore $backupdir/* `echo "./guile-gnome-glib.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
/<>/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
 You should only need it if you modified a '.texi' file, or
 any other file indirectly affecting the aspect of the manual.
 You might want to install the Texinfo package:
 
 The spurious makeinfo call might also be the consequence of
 using a buggy 'make' (AIX, DU, IRIX), in which case you might
 want to install GNU make:
 
make[4]: *** [Makefile:470: guile-gnome-glib.info] Error 127
make[4]: Leaving directory '/<>/glib/doc/glib'
make[3]: *** [Makefile:399: check-recursive] Error 1
make[3]: Leaving directory '/<>/glib/doc'
make[2]: *** [Makefile:513: check-recursive] Error 1
make[2]: Leaving directory '/<>/glib'
make[1]: *** [Makefile:457: check-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:113: 
debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/guile-gnome-platform.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#904694: marked as done (tracker.debian.org: don't complain about outdated S-V for packages only in <= stable)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 21:51:57 +
with message-id <5b7b37fd77cc4_38e2b1bb614b0d467...@godard.mail>
and subject line Bug #904694 in tracker.debian.org fixed
has caused the Debian Bug report #904694,
regarding tracker.debian.org: don't complain about outdated S-V for packages 
only in <= stable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
904694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org

Hi,

https://tracker.debian.org/pkg/postgresql-9.6 reports both that the
package is "not in any development repository", and that "[t]he package
is severely out of date with respect to the Debian Policy".

It seems silly (and apparently confusing to at least some users) to
complain about the outdated S-V for a package that only exists in
(old)stable, where the package won't be tracking updates to Policy.

Regards,

Adam
--- End Message ---
--- Begin Message ---
Hello,

Bug #904694 in tracker.debian.org reported by you has been fixed in the Git 
repository.
You can see the commit message below, and you can check the diff of the fix at:

https://salsa.debian.org/qa/distro-tracker/commit/73eafc168ede50bc0e53c4cd36a23e8ad8ee8764


stdver_warnings: properly handle removal from default repository

The way I initially implemented items_extend_queryset() means that
we processed all repositories instead of only the default one. The
task was taking way too long and we failed to drop some items that
should have been dropped.

Closes: #904694



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904694--- End Message ---

Bug#895393: marked as done (tracker.debian.org thinks 3.9.8 is the latest standards version)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 21:51:57 +
with message-id <5b7b37fd842da_38e2b1bb614b0d467...@godard.mail>
and subject line Bug #895393 in tracker.debian.org fixed
has caused the Debian Bug report #895393,
regarding tracker.debian.org thinks 3.9.8 is the latest standards version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
895393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: normal

Dear Maintainer,

The old package tracker complains that my package is "severely out of
date", while the new one thinks it is up to date and doesn't complain
about anything.

Compare:

https://packages.qa.debian.org/b/bitlbee.html
https://tracker.debian.org/pkg/bitlbee

< kilobyte> looking at some other package, the tracker still thinks
3.9.8 is current
< pabs> IIRC the tracker code looks at the version of the debian-policy
package

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.13-1-ARCH (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Hello,

Bug #895393 in tracker.debian.org reported by you has been fixed in the Git 
repository.
You can see the commit message below, and you can check the diff of the fix at:

https://salsa.debian.org/qa/distro-tracker/commit/707995a1d8906b934dd7f419c97a654543f499f5


stdver_warnings: force full update when a new policy version is released

Closes: #895393



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895393--- End Message ---

Bug#906436: nis

[Michael Biebl]

On Mon, 20 Aug 2018 22:46:42 +0200 Thomas Lange
 wrote:
> 
> ypbind is started by /etc/init.d/nis which includes this:
> # Required-Start:   $network $portmap $remote_fs
> 
> There's not ypbind.service or any other .service file inside the nis
> package. Maybe this is a problem?

nis ships a SysV init script which is supposed to start all necessary
daemons.
Obviously it would be much better, if the individual daemons would have
a separate, native .service file, but that's a different issue.
The nis package would need a lot of love to be a properly maintained
package. It's imho at a pretty sad state atm.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#906436: nis

[Thomas Lange]

ypbind is started by /etc/init.d/nis which includes this:
# Required-Start:   $network $portmap $remote_fs

There's not ypbind.service or any other .service file inside the nis
package. Maybe this is a problem?

-- 
regards Thomas

Bug#816733: PTS doesn't understand RFS bugs

[Raphael Hertzog]

Control: severity -1 wishlist
Control: retitle -1 tracker.debian.org: please show sponsorship requests

On Fri, 04 Mar 2016, Jakub Wilk wrote:
> https://packages.qa.debian.org/o/openfst.html says:
> > The WNPP database contains an entry for this package, but it is unclear
> > what kind of entry it is. This is probably an error. Please see bug
> > number #814852 for more information.
> 
> But #814852 is not a wnpp bug, it's an RFS.

I think this bug does not apply to tracker.debian.org. Thus changing
this bug into a wishlist to actually show the sponsorship requests. Those
are RFS bugs filed against the sponsorship-requests package:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sponsorship-requests

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Processed: Re: Bug#816733: PTS doesn't understand RFS bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #816733 [tracker.debian.org] PTS doesn't understand RFS bugs
Severity set to 'wishlist' from 'normal'
> retitle -1 tracker.debian.org: please show sponsorship requests
Bug #816733 [tracker.debian.org] PTS doesn't understand RFS bugs
Changed Bug title to 'tracker.debian.org: please show sponsorship requests' 
from 'PTS doesn't understand RFS bugs'.

-- 
816733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#784164: marked as done (tracker.debian.org: Duplicated metadata files)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 21:15:21 +0200
with message-id <20180820191521.ga15...@home.ouaza.com>
and subject line Re: Bug#784164: tracker.debian.org: Duplicated metadata files
has caused the Debian Bug report #784164,
regarding tracker.debian.org: Duplicated metadata files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
784164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: normal

Since the reintroduction of squeeze, and the subsequent rebuild of the
site, there's now duplicated and strangely (temp) named metadata files
being used.

From  which links to:

 https://tracker.debian.org/media/packages/d/dpkg/changelog-1.15_1nypb7o.11
 https://tracker.debian.org/media/packages/d/dpkg/copyright-1.15_iKB32fL.11
 https://tracker.debian.org/media/packages/d/dpkg/rules-1.15_V6T5iW2.11
 https://tracker.debian.org/media/packages/d/dpkg/control-1.15_41mi0Cu.11

But the correct ones are available there as well.

 https://tracker.debian.org/media/packages/d/dpkg/changelog-1.15.11
 https://tracker.debian.org/media/packages/d/dpkg/copyright-1.15.11
 https://tracker.debian.org/media/packages/d/dpkg/rules-1.15.11
 https://tracker.debian.org/media/packages/d/dpkg/control-1.15.11

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Hi,

On Sun, 03 May 2015, Guillem Jover wrote:
> Since the reintroduction of squeeze, and the subsequent rebuild of the
> site, there's now duplicated and strangely (temp) named metadata files
> being used.
> 
> From  which links to:
>  https://tracker.debian.org/media/packages/d/dpkg/changelog-1.15_1nypb7o.11
> But the correct ones are available there as well.
>  https://tracker.debian.org/media/packages/d/dpkg/changelog-1.15.11

I just fixed this.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/--- End Message ---

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Michael Biebl]

On 8/20/18 14:40, Nuno Oliveira wrote:
> Hi Bertrand,
> 
> I got a similar behaviour. This is probably due to dropped
> NetworkManager support in the last package version by Michael Biebl.
> Presently I cannot
> run sucessfully a plain
> 
> /usr/sbin/ypbind
> 
> in a startup script, not even in /etc/rc.local. If this is a run after
> system startup, then nis starts normally, though.
>

Does ypbind need the network to be up before it can start?
If so, how do you configure your network (details please, including
configuration files.)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: severity of 902262 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 902262 normal
Bug #902262 [tracker.debian.org] tracker.debian.org: incorrect data for 
owncloud removal
Severity set to 'normal' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: closing 899405

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 899405
Bug #899405 [tracker.debian.org] tracker: Default documentation is not 
user-oriented
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
899405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899405: tracker: Default documentation is not user-oriented

[Raphael Hertzog]

Hi,

On Thu, 24 May 2018, Raphael Hertzog wrote:
> Definitely! This is now even more needed because we have a few interesting
> team-oriented features that really need to be documented.
> 
> I would like https://qa.pages.debian.net/distro-tracker/ to provide
> user-oriented documentation (as well as developer/contributor docs)
> so the plan is to merge what is in the developers reference
> into the distro-tracker doc, expand it, and then replace the section
> in the developer's reference with a link to the distro-tracker
> documentation.

I did that a while ago. Closing the bug. The documentation can always
be expanded of course.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#824899: marked as done (tracker.debian.org: broken non-Latin scripts support? (testing migrations section))

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 15:54:24 +0200
with message-id <20180820135424.ga9...@home.ouaza.com>
and subject line Re: Bug#824899: tracker.debian.org: broken non-Latin scripts 
support? (testing migrations section)
has caused the Debian Bug report #824899,
regarding tracker.debian.org: broken non-Latin scripts support? (testing 
migrations section)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
824899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: tracker.debian.org

Dear Maintainer,

perhaps it has somewhat broken non-Latin scripts support;
please look at the "testing migrations" section here:
https://tracker.debian.org/pkg/harfbuzz

(Screenshot attached for history).

--
Best wishes,
Bob
--- End Message ---
--- Begin Message ---
On Sat, 21 May 2016, Bob Bib wrote:
> Dear Maintainer,
> 
> perhaps it has somewhat broken non-Latin scripts support;
> please look at the "testing migrations" section here:
> https://tracker.debian.org/pkg/harfbuzz

This has been fixed in the mean time by using proper YAML input for
the excuses data shown there.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/--- End Message ---

Bug#809211: marked as done (tracker.debian.org: sqlite backend not usable)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 15:39:22 +0200
with message-id <20180820133922.ga8...@home.ouaza.com>
and subject line Re: Bug#809211: tracker.debian.org: sqlite backend not usable
has caused the Debian Bug report #809211,
regarding tracker.debian.org: sqlite backend not usable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
809211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tracker.debian.org
Severity: normal

I am trying to run tracker configured with debian repositories using the sqlite
backend, but several tasks are giving:

  OperationalError: too many columns in result set

Tasks that are frequently failing:

  UpdateRepositoriesTask
  UpdatePackageBugStats
  UpdateLintianStatsTask
  UpdateExcusesTask
  UpdateBuildLogCheckStats
  DebianWatchFileScannerUpdate
  UpdateSecurityIssuesTask
  UpdateUbuntuStatsTask
  UpdateWnppStatsTask

I have tried the following with little success:

  Use a small subset of repositories
  Recompile libsqlite with #define SQLITE_MAX_COLUMN 32767
  Hack the querysets like 
http://stackoverflow.com/questions/7106016/too-many-sql-variables-error-in-django-witih-sqlite3

I think sqlite does not scale and we should not recommend it, in the setting 
files:

  # If you want to run a development setup close to what's running on
  # tracker.debian.org, then uncomment the next two lines.
  from .debian import *
- from .db_sqlite import DATABASES
+ from .db_postgresql import DATABASES

and remove db_sqlite.py.

Note we have a warning in the documentation:

  Distro Tracker does not rely on any database specific features and as such 
should be
  able to run on top of any database server. The only possible known issue is 
when
  using sqlite3 which has a limit on the number of query parameters of 999 on
  some systems.

Cheers,
Christophe
--- End Message ---
--- Begin Message ---
Hi,

On Sat, 09 Jan 2016, Raphael Hertzog wrote:
> On Fri, 08 Jan 2016, Aymeric Augustin wrote:
> > I didn’t realize SQLITE_MAX_COLUMN would be the limit here.
> > 
> > Would you mind opening a ticket on https://code.djangoproject.com/?
> 
> Done: https://code.djangoproject.com/ticket/26063

This has been fixed a long time ago and the current version of Django that
we recommend does not have the problem. I'm still actively using sqlite
for development and it works fine.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/--- End Message ---

Bug#906436: confirm this bug

[Thomas Lange]

I can confirm this bug. I use a Debian NIS master (still on stretch)
but on a buster client, the nis service is not started during booting

# systemctl|grep nis says:

nis.service loaded active exited  LSB: Start NIS client and server daemons



# journalctl
buster nis[702]: Starting NIS services: ypbindbinding to YP 
server...failed (backgrounded).
buster systemd[1]: Started LSB: Start NIS client and server


But ypbind is not started. I can start it manually and then
everythings works. But it's not started when rebooting the machine.
-- 
regards Thomas

Bug#906436: 906436: nis: /etc/init.d/nis doesn't start ypbind, thus ypwhich timeouts

[Nuno Oliveira]

Hi Bertrand,

I got a similar behaviour. This is probably due to dropped NetworkManager 
support in the last package version by Michael Biebl. Presently I cannot

run sucessfully a plain

/usr/sbin/ypbind

in a startup script, not even in /etc/rc.local. If this is a run after 
system startup, then nis starts normally, though.


Regards,

Nuno.

Bug#906663: vcswatch: should not flag an UNRELEASED changelog entry as "ready for upload"

[Marc Haber]

On Mon, Aug 20, 2018 at 10:23:50AM +0200, Christoph Berg wrote:
> Re: Marc Haber 2018-08-19 <20180819185517.gl5...@torres.zugschlus.de>
> > I'm trying to avoid
> > 
> > Case 1: Somebody working on the branch, committing things and generating
> > new changelog entries for a version (x-y) that is already in the archive and
> > should therefore not be changed in the vcs
> 
> "dch" will take care of automatically incrementing the version number
> if the distribution is not UNRELEASED.

With a usual workflow, when the changelog is only adapted after a few
commits have accumulated (with dch --since), that will mean that the
changelog indicates that the git repo contains the released version. On
a second thought, I can probably live with that after adopting the view
that debian/changelog is only relevant in an uploaded package.

> > Case 2: Somebody working on the branch with a new version (x-y+1),
> > deploying test versions of the package that will not be overwritten by
> > later versions of the package (with the same version number) from the
> > archive, with the side effect that different but identically numbered
> > versions of the packages fly around.
> 
> I think the proper fix if that behavior is desired is
> 
> 1) tell dch to produce a .0 (I'd prefer ~unrel) version number (and
> have "dch -r" remove it) and

so I'd generate a changelog entry for x-y+1~unrel after uploading x-y?
that's indeed nicer than a .0 version.

> 2) only generate this changelog entry with the first change, i.e.
> leave git unmodified until the first change happens.

That would mean that all people committing would have to remember that.
I don't think that's realistic in a team maintained package.

> I don't think we can easily tell this case from various other edge
> cases apart in vcswatch. If there's a new changelog entry, or commits
> since the last tag, it needs to raise "NEW" or "UNREL".

Right.

Thanks for your explanations, they have really been enlightening to me.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#906663: vcswatch: should not flag an UNRELEASED changelog entry as "ready for upload"

[Christoph Berg]

Re: Marc Haber 2018-08-19 <20180819185517.gl5...@torres.zugschlus.de>
> I'm trying to avoid
> 
> Case 1: Somebody working on the branch, committing things and generating
> new changelog entries for a version (x-y) that is already in the archive and
> should therefore not be changed in the vcs

"dch" will take care of automatically incrementing the version number
if the distribution is not UNRELEASED.

> Case 2: Somebody working on the branch with a new version (x-y+1),
> deploying test versions of the package that will not be overwritten by
> later versions of the package (with the same version number) from the
> archive, with the side effect that different but identically numbered
> versions of the packages fly around.

I think the proper fix if that behavior is desired is

1) tell dch to produce a .0 (I'd prefer ~unrel) version number (and
have "dch -r" remove it) and

2) only generate this changelog entry with the first change, i.e.
leave git unmodified until the first change happens.

> Additionally, the tracker would
> begin to remind uploading those versions.

It should not nag about uploading, just remind that there's pending
changes. I think this is the major issue here. It's a maintainer
decision if pending changes warrant an upload, not an automated
system's one.

I don't think we can easily tell this case from various other edge
cases apart in vcswatch. If there's a new changelog entry, or commits
since the last tag, it needs to raise "NEW" or "UNREL".

Christoph