close 806215 4.2-1
thanks
Hi,
thank you for reporting this issue and sorry for the inconvenience. This
change you mentioned has been reverted in one of the previous versions,
at least it's not present anymore in 4.2, thus closing this bug.
Regards,
Daniel
close 864145
thanks
Hi,
this setup works (both when installing new with d-i and when later
migrating it manually to it). since there's a long time no answer here
and the system most likely has been resetup, I'm closing this bug.
Regards,
Daniel
close 837964 4.2-1
thanks
Hi,
thank you for reporting this, a patch has been included in some of the
newer mdadm releases, but at least with 4.2, hence closing the bug
accordingly.
Regards,
Daniel
close 818344 4.2-1
thanks
Hi,
thank you for reporting your issue and sorry that you've experienced it.
The bug you're describing should be fixed in current mdadm as the whole
disk assembly stuff has been entirely changed/improved, hence I'm
closing this bug.
If you can still reproduce it with
close 857284 4.2-1
thanks
Hi,
thank you for reporting this issue, however, as noted in the bug this is
not applicable anymore as nothing of the old code is present anymore,
thus closing the bug.
Regards,
Daniel
close 780941
thanks
Hi,
as upstream said, this doesn't make sense as a default, but can be added
on a case-by-case/system-specific basis by the sysadmin, thus closing
the bug.
Regards,
Daniel
close 616688 4.1-3
thanks
Hi,
thank you for reporting this issue, this bothered me too.. which is why
since mdadm 4.1-3 you can disable the different checks
alltogether/individually via debconf.
If you do that, then you don't get any runs of checkarray and therefore
no messages from cron.
close 854830 4.2-1
thanks
Hi,
thank you for reporting this issue and sorry for encountering it.
However, at least current mdadm (as of bullseye) does not change
mdadm.conf (which then gets copied into initramfs) upon hostname
changes. Thus, closing this bug.
Regards,
Daniel
retitle 860458 debconf question to disable initramfs integration
severity 860458 wishlist
thanks
Hi Russell,
thank you for reporting things - this has also bother me in "rescue
system" situations/use-cases. I'll add a debconf question to address
this in one of the next uploads.
Regards,
Daniel
close 865976
thanks
Hi,
thank you for reporting your issue and sorry for running into it.
However, there are lots of things that could have gone wrong
here/outside of what is supported and there's too little information to
even try to reproduce it, and it's very likely that this could have been
close 954816 4.2-1
thanks
Hi,
thank you for reporting this issue.
As this has been fixed in mdadm 4.2, I'm closing the bug accordingly.
Regards,
Daniel
close 844652 4.2-1
thanks
Hi,
thank you for reporting your issue and sorry to hear of your troubles.
However, the current versions of everything (mdadm/kernel/cryptsetup) do
work correctly out-of-the-box and given the long time ago you hit the
issue, this cannot reasonably be fixed "backwards"
close 777140 4.2-1
thanks
Hi,
thank you for reporting this issue.
Fortunately installing on IMSM works out-of-the-box at least with
bullseye and newer, thus closing the bug accordingly.
Regards,
Daniel
close 812608 4.2-1
thanks
Hi,
thank you for your report.
There are two things to note here:
* in general, that the system is doing an fsck all the time is not per
se caused by mdadm. mdadm just assembles the array, and
e2fsprogs/systemd (or the equivalent alternative fs/init) will do
close 855871 4.2-1
thanks
Hi,
current Debian releases (at least bullseye and newer) do allow the large
amount of disks by using v1.2 superblocks by default (in fact, it's
really hard to use the old one if, for whatever reason, one really wants
to). Therefore I'm closing this bug.
Regards,
close 995093
thanks
Hi,
thank you for your suggestion - since mdadm is already available in
stable-backports (containing other fixes that wouldn't be suitable for
stable release), I'm closing this bug.
Regards,
Daniel
close 534470 4.2-1
thanks
Hi,
after reading through the messages, my take on it is:
* if the admin start using newer kernels 'by accident' with e.g. a
rescue system and then revert back to the old kernel on the system,
this is obviously very anoying and understandably worrysome if the
On 2/25/23 00:43, Thorsten Alteholz wrote:
> The problem is related to the 10GB interfaces that are handled by module
> ixgbe. They are called eno*.
jftr, that depends on the board/card configuration (in the majority of
our supermicro servers, the ixgbe are usually enp175* and ens2*)
> The first
close 844354
thanks
Hi,
GNOME >=40 switched to non-rounded corners for fullscreen windows by
default, making this extension obsolete, hence closing the bug.
Regards,
Daniel
close 683293
thanks
Hi,
thank you for bringing up this suggestion.
However, given that the bug has been forwarded upstream, I'd prefer to
track it there rather than to leave it stale here forever in the Debian
BTS where nobody/I will do anything about it anyway. Therefore, I'm
closing it now.
close 653214
thanks
Hi,
thank you for bringing up this suggestion.
However, given that the bug has been forwarded upstream, I'd prefer to
track it there rather than to leave it stale here forever in the Debian
BTS where nobody/I will do anything about it anyway. Therefore, I'm
closing it now.
close 514968
thanks
Hi,
thank you for bringing up this suggestion.
However, given that the bug has been forwarded upstream, I'd prefer to
track it there rather than to leave it stale here forever in the Debian
BTS where nobody/I will do anything about it anyway. Therefore, I'm
closing it now.
close 996975 2.1.1-1
thanks
Hi,
thank you for reporting this issue - it has been fixed upstream in
2.1.1-1, hence closing the bug.
Regards,
Daniel
close 741639
thanks
Hi,
thanks for the report, however, given that libjs-extjs was removed from
Debian 2 years ago, I'm closing the bug. Once libjs-extjs is available
in Debian again, I'm happy to switch to it.
Regards,
Daniel
close 682080
thanks
Hi,
thank you for your report. Like Robert explained, this isn't actually a
bug but intended behaviour, hence closing.
Regards,
Daniel
Hi Thorsten,
On 2/24/23 00:28, Thorsten Alteholz wrote:
> The devices are recognized and can be configured but "ip a" shows
> "no-carrier" for them.
I can't reproduce it, the nics works for fine for me with both 6.1.8 and
6.1.12.
Can you rule out that you were hit by the "interface names
close 964279 2.1.1-1
thanks
Hi Lyndon,
thanks for the feedback, I'll close the bug then.
Regards,
Daniel
close 927196
thanks
Hi,
thank you for your report. Like Robert explained, this isn't actually a
bug but intended behaviour, hence closing.
Regards,
Daniel
close 722719
thanks
Hi,
given that the current package has a systemd unit for deluge-web (which
needs fixing though, #996975), it doesn't make sense to add a
initscript, so closing the bug.
Regards,
Daniel
retitle 691649 make default umask configurable
tag 691649 - patch
severity 691649 wishlist
thanks
Hi,
thank you for reporting this and thanks for the patch (this needs to be
reworked for the systemd integration). I'll make it configurable and add
a debconf question for this in one of the next
close 695752 2.1.1-1
thanks
Hi,
thank you for reporting this, it has been fixed somewhen in the 2.x
uploads as I coudn't reproduce it with the current version, hence
closing this bug.
Regards,
Daniel
retitle 964279 deluge-gtk: python type errors in log
tag 964279 + moreinfo
tag 964279 + unreproducible
thanks
Hi Lyndon,
thank you for your report.
I didn't find any of these with deluge 2.1.1-1, in order to confirm that
this is fixed - where exactly would I find these messages?
Regards,
close 1020825 2.1.1-1
thanks
Hi,
thanks for your report, according to the upstream commits this is
supposedly fixed, hence closing and marking the bug as such.
Regards,
Daniel
close 613443 2.0.3-3.3
thanks
Hi,
this has been fixed in one of the 2.x version, at latest in 2.0.3.
Regards,
Daniel
close 1005411 2.1.1-1
thanks
Hi,
thank you for reporting this, the referenced fixes are included in the
2.1.1 version, hence closing the bug.
Regards,
Daniel
close 954275 2.0.3-3.3
thanks
Hi,
thank you for reporting this, it has been fixed somewhen in the 2.x
version but definitly in 2.0.3, hence closing the bug.
Regards,
Daniel
close 996677 2.1.1-1
thanks
Hi,
the fix for this is included in 2.1.1-1, thus closing the bug accordingly.
Regards,
Daniel
close 701003 2.0.3-3.3
thanks
Hi,
this has indeed been fixed in an earlier version, but definitely with
the version in bullseye, hence closing this bug.
Regards,
Daniel
close 781931 2.0.3-3.3
thanks
Hi,
thank you for reporting this, it has been fixed somewhen in the 2.x
uploads, hence closing this bug.
Regards,
Daniel
close 954232 2.1.1-1
thanks
Hi,
thank you for reporting this.
I can reproduce it with 2.0.3-3.3 and am happy to tell that this was
fixed somewhen after, at latest in 2.1.1-1 with which I can't reproduce
it anymore.
Regards,
Daniel
close 1000456 2.1.1-1
thanks
Hi,
thanks for reporting - it's part of the new upstream version, closing
this bug report.
Regards,
Daniel
close 987118 2.1.1-1
thanks
Hi,
thank you for reporting this bug, I've experienced this several times
with the 2.0.3 version as well. According to the upstream commits, this
should have been fixed in any later version between 2.0.3 and 2.1.1,
hence closing the bug.
Regards,
Daniel
close 839983 2.0.3-3.3
thanks
Hi,
thank you for reporting this issue - this has been fixed somewhen before
bullseye, hence closing the bug.
Regards,
Daniel
close 898355 2.0.3-3.3
thanks
Hi,
this has been fixed in one of the 2.x versions, hence closing this bug.
Regards,
Daniel
close 808443 2.0.3-3.3
thanks
Hi,
there are no more python related errors with 2.x as they were with 1.x,
thus closing the bug.
Regards,
Daniel
close 780833 2.0.3-3.3
thanks
Hi,
I've tried this with the current version in bullseye and this has worked
for me, hence closing the bug.
Regards,
Daniel
close 692869 2.0.3-3.3
thanks
Hi,
it used to be that deluge 1.x is not that stable under heavy load. this
has become much, much better in 2.x where I've never experienced this
anymore, hence closing this bug.
Regards,
Daniel
close 690725
thanks
Hi,
thank you for reporting this issue.
However, since this is a very old bug with very old versions of
everything and a bug that apparently noone else seem to have experienced
(I also never did), I'm closing the bug. Feel free to reopen if it you
can reproduce it with the
close 637807 2.0.3-3.3
thanks
Hi,
I can't reproduce the bug with bullseye nor testing/unstable (with
2.1.1), hence closing the bug.
Regards,
Daniel
close 637798 2.0.3-3.3
thanks
Hi,
I can't reproduce the bug with bullseye nor testing/unstable (with
2.1.1), hence closing the bug.
Regards,
Daniel
close 993083 2.1.1-1
thanks
Hi,
this is fixed in the upload of deluge 2.1.1, hence closing the bug.
Regards,
Daniel
close 1031593 2.1.1-1
thanks
Hi,
I can confirm that this doesn't happen with the 2.1.1 version.
Regards,
Daniel
close 994582 2.1.1-3.3
thanks
Hi,
this has been fixed for bullseye, closing accordingly.
Regards,
Daniel
close 993085 2.0.3-3.3
thanks
Hi,
this has been fixed for bullseye, closing accordingly.
Regards,
Daniel
close 907347 2.0.3-3.3
thanks
Hi,
thank you for your report. Since this is against a 1.x version of deluge
which is buster and earlier, and I coudn't reproduce it with 2.x, I'm
closing the bug.
Regards,
Daniel
close 764099 2.0.3-3.1
thanks
Hi,
thank you for your report. It used to be that deluge-web in deluge 1.x
didn't really work as it should, but since the 2.x uploads this works
without any configuration (except for starting it).
Regards,
Daniel
close 890010 2.1.1-1
thanks
[sorry, pressed 'sent' to early']
there are two issues here:
* upstream: deluge-web doesn't work over ipv6 at all
-> this has been fixed in one of the versions after 2.0.3.
* downstream: while it's still possible to do it by hand[*],
it would be nice if
close 890010 2.1.1-1
thanks
Hi,
there are two issues here:
* upstream: deluge-web doesn't work over ipv6 at all
-> this has been fixed in one of the versions after 2.0.3.
* downstream: deluge-web needs some proper integration
so that it works on both ipv4 and ipv6.
using the
close 979068 2.1.1-1
thanks
Hi,
thank you for your report. I tested this with the current upstream
version (2.1.1-1) and deluge-gtk works without at-spi2-core installed,
hence closing the bug accordingly.
Regards,
Daniel
close 806968 2.0.3-3.1
thanks
Hi,
I can't reproduce this with either bullseye nor testing/unstable. If
you're still able to reproduce it, please reopen the bug and attach the
torrent file.
Regards,
Daniel
close 694885 2.0.3-3.1
thanks
Hi,
as this is a very old bug that I cannot reproduce with bullseye nor
testing/unstable, and both deluge as libtorrent-rasterbar have
significantly progressed since, I'm closing it - for the unlikely case
that you're still able to reproduce it with current debian,
close 781930 2.0.3-3.1
thanks
Hi,
as this is a very old bug that I cannot reproduce with bullseye nor
testing/unstable, and both deluge as libtorrent-rasterbar have
significantly progressed since (e.g. there's no python 2 anymore), I'm
closing it - for the unlikely case that you're still able
retitle 646107 deluge-plugins-extra
thanks
Hi,
yes - this is on my todo:
https://sources.debian.org/src/deluge/latest/debian/TODO/
Regards,
Daniel
close 685780 2.0.3-3.1
thanks
Hi,
thank you for your suggestion.
When you click on a magnet link, deluge downloads the torrent and (if
configured) saves the torrent file, so practically there's no need to
retain the magnet link - you already got the torrent file.
Regards,
Daniel
close 601938 2.0.3-3.1
thanks
Hi,
thank you for your report - this has been fixed by upstream in an early
2.x release (at least as of the version in bullseye), hence closing this
bug.
Regards,
Daniel
close 834428 2.1.1-1
thanks
Hi,
thank you for your report. this has been fixed upstream somewhen in the
2.x releases, but definitely as of 2.1.1-1, hence closing the bug.
Regards,
Daniel
close 705218 2.1.1-1
thanks
Hi,
thank you for your report. this has been fixed upstream somewhen in the
2.x releases, but definitely as of 2.1.1-1, hence closing the bug.
Regards,
Daniel
close 744962 2.1.1-1
thanks
Hi,
thank you for your report. this has been fixed upstream somewhen in the
2.x releases, but definitely as of 2.1.1-1, hence closing the bug.
Regards,
Daniel
close 723128 2.1.1-1
thanks
Hi,
thank you for your report. this has been fixed upstream somewhen in the
2.x releases, but definitely as of 2.1.1-1, hence closing the bug.
Regards,
Daniel
close 860944 2.1.1-1
thanks
Hi,
thank you for your report. Current deluge doesn't support using the
systray anymore as there's currently no support for ayatana-indicators,
thus closing this bug.
Regards,
Daniel
close 796697 2.1.1-1
thanks
Hi,
thank you for your report. Current deluge doesn't support using the
systray anymore as there's currently no support for ayatana-indicators,
thus closing this bug.
Regards,
Daniel
close 773069 2.1.1-1
thanks
Hi,
this has been fixed upstream somewhen in the 2.x releases, but
definitely as of 2.1.1-1, hence closing the bug.
Regards,
Daniel
close 898382 2.1.1-1
thanks
Hi Unit,
thanks for the report. Looking at the current upstream version (2.1.1),
I checked if it works with ayatana indicators and it doesn't - there's
seems to be more needed to make it work, hence closing the bug.
Feel free to reopen the bug if you'd like to
close 985038 2.1.1-1
thanks
Hi,
this has been fixed in one of the newer upstream releases after 2.0.3,
I've verified it with 2.1.1, hence closing the bug.
Regards,
Daniel
close 954165 2.0.3-3.1
thanks
Hi,
although this bug is still present when upgrading from deluge 1.x to
2.x, it doesn't make sense to keep the bug report open here:
* doing a debian specific patch enforcing non-utf8 charset doesn't
make sense for the future (also because everyone else
close 988414 2.1.1-1
thanks
This has been fixed upstream, closing.
Regards,
Daniel
close 685778
thanks
As noted in the previous message, there's a deluge plugin for this.
Regards,
Daniel
close 689491 2.1.1-1
thanks
Hi,
this has been fixed upstream - deluge-gtk now handles it gracefully if
it doesn't have a connection to deluged.
Regards,
Daniel
close 659042 2.0.3-3.1
thanks
Hi,
I can't reproduce the bug with bullseye or current testing/unstable,
hence closing.
Regards,
Daniel
close 935043 2.0.3-3.1
thanks
Hi,
I'm using this in deluge, moving storage works from the context-menu
without errors with both the version in bullseye as well as the one in
testing/unstable.
Regards,
Daniel
close 980738 2.0.3-3.1
thanks
Hi,
I'm using this in deluge, switching the priority works without errors
with both the version in bullseye as well as the one in testing/unstable.
Regards,
Daniel
close 977698 2.0.3-3.1
thanks
Hi,
I'm using this in deluge, works without errors with both the version in
bullseye as well as the one in testing/unstable.
Regards,
Daniel
retitle 1031593 deluge-web: gettext error
severity 1031593 important
thanks
Hi James,
thanks for your report. I'll take a look at it by updating deluge to the
current upstream version (and make sure that deluge-web works as I use
it myself).
Regarding this bug, just so much for now: even if
retitle 995078 ITA: deluge -- bittorrent client written in Python/PyGTK
owner 995078 Daniel Baumann
thanks
Hi,
given that nobody stepped up yet and I'm a deluge user, I'm happy to
adopt the package.
Regards,
Daniel
Hi Markus,
On 2/3/23 07:41, Markus wrote:
> I fixed my problem. strace indicated a problem with netdata's sqlite
> database. That was not reported in any netdata output. So I deleted the
> contents of /var/cache/netdata and all was fine.
great - shouldn't be needed though :/
since upstream
retitle 996042 rebuild inline html from source
thanks
Current status:
* the sources in html/* are complete
(already since some ttyd releases ago)
* not all required node-* packages are in debian to build html.h
* some of the required node-* packages that are in debian are still
Hi Simon,
On 2/9/23 14:50, Simon McVittie wrote:
> My understanding from the changelog is that the maintainer Daniel Baumann
> first packaged a bunch of GNOME Shell extensions according to the GNOME
> team's usual convention (one package per independent upstream project),
> and th
Hi Jeremy
On 2/9/23 13:15, Jeremy Bícha wrote:
> I am lowering the severity of this bug to allow these extensions to
> reach Debian 12.
thanks you, that is very reasonable as it gives us a bit more time.
please let me re-iterate that I'm perfectly fine with whatever consensus
is reached between
Package: python3.11
Severity: normal
Hi,
the last upload of python3.11 claims to be of version 3.11.2, yet, it's
the same as 3.11.1:
daniel@daniel:~$ wget
https://deb.debian.org/debian/pool/main/p/python3.11/python3.11_3.11.1.orig.tar.xz
--2023-02-07 19:44:22--
fwd, seems not to have made it to the bts
Forwarded Message
Subject: Re: Bug#1030683: gnome-shell-extensions-extra: unmaintainable
Date: Tue, 7 Feb 2023 00:49:42 +0100
From: Daniel Baumann
Reply-To: m...@daniel-baumann.ch
To: Jeremy Bícha
CC: Thorsten Alteholz ,
1030
fwd, seems not to have made it to the bts
Forwarded Message
Subject: Re: Bug#1030683: gnome-shell-extensions-extra: unmaintainable
Date: Mon, 6 Feb 2023 17:01:27 +0100
From: Daniel Baumann
Reply-To: m...@daniel-baumann.ch
To: Jeremy Bícha , Thorsten Alteholz
CC: 1030
Hi Andreas,
On 2/6/23 16:43, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
thanks.
> I'm not sure whether B+R are the right solution here or
retitle 1021950 update to current LTS version (6.0)
thanks
Hi,
I'd like to upload a package to debian that requires basel >=6, it would
be nice if you could update the package.
Regards,
Daniel
Hi Fabian,
On 2/3/23 23:53, Fabian Greffrath wrote:
> sorry, but your patch doesn't apply in debian/control.
sorry, here's an updated one (against current git head).
Regards,
DanielFrom b31c396a283fb8c3fedbbbd3ce6259b3e221342f Mon Sep 17 00:00:00 2001
From: Daniel Baumann
Date: Sat, 4 Feb 2
retitle 1030203 fails after start with exit code 1
severity 1030203 important
tag 1030203 + moreinfo
tag 1030203 + unreproducible
thanks
Hi Markus,
thank you for your report.
"fortunately" (or unfortunatly) I cannot reproduce it.. but I've got a
few questions to narrow it down (given that
close 1030092 2.3-1
thanks
On 1/31/23 05:30, Daniel Baumann wrote:
> I've just uploaed 2.3 that should indeed fix
> it.
I've reproduced the bug with 2.2 and can confirm that 2.3 does fix it.
Regards,
Daniel
tag 1030155 + patch
thanks
patch attached.
Regards,
DanielFrom ed2b2936192c897c592930ebb36d1ae3b7bee731 Mon Sep 17 00:00:00 2001
From: Daniel Baumann
Date: Mon, 30 Jan 2023 21:33:25 +0100
Subject: [PATCH 1/2] Adding fonts-dejavu-web package (Closes: #1030155).
Signed-off-by: Daniel Baumann
Package: fonts-dejavu
Version: 2.37-2
Severity: wishlist
Hi,
dejavu is often considered some sort of a "default font", or at the very
least it's a pretty importand and often used font.
given that not all computers have it (especially non-linux systems),
using it for websites as a webfont
Hi Daniel,
thank you for your report - I've just uploaed 2.3 that should indeed fix
it. It would be nice if you could try to confirm it.
Regards,
Daniel
Hi William,
sorry for the delay and thanks for asking about it.
On 1/21/23 20:09, William Desportes wrote:
> Do you need some help with the upload or the package ?
it's ready now, I almost finished it today.. will need some last touches
and updates on debian/copyright, will upload tomorrow or
101 - 200 of 5758 matches
Mail list logo