ANN: Back In Time 1.3.3 released
Hello, on behalf of the maintaining team I'm happy to announce the Back In Time release version 1.3.3 [1]. Germar also made that release available on Launchpad [2] via the testing-PPA ("ppa:bit-team/testing"). The Debian release is also on its way [3]. I hope it can happen before Debians Freeze phase starting on 23th January. Thanks to the Team, to Germar, all Contributors and Users. Kind Christian Buhtz [1] -- <https://github.com/bit-team/backintime/releases/tag/v1.3.3> [2] -- <https://launchpad.net/backintime/1.3/1.3.3> [3] -- <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027823>
Hi Christian and all, Thanks a lot for the heads-up and congratulations. It's great to hear that BiT has a new release. BTW, I've just read the Debian bug report. Does the Debian package have a maintainer or somebody should file an ITP (Intention to Package) for that and step-up as a maintainer for the package? Happy new year and cheers, Hakan On 4.01.2023 11:06, c.buhtz@posteo.jp wrote:
Hello,
on behalf of the maintaining team I'm happy to announce the Back In Time release version 1.3.3 [1].
Germar also made that release available on Launchpad [2] via the testing-PPA ("ppa:bit-team/testing").
The Debian release is also on its way [3]. I hope it can happen before Debians Freeze phase starting on 23th January.
Thanks to the Team, to Germar, all Contributors and Users.
Kind Christian Buhtz
[1] -- <https://github.com/bit-team/backintime/releases/tag/v1.3.3> [2] -- <https://launchpad.net/backintime/1.3/1.3.3> [3] -- <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027823> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org
Dear Hakan, On 2023-01-04 11:20 Hakan Bayındır <hakan@bayindir.org> wrote:
BTW, I've just read the Debian bug report. Does the Debian package have a maintainer or somebody should file an ITP (Intention to Package) for that and step-up as a maintainer for the package?
Thanks for asking back. An ITP and "step-up as a maintainer" are very different things in Debian. The Debianoids love their rules. :D No there is no need currently. And it is IMHO organizational and technical impossible for debian-unexperienced person preparing a package in that short time we have. I tried this in the past with much easier packages than BIT; and failed. I'm in contact with Fabio Fantoni [1] who is not officially connected to the Debian package but who did the last upload of Back In Time 1.3.2-0.1 [2]. Fabio is also an experienced Debian Maintainer for other packages. He is aware of the importance of the release because of the rsync-bug and try to test and prepare a package before the Debian freeze. He didn't promise but I'm optimistic. The official maintainer [3] for Back In Time didn't answer my mails about the new release. I'm sure he is quite busy with other packages in context of the near Debian Freeze. I was in contact with him in the past. The official uploader [4] respond to me but was clear about that he won't find the time to prepare a new package before the Debian Freeze. After the release process is done I will contact the Debian Python Team (DPT) [5] and discuss the situation. I assume it is best that the Team will take over the official maintainer ship. Then we have time and support to try and learn doing the packing our own. The time is important also to build trust in the Debian Team. Kind Christian [1] -- <https://udd.debian.org/dmd/?fantonifabio%40tiscali.it> [2] -- <https://tracker.debian.org/news/1320800/accepted-backintime-132-01-source-in...> [3] -- <https://udd.debian.org/dmd/?jmw%40debian.org> [4] -- <https://udd.debian.org/dmd/?fabi.wolff%40arcor.de> [5] -- <https://wiki.debian.org/Teams/PythonTeam>
Dear Christian, Thanks for clarifying. You’re right ITP and package adoption is very different things in Debian, I just messed up the wording, sorry. I assumed that BiT was in WNPP list because of the unmaintained time frame, and I’m glad that I was very wrong. As a former tech-lead of a (government supported) Debian derivative, I have some connection and experience with Debian, and I’m somewhat knowledgeable about how things work and done. I didn’t know that you were involved way more than me with Debian’s machinery and processes, and thought maybe I can help with packaging if the project needed some support. As I said, I was very wrong and I’m glad about it. Cheers, Hakan
On 4 Jan 2023, at 11:56, <c.buhtz@posteo.jp> <c.buhtz@posteo.jp> wrote:
Dear Hakan,
On 2023-01-04 11:20 Hakan Bayındır <hakan@bayindir.org> wrote:
BTW, I've just read the Debian bug report. Does the Debian package have a maintainer or somebody should file an ITP (Intention to Package) for that and step-up as a maintainer for the package?
Thanks for asking back. An ITP and "step-up as a maintainer" are very different things in Debian. The Debianoids love their rules. :D
No there is no need currently. And it is IMHO organizational and technical impossible for debian-unexperienced person preparing a package in that short time we have. I tried this in the past with much easier packages than BIT; and failed.
I'm in contact with Fabio Fantoni [1] who is not officially connected to the Debian package but who did the last upload of Back In Time 1.3.2-0.1 [2]. Fabio is also an experienced Debian Maintainer for other packages. He is aware of the importance of the release because of the rsync-bug and try to test and prepare a package before the Debian freeze. He didn't promise but I'm optimistic.
The official maintainer [3] for Back In Time didn't answer my mails about the new release. I'm sure he is quite busy with other packages in context of the near Debian Freeze. I was in contact with him in the past.
The official uploader [4] respond to me but was clear about that he won't find the time to prepare a new package before the Debian Freeze.
After the release process is done I will contact the Debian Python Team (DPT) [5] and discuss the situation. I assume it is best that the Team will take over the official maintainer ship. Then we have time and support to try and learn doing the packing our own. The time is important also to build trust in the Debian Team.
Kind Christian
[1] -- <https://udd.debian.org/dmd/?fantonifabio%40tiscali.it> [2] -- <https://tracker.debian.org/news/1320800/accepted-backintime-132-01-source-in...> [3] -- <https://udd.debian.org/dmd/?jmw%40debian.org> [4] -- <https://udd.debian.org/dmd/?fabi.wolff%40arcor.de> [5] -- <https://wiki.debian.org/Teams/PythonTeam> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org
Dear Hakan, thanks for the reply. On 2023-01-04 21:02 Hakan Bayındır <hakan@bayindir.org> wrote:
As a former tech-lead of a (government supported) Debian derivative, I have some connection and experience with Debian, and I’m somewhat knowledgeable about how things work and done.
Great to hear! In that case I assume you are way more experienced then me with Debian.
I didn’t know that you were involved way more than me with Debian’s machinery and processes, and thought maybe I can help with packaging if the project needed some support.
I just tried 3 or 4 times to start packaging something and failed. I can even tell you exactly what the problem was. :D It must be a mix of technological and organizational problems. I read a lot of wiki stuff and mailing list conversations. But not much more. Did you ever packed a Python project for Debian? Kind Christian
Hi Christian, Thanks for your answer. Let’s say I’ve interacted with people and developers and did what I can do. I’m no way an expert of mentat on the issue. These days I follow e-mail lists and contribute my views to issues which interests me. I have packaged “lintian-clean” packages in the past, but none of them were Python projects, hence I didn’t study Debian’s Python guidelines. However, I may take a look at them if there’s need for an helping hand. Cheers, Hakan
On 4 Jan 2023, at 23:22, c.buhtz@posteo.jp wrote:
Dear Hakan,
thanks for the reply.
On 2023-01-04 21:02 Hakan Bayındır <hakan@bayindir.org> wrote:
As a former tech-lead of a (government supported) Debian derivative, I have some connection and experience with Debian, and I’m somewhat knowledgeable about how things work and done.
Great to hear! In that case I assume you are way more experienced then me with Debian.
I didn’t know that you were involved way more than me with Debian’s machinery and processes, and thought maybe I can help with packaging if the project needed some support.
I just tried 3 or 4 times to start packaging something and failed. I can even tell you exactly what the problem was. :D It must be a mix of technological and organizational problems. I read a lot of wiki stuff and mailing list conversations. But not much more.
Did you ever packed a Python project for Debian?
Kind Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org
On Sun, Jan 8, 2023 at 9:36 AM Hakan Bayındır <hakan@bayindir.org> wrote:
Hi Christian,
Thanks for your answer. Let’s say I’ve interacted with people and developers and did what I can do. I’m no way an expert of mentat on the issue.
These days I follow e-mail lists and contribute my views to issues which interests me.
I have packaged “lintian-clean” packages in the past, but none of them were Python projects, hence I didn’t study Debian’s Python guidelines. However, I may take a look at them if there’s need for an helping hand.
Cheers,
Hakan
On 4 Jan 2023, at 23:22, c.buhtz@posteo.jp wrote:
Dear Hakan,
thanks for the reply.
On 2023-01-04 21:02 Hakan Bayındır <hakan@bayindir.org> wrote:
As a former tech-lead of a (government supported) Debian derivative, I have some connection and experience with Debian, and I’m somewhat knowledgeable about how things work and done.
Great to hear! In that case I assume you are way more experienced then me with Debian.
I didn’t know that you were involved way more than me with Debian’s machinery and processes, and thought maybe I can help with packaging if the project needed some support.
I just tried 3 or 4 times to start packaging something and failed. I can even tell you exactly what the problem was. :D It must be a mix of technological and organizational problems. I read a lot of wiki stuff and mailing list conversations. But not much more.
Did you ever packed a Python project for Debian?
Kind Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org
_______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: ritaarrington275@gmail.com
participants (3)
-
c.buhtz＠posteo.jp -
Hakan Bayındır -
Rita Arrington