Bug#1091714:

FYI. Back In Time now is prepared to use a local installed manual if it is available [1] at /usr/'share/doc/backintime-common/manual/index.html Otherwise it will fallback to the online manual [2]. [1] --

Bug#1101208:

Hello Fabio, My apologize there might be a missunderstanding. Am 11.04.2025 12:07 schrieb Fabio Fantoni: Hi, I wanted at least a test of the package to be done on Sid before requesting the upload to a DD, now I tried it and sent a request I used the tar.gz file (source tarball) available at up

Bug#1101208:

Hello, My apologize for asking again. I just want to be sure that I not might have misunderstood something? The freeze is near, but there is no upload yet. Is there any task that need to be done before? Regards, Christian

Bug#1102363: licensecheck: source formats: support excluding formats e.g. to only check for SPDX fields

Hello Jonas, thanks for asking back. Am 08.04.2025 12:44 schrieb Jonas Smedegaard: I have reframed it as an option (rather than a default goal): support excluding formats e.g. to only check for SPDX fields Do you agree that this covers the point of this issue? Kind of. Yes. ;) But I would

Bug#960665:

Hello, please let me add one additional item to this feature. Assuming SPDX license names are supported and the tool is able to specifically parse for SPDX-fields. In this case only that SPDX fields should be considered. Other licenses strings, e.g. in comments, should be ignored. See as a goo

Bug#1100900:

Hello Thomas, thanks for the reply and the details. I know and understand the technical details behind that topic. But that is not the point. My apologize but it seems I wasn't clear enough. The problem is that users (readers of the website) do get the message that a page's translation is out

Bug#1101208: /usr/bin/backintime: New upstream version 1.5.4 targeting Trixie

Am 04.04.2025 18:58 schrieb Fabio Fantoni: Il 04/04/2025 16:50, c.bu...@posteo.jp ha scritto: That bug seems for tool not supporting all SPDX licenses Yes, but it could work the other way around. Our use case could be considered whi

Bug#1101208: /usr/bin/backintime: New upstream version 1.5.4 targeting Trixie

Hello Fabio, Thank you for working on this. Me and the user appreciate this. Am 04.04.2025 15:43 schrieb Fabio Fantoni: noticed that updating d/copyright is a waste a lot of time, especially for the many false positives generated by the checks due to the citation of the main license of the progr

Bug#1101208: /usr/bin/backintime: New upstream version 1.5.4 targeting Trixie

Am 04.04.2025 16:45 schrieb c.bu...@posteo.jp: I would call this a bug in Debian's copyright checking tool then. The rule is simpel: If SPDX meta data is provided all other comments/headers should be ignored. Please let me know if you open a bug report about it, so I can subscribe it. This mig

Bug#1101208: /usr/bin/backintime: New upstream version 1.5.4 targeting Trixie

Hello Fabio Am 04.04.2025 16:23 schrieb Fabio Fantoni: I mean this text on comment on any file: # This file is part of the program "Back In Time" which is released under GNU # General Public License v2 (GPLv2). See file/folder LICENSE or go to #

Bug#1100964: apt: [INTL:pt_BR] Brazilian Portuguese translation

Hello, Am 21.03.2025 05:25 schrieb Rafael Fontenelle: Package: apt Version: 2.9.33 Severity: wishlist X-Debbugs-Cc: debian-l10n-portugu...@lists.debian.org Why not using the Weblate instance instead of poluting the mailing list and ticket system? See https://translate.debian.net/projects/po

Bug#1100900:

Hello Boyuan Yang, thanks for your reply. Am 23.03.2025 16:42 schrieb Boyuan Yang: I don't understand. What are you trying to do? Sorry, if this wasn't clear from my initial posting. All URLs I posted do have German translation. They are outdated and should be deleted because it harms the p

Bug#1100900:

Please allow me to add some more, because sometimes it is not easy for me to find the right words. Even if there are no resources (human, time, infrastructure, etc) someone need to make decisions. Being scared of decisions will harm the project. That is what maintaining is about. I am aware

Bug#1100900:

Hello Holger Am 24.03.2025 13:16 schrieb Holger Wansing: It's as always (or at least at many points) in Debian: the main issue is lack of manpower. I disagree on that point. Lack of human resources is one factor but not the main factor. But it is always an excuse for low quality. This is a FO

Bug#1100900:

Hello Holger, thanks for your reply on this topic. Am 23.03.2025 22:30 schrieb Holger Wansing: In that case, the user would see not many translated pages. English would be the usual language. That is not bad. It is good. No errors or indications of low quality. That is the goal and in the int

Bug#1100900:

I found more candidates. - https://www.debian.org/international/l10n/ddtp

Bug#1100900:

Please let me add additional German pages, also with the same request for removal: - https://www.debian.org/distrib/ - https://www.debian.org/releases/ - https://www.debian.org/releases/stable/ - https://www.debian.org/distrib/pre-installed - https://www.debian.org/CD/live/

Bug#1099172: No package name in BTS notification emails

Hello Don, thanks for the reply. Am 07.03.2025 00:57 schrieb Don Armstrong: What would a solution look like for you? [Note that modifying the subject and body of the message is problematic for many reasons including PGP and DKIM, so that's not an approach that can be used.] Subject or body, ye

Bug#1099172: No package name in BTS notification emails

Hello Chris, thanks for your eply and comments. Am 10.03.2025 10:35 schrieb Chris Hofstaedtler: Don already told you that what you want - modifying the subject is not technically possible: | What would a solution look like for you? [Note that modifying the | subject and body of the message is p

Bug#1099172: No package name in BTS notification emails

Hello Don, is your deny because of resources or do you really don't see the problem? A ticket/bugreport is not about resources. If you agree with the problem I do describe, leave the ticket open. We will think about what need to be done to solve it. No matter how much and long it does take.

Bug#1099172: No package name in BTS notification emails

Hello Don, thank you for your reply. Am 06.03.2025 05:01 schrieb Don Armstrong: They do have it in the X-Debian-PR-Package: header. For example, this message will have the following: X-Debian-PR-Package: bugs.debian.org But that is not human readable. Most of email clients do not show header

Bug#1099523:

This issue might be obsolete if the following two issues are fixed - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903272 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805378

Bug#903272:

From users perspective I do agree. That need to be a dependency. If this is fixed the bug #1099523 would be obsolete.

Bug#1099172: No package name in BTS notification emails

package: bugs.debian.org version: 1 Hello, the BTS system does communicate via emails. The problem is that the emails do not contain the relevant package name in subject or header. There is only the bug number. Being involved in several packages it is very hard to manage my bug emails without

Bug#1099171: Upgrade Debian Policy Standards Version to latest 4.7.2

Package: backintime Version: 1.5.3-1 Hello, I checked the difference between 4.7.0 and 4.7.2 and can't find something relevant to backintime. So it seems the version can be upgraded. btw: I am preparing the 1.5.4 release at upstream until 1th April to get included in upcoming Debian 13. Re

Bug#1087686:

Hello Fabio, the tracker now shows "1.5.4-rc2" as the latest upstream release. Is the fix pending or not working? Regards, Christian

Bug#1087686: Please package 1.5.3 before Ubuntu's Debian Import Freeze

Hello, upstream maintainer here. Ubuntus Debian Import Freeze is schedule for 20th February. I can surly tell that we won't release another version until this deadline. So please package the latest stable release, which is version 1.5.3 before that deadline. Thanks in advance, Christian Buh

Bug#1087582: backintime-qt: No set LC_TIME causes core dump

Hello Dave, thank you for reporting back. I don't see an error in your first post. I also don't understand why you think this is connected to LC_TIME. Are you sure? I would expect a Python exception instead of a core dump if BIT is not able to handle something with the locale setting. I saw

Bug#1087582: backintime-qt: No set LC_TIME causes core dump

Sorry, I meant "backintime-qt --debug" (with debug switch) of course.

Bug#1087582: backintime-qt: No set LC_TIME causes core dump

Hello Dave, upstream maintainer here. Thank you for reporting. Can you please run "backintime-qt" in your terminal and post the error output, too? Can you also please post the output of "locale". And for my understanding of your use case and environment: How does it come that LC_TIME is not

Bug#985260:

Upstream has several issues related to error reporting and cron error mails in context of user-callback script. I opened a new upstream ticket to reflect this specific bug ticket which is, to my understanding, about missing cron error mails in case of syntax errors in the user-callback script.

Bug#985257:

The upstream ticket #1331 does mix CLI and GUI issues. I realized this Debian ticket is bound to "common" (the CLI auf Back In Time). Because of that I vote to close this ticket with the next released because the issue is fixed. The example scripts now installed with "common".

Bug#985257:

Hello, upstream maintainer here. Please see this merged upstream PR The user-callback scripts not part of upstream repo, installed in "/usr/share/doc/backintime-common/user-callback-examples" (via make) and added to the user manual. The

Bug#985257:

Hello Franceso, Hello Jonathan, please see upstream PR #1899 The user-callback example scripts now installed (via make) in /usr/share/doc/backintime-common/user-callback-examples This might half fix your ticket. From the GUI this script

Bug#1078593: Acknowledgement (appstream: asv-summary-too-long Warning needs more details)

Please let me give additional information. Using "appstreamcli validate foobar.xml" on my local machine do not give me a warning about the length of that field. That confuses me much more. Which check command is used on the Debian Build Servers to generate that warning message? I opened a ti

Bug#1072474: backintime-common: "sshfs" should be "dep" instead of "sug"

It gives an error message dialog: "sshfs not found. Please install it (e.g. via "apt install sshfs")" I don't like that behavior. The GUI suggest that this functionality does exist, the user invest time in configuring it and near the end that error comes up. From a view point of usability it i

Bug#1072474: backintime-common: "sshfs" should be "dep" instead of "sug"

Am 22.07.2024 12:23 schrieb Fabio Fantoni: I think sshfs will be better in recommends instead depends as not all use remote backup on ssh. Have it as depends also make unable to uninstall it. Is this okay or is there some other reason why it's better to be in depends? SSH profiles is not an o

Bug#1037133:

Hello, I want to give an update of the situation because I migrated from Debian 11 to 12 (old-stable to stable). Stable now has ownCloud client 2.11.0. The described bug is still in this version. As upstream reported (https://github.com/owncloud/client/issues/10071) it might be fixed in 2.11

Bug#985257: Location of example scripts?

Hello, I do have a side question regarding to a possible solution of this issue. Back In Time (BIT) still have eight example callback scripts in a separate repo [1]. I plan to integrate them into the primary repo. But I ask myself where to install them when "./configure && make && sudo make i

Bug#1067029: closed by Thomas Lange (closing)

Dear Thomas, thanks for your your reply. My report was not about how to find donation info because I am looking for them. My intention was to improve Debian. I still recommend to add "Donations" as a term to the landing page. Doing a text search (CTRL+F) on that page for "Donation" has 0 hit

Bug#921239:

I support this wish because of the low quality German translation of the current man page. Translating it is waste of ressources. It is also not clear where the translation comes from Upstream do not provide translations. It is obvious that the German man page was translated by a machine or a

Bug#1062827: RFP: pydevtool -- CLI dev tools powered by pydoit

I checked upstream README.md. I have no clue what this is. Can someone explain please? Am 03.02.2024 18:05 schrieb dpars...@debian.org: Package: wnpp Severity: wishlist X-Debbugs-Cc: debian-pyt...@lists.debian.org Control: affects -1 src:scipy * Package name: pydevtool Version :

Bug#990343:

The problem is fixed in version 1.4.2.

Bug#1061974:

And also using "Package: backintime" do not work as expected. A message like this result in new bugs and not in closing an existing one. See this two examples: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061973 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061975 I am confused.

Bug#985260:

Dear Francesco, can you please have a look at the latest upstream release of Back In Time. Upstream assumes the problem is solved. Can you confirm this? Kind Christian

Bug#1037133:

Upstream responded to my questions about how this was fixed. They pointed to two PullRequests. https://github.com/owncloud/client/pull/10058 https://github.com/owncloud/client/pull/10065 My apologize. I'm not experienced enough to provide this as a patch to the current Debian version. Hope some

Bug#940319: [#940319 backintime] run test suite during build" : Request for maintainer feedback

Dear Jonathan, before investing my ressources into a solution can you please give me feedback about my proposal. Would this fit to your needs as DM and solve this bug? Kind Christian

Bug#1043046:

Dear Armin, maybe you can save the time generating all the diagnostic output I asked for. I'm not absolute sure about this point but based on my research it is not possible to configure Back In Time (BIT) that way that it run "Every Day" and at boot. "Every Day" do result in a crontab line li

Bug#1043046:

Please show the output of cat /etc/anacrontab Please also think hard about if you have configured something on your Debian 11 machines in the past? I'm not an expert in cron and anacron but in my understanding anacron do not start cron-jobs after their scheduled time (in hours in minutes).

Bug#1043046:

Dear Armin, thanks for reporting this. I'm member of the upstream maintainer team and not a Debian person. Please be aware that the current maintainer team is quit new to BIT and we are not yet familiar with all parts of the code and the behavior of BIT. But I'll try to assist you. I need to

Bug#1042428: qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)

Dear Sebastiaan, thanks for reporting back. Am 28.07.2023 10:00 schrieb Sebastiaan Couwenberg: You can get the tag description from lintian-explain-tags: I know that. The bug report wasn't a support question but a feature request. The infos about the meaning of the tags need to be part of

Bug#940319:

No response to my questions. I also asked on the debian python team mailing list. Without response I'll close the ticket on next iteration.

Bug#1033829:

Hello, upstream maintainer here. I just want to inform. I don't know how Debian would handle this usually. The problem is fixed in upstream but unreleased. And this NMU tries to backport the fix. The next Debian release will come in around 2 years. Until then upstream will do a new release.

Bug#963849:

Dear Felix, can you please try to reproduce the problem with a newer release. Debian 12 now has 1.3.3 on board which is the latest upstream version. This version is also available via an Ubuntu PPA or directly via git clone. Feel free to ask if you need further help with installing. Kind Chr

Bug#940319:

Hello, I try to learn here and that is why I asked. Do I get it right that the problem is that BIT do write and read from the users home folder. And that is not possible or not recommended on Debian's own build and test system. Am I right so far? To my knowledge as upstream maintainer this p

Bug#998105:

Do I see it correct that the commit was done but not yet uploaded? In result there should be a 1.3.3-5, right?

Bug#940319:

Dear Jonathan, what is the current situation about that issue? There where some new releases of Back In Time in Debian. Do you workaround that problem on your Debian side? And how? Kind Christian

Bug#859115:

Initial report based on a very old version of Back In Time. No feedback from reporter. Not able to reproduce.

Bug#985631:

Seems to be a duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985256

Bug#985256:

Looks like a duplicate of this to me: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985631

Bug#985258: closed by c.bu...@posteo.jp ()

Dear Francesco, thanks for the reply. Am 20.01.2023 12:53 schrieb Francesco Potortì: I understand that this is not an error hand has no consequences. However, for someone using the progrma, it gives the impression of inaccuracy, carelessness and possible unreliability, which is grave for a back

Bug#985260:

Tags: confirmed, upstream Upstream do confirm this bug. Which is related to the fact how Back In Time reacts on failing user-callback scripts. It seems that BIT doesn't exit with an error code. There is an upstream report about it: https://github.com/bit-team/backintime/issues/1053

Bug#998105:

Dear Sven, there is a new release 1.3.3 in "unstable" branch of Debian. Can you please try to reproduce the problem with that version and then report back. Thanks Christian

Bug#920050: Vote for close

#Close Close Can I send commands myself? I vote for closing this issue because it is not reproducible. Kind Christian

Bug#1025543: backintime: dependency on transitional policykit-1 package

Dear Simon, thanks for that report. I'm a member of the new upstream maintainer team. Do I understand it correct that this ticket is relevant only for the Debian Package Maintainer? Or can we as upstream do something about it? Kind Christian Buhtz

Bug#639537: backintime: messes with file access time when performing backups

Dear Julian, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream version. If you can reproduce it please open an Issue at upstream and link it here. It seems rsync specific but we would take care of it if it is

Bug#985355: backintime-qt: runtime error - reentrant call

Dear Francesco, I'm a member of the new upstream maintainer team. I assume this is reported at upstream https://github.com/bit-team/backintime/issues/1003 and also fixed there https://github.com/bit-team/backintime/pull/1380 Please try to reproduce that problem with the current upstream versio

Bug#985257: backintime-qt: no user callback example installed

Hello, I'm a member of the new upstream maintainer team. It is not a bug but a feature request. It is still tracked at upstream. So suggest to close that Debian bug report because it seems not distro specific. Kind Christian Buhtz

Bug#985260: backintime-qt: cron jobs error not mailed to user

Dear Francesco, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream version. If you can reproduce it please open an Issue at upstream and link it here. I suggest to close that Debian bug report because it seems

Bug#985256: backintime-qt: unmount at wrong time leads to core dump

Dear Francesco, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream version. If you can reproduce it please open an Issue at upstream and link it here. You still gave us the steps to reproduce. Can you please g

Bug#978735: backintime-qt: crash and failure to create SSH profile

Dear Sebastian, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream release. If you can reproduce it please open an Issue at upstream and link it here. I suggest to close that Debian bug report because it seems

Bug#973760: backintime-common: in backintime.py function smartRemoveList missing return value

Dear Greg, I'm a member of the new upstream maintainer team. Thank you for reporting this. I opened an upstream Issue for that https://github.com/bit-team/backintime/issues/1392 I suggest to close that Debian bug report because it seems not distro specific. Kind Christian Buhtz

Bug#920050: backintime-common: restoring file within a symbolic-linked directory removes symbolic link

Dear Jacob, I'm a member of the new upstream maintainer team. Your report sounds serious but is IMHO not distro specific. The bug is quit old. Please try to reproduce that problem with the current upstream release. If you can reproduce it please open an Issue at upstream and link it here. I

Bug#888914: backintime adds current directory to path?

Hello, I'm a member of the new upstream maintainer team. Please try to reproduce that problem with the current upstream release and report back. I suspect that the fix Fabian linked to does fix your problem. I suggest to close that Debian bug report because it seems not distro specific. K

Bug#866741: backintime-qt4: Freezes when pressing button "View last log"

Hello, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream release. If you can reproduce it please open an Issue at upstream and link it here. I suggest to close that Debian bug report because it seems not dist

Bug#859115: backintime-gnome: The 'backintime-gnome' blames Canberra, while 'backintime' blames keyring

Hello, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream release. If you can reproduce it please open an Issue at upstream and link it here. Based on your report I'm not sure if this is maybe Debian specific.

Bug#995257: backintime-qt4: does not check if backup directory exists (or drive is mounted)

Hello, I'm a member of the new upstream maintainer team. The bug is quit old. Please try to reproduce that problem with the current upstream release. If you can reproduce it please open an Issue at upstream and link it here. I suggest to close that Debian bug report because it is not distro

Bug#639537:

Thanks for the report. Can you reproduce that problem with current "stable" Debian version?

Bug#607758:

Thanks for the report. This is a feature request not a bug. And BIT does offer other ways (SSH, user-callback, ...) to access such devices. smb:// urls wont be supported in the future. Access that machine via SSH or mount the smb share via an user-callback script. Please close that report

Bug#985257:

Thank you very much for your report and your idea. We will take this into account at upstream. Currently there is no open Issue for that but it is on our internal TODO list. Please feel free to open an Issue for that: https://github.com/bit-team/backintime/issues I would suggest to close this

Bug#985631:

Not exactly the same but maybe related Issue on upstream: https://github.com/bit-team/backintime/issues/977

Bug#985355:

Reported on a "testing" Debian with a now outdated BIT version. I also can't see something helpfull in the traceback. Sorry. Can you reproduce the problem with a current "stable" Debian?

Bug#985260:

Thanks for the report. But I'm sorry I don't understand all details. What does the user-callbacks have to do with cron? Maybe the bug is related to cron and not to BIT?

Bug#983616:

Thank you very much for the report. This is fixed upstream. https://github.com/bit-team/backintime/pull/1246 But not yet released.

Bug#985256:

This was reported with a "testing" Debian with a now outdated BIT version. Can you reproduce the problem with the current "stable" Debian?

Bug#978735:

This was reported with a "testing" Debian. Can you reproduce the problem with the current "stable" Debian?

Bug#866741:

Thank you for the report. Can you reproduce the problem with the current version 1.3.2 from "stable" Debian?

Bug#859115:

Outdated. Please close.

Bug#816197:

Fixed now and can be closed. Thanks.

Bug#989202:

There is a closed Issue on Upstream. I don't understand the details but it seems to be a usual behavior. KeePassXC keeps a local and a shareable config file. https://github.com/keepassxreboot/keepassxc/issues/7990 So this isn't a bug?

Bug#985258:

Apologize for multiple posts. As upstream I vote for close. It is a comprehensible warning caused by running backintime in root mode. It is not an error. It doesn't affect the functionality of backintime because it doesn't use XDG_RUNTIME_DIR or QStandardPaths. I checked the code for that.

Bug#985258:

I can reproduce the warning with Version 1.2.1 as "root". Does root need XDG_RUNTIME_DIR? Is it relevant for the use of backintime?

Bug#1018757: minidlna.log permission denied (only in Debian 11) when using multiple instances

Package: minidlna Version: 1.3.0+dfsg-2+deb11u1 Hello, this report is based on that German forum post where someone still helped me to solve the problem and also analyzed the root of the problem. https://debianforum.de/forum/viewtopic.php?p=1307710#p1307710 I'm using multiple instances of mi

Bug#940319: backintime: run test suite during build

Dear Jonathan, 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 auto-builders. Need to find a solution to that. I would like to suggest to save time and resources

Bug#869277: /usr/bin/notify-send: Improve the manpage

Upstream moved its BugTracker Here are the new links to two of the related Issues in upstream https://gitlab.gnome.org/GNOME/libnotify/-/issues/24 https://gitlab.gnome.org/GNOME/libnotify/-/issues/23

Bug#995442: improve README.md on salsa repo

Package: python-debian Version: 0.1.41 This is about the salsa repository for this package. https://salsa.debian.org/python-debian-team/python-debian Issues are deactivated in that repo on salsa. For new users (e.g. Me, who tries to dive deeper into python debian packaging) it is unclear what

Bug#964816: (kein Betreff)

This is a known problem. The initial Debian bug ticket https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946788 and the corresponding upstream ticket https://github.com/kurtmckee/feedparser/issues/198 Your problem specific to georss is upstream reported here https://github.com/kurtmckee/feedpars

Bug#946788: (kein Betreff)

The problem still exists in Debian 11 because the packages was not updated. I do not understand why this was n marked as a release stopping bug for Debian 11.

Bug#970380: (kein Betreff)

1. Unclear log message about "Security Layer" I assume this as upstream related so I opened an Issue there. https://github.com/neutrinolabs/xrdp/issues/1974 Is fixed and merged in upstream. https://github.com/neutrinolabs/xrdp/pull/1975#event-5252991803

Bug#697885: firefox-esr the same

This problem still exists in firefox-esr (Debian 10 & 11). I am not sure about that but I think on a Windows machine my Firefox-ESR does not lose the search shortcuts when I updated it. So it could be related to the debian packaing process. Kind Christian

  1   2   >