Hello,
I assume this topic is not specific to one package but to the whole
python packaging universe.
There is "backintime" which unittests do write to $HOME. I'm one of the
new upstream maintainers and know that this isn't a good idea. It will
take time to fix this.
About that problem ther
Hello,
I couldn't find a mailing list specific to the Bug Tracking System.
In the bugs summary list for a specific package I can find
"Unclassified" bugs. But what is "Unclassified"?
Looking into other (not "Unclassified") bugs all have a "severity", some
are "confirmed" some not. So a missi
Hello,
I try to understand a problem with the Bug Tracking System. I tried to
merge two bugs because one is a duplicate. I send to control@
merge 985631 985256
I also tried the other way around switching the numbers.
But I got back that message that I don't understand. The link to the
u
On 29.03.2023 10:05, c.bu...@posteo.jp wrote:
Hi,
Bug #985631 [backintime-qt] backintime-qt: for volumes mounted on
demand, exiting backupintime-qt during the backup fails
Unable to merge bugs because:
forwarded of #985256 is '' not
'https://github.com/bit-team/backintime/issues/724'
Failed to
Dear Hilmar,
thanks for the reply.
Am 29.03.2023 10:33 schrieb preusse:
Do, what it says: the forwarded value must be equal for both bugs.
The system should do what I say: merge. :D
Looking into the BTS's own bug tracker it seems it has no effect when
opening a bug report about that.
On Wed, Mar 29, 2023 at 08:42:02AM +, c.bu...@posteo.jp wrote:
> > Do, what it says: the forwarded value must be equal for both bugs.
>
> The system should do what I say: merge. :D
That's not what the docs for the command say, please read them before
using the command.
And the command for "do
On Wed, Mar 29, 2023 at 08:02:56AM +, c.bu...@posteo.jp wrote:
> Hello,
>
> I couldn't find a mailing list specific to the Bug Tracking System.
Then please use debian-mentors@ or debian-devel@, not debian-python@.
> In the bugs summary list for a specific package I can find "Unclassified"
> b
On Wed, Mar 29, 2023 at 07:52:35AM +, c.bu...@posteo.jp wrote:
> I assume this topic is not specific to one package but to the whole python
> packaging universe.
>
> There is "backintime" which unittests do write to $HOME. I'm one of the new
> upstream maintainers and know that this isn't a go
Thanks for your reply.
Am 29.03.2023 11:35 schrieb Andrey Rakhmatullin:
One example is the backintime package
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=backintime
(I don't see the word "Unclassified" on that page)
Yes it is gone. Bug is closed or modified. Can't figur
Dear Andrey,
thank you for the reply.
Am 29.03.2023 11:40 schrieb Andrey Rakhmatullin:
The usual solution is AFAIK to set a temporary $HOME inside d/rules
though.
I was looking into
https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules
I don't see creation of a HOME or
Dear Andrey,
thank you for the reply.
Am 29.03.2023 11:40 schrieb Andrey Rakhmatullin:
The usual solution is AFAIK to set a temporary $HOME inside d/rules
though.
I was looking into
https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules
I don't see creation of a HOME or
On Wed, 29 Mar 2023 at 07:52:35 +, c.bu...@posteo.jp wrote:
> My question now is why newer version of this package are uploaded then? I
> couldn't find that the tests where deactivated. Maybe this "disabled on
> Debian auto-builders" is outdated and today it is possible to write to HOME
> durin
On Wed, Mar 29, 2023 at 10:03:31AM +, c.bu...@posteo.jp wrote:
> > The usual solution is AFAIK to set a temporary $HOME inside d/rules
> > though.
>
> I was looking into
> https://salsa.debian.org/jmw/pkg-backintime/-/blob/debian/debian/rules
>
> I don't see creation of a HOME or deactivation
13 matches
Mail list logo
