On December 19, 2018 7:18:42 AM UTC, Paul Wise wrote:
>On Wed, 19 Dec 2018 01:00:43 +0100 Chris Lamb wrote:
>
>> Nobody is doubting the value here, one just has to square that with
>> the idea that Lintian being too pedantic, noisy or making the wrong
>> priority choices is bad for
Package: lintian
Version: 2.5.117
Severity: normal
The appstream-metadata-missing-modalias-provide relates to a nice to have
feature. Lintian treating this at a "Warning" level seems excessive for
something that's completely optional. Info seems right.
Scott K
Package: live-wrapper
Version: 0.7
Severity: important
The vmdebootstrap maintainer has a strong preference for the package to be
removed from Debian [1]. live-wrapper is the only remaining user. Pleae
port it to use something else.
Scott K
[1]
On Wed, 05 Dec 2018 07:43 -0500 Scott Kitterman wrote:
> On Tue, 4 Dec 2018 19:11:33 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?=
> wrote:
> > severity nn normal
> > reassign nn ftp.debian.org
> > retitle nn RM: aolserver4 -- RoQA; unmaintained upstream, al
On Tue, 17 May 2016 15:08:02 +0200 Andreas Beckmann wrote:
> Source: postfix
> Version: 3.1.0-3
> Severity: important
>
> Hi,
>
> postfix FTBFS on kfreebsd since version 3.0.x:
>
> https://buildd.debian.org/status/fetch.php?pkg=postfix=kfreebsd-i386=3.1.0-3=1460572384
>
Package: wnpp
Severity: normal
Neither of the current uploaders have time/interest in continuing to work on
this package (in my case, I've just orphaned the rdepend that led me to
package it in the first place).
This package does not take alot of maintenance. Upstream is either dead or
sleeping
On Wednesday, December 12, 2018 05:00:32 AM Diederik de Haas wrote:
> On woensdag 12 december 2018 04:47:37 CET Scott Kitterman wrote:
> > > My reaction was in response to "DAEMON_OPTS is never defined"
> >
> > OK. I guess I should have been clearer:
> >
On Wednesday, December 12, 2018 04:43:26 AM Diederik de Haas wrote:
> On woensdag 12 december 2018 02:48:25 CET Scott Kitterman wrote:
> > >It is defined in /etc/init.d/quasselcore (with value "", but one can
> > >change that)
> >
> > Right, but that's
On December 12, 2018 1:09:17 AM UTC, Diederik de Haas
wrote:
>On Tue, 11 Dec 2018 11:03:06 -0500 Scott Kitterman
>
>wrote:
>> What does this accomplish? As far as I can see, DAEMON_OPTS is never
>defined
>> (defaults isn't sourced and AIUI there's no easy way to do
Updating to orphan the package, fundamentally I've lost motivation on this
package. I still think it's important, but I don't have the time/priority for
it. I should also have mentioned there is a shared library, so you have to
know how to do shared library packaging.
> opendkim is the major
est. Could your
> concern be resolved by better naming?
>
> I process the tag name (it has already been renamed once [1]) as
> "debian-watch-does-not-check-A-gpg-signature." Without a signature
> that is an objective fact.
>
> On Tue, Dec 11, 2018 at 5:18 AM Scott Kitterm
Package: lintian
Version: 2.5.116
Severity: minor
As designed, debian-watch-does-not-check-gpg-signature does not check if
upstream provides a GPG signature to make checking it possible. I get that
the "Certainty: certain" is meant to mean that it's certain that uscan won't
check a GPG
On Tue, 06 Nov 2018 19:47:34 -0500 Scott Kitterman
wrote:
> Would someone who is still having this problem please try the attached
> configure-instance.sh in place of the installed version in /usr/lib/postfix?
>
> This one avoids postmulti in every case and might actually work
On December 8, 2018 9:27:22 AM UTC, gustavo panizzo wrote:
>
>On Sat, Dec 08, 2018 at 04:03:05AM +, Scott Kitterman wrote:
>
>>
>>It seems like it's not for sure this should be removed right now.
>Axel: are you willing to take over as maintainer? I see there is
On Sat, 8 Dec 2018 08:12:54 +0800 gustavo panizzo wrote:
> On Fri, Dec 07, 2018 at 11:06:01AM +0100, Axel Beckert wrote:
> >Hi,
>
> >> leap second [2],
> >
> >Never noticed that despite having uptimed installed on more or less
> >all my Debian systems for more like 15 years or so. You're
t;
> Regards
> Brent
>
> On 2018/12/07 09:18, Paul Wise wrote:
> > On Fri, Dec 7, 2018 at 3:12 PM Scott Kitterman wrote:
> >> This package currently has Paul Wise listed as a co-maintainer, but
> >> you've
> >> removed him. Did you coordinate that with h
wait until it's in testing before uploading the
pu, even if I get the ack before.
Scott K
>From 0ec9807a6233bd5e5856c79fb3d53e37331f3617 Mon Sep 17 00:00:00 2001
From: Scott Kitterman
Date: Fri, 7 Dec 2018 08:24:23 -0500
Subject: [PATCH] Add
debian/patches/0002-fix-error-when-parsing-nsec3-bit
This package currently has Paul Wise listed as a co-maintainer, but you've
removed him. Did you coordinate that with him? In any case, the change needs
to be documented in debian/changelog.
Scott K
On Thursday, December 06, 2018 08:01:39 AM Brent Clark wrote:
> Package: sponsorship-requests
On Tue, 4 Dec 2018 19:11:33 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?=
wrote:
> severity nn normal
> reassign nn ftp.debian.org
> retitle nn RM: aolserver4 -- RoQA; unmaintained upstream, alternatives
exist, low popcon
> thanks
>
> > > So my question: Can we remove aolserver4 from
Package: ftp.debian.org
Severity: normal
Until Qt is fixed on kfreebsd, these binaries should go away.
Scott K
On Monday, December 03, 2018 09:41:44 PM Dr. Tobias Quathamer wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Hi,
>
> please remove golang-1.9 from unstable. It's obsolete and replaced by
> newer versions. It also has an RC bug (#897762).
>
> There's still one reverse dependency on
On Fri, 30 Nov 2018 19:59:17 -0500 Scott Kitterman wrote:
> Forwarded upstream, but the clamav bugzilla makes all bugs private by
> default.
> I've asked them to make it public.
It's public now. I got positive feedback via IRC on the change.
Scott K
On Fri, 23 Nov 2018 18:00:12 +0100 Emmanuel Bourg wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Hi,
>
> Please remove the icu4j-49 package. It's an old version of ICU4J that was
> only used for the needs of src:eclipse, and it's about to be removed
(#914448).
At least according to
Package: pytest-remotedata
Version: 0.3.1-2
Severity: serious
Justification: Policy 3.3
The FTP team received this bounce after a recent upload:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
Package: pytest-openfiles
Version: 0.3.1-1
Severity: serious
Justification: Policy 3.3
The FTP team received this bounce after a recent upload:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman
* Package name: authheaders
Version : 0.10.0
Upstream Author : Valimail Inc
* URL : https://github.com/ValiMail/authentication-headers
* License : BSD like, ZPL 2.1, MPL 2.0
Programming Lang: Python
Package: python3-wget
Version: 3.2-1
Severity: normal
python3-wget has the following in it's Depends:
Depends: python-urllib3, ${misc:Depends}, ${python3:Depends}
Unfortunately, python-urllib3 is both wrong and unnecessary. It is wrong
because a python3 package needs to depend on the python3
Package: src:pyqwt5
Version: 5.2.1~cvs20091107+dfsg-8
Severity: serious
Justification: 2
This package is scheduled for removal before buster is released. Most, but
not all of the rdepends are already out of testing for one reason or another,
but it would be good to get pyqwt5 removed from
Package: gr-fosphor
Version: 3.7.0.2.7b6b996-3
Severity: important
Your package build-depends (and depends) on python-qwt5-qt4. There is no plan
to port it to Qt5, so any Qt5 port of your package will have to be done
without it. It is scheduled to be removed [1].
Scott K
[1]
Package: src:hgview
Version: 1.9.0-1.1
Severity: minor
The email address of Julien Cristau in Uploaders is bouncing:
: host mail.logilab.fr[109.190.107.82] said: 550
5.1.1 : Recipient address rejected: User unknown
in local recipient table (in reply to RCPT TO command)
Scott K
It's had no upstream commits in over 6 years. Is it really suitable for
introduction into Debian?
Also, it's not clear it works with a modern Python 3. I'd also check if it
does before considering it suitable.
New guess is if you package this, you'll end up effectively being upstream. I
Package: python3.7
Version: 3.7.1-1
Severity: important
The switch to python3.7 as default will cause the stable version of
python3-dns to break during upgrade (due to async being a keyword in
python3.7). Please add Breaks: python3-dn (<< 3.2.0) so that packages are
upgraded in the correct
On Monday, November 05, 2018 12:07:43 PM Daniel Kahn Gillmor wrote:
> Control: tags 908755 - moreinfo
>
> On Sun 2018-11-04 11:54:48 -0500, Scott Kitterman wrote:
> > There is a rdepend that should be addressed too:
> >
> > Checking reverse dependencies...
> > #
Package: ftp.debian.org
Severity: normal
clamtk-nautilus | 5.25-1| unstable | all
NBS as of 5.26-1. Not in cruft report, so needs manual rm.
Scott K
On Sat, 01 Sep 2018 14:42:36 +0300 Lars Wirzenius wrote:
> Package: ftp.debian.org
> Severity: normal
>
> I wrote vmdebootstrap in 2011, originally. It has been maintained by
> others since then, upstream and in Debian. I am now again the upstream
> and Debian maintainer since last year.
>
> As
On Wed, 25 Jul 2018 22:03:46 +0200 Sebastian Andrzej Siewior
wrote:
> On 2018-07-25 12:14:17 [+0900], Marc Dequènes (duck) wrote:
> > Quack,
> >
> > I did not try to switch on ScanOnAccess on my production system, but with my
> > configuration, which is not that different, I do not have the
On Thu, 18 Aug 2016 19:57:35 +0200 Anthon van der Neut wrote:
>
> I can confirm this still happens with python-yaml 3.10 and 3.11.2, as
> well as with the package python-ruamel.yaml 0.11.14-1 (a fork and
> superset of python-yaml).
>
> This has been fixed in version 0.12.3 of ruamel.yaml.
>
>
On Sunday, October 28, 2018 01:30:04 AM Debian Bug Tracking System wrote:
There is a new python3-dkim release that is compatible with python3.7. Please
add Breaks: python3-dkim (<< 0.9.0) to python3.7 and then close this bug.
Thanks,
Scott K
On Sun, 18 Mar 2018 18:31:26 +0100 Sylvestre Ledru
wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Let's start the work to remove llvm 4.0.
> I will fill the requests for rdeps to start moving to 6.0
>
Still not there yet:
Checking reverse dependencies...
# Broken Depends:
julia:
It looks like it's the combination of these two changes:
https://bugs.python.org/issue25054
https://bugs.python.org/issue32308
No idea what else that broke.
Scott K
signature.asc
Description: This is a digitally signed message part.
Package: python3.7
Version: 3.7.1-1
Severity: important
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I ran the dkimpy test suite with both python3.6 and python3.7.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Running the test suite
On October 22, 2018 4:37:14 PM UTC, Yuri D'Elia wrote:
>On Mon, Oct 22 2018, gregor herrmann wrote:
>> You can easily sub-class Mail::SPF::Server and the
>> Mail::SPF::Result class collection in order to extend or modify
>> their behavior. The hypothetical Mail::SPF::BlackMagic package
On October 9, 2018 1:02:10 PM UTC, Salvo Tomaselli wrote:
>Is this package unmaintained/abandoned?
>
>I could take it…
>
>--
>Salvo Tomaselli
DPMT is the maintainer, so you can update it with a team upload.
Scott K
I'd have to try it out to be sure and I'm lacking the time to investigate.. If
it results in the file in the right place and not a conffile, then I'm happy.
Scott K
The problem is that this is installed for user appreciation and so we should
install it in the expected location (/etc/postfix).
I agree it shouldn't be a conffile.
You should be able to install it somewhere temporary (sharedir is fine) cat it
into /etc/postfix in the postinst, and then remove
On July 29, 2018 7:39:53 AM UTC, Chris Lamb wrote:
>Hey Scott,
>
>> You don't need to know. All you need to know is a package depends on
>both. I
>> don't think that there is any need to limit it to pyhon{3}-*
>pacakges.
>
>Nod. :)
>
>(Oh, just in case I am parsing your '{3}' regex wrong,
On Sat, 28 Jul 2018 14:16:11 +0100 Chris Lamb wrote:
> Hi Stuart,
>
> > In the upload of translate-toolkit 2.3.0-3, I ended up with the following:
> >
> > Depends: python3, python3-pkg-resources, python3-six, python3-translate,
> > python3:any, python:any
> >
> > such that the package
Package: ftp.debian.org
Severity: normal
This can and should go as part of Qt4 removal (See #875193). The last rdepend
qt4-perl, is planned for removal (See #904583).
Scott K
Package: ftp.debian.org
Severity: normal
The last rdepend has been resolved (See #631769), so this can and should be
removed now as part of the Qt4 removal effort.
Scott K
On July 24, 2018 10:42:44 AM UTC, richard lucassen
wrote:
>On Tue, 24 Jul 2018 08:19:15 +0200
>Sebastian Andrzej Siewior wrote:
>
>> Is the kernel complaining about something like in the other report
>> where it claimed something about a deadlock?
>
>No, no words like fanotify, deadlock or
On Mon, 23 Jul 2018 20:40:29 +0200 Andreas Beckmann wrote:
> Package: python3-dns
> Version: 3.1.1-1
> Severity: serious
> Tags: sid buster
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 902788 with -1
>
> Hi,
>
> during a test with piuparts I noticed your package
On Mon, 23 Jul 2018 20:40:29 +0200 Andreas Beckmann wrote:
> Package: python3-dns
> Version: 3.1.1-1
> Severity: serious
> Tags: sid buster
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 902788 with -1
>
> Hi,
>
> during a test with piuparts I noticed your package
On July 22, 2018 10:51:30 AM UTC, peter green wrote:
>package: ftp.debian.org
>x-debbugs-cc: python-green...@packages.debian.org
>
>The python-greenlet source package no longer builds python-greenlet-dbg
>or python3-greenlet-dbg. The continued presence of these packages seems
>to be blocking
I had hoped to work on this this week. It hasn't happened and it's not going
to.
In the end, I the Qt4 stuff has to go, so I wouldn't wait on this for the
transition.
Scott K
On June 28, 2018 1:23:31 PM UTC, "Lisandro Damián Nicanor Pérez Meyer"
wrote:
>El miércoles, 27 de junio de 2018
This is actually a Qt problem. I've seen it before with another package. The
kernel you are running is too old for the current Qt to work correctly, but
there's nothing to fall back to how older kernels worked.
Scott K
On Friday, June 22, 2018 04:47:57 PM Christoph Terasa wrote:
> Hi Boris,
Excellent. Thanks,
Scott K
On June 21, 2018 1:01:48 PM UTC, Alex Mestiashvili
wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Alex Mestiashvili
>X-Debbugs-Cc: ames...@rsh2.donotuse.de, debian-de...@lists.debian.org
>
>* Package name: krop
> Version : 0.5.0
> Upstream Author : Armin Straub
>* URL
On June 18, 2018 7:44:26 AM UTC, Markus Koschany wrote:
>
>Am 18.06.2018 um 04:53 schrieb Scott Kitterman:
>[...]
>>> Please remove the following leaf packages. Thank you!
>>>
>>> childsplay-alphabet-sounds-bg
>>> childsplay-alphabet-sounds-ca
>
Package: wnpp
Severity: normal
opendkim is the major open source C implementation of the DKIM (Domain Keys
Identified Mail) protocol (see RFC 6376). I believe it is important that it
be in Debian and well maintained, but I am no longer using it, so my ability
to test things and my motivation are
The next upstream release will use setuptools, so this problem will go away
then.
Scott K
On Tue, 24 Apr 2018 11:57:36 +0300 Adrian Bunk wrote:
> Source: pypolicyd-spf
> Version: 2.0.2-1
> Severity: serious
>
>
On Sun, 13 May 2018 12:25:13 +0200 Jan Luca Naumann
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Control: tags 897210 fixed-in-experimental
>
> Dear Scott,
>
> I have uploaded nitrokey-app in the current versiont to experimental
> as well to allow
On Monday, May 07, 2018 01:35:30 PM Russ Allbery wrote:
> Scott Kitterman <deb...@kitterman.com> writes:
> > Package: lintian
> > Version: 2.5.85
> > Severity: normal
> >
> > Also, please reduce the certainty from certain. It's not.
> >
> &g
Package: lintian
Version: 2.5.85
Severity: normal
Also, please reduce the certainty from certain. It's not.
I'd just noticed depends-on-mail-transport-agent-without-alternatives. I
mainain approximately 10% of the packages affected by the check (3 of 33) and
in all those cases the check is
On May 7, 2018 1:26:36 AM UTC, Russ Allbery wrote:
>Chris Lamb writes:
>
>> However, my experience with being an author of a handful of static
>> analysis tools is that people have a slight tendency to delegate
>> thinking to the computer's output. The
On May 7, 2018 12:20:04 AM UTC, Chris Lamb wrote:
>Hi Scott,
>
>> For what it's worth, this is an example of the kind of check that
>isn't
>> supported by policy.
>
>I'm not quite following your chain of logic wrt to Lintian and Debian
>Policy. I mean, there are countless
On Sat, 05 May 2018 19:42:05 +0100 Chris Lamb wrote:
> tags 884499 + pending
> thanks
>
> Actually, let's give this a whirl. Implemented in Git,
> pending upload:
>
>
> https://salsa.debian.org/lintian/lintian/commit/1ecc761fea7b22f85faf400ac134d24438454e4d
>
>
On Friday, May 04, 2018 04:17:37 PM Nicholas D Steeves wrote:
> I remember this Thanks for mentioning this bug in
> #debian-python. I followed
> https://wiki.debian.org/Python/LibraryStyleGuide#Python_versions and
> it would seem it also needs to be updated.
...
>
> Should articles in the wiki
On Thu, 08 Mar 2018 02:07:36 + Chris Lamb wrote:
> Package: lintian
> Version: 2.5.77
> Severity: wishlist
>
> Hi,
>
> Should we warn about "old" X-Python3-Version fields? For example, I
> just saw a new package from a sponsee with:
>
> X-Python3-Version: >= 3.2
>
>
Libnitrokey 3.3 has been accepted into experimental.
Scott K
Thanks. I think that will work.
Scott K
On Thursday, May 03, 2018 05:48:36 AM Chris Lamb wrote:
> tags 897213 + pending
> thanks
>
> > People pay attention to lintian results and so the tags
> > should be actionable.
>
> Indeed, that's convincing enough and I have not heard anything from
>
Requested amd64 strace for the failure.
Scott Kstrace python -c "import PyQt5.QtCore"
execve("/usr/bin/python", ["python", "-c", "import PyQt5.QtCore"],
0x7ffdbf72ace0 /* 32 vars */) = 0
brk(NULL) = 0x7ff0643bf000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT
On Mon, 30 Apr 2018 13:37:05 -0400 Scott Kitterman <deb...@kitterman.com>
wrote:
> As requested on IRC:
ldd /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
linux-vdso.so.1 (0x7a3ec000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x
As requested on IRC:
ldd /usr/lib/python3/dist-packages/PyQt5/QtCore.cpython-36m-x86_64-linux-
gnu.so
linux-vdso.so.1 (0x7fff9cba2000)
libQt5Core.so.5 => not found
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f6ac1f6c000)
libc.so.6 =>
On Monday, April 30, 2018 06:52:30 AM Chris Lamb wrote:
> [adding Matthias to CC as he filed #883581]
> [adding Holger to CC as he filed #886259]
>
> Hi Scott,
>
> Thanks for opening this!
>
> > I understand (and agree with) the intent of this check, but in practice,
> > it's harming the
Package: lintian
Version: 2.5.84
Severity: important
Dear Maintainer,
There has been a lot of discussion on debian-devel about the future of
python2.7 in Buster. The dependency-on-python-version-marked-for-end-of-life
flag is confusing people into thinking they should drop python2.7 support
Package: nitrokey-app
Version: 1.2-1
Severity: important
Nitrokey has released libnitrokey 3.3 and nitrokey-app 1.3. They moved the
udev rule to the lib. I have created a package and will upload it to
experimental. Unfortunately, it has to go through New, so I don't know when
it will be there.
On Wed, 18 Apr 2018 12:48:27 +0300 Dmitry Shachnev wrote:
> On Sun, Apr 15, 2018 at 01:26:50PM +0300, Dmitry Shachnev wrote:
> > Works for me in a clean sid chroot.
>
> The CI tests for pyqt5 are also passing [1], so I am closing this bug.
>
> [1]:
I'm running the patched quassel core on Stretch and it is working fine.
Scott K
signature.asc
Description: This is a digitally signed message part.
Issue descriptions from Gentoo (input for DSA text). I'm not sure issue 2 is
really a security issue.
Vuln 1:
Title: quasselcore, corruption of heap metadata caused by qdatastream
leading to preauth remote code execution.
Severity: high, by default the server port is publicly open and the
On Tuesday, April 24, 2018 07:46:51 PM Lisandro Damián Nicanor Pérez Meyer
wrote:
> El mar., 24 de abr. de 2018 02:47, Niels Thykier <ni...@thykier.net>
>
> escribió:
> > Scott Kitterman:
> > > On April 23, 2018 10:03:45 PM UTC, "Lisandro Damián Nic
On April 23, 2018 10:03:45 PM UTC, "Lisandro Damián Nicanor Pérez Meyer"
wrote:
>If I understand correctly and, let's suppose, libQtFoo 5.10.2 is built
>with a patched compat 12, then all applications rebuilt against 5.10.2
>would require at very least 5.10.2 even if
On Monday, April 23, 2018 05:34:33 PM you wrote:
> Package: kbackup
> Severity: normal
>
> I intend on packaging this.
I was the previous maintainer of the KDE4 version of kbackup and I support
this (for avoidance of doubt).
Scott K
signature.asc
Description: This is a digitally signed
On April 20, 2018 2:02:52 PM UTC, Dimitri John Ledkov wrote:
>Package: ftp.debian.org
>Severity: wishlist
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>FTP team brodly consists of Masters, Assistants, Wizards, and
>Trainees.
>
>However who the current Trainees are, is
Package: virtualbox-ext-pack
Version: 5.2.10-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
After a recent upload, the FTP team received this error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more
Package: virtualbox
Version: 5.2.10-dfsg-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
After a recent upload, the FTP team received this error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of
Package: python-acme
Version: 0.22.2-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
After a recent upload, the FTP team received this error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
Package: gir-to-d
Version: 0.15.0-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
After a recent upload, the FTP team received this error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
Package: geany-plugins
Version: 1.33+dfsg-1
Severity: serious
Justification: Policy 3.3
Dear Maintainer,
After a recent upload, the FTP team received this error:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of
Package: python-pyqt5
Version: 5.9.2+dfsg-1
Severity: grave
Justification: renders package unusable
Tried this on sid with both pyqt5 5.9.2 and 5.10.1:
Unpacking python-pyqt5 (5.10.1+dfsg-1) over (5.9.2+dfsg-1+b1) ...
Setting up python-pyqt5 (5.10.1+dfsg-1) ...
# python
Python 2.7.14+ (default,
On April 8, 2018 5:41:37 PM UTC, "Raphaël Halimi"
wrote:
>Package: postfix
>Version: 3.3.0-1
>Severity: wishlist
>
>Hi,
>
>I report this bug following my own advice in [1].
>
>I have set the severity to wishlist, but from a security point of view,
>it could be
On Fri, 30 Mar 2018 23:04:49 -0400 Jason Pleau wrote:
> Small typo in my previous email, the .prerm script contains:
>
> pyclean -p python-backports.ssl-match-hostname
>
> I had another package in my clipboard, just wanted to clear that up so
> there's no confusion :)
Thanks.
Please file a new bug for that.
Scott K
On March 29, 2018 12:59:26 PM UTC, Jordi Mallach wrote:
>Package: ftp.debian.org
>Followup-For: Bug #894281
>
>Hello,
>
>I was pointed out by Adrian Bunk on IRC that the ppc binaries for
>gnome-video-arcade should also be removed.
>
There are a few changes that still need merged for the next upload. It would
be better to include those and upload once. No need to autoremove now though.
Scott K
Package: ftp.debian.org
Severity: normal
For quite some time now the package hasn't built on these archs and there is
no prospect of it getting better. May as well clear up a bit of cruft.
Scott K
Package: libmail-dkim-perl
Version: 0.44-1
Severity: important
Tags: upstream
The IETF recently published updated guidance on minimum RSA key sizes for use
with DKIM[1]. I decided to check in Debian to see what packages might need to
be updated as a result. I've looked and I can't find where
Package: libdkim
Version: 1:1.0.21-3
Severity: important
Tags: upstream
The IETF recently published updated guidance on minimum RSA key sizes for use
with DKIM[1]. I decided to check in Debian to see what packages might need to
be updated as a result. I've looked and I can't find where libdkim
On March 15, 2018 10:03:03 AM UTC, Paul Gevers <elb...@debian.org> wrote:
>Control: tags -1 moreinfo
>Control: reassign -1 autodep8
>Control: retitle -1 autodep8 should maybe ignore transitional packages
>
>On Mon, 08 Jan 2018 17:43:34 -0500 Scott Kitterman
><
Package: wnpp
Severity: wishlist
Owner: Scott Kitterman <deb...@kitterman.com>
* Package name: dkimpy-milter
Version : 0.9.5.1
Upstream Author : Scott Kitterman <sc...@kitterman.com>
* URL : https://launchpad.net/dkimpy-milter
* License : GPL
Prog
On Sat, 17 Feb 2018 07:56:31 + Marten KARL
wrote:
> Package: python3-postgresql
> Version: 1.1.0-2+b4
> Severity: grave
> Justification: renders package unusable
>
> Split of Versionstring fails:
> db = postgresql.open(database='marten',host='10.8.2.1',port=5431)
Package: src:python-bleach
Version: 2.1.2-1
Severity: important
Tags: upstream, security
Version 2.1.3 (March 5th, 2018)
---
**Security fixes**
* Attributes that have URI values weren't properly sanitized if the
values contained character entities. Using character
901 - 1000 of 3027 matches
Mail list logo