Bug#565974: marked as done (cdbs distutils target should byte-compile on install)

2025-08-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Aug 2025 11:04:05 + with message-id and subject line Bug#565974: fixed in cdbs 0.4.176 has caused the Debian Bug report #565974, regarding cdbs distutils target should byte-compile on install to be marked as done. This means that you claim that the problem has been

Bug#606530: marked as done (packages build-depending on python-dev should not be built for non-default python version)

2025-08-31 Thread Debian Bug Tracking System
Your message dated Sun, 31 Aug 2025 11:04:05 + with message-id and subject line Bug#606530: fixed in cdbs 0.4.176 has caused the Debian Bug report #606530, regarding packages build-depending on python-dev should not be built for non-default python version to be marked as done. This means

Bug#1112618: Should mmh be removed from unstable?

2025-08-31 Thread Helmut Grohne
ckage. In case the package should be kept in unstable, please evaluate each of the RC-bugs listed above. * If the bug is meant to permanently prevent the package from entering testing or a stable release, but this package should stay part of unstable, please add a usertag: user

Processed: dpkg-cross should mark converted packages as multiarch foreign

2025-07-20 Thread Debian Bug Tracking System
Processing control commands: > owner -1 helm...@debian.org Bug #1109563 [dpkg-cross] dpkg-cross should mark converted packages as multiarch foreign Owner recorded as helm...@debian.org. -- 1109563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109563 Debian Bug Tracking System Contact

Bug#1109563: dpkg-cross should mark converted packages as multiarch foreign

2025-07-20 Thread Aurelien Jarno
Package: dpkg-cross Severity: normal X-Debbugs-Cc: debian-cr...@lists.debian.org Control: owner -1 helm...@debian.org In order to allow foreign cross-toolchain to be installed, the dpkg-cross converted packages needs to be marked multiarch foreign. Helmut intends to handle the problem. # apt-get

Processed: Re: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

2025-04-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 dssi-dev Bug #1103192 [src:naspro-bridges] naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp] Bug reassigned from package 'src:naspro-bridges' t

Bug#1103192: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

2025-04-19 Thread Petter Reinholdtsen
Control: reassign -1 dssi-dev Control: found -1 1.1.1~dfsg0-6 Control: affects -1 src:naspro-bridges Issue #1103192 is also reported as issue #1103187, and need to be fixed in dssi-dev. -- Happy hacking Petter Reinholdtsen

Bug#1103192: naspro-bridges: FTBFS: /usr/include/alsa/seq_event.h:30:2: error: #warning "use #include , should not be used directly" [-Werror=cpp]

2025-04-14 Thread Santiago Vila
'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' configure.ac:31: warning: The macro 'AC_PROG_CC_C99' is obsolete. configure.ac:31: You should run a

Bug#661743: marked as done (apt-xapian-index: should document query language)

2025-04-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Apr 2025 13:22:56 + with message-id and subject line Bug#1100760: Removed package(s) from unstable has caused the Debian Bug report #661743, regarding apt-xapian-index: should document query language to be marked as done. This means that you claim that the problem

Bug#833448: marked as done (libapache2-mod-evasive: Wrong prime number. Should be 3079 instead of 3097)

2025-04-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 Apr 2025 17:04:29 + with message-id and subject line Bug#833448: fixed in libapache-mod-evasive 2.4.0-1 has caused the Debian Bug report #833448, regarding libapache2-mod-evasive: Wrong prime number. Should be 3079 instead of 3097 to be marked as done. This means

Processed: retitle 485978 to xfrisk: friskserver should have a systemd .service

2025-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 485978 xfrisk: friskserver should have a systemd .service Bug #485978 [xfrisk] xfrisk: friskserver should have an init script Changed Bug title to 'xfrisk: friskserver should have a systemd .service' from 'xfrisk: frisk

Bug#494288: marked as done (dh_pycentral/dh_pysupport should run before dh_installinit)

2025-03-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 Mar 2025 13:03:24 +0100 with message-id and subject line Re: dh_pycentral/dh_pysupport should run before dh_installinit has caused the Debian Bug report #494288, regarding dh_pycentral/dh_pysupport should run before dh_installinit to be marked as done. This means that

Bug#1100941: python3-bsddb3: Module bsddb3 is deprecated and should be replaced by 'berkeleydb'

2025-03-22 Thread Lars H. Rohwedder
Package: python3-bsddb3 Version: 6.2.9-2+b4 Severity: normal Dear Maintainer, according to https://pypi.org/project/bsddb3/ this Python module is deprecated and should be replaced by module 'berkeleydb'. But there is no module of this name in Debian, yet. -- System Information: Debi

Bug#889794: marked as done (elpa-cider: should inject dependencies from Debian packages)

2025-03-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Mar 2025 18:45:36 + with message-id and subject line Bug#1100371: Removed package(s) from unstable has caused the Debian Bug report #889794, regarding elpa-cider: should inject dependencies from Debian packages to be marked as done. This means that you claim that

Bug#846777: marked as done (multistrap should fail immediately if hooks return a non-zero exit status)

2025-01-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Jan 2025 16:20:10 + with message-id and subject line Bug#1093962: Removed package(s) from unstable has caused the Debian Bug report #846777, regarding multistrap should fail immediately if hooks return a non-zero exit status to be marked as done. This means that

Bug#1093403: Acknowledgement (gthumb: drag should copy files)

2025-01-17 Thread Allan Wind
gthumb 3:3.12.2-3+b1 (stble) behaves the same way for me.

Bug#1093403: gthumb: drag should copy files

2025-01-17 Thread Allan Wind
Package: gthumb Version: 3:3.12.6-1~bpo12+1 Severity: normal Dear Maintainer, When I drag a file to a folder gthumb will open a dialog asking me to confirm that I want to move the file(s), however per https://help.gnome.org/users/gthumb/stable/gthumb-file-copy-move.html.en drag should be a copy

Processed: Re: colorhug-client: Obsolete appdata should be renamed to metainfo

2025-01-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1078121 [colorhug-client] colorhug-client: Problems reported by "appstreamcli validate-tree" Added tag(s) patch. -- 1078121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078121 Debian Bug Tracking System Contact ow...@bugs.debian.org wit

Bug#1078121: colorhug-client: Obsolete appdata should be renamed to metainfo

2025-01-16 Thread Petter Reinholdtsen
Control: tags -1 + patch [Andreas Tille 2024-11-11] > remains and I need to admit I have no idea how to fix it. Thus I > retitle the bug to the remaining problem. Very good. Here is a patch solving all parsing errors. diff --git a/debian/patches/1010-appstream-typos.patch b/debian/patches/101

Processed (with 1 error): Re: Processed (with 1 error): Re: directfb: Should this package be removed?

2025-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1083037 RM: directfb -- RoQA; RC-buggy, unmaintained Bug #1083037 [src:directfb] RM: directfb -- RoQA; RC-buggy, unmaintained Ignoring request to change the title of bug#1083037 to the same title > user ftp.debian@packages.debian.org S

Bug#1083037: directfb: Should this package be removed?

2025-01-03 Thread Niels Thykier
retitle 1083037 RM: directfb -- RoQA; RC-buggy, unmaintained user ftp.debian@packages.debian.org userags 1083037 remove severity 1083037 normal thanks Hi, As suggested by Simon (full context below), lets remove this package now. Only one rdeps remains (BTS blocker set, so it will disappear

Processed (with 1 error): Re: directfb: Should this package be removed?

2025-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1083037 RM: directfb -- RoQA; RC-buggy, unmaintained Bug #1083037 [src:directfb] directfb: Should this package be removed? Changed Bug title to 'RM: directfb -- RoQA; RC-buggy, unmaintained' from 'directfb: Should this

Bug#655091: marked as done (--dump-memory-profile should log at info level)

2024-12-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Dec 2024 18:28:11 + with message-id and subject line Bug#1088867: Removed package(s) from unstable has caused the Debian Bug report #655091, regarding --dump-memory-profile should log at info level to be marked as done. This means that you claim that the problem

Bug#530676: marked as done (giggle: Shared libraries and headers should be split into packages)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 17:00:47 + with message-id and subject line Bug#1084750: Removed package(s) from unstable has caused the Debian Bug report #530676, regarding giggle: Shared libraries and headers should be split into packages to be marked as done. This means that you claim

Bug#748095: marked as done (guessnet: should no longer build-depend on transitional package libpcap-dev)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #748095, regarding guessnet: should no longer build-depend on transitional package libpcap-dev to be marked as done. This means that

Bug#319076: marked as done (should lower the priority of dhcp profile candidates)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:59:46 + with message-id and subject line Bug#1084746: Removed package(s) from unstable has caused the Debian Bug report #319076, regarding should lower the priority of dhcp profile candidates to be marked as done. This means that you claim that the

Bug#444790: marked as done (Key upload should be automatic)

2024-11-11 Thread Debian Bug Tracking System
Your message dated Mon, 11 Nov 2024 16:58:38 + with message-id and subject line Bug#1084742: Removed package(s) from unstable has caused the Debian Bug report #444790, regarding Key upload should be automatic to be marked as done. This means that you claim that the problem has been dealt

Bug#52691: marked as done (Should support multi-line messages and encrypting messages)

2024-11-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 18:14:37 + with message-id and subject line Bug#1084189: Removed package(s) from unstable has caused the Debian Bug report #52691, regarding Should support multi-line messages and encrypting messages to be marked as done. This means that you claim that the

Bug#52690: marked as done (Should support gnupg)

2024-11-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 18:14:37 + with message-id and subject line Bug#1084189: Removed package(s) from unstable has caused the Debian Bug report #52690, regarding Should support gnupg to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#704277: marked as done (receive should move files within a filesystem)

2024-11-08 Thread Debian Bug Tracking System
Your message dated Fri, 08 Nov 2024 18:14:37 + with message-id and subject line Bug#1084189: Removed package(s) from unstable has caused the Debian Bug report #704277, regarding receive should move files within a filesystem to be marked as done. This means that you claim that the problem has

Processed: Blobwars should build-depend on zlib1g-dev

2024-10-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 672897 unreproducible Bug #672897 [blobwars] Blobwars should build-depend on zlib1g-dev (and possibly others) Added tag(s) unreproducible. > End of message, stopping processing here. Please contact me if you need assistance. --

Bug#672897: Blobwars should build-depend on zlib1g-dev (and possibly others)

2024-10-20 Thread Mindiell
Hi there, As maybe the future new maintainer of this package, I'm going to close this bug as I compiled and played blobwars without any problem. So I think this is unreproducible for now. Thx, Mindiell Control: unreproducible

Bug#1084793: marked as done (git2cl: Should default to UTF-8)

2024-10-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Oct 2024 16:49:17 + with message-id and subject line Bug#1084793: fixed in git2cl 1:3.0-1 has caused the Debian Bug report #1084793, regarding git2cl: Should default to UTF-8 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1084793: git2cl: Should default to UTF-8

2024-10-08 Thread Matthias Urlichs
Source: git2cl Version: 1:2.0+git20120920-4 Severity: important X-Debbugs-Cc: sm...@smurf.noris.de git2cl may emit latin1 output. This is not a good idea these days. https://savannah.nongnu.org/bugs/index.php?reload=1&func=detailitem&item_id=66305 I found the problem via https://github.com/gramp

Bug#1082604: Should syncmaildir be removed from unstable?

2024-09-30 Thread Antoine Beaupré
ot;, mark for removal you mean? Just to clarify. > Some observations: > > - The services which Antoine mentions are examples in the source code, > the smd-loop script provided in the package itself should hopefully > not run in that situation. "Hopefully". In practice,

Processed: directvnc: should this package be removed?

2024-09-30 Thread Debian Bug Tracking System
Processing control commands: > block 1083037 by -1 Bug #1083037 [src:directfb] directfb: Should this package be removed? 1083037 was blocked by: 1083040 1083042 1083037 was not blocking any bugs. Added blocking bug(s) of 1083037: 1083043 -- 1083037: https://bugs.debian.org/cgi-bin/bugreport.

Bug#1083037: directfb: Should this package be removed?

2024-09-30 Thread Simon McVittie
Source: directfb Severity: serious Justification: ensure visibility for potential adopters X-Debbugs-Cc: debian-...@lists.debian.org, debian...@lists.debian.org User: debian...@lists.debian.org Usertags: directfb directfb has been unmaintained in Debian since 2018, and its web pages directfb.org a

Bug#1082604: Should syncmaildir be removed from unstable?

2024-09-29 Thread Salvatore Bonaccorso
reassigned to ftp.debian.org to actually request removal of the package. > > In case the package should be kept in unstable, please evaluate each of the > RC-bugs listed above. > * If the bug is meant to permanently prevent the package from entering > testing >or a sta

Bug#1082604: Should syncmaildir be removed from unstable?

2024-09-22 Thread Helmut Grohne
: 2 years * It is not part of bookworm or trixie and is not a key package. This bug serves as a pre-removal warning. After one month, the bug will be reassigned to ftp.debian.org to actually request removal of the package. In case the package should be kept in unstable, please evaluate each of the

Bug#1080501: Should airport-utils be removed from unstable?

2024-09-04 Thread Helmut Grohne
package should be kept in unstable, please evaluate each of the RC-bugs listed above. * If the bug is meant to prevent the package from entering testing or a stable release, but this package should stay part of unstable, please add a usertag: user helm...@debian.org usertags NNN

Bug#907974: marked as done (perl-doc-html: Should be updated to 5.28 at the point of the transition)

2024-09-03 Thread Debian Bug Tracking System
Your message dated Wed, 04 Sep 2024 04:10:48 + with message-id and subject line Bug#1079690: Removed package(s) from unstable has caused the Debian Bug report #907974, regarding perl-doc-html: Should be updated to 5.28 at the point of the transition to be marked as done. This means that you

Bug#1079960: Should fruit be removed from unstable?

2024-08-28 Thread Helmut Grohne
Last modified: 2 years * It is not part of bookworm or trixie and is not a key package. This bug serves as a pre-removal warning. After one month, the bug will be reassigned to ftp.debian.org to actually request removal of the package. In case the package should be kept in unstable, please evaluate

Bug#864658: marked as done (wireless-tools: Homepage: should be updated to https://hewlettpackard.github.io/wireless-tools/Tools.html)

2024-07-24 Thread Debian Bug Tracking System
Your message dated Wed, 24 Jul 2024 11:04:00 + with message-id and subject line Bug#864658: fixed in wireless-tools 30~pre9-18 has caused the Debian Bug report #864658, regarding wireless-tools: Homepage: should be updated to https://hewlettpackard.github.io/wireless-tools/Tools.html to be

Bug#1020239: marked as done (gcc-3.3: build-depends on gsfonts-x11 should be replaced by fonts-urw-base35)

2024-06-15 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jun 2024 00:56:13 + with message-id and subject line Bug#1072999: Removed package(s) from unstable has caused the Debian Bug report #1020239, regarding gcc-3.3: build-depends on gsfonts-x11 should be replaced by fonts-urw-base35 to be marked as done. This means

Bug#601605: marked as done (fbreader should register as a handler for the application/epub+zip mime type)

2024-05-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 May 2024 11:34:24 + with message-id and subject line Bug#601605: fixed in fbreader 0.99.4+dfsg-6 has caused the Debian Bug report #601605, regarding fbreader should register as a handler for the application/epub+zip mime type to be marked as done. This means that

Bug#601609: marked as done (fbreader desktop entry should declare application/epub+zip mime type)

2024-05-10 Thread Debian Bug Tracking System
Your message dated Fri, 10 May 2024 11:34:24 + with message-id and subject line Bug#601609: fixed in fbreader 0.99.4+dfsg-6 has caused the Debian Bug report #601609, regarding fbreader desktop entry should declare application/epub+zip mime type to be marked as done. This means that you claim

Bug#641204: marked as done (olpc-powerd: should list the "dialog" package (at least) as a suggested package)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 11:51:41 + with message-id and subject line Bug#641204: fixed in olpc-powerd 23-5 has caused the Debian Bug report #641204, regarding olpc-powerd: should list the "dialog" package (at least) as a suggested package to be marked as done. This mean

Bug#177966: marked as done (kinput2-wnn: Multiple invocation should be avoided)

2024-04-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 17:47:53 + with message-id and subject line Bug#1068259: Removed package(s) from unstable has caused the Debian Bug report #177966, regarding kinput2-wnn: Multiple invocation should be avoided to be marked as done. This means that you claim that the

Bug#725454: marked as done (libapache2-mod-auth-kerb: should read keytab before dropping privileges)

2024-04-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 Apr 2024 17:27:47 + with message-id and subject line Bug#1068262: Removed package(s) from unstable has caused the Debian Bug report #725454, regarding libapache2-mod-auth-kerb: should read keytab before dropping privileges to be marked as done. This means that you

Bug#1024927: marked as done (libtextwrap should support the noudeb build profile)

2024-03-25 Thread Debian Bug Tracking System
Your message dated Mon, 25 Mar 2024 07:36:09 + with message-id and subject line Bug#1024927: fixed in libtextwrap 0.1-17 has caused the Debian Bug report #1024927, regarding libtextwrap should support the noudeb build profile to be marked as done. This means that you claim that the problem

Bug#850955: marked as done (libapache2-request-perl: description should include the names of the libraries)

2024-02-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 Feb 2024 17:50:58 + with message-id and subject line Bug#850955: fixed in libapreq2 2.17-4~exp1 has caused the Debian Bug report #850955, regarding libapache2-request-perl: description should include the names of the libraries to be marked as done. This means that

Bug#287118: marked as done (rsh-client: should work even if not SETUID)

2024-01-31 Thread Debian Bug Tracking System
Your message dated Wed, 31 Jan 2024 18:38:44 + with message-id and subject line Bug#1041864: Removed package(s) from unstable has caused the Debian Bug report #287118, regarding rsh-client: should work even if not SETUID to be marked as done. This means that you claim that the problem has

Bug#1061090: autoconf-doc: single html file should be broken into one web page per node

2024-01-17 Thread Louie S.
Package: autoconf-doc Severity: wishlist X-Debbugs-Cc: lshpr...@tutanota.com Dear Maintainer, This package ships HTML documentation in a single file, as opposed to multiple files, with one web page per node. Generally, GNU software documentation can target HTML format either as entirely one web p

Bug#483086: marked as done (gs-common should be in oldlibs)

2024-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 00:58:13 -0600 with message-id <6639722.GXAFRqVoOG@riemann> and subject line Re: gs-common should be in oldlibs has caused the Debian Bug report #483086, regarding gs-common should be in oldlibs to be marked as done. This means that you claim that the p

Bug#457381: marked as done (libgs8: should libcupsimage2 be a recommends rather than depends?)

2024-01-04 Thread Debian Bug Tracking System
Your message dated Fri, 05 Jan 2024 00:56:29 -0600 with message-id <6667549.31r3eYUQgx@riemann> and subject line Re: it would be nice to be able to install ghostscript without libcupsys2 has caused the Debian Bug report #452382, regarding libgs8: should libcupsimage2 be a recommends rathe

Bug#693321: marked as done (ghostscript: -r option should be instead -r in the manual)

2024-01-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jan 2024 22:43:56 -0600 with message-id <3361117.VqM8IeB0Os@riemann> and subject line Re: ghostscript: -r option should be instead -r in the manual has caused the Debian Bug report #693321, regarding ghostscript: -r option should be instead -r in the manual

Bug#555005: marked as done (ghostscript: help text should mention -doc package)

2024-01-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Jan 2024 20:59:18 -0600 with message-id <3592248.V25eIC5XRa@riemann> and subject line Re: [ghostscript] Patch has caused the Debian Bug report #555005, regarding ghostscript: help text should mention -doc package to be marked as done. This means that you claim th

Bug#733545: marked as done (cpufreqd should honour bios_limit when setting max/min freq)

2023-11-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 Nov 2023 18:30:32 + with message-id and subject line Bug#1056251: Removed package(s) from unstable has caused the Debian Bug report #733545, regarding cpufreqd should honour bios_limit when setting max/min freq to be marked as done. This means that you claim that

Bug#627265: marked as done (cpufreqd: should not use numeric signals in init script)

2023-11-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 Nov 2023 18:30:32 + with message-id and subject line Bug#1056251: Removed package(s) from unstable has caused the Debian Bug report #627265, regarding cpufreqd: should not use numeric signals in init script to be marked as done. This means that you claim that the

Bug#748631: marked as done (apt-listchanges should put separate version numbers in seen DB for each binary package)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#748631: fixed in apt-listchanges 4.0 has caused the Debian Bug report #748631, regarding apt-listchanges should put separate version numbers in seen DB for each binary package to be marked as done. This

Bug#514865: marked as done (apt-listchanges: GTK+ window should not steal focus, and only appear if there is anything to show)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:07 + with message-id and subject line Bug#514865: fixed in apt-listchanges 4.0 has caused the Debian Bug report #514865, regarding apt-listchanges: GTK+ window should not steal focus, and only appear if there is anything to show to be marked as done

Bug#1028474: marked as done (apt-listchanges: text frontend should flush stdout before prompting for confirmation)

2023-10-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 21:34:08 + with message-id and subject line Bug#1028474: fixed in apt-listchanges 4.0 has caused the Debian Bug report #1028474, regarding apt-listchanges: text frontend should flush stdout before prompting for confirmation to be marked as done. This

Bug#322349: marked as done (grun should strip spaces)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #322349, regarding grun should strip spaces to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#310748: marked as done (order of entries should be LRU)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #310748, regarding order of entries should be LRU to be marked as done. This means that you claim that the problem has been dealt

Bug#1003112: apt-listchanges uses sensible-pager now, should this be sensible-pager's job?

2023-10-02 Thread Russ Allbery
Jonathan Kamens writes: > apt-listchanges no longer calls less by default, it calls > sensible-pager. It feels to me like perhaps settings LESSSECURE should > be sensible-pager's job if anybody is going to do it, not > apt-listchanges's job. What do you think? I'm

Bug#1026376: marked as done (apt-listchanges: Should not emit "WARNING: Unknown distro but dpkg found, assuming Debian" on Debian (Unstable))

2023-10-02 Thread Debian Bug Tracking System
Your message dated Mon, 2 Oct 2023 18:16:46 -0400 with message-id <8981438c-2e75-4565-bb07-479119bc6...@kamens.us> and subject line I don't think this was an apt-listchanges bug has caused the Debian Bug report #1026376, regarding apt-listchanges: Should not emit "WARNING: Unknown

Bug#1003112: apt-listchanges uses sensible-pager now, should this be sensible-pager's job?

2023-10-02 Thread Jonathan Kamens
apt-listchanges no longer calls less by default, it calls sensible-pager. It feels to me like perhaps settings LESSSECURE should be sensible-pager's job if anybody is going to do it, not apt-listchanges's job. What do you think?

Bug#1040322: marked as done (debdry: should not ship test data in /usr/lib/python3/dist-packages/control)

2023-09-26 Thread Debian Bug Tracking System
Your message dated Tue, 26 Sep 2023 16:31:53 + with message-id and subject line Bug#1051718: Removed package(s) from unstable has caused the Debian Bug report #1040322, regarding debdry: should not ship test data in /usr/lib/python3/dist-packages/control to be marked as done. This means

Processed: retitle 748631 to apt-listchanges should put separate version numbers in seen DB for each binary package

2023-09-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 748631 apt-listchanges should put separate version numbers in seen DB > for each binary package Bug #748631 [apt-listchanges] apt-listchanges should put separate version numbers Changed Bug title to 'apt-listchanges should p

Bug#1028474: apt-listchanges: text frontend should flush stdout before prompting for confirmation

2023-09-25 Thread Jonathan Kamens
Thanks for the bug report and patch, will fix. Do you want to be credited for the fix in the changelog, and if so, how do you want to be identified?

Bug#532755: gthumb: import dialog box should not close after importing photos

2023-09-15 Thread Boyuan Yang
Control: close -1 On Thu, 11 Jun 2009 11:44:53 +0100 Julian Gilbey wrote: > Package: gthumb > Version: 3:2.10.11-1 > Severity: wishlist > > I imported 2 photos from a camera, and wanted to import further ones > from the same camera.  Unfortunately, after clicking "Import" and > importing the fir

Processed: Re: gthumb: import dialog box should not close after importing photos

2023-09-15 Thread Debian Bug Tracking System
Processing control commands: > close -1 Bug #532755 [gthumb] gthumb: import dialog box should not close after importing photos Marked Bug as done -- 532755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532755 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#345606: marked as done ("Read Msg" should work sane for default options)

2023-07-29 Thread Debian Bug Tracking System
Your message dated Sat, 29 Jul 2023 17:20:48 + with message-id and subject line Bug#1041720: Removed package(s) from unstable has caused the Debian Bug report #345606, regarding "Read Msg" should work sane for default options to be marked as done. This means that you claim that t

Bug#1040322: debdry: should not ship test data in /usr/lib/python3/dist-packages/control

2023-07-04 Thread Helmut Grohne
se it clearly should not be installing this file. Helmut

Bug#360884: rwhod: There should be an option to configure the alarm interval

2023-06-25 Thread Gürkan Myczko
With the new ruptime, see https://bugs.debian.org/1013361 you can easily configure this option.

Bug#820994: marked as done (argon2: Section should be “utils”)

2023-06-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jun 2023 15:27:05 +0200 with message-id <9fd1f3ad-7c01-040e-91c7-1f14778e4...@debian.org> and subject line Re: Bug#820994: argon2: Section should be “utils” has caused the Debian Bug report #820994, regarding argon2: Section should be “utils” to be marked as done.

Processed: libapache2-request-perl: description should include the names of the libraries

2023-06-12 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #850955 [libapache2-request-perl] libapache2-request-perl: description should include the names of the libraries Added tag(s) pending. -- 850955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850955 Debian Bug Tracking System Contact

Bug#850955: libapache2-request-perl: description should include the names of the libraries

2023-06-12 Thread Sebastiaan Couwenberg
Control: tags -1 pending This is fixed in git: https://salsa.debian.org/debian/libapreq2/-/commit/b450debda66bcf40de4c1053da642a8bd972a973 Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Bug#560014: marked as done (Installing libapache2-mod-apreq2 should enable the apreq module)

2023-06-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Jun 2023 07:29:05 +0200 with message-id and subject line Re: Installing libapache2-mod-apreq2 should enable the apreq module has caused the Debian Bug report #560014, regarding Installing libapache2-mod-apreq2 should enable the apreq module to be marked as done. This

Bug#1027355: marked as done (src:libapreq2: Should not migrate to testing.)

2023-06-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Jun 2023 18:42:02 +0200 with message-id <300af957-6854-50b8-8d4b-3cd6e1294...@xs4all.nl> and subject line Re: Bug#1027355: src:libapreq2: Should not migrate to testing. has caused the Debian Bug report #1027355, regarding src:libapreq2: Should not migrate to testi

Bug#807595: marked as done (grepmail: standard directory structure should be used)

2023-05-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 May 2023 17:34:11 + with message-id and subject line Bug#807595: fixed in grepmail 5.3111-1 has caused the Debian Bug report #807595, regarding grepmail: standard directory structure should be used to be marked as done. This means that you claim that the problem

Bug#1034696: marked as done (libargon2-1-udeb: should build with threading support)

2023-04-25 Thread Debian Bug Tracking System
Your message dated Wed, 26 Apr 2023 06:48:46 + with message-id and subject line Bug#1034696: fixed in argon2 0~20171227-0.3+deb12u1 has caused the Debian Bug report #1034696, regarding libargon2-1-udeb: should build with threading support to be marked as done. This means that you claim that

Bug#1034696: marked as done (libargon2-1-udeb: should build with threading support)

2023-04-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Apr 2023 22:19:04 + with message-id and subject line Bug#1034696: fixed in argon2 0~20190702+dfsg-3 has caused the Debian Bug report #1034696, regarding libargon2-1-udeb: should build with threading support to be marked as done. This means that you claim that the

Bug#1034696: libargon2-1-udeb: should build with threading support

2023-04-21 Thread Guilhem Moulin
Source: argon2 Package: libargon2-1-udeb Version: 0~20190702+dfsg-2 Control: found -1 0~20171227-0.2 Control: found -1 0~20171227-0.3 Control: affects -1 cryptsetup-udeb Severity: important Tags: d-i patch bookworm Hi, While investigating LUKS2 PBKDF benchmark results in d-i with kibi (d-i mainta

Processed: libargon2-1-udeb: should build with threading support

2023-04-21 Thread Debian Bug Tracking System
Processing control commands: > found -1 0~20171227-0.2 Bug #1034696 [src:argon2] libargon2-1-udeb: should build with threading support Marked as found in versions argon2/0~20171227-0.2. > found -1 0~20171227-0.3 Bug #1034696 [src:argon2] libargon2-1-udeb: should build with threading s

Bug#1008579: marked as done (a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write')

2023-04-13 Thread Debian Bug Tracking System
Your message dated Fri, 14 Apr 2023 03:19:05 + with message-id and subject line Bug#1008579: fixed in a2ps 1:4.14-8 has caused the Debian Bug report #1008579, regarding a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write' to be marked as done.

Bug#1008579: marked as done (a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write')

2023-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 15 Mar 2023 20:39:46 + with message-id and subject line Bug#1008579: fixed in a2ps 1:4.15.1-1~exp1 has caused the Debian Bug report #1008579, regarding a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write' to be marked

Bug#472947: marked as done (package sanitizer should be really debianized)

2023-02-28 Thread Debian Bug Tracking System
Your message dated Tue, 28 Feb 2023 15:10:36 + with message-id and subject line Bug#1016190: Removed package(s) from unstable has caused the Debian Bug report #472947, regarding package sanitizer should be really debianized to be marked as done. This means that you claim that the problem has

Bug#969861: marked as done (rdist: autopkgtest should be marked superficial)

2023-02-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Feb 2023 21:23:09 + with message-id and subject line Bug#1031841: Removed package(s) from unstable has caused the Debian Bug report #969861, regarding rdist: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem

Bug#585972: marked as done (metche.conf should allow keywords with capital Characters)

2023-02-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Feb 2023 21:24:02 + with message-id and subject line Bug#913719: Removed package(s) from unstable has caused the Debian Bug report #585972, regarding metche.conf should allow keywords with capital Characters to be marked as done. This means that you claim that the

Bug#352123: marked as done (libcommoncpp2-dev: slog should not cut after 128 bytes)

2023-02-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Feb 2023 21:24:29 + with message-id and subject line Bug#998889: Removed package(s) from unstable has caused the Debian Bug report #352123, regarding libcommoncpp2-dev: slog should not cut after 128 bytes to be marked as done. This means that you claim that the

Bug#1027355: src:libapreq2: Should not migrate to testing.

2023-01-23 Thread Salvatore Bonaccorso
l: affects -1 rapache > Control: affects -1 libapache2-authcassimple-perl > Control: affects -1 libapache2-sitecontrol-perl > > The package should probably be removed for bookworm, > at least without clarification from upstream about the security issue. > (see for details #1018191) FT

Processed: telnet and telnet-ssl entries for the same issue should now be merged

2023-01-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 338494 normal Bug #338494 [telnet-ssl] netkit-telnet: Cannot enter some UTF-8 strings Severity set to 'normal' from 'important' > merge 338494 749322 Bug #338494 [telnet-ssl] netkit-telnet: Cannot enter some UTF-8 strings Bug #749322 [tel

Bug#300833: marked as done (no logrotate configuration (should it be a bind9 bugreport?))

2022-12-19 Thread Debian Bug Tracking System
Your message dated Mon, 19 Dec 2022 23:32:09 + with message-id and subject line Bug#1026360: Removed package(s) from unstable has caused the Debian Bug report #300833, regarding no logrotate configuration (should it be a bind9 bugreport?) to be marked as done. This means that you claim that

Processed: Re: Bug#1024824: The software outputs: "No access to printer device file". Normal user should be added to lp group to make `mtink` work and it has been added to it indeed, so it is in the /

2022-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1024824 The software outputs: "No access to printer device file" Bug #1024824 [mtink] The software outputs: "No access to printer device file". Normal user should be added to lp group to make `mtink` work and i

Bug#1024927: libtextwrap should support the noudeb build profile

2022-11-27 Thread Helmut Grohne
Source: libtextwrap Version: 0.1-15 Severity: minor Tags: patch User: helm...@debian.org Usertags: rebootstrap libtextwrap builds a udeb. Therefore, it should support a noudeb build profile. It's a one-line change and I'm attaching a patch for your convenience. Helmut diff --mi

Bug#1024824: The software outputs: "No access to printer device file". Normal user should be added to lp group to make `mtink` work and it has been added to it indeed, so it is in the /etc/group file

2022-11-25 Thread Nicholas Sheriff
Package: mtink Version: 1.0.16-14 Severity: grave X-Debbugs-Cc: caterpillar@gmail.com -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: L

Bug#432537: marked as done (libnss-ldap should support tls configuration)

2022-11-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2022 01:20:11 + with message-id and subject line Bug#1024140: Removed package(s) from unstable has caused the Debian Bug report #432537, regarding libnss-ldap should support tls configuration to be marked as done. This means that you claim that the problem has

Bug#273059: marked as done (PAM should canocolize uid with NSS before group membership is set)

2022-11-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Nov 2022 01:20:11 + with message-id and subject line Bug#1024140: Removed package(s) from unstable has caused the Debian Bug report #273059, regarding PAM should canocolize uid with NSS before group membership is set to be marked as done. This means that you claim

Bug#964536: marked as done (mutrace should not depend on the shared binutils libraries)

2022-11-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Nov 2022 01:02:27 + with message-id and subject line Bug#1024110: Removed package(s) from unstable has caused the Debian Bug report #964536, regarding mutrace should not depend on the shared binutils libraries to be marked as done. This means that you claim that

  1   2   3   4   5   6   7   8   9   10   >