Your message dated Wed, 2 Nov 2022 07:11:39 +0100
with message-id <69420bbd-8054-6de2-b9a7-49d3b6a7f...@xs4all.nl>
and subject line Re: Bug#1023310: josm: Debian version prompts for external
updates even though that would break Debian
has caused the Debian Bug report #1023310,
regarding josm: Debian version prompts for external updates even though that
would break Debian
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.)
--
1023310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: josm
Version: 0.0.svn18570+dfsg-1~bpo11+1
Severity: normal
X-Debbugs-Cc: alt.people.davidcal...@gmail.com
Dear Maintainer,
I ran JOSM and it said to update to 18583, which it said was the newest
stable version. That's not even in sid yet, much less stable-backports.
Something official Debian materials say to do is "don't break Debian",
"don't make a Frankendebian", "always install from apt if it's there",
and so on. I wonder if someone more familiar with Debian policies than
me can upgrade the severity to serious upon finding chapter and verse.
-- System Information:
Debian Release: 11.2
APT prefers stable-security
APT policy: (500, 'stable-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages josm depends on:
ii default-jre [java9-runtime] 2:1.11-72
ii fonts-noto 20201225-1
ii jmapviewer 2.16+dfsg-1~bpo11+1
ii libcommons-compress-java 1.20-1
ii libgettext-commons-java 0.9.6-6
ii openjdk-11-jre [java9-runtime] 11.0.16+8-1~deb11u1
ii openjfx 11.0.11+0-1
ii proj-data 7.2.1-1
Versions of packages josm recommends:
ii josm-l10n 0.0.svn18570+dfsg-1~bpo11+1
josm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 1023310 upstream wontfix
thanks
On 11/2/22 07:02, David Calman wrote:
I ran JOSM and it said to update to 18583
The upstream StartupPage does that:
https://josm.openstreetmap.de/wiki/StartupPage
, which it said was the newest
stable version. That's not even in sid yet, much less stable-backports.
It was uploaded this morning:
https://tracker.debian.org/pkg/josm
Something official Debian materials say to do is "don't break Debian",
"don't make a Frankendebian", "always install from apt if it's there",
and so on. I wonder if someone more familiar with Debian policies than
me can upgrade the severity to serious upon finding chapter and verse.
Just ignore the StartupPage message and wait for the backport to be
updated, or switch to josm-installer which uses the upstream JARs.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
