Your message dated Tue, 04 Feb 2025 07:49:19 +
with message-id
and subject line Bug#1083384: fixed in fabric 2.6.0-4
has caused the Debian Bug report #1083384,
regarding fabric: (build-)depends on deprecated module python3-pkg-resources
to be marked as done.
This means that you claim that the
Your message dated Tue, 04 Feb 2025 07:04:33 +
with message-id
and subject line Bug#1094724: fixed in plplot 5.15.0+dfsg2-13
has caused the Debian Bug report #1094724,
regarding plplot: Please update Homepage
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Tue, 04 Feb 2025 07:04:33 +
with message-id
and subject line Bug#1094696: fixed in plplot 5.15.0+dfsg2-13
has caused the Debian Bug report #1094696,
regarding plplot: FTBFS on all architectures
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 07:04:10 +
with message-id
and subject line Bug#1093030: fixed in libdata-streamserializer-perl 0.07-2
has caused the Debian Bug report #1093030,
regarding ITS: libdata-streamserializer-perl
to be marked as done.
This means that you claim that the problem h
Your message dated Tue, 04 Feb 2025 06:49:56 +
with message-id
and subject line Bug#1094890: fixed in xfce4-session 4.20.0-2
has caused the Debian Bug report #1094890,
regarding xfce4-session: Remove alternate Recommends: gnome-screensaver
to be marked as done.
This means that you claim that
Your message dated Tue, 04 Feb 2025 06:49:56 +
with message-id
and subject line Bug#1093378: fixed in xfce4-session 4.20.0-2
has caused the Debian Bug report #1093378,
regarding xfce4-session: xflock4 now uses gdbus without depending on
libglib2.0-bin
to be marked as done.
This means that yo
Your message dated Tue, 04 Feb 2025 06:49:56 +
with message-id
and subject line Bug#1092334: fixed in xfce4-session 4.20.0-2
has caused the Debian Bug report #1092334,
regarding xflock4 dependency missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 04 Feb 2025 06:49:56 +
with message-id
and subject line Bug#1064099: fixed in xfce4-session 4.20.0-2
has caused the Debian Bug report #1064099,
regarding xfce4-session should recommend or suggest libglib2.0-bin for xflock4
to work
to be marked as done.
This means that
Your message dated Tue, 04 Feb 2025 06:21:11 +
with message-id
and subject line Bug#1093301: fixed in qgis 3.34.15+dfsg-2
has caused the Debian Bug report #1093301,
regarding qgis: Get rid of qtwebkit dependency
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Tue, 04 Feb 2025 05:19:35 +
with message-id
and subject line Bug#1078635: fixed in puppetserver 8.7.0-3
has caused the Debian Bug report #1078635,
regarding puppetserver: will FTBFS during trixie support period
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 04 Feb 2025 05:19:35 +
with message-id
and subject line Bug#1092567: fixed in puppetserver 8.7.0-3
has caused the Debian Bug report #1092567,
regarding puppetserver: update dependency version on ruby-concurrent (1.3.4 in
experimental)
to be marked as done.
This means
Your message dated Tue, 04 Feb 2025 05:19:35 +
with message-id
and subject line Bug#1078635: fixed in puppetserver 8.7.0-3
has caused the Debian Bug report #1078635,
regarding puppetserver: FTBFS: make[1]: *** [debian/rules:64:
override_dh_auto_test] Error 1
to be marked as done.
This means
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #683408,
regarding please package pcretest
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #528691,
regarding serverstats crashes on cron update
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #900625,
regarding Bug still present in stretch: [Bug#865987: libpcre3: Drop hard-coded
Pre-Depends on deprecated multiarch-support]
t
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #904506,
regarding pcre3: FTBFS on most architectures: more STL symbols disappear
to be marked as done.
This means that you claim that
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #677106,
regarding pcreprecompile(3): Macro ".sh" not found in the manual
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #858678,
regarding pcre3: CVE-2017-7245
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #827564,
regarding pcre3: Stack corruption from crafted pattern
to be marked as done.
This means that you claim that the problem has b
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #858679,
regarding pcre3: CVE-2017-7246
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #840354,
regarding src:pcre3: FTBFS on powerpc (G4 CPU)
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #803746,
regarding src:pcre3: Please honour "nocheck" or "notest" in DEB_BUILD_OPTIONS
to be marked as done.
This means that you claim
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #797062,
regarding pcre3: Please ship pcretest again
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #796670,
regarding pcre3: unhelpful README.Versioning.libtool
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #787641,
regarding pcre3: CVE-2015-3217
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #436277,
regarding pcregrep: unknown option bit(s) set
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #796663,
regarding pcre3: please add Homepage field
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #746165,
regarding libpcre3: please automatically restart init in postinst
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #649733,
regarding php5-cgi: Segmentation fault in preg_replace()
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #555808,
regarding libpcre3: segfault on matching certain regexes with large input
to be marked as done.
This means that you claim tha
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #552002,
regarding obsolete package description
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #528691,
regarding serverstats: update.php crashes while collecting CPU stats
to be marked as done.
This means that you claim that the
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #550185,
regarding pcregrep: linefeed matching with '-M': '2\n3' works, '(*CR)2.3' kinda
works, '(*ANY)2.3' doesn't
to be marked as do
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #498344,
regarding pcregrep: option to filter non-printable characters from contents
to be marked as done.
This means that you claim t
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #448388,
regarding allow any record separator
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #520719,
regarding pcre3: Stack Overflow with repeating Look-Aheads
to be marked as done.
This means that you claim that the problem h
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #512928,
regarding libpcre3-dev fails to install due to unmet dependencies
to be marked as done.
This means that you claim that the pr
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #476419,
regarding libpcre3: stack overflow via certain regular expressions
to be marked as done.
This means that you claim that the p
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #393687,
regarding libpcre3: upgrade to 6.7 causes "subpattern too long" errors
to be marked as done.
This means that you claim that t
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #312692,
regarding libpcre3-dev: pcreposix.h ==> pcre/regex.h
to be marked as done.
This means that you claim that the problem has bee
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #392363,
regarding dokuwiki: PHP preg_match() errors on page SAVE
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #395103,
regarding libpcre3-dev: should provide a pkg-config file for libpcrecpp
to be marked as done.
This means that you claim that
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #380725,
regarding incompatible soversion
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #392363,
regarding dokuwiki: Fails to save changes upon spam check
to be marked as done.
This means that you claim that the problem ha
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #1072565,
regarding pcregrep: fails to open very long filenames
to be marked as done.
This means that you claim that the problem has b
Your message dated Tue, 04 Feb 2025 03:51:22 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #1094807,
regarding RM: pcre3 -- ROM; Long obsolete
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #1071970,
regarding pcre3 should not be part of trixie
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 03:51:39 +
with message-id
and subject line Bug#1094807: Removed package(s) from unstable
has caused the Debian Bug report #1063571,
regarding libpcre3: move libraries to /usr (DEP17)
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #995808,
regarding --help does not mention required --enable-local-file-access
to be marked as done.
This means that you claim that th
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #540988,
regarding wondershaper: add ppp/ip-*.d scripts
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #953518,
regarding wkhtmltopdf: crash on alpha and ppc64
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #872336,
regarding wkhtmltopdf doesn't work without X (exit status code 134)
to be marked as done.
This means that you claim that the
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #930076,
regarding wkhtmltopdf ignores --page-height option.
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #885833,
regarding wkhtmltopdf ignores header/footer options ("using unpatched qt")
to be marked as done.
This means that you claim th
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #1082601,
regarding wkhtmltopdf: The “--header-left '[webpage]'” option has no effect
to be marked as done.
This means that you claim
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #811085,
regarding --disable-smart-width not supported
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #806674,
regarding wkhtmltopdf ignores /etc/papersize
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #545826,
regarding wkhtmltopdf: Can only process one html file at a time
to be marked as done.
This means that you claim that the prob
Your message dated Tue, 04 Feb 2025 03:41:13 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #1091821,
regarding RM: wkhtmltopdf -- RoQA; upstream dead; depends on qtwebkit
to be marked as done.
This means that you claim that t
Your message dated Tue, 04 Feb 2025 03:41:18 +
with message-id
and subject line Bug#1091821: Removed package(s) from unstable
has caused the Debian Bug report #613141,
regarding wkhtmltopdf: SIGBUS on sparc
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 04 Feb 2025 03:32:42 +
with message-id
and subject line Bug#1094639: Removed package(s) from unstable
has caused the Debian Bug report #1094631,
regarding abydos: FTBFS with numpy 2.x
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 04 Feb 2025 03:32:34 +
with message-id
and subject line Bug#1094639: Removed package(s) from unstable
has caused the Debian Bug report #1094639,
regarding RM: abydos -- ROM; abandoned upstream, no longer required as a
dependency
to be marked as done.
This means that y
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #924011,
regarding wondershaper: README.Debian: Suggest using $IFACE in
/etc/network/interfaces reference
to be marked as done.
This
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #461560,
regarding wondershaper: allow setting high priority ports also (ssh, ntp, etc.)
to be marked as done.
This means that you cla
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #848571,
regarding O: wondershaper -- Easy to use traffic shaping script
to be marked as done.
This means that you claim that the prob
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #795874,
regarding wondershaper: Hardcoded bandwidth limit
to be marked as done.
This means that you claim that the problem has been d
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #797050,
regarding wondershaper: Please add a NetworkManager script and instructions
to be marked as done.
This means that you claim t
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #651586,
regarding wondershaper: Prioritize DNS traffic
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #616034,
regarding wondershaper: root CBQ bandwidth needs to be bigger
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #384536,
regarding wondershaper: add config scripts for /etc/network
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #440274,
regarding wondershaper: limits incoming traffic although a higher value is set
on start
to be marked as done.
This means tha
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #256754,
regarding wondershaper: Needs a benchmark>>autoconfigure script.
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #348715,
regarding wondershaper: [PATCH] Split default class into 5 based on packet size
and reduce child class rates to be inclusive
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #303520,
regarding wondershaper: Please add a --dry-run option
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #308070,
regarding Reenabling the NOPRIO* options of wondershaper. Some more informative
output.
to be marked as done.
This means tha
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #253554,
regarding Please use something like /etc/default/wondershaper
to be marked as done.
This means that you claim that the proble
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #256461,
regarding wondershaper: Option to limit range of rules?
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #253790,
regarding wondershaper: use the HTB version of the Wondershaper, not the CBQ
version
to be marked as done.
This means that y
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #253385,
regarding wondershaper: more advanced, but complex, option parsing
to be marked as done.
This means that you claim that the p
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #253554,
regarding doesn't let you set the NOPRIOHOSTSRC etc variables without patching
the file in /sbin/wondershaper
to be marked as
Your message dated Tue, 04 Feb 2025 03:23:47 +
with message-id
and subject line Bug#1095044: Removed package(s) from unstable
has caused the Debian Bug report #1095044,
regarding RM: ring -- RoQA; superseded by source package jami
to be marked as done.
This means that you claim that the probl
Your message dated Tue, 04 Feb 2025 03:24:16 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #1095040,
regarding RM: wondershaper -- RoQA; unmaintained, and broken on kernel 6.3-rc1
and later
to be marked as done.
This means t
Your message dated Tue, 04 Feb 2025 03:25:31 +
with message-id
and subject line Bug#1094954: Removed package(s) from unstable
has caused the Debian Bug report #1094954,
regarding RM: nixnote2 -- RoQA; Orphaned; Depends on obsolete QtWebkit
to be marked as done.
This means that you claim that
Your message dated Tue, 04 Feb 2025 03:25:33 +
with message-id
and subject line Bug#1094954: Removed package(s) from unstable
has caused the Debian Bug report #1093528,
regarding nixnote2: Unmaintained upstream
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 04 Feb 2025 03:24:58 +
with message-id
and subject line Bug#1094970: Removed package(s) from unstable
has caused the Debian Bug report #1094970,
regarding RM: ruby-faraday-middleware -- ROM; RC-buggy, leaf package, obsoleted
with ruby-faraday 2
to be marked as done.
T
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #1006279,
regarding Please update to latest release 1.4.1 including configuration file
and systemd support
to be marked as done.
This
Your message dated Tue, 04 Feb 2025 03:25:33 +
with message-id
and subject line Bug#1094954: Removed package(s) from unstable
has caused the Debian Bug report #1064912,
regarding O: nixnote2 -- Open Source Evernote client
to be marked as done.
This means that you claim that the problem has be
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #1089931,
regarding wondershaper: does not work at all with newer Linux versions (CBQ net
scheduler)
to be marked as done.
This means
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #1041584,
regarding Consider switching to wondershaper 1.4.1
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 03:24:31 +
with message-id
and subject line Bug#1095040: Removed package(s) from unstable
has caused the Debian Bug report #1067658,
regarding Update source link to package recent software version
to be marked as done.
This means that you claim that the pro
Your message dated Tue, 04 Feb 2025 03:24:59 +
with message-id
and subject line Bug#1094970: Removed package(s) from unstable
has caused the Debian Bug report #1025092,
regarding ruby-faraday-middleware fails to rebuild after updating ruby-faraday
to be marked as done.
This means that you cla
Your message dated Tue, 4 Feb 2025 11:20:16 +0800
with message-id <8db8485f-d263-4075-bcd7-9092e56e3...@gmail.com>
and subject line Re: Bug#1093500: ipxe: /etc/grub.d/20_ipxe should produce a
separate entry for the EFI binary
has caused the Debian Bug report #1093500,
regarding ipxe: /etc/grub.d/2
Your message dated Tue, 04 Feb 2025 03:19:32 +
with message-id
and subject line Bug#1095060: Removed package(s) from unstable
has caused the Debian Bug report #1095053,
regarding ITS: apache2-mod-xforward
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 04 Feb 2025 03:19:04 +
with message-id
and subject line Bug#1095069: Removed package(s) from unstable
has caused the Debian Bug report #1095069,
regarding RM: safe -- ROM; not in use, low popcon
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 03:18:37 +
with message-id
and subject line Bug#1095115: Removed package(s) from unstable
has caused the Debian Bug report #1095115,
regarding RM: roct-thunk-interface [armel armhf i386 mips64el riscv64 s390x] --
ANAIS; The architectures are limited in the
Your message dated Tue, 04 Feb 2025 03:19:30 +
with message-id
and subject line Bug#1095060: Removed package(s) from unstable
has caused the Debian Bug report #1095060,
regarding RM: apache2-mod-xforward -- ROM; Forgot to drop together with it's
rdepends long ago
to be marked as done.
This m
Your message dated Tue, 04 Feb 2025 03:19:05 +
with message-id
and subject line Bug#1095069: Removed package(s) from unstable
has caused the Debian Bug report #1034669,
regarding libsafe-dev: Update the package to 1.1.0
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 04 Feb 2025 03:19:32 +
with message-id
and subject line Bug#1095060: Removed package(s) from unstable
has caused the Debian Bug report #1081626,
regarding apache2-mod-xforward: maybe interesting edit on original repo
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 1094990 3.7-4
Bug #1094990 [libselinux1] puppet crash on trixie
Marked as fixed in versions libselinux/3.7-4.
Bug #1094990 [libselinux1] puppet crash on trixie
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you n
Your message dated Mon, 03 Feb 2025 20:35:22 -0500
with message-id <83cyfyjxut@scm.rf.org>
and subject line libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
has caused the Debian Bug report #1059874,
regarding libuhd4.6.0: Segfault in gqrx related to libuhd 4.6.0
to be marked as done.
Thi
1 - 100 of 180 matches
Mail list logo
