Carsten Schoenert writes:
> There is a private list there such information *can* be given, again,
> there is no rule that I need to do this.
> There are options if some other DD believes a package is needing an
> update, that process is called NMU (non maintainer upload). Or if you
> think
On Fri, Jul 28, 2023 at 11:08:38AM +, c.bu...@posteo.jp wrote:
> So it is possible to have packages in the debian repo that don't run any
> tests? I wasn't expecting this.
Many packages don't have tests at all. For many of them tests are not
possible or don't make much sense.
Dear Simon,
thanks for your thougths.
Am 28.07.2023 14:44 schrieb Simon McVittie:
The other angle this could be approached from is as an upstream
developer:
IMHO this is the only angle it should be approached from because it is
upstreams responsibility and Debian shouldn't waste resources
On Fri, 28 Jul 2023 at 11:53:29 +0200, Carsten Schoenert wrote:
> To quote from the BTS:
> ---%<---
> > In 1.2 upstream added a test suite. We should run it during build
> > (cd common && $(MAKE) test) but it needs to be able to write to the home
> > directory, which is disabled on Debian
On Fri, 28 Jul 2023 at 11:08:38 +, c.bu...@posteo.jp wrote:
> Am 28.07.2023 11:53 schrieb Carsten Schoenert:
> > I don't see any workaround and there is non needed. The bug issue is
> > about the not usable upstream test suite that would need to be called
> > through d/rules.
>
> Maybe this
Dear Carsten,
thanks for taking time and replying.
Am 28.07.2023 11:53 schrieb Carsten Schoenert:
you really should read the Social Contract/DFSG, the Debian policy and
the Developers reference a few times.
I'll do.
There is no rule that any DD or DM *must* do something in Debian, so
you
Hello Christian,
Am 27.07.23 um 21:56 schrieb c.bu...@posteo.jp:
Dear Carsten,
thanks for your feedback, your kind words and your patience with my
frustration. :)
I was thinking about what it is what bothers me here. It is not that
"the work" isn't done or bugs not fixed. It is that there is
Hello Christian,
if you want to improve my understanding of Debian's build environment
and learn more about it you should start to build yourself a package
locally in a Debian's build environment.
I went this way myself some years ago. We here at the list we can help
you to do it yourself.
Dear Mechtilde,
thanks for taking time to reply.
Am 28.07.2023 07:31 schrieb Mechtilde:
Did you try to build the last released version?
What are your problems to build backintime?
At upstream I have no problems to build and test it because I'm
upstream. ;)
But in my understanding the
Hello Christian,
a short comment to your log mail,
Am 27.07.23 um 21:56 schrieb c.bu...@posteo.jp:
Dear Carsten,
You might haven't read all ticket comments or I wasn't able to make my
question clear. The intention of my last comments to that ticket are to
understand how Jonathan worked
Dear Carsten,
thanks for your feedback, your kind words and your patience with my
frustration. :)
I was thinking about what it is what bothers me here. It is not that
"the work" isn't done or bugs not fixed. It is that there is no
reaction; zero; total silence.
The current Debian release is
Hello Christian,
Am 23.07.23 um 09:09 schrieb c.bu...@posteo.jp:
Hello,
On 2023-06-12 10:40 Jonathan Carter wrote:
Adding DPT to at least uploaders and having the package VCS in the
python-team namespace would probably be a good idea, but that's up to
Jonathan Wiltshire.
I have to state
Hello,
On 2023-06-12 10:40 Jonathan Carter wrote:
> Adding DPT to at least uploaders and having the package VCS in the
> python-team namespace would probably be a good idea, but that's up to
> Jonathan Wiltshire.
I have to state that after 5 weeks of waiting there is no reaction from
Jonathan
Hi
On 2023/06/12 09:51, c.bu...@posteo.jp wrote:
Currently Jonathan Wiltshire is official DM for that package.
I'm sure he makes a good job as DM. But other packages might have higher
priorities. He do not response in time and in some topics never. As
upstream maintainer I miss the dialog
Dear Python Team,
dear Jonathan,
first of all, please take my congratulations for the Debian 12 release
yesterday.
I'm member of the upstream maintenance team of "Back In Time" [1].
In short: I would like to switch its Debian Maintainer to "Debian Python
Team (DPT)".
I'm a little concerned
15 matches
Mail list logo
