Package: ftp.debian.org
Severity: normal
Out of date and depends on obsolete Qt4 libs.
Package: ftp.debian.org
Severity: normal
Picard version 2 is Qt5. Obsolete binaries on kfreebsd depend on obsolete
Qt4 libs.
Package: ftp.debian.org
Severity: normal
NBS and (pointlessly) keeping old source/arch all version in the archive.
Scott K
That only means Qt5 or pyqt5 is out of date on riscv64, so python-pyqt5 isn't
installable. Qscintilla2 is the victim here. Nothing you did wrong.
Scott K
On February 23, 2019 7:31:23 AM UTC, "Gudjon I. Gudjonsson"
wrote:
>Hi Manuel
>
>Sorry for a slow response. But can you please take at loo
On Thursday, February 21, 2019 05:35:26 PM Robert Munyer wrote:
> Control: found -1 3.1.9-0+deb9u2
>
> Scott Kitterman wrote:
> > I agree this is a problem. A design change like this should not be
> > implemented at the distro level, so it's not a patch I would co
On February 18, 2019 3:52:55 PM UTC, "Antoine Beaupré"
wrote:
>Package: wnpp
>Severity: wishlist
>Owner: Antoine Beaupré
>
>* Package name: dt
> Version : 0.0.9
> Upstream Author : Wim
>* URL : https://github.com/42wim/dt
>* License : Apache-2.0
> Programmin
> Its seemingly easy to configure postfix to opportunisticly encrypt
> email. That may not be its primary use, and many of the pages
> describing how to set things up miss this, but
>
> In main.cf:
> smtp_use_tls = yes
> smtp_tls_note_starttls_offer = yes
Reviewed the status of this Feb 18, 2019
Package: ftp.debian.org
Severity: normal
The package is unbuildable, uninstallable, and has not been uploaded in very
close to a decade.
Scott K
Can you change:
Linux.[34].*) SYSTYPE=LINUX$RELEASE_MAJOR
to:
Linux.[345].*) SYSTYPE=LINUX$RELEASE_MAJOR
in makedefs and verify it builds and works (just a smoke test is fine) with
your kernel? I'm having discussions with upstream about this and that would be
helpful in moving things forward
On Saturday, February 16, 2019 01:18:51 PM László Böszörményi wrote:
> On Sat, Feb 16, 2019 at 1:12 PM Scott Kitterman wrote:
> > On Saturday, February 16, 2019 12:08:48 PM Luca Boccassi wrote:
> > > A build-dependency on pkg-config needs to be added, it's not install
On Saturday, February 16, 2019 12:08:48 PM Luca Boccassi wrote:
> A build-dependency on pkg-config needs to be added, it's not installed
> otherwise when building with pbuilder/sbuild/etc. Could this be the
> issue?
That was it. Thanks.
I think it would be prudent to rebuild any other libicu-dev
On Saturday, February 16, 2019 12:08:48 PM Luca Boccassi wrote:
> A build-dependency on pkg-config needs to be added, it's not installed
> otherwise when building with pbuilder/sbuild/etc. Could this be the
> issue?
Probably. Let me try that.
Thanks,
Scott K
signature.asc
Description: This is
On Saturday, February 16, 2019 12:00:51 PM László Böszörményi wrote:
> Control: tags -1 +patch
>
> On Sat, Feb 16, 2019 at 10:21 AM Scott Kitterman
wrote:
> > It would have been nice if you had investigated the impact of dropping
> > icu-
> > config. The postfix bui
Package: icu-devtools
Version: 63.1-6
Severity: important
It would have been nice if you had investigated the impact of dropping icu-
config. The postfix build system uses the presence of icu-config to determine
if libicu is present (and thus SMTPUTF8 support should be built in). See
#921075.
I
On Friday, February 15, 2019 08:59:41 PM Sean Whitton wrote:
> Hello,
>
> Use of the Build-Conflicts field is currently mostly optional, but Ian
> Jackson and I have been working on text for Debian Policy that would
> require its use in certain cases. See #824495 for the discussion.
>
> There ar
See the package Suggests. This is intentional.
Scott K
On February 13, 2019 7:23:14 PM UTC, Ralf Treinen wrote:
>Hi,
>
>On Tue, Feb 12, 2019 at 08:57:55AM -0500, Scott Kitterman wrote:
>> Package: src:marionnet
>> Version: 0.90.6+bzr508-1
>> Severity: serious
>> Justification: fails to build from source (bu
No. First we have to get it in Testing. We are currently waiting for release
team approval to do that.
Scott K
On February 13, 2019 9:44:21 AM UTC, "Ivan Jurišić" wrote:
>I don't see backported package, any chance to bring this important
>package to backport?
>
>See lot FIX-ed stuff from v100
Package: src:marionnet
Version: 0.90.6+bzr508-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
liblablgtksourceview2-ocaml and liblablgtksourceview2-ocaml-dev are no longer
built by lablgtk2 and will be removed. Marionnet build-depends on
liblablg
The one trick I don't think that can be managed this way is that currently
dkimpy-milter reads the private key files as root and then drops privileges so
that it doesn't have access to the key while running (it's only in memory).
Opendkim does similar, which is where I got the idea.
I'm happy
On Monday, February 11, 2019 02:33:35 AM Daniel Kahn Gillmor wrote:
> Package: dkimpy-milter
> Version: 1.0.0-1
>
> Hi Scott--
>
> I see that python3-milter exists now. it would be great to move
> dkimpy-milter to python3 as well, so that mailserver administrators
> using dkimpy-milter don't nee
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Even though we are after the transition deadline, we would like to have
permission to go ahead with the clamav transition. Typically we keep clamav
updated in stable for effectiveness re
Package: src:kauth
Version: 5.54.0-1
Severity: normal
Seen in the amd64 build logs for 5.54.0-1:
dpkg-gensymbols: warning: some libraries disappeared in the symbols file:
kauth_backend_plugin.so kauth_helper_plugin.so
dpkg-gensymbols: warning: debian/libkf5auth5/DEBIAN/symbols doesn't match
com
Package: src:kauth
Version: 5.28.0-2
Severity: grave
Tags: security upstream patch
Justification: user security hole
See the KDE announce list [1]. It includes reference to a fix [2]. This is
CVE-2019-7443.
Scott K
[1] https://mail.kde.org/pipermail/kde-announce/2019-February/11.html
[2]
I think the only API change that's relevant might be:
is_utc to icaltime_is_utc() in icaltimetype
For anyonne with a non-trivial C++ knowledge (i.e. not me), I suspect this
wouldn't be too hard.
Scott K
What about porting it to libical3? That might be easier. I tried to build it
and it does need some changes, but I don't think keeping libical2 is feasible.
See the attached for the error.
Scott K
On Friday, February 08, 2019 10:46:21 PM Sandro Knauß wrote:
> Hey,
>
> for me it looks like we
Package: src:didjvu
Version: 0.8.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
This package both build-depends and suggests python-libxmp,
It is not installable and does not appear to be reasonablly fixable to work
with libexempi8 (thus remov
Package: src:datalad
Version: 0.11.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
This package both build-depends and recommends python-libxmp/python3-libxmp,
They are not installable and do not appear to be reasonable fixable to work
with libe
On Fri, 08 Feb 2019 04:41:41 -0500 Scott Kitterman
wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Dead due to lack of libexempi8 compatibility.
# Broken Build-Depends:
datalad: python-libxmp
python3-libxmp
didjvu: python-libxmp
Dependency problem found.
more
Package: olive-editor
Version: 20181223-1
Severity: important
Once the currently requested removal of src:olive is done, and olive-editor is
in testing, the conflicts/replaces should be dropped as olive-editor does not
conflict nor replace the old olive package that is in stable.
Scott K
Package: olive-editor
Version: 20181223-1
Severity: serious
Justification: Policy 7.6
Because olive-editor doesn't provide a olive binary transitional package
(which would depend on olive-editor), the proper upgrade path is not provided.
Please add a transitional package so that users will end up
Package: ftp.debian.org
Severity: normal
Dead due to lack of libexempi8 compatibility.
Scott K
My recollection is that you mail debian-release and ask.
Scott y
On February 7, 2019 7:51:29 AM UTC, Michael Stapelberg
wrote:
>On Thu, Feb 7, 2019 at 8:46 AM Scott Kitterman
>wrote:
>
>> No. It's an actual policy violation, so the bug is correct. I'd
>leave it
No. It's an actual policy violation, so the bug is correct. I'd leave it as
is and ask the release team to mark it buster-ignore.
Scott K
On February 7, 2019 7:29:01 AM UTC, Michael Stapelberg
wrote:
>On Wed, Feb 6, 2019 at 11:01 PM Scott Kitterman
>wrote:
>
>> It
Package: ftp.debian.org
Severity: normal
See subj.
Package: ftp.debian.org
Severity: normal
See subj.
Package: ftp.debian.org
Severity: normal
See subj.
Package: ftp.debian.org
Severity: normal
See subj
Package: ftp.debian.org
Severity: normal
See subj.
e case, so
>any
>help is appreciated. Thanks!
>
>On Wed, Feb 6, 2019 at 7:49 PM Scott Kitterman
>wrote:
>
>> Package: prometheus-postfix-exporter
>> Version: 0.1.2-1
>> Severity: serious
>> Justification: Policy 9.11
>>
>> Excerpt from polic
On Wed, 06 Feb 2019 05:59:37 + "Adam D. Barratt" wrote:
> Control: tags -1 + confirmed
...
>
> Please go ahead.
>
> Regards,
>
> Adam
Uploaded. Thanks,
Scott K
On February 5, 2019 11:50:47 PM UTC, Nicholas D Steeves
wrote:
>Hi Scott,
>
>Reply follows inline.
>
>On Tue, Feb 05, 2019 at 05:31:23PM -0500, Scott Kitterman wrote:
>> Package: calibre
>> Version: 3.39.1+dfsg-1
>> Severity: serious
>> Justification: P
This seems relevant:
https://github.com/python/typing/issues/523
Scott K
On Tuesday, February 05, 2019 11:02:56 PM Ruano Ruano Javier wrote:
> Hello Diane,
> The exact message is:
>
> args2 = [_get_recursive(dsk, k, cache) for k in args]
> File "/usr/lib/python3/dist-packages/dask/core.py",
018-02-23 17:29:18.0 -0500
+++ postfix-3.1.9/debian/changelog 2019-02-05 17:51:41.0 -0500
@@ -1,3 +1,35 @@
+postfix (3.1.9-0+deb9u1) stretch; urgency=medium
+
+[Scott Kitterman]
+
+ * Unset inet_interfaces in postfix-instance-generator to avoid postconf
+failures when the genera
Package: calibre
Version: 3.39.1+dfsg-1
Severity: serious
Justification: Policy 3.3
Debian policy requires a valid maintainer address:
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:
prein...@debian.o
Package: prometheus-postfix-exporter
Version: 0.1.2-1
Severity: serious
Justification: Policy 9.11
Excerpt from policy 9.11:
However, any package integrating with other init systems
must also be backwards-compatible with sysvinit by providing a SysV-
style init script with the same name as and eq
libyaml-cpp0.5d1 has been removed. libyaml-cpp0.5v5 has not, so reopening.
Scott K
Package: ftp.debian.org
Severity: normal
Replaced by e2guardian. In addition to being actively maintained upstream,
e2guardian has switched to use clamd instead of libclamav, so it doesn't need
patching everytime libclamav changes API.
Maintainer (formerer) agreed on IRC:
formorer: We have an
On Sat, 26 Jan 2019 08:47:52 -0800 Paul Hardy wrote:
> Unicode's new version for 2019 is attached, with data files in
> http://www.unicode.org/ivd/data/ explicitly mentioned as covered under
> the license. The source text is at
> http://www.unicode.org/copyright.html.
According to my wrangling o
On Wed, 30 Jan 2019 20:32:02 +0100 Emilio Pozuelo Monfort
wrote:
...
> - Can you get this into experimental first so that we can check that there
are
> no issues, e.g. that the package builds on all architectures?
...
It's through New and accepted into experimental.
Scott K
Package: colmap
Version: 3.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
According to https://buildd.debian.org/status/package.php?p=colmap the package
is FTBFS on all archs. Experimental apparently builds, but unstable is
blocking the comple
Package: ftp.debian.org
Severity: normal
Needs porting to a newer nanomsg. No one in Debian is working on this package
(I last touched at a year and a half ago to fix another RC bug) and there's
almost no activity upstream.
If it ever gets updated and someone interested in the package appears, t
On Sat, 29 Dec 2018 10:05:44 + Hugh McMaster
wrote:
> Package: ruby-zoom
> Version: 0.5.0-1+b2
> Severity: important
>
> Dear Maintainer,
>
> Your package currently build-depends on libyaz4-dev. However, this package
> will soon be replaced by libyaz-dev during an upcoming transition.
>
>
Package: wfrog
Version: 0.8.2+svn973-1
Severity: grave
Justification: renders package unusable
wfrog is currently uninstallable due to the removal of pygooglechart (See
http://bugs.debian.org/920779 for details).
Scott K
On Sat, 1 Sep 2018 14:46:57 +0200 Mattia Rizzolo wrote:
> Source: webdis
> Version: 0.1.4+dfsg-1
> Severity: serious
>
> Dear maintainer,
>
> the package FTBFS on the buildds on i386 and mips64el:
It since built on i386 and the mips64el binary has been removed, so
downgrading to important.
Sc
Package: ftp.debian.org
Severity: normal
Package is long-term unbuildable on mips64el (#907754) and is blocking
removal of cruft binary libhiredis0.13.
Scott K
On Mon, 19 Nov 2018 16:42:35 -0800 Adam Lambert wrote:
> Ah, so I think you may have the winner. I set my temp directory to be
> something other than /tmp, and turned ClamAV back on, and it's been running
> for about an hour now with no obvious ill effects. I will report back if
> something e
On Fri, 25 Jan 2019 14:05:40 +0900 Arnaud Fontaine wrote:
> Package: ftp.debian.org
> Severity: normal
>
> I no longer use nor have time to take care of the package but for the
> following reasons I'm requesting its removal rather than orphaning it:
>
> * There has been no upstream release for
Package: unbound
Version: 1.8.1-1
Severity: wishlist
According to the upstream website, 1.8.3 is available. It would be nice to
see the package updated before the release freeze. This isn't showing up
on tracker.d.o or p.qa.d.o, so I imagine the watch file needs work too,
although I didn't look
Package: python3-unbound
Version: 1.8.1-1
Severity: important
The python/python3-unbound packages ship both unbound and unboundmodule python
modules. The unbound module seems to work (because the swig build for the
compile part is executed and then it is installed). Currenlty though
unboundmodul
On Wednesday, January 23, 2019 05:32:49 PM Otto Kekäläinen wrote:
> > Can't you just use dh_link to add a symlink?
>
> I am re-evaluating this fix and considering to revert it. The problem
> with Postfix was that it did not find /usr/include/mysql/mysql.h and
> we added a symlink in libmariadb-dev
Package: src:prettytable
Severity: wishlist
https://github.com/kxxoling/PTable is a fork of prettytable that is now
needed for python-softlayer. To prevent that update from being blocked, I
have temporarily packaged ptable. Please review it and see if you think it
would be appropriate to update
Package: unyaffs
Version: 0.9.7-0.1
Severity: serious
Justification: Policy 3.3
A working maintainer address is required:
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:
matthew.fisc...@ubuntu.com
Package: ftp.debian.org
Severity: normal
It's broken and won't be fixed, so time for it to go.
Scott K
Package: argonaut
Version: 1.2-2
Severity: serious
Justification: Policy 3.3
This message was created automatically by mail delivery software.
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:
packa...@
On Fri, 11 Jan 2019 17:34:35 -0500 Scott Kitterman
wrote:
> On Thu, 10 Jan 2019 09:43:23 +0100 Andreas Tille wrote:
> > Package: ftp.debian.org
> > Severity: normal
> >
> > Hi,
> >
> > according to
> >
> > $ rmadison r-cran-rsql
On January 15, 2019 7:17:36 AM UTC, Pino Toscano wrote:
>In data lunedì 14 gennaio 2019 12:22:52 CET, Scott Kitterman ha
>scritto:
>> On Thu, 01 Nov 2018 14:04:12 -0300 Lisandro
>> =?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer
> wrote:
>> > On Wed, 17 Oct 201
Package: kde-standard
Version: 5:102
Severity: normal
Debian ought to be making barriers to using encryption as low as we reasonably
can. If you attempt to set a preferred gpg key in kmail without kleopatra
installed, it fails with a very unhelpful error message.
Rather than improve the error me
On Mon, 14 Jan 2019 00:17:55 -0500 Scott Kitterman
wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Last maintainer upload was in 2012. Package has been out of Testing for 15
> months and will not return. This is an obsolete, unmaintained Qt4 package
> that should
On Mon, 14 Jan 2019 17:54:40 + Debian FTP Masters
wrote:
> Version: 1.4.0.19-3+rm
...
Package was removed in error.
Bug reopened.
Scott K
On Monday, January 14, 2019 08:56:49 PM Timo Aaltonen wrote:
...
>
> the closed bugs need to be reopened though, including this one until
> svrcore is removed ;)
svrcore is removed.
#834233 and #912224 are reopened. I believe those are the only ones. All the
other recently closed bugs were al
On Mon, 14 Jan 2019 17:54:40 + Debian FTP Masters
wrote:
> Version: 1.4.0.19-3+rm
...
Package was removed in error.
Bug reopened.
Scott K
On Monday, January 14, 2019 08:07:13 PM Timo Aaltonen wrote:
> On 14.1.2019 19.54, Debian FTP Masters wrote:
> > We believe that the bug you reported is now fixed; the following
> > package(s) have been removed from unstable:
> >
> > 389-ds-base | 1.3.4.9-1 | source
> > 389-ds-base | 1.3.4.9-1+b1
On Monday, January 14, 2019 08:56:49 PM Timo Aaltonen wrote:
> On 14.1.2019 20.30, Scott Kitterman wrote:
> > On Monday, January 14, 2019 08:07:13 PM Timo Aaltonen wrote:
> >> On 14.1.2019 19.54, Debian FTP Masters wrote:
> >>> We believe that the bug you report
dewebkit
+ widgets, private/animablegraphicswebview, and widgets/webview
+- Drop libkdewebkit5 binary package
+- Build plasma3 without webkit
+- Update install files (verified header files that are no longer shipped
+ are not used elsewhere in Debian)
+
+ -- Scott Kitterman M
Package: qgis
Followup-For: Bug #875135
qgis is the last package that depends on the Qt4 version of QScintilla2. It
would be nice to be able to drop that for Buster.
I notice that qgis 3.4.3 is available as a Qt5 based LTS release. It would be
great to see this in Buster.
Scott K
Package: ftp.debian.org
Severity: normal
Built with Qt5 on other archs.
Scott K
Package: ftp.debian.org
Severity: normal
Package is updated for Qt5 on other archs.
Scott K
Package: ftp.debian.org
Severity: normal
Package is updated for Qt5 on other archs.
Scott K
Package: ftp.debian.org
Severity: normal
Last maintainer upload was in 2012. Package has been out of Testing for 15
months and will not return. This is an obsolete, unmaintained Qt4 package
that should be removed.
Scott K
Package: cloudsql-proxy
Version: 1.13-1
Severity: important
This message was created automatically by mail delivery software.
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:
sriva...@golden-gryphon.co
Package: ftp.debian.org
Severity: normal
Not buildable on kfreebsd and not likely to change.
Scott K
Package: ftp.debian.org
Severity: normal
Package is no longer buildable on kfreebsd with no real prospect that it
will change. Part of old KDE4 binary cleanup.
Scott K
Package: ftp.debian.org
Severity: normal
Not going to build on kfreebsd.
Scott K
Package: ftp.debian.org
Severity: normal
This should have been removed years ago.
Scott K
Package: cli-common
Version: 0.9+nmu3
Severity: serious
Justification: Policy 3.3
This message was created automatically by mail delivery software.
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:
pkg-
Package: xmms2-scrobbler
Version: 0.4.0-4
Severity: serious
Justification: Policy 3.3
A working maintainer address is required:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent e
Package: src:zeitgeist
Version: 1.0.1-0.3
Severity: serious
Justification: Policy 3.3
This message was created automatically by mail delivery software.
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: src:zeitgeist
Version: 1.0.1-0.3
Severity: serious
Justification: Policy 3.3
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:
rai...@ubuntu.com
host mx.canonical.com [91.189.95.10]
SMTP
Package: ftp.debian.org
Severity: normal
In the way of the libcurl transition:
RM, failed to build or uninstallable, no deps
dak rm -p -R -B -n -a kfreebsd-amd64 amanda
dak rm -p -R -B -n -a kfreebsd-amd64,kfreebsd-i386,hurd-i386 xmms2-scrobbler
dak rm -p -R -B -n -a
These failures are because we're using libyaml and it supports a newer yaml
version than the pure python implementation that the tests were made for.
I've verified this by rebuilding pyyaml without libyaml. Then all the tests
pass.
Before making the failures fatal, these tests need to be updat
Upstream withdrew this release. I'm in favor of switching to safe load by
default, but I think we need to be careful about it. I haven't checked the
details on why 4.1 was withdrawn. We may be better off cherry-picking the safe
load changes.
Thanks for working on pyyaml.
Scott K
Package: xfce4-screensaver
Severity: serious
Justification: Policy 3.3
As seen in the FTP team role account for the message subject 'Processing of
xfce4-screensaver_0.1.3-1_amd64.changes':
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error.
On Friday, January 04, 2019 06:06:09 PM Chris Lamb wrote:
> Hi Lisandro,
>
> > DAK-process-new does not has the option to ACCEPT a package and file a
> > bug against it.
>
> I like the idea in general but alas being integrated into dak would
> not fit my bug-filing/email workflow so I would be so
As the FTP Team member doing most of the the removals work, I think that would
be a helpful change.
Scott K
On January 1, 2019 11:07:50 PM UTC, Sandro Tosi wrote:
>> Sometimes we need to report an RM bug against ftp.debian.org to
>remove
>> a binary package which is no longer built.
>>
>> repor
You can find information on the Debian maintainer/uploaders at
https://tracker.debian.org/pkg/foxyproxy . I would get in touch with them.
Scott K
On Fri, 28 Dec 2018 16:41:33 +0200 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> Hello!
>
> pe 28. jouluk. 2018 klo 15.33 Scott Kitterman (deb...@kitterman.com)
kirjoitti:
> >
> > I did add a symlink as in the attached patch and postfix builds again. I
> > don'
I did add a symlink as in the attached patch and postfix builds again. I
don't have a good way to do run-time testing, so I don't know if there are any
further changes needed, but this at least fixes package building.
Please consider.
Scott K--- mariadb-10.3-10.3.11/debian/libmariadb-dev.links
On December 25, 2018 10:28:50 AM UTC, "Otto Kekäläinen" wrote:
>Hello!
>
>ti 25. jouluk. 2018 klo 10.06 Scott Kitterman (deb...@kitterman.com)
>kirjoitti:
>> Severity: grave
>> Justification: renders package unusable
>>
>> no longer found.
>
I quick look at codesearch.d.o suggests this will break 4 - 5 dozen packages.
Scott K
801 - 900 of 3039 matches
Mail list logo
