Bug#957029: ax25mail-utils: ftbfs with GCC-10

2020-08-04 Thread Christoph Berg
> The last commit for ax25mail-utils was back in late December 2019 and April > 11th 2020 for Linpac so I wouldn't call these as "very much dead upstream". Hi David, thanks for the feedback! I was glancing at the SF.net repo for ax25mail-utils but thought I had seen the last commit in 2018.

Bug#957029: ax25mail-utils: ftbfs with GCC-10

2020-08-04 Thread Christoph Berg
Control: tags -1 upstream wontfix > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -Wall -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c axgetlist.c > In file included from /usr/include/string.h:495, > from

Bug#967226: redundant-globbing-patterns [* *] for legitimate use of * and debian/*

2020-08-04 Thread Christoph Berg
Package: lintian Version: 2.80.0 Severity: normal python-skytools uses this copyright file: Files: * Copyright: Copyright (c) 2007-2017 Skytools Authors Copyright (c) 2007-2017 Marko Kreen License: ISC Files: skytools/apipkg.py Copyright: Copyright (c) holger krekel, 2009 License: MIT Files:

Bug#956975: Removing acfax (acfax: ftbfs with GCC-10)

2020-08-01 Thread Christoph Berg
Control: clone -1 -2 Control: reassign -2 ftp.debian.org Control: severity -2 normal Control: retitle -2 RM: acfax -- RoM: obsolete and buggy Re: To 956...@bugs.debian.org > I believe acfax has long reached the end of its usefulness. The build > log is full of ugly warnings, the last upstream

Bug#966022: lintian: False positive on missing-depends-on-sensible-utils with commands like i3-sensible-pager

2020-07-30 Thread Christoph Berg
Re: Raphaël Hertzog > E: i3-gaps-wm: missing-depends-on-sensible-utils usr/bin/i3 > E: i3-gaps-wm: missing-depends-on-sensible-utils usr/bin/i3-sensible-pager Additionally, the warnings are somewhat useless because it doesn't say which of the utils is being nagged about. Could the warning be

Bug#956975: Removing acfax (acfax: ftbfs with GCC-10)

2020-07-25 Thread Christoph Berg
Hi, I believe acfax has long reached the end of its usefulness. The build log is full of ugly warnings, the last upstream release was in 1998, the Debian release number has reached an impressive -17, and the program doesn't even start because it wants to open /dev/dsp which is long gone. I

Bug#964208: wsjtx: FTBFS without internet access

2020-07-05 Thread Christoph Berg
Re: tmanc...@debian.org > For now I'll add docbook-xsl to the B-D for wsjtx > and upload with the patch for XSLTPROC_OPTS to add --nonet. That's the best option, I think. Thanks! Christoph

Bug#964208: wsjtx: FTBFS without internet access

2020-07-05 Thread Christoph Berg
Re: tmanc...@debian.org > > I/O error : Attempt to load network entity > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > > warning: failed to load external entity > > "http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl; > > compilation error: file

Bug#964208: wsjtx: FTBFS without internet access

2020-07-04 Thread Christoph Berg
Ideally we should add some --nonet flag to make the failure both more obvious and reproducible.

Bug#964016: js8call: New Upstream Available

2020-07-03 Thread Christoph Berg
Re: Dave Hibberd > I'm happy to prepare an update on salsa, if no one has any objections! Fine with me. Thanks, Christoph

Bug#963887: UDD: 'duck' importer broken since 2020-05-25

2020-07-03 Thread Christoph Berg
Re: Baptiste BEAUPLAT > >> Maybe you could add that to vcswatch? > > The main differences between vcswatch and duck.d.n are: > > - history: duck used to keep 6 runs for each package, reporting only > after 3 failures. vcswatch only keeps the last run. vcswatch could be improved by not notifying

Bug#963699: PostgreSQL: WolfSSL support

2020-06-27 Thread Christoph Berg
Re: Florian Weimer > Sadly, upstream refused to clarify this > > > > At this point, I have no idea what the actual intent is. Ouch, that's a pretty non-helpful reply from upstream. Browsing the source I saw only the usual "version 2, or any

Bug#963699: PostgreSQL: WolfSSL support

2020-06-27 Thread Christoph Berg
Re: Florian Weimer > WolfSSL is licensed under the GPL, version 2 only. This means that > applications which use libpq and whose license is incompatible with > the GPL now violate the license of WolfSSL. Furthermore, the original > GPL compatibility problem is only addressed for programs which

Bug#963699: PostgreSQL: wolfSSL support

2020-06-26 Thread Christoph Berg
Re: Felix Lechner > > For postgresql-12, it fails at the configure stage > > Attached please find a WIP patch for wolfSSL support in postgresql-12. Hi, very cool, thanks! I'm on vacation for the next two weeks, so it's not very likely I can have a closer look during that time. What you could

Bug#924937: libpq5: OpenSSL license contamination of GPL reverse-dependencies

2020-06-24 Thread Christoph Berg
Re: Felix Lechner > There may be an alternative for some cases mentioned here. The wolfSSL > encryption library is a FIPS-certified, commercial product with a > fully usable, although incomplete, OpenSSL compatibility layer. Interesting pointer, thanks. For postgresql-12, it fails at the

Bug#932296: qa.debian.org: getwatch filling up /tmp

2020-06-21 Thread Christoph Berg
Re: Lucas Nussbaum > To get the watch file, UDD extracts the source package (once per source > package per version; then the watch file is stored in DB). /tmp on > ullmann only has 5.3GB available, which is too small to extract some > source packages in Debian (such as nvidia-cuda-toolkit). For

Bug#962828: libpgjava: CVE-2020-13692

2020-06-14 Thread Christoph Berg
Re: Salvatore Bonaccorso > CVE-2020-13692[0]: > | PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE. Hi, upstream switched the buildsystem in the .13 release, so uploading isn't as easy as I had hoped. Details are in https://github.com/pgjdbc/pgjdbc/issues/1440 (Seen the end of the

Bug#960385: dds: diff for NMU version 2.9.0-7.1

2020-06-10 Thread Christoph Berg
Re: Bruno Naibert de Campos > I've prepared an NMU for dds (versioned as 2.9.0-7.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks! I rescheduled it for immediate release. Christoph

Bug#962542: RFS: pat/0.9.0+dfsg.1-1 [ITP] -- Winlink client for sending and receiving radio mail

2020-06-09 Thread Christoph Berg
Hi Taowa, some comments on the package: The list of Depends is borked, I don't think you need any of the go packages at runtime as everything is statically linked. Why is libax25 there? It should be pulled in via shlibdeps, not explicitly. The description doesn't mention anything about

Bug#961594: Connection failed [IP: 151.101.112.204 80]

2020-06-03 Thread Christoph Berg
> > I wonder if turning on apt's Debug::Acquire::http would give more of a > > clue on where things go wrong? OTOH given this is highly intermittent > > it'd be quite noisy... Christoph, would you be able to give that a try? > > I'll do that now. The first two retries with that setting didn't >

Bug#962073: alsa-info is calling home without asking

2020-06-02 Thread Christoph Berg
Package: alsa-utils Version: 1.2.2-1 Severity: serious Hi, I just launched alsa-info and was surprised that it presented me with this popup box: ┌───┐ │ Newer version of ALSA-Info has been │ │ found

Bug#961594: Connection failed [IP: 151.101.112.204 80]

2020-06-02 Thread Christoph Berg
Re: Julien Cristau 2020-05-27 <20200527130809.GA1144124@chou> > > 26 11:58 11:53:34 Err http://security.debian.org/debian-security > > stretch/updates/main > > amd64 libldap-common all 2.4.44+dfsg-5+deb9u4 > > 26 11:58 11:53:34 Connection failed [IP: 151.101.112.204 80] It

Bug#961604: History was empty on first startup, but appeared on second launch

2020-05-26 Thread Christoph Berg
Package: diodon Version: 1.9.0-1 Severity: normal Hi, I just started using diodon because clipit notified me that it is gone. On the first startup, I selected some options (notably to track the primary selection and to sync selections), and tried to select some things. The history in the diodon

Bug#961594: Connection failed [IP: 151.101.112.204 80]

2020-05-26 Thread Christoph Berg
Package: mirrors,apt Severity: normal On the apt.postgresql.org buildds, I've repeatedly seen failures when retrieving files from security.debian.org. It started a few weeks ago, and stopped when I reported the problem on #debian-mirrors on the 20th when jcristau modified some SRV records for the

Bug#961532: devscripts: Missing package relation with pristine-tar (used by origtargz)

2020-05-25 Thread Christoph Berg
Re: Axel Beckert > to my surprise the devscripts has no package relation with pristine-tar > nor is it mentioned in devscripts' long package description despite > origtargz uses it unconditionally. pristine-tar is though mentioned in > the origtargz(1) man page and changelog.Debian.gz. > >

Bug#961501: remmina is calling home for update notifications

2020-05-25 Thread Christoph Berg
Package: remmina Version: 1.4.3+dfsg-2 Severity: grave Hi, this is the second time I've gotten an "What's new in Remmina" popup window out of the blue (i.e. not while actually using it, it's just sitting in the background at the moment). I suspect it is calling home, which would be a gross

Bug#960697: dh_missing manpage still defaults to --list-missing

2020-05-15 Thread Christoph Berg
Package: debhelper Version: 13 Severity: normal The dh_missing manpage wasn't updated for #917368: OPTIONS --list-missing Warn on stderr about source files not installed to somewhere. Note that many dh-tools acting on a path will mark the path as installed even if

Bug#960690: RM: pgadmin3 -- ROM; obsolete and unmaintained

2020-05-15 Thread Christoph Berg
Package: ftp.debian.org Severity: normal Please remove pgadmin3 from unstable. Upstream has long moved to pgadmin4, and attempts at keeping the old codebase alive by other people across the internet have failed to produce anything that works on all platforms. Let's stick a fork in it. Christoph

Bug#959665: git-buildpackage: please put a full stop after "New upstrem version X."

2020-05-04 Thread Christoph Berg
I prefer my debian/changelog entries to end with a dot, please allow for that. Christoph

Bug#959705: Please enable datachecksums for new clusters

2020-05-04 Thread Christoph Berg
Control: tags -1 upstream > Please consider enabling data checksums for new clusters on versions > that support them. From what I can tell, the upstream vibe became > something along the lines of "they dont hurt performance wise and > its a good idea generally". I agree it would be a good thing,

Bug#959165: udd vcswatch: 429 "Retry later" or "could not read Username" from Salsa

2020-04-30 Thread Christoph Berg
Control: reassign -1 python-asteval Re: Rebecca N. Palmer 2020-04-30 > spyder, python-asteval and beignet don't have a cgit in Vcs-Git. Hence, > while I agree it's a bug that apertium-bel does, this alone doesn't explain > either of the above messages. Salsa was down for two days, you can

Bug#959165: udd vcswatch: 429 "Retry later" or "could not read Username" from Salsa

2020-04-30 Thread Christoph Berg
Control: reassign -1 apertium-bel Re: Rebecca N. Palmer 2020-04-30 > Package: qa.debian.org > User: qa.debian@packages.debian.org > Usertags: udd > > Some packages' vcswatch pages have the error > > fatal: could not read Username for 'https://salsa.debian.org': No such > device or address

Bug#950920: [3dprinter-general] trimesh_3.5.25-1_amd64.changes REJECTED

2020-04-12 Thread Christoph Berg
retitle 950920 RFP: trimesh -- Python triangular meshes with an emphasis on watertight surfaces noowner 950920 thanks Re: Thorsten Alteholz 2020-04-08 > please mention trimesh-3.5.25/models/duck.dae in your debian/copyright. > > While you are at it, please also take care of the lintian error.

Bug#885265: Bug#936299: chirp: Python2 removal in sid/bullseye

2020-03-31 Thread Christoph Berg
Re: Moritz Muehlenhoff 2020-03-27 <20200327220044.s7cmyqmlnevty...@inutil.org> > > There's a py3 branch in upstream Hg that's activish. I haven't tried > > it yet, but it looks promising. I'll give it a try over the weekend > > and report back here. I've pushed the new branch to our git, but it's

Bug#947763: "aCount" is not a spelling error of "account"

2020-03-30 Thread Christoph Berg
Re: Felix Lechner 2020-03-30 > Hi Christoph, > > On Mon, Dec 30, 2019 at 2:51 AM Christoph Berg wrote: > > > > "aCount" is hardly a spelling error for "account". It's not even > > present in the source, but only in the "strings /usr/bin/cqrl

Bug#885265: Bug#936299: chirp: Python2 removal in sid/bullseye

2020-03-27 Thread Christoph Berg
Re: Moritz Mühlenhoff 2020-03-27 <20200327215634.GA1565432@pisco.westfalen.local> > On Sun, Oct 13, 2019 at 07:16:47PM +, Chris Knadle wrote: > > There has been some discussion about #936299 on the upstream mailing list, > > and > > there have been a few upstream commits starting to port the

Bug#955036: "convenience copies" should be named "embedded code copies"

2020-03-27 Thread Christoph Berg
Package: debian-policy Version: 4.5.0.0 Severity: wishlist Yesterday I was looking for a document to show upstream why Debian thinks embedded code copies are bad. I started with looking in policy, but completely missed section "4.13. Convenience copies of code" because it doesn't mention "embed".

Bug#954979: RM: postgresql-11 -- ROM; superseded by postgresql-12

2020-03-26 Thread Christoph Berg
Package: ftp.debian.org Severity: normal Please remove postgresql-11 from unstable, we have postgresql-12 now. Furthermore, it's uninstallable now because of clang-9, and fixing that doesn't make sense, removing is easier. There's one single rdependency left (postgresql-11-pgl-ddl-deploy, plus

Bug#954897: pydxcluster: should this package be removed?

2020-03-25 Thread Christoph Berg
Re: Sandro Tosi 2020-03-25 <158509215087.18239.15325100274815623896.report...@zion.matrix.int> > i believe this package should be removed: +1 from me. Christoph

Bug#954341: lintian: What's going on with "field-too-long Installed-Build-Depends"?

2020-03-22 Thread Christoph Berg
Control: severity -1 important Re: Felix Lechner 2020-03-20 > > E: pkg-perl-tools buildinfo: field-too-long Installed-Build-Depends (11190 > > chars > 5000) > > I will disable the tag for this particular buildinfo field in the near future. This is causing lots of salsa-ci pipelines to fail

Bug#954186: RFS: libxtrxdsp/0.0.1+git20190830.eec2864-2 -- Library of DSP functions, developed for XTRX SDR

2020-03-19 Thread Christoph Berg
Re: Sepi Gair 2020-03-18 <370975eaac3fc60a4dc57cb13d003dc9ac47d78b.ca...@email.cz> > * Package name: libxtrxdsp >Version : 0.0.1+git20190830.eec2864-2 Hi Sepi, I suggest we wait with this upload until the -1 version has passed NEW. Christoph

Bug#861789: Please provide database.target as a synchronization point for applications providing databases and needing databases

2020-03-19 Thread Christoph Berg
Re: Michael Biebl 2020-03-18 <27361fa3-c814-8787-6e10-c5d13956a...@debian.org> > My concerns are still the same as I outlined above, so I think such a > database.target would not be too useful given it would only be very > vaguely defined. Also, we shouldn't invent a snowflake solution in Debian

Bug#953547: RFS: libusb3380/0.0.1+git20190125.c83d1e9-1 [ITP] -- USB3380 abstraction layer for libusb: development

2020-03-10 Thread Christoph Berg
Hi Sepi, there's a missing copyright attribution: ./cmake_modules/Findlibusb-1.0.cmake: # Adapted from cmake-modules Google Code project # # Copyright (c) 2006 Andreas Schneider # # (Changes for libusb) Copyright (c) 2008 Kyle Machulis # # Redistribution and use is allowed according to the

Bug#953204: postgresql-11 segmentation fault

2020-03-05 Thread Christoph Berg
Control: tags -1 moreinfo Re: Tim Bishop 2020-03-05 <27c7ad55-9e4c-7b03-9391-4ef3c660a...@inroads.ai> > I tried to run postgresql through gdb but was unable to reproduce the error > this way. The query is running accross multiple child processes and I'm > unable to determine which one is causing

Bug#953157: improve brittle pg_lsclusters parsing

2020-03-05 Thread Christoph Berg
Re: Tomas Pospisek 2020-03-05 <158341012952.22047.14835993299149410230.reportbug@hier> > if for whatever reason a cluster status line will contain the string > `Port`, then that line will be filtered out. > > I instead suggest to do: > > PORT=$(($(pg_lsclusters | tail -n +2 | awk '{print

Bug#953120: "salsa.sh update_safe" with no extra arguments should error out

2020-03-04 Thread Christoph Berg
Package: devscripts Version: 2.20.2 Severity: normal $ cat config #SALSA_GROUP=debian-hamradio-team SALSA_GROUP=debian-hamradio-team/soapysdr SALSA_TOKEN_FILE=~/.priv/pw/salsa-token SALSA_IRKER=no SALSA_KGB=yes SALSA_IRC_CHANNEL='debian-hams;use_irc_notices=1;squash_threshold=3'

Bug#943636: uhd: b-d on python3-all-dev, but not built for all supported Python3 versions

2020-03-04 Thread Christoph Berg
Re: Matthias Klose 2019-10-27 > Package: src:uhd > Version: 3.14.1.1-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: python3.8 python3-all-dev > > The package build-depends on python3-all-dev, but does not build > extensions/libraries for all

Bug#952974: [Pkg-nagios-devel] Bug#952974: Typo /etc/icingweb2 in a lot of module packages

2020-03-02 Thread Christoph Berg
Re: Sebastiaan Couwenberg 2020-03-02 <58cea4eb-d7a5-7cca-aea8-0c4238c3f...@xs4all.nl> > > The typo "/etc/icingweb2" seems to be in a lot of icingweb2 module > > packages: > > Those are separate source packages from icingaweb2, and not maintained > within this team. Reassigning. Fwiw, I suspect

Bug#952974: Typo /etc/icingweb2 in a lot of module packages

2020-03-02 Thread Christoph Berg
Package: icingaweb2 Version: 2.7.3-1 Severity: normal The typo "/etc/icingweb2" seems to be in a lot of icingweb2 module packages: https://codesearch.debian.net/search?q=icingweb=1 icingaweb2-module-ipl_0.1.1-1/debian/rules # enable module mkdir -p

Bug#948728: apt doesn't completely remove "postgresql-11" dependencies

2020-03-02 Thread Christoph Berg
Re: Mario E. Weisz 2020-01-12 > $ sudo apt autoremove > > leaves these packages behind: > postgresql-client-11 As mentioned in one of the other bugs you filed, this was caused by /etc/apt/apt.conf.d/01autoremove-postgresql. I've now replaced this with a smarter solution that only marks

Bug#950920: RFP: trimesh -- Trimesh is a Python library for loading and using triangular meshes with an emphasis on watertight surfaces

2020-03-01 Thread Christoph Berg
Control: retitle -1 ITP: trimesh -- Python triangular meshes with an emphasis on watertight surfaces Control: owner -1 ! Control: tag -1 pending Status: Waiting for https://github.com/mikedh/trimesh/issues/728 Christoph

Bug#952572: procps: move binaries back to /bin

2020-02-26 Thread Christoph Berg
Another place where things must be called with absolute path: /lib/systemd/system $ grep bin/kill * gdm3.service:ExecReload=/bin/kill -SIGHUP $MAINPID gdm.service:ExecReload=/bin/kill -SIGHUP $MAINPID network-manager.service:#ExecReload=/bin/kill -HUP $MAINPID

Bug#919385: postgresql-common: alter system set port ignored by pg-commands

2020-02-24 Thread Christoph Berg
Re: To wim.bert...@ucll.be 2019-02-27 <20190227143731.gc25...@msg.df7cb.de> > 4. Patch PostgreSQL such that it puts the port into external_pid_file, > i.e. into /var/run/postgresql/11-main.pid > > The bottom line is that #4 looks most attractive, but I'm not fixing > this in postgresql-common

Bug#952116: [ru...@bogodyn.org: Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL]

2020-02-23 Thread Christoph Berg
Re: Tom Russo 2020-02-23 <20200223182310.ga7...@bogodyn.org> > The script looks in the top level of the Xastir source tree being built > for the presence of a .git directory. The fact that the source tree is under > a package directory that is itself in git should have no impact (there will >

Bug#952116: [ru...@bogodyn.org: Re: [Xastir] Fwd: Bug#952116: xastir: Impossible to transmit due to malformed TOCALL]

2020-02-23 Thread Christoph Berg
Re: Tom Russo 2020-02-23 <20200223174551.gd5...@bogodyn.org> > That won't work if you're building the Debian package > out of a tarball (the trick involves looking for a .git directory, and if > found, invoking a git log command to get the current SHA-1). Fwiw, these tricks are often a PITA for

Bug#951001: quisk: SoapySDR support

2020-02-09 Thread Christoph Berg
> Also, how about moving quisk to the debian-hamradio-team on salsa? > I'd be interested to work on quisk. I should have checked Salsa before writing that, https://salsa.debian.org/debian-hamradio-team/quisk Thanks! Christoph

Bug#951001: quisk: SoapySDR support

2020-02-09 Thread Christoph Berg
Package: quisk Version: 4.1.52-1 Severity: wishlist Hi, I just discovered quisk - afaict the only SDR application in Debian that can transmit and not just receive. Unfortunately, it's not built with soapysdr support which my LimeSDR would require. Afaict all it takes is build-depending on

Bug#947151: [3dprinter-general] Bug#947151: Bug#947151: cura: GUI unusable under scaled desktop

2020-02-08 Thread Christoph Berg
Re: Gregor Riepl 2020-01-29 <9ab5ab88-5337-9474-0683-fb21a6317...@gmail.com> > I think the original upstream bug was this one: > https://github.com/Ultimaker/Cura/issues/5296 #947151 is about *scaled* desktops, while #5296 is about generally broken or empty display. The core issue might still be

Bug#950934: RM: postgresql-12-wal2json [armel armhf i386 mipsel] -- NBS; Package only supports 64bit

2020-02-08 Thread Christoph Berg
Package: ftp.debian.org Severity: normal Hi, please remove the 32bit packages of postgresql-12-wal2json in unstable. Thanks. Reference: https://github.com/eulerto/wal2json/issues/142 Christoph

Bug#950734: Remove postgresql-11 from testing

2020-02-07 Thread Christoph Berg
Re: Graham Inggs 2020-02-07 > Done. Thanks! Christoph

Bug#950608: gmp 6.2.0 crashes postgresql-pgmp

2020-02-06 Thread Christoph Berg
Re: Steven Robbins 2020-02-06 <4839510.uz11uGdL23@riemann> > > 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.

Bug#950734: Remove postgresql-11 from testing

2020-02-05 Thread Christoph Berg
Package: postgresql-11 Version: 11.6-2~sid1 Severity: serious postgresql-11 should not be part of testing, please remove it, and all reverse-dependencies. The upstreams of the reverse-dependencies have all been pinged plenty of times, and have had enough time to fix their stuff. Thanks,

Bug#950608: gmp 6.2.0 crashes postgresql-pgmp

2020-02-04 Thread Christoph Berg
Source: gmp Version: 2:6.2.0+dfsg-3 Severity: grave 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) I can also see the crash on amd64 with

Bug#947151: [3dprinter-general] Bug#947151: cura: GUI unusable under scaled desktop

2020-01-29 Thread Christoph Berg
Re: Gregor Riepl 2019-12-22 > The bug is known, but I'm not sure if it is in python3-qt or in Cura itself. Do you know if it was already reported to upstream? I couldn't find it on github, but there's 967 issues open... Christoph

Bug#947151: [3dprinter-general] Bug#947151: Bug#947151: cura: GUI unusable under scaled desktop

2020-01-29 Thread Christoph Berg
Re: Kyle Robbertze 2020-01-29 <0b496332-2245-ee1b-8515-a2931ff12...@debian.org> > While the update means I can actually read some of the text, alignment > between checkboxes and labels is still broken as is the text displayed > on the screen. I have attached two screenshots of the issue I am

Bug#950033: missing dependencies on python3-healpy and python3-tk

2020-01-28 Thread Christoph Berg
Package: pymoctool Version: 0.5.0-4 Severity: normal pymoctool is missing dependencies on python3-healpy and python3-tk: $ pymoctool ../cepheiden.moc --plot Traceback (most recent call last): File "/usr/bin/pymoctool", line 40, in main() File "/usr/bin/pymoctool", line 33, in main

Bug#947244: shouldn't include Architectures in sources file by default

2020-01-23 Thread Christoph Berg
Re: Wouter Verhelst 2020-01-23 <20200123130529.gf1...@grep.be> > > (On a similar ticket, should "deb-src" be include by default? At least > > a switch to configure that at "enable" time would be nice.) > > I think it should. It doesn't hurt? Sometimes I try getting rid of extra things to

Bug#949377: dh_python --buildsystem=cmake doesn't pass recently added Python_EXECUTABLE variable

2020-01-22 Thread Christoph Berg
Fwiw, olasd found a way to make it work using the current dh_python version: https://salsa.debian.org/3dprinting-team/libarcus/commit/2503ec8273bdb67a710a0d2b633efa8909ed083c But having that built-in would be nicer. Christoph >From 2503ec8273bdb67a710a0d2b633efa8909ed083c Mon Sep 17 00:00:00

Bug#949428: postgresql-12: FTBFS with libxml2 2.9.10 (uses xml2-config)

2020-01-20 Thread Christoph Berg
Control: tags -1 wontfix Re: Mattia Rizzolo 2020-01-20 <20200120194247.ga3704...@mapreri.org> > your package is using `xml2-config` to detect and use libxml2. I'm > removing that script Hi, please don't do that unless you get libxml2 upstream to properly announce the deprecation first.

Bug#949377: dh_python --buildsystem=cmake doesn't pass recently added Python_EXECUTABLE variable

2020-01-20 Thread Christoph Berg
Package: dh-python Version: 4.20191017 Severity: normal libarcus and libsavitar from the 3dprinting team have the problem that the cmake jobs called from dh_auto_install use the wrong python version, note that 3.8 is used in the 3.7 install pass:

Bug#948797: fails to compile cqrlog on mipsel: Fatal: Internal error 200603251

2020-01-16 Thread Christoph Berg
Re: Graham Inggs 2020-01-14 > I think this is #948803 in binutils. > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948803 Thanks for the pointer. This one has been fixed in the meantime. Re: To Graham Inggs 2020-01-13 <20200113143325.ge11...@msg.df7cb.de> > Oh, actually I didn't look

Bug#948797: fails to compile cqrlog on arm64: cqrlog.lpr(84) Warning: (9034) "crtbegin.o" not found, this will probably cause a linking failure

2020-01-13 Thread Christoph Berg
Re: Graham Inggs 2020-01-13 > > Other architectures are fine. > > I don't think anything changed in lazarus or fpc. > I uploaded doublecmd yesterday and it build successfully on arm64[1]. > Today it fails the reproducible build[2] with the same error as cqrlog. Oh, actually I didn't look

Bug#948797: fails to compile cqrlog on arm64: cqrlog.lpr(84) Warning: (9034) "crtbegin.o" not found, this will probably cause a linking failure

2020-01-13 Thread Christoph Berg
Source: lazarus Version: 2.0.6+dfsg-3 Severity: normal Hi, I think this is a bug in lazarus on arm64, but maybe I'm wrong: https://buildd.debian.org/status/fetch.php?pkg=cqrlog=arm64=2.4.0-3=1578918606=0 700 291.337/324.064 Kb Used 800 291.987/324.064 Kb Used (9009) Assembling dlogupload

Bug#948549: pgadmin3: Segfault when trying toi start query tool

2020-01-13 Thread Christoph Berg
Re: To Erwin Brandstetter 2020-01-10 <20200110140734.ge30...@msg.df7cb.de> > I can revert to the old wxgtk package on the older distributions, but > maybe we have to accept that pgadmin3 is dead now and ultimately > remove it from unstable. I just updated the pgadmin3 packages on apt.pg.o to use

Bug#813487: pgbouncer: Upgrading pgbouncer drops connections when run with systemd

2020-01-12 Thread Christoph Berg
Re: Peter Eisentraut 2020-01-11 > It might be possible to do this if we have systemd organize the file > descriptor passing (using socket activation and all that). It's something > I've been meaning to look into, but it would be a development effort, not > just a packaging change. That sounds

Bug#948549: pgadmin3: Segfault when trying toi start query tool

2020-01-10 Thread Christoph Berg
Re: Erwin Brandstetter 2020-01-10 <157862519463.9993.8745255910335394793.reportbug@brsanuc5> > Package: pgadmin3 > Version: 1.22.2-6.pgdg100+1 > Severity: grave > Justification: renders package unusable > > Introduced with installing pgadmin3 1.22.2-6.pgdg18.04+1 > Now it segfaults every time

Bug#948571: Description isn't descriptive

2020-01-10 Thread Christoph Berg
Package: libstb0 Version: 0.0~git20190817.1.052dce1-1 Severity: normal Hi, libstb{0,-dev}'s Description is Description-en: single-file public domain (or MIT licensed) libraries for C/C++ It includes the following modules: * stb_vorbis.c: decode ogg vorbis files from file/memory to

Bug#889883: dh-lua: Please disable --silent in libtool calls

2019-12-31 Thread Christoph Berg
Re: Jean-Michel Vourgère 2018-02-08 <2927066.44csPzL39Z@deimos> > My rrdtool package uses dh-lua. I get a bunch of compiler-flags-hidden > warnings in build log scanner [1], from package blhc. Hi, I'm getting these warnings on hamlib. I'd appreciate if the dh-lua fix were uploaded to unstable

Bug#947763: "aCount" is not a spelling error of "account"

2019-12-30 Thread Christoph Berg
Package: lintian Version: 2.25.0 Severity: normal I: cqrlog: spelling-error-in-binary usr/bin/cqrlog aCount account "aCount" is hardly a spelling error for "account". It's not even present in the source, but only in the "strings /usr/bin/cqrlog" output. I suggest excluding CamelCased words from

Bug#947244: shouldn't include Architectures in sources file by default

2019-12-23 Thread Christoph Berg
Package: extrepo Version: 0.6 Severity: normal Hi, I just enabled the postgresql repo here: Holen:10 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main Sources [42,7 kB] Holen:11 http://apt.postgresql.org/pub/repos/apt bullseye-pgdg/main amd64 Packages [147 kB] Holen:12

Bug#947067: extrepo UX quirks

2019-12-20 Thread Christoph Berg
Package: extrepo Version: 0.6 Severity: wishlist These could raise nicer warnings: $ extrepo Use of uninitialized value $cmdlower in ucfirst at /usr/bin/extrepo line 98. Undefined subroutine ::ExtRepo::Commandsrun called at (eval 15) line 1. ...propagated at /usr/bin/extrepo line

Bug#946359: pg-snakeoil: Selftest apears to be broken

2019-12-20 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2019-12-19 <20191219193659.t6qzowamewru7yfk@flow> > > One bit that could have been relevant is that I'm running on schroot > > with tmpfs on an overlay fs. > > But that part is transparent. There's one thing that doesn't work on overlayfs, renaming (underlay?)

Bug#946957: postgresql-common: pg_upgradecluster woe: postgres fails to restart after upgrade

2019-12-19 Thread Christoph Berg
Re: Julian Gilbey 2019-12-18 <20191218140411.ga8...@d-and-j.net> > Running 'invoke-rc.d postgresql start' does not help: it still does > not bring up the postgresql server. Hi, did you invoke pg_upgradecluster as 'postgres' user? In that case, systemd doesn't get notified that a new cluster

Bug#946359: pg-snakeoil: Selftest apears to be broken

2019-12-19 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2019-12-18 <20191218225837.qttuxpwrbo5ukpr3@flow> > > $ sudo -u clamav freshclam --verbose > > what happens if you strip the sudo part? One of the first thing is to > change to the clamav user (well so is my memory and the /var/…/clamav is > owned by clamav so…)?

Bug#946359: pg-snakeoil: Selftest apears to be broken

2019-12-18 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2019-12-11 <20191211141451.tn2u64ssgarpgz25@flow> > > The test fails in my sid chroot as well because freshclam can't > > download the database, /var/lib/clamav/ is empty except for a "tmp" > > directory. > > Do you have a special inet setup? Kind of web proxy or

Bug#946938: postgresql-common: pg_upgradecluster woes: fails to upgrade to v12 because ee key too small; postgres also fails to restart after upgrade

2019-12-18 Thread Christoph Berg
Control: reassign -1 ssl-cert Control: affects -1 postgresql-common Re: Julian Gilbey 2019-12-18 <157666085037.520017.6645946659722479335.report...@erdos.d-and-j.net> > I've just tried upgrading postgresql from version 11 to version 12, > following the instructions in README.Debian. Hi, did

Bug#938510: soapysdr: Python2 removal in sid/bullseye

2019-12-17 Thread Christoph Berg
Hi Andreas, I pushed some changes to git. Could you review these? Christoph

Bug#946776: datefudge --static doesn't fix the sub-seconds part

2019-12-15 Thread Christoph Berg
Package: datefudge Version: 1.23 Severity: important I just tried to use `datefudge --static` to fix varying timestamps in some sphinx documentation, but ultimately failed because the sub-seconds part of the time is still not constant: $ datefudge --static '@1576429380' date '+%T %N' 18:03:00

Bug#946627: ITP: js8call -- Amateur Radio Digital Mode providing weak signal keyboard to keyboard messaging

2019-12-12 Thread Christoph Berg
Package: wnpp Severity: wishlist Owner: Christoph Berg * Package name: js8call Version : 2.0.1 * URL : http://js8call.com/ * License : GPL, LGPL, BSD, MIT/X, etc.) Programming Lang: C++, Fortran Description : Amateur Radio Digital Mode providing weak

Bug#946359: pg-snakeoil: Selftest apears to be broken

2019-12-11 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2019-12-07 <20191207201131.v563o62fpmjnz7ol@flow> > clamav can't migrate because the debci-test for pg-snakeoil fails. I > *think* that the test itself is somehow borken since after installing > the bytecode.cvd itself appears on my system. Could you please take a >

Bug#946557: buster-pu: package clamav/0.102.1+dfsg-0+deb10u1

2019-12-11 Thread Christoph Berg
Re: Sebastian Andrzej Siewior 2019-12-10 <20191210224647.dk4svg65hleftr7r@flow> > +clamav (0.101.4+dfsg-0+deb10u1) buster; urgency=medium > + > + - update symbols file (bump to 101.4 and drop unused cli_strnstr). Did all these symbols change semantics? I'm surprised to see so many symbols

Bug#946462: postgresql-common: autopkgtests should have versioned postgresql deps

2019-12-09 Thread Christoph Berg
Re: Dimitri John Ledkov 2019-12-09 <157589727865.175171.11228668415175195788.reportbug@ottawa.168.1.5> > Does above makes sense at all? It does, see also #944457. Christoph

Bug#946251: Tests are failing since postgresql-common 208

2019-12-08 Thread Christoph Berg
Re: Sebastien Bacher 2019-12-06 <18cb3ad6-93b1-7044-5edd-023c5ca0a...@debian.org> > Package: pglogical-ticker > Version: 1.4.0-1 > > The tests are failing since postgresql-common got updated to 208 > https://ci.debian.net/packages/p/pglogical-ticker/unstable/amd64/ > > pg_buildext: error:

Bug#900015: missing pkg-config support is blocking switch to mbedTLS in libgit2

2019-12-01 Thread Christoph Berg
Re: James Cowgill 2019-04-30 <403b111b-ff0a-62a2-71d1-150b3c01b...@debian.org> > > fldigi 4.1.02's configure check probes for mbedtls >= 2.16 using > > pkg-config (and builds the embedded copy otherwise), so it seems > > this has been implemented upstream in mbedtls by now. Can we have > > it in

Bug#788813: [slony1-2-bin] initscript and perl tools do not agree on pidfile name

2019-11-29 Thread Christoph Berg
Control: tags -1 help Re: Antti Salmela 2015-11-13 <20151113104231.ga27...@asalmela.iki.fi> > With the following patch to the /etc/init.d/slony1, and renaming > /etc/slony1/slon_tools.conf > to /etc/slony1/slon_tools_replication.conf, and altering > /etc/default/slony1 to include cluster name, I

Bug#813487: pgbouncer: Upgrading pgbouncer drops connections when run with systemd

2019-11-28 Thread Christoph Berg
Control: tags -1 upstream Re: Chris Butler 2016-02-02 <20160202131415.28076.48745.report...@taskrunner.staging.trac.jobs> > In the good old sysvinit days, an upgrade to pgbouncer could be done > seamlessly > because the init script used the -R flag to tell pgbouncer to take over from > the >

Bug#945573: RM: d-rats -- ROM; dead upstream and depends on obsolete pygtk

2019-11-27 Thread Christoph Berg
Package: ftp.debian.org Severity: normal Please remove d-rats from unstable. Thanks. Christoph

Bug#945468: RFH: pgq, pgqd, pgq-node, python-pgq, python-skytools -- Queuing for PostgreSQL

2019-11-25 Thread Christoph Berg
Package: wnpp Severity: normal I request help with maintaining the pgq family of packages. They implement a queuing mechanism on top of PostgreSQL, but I'm not using them myself. Packages are: pgq pgqd pgq-node python-pgq python-skytools Previously, this was a single package, skytools3, but

Bug#945005: RM: postgresql-11-*/experimental -- ROM; Newer version in unstable

2019-11-18 Thread Christoph Berg
Package: ftp.debian.org Severity: normal The PostgreSQL 12 transition left cruft behind in experimental that doesn't get automatically removed because the name of the binary packages changed from postgresql-11-* to postgresql-12-*. Please remove from experimental (source package names):

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-16 Thread Christoph Berg
Re: Chris Lamb 2019-11-14 <36f7dff0-df0b-479b-aa5e-9018ce438...@www.fastmail.com> > 2.35.0~bpo9+1 and 2.35.0~bpo10+1 uploaded to {stretch,buster}-backports > respectfully. Thanks! Christoph

<    1   2   3   4   5   6   7   8   9   10   >