Your message dated Fri, 28 Feb 2025 14:09:41 +0100
with message-id
and subject line Re: Bug#1099087: general: Looping when updating sistem
has caused the Debian Bug report #1099087,
regarding general: Looping when updating sistem
to be marked as done.
This means that you claim that the problem
ng fro upgrade on trixie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
m
* Niels Thykier [241108 14:12]:
> Jakub Ružička:
> > I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
> > marked as Done but the bug still blocks knot migration for reasons I
> > don't understand:
> > https://qa.debian.org/excuses.php
Jakub Ružička:
Hello,
I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
don't understand:
https://qa.debian.org/excuses.php?package=knot
What do I need to do to finally finish migration?
Hello,
I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
don't understand:
https://qa.debian.org/excuses.php?package=knot
What do I need to do to finally finish migration?
Cheers
be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking
Your message dated Fri, 07 Jun 2024 22:18:08 +0200
with message-id
and subject line Re: Bug#1072491: Dead keys stopped working in unspecified
environment
has caused the Debian Bug report #1072491,
regarding Dead keys stopped working in unspecified environment
to be marked as done.
This means
rt #1068778,
regarding geoclue and gpsd are running by default (they aren't needed and could
be used for location tracking)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if neces
-bit) running Debian 11.7,
Logitech USB keyboard and mouse.
--J
Sent from my mobile device.
From: Debian Bug Tracking System
Sent: Wednesday, October 18, 2023 06:39
To: Tomas Pospisek
Subject: Bug#1053664: marked as done (general: Plugging or unplugging USB
: Wednesday, October 18, 2023 06:39
To: Tomas Pospisek
Subject: Bug#1053664: marked as done (general: Plugging or unplugging USB
device sometimes causes the system to lockup.)
Your message dated Wed, 18 Oct 2023 12:57:27 +0200 (CEST)
with message-id <436febb7-775-290-45a4-7a98acfb...@sourcepole.ch>
tem to lockup.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
mess
On Mon, 25 Sep 2023, Jonathan Kamens wrote:
> Thank you! A canonical answer at last.
The reason why it wasn't implemented for -done and -forwarded is because
the psuedoheader parsing for -done is pretty different, and we aren't
doing any parsing for -forwarded.
There's no techn
* Andrey Rakhmatullin [230925 15:13]:
> On Mon, Sep 25, 2023 at 01:55:22PM -0400, Jonathan Kamens wrote:
> > The documentation you inked to does not specify a tag that can be used
> > specifically to mark something as not actually a bug.
> Yes, we just close those. The Debian BTS is not as rich as
ther reasons why *this bug won't be fixed*, which doesn't apply if this
is not a bug.
> Is there some harm that is done by marking a bug that falls into this
> category with "wontfix"?
I think there is some: it having wontfix suggests the bug is valid but
won't
* Jonathan Kamens [230925 12:56]:
> Closed bugs are available for direct search for 30 days after they're
> closed.
>
> After that you can still search them by selecting either "Archived" or
> "Archived and Unarchived" under "Misc Options" on the search page.
Except that in the general case, thi
* Russ Allbery [230925 12:43]:
> Marvin Renich writes:
>
> > I've seen differing opinions about closing "wontfix" bugs, but as a
>
> I think it's a trade-off.
Which is why I said there are differing opinions. This has come up on
this list before.
> There are some bugs that seem unlikely to e
x27;t consider this a bug" seems, to me, to fit under "other reasons."
Is there some harm that is done by marking a bug that falls into this
category with "wontfix"?
jik
On 9/25/23 13:40, Andrey Rakhmatullin wrote:
On Mon, Sep 25, 2023 at 12:55:16PM -0400, Jonathan
On Mon, Sep 25, 2023 at 12:55:16PM -0400, Jonathan Kamens wrote:
> All that aside, in this particular case I closed the bug because it wasn't
> actually a bug, but rather a PEBKAC issue (user complaining that a program
> wasn't respecting his locale when he had LC_ALL set to "C" so he was
> essenti
Closed bugs are available for direct search for 30 days after they're
closed.
After that you can still search them by selecting either "Archived" or
"Archived and Unarchived" under "Misc Options" on the search page.
All that aside, in this particular case I closed the bug because it
wasn't a
Marvin Renich writes:
> I've seen differing opinions about closing "wontfix" bugs, but as a
> user, I appreciate when they are left open. Whether it is a simple
> wishlist feature request or a crash when the user abuses the software,
> if I go to file the same or similar bug at a later time, if
* Jonathan Kamens [230925 07:17]:
> Hi all,
>
> I recently tried to close a bug, explain why, and set a "wontfix" tag all at
> once by sending my explanation to ###-d...@bugs.debian.org with "Control:
> tags ### wontfix" as the first line of my message body. The bug was closed
> but the tags comm
n.org with "Control:
tags ### wontfix" as the first line of my message body. The bug was closed
but the tags command wasn't processed.
It doesn't work for NNN-done@ according to
https://www.donarmstrong.com/posts/control_at_submit/
sage body. The bug was closed
> but the tags command wasn't processed.
It doesn't work for NNN-done@ according to
https://www.donarmstrong.com/posts/control_at_submit/
il to bugnumber@b.d.o
><mailto:bugnumber@b.d.o> or do you need to use control@b.d.o
><mailto:control@b.d.o>?
>
>ANSWER: You need to use the explicit control@ mail copy, automatic
>parsing isn't done. From what I understood it's worked on but it
>mi
...and I just successfully used a Control: header in an email to
###@bugs.debian.org, so the only question remaining in my mind is
whether the one that didn't work failed because it was sent to ###-done,
or failed because of the base64 encoding. I can't think of any other
reaso
On Mon, Sep 25, 2023 at 02:44:19PM +0100, Peter B wrote:
> On 25/09/2023 14:25, Jonathan Kamens wrote:
> >
> > So putting a Control: line in the pseudo-header of a message sent to
> > ###-d...@bugs.debian.org doesn't work at all?
> >
>
> It should work if the syntax is correct. The + character
udo header in an email to bugnumber@b.d.o
<mailto:bugnumber@b.d.o> or do you need to use control@b.d.o
<mailto:control@b.d.o>?
ANSWER: You need to use the explicit control@ mail copy, automatic
parsing isn't done. From what I understood it's worked on but it
might
On 25/09/2023 14:25, Jonathan Kamens wrote:
So putting a Control: line in the pseudo-header of a message sent to
###-d...@bugs.debian.org doesn't work at all?
It should work if the syntax is correct. The + character was missing.
On Mon, Sep 25, 2023 at 02:06:44PM +0100, Peter B wrote:
> > I recently tried to close a bug, explain why, and set a "wontfix" tag
> > all at once by sending my explanation to ###-d...@bugs.debian.org with
> > "Control: tags ### wontfix" as the first line of my message body. The
> > bug was closed
So putting a Control: line in the pseudo-header of a message sent to
###-d...@bugs.debian.org doesn't work at all?
On 9/25/23 09:06, Peter B wrote:
On 25/09/2023 12:16, Jonathan Kamens wrote:
Hi all,
I recently tried to close a bug, explain why, and set a "wontfix" tag
all at once by sendin
On 25/09/2023 12:16, Jonathan Kamens wrote:
Hi all,
I recently tried to close a bug, explain why, and set a "wontfix" tag all at once by sending my explanation to
###-d...@bugs.debian.org with "Control: tags ### wontfix" as the first line of my message body. The bug was closed but
the tags co
Hi all,
I recently tried to close a bug, explain why, and set a "wontfix" tag
all at once by sending my explanation to ###-d...@bugs.debian.org with
"Control: tags ### wontfix" as the first line of my message body. The
bug was closed but the tags command wasn't processed.
Looking at the raw
Your message dated Tue, 19 Sep 2023 08:35:05 +0200 (CEST)
with message-id <10e42929-f4db-dc2d-ea8-cb9a8cfaf...@sourcepole.ch>
and subject line closing bug report
has caused the Debian Bug report #1051401,
regarding general: PATH variable definition in debian 12
to be marked as done.
This
Your message dated Wed, 14 Jun 2023 23:55:39 +
with message-id
and subject line Re: Bug#1037968: unauthorised background updates
has caused the Debian Bug report #1037968,
regarding unauthorised background updates
to be marked as done.
This means that you claim that the problem has been
0, but logout occurs much
earlier
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this
dules/5.10.0-17-amd64
has caused the Debian Bug report #1018891,
regarding general: Can't install fans on msi laptop due to missing ec_sys
kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL:
Module ec_sys not found in directory /lib/modules/5.10.0-17-amd64
to be marked as d
ject and does see releases (even though with a long cadence).
The described plan is implemented and all done:
- Upload of inetutils taking over the packages and updating
alternative priority.
- Upload of netkit-telnet renaming the packages.
- Migration of inetutils to testing.
- Overrides upd
Your message dated Thu, 30 Jun 2022 10:22:58 +0200
with message-id <20220630082257.dfe35x2cghs7a...@gpm.stappers.nl>
and subject line Too broad
has caused the Debian Bug report #1014029,
regarding invisible malicious unicode in source code - detection and prevention
to be marked as done.
Your message dated Wed, 2 Mar 2022 10:01:53 +0100 (CET)
with message-id
and subject line reporter has solved the issue
has caused the Debian Bug report #1005339,
regarding general: usbmouse+keyboard lag on closing the lid or issuing xrandr
--output eDP-1 --off
to be marked as done.
This means
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking
989370,
regarding general: In bonding network configuration, hwaddress crashes
networking service, fails to restart
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/
Your message dated Tue, 09 Mar 2021 10:51:14 +0100
with message-id <87a6rcy7sd@mimuw.edu.pl>
and subject line problem no longer reproducible
has caused the Debian Bug report #983523,
regarding general: some WWW sites no longer work neither in Firefox nor in
Chrome
to be marked as done.
Your message dated Wed, 23 Dec 2020 20:48:41 +0100
with message-id <8735zwi9ra@hands.com>
and subject line Re: Bug#977975: general: Root does not aknoledge root password
has caused the Debian Bug report #977975,
regarding general: Root does not aknoledge root password
to be marked a
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking
caused the Debian Bug report #865771,
regarding general: always stuck before reaching gui mode and can not reach text
mode with ctrl + alt + f6 (debian 9 stable, asus rog552vx)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is no
nitors - Full Screen behaviour
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
arding bugs.debian.org: Boot process with kernel 4.18.0.3 fails and goes to
black screen.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(
878259,
regarding general: Image icons progressively becoming either absent or default
placemat whatever settings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or f
de not completed on the bios machine or similar.
has caused the Debian Bug report #964940,
regarding bugs.debian.org: After an upgrade and crash, the boot process say
ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not
completed on the bios machine or similar.
to be marked a
e even when i shut it down
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea wha
: Boot fails without acpi=off on HP ENVY 13-ah0003na
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system adminis
an.org: Laptop does not resume when undocked while suspended.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
Your message dated Sun, 30 Aug 2020 13:00:01 +0200
with message-id <20200830105959.q6npnd54jao4v...@percival.namespace.at>
and subject line Re: Bug#538022: PAGER as a pipeline
has caused the Debian Bug report #538022,
regarding PAGER as a pipeline
to be marked as done.
This means that you
RT2870 usb wifi cannot connect (worked on Jessie)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrat
ing general: Touchpad don't work correctly in MacBook 4.1 in Debian 9
with Gnome
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(
.5 GPU hardware acceleretion of my hardware is disable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrat
ternal webcam when the LID is closed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
eneral: Laptop crashing after suspend if device is plugged into
headphone jack
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB:
always change
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
mess
some cases Fira Sans font doesn't render in browsers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system a
mouse disconnects and is reconnected every minute
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator an
utdown problem gui/acpi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea wha
776005,
regarding general: After finished the installation, I rebooted and the
initialization has been stopped
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the p
ortbug: ThinkPad E595 trackpoint physical buttons stopped working
after ipp-usb upgrade on 08/01
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the p
Your message dated Fri, 07 Aug 2020 21:05:15 +0200
with message-id <7ed25d1ff069413744eddb3b32d85fa087178441.ca...@43-1.org>
and subject line Re: [083150171666]
has caused the Debian Bug report #968061,
regarding [083150171666]
to be marked as done.
This means that you claim that the p
Your message dated Sun, 2 Aug 2020 22:41:45 +0200 (CEST)
with message-id
and subject line data gathering required
has caused the Debian Bug report #966622,
regarding general: lock_screen causes blank screen which is onlyresolved with
full power off using button
to be marked as done.
This means
l: USB keyboard stops working after a few seconds due to USB
suspend
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you
drive mount does not show up on desktop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and h
not on current x-win screen
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
pdated debian stretch in my lenovo
G-50-45 laptop it's crashing conatcntly saying Cinnamon is running on fallback
mode before upgrade it was working fine.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibilit
: backports suite-names can't be properly used in sources.list
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If
ainers: problem mit instalation HP DeskJet 2130 all-in-one
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
e clic (graphical problem ?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea wha
owsers except Links2 crash constantly and iceweasel is
broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
134,
regarding general: Laptops's external screen is blank despite still recognised
by Settings>Dispaly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary,
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking
ckages really worth the space savings?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have n
ze the system
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
mess
rocess has a delay of 2-5 minutes bevor the login screen
appears
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
Your message dated Tue, 28 Jul 2020 15:53:28 +0200
with message-id
and subject line Re: security.debian.org: User password is shown in the TTY
has caused the Debian Bug report #865061,
regarding security.debian.org: User password is shown in the TTY
to be marked as done.
This means that you
Your message dated Tue, 28 Jul 2020 15:53:28 +0200
with message-id
and subject line Re: security.debian.org: User password is shown in the TTY
has caused the Debian Bug report #865061,
regarding security.debian.org: User password is shown in the TTY
to be marked as done.
This means that you
d have alternatives for graphical su and sudo (x-su,
x-sudo?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
Your message dated Tue, 28 Jul 2020 15:44:41 +0200
with message-id
and subject line Re: "event based boot system needed to solve use cases"
has caused the Debian Bug report #417118,
regarding "event based boot system needed to solve use cases"
to be marked as done.
This
Your message dated Tue, 28 Jul 2020 15:44:41 +0200
with message-id
and subject line Re: "event based boot system needed to solve use cases"
has caused the Debian Bug report #417118,
regarding fstab doesn't mount external USB-drive, but mount -a does
to be marked as done.
This
Your message dated Tue, 28 Jul 2020 15:40:39 +0200
with message-id
and subject line Re: general: black screen after suspending
has caused the Debian Bug report #838211,
regarding general: black screen after suspending
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 28 Jul 2020 15:39:36 +0200
with message-id
and subject line Re: general: system freeze
has caused the Debian Bug report #837606,
regarding general: system freeze
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
after suspend on acer laptop (only if logged on)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrat
Your message dated Tue, 28 Jul 2020 15:37:54 +0200
with message-id <60db400b892431619e370fb4f7197630033a3838.ca...@43-1.org>
and subject line Re: system crashes using HDMI
has caused the Debian Bug report #827650,
regarding system crashes using HDMI
to be marked as done.
This means that you
Your message dated Tue, 28 Jul 2020 15:35:32 +0200
with message-id <2b39b33da255da2462627227962e4ffa4b0e2656.ca...@43-1.org>
and subject line Re: general: Bluetooth doesn't work
has caused the Debian Bug report #812885,
regarding general: Bluetooth doesn't work
to be marked as d
rectly after automatic suspend
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
eneral: Lenovo G50-30 freezes running debian 4.3.0-0.bpo.1-amd64;
Intel Pentium N3530
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(
res to bits/predefs.h, but no "bits" link
or dir in /usr/include
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If
s from upstream with multiarch-toolchain?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and h
.h(323): catastrophic error: could not open
source file "bits/predefs.h"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If
erning crt1.o, crti.o and crtn.o breaks
building LLVM Trunk
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a
rt for non-multiarch toolchain
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no ide
Your message dated Mon, 27 Jul 2020 18:00:18 +0200
with message-id <10adcf7ba4466553aeb2b50f38a58bde9af46300.ca...@43-1.org>
and subject line Re: Sorting out mail-transport-agent mess
has caused the Debian Bug report #508644,
regarding Sorting out mail-transport-agent mess
to be marked a
arding updates appear in wheezy-security before jessie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system adminis
1 - 100 of 801 matches
Mail list logo
