Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hi Jörg, I have fixed the old debian/changelog entry and uploaded the new version to DELAYED/7. Please feel free to tell me if I should delay it longer. The patch is attached. Cheers Jochen * Jochen Sprickerhof [2024-04-10 07:25]: Hi Jörg, is there anything I can help with to get libhx updated? (I agree with what Tobias said below.) Cheers Jochen * Tobias Frost [2024-03-17 20:22]: Control: tags -1 moreinfo On Sun, Mar 17, 2024 at 04:57:54PM +0100, Jörg Frings-Fürst wrote: tags 1065193 - moreinfo thanks Hi Tobias, Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: Hi Jörg, "debcheckout libhx" still gives me 4.17-1 as head. After looking at your repo, I think I should point you to DEP-14 as a recommended git layout for packaging. As the branch name indicates you are using per-package-revision branches: IMHO It makes little sense to have one branch per debian package version/revision; (I had a similiar discussion on vzlogger lately, so to avoid repetiions: #1064344#28) Please clarify how you want to manage the package in git, as this needs to be reflected in d/control's VCS-* fields correctly. (this is now blocking the upload.) I have been using Vincent Driessen's branching model and the corresponding git extension gitflow-avh for at least 7 years with Debian and for a long time at work. The default branch is master and development takes place in the develop branch. The release candidates are managed in the branch release. The extension debian/debian-version is used as a tag during the transfer. The master branch always contains the last published executable version to which the git tag in debian/control points. a> The procedure is described in the README.debian. ok, won't further argue about how to organize your git repo, but I can only tell the Debian perspective: It is breaking expectations as a debcheckout libhx does today NOT give me a state that represents the package in unstable. VCS-Git specifies where the (package) development is happening [1]. [1] Policy 5.6.26 But as I am not using the git repo as base for the sponsoring, lets put that topic to rest. (The current fields say the package is maintained in the default branch of your repo. I see a debian/ directory there, but that one is missing released (it is at 4.17-1, while unstable is at 4.19-1.1) The review is based on the .dsc, timestamped on mentors.d.n 2024-03-17 12:00 d/changelog is *STILL* changing history for the 4.19-1 changelog block. (This issue must be fixed before upload.) I think these were artifacts because my changes to the NMU were not adopted. Has been corrected. No it has not. I expect old changelog entries to be *identical* to the ones that have been uploaded, and they still are not, so I fear we are talking past each other. Please let me know what you think that you have fixed, so that we can spot the different expectations. For my perspective: This is the diff from debian/changelog from the current version in the archives and the dsc uploaded to mentors at 2024-03-17 14:45 You are still rewriting history (second hunk of this diff), this hunk should not exists. diff -Naur archive/libhx-4.19/debian/changelog mentors/libhx-4.23/debian/changelog --- archive/libhx-4.19/debian/changelog 2024-02-28 13:48:09.0 +0100 +++ mentors/libhx-4.23/debian/changelog 2024-03-17 15:23:31.0 +0100 @@ -1,3 +1,17 @@ +libhx (4.23-1) unstable; urgency=medium + + * New upstream release (Closes: #1064734). + * Add debian/.gitignore + * Remove not longer needed debian/libhx-dev.lintian-overrides. + * Fix debian/libhx32t64.lintian-overrides. + * debian/copyright: +- Add 2024 to myself. + * debian/control: +- Readd BD dpkg-dev (>= 1.22.5). + Thanks to Tobias Frost + + -- Jörg Frings-Fürst Sun, 17 Mar 2024 15:23:31 +0100 + libhx (4.19-1.1) unstable; urgency=medium * Non-maintainer upload. @@ -9,11 +23,8 @@ * New upstream release. - Refresh symbols files. - * Remove empty debian/libhx-dev.symbols. - * debian/rules: -- Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 libhx (4.14-1) unstable; urgency=medium From e82f0d623be16aad21807a7a5089fbfdbbd8ba05 Mon Sep 17 00:00:00 2001 From: Jochen Sprickerhof Date: Sun, 21 Apr 2024 09:03:28 +0200 Subject: [PATCH] Fix old debian/changelog entry --- debian/changelog | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index 5471467..e4c0c41 100644 --- a/debian/changelog +++ b/debian/changelog @@ -23,8 +23,11 @@ libhx (4.19-1) unstable; urgency=medium * New upstream release. - Refresh symbols files. + * Remove empty debian/libhx-dev.symbols. + * debian/rules: +- Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 + -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 libhx (4.14-1) unstable;
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hi Jörg, is there anything I can help with to get libhx updated? (I agree with what Tobias said below.) Cheers Jochen * Tobias Frost [2024-03-17 20:22]: Control: tags -1 moreinfo On Sun, Mar 17, 2024 at 04:57:54PM +0100, Jörg Frings-Fürst wrote: tags 1065193 - moreinfo thanks Hi Tobias, Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: > Hi Jörg, > > "debcheckout libhx" still gives me 4.17-1 as head. > > After looking at your repo, I think I should point you to DEP-14 > as a recommended git layout for packaging. > As the branch name indicates you are using per-package-revision > branches: > IMHO It makes little sense to have one branch per debian package > version/revision; (I had a similiar discussion on vzlogger lately, > so to avoid repetiions: #1064344#28) > > Please clarify how you want to manage the package in git, as > this needs to be reflected in d/control's VCS-* fields correctly. > (this is now blocking the upload.) I have been using Vincent Driessen's branching model and the corresponding git extension gitflow-avh for at least 7 years with Debian and for a long time at work. The default branch is master and development takes place in the develop branch. The release candidates are managed in the branch release. The extension debian/debian-version is used as a tag during the transfer. The master branch always contains the last published executable version to which the git tag in debian/control points. a> The procedure is described in the README.debian. ok, won't further argue about how to organize your git repo, but I can only tell the Debian perspective: It is breaking expectations as a debcheckout libhx does today NOT give me a state that represents the package in unstable. VCS-Git specifies where the (package) development is happening [1]. [1] Policy 5.6.26 But as I am not using the git repo as base for the sponsoring, lets put that topic to rest. > > (The current fields say the package is maintained in the default branch > of your repo. I see a debian/ directory there, but that one is missing > released (it is at 4.17-1, while unstable is at 4.19-1.1) > > The review is based on the .dsc, timestamped on mentors.d.n > 2024-03-17 12:00 > > d/changelog is *STILL* changing history for the 4.19-1 changelog > block. (This issue must be fixed before upload.) > I think these were artifacts because my changes to the NMU were not adopted. Has been corrected. No it has not. I expect old changelog entries to be *identical* to the ones that have been uploaded, and they still are not, so I fear we are talking past each other. Please let me know what you think that you have fixed, so that we can spot the different expectations. For my perspective: This is the diff from debian/changelog from the current version in the archives and the dsc uploaded to mentors at 2024-03-17 14:45 You are still rewriting history (second hunk of this diff), this hunk should not exists. diff -Naur archive/libhx-4.19/debian/changelog mentors/libhx-4.23/debian/changelog --- archive/libhx-4.19/debian/changelog 2024-02-28 13:48:09.0 +0100 +++ mentors/libhx-4.23/debian/changelog 2024-03-17 15:23:31.0 +0100 @@ -1,3 +1,17 @@ +libhx (4.23-1) unstable; urgency=medium + + * New upstream release (Closes: #1064734). + * Add debian/.gitignore + * Remove not longer needed debian/libhx-dev.lintian-overrides. + * Fix debian/libhx32t64.lintian-overrides. + * debian/copyright: +- Add 2024 to myself. + * debian/control: +- Readd BD dpkg-dev (>= 1.22.5). + Thanks to Tobias Frost + + -- Jörg Frings-Fürst Sun, 17 Mar 2024 15:23:31 +0100 + libhx (4.19-1.1) unstable; urgency=medium * Non-maintainer upload. @@ -9,11 +23,8 @@ * New upstream release. - Refresh symbols files. - * Remove empty debian/libhx-dev.symbols. - * debian/rules: -- Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 libhx (4.14-1) unstable; urgency=medium signature.asc Description: PGP signature
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Control: tags -1 moreinfo On Sun, Mar 17, 2024 at 04:57:54PM +0100, Jörg Frings-Fürst wrote: > tags 1065193 - moreinfo > thanks > > Hi Tobias, > > > > Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: > > Hi Jörg, > > > > "debcheckout libhx" still gives me 4.17-1 as head. > > > > After looking at your repo, I think I should point you to DEP-14 > > as a recommended git layout for packaging. > > As the branch name indicates you are using per-package-revision > > branches: > > IMHO It makes little sense to have one branch per debian package > > version/revision; (I had a similiar discussion on vzlogger lately, > > so to avoid repetiions: #1064344#28) > > > > Please clarify how you want to manage the package in git, as > > this needs to be reflected in d/control's VCS-* fields correctly. > > (this is now blocking the upload.) > > I have been using Vincent Driessen's branching model and the corresponding git > extension gitflow-avh for at least 7 years with Debian and for a long time at > work. > > The default branch is master and development takes place in the develop > branch. > > The release candidates are managed in the branch release. The extension > debian/debian-version is used as a tag during the transfer. > > The master branch always contains the last published executable version to > which > the git tag in debian/control points. > a> The procedure is described in the README.debian. ok, won't further argue about how to organize your git repo, but I can only tell the Debian perspective: It is breaking expectations as a debcheckout libhx does today NOT give me a state that represents the package in unstable. VCS-Git specifies where the (package) development is happening [1]. [1] Policy 5.6.26 But as I am not using the git repo as base for the sponsoring, lets put that topic to rest. > > > > (The current fields say the package is maintained in the default branch > > of your repo. I see a debian/ directory there, but that one is missing > > released (it is at 4.17-1, while unstable is at 4.19-1.1) > > > > The review is based on the .dsc, timestamped on mentors.d.n > > 2024-03-17 12:00 > > > > d/changelog is *STILL* changing history for the 4.19-1 changelog > > block. (This issue must be fixed before upload.) > > > > I think these were artifacts because my changes to the NMU were not adopted. > Has > been corrected. No it has not. I expect old changelog entries to be *identical* to the ones that have been uploaded, and they still are not, so I fear we are talking past each other. Please let me know what you think that you have fixed, so that we can spot the different expectations. For my perspective: This is the diff from debian/changelog from the current version in the archives and the dsc uploaded to mentors at 2024-03-17 14:45 You are still rewriting history (second hunk of this diff), this hunk should not exists. diff -Naur archive/libhx-4.19/debian/changelog mentors/libhx-4.23/debian/changelog --- archive/libhx-4.19/debian/changelog 2024-02-28 13:48:09.0 +0100 +++ mentors/libhx-4.23/debian/changelog 2024-03-17 15:23:31.0 +0100 @@ -1,3 +1,17 @@ +libhx (4.23-1) unstable; urgency=medium + + * New upstream release (Closes: #1064734). + * Add debian/.gitignore + * Remove not longer needed debian/libhx-dev.lintian-overrides. + * Fix debian/libhx32t64.lintian-overrides. + * debian/copyright: +- Add 2024 to myself. + * debian/control: +- Readd BD dpkg-dev (>= 1.22.5). + Thanks to Tobias Frost + + -- Jörg Frings-Fürst Sun, 17 Mar 2024 15:23:31 +0100 + libhx (4.19-1.1) unstable; urgency=medium * Non-maintainer upload. @@ -9,11 +23,8 @@ * New upstream release. - Refresh symbols files. - * Remove empty debian/libhx-dev.symbols. - * debian/rules: -- Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 libhx (4.14-1) unstable; urgency=medium
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
tags 1065193 - moreinfo thanks Hi Tobias, Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: > Hi Jörg, > > "debcheckout libhx" still gives me 4.17-1 as head. > > After looking at your repo, I think I should point you to DEP-14 > as a recommended git layout for packaging. > As the branch name indicates you are using per-package-revision > branches: > IMHO It makes little sense to have one branch per debian package > version/revision; (I had a similiar discussion on vzlogger lately, > so to avoid repetiions: #1064344#28) > > Please clarify how you want to manage the package in git, as > this needs to be reflected in d/control's VCS-* fields correctly. > (this is now blocking the upload.) I have been using Vincent Driessen's branching model and the corresponding git extension gitflow-avh for at least 7 years with Debian and for a long time at work. The default branch is master and development takes place in the develop branch. The release candidates are managed in the branch release. The extension debian/debian-version is used as a tag during the transfer. The master branch always contains the last published executable version to which the git tag in debian/control points. The procedure is described in the README.debian. > > (The current fields say the package is maintained in the default branch > of your repo. I see a debian/ directory there, but that one is missing > released (it is at 4.17-1, while unstable is at 4.19-1.1) > > The review is based on the .dsc, timestamped on mentors.d.n > 2024-03-17 12:00 > > d/changelog is *STILL* changing history for the 4.19-1 changelog > block. (This issue must be fixed before upload.) > I think these were artifacts because my changes to the NMU were not adopted. Has been corrected. > Thanks for re-adding the B-D on dpkg-dev. > > > So, please elaborate on the git issue (so that the correct VCS-* can be > confirmed or specified) , and fix the rewriting history part, and I'll upload > > Remove the moreinfo tag when ready. > > Cheers, > -- > tobi > [...] CU Jörg -- 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 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hi Jörg, "debcheckout libhx" still gives me 4.17-1 as head. After looking at your repo, I think I should point you to DEP-14 as a recommended git layout for packaging. As the branch name indicates you are using per-package-revision branches: IMHO It makes little sense to have one branch per debian package version/revision; (I had a similiar discussion on vzlogger lately, so to avoid repetiions: #1064344#28) Please clarify how you want to manage the package in git, as this needs to be reflected in d/control's VCS-* fields correctly. (this is now blocking the upload.) (The current fields say the package is maintained in the default branch of your repo. I see a debian/ directory there, but that one is missing released (it is at 4.17-1, while unstable is at 4.19-1.1) The review is based on the .dsc, timestamped on mentors.d.n 2024-03-17 12:00 d/changelog is *STILL* changing history for the 4.19-1 changelog block. (This issue must be fixed before upload.) Thanks for re-adding the B-D on dpkg-dev. So, please elaborate on the git issue (so that the correct VCS-* can be confirmed or specified) , and fix the rewriting history part, and I'll upload Remove the moreinfo tag when ready. Cheers, -- tobi On Sun, Mar 17, 2024 at 01:48:57PM +0100, Jörg Frings-Fürst wrote: > Hello Tobias, > > thanks for your review. > > > Am Donnerstag, dem 14.03.2024 um 17:53 +0100 schrieb Tobias Frost: > > Control: tags -1 moreinfo > > > > Hi Jörg, > > > > d/copyright: > > you are changing history: > > > > diff -Naur archive/libhx-4.19/debian/changelog > > new/libhx-4.23/debian/changelog > > (...) > > * debian/rules: > > - Remove build of libhx-dev.symbols. > > > > - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 > > + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 > > > > libhx (4.14-1) unstable; urgency=medium > > > > - you git repository seems to missing commits. a debcheckout libhx > > gives me 4.17-1 in d/changelog. > > Sorry, that's my mistake. > > > > > - please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the > > time_t transition requires it, > > > > Ok. I have add it. > > > -- > > tobi > > > > CU > Jörg > > -- > 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 > > > Jörg Frings-Fürst > D-54470 Lieser > > > git: https://git.jff.email/cgit/ > > Skype:jff-skype@jff.email > Jami: joergfringsfuerst > Telegram: @joergfringsfuerst > Matrix: @joergff:matrix.snct-gmbh.de > > My wish list: > - Please send me a picture from the nature at your home. > > > >
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hello Tobias, thanks for your review. Am Donnerstag, dem 14.03.2024 um 17:53 +0100 schrieb Tobias Frost: > Control: tags -1 moreinfo > > Hi Jörg, > > d/copyright: > you are changing history: > > diff -Naur archive/libhx-4.19/debian/changelog new/libhx-4.23/debian/changelog > (...) > * debian/rules: > - Remove build of libhx-dev.symbols. > > - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 > + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 > > libhx (4.14-1) unstable; urgency=medium > > - you git repository seems to missing commits. a debcheckout libhx > gives me 4.17-1 in d/changelog. Sorry, that's my mistake. > > - please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the > time_t transition requires it, > Ok. I have add it. > -- > tobi > CU Jörg -- 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 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
On Fri, Mar 01, 2024 at 06:50:24PM +0100, Jörg Frings-Fürst wrote: > libhx (4.23-1) experimental; urgency=medium Note: the dsc file targets unstable, not experimental. The review was using unstable as target. -- tobi
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Control: tags -1 moreinfo Hi Jörg, d/copyright: you are changing history: diff -Naur archive/libhx-4.19/debian/changelog new/libhx-4.23/debian/changelog (...) * debian/rules: - Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 libhx (4.14-1) unstable; urgency=medium - you git repository seems to missing commits. a debcheckout libhx gives me 4.17-1 in d/changelog. - please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the time_t transition requires it, -- tobi On Fri, Mar 01, 2024 at 06:50:24PM +0100, Jörg Frings-Fürst wrote: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "libhx": > > Package name : libhx > Version : 4.23-1 > Upstream contact : Jan Engelhardt > URL : https://inai.de/projects/libhx/ > License : LGPL-2.1+, WTFPL-2+, GPL-2+ > Vcs : https://git.jff.email/cgit/libhx.git > Section : libs > > The source builds the following binary packages: > > libhx32t64 - C library providing queue, tree, I/O and utility functions > libhx-dev - Development files for libhx > libhx-doc - Documentation files for libhx > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/libhx/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_4.23-1.dsc > > or from > > git https://git.jff.email/cgit/libhx.git?h=release%2Fdebian%2F4.23-1 > > > > Changes since the last upload: > > libhx (4.23-1) experimental; urgency=medium > . > * New upstream release (Closes: #1064734). > * Add debian/.gitignore > * Remove not longer needed debian/libhx-dev.lintian-overrides. > * Fix debian/libhx32t64.lintian-overrides. > * debian/copyright: > - Add 2024 to myself. > > > > CU > > Jörg > > > -- > 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 > > > Jörg Frings-Fürst > D-54470 Lieser > > > git: https://git.jff.email/cgit/ > > Skype:jff-skype@jff.email > Jami: joergfringsfuerst > Telegram: @joergfringsfuerst > Matrix: @joergff:matrix.snct-gmbh.de > > My wish list: > - Please send me a picture from the nature at your home. > > > >
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "libhx": Package name : libhx Version : 4.23-1 Upstream contact : Jan Engelhardt URL : https://inai.de/projects/libhx/ License : LGPL-2.1+, WTFPL-2+, GPL-2+ Vcs : https://git.jff.email/cgit/libhx.git Section : libs The source builds the following binary packages: libhx32t64 - C library providing queue, tree, I/O and utility functions libhx-dev - Development files for libhx libhx-doc - Documentation files for libhx To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libhx/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_4.23-1.dsc or from git https://git.jff.email/cgit/libhx.git?h=release%2Fdebian%2F4.23-1 Changes since the last upload: libhx (4.23-1) experimental; urgency=medium . * New upstream release (Closes: #1064734). * Add debian/.gitignore * Remove not longer needed debian/libhx-dev.lintian-overrides. * Fix debian/libhx32t64.lintian-overrides. * debian/copyright: - Add 2024 to myself. CU Jörg -- 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 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
