Control: forwarded -1 https://release.debian.org/transitions/html/auto-re2.html
Uploaded, and it's built on all the release archs.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
Processing control commands:
> forwarded -1 https://release.debian.org/transitions/html/auto-re2.html
Bug #965023 [release.debian.org] transition: re2
Changed Bug forwarded-to-address to
'https://release.debian.org/transitions/html/auto-re2.html' from
I just went through the remaining items on the transition tracker for this
transition
filing bug reports where appropriate.
freewheeling:
sid-only, unrelated FTBFS bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946863
haskell-hopenpgp/haskell-hopenpgp-tools:
haskell-incremental-parser
Processing control commands:
> tags -1 + confirmed
Bug #965023 [release.debian.org] transition: re2
Added tag(s) confirmed.
--
965023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + confirmed
On 2020-07-14 20:25:37 +0200, Sebastian Ramacher wrote:
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-protobuf.html
>
> On 2020-07-14 08:29:21 -0700, Stefano Rivera wrote:
> > Package: release.debian.org
> > Severity: normal
> > User:
Control: forwarded -1 https://release.debian.org/transitions/html/auto-pcl.html
Control: tags -1 + confirmed
On 2020-07-16 16:10:32 +0200, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Hi
Processing control commands:
> forwarded -1 https://release.debian.org/transitions/html/auto-pcl.html
Bug #965124 [release.debian.org] transition: pcl
Set Bug forwarded-to-address to
'https://release.debian.org/transitions/html/auto-pcl.html'.
> tags -1 + confirmed
Bug #965124
On 18 July 2020 22:39:05 BST, Steve McIntyre wrote:
>On Sat, Jul 18, 2020 at 10:12:41PM +0100, Adam Barratt wrote:
>>On Sun, 2020-07-12 at 15:35 +0100, Adam D. Barratt wrote:
>>> Hi Steve,
>>>
>>> On Sun, 2020-07-12 at 12:46 +0100, Steve McIntyre wrote:
>>> > Argh, massive apologies...
>>> >
On Sat, Jul 18, 2020 at 10:12:41PM +0100, Adam Barratt wrote:
>On Sun, 2020-07-12 at 15:35 +0100, Adam D. Barratt wrote:
>> Hi Steve,
>>
>> On Sun, 2020-07-12 at 12:46 +0100, Steve McIntyre wrote:
>> > Argh, massive apologies...
>> >
>> > On Thu, Jun 25, 2020 at 10:38:14AM +0200, Laura Arjona
Adam D. Barratt (2020-07-18):
> Now that stretch EoL is (more or less) out of the way, it would be good
> to get 10.5 done as soon as we sensibly can, so as not to slip too far
> off schedule.
>
> Next weekend is probably a little too soon - I'd at least like to not
> jump straight back into
On Sun, 2020-07-12 at 15:35 +0100, Adam D. Barratt wrote:
> Hi Steve,
>
> On Sun, 2020-07-12 at 12:46 +0100, Steve McIntyre wrote:
> > Argh, massive apologies...
> >
> > On Thu, Jun 25, 2020 at 10:38:14AM +0200, Laura Arjona Reina wrote:
> > > El 15/6/20 a las 18:44, Adam D. Barratt escribió:
>
Processing changes file: heartbleeder_0.1.1-5+b3_ppc64el.changes
ACCEPT
Quoting Adrian Bunk (2020-07-18 10:36:11)
> On Thu, Jul 16, 2020 at 07:27:52PM +0200, Julian Andres Klode wrote:
> >...
> > We have came up with a syntax, one goal being to break parsers and not
> > silently ignore optional deps:
> >
> > Build-Depends: foo? (>= 1) | baz
>
> Any suggestion has
Hey,
On 08.07.20 21:21, Paul Gevers wrote:
> As part of the interim architecture qualification for bullseye, we
> request that DSA, the security team, Wanna build, and the toolchain
> maintainers review and update their list of known concerns for bullseye
> release architectures.
I'd also
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964809,
regarding stretch-pu: package batik/1.8-4+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964777,
regarding stretch-pu: package atril/1.16.1-2+deb9u2
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964727,
regarding stretch-pu: package jackson-databind/2.8.6-1+deb9u6
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964861,
regarding stretch-pu: package glib-networking/2.50.0-1+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964813,
regarding stretch-pu: package debian-security-support/2020.06.21~deb9u1
to be marked as done.
This means that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964764,
regarding stretch-pu: package file-roller/3.22.3-1+deb9u2
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964244,
regarding stretch-pu: package xml-security-c/1.7.3-4+deb9u2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964398,
regarding stretch-pu: package libembperl-perl/2.5.0-10+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964325,
regarding stretch-pu: package compactheader/3.0.0~beta5-2~deb9u1
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964456,
regarding stretch-pu: package roundcube/1.2.3+dfsg.1-4+deb9u6
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #922170,
regarding nmu: Four packages for golang
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964340,
regarding stretch-pu: package sogo-connector/68.0.1-2~deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964411,
regarding stretch-pu: package c-icap-modules/1:0.4.4-1+deb9u2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #963703,
regarding stretch-pu: package gnutls28/3.5.8-5+deb9u5
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964351,
regarding stretch-pu: package intel-microcode/3.20200616.1~deb9u1
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964588,
regarding stretch-pu: package fwupd/0.7.4-2
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #964713,
regarding stretch-pu: package storebackup/3.2.1-2~deb9u1
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #962155,
regarding stretch-pu: package ca-certificates/20200601~deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #962264,
regarding stretch-pu: package ruby2.3/2.3.3-1+deb9u8
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #962256,
regarding stretch-pu: package ruby-json/2.0.1+dfsg-3+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #963693,
regarding stretch-pu: package libexif/0.6.21-2+deb9u4
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #963942,
regarding stretch-pu: package nvidia-graphics-drivers/390.138-1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #962068,
regarding stretch-pu: package dbus/1.10.30-0+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961937,
regarding stretch-pu: package ssvnc/1.0.29-3+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #963614,
regarding stretch-pu: package nfs-utils/1:1.3.4-2.1+deb9u1
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961804,
regarding stretch-pu: package libexif/0.6.21-2+deb9u3
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961945,
regarding stretch-pu: package php-horde/5.2.13+debian0-1+deb9u2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961922,
regarding stretch-pu: package php-horde-gollem/3.0.10-1+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961440,
regarding stretch-pu: package clamav/0.102.3+dfsg-0~deb9u1
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #958995,
regarding stretch-pu: package tzdata/2020a-0+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #956532,
regarding stretch-pu: package php-horde-data/2.1.4-3+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #956537,
regarding stretch-pu: package php-horde-trean/1.1.7-1+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961020,
regarding stretch-pu: package libexif/0.6.21-2+deb9u2
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #958850,
regarding stretch-pu: package gosa/2.7.4+reloaded2-13+deb9u3
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #958953,
regarding stretch-pu: package cups/2.2.1-8+deb9u6
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #956805,
regarding stretch-pu: package megatools/1.9.98-1+deb9u1
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #958192,
regarding stretch-pu: package xdg-utils/1.1.1-1+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #956929,
regarding stretch-pu: package nvidia-graphics-drivers/390.132-1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #961579,
regarding stretch-pu: package erlang/1:19.2.1+dfsg-2+deb9u3
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #956534,
regarding stretch-pu: package php-horde-form/2.0.15-1+deb9u2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #955861,
regarding stretch-pu: package csync2/2.0-8-g175a01c-4+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #955409,
regarding stretch-pu: package tinyproxy/1.8.4-3~deb9u2
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #949367,
regarding stretch-pu: package wpa/2:2.4-1+deb9u6
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #954863,
regarding stretch-pu: package checkstyle/6.15-1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #951564,
regarding stretch-pu: package postfix/3.1.14-0+10debu1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #953123,
regarding stretch-pu: package rake/10.5.0-2+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #955394,
regarding stretch-pu: package libvncserver/0.9.11+dfsg-1.3~deb9u4
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #953745,
regarding stretch-pu: package proftpd-dfsg/1.3.5b-4+deb9u5
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #954664,
regarding stretch-pu: package rails/2:4.2.7.1-1+deb9u2
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #949925,
regarding stretch-pu: package cram/0.7-1+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #948651,
regarding stretch-pu: package neon27/0.30.2-2+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #948650,
regarding stretch-pu: package nginx/1.10.3-1+deb9u3
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #948678,
regarding stretch-pu: package libbusiness-hours-perl/0.13-0+deb9u1
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #948653,
regarding stretch-pu: package mod-gnutls/0.8.2-3+deb9u2
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #935739,
regarding stretch-pu: package sendmail/8.15.2-8+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #949112,
regarding stretch-pu: package xtrlock/2.8+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #893548,
regarding stretch-pu: package python-icalendar/3.8-1+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #893439,
regarding pu: libdbi/0.9.0-4+deb9u2
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #944228,
regarding stretch-pu: package phpmyadmin/4:4.6.6-4+deb9u1
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #927433,
regarding stretch-pu: package gosa/2.7.4+reloaded2-13+deb9u2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #912531,
regarding stretch-pu: package exiv2/0.25-3.1+deb9u2
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #921319,
regarding stretch-pu: package iptables-persistent/1.0.4+nmu2
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #892932,
regarding stretch-pu: package websockify/0.8.0+dfsg1-7+deb9u1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #891657,
regarding stretch-pu: package swt-gtk/3.8.2-3+deb9u1
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #881871,
regarding stretch-pu: package bacula/7.4.4+dfsg-6
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 13:07:00 +0100
with message-id
and subject line Closing requests for fixes included in 9.13 point release
has caused the Debian Bug report #898006,
regarding stretch-pu: package pcl/1.8.0+dfsg1-3
to be marked as done.
This means that you claim that the
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: buster
Severity: normal
ClamAV upstream released 0.102.4 fixing three CVEs. From their news:
- [CVE-2020-3350]
Fix a vulnerability wherein a malicious user could replace a scan target's
directory with
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
The package openhackware builds a single binary blob, ppc_rom.bin,
which is a bios/firmware for old PowerPC machines.
This firmware were used by qemu package (namely, qemu-system-ppc)
to
Your message dated Sat, 18 Jul 2020 09:36:12 +
with message-id
and subject line Bug#964342: Removed package(s) from oldstable
has caused the Debian Bug report #964342,
regarding RM: mathematica-fonts -- RoQA; relies on unavailable download location
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 09:36:28 +
with message-id
and subject line Bug#964883: Removed package(s) from oldstable
has caused the Debian Bug report #964883,
regarding RM: gplaycli -- RoQA; broken by Google API changes
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 09:34:26 +
with message-id
and subject line Bug#961270: Removed package(s) from oldstable
has caused the Debian Bug report #961270,
regarding RM: pdns-recursor -- RoM; unsupported
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 18 Jul 2020 09:33:47 +
with message-id
and subject line Bug#959492: Removed package(s) from oldstable
has caused the Debian Bug report #959492,
regarding RM: getlive -- RoQA; Upstream Dead; Not Working Anymore
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 09:33:04 +
with message-id
and subject line Bug#959377: Removed package(s) from oldstable
has caused the Debian Bug report #959377,
regarding RM: torbirdy -- RoQA; incompatible with newer Thunderbird versions
to be marked as done.
This means that you claim
Your message dated Sat, 18 Jul 2020 09:35:19 +
with message-id
and subject line Bug#964217: Removed package(s) from oldstable
has caused the Debian Bug report #964217,
regarding RM: simpleid-ldap -- RoQA; depends on to-be-removed simpleid
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 09:34:44 +
with message-id
and subject line Bug#961515: Removed package(s) from oldstable
has caused the Debian Bug report #961515,
regarding RM: certificatepatrol -- ROM; No longer usable after xul deprecation,
dead upstream
to be marked as done.
This
Your message dated Sat, 18 Jul 2020 09:34:05 +
with message-id
and subject line Bug#960586: Removed package(s) from oldstable
has caused the Debian Bug report #960586,
regarding RM: selenium-firefoxdriver -- RoQA; does not support firefox beyond
52.0
to be marked as done.
This means that
Your message dated Sat, 18 Jul 2020 09:35:52 +
with message-id
and subject line Bug#964331: Removed package(s) from oldstable
has caused the Debian Bug report #964331,
regarding RM: colorediffs-extension -- RoQA; incompatible with newer
Thunderbird versions
to be marked as done.
This means
Your message dated Sat, 18 Jul 2020 09:33:25 +
with message-id
and subject line Bug#959430: Removed package(s) from oldstable
has caused the Debian Bug report #959430,
regarding RM: libmicrodns -- RoM; security issues
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 18 Jul 2020 09:35:01 +
with message-id
and subject line Bug#964216: Removed package(s) from oldstable
has caused the Debian Bug report #964216,
regarding RM: dynalogin -- RoQA; depends on to-be-removed simpleid
to be marked as done.
This means that you claim that the
Your message dated Sat, 18 Jul 2020 09:32:27 +
with message-id
and subject line Bug#958576: Removed package(s) from oldstable
has caused the Debian Bug report #958576,
regarding RM: kerneloops -- RoQA; service http://oops.kernel.org no longer
available
to be marked as done.
This means that
Your message dated Sat, 18 Jul 2020 09:31:43 +
with message-id
and subject line Bug#956701: Removed package(s) from oldstable
has caused the Debian Bug report #956701,
regarding RM: enigmail -- RoQA; incompatible with stretch's thunderbird
to be marked as done.
This means that you claim that
Your message dated Sat, 18 Jul 2020 09:32:00 +
with message-id
and subject line Bug#958573: Removed package(s) from oldstable
has caused the Debian Bug report #958573,
regarding RM: yahoo2mbox -- RoQA; unusable since 2013
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 18 Jul 2020 09:32:45 +
with message-id
and subject line Bug#958923: Removed package(s) from oldstable
has caused the Debian Bug report #958923,
regarding RM: quotecolors -- RoM; incompatible with newer Thunderbird versions
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 09:28:37 +
with message-id
and subject line Bug#905385: Removed package(s) from oldstable
has caused the Debian Bug report #905385,
regarding RM: weboob -- RoM; unmaintained; already removed from later releases
to be marked as done.
This means that you
Your message dated Sat, 18 Jul 2020 09:29:36 +
with message-id
and subject line Bug#952647: Removed package(s) from oldstable
has caused the Debian Bug report #952647,
regarding RM: firefox-esr/60.9.0esr-1~deb9u1 [armel] -- RoQA; version 68+ no
longer supported on armel
to be marked as done.
Your message dated Sat, 18 Jul 2020 09:29:02 +
with message-id
and subject line Bug#929871: Removed package(s) from oldstable
has caused the Debian Bug report #929871,
regarding RM: simpleid -- RoM; does not work with PHP7
to be marked as done.
This means that you claim that the problem has
1 - 100 of 104 matches
Mail list logo
