Your message dated Sun, 19 Nov 2017 20:51:24 +0100
with message-id <20171119195124.fijgcrjfacnvd...@angband.pl>
and subject line Re: Bug#880411: Subject: RFS: sqldeveloper-package/0.4.4
has caused the Debian Bug report #880411,
regarding RFS: sqldeveloper-package/0.4.4
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.)
--
880411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "sqldeveloper-package"
* Package name : sqldeveloper-package
Version : 0.4.4
Upstream Author : Lazarus Long <lazarus.l...@sapo.pt>
* URL : <https://lazarusllong.github.io/sqldeveloper-package/>
* License : GPL-3+
Section : misc
It builds this binary package:
sqldeveloper-package - Oracle SQL Developer Debian package builder
To access further information about this package, please visit the
following URL:
<https://mentors.debian.net/package/sqldeveloper-package>
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/contrib/s/sqldeveloper-package/sqldeveloper-package_0.4.1.dsc
More information about sqldeveloper-package can be obtained from
<https://lazarusllong.github.io/sqldeveloper-package/>.
Changes since the last upload:
sqldeveloper-package (0.4.4) unstable; urgency=low
* Removed debian/watch script, it doesn't belong in a native package
-- Lazarus Long <lazarus.l...@sapo.pt> Tue, 31 Oct 2017 09:04:05 +0000
sqldeveloper-package (0.4.3) unstable; urgency=low
* Changed author/maintainer email address
* Generated new GPG key
* Added debian/watch script
-- Lazarus Long <lazarus.l...@sapo.pt> Mon, 30 Oct 2017 17:10:01 +0000
sqldeveloper-package (0.4.2) unstable; urgency=low
* Fixed lintian warning no-dep5-copyright
* Clarified the JDK requirements for all SQL Developer version families
-- Lazarus Long <lazarus.l...@bigfoot.com> Mon, 30 Oct 2017 04:13:57 +0000
sqldeveloper-package (0.4.1) unstable; urgency=high
* Fixed a flaw in the added logic to remove a stale JVM path from
configuration, the way the path is stored has changed from v4.x
onward (Closes: #693798)
(Reported by Steven Post)
* Several small fixes and improvements:
- Fixed the JDK requirements for SQL Developer v4.0
- Added image thumbnails databases to the list of cruft to remove
* Fixed lintian warning windows-thumbnail-database-in-package
* (Re-)Tested against v3.x release family of SQL Developer
-- Lazarus Long <lazarus.l...@bigfoot.com> Sun, 29 Oct 2017 21:38:19 +0000
sqldeveloper-package (0.4.0) unstable; urgency=high
* Addressed all correctable issues and bugs:
- Separated target from options and disabled check for original file in
package build (Closes: #868673)
(Reported and patch by Phil Morrell)
- Added logic to wrapper script to remove a stale JVM path from
configuration
(Reported by Steven Post)
* Fixed lintian warnings:
- ancient-standards-version
- package-uses-deprecated-debhelper-compat-version
- spelling-error-in-description
* Modified make-sqldeveloper-package to fix lintian warnings and errors:
- command-in-menu-file-and-desktop-file
- desktop-mime-but-no-exec-code
- extra-license-file
- new-package-should-close-itp-bug
- priority-extra-is-replaced-by-priority-optional
* Several small fixes and improvements:
- Simplified debian/rules since dh_strip_nondeterminism was heavilly
impacting build time by make-sqldeveloper-package
- Added 64-bit foreign DLLs to the list of cruft to remove
- Moved demo files to documentation structure
- Introduced lintian overrides for warnings out of our control:
- classpath-contains-relative-path
- codeless-jar
* New homepage for the package
* Updated documentation regarding compatible JDKs
* Tested against v4.x and v17.x release families of SQL Developer
* Verified compliancy with Standards-Version: 4.1.1
* Bumped version to reflect functionality
-- Lazarus Long <lazarus.l...@bigfoot.com> Sun, 29 Oct 2017 14:41:27 +0000
sqldeveloper-package (0.3.0) unstable; urgency=low
* Addressed all reported issues and bugs:
- Included debhelper on the build dependency list (LP: #588458)
(Reported by Seth Rosenblum)
- Replaced dh options with overrides (LP: #998258)
(Reported by Christian Loos)
* Several small fixes and improvements:
- Fixed an unknown parameter passed to trap when in debug mode
- Strengthened trap exit handling
- (Re-)Corrected an unescaped '$' in OTN license text introduced in the
previous version
* New homepage for the package
* Updated documentation regarding compatible JDKs
* Solved Debian QA warnings:
- Converted source format to 3.0 (native)
- Added Homepage to debian/control
* Changed the source compression format to xz
* Verified compliancy with Standards-Version: 3.9.3
* Bumped version to reflect functionality
-- Lazarus Long <lazarus.l...@bigfoot.com> Mon, 19 Nov 2012 18:58:16 +0000
Regards,
--
Lazarus Long
--- End Message ---
--- Begin Message ---
On Sun, Nov 19, 2017 at 04:55:42AM +0000, Lazarus Long wrote:
> The NMU is for a version from Nov 2012. After that I've had 0.3.0 for over
> 5 years before the specific bug has been created.
>
> The bug was fixed in version 0.4.0 (where one can find it's
> acknowledgement). I'm not sure if or how my log should or could include the
> NMU entry. If I put it in version order the patch is removed in the
> immediate version and the NMU is 5 years newer than the following version,
> if I put it in date order the NMU version is out of sequence and impossible
> to patch in-between the previous and the following ones.
>
> The fact is that the NMU became a fork of an older version, that is out of,
> and irrelevant for, my timeline.
Well, the history not having a record of a previous upload will confuse bug
version tracking. I think that, barring a manual intervention of setting a
"fixed" version in the bug that's a part of its current version history,
the bug will never go away.
But I'm not sure what will happen. If you prefer a history that represents
your development accurately, rather than the history of uploads, let's see
how it goes.
Uploaded as-is, for science.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out,
⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the
⠈⠳⣄⠀⠀⠀⠀ sky. Your cat demands food. The priority should be obvious...
--- End Message ---