Package: ftp.debian.org
Severity: normal
Part of Qt4 removal. Won't be ported to Qt5.
Scott K
On Sat, 03 Mar 2018 21:16:22 +0100 Andreas Beckmann wrote:
> Source: syrthes
> Version: 4.3.0-dfsg1-2
> Severity: serious
> Tags: sid buster
> Justification: blocks python-qwt5-qt4 removal
> Control: block 886779 with -1
>
> Hi,
>
> src:syrthes Build-Depends on python-qwt5-qt4 which is scheduled
Package: ftp.debian.org
Severity: normal
This package depends on both python2 and Qt4 libraries that are being
removed this cycle. It is dead upstream, so it seems extremely unlikely
it will get a Qt5/Python3 port.
cc'ing the package uploaders to see if they have plans to port it
themsleves.
Sc
Package: ftp.debian.org
Severity: normal
Replaced by pyside2 (Qt5).
Scott K
Package: ftp.debian.org
Severity: normal
This was only intended to be provided for one release, so it should have
already been removed.
Scott K
Package: ftp.debian.org
Severity: normal
Dead upstream, part of the Qt-KDE team effort to remove Qt4 in this
cyle.
Scott K
Package: ftp.debian.org
Severity: normal
This is part of the Qt-KDE team removal of Qt4 packages. While amarok
is not entirely dead upstream, a Qt5 release has not yet appeared. This
can be reintroduced later if one ever arrives.
Scott K
On August 11, 2019 5:58:39 PM UTC, Colin Watson wrote:
>On Mon, Aug 05, 2019 at 11:31:54PM +0500, Andrey Rahmatullin wrote:
>> Orphaned, doesn't support Python 2, doesn't have revdeps (checked
>with `dak rm
>> -Rn storm`).
>>
>> No Py3 support upstream either:
>https://bugs.launchpad.net/storm
Package: ftp.debian.org
Severity: normal
[2:47:07 pm] From the packages that I maintain, encuentro can be
removed
Qt4 is on the way out, so this should go.
Scott K
/changelog 2019-07-05 13:16:56.0 +
+++ octavia-4.0.0/debian/changelog 2019-08-09 18:29:45.0 +
@@ -1,3 +1,9 @@
+octavia (4.0.0-4) UNRELEASED; urgency=medium
+
+ * Correct depends for yaml
+
+ -- Scott Kitterman Fri, 09 Aug 2019 18:29:45 +
+
octavia (4.0.0-3) unstable
On Sat, 9 Sep 2017 23:11:23 +0200 Lisandro =?iso-8859-1?Q?
Dami=E1n_Nicanor_P=E9rez?= Meyer wrote:
> Source: tora
> Version: 2.1.3-3
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4-removal
>
>
> Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
> as
On Thu, 10 Jan 2019 11:19:01 + Simon McVittie wrote:
> Source: pyyaml
> Severity: wishlist
>
> pyyaml 4.1 is available.
>
> This version addresses CVE-2017-18342 (
Uploaded 5.1.2-1.
Scott K
On Thu, 11 Jul 2019 10:16:48 +0300 mer...@debian.org wrote:
> Hello,
>
> According to [1] the unsafe loader yaml.UnsafeLoader is still
> vulnerable, and could be used upon request. While strictly speaking the
> vulnerability is fixed by using safe reader by default, I assume
> complete safety can
Package: src:python-torctl
Severity: important
This package looks pretty dead upstream. It's currently blocking me
from dropping python-geoip as part of the python2 removal effort.
Please either port it to python3 or have it removed. If you'd prefer to
have it removed, but don't have time to de
Package: ftp.debian.org
Severity: normal
Python2 only and blocking other python-* removals.
Scott K
Package: src:valinor
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
FAIL: testARMNoneEABIGDB (test.test_outputdir.TestCLIOutputDirectory)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lx
Package: src:salt
Version: 2018.3.4+dfsg1-6
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:python-tablib
Version: 0.12.1-2
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:python-markdown
Version: 3.0.1-3
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:lavacli
Version: 0.9.7-1
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These
Package: src:lava
Version: 2019.01-5
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These a
Package: src:knot
Version: 2.7.6-2
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These are
Package: ftp.debian.org
Severity: normal
Part of python2-rm.
Scott K
Package: ftp.debian.org
Severity: normal
Part of python-rm
Scott K
Package: ftp.debian.org
Severity: normal
Part of python2 remvoval effort.
Scott K
Package: ftp.debian.org
Severity: normal
This one died upstream a long time ago.
Scott K
Package: ftp.debian.org
Severity: normal
python2 binary has been dropped.
Scott K
Package: ftp.debian.org
Severity: important
It is expected that epydoc, which DAK uses for documentation generation
will be removed in the Bullseye release cycle [1] as part of the python2
phase out. The docs need porting to something else.
Scott K
[1] http://bugs.debian.org/932574
Package: ftp.debian.org
Severity: normal
Obsolete libs.
Scott K
On July 28, 2019 6:00:28 PM UTC, "Michael Müller" wrote:
>Package: kmail
>Version: 4:18.08.3-1
>Severity: normal
>
>Dear Maintainer,
>
>when printing mails, kmail only prints blank pages, also when printing
>to PDF or in the pre-view.
>
I have run into this problem too, but I hadn't gotten arou
Package: lintian
Version: 2.16.0
Severity: normal
There are several python3 packages that ship python scripts in
usr/lib/python3/dist-packages. Currently this trips the test. As far
as I can tell, it's a false positive in all such cases (since files in
dist-packages aren't supposed to be called
Package: ftp.debian.org
Severity: normal
Not picked up in cruft report.
Scott K
Package: ftp.debian.org
Severity: normal
Not picked up by cruft report.
Scott K
On Sunday, July 21, 2019 4:15:43 PM EDT Jonathan Wiltshire wrote:
> On Sun, Jul 21, 2019 at 08:00:20PM +0000, Scott Kitterman wrote:
> > Thanks. It looks plausible. As doko mentioned, it'll need the same for
> > build depends.
>
> It already has the .build-depends, th
Thanks. It looks plausible. As doko mentioned, it'll need the same for build
depends.
Scott K
On Tuesday, July 9, 2019 11:50:26 AM EDT Matthias Klose wrote:
> On 09.07.19 00:31, Scott Kitterman wrote:
> > Ben file:
> >
> > title = "python-defaults";
> > is_affected = .depends ~
> > /python|python-minimal|python-dev|libpython-dev|libpython-stdl
On July 9, 2019 8:19:03 AM UTC, Jonathan Wiltshire wrote:
>Control: tag -1 moreinfo
>
>Hi,
>
>On Mon, Jul 08, 2019 at 06:31:50PM -0400, Scott Kitterman wrote:
>> title = "python-defaults";
>> is_affected = .depends ~
>/python|python-minimal|python-dev|l
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
The Debian Python teams are working to push early for reduction/removal
of our python(2) packages with the goal of releasing bullseye with
python3 only. is_bad includes all the binaries
On July 8, 2019 9:10:54 AM UTC, Gordon Ball wrote:
>Those that I'm involved with:
>
>* xonsh is compatibile with either prompt_toolkit 1.x or 2.x
>* updating jupyter_console -> 6 is blocked on prompt_toolkit 2
>* updating ipython -> 7 is blocked on prompt_toolkit 2
>
>The ipython case is compli
Package: ftp.debian.org
Severity: normal
As described in the buster release notes, these packages are not to be
released with bullseye.
Scott K
-resources:
+- For postfix-policyd-spf-python (Closes: #928487)
+- For pyspf-milter (Closes: #928488)
+
+ -- Scott Kitterman Sun, 05 May 2019 18:07:33 -0400
+
spf-engine (2.9.0-3) unstable; urgency=medium
* Install pyspf-milter config file in /etc/pyspf-milter/pyspf-milter.conf
diff -Nru
Package: pyspf-milter
Version: 2.9.0-3
Severity: serious
Justification: Policy 3.5
# /usr/bin/pyspf-milter
Traceback (most recent call last):
File "/usr/bin/pyspf-milter", line 6, in
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'
Missing dep
On April 26, 2019 2:10:36 AM UTC, Ryo IGARASHI wrote:
>Hi, Bernhard,
>
>Thank you for the workaround. Now that I can launch QT application on
>my machine.
>
>As this issue only affects WSL environment, I don't think this is an
>RC bug, but I will
>let the maintainers set the proper severities.
Package: ubuntu-dev-tools
Version: 0.166
Severity: important
The requestsync script uses the DNS module (python-dns). I plan to remove
this package during the Bullseye development cycle. DNS is available for
Python 3 (python3-dns). Please port to Python 3. At a glance, it doesn't
look like a d
Package: src:tumgreyspf
Version: 1.36-4.1
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure tumgreyspf can stay in Debian, please
port it to pyth
Package: src:zabbix-cli
Version: 1.7.0-1
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure zabbix-cli can stay in Debian, please
update it to the
Package: src:rekall
Version: 1.6.0+dfsg-2
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure rekall can stay in Debian, please
update it to the py
Package: src:ifupdown2
Version: 1.2.5-1
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure ifupdown2 can stay in Debian, please
port it to python3
Package: src:hash-slinger
Version: 2.7-1
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure hash-slinger can stay in Debian,
please port it to pyt
Package: src:grr
Version: 3.1.0.2+dfsg-6
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure grr can stay in Debian, please port
it to python3 (I s
Package: ganeti-2.16
Version: 2.16.0-5
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure ganetia can stay in Debian, please
port it to python3.
On Mon, 15 Apr 2019 02:00:36 -0400 Scott Kitterman
wrote:
> Package: bley
> Version: 2.0.0-2
> Severity: important
>
> Python2.7 will go out of upstream security support during the Bullseye
> development cycle. It is not safe to assume it will be included in the
> next re
Package: criu
Version: 3.11-2
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure criu can stay in Debian, please
update it to the python3 version
Package: ftp.debian.org
Severity: normal
Note: This shouldn't be done until after Buster releases. Python2.7 is
supported in Buster and there are no significant bugs that would suggest the
package shouldn't be in Buster.
Scott K
Package: automx
Version: 0.10.0-2.1
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure automx can stay in Debian, please
update it to the python3
Package: bley
Version: 2.0.0-2
Severity: important
Python2.7 will go out of upstream security support during the Bullseye
development cycle. It is not safe to assume it will be included in the
next release, so if you want to be sure bley can stay in Debian, please port
it to python3.
Personally,
On Saturday, April 13, 2019 09:58:15 PM Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Mon, 2019-04-01 at 14:30 -0400, Scott Kitterman wrote:
> > This is the next in a series. It contains upstream bug fix releases
> > 3.1.10,
> > 3.1.11, and 3.1.12. I
Package: release-notes
Severity: normal
Tags: patch
Both spf-milter-python and dkim-milter-python will be superseded by pyspf-
milter and dkimpy-milter in Bullseye. Buster is the release for users to
switch since both are provided. Proposed release notes below.
The sp
This is a show stopper bug for any package that uses the functionality.
Bumping to serious.
Scott K
It's possible I jumped the gun on the bug report. I'll try and investigate
further.
Scott K
On Wednesday, April 10, 2019 03:04:43 PM Norbert Preining wrote:
> Hi
>
> > gzip: warning: GZIP environment variable is deprecated; use an alias or
> > script^M
> I don't see a place where we set this in texinfo, could it be that your
> /etc/environment(.d)
> contains something like this?
>
Package: ispell
Version: 3.4.00-6
Severity: normal
>From the apt term log of a Stretch -> Buster upgrade done today:
ispell-autobuildhash: Processing 'american' dict.^M
gzip: warning: GZIP environment variable is deprecated; use an alias or script^M
ispell-autobuildhash: Processing 'british' dict
Package: install-info
Version: 6.5.0.dfsg.1-4
Severity: normal
Saw this in the apt term log from a Stretch -> Buster upgrade today:
Setting up libxmlrpc-lite-perl (0.717-2) ...^M
Processing triggers for sgml-base (1.29) ...^M
Processing triggers for install-info (6.5.0.dfsg.1-4+b1) ...^M
gzip: wa
Package: clamav-freshclam
Version: 0.100.2-1
Severity: normal
Stretch -> Buster upgrade today:
Setting up clamav-freshclam (0.101.2+dfsg-1) ...^M
Installing new version of config file /etc/apparmor.d/usr.bin.freshclam ...^M
Installing new version of config file
/etc/network/if-down.d/clamav-fres
/etc/pyspf-milter/pyspf-milter.conf
+and update the service file so it is used (Closes: #926752)
+
+ -- Scott Kitterman Wed, 10 Apr 2019 00:28:09 -0400
+
spf-engine (2.9.0-2) unstable; urgency=high
* Add Breaks/Replaces for python3-spf-engine to fix upgrade issues (Closes:
diff -Nru spf-engine-2.
Package: pyspf-milter
Version: 2.9.0-2
Severity: serious
Justification: causes non-serious data loss
Sigh,
As packaged, no configuration file is installed and on startup it attempts to
read the configuration from /usr/local/etc instead of /etc. This was masked
by leftover /usr/local bits I had f
On Monday, April 08, 2019 04:50:31 PM ana wrote:
> Thanks for the update on this. It would be a shame to drop the package
> entirely from Debian. Have had a look at the packaging on salsa and I'm
> happy to take over. I would need DM permissions on it to make uploads.
OK. Please add yourself to u
On Monday, April 08, 2019 10:38:40 AM Clint Adams wrote:
> On Sat, Apr 06, 2019 at 12:59:15AM +0200, Stefan Schörghofer wrote:
> > Please remove the package ytalk due to following reasons:
> > - Package is orphaned since > 1500 days
> > - lates upstream release is from 2005
> > - Popcon is < 250
On Mon, 01 Apr 2019 21:22:14 -0400 Scott Kitterman
wrote:
> Package: ftp.debian.org
> Severity: normal
>
> This package has never been widely used. I'm no longer a Softlayer
customer,
> so I can't really maintain it properly anymore. Given the upstream churn,
&g
Package: src:lexicon
Version: 3.0.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
I'm filing this as a FTBFS bug, not because the package FTBFS now, but because
it will once python-softlayer is removed (See #926209). The package is not
difficul
Package: lintian
Version: 2.12.0
Severity: normal
Reporting this as a bug against the package because the web site says:
"Comments about these web pages? Please use reportbug to report a bug against
the lintian package."
I am 100% certain that postfix is not lintian clean, yet it isn't on
lintia
On Mon, 01 Apr 2019 14:57:01 -0400 Scott Kitterman
wrote:
> On Mon, 01 Apr 2019 14:30:04 -0400 Scott Kitterman
> wrote:
> > Package: release.debian.org
> > Severity: normal
> > Tags: stretch
> > User: release.debian@packages.debian.org
> > Usertags: pu
&
Package: ftp.debian.org
Severity: normal
This package has never been widely used. I'm no longer a Softlayer customer,
so I can't really maintain it properly anymore. Given the upstream churn,
this package isn't really suitable for maintenance by QA upload.
Scott K
On Mon, 01 Apr 2019 14:30:04 -0400 Scott Kitterman
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
>
> This is the next in a series. It contains upstream bug fix releases 3.1.10,
> 3.1
g that has been extensively tested
by the postfix community, most of the changes are documentation. The other
code changes seem reasonably compact and low risk.
Usual fix list:
[ Scott Kitterman ]
* Add detailed smarthost instructions to README.Debian. Thanks to Celejar
for the input.
mismatch. Therefore, idle cached connections
+ could exhaust LMTP server resources, resulting in two-second
+ pauses between email deliveries. This problem was investigated
+ by Juliana Rodrigueiro. File: smtp/smtp_connect.c.
+
+ -- Scott Kitterman Mon, 01 Apr 2019 13:27:26 -0
On Monday, April 01, 2019 09:25:17 AM Johannes Schauer wrote:
> Control: tag -1 - moreinfo
>
> Quoting Scott Kitterman (2019-04-01 06:26:13)
>
> > > Alright, I think it's time to pull the plug. :(
> > >
> > > Reassigning and retitling accordingly.
On April 1, 2019 10:30:58 AM UTC, Chris Lamb wrote:
>Hi Scott,
>
>> > > I'm reasonably confident that clamav testfiles don't need
>hardening
>> > > features, so [1] seems pretty pointless.
>> >
>> > I don't disagree at all here but I'm wondering how Lintian would be
>> > able to detect that th
On Monday, April 01, 2019 04:45:44 AM Chris Lamb wrote:
> tags 926060 + moreinfo
> thanks
>
> Hi Scott,
>
> > I'm reasonably confident that clamav testfiles don't need hardening
> > features, so [1] seems pretty pointless.
>
> I don't disagree at all here but I'm wondering how Lintian would be
>
On Tue, 19 Mar 2019 11:03:37 + wmwmw wrote:
> Package: python3-celery
> Version: 4.2.1-3
> Severity: grave
> Justification: renders package unusable
>
> Should be fixed in the upstream, but current versions in repository are
incompatible.
>
> https://github.com/celery/celery/issues/5175
Fi
Package: lintian
Version: 2.11.0
Severity: normal
I'm reasonably confident that clamav testfiles don't need hardening features,
so [1] seems pretty pointless.
Scott K
[1]
https://lintian.debian.org/maintainer/pkg-clamav-de...@lists.alioth.debian.org.html#clamav
clamav-testfiles
E portable
This removal is done now.
Documenting the cruft left behind for the future:
# Broken Depends:
ecflow: python3-ecflow [kfreebsd-amd64 kfreebsd-i386]
gdb: gdb [hurd-i386]
gdb-multiarch [hurd-i386]
glom: glom [kfreebsd-amd64 kfreebsd-i386]
libglom-1.30-0 [kfreebsd-amd64 kfreebsd-i386]
lib
On March 30, 2019 6:10:40 PM UTC, Giovanni Mascellani wrote:
>user debian-rele...@lists.debian.org
>
>usertags 915319 + bsp-2019-03-fr-paris
>tags 915319 + patch
>thank you
>
>Hi,
>
>I did some further diagnosis on this bug: the reason why CMake fails to
>discover libsmbclient is because CMake
On Sat, 30 Mar 2019 04:01:40 -0400 Scott Kitterman
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Clamav upstream has just done a security release. They did do a 0.100
update
>
On Wed, 27 Mar 2019 19:43:13 + "Adam D. Barratt" wrote:
> On Wed, 2019-03-27 at 19:54 +0100, Sebastian Andrzej Siewior wrote:
> > On 2019-03-10 23:55:55 [+0100], To sub...@bugs.debian.org wrote:
> > > We would like to update clamav in stable to 0.101.1 which is the
> > > latest
> > > release p
Package: src:groonga
Version: 9.0.1-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
Debian Policy (3.3) requires a working maintainer email address, which groonga
does not currently have:
This message was created automatically by mail delivery software.
A message that you sent co
Package: src:schema2ldif
Version: 1.3-2
Severity: serious
Justification: Policy 3.3
Policy 3.3 requires a working email address for the maintainer.
Maintainer notifications from ftp-master.debian.org are failing:
This message was created automatically by mail delivery software.
A message that
Package: src:lirc
Version: 0.10.1-5.1
Severity: grave
Justification: renders package unusable
Removal of the obselete packages dropped in the most recent upload is
blocked by:
- broken Build-Depends:
audacious-plugins: liblircclient-dev
bino: liblircclient-dev
geeqie: liblircclient-
On Monday, March 25, 2019 02:17:15 PM Thorsten Glaser wrote:
> On Mon, 25 Mar 2019, Emmanuel Bourg wrote:
> > Please remove the tomcat8 package from testing and unstable (not
> > experimental). This package has been replaced by tomcat9 for Buster.
>
> Please don’t, tomcat9 has no sysvinit script,
On Sun, 24 Mar 2019 16:04:02 -0400 Scott Kitterman
wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Please unblock package postfix
>
> About the time we were switching to postfix 3.4 in Bus
On Mon, 25 Mar 2019 07:10:22 -0700 James Bottomley
wrote:
> On Tue, 19 Mar 2019 21:53:41 +0000 Scott Kitterman m> wrote:
> > This is fixed in a new upstream release that I expect to package
> > shortly.
>
> Me too on being affected by this and waiting to the fix
by left-over debris from the 20181226
+ TLS library overhaul. Scott Kitterman. File: tls/tls_dane.c.
+ Closes: #924183
+- Bugfix (introduced: Postfix-1.0.1): null pointer read, while
+ logging a warning after a corrupted bounce log file. File:
+ global/bounce_log.c.
+- Bu
This is fixed in a new upstream release that I expect to package shortly.
Scott K
On March 19, 2019 6:24:30 PM UTC, Thorben Thuermer wrote:
>Package: postfix
>Version: 3.4.1-1
>Severity: important
>
>Dear Maintainer,
>
>as also reported upstrean at
>https://marc.info/?t=15530176323&r=1&w=2
>
Yes. It is. I'm waiting a bit to see if there's another quick release before
updating in Debian.
Upstream used the Debian provided patch to resolve the issue.
Scott K
On March 13, 2019 9:21:34 PM UTC, MK wrote:
>Postfix stable release 3.4.3 (and actually in 3.4.2, but that missed a
>linux5 c
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package celery
Celery 4.2.1-3 fixes RC bug #923719.
I didn't upload this package, but I'm filing the unblock request because the
uploader asked me to due to lack of time thi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package pyglet
Unfortunately, due to my miscalculation by a few hours of when the freeze
would hit, unstable is now blocked for pyglet for future uploads to support
buster.
On Sun, 10 Mar 2019 00:52:35 +0100 Andreas Beckmann wrote:
> On Fri, 15 Feb 2019 12:52:13 -0500 Scott Kitterman
> wrote:
> > See the package Suggests. This is intentional.
>
> There is no package in sid that ships a mpris-quassel binary.
Thanks. Looks like I got it mixe
On Wednesday, March 06, 2019 07:39:07 PM Jonathan Wiltshire wrote:
> Control: tag -1 moreinfo
>
> On Fri, Mar 01, 2019 at 02:46:41PM -0500, Scott Kitterman wrote:
> > Given the outstanding track record this upstream has for delivering
> > mature,
> > well tested co
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package postfix
I realize 'unblock' is slightly jumping the gun, but I would like to solicit
feedback/agreement from the release team before doing something non-minimal
right
Package: ftp.debian.org
Severity: normal
Out of date and still depends on obsolete Qt4.
701 - 800 of 3039 matches
Mail list logo
