-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2020-02-05 at 19:32 +0100, Till Kamppeter wrote:
> Probably the best is to try to print without using PostScript. When
> creating a print queue and selecting your printer's make, model, and
> driver manually, have a look at PCL 6/XL (pxlmon
Package: jove
Version: 4.17.1.4-1
Severity: wishlist
Tags: patch l10n
Please find the updated German debconf translation for jove
attached.
Please place this file in debian/po/ as de.po for your next upload.
If you update your template, please use
'msgfmt --statistics '
to check the po-files fo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
libstk bumped its SOAME. So please schedule rebuilds for its reverse
dependencies:
nmu csound_1:6.13.0~dfsg-3 . ANY . unstable . -m "Rebuild against libstk-4.6.1"
dw csound_1:6.13.0~dfsg-3 .
On Thursday, 6 February 2020 4:06:03 AM AEDT Debian Bug Tracking System
wrote:
> Bug #945546 [src:libcrcutil] libcrcutil: Please enable building on riscv64
> architecture Added tag(s) pending.
Thanks for your NMU, Adrian.
--
Regards,
Dmitry Smirnov.
---
Honesty is a gift we can give to other
On Wed 05 Feb 2020 at 20:05:27 +0100, Yves-Alexis Perez wrote:
> On Wed, 2020-02-05 at 17:19 +, Brian Potkin wrote:
> > > Not really sure, but I don't think so. I mean, I'm using the PPD file
> > > from cups Debian packages, not anything from Brother.
> >
> > As root, what do you get for
> >
I have tried it also and with the command line
cupsfilter -p ../HL5250DN.ppd -i text/plain -m
application/vnd.cups-postscript -e ~/.bashrc > out.ps 2>log
I got valid PostScript output with a PJL header. Note that I had to
specify both input and output MIME types.
Probably in the cases whent
Package: unbound
Version: 1.9.6-1
Severity: serious
Hi,
After upgrade to 1.9.6-1, unbound did no longer start. It did not
log anything about this in any log file.
I have a config that says:
do-not-query-localhost: no
It now returns a syntax error for that.
Kurt
On 05/02/2020 20:14, Yves-Alexis Perez wrote:
So, I'm even more confused. I've upgraded again cups-filters (to 1.27.0-2) in
order to do a comparison check, and tried to print, and it did work (with the
Brother PPD, unchanged).
This looks strange, there is no change in the pdftops filter which c
Source: plover
Version: 4.0.0~dev8~66~g685bd33-1
Severity: important
Dear plover maintainer,
Your last upload of plover in Debian was the first upload. As a result, it was
not a source-only upload. Please make another source-only upload to allow the
package to migrate to Testing. You may find det
Source: zookeeper
Version: 3.4.13-4
Severity: important
X-Debbugs-CC: ebo...@apache.org tmanc...@debian.org
Dear zookeeper maintainers,
The latest upload of package zookeeper introduced the new binary package
(python3-zookeeper) thus it was not a source-only upload. Please make another
source-onl
Source: python-django-rest-framework-guardian
Version: 0.3.0-1
Severity: important
X-Debbugs-CC: fl...@debian.org
Dear python-django-rest-framework-guardian maintainer,
The package python-django-rest-framework-guardian you maintain in Debian saw
only the initial upload back in December. As a resu
Source: namecheap
Version: 0.0.3-2
Severity: important
Dear namecheap maintainer,
Your package namecheap in Debian only saw the very first initial upload. As a
result, this upload will not migrate to Testing.
Please make another source-only upload to allow Testing migration. You may
find more in
Package: prometheus
Severity: wishlist
I'm working with the Puppet community to maintain a Prometheus Puppet
module that's available here:
https://github.com/voxpupuli/puppet-prometheus/
We recently introduced a new feature where the systemd unit file is
hardened. I think it would be a great add
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "libbpf"
* Package name: libbpf
Version : 0.0.6-1
Upstream Author : NA
* URL : https://github.com/libbpf/libbpf
* License : LGPL-2.1
* Vcs
On Wed, Feb 05, 2020 at 01:26:31PM +, Simon McVittie wrote:
> On Wed, 05 Feb 2020 at 08:18:41 +0100, rene.engelh...@mailbox.org wrote:
> > Thanks, yes, that prevents the install of the "old"
> > gobject-introspection with the new python3 from experimental.
>
> Sorry, I wasn't thinking straight
Thanks! Do you know why only ppc64el fails?
On February 5, 2020 7:19:17 a.m. CST, "Frédéric Bonnard"
wrote:
>Package: src:digikam
>Version: 4:6.4.0+dfsg-1
>Control: tags -1 ftbfs patch
>
>--
>
>Dear maintainer,
>latest 4:6.4.0+dfsg-1 fails to build on ppc64el here :
>https://buildd.debian.org/
Hi All,
On Fri, Jan 31, 2020 at 04:28:34PM +, Sudip Mukherjee wrote:
> On Fri, Jan 31, 2020 at 4:11 PM Ben Hutchings wrote:
> >
> > On Wed, 2020-01-15 at 12:50 +, Sudip Mukherjee wrote:
> > > Hi Jonathan,
> > >
>
> >
> > So on balance I support moving libbpf out to a separate source pac
Dear Bas,
indeed the problem is related to xarray, but IMHO the problem is in the
latest version of the xarray package which seems to be broken.
The xarray.core subpackage (wihic is also used in xarray/__init__.py)
seems to be totally missing.
I'm going to ressign to python-xarray.
kind regards
Source: ipmitool
Version: 1.8.18-8
Severity: important
Tags: security upstream
Control: found -1 1.8.18-6
Control: found -1 1.8.18-3
Hi,
The following vulnerability was published for ipmitool.
CVE-2020-5208[0]:
| It's been found that multiple functions in ipmitool before 1.8.19
| neglect proper
FWIW, I rebuilt 4.1.1 sogo and sope packages from bullseye modified
slightly to link against OpenSSL instead of GnuTLS, installed on a
production buster system, success!
Thank you Adi Kriegisch for pointing this out.
--
Gerald Turner Encrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 3
Package: ksh,ksh93
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Control: found -1 2020.0.0-5
Control: found -1 93u+20120801-6
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another
On Tue, Feb 04, 2020 at 03:48:32PM -0800, Josh Triplett wrote:
> I would suggest testing on a c5.large. t2 and t3 have shared CPUs, so
> they have less consistent boot time. c5.large is about the same cost as
> t3.large, but will have far more consistent performance.
Performance definitely seems t
control: tags -1 pending
ongoing the following as NMU
On Mon, 3 Feb 2020 18:13:07 +0100 Gianfranco Costamagna
wrote:
> control: tags -1 patch
>
> Author: Gianfranco Costamagna
> Last-Update: 2020-02-03
>
> --- gst-plugins-bad1.0-1.16.2.orig/configure.ac
> +++ gst-plugins-bad1.0-1.16.2/config
Package: wifite
Version: 2.5.0~git20191114-2
Hi,
I've just prepare a MR [1] to fix this issue.
Please consider apply it.
[1] https://salsa.debian.org/pkg-security-team/wifite/merge_requests/1
Cheers,
eamanu
Because this changes the versioning scheme from kernel releases
(libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
believe.
CC'ing debian-devel for discussion/consensus, per Debian Policy Manual 5.6.12.
Christian
Package: wnpp
Owner: Judit Foglszinger
Severity: wishlist
* Package name: braillefont
Version : git
Upstream Author : Adam Borowski
* URL : https://github.com/kilobyte/braillefont
* License : Public Domain (CC0)
Programming Lang: C
Description : Prints
On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
wrote:
>
> Because this changes the versioning scheme from kernel releases
> (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> version numbers (0.0.6-1), the epoch needs to be incremented to 1 I
> believe.
I had this doubt but
Source: pg-fact-loader
Version: 1.5.2-1
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pg-fact-loader.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2018-11-29 04:36:36.0 -1200
+++ debia
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I just realized that the 340.108 release of nvidia-settings contained
not only version number bumping (therefore I initially planned to not
update nvidia-settings-legacy-340xx a
Source: pgl-ddl-deploy
Version: 1.5.1-1
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/pgl-ddl-deploy.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2019-01-15 05:04:16.0 -1200
+++ debia
Package: postgresql-11-python3-multicorn
Version: 1.3.4-31-g9ff7875-2
Severity: normal
Tags: upstream patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8
FYI: The multicorn.so PostgreSQL plugin will not be linked to libpython
when built under Python 3.8, without this patch:
https://git
On Wed, 2020-02-05 at 22:42 +, Sudip Mukherjee wrote:
> On Wed, Feb 5, 2020 at 10:22 PM Christian Barcenas
> wrote:
> > Because this changes the versioning scheme from kernel releases
> > (libbpf-dev and libbpf0 currently are at 5.4.13-1 in sid) to libbpf
> > version numbers (0.0.6-1), the epo
s/Version : git/Version : 0.0.20161007~14b2b1a/
signature.asc
Description: This is a digitally signed message part.
Version : 0~20161007~14b2b1a
signature.asc
Description: This is a digitally signed message part.
I think this is fixed
byhttps://github.com/seebk/GIMP-Lensfun/commit/ca4511c1a4dd8edabe86e4a943861fda07b7e86c
Feel free to 0day NMU, I don't have much time right now.
I did a test build with that commit added as a quilt patch and it built
successfully, so I went ahead with the 0-day NMU. Debdi
reopen 950172
close 950170 0.2.4-1.1
thanks
Sorry I copy/pasted the wrong bug number into the changelog.
tags 950171 +patch
tags 950171 +fixed-upstream
thanks
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.
Upstream fixed this in commit 1ecee9a47717e36cb8a3925d011d1a6de11d631c
I applied that commit (minus the changes to the upstream changelog
On Wed, Feb 05, 2020 at 04:27:23PM -0500, Noah Meyerhans wrote:
> On Tue, Feb 04, 2020 at 03:48:32PM -0800, Josh Triplett wrote:
> > I would suggest testing on a c5.large. t2 and t3 have shared CPUs, so
> > they have less consistent boot time. c5.large is about the same cost as
> > t3.large, but wi
Source: cluster3
Version: 1.59-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
cluster3 does FTBFS in a minimal buildd chroot:
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh: error: unable to load addon python3: Can't locate
Debian/De
Package: pingus
Version: 0.7.6-5
Severity: serious
Tags: upstream
Justification: ftbfs
Dear Maintainer,
pingus ftbfs against the new boost1.71 as signals library is removed.
There has been a lot of development since 0.7.6 at
https://gitlab.com/pingus/pingus and it almost builds fine with only
mi
On Mon, 20 May 2019 15:34:34 +0200 Mattia Rizzolo wrote:
> On Mon, May 20, 2019 at 03:32:26PM +0200, Dominik George wrote:
> > as I needed libswiften to build something, I went fixing the most important
> > bugs in the package so it at least builds again in current sid.
> >
> > Would you want me t
Package: ftp.debian.org
Severity: normal
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915805
RC-buggy, uses qt4 / openssl 1.0 / boost signals library that no longer
exists / not in testing.
I don't see any reverse depends or build-depends, please remove from unstable.
Regards,
Dimitri.
Package: mount
Version: 2.33.1-0.1
Severity: minor
-- Additional info:
Using mount with '-f' will write to /run/mount/utab.
I think the '-n' option should be included implicitly since it is just a
simulation?
When the root user does a mount with '-f' on a device previously mounted by
another us
Source: swupdate
Version: 2019.04+git20190903.c3ef374-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
swupdate/experimental FTBFS during separate arch and indep builds (as
done on the buildds). But it builds fine if both are being done within
one build process.
tags 950310 +patch
thanks
This build failure is caused by missing "#include " in a couple of
files. I would guess that in the past the header was pulled in indirectly.
I fixed this in raspbian, a debdiff should appear soon at
https://debdiffs.raspbian.org/main/n/nomacs
Rt
tags 950172 +patch
thanks
This build failure was a simple case of a missing #include "exiv2/error.hpp" ,
I fixed it in raspbian, a debdiff should appear soon at
https://debdiffs.raspbian.org/main/g/gpscorrelate no intent to NMU in debian.
On Mon, Feb 3, 2020 at 3:50 PM Felipe Sateler wrote:
>
>
> On Sun, Feb 2, 2020, 17:04 Zbigniew Jędrzejewski-Szmek
> wrote:
>
>> On Thu, Jan 30, 2020 at 11:51:48PM -0300, Felipe Sateler wrote:
>> > On Thu, Jan 30, 2020 at 6:40 PM Michael Biebl wrote:
>> >
>> > > Hi Felipe
>> > >
>> > > Am 30.01.
On Wed, Feb 05, 2020 at 03:31:28PM -0500, Boyuan Yang wrote:
> Source: zookeeper
> Version: 3.4.13-4
> Severity: important
> X-Debbugs-CC: ebo...@apache.org tmanc...@debian.org
>
> Dear zookeeper maintainers,
>
> The latest upload of package zookeeper introduced the new binary package
> (python3-
On 2/5/20 10:02 PM, Antonio Valentino wrote:
> indeed the problem is related to xarray, but IMHO the problem is in the
> latest version of the xarray package which seems to be broken.
> The xarray.core subpackage (wihic is also used in xarray/__init__.py)
> seems to be totally missing.
>
> I'm goi
tags 950402 +patch
thanks
This build failure is fixed by upstream commit
faaa552de9ec099184d131c08b76ae0b1ce4f5ec , I adapted it to apply to the debian
package and was able to sucessfully build the patched package in a raspbian
bullseye-staging environment.
I have uploaded the fixed package t
On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> Package: src:gmp
> Version: 6.2.0+dfsg-3
>
> Since binutils/gcc meet some problem due to 2GB/3GB memory limitation
> on 32bit system.
Since GMP has built on all architectures, so I don't understand what problem
you are trying to solve. Pl
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi,
node-dot-prop is vulnerable to a prototype pollution. This upstream
patch fixes the problem.
Cheers,
Xavier
diff --git a/debian/changelog b/debian/changelog
index 84868fc..f750
On Tue, 4 Feb 2020 09:23:34 +0100 Christoph Berg wrote:
> Hi,
>
> the new gmp version makes postgresql-pgmp crash on arm64:
>
> https://ci.debian.net/data/autopkgtest/testing/arm64/p/postgresql-pgmp/
4173638/log.gz
> (linked from https://packages.qa.debian.org/g/gmp.html)
...etc. Thanks, that
Source: opensubdiv
Version: 3.4.0-6
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
opensubdiv fails to cross build from source, because the build misses a
stringify tool. This tool is built during a native build and should be
provided for cross builds. It is installed into the op
Control: summary -1 This may be fixed already, need submitter to re-test.
Howdy Enrico,
On 15-Feb-2019, Enrico Zini wrote:
> It looks like --background has been added to the command line parser,
> but not to the function arguments to which the command line parser
> result is sent.
The code chan
Hi,
build & test fail for node-base64url. At least this has to be fixed:
--- a/debian/patches/2001_shared_types.patch
+++ b/debian/patches/2001_shared_types.patch
@@ -13,7 +13,7 @@ This patch header follows DEP-3:
http://dep.debian.net/deps/dep3/
+"target": "es5",
+"types": ["node"],
+
Steven Robbins 于2020年2月6日周四 下午1:23写道：
>
> On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> > Package: src:gmp
> > Version: 6.2.0+dfsg-3
> >
> > Since binutils/gcc meet some problem due to 2GB/3GB memory limitation
> > on 32bit system.
>
> Since GMP has built on all architectures, so I don't
Steven Robbins 于2020年2月6日周四 下午3:05写道：
>
> On Thursday, February 6, 2020 12:51:23 A.M. CST YunQiang Su wrote:
> > Steven Robbins 于2020年2月6日周四 下午1:23写道：
> >
> > > On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> > > > Package: src:gmp
> > > > Version: 6.2.0+dfsg-3
> > > >
> > > > Since binut
On Thursday, February 6, 2020 12:51:23 A.M. CST YunQiang Su wrote:
> Steven Robbins 于2020年2月6日周四 下午1:23写道：
>
> > On Tue, 4 Feb 2020 21:20:59 +0800 YunQiang Su wrote:
> > > Package: src:gmp
> > > Version: 6.2.0+dfsg-3
> > >
> > > Since binutils/gcc meet some problem due to 2GB/3GB memory limitat
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org,
pkg-rust-maintain...@lists.alioth.debian.org
Package name: boringtun
Version: 0.2.0
Upstream Author: Cloudflare, Inc.
License: BSD-3-Clause
URL: https://github.com/cloudflare/boringtun
Package: memcached
Version: 1.5.22-1
FTFBS on s390x.
I have seen the same in Ubuntu and filed/discussed this issue [1]
I have also filed a salsa MR [2] but it seems the MR was missed when
uploading 1.5.22-1 recently (I assume we raced each other working on this).
>From the logs on the buildds it
Package: apt-utils
Version: 1.8.2
Severity: minor
File: /usr/bin/apt-ftparchive
Tags: patch
I'm pretty sure this is a simple typo:
diff --git a/ftparchive/apt-ftparchive.cc b/ftparchive/apt-ftparchive.cc
index 077701c..51d492c 100644
--- a/ftparchive/apt-ftparchive.cc
+++ b/ftparc
Hi Andreas,
thanks for the bug report and all your QA work. It is really
appreciated.
On Thu, Feb 06, 2020 at 02:31:12AM +0100, Andreas Beckmann wrote:
> Furthermore, cluster3 is in non-free and not whitelisted for
> autobuilding, so it needs source+binary uploads. You should
> investigate whet
Hi,
Quoting Michael Biebl (2020-02-05 19:16:03)
> Am 05.02.20 um 18:15 schrieb Michael Biebl:
> > Am 05.02.20 um 13:28 schrieb Michael Biebl:
> >> Am 05.02.20 um 13:22 schrieb Michael Biebl:
> >>> Am 05.02.20 um 10:47 schrieb Andrey Rahmatullin:
> Attached.
> >>>
> >>>
> Running create a
101 - 165 of 165 matches
Mail list logo
