Bug#910161: marked as done (RFS: xbase64/3.1.2-13)
Your message dated Sun, 7 Oct 2018 15:31:49 +0200
with message-id <20181007133149.5kkl7dxrmxy7sniw@angband.pl>
and subject line uploaded
has caused the Debian Bug report #910161,
regarding RFS: xbase64/3.1.2-13
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 owner@bugs.debian.org
immediately.)
--
910161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910161
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xbase64"
Package name : xbase64
Version : 3.1.2-13
Upstream Author : Gary A. Kunkel <gkunkel@zhsac.com>
URL : https://sourceforge.net/projects/xdb/
License : LGPL-2.1+, GPL-2+,GPL-3.0+
Section : libs
It builds those binary packages:
libxbase64-1 - xbase compatible C++ class library (shared libraries)
libxbase64-bin - xbase compatible C++ class library (utilities)
libxbase64-dev - xbase compatible C++ class library (development files)
libxbase64-doc - xbase compatible C++ class library (documentation)
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/xbase64
Alternatively, one can download the package with dget using this
command:
dget -x https://mentors.debian.net/debian/pool/main/x/xbase64/xbase64_3.1.2-13.dsc
or
git https://jff.email/cgit/xbase64.git/?h=release%2Fdebian%2F3.1.2-13
Changes since the last upload:
* Change to my new mail address:
- debian/control,
- debian/copyright
* Migrate to debhelper 11:
- Change debian/compat to 11.
- Bump minimum debhelper version in debian/control to >= 11.
- Remove obsolate dh_autoreconf.
* Declare compliance with Debian Policy 4.2.1 (No changes needed).
* Add new README.source to explain the branching model used.
* New debian/source/lintian-overrides.
* debian/patches/0120-fix-types-include.diff:
- Fix typo.
* debian/control:
- Switch Vcs-* to new location.
* debian/copyright:
- Use secure copyright format URI.
- Change years for me.
* debian/watch:
- Use secure URI.
Regards,
Jörg Frings-Fürst
- --
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56
Old pgp Key: BE581B6E (revoked since 2014-12-31).
Jörg Frings-Fürst
D-54470 Lieser
git: https://jff.email/cgit/
Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst
My wish list:
- Please send me a picture from the nature at your home.
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAlu0nzQACgkQCfifPIyh
0l07dA//VG6MJpKm9HEzsDPMyDiJH4gIixXOEop9g3PFVFknvw/v7lcQxvGQ4SUp
XlPDMFjq7sxQhf1WcYYTn7Efsk5Wv8fOYc0dMOAIp0D96U0EWraDfQuQupouND4F
M16Wwwd4DTHWcr0AgjVOBL65XSKtE0cSvMkThOSJPZKGOO6OvseIJ1bu0qJjXLLy
XOOGeFmIf0HavCH2v6rr720tGsoq1utG+Zzs1rVJtepAebfJjTJOZyK2raN4DXYw
5o8nLCe9AQLAnSpQqkZG37AKFxHYC5b5mwwDiM2D+Ur2/SfByPmGsPTOWsSxDovt
jqnDXOaz9FQmazxLu12aBe5AEQn5BLFJfzwGusAq8Lwz3IjN6cluMsy6HJfZsczE
6+JzPAW7RCnp4RVrW2Ubapihm9cOE1c0C5xkRxWHEBwUi/n9W7MmgZNC+vsaIwgZ
4CgN3qLNp1bykSKJigQYZ1ltVFB86rjRPP2wNwHeYo13L1IahhfNttJP+bRfeKZO
TOvaAm/wQRWeG2G5JdI5A6iKynUbsOkhTNGB3MatTECPgtK9mU3u0vUjBICF+RHk
RGZwztyAi/FRe8JOrKDnUajpCL51xVrY8Z0ZzMbnOACTuzgrtq5nwQp04UWpArng
NNsy08QBkpQdwEvhmSYZe0bXiKcSrbKc/qPTDE47/W2IE7F0ZBY=
=FrrM
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Sorry for this batched clossage, but I'm doing this on the go. All of these
packages have been uploaded.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ 10 people enter a bar: 1 who understands binary,
⢿⡄⠘⠷⠚⠋⠀ 1 who doesn't, D who prefer to write it as hex,
⠈⠳⣄⠀⠀⠀⠀ and 1 who narrowly avoided an off-by-one error.
--- End Message ---
Reply to: