Bug#1032942: ITS: tnetstring3

2023-03-14 Thread Jan Niehusmann
Hi Bastian! On Tue, Mar 14, 2023 at 02:31:08PM +0100, Bastian Germann wrote: > Source: tnetstring3 > Severity: important > > I am filing this intend to salvage the tnetstring3 package which is > unmaintained. > The ITS is meant to remove the package from the archive when the waiting > period

Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.

2023-01-29 Thread Jan Niehusmann
On Sun, Jan 29, 2023 at 01:10:17PM +0200, Adrian Bunk wrote: > Keeping it "Architecture: any" will automatically (re)add it on > architectures whenever they gain ring support. [...] > Yes, since there are no reverse (build) dependencies > "reportbug ftp.debian.org" to remove the stale binaries >

Bug#1029943: RM: pushpin [mips64el mipsel ppc64el s390x alpha hppa hurd-i386 ia64 kfreebsd-amd64 kfreebsd-i386 m68k powerpc ppc64 riscv64 sh4 sparc64] -- RoM; FTBFS

2023-01-29 Thread Jan Niehusmann
Package: ftp.debian.org Dear ftpmasters, please remove pushpin for the listed architectures from unstable. It's currently not possible to build them, because a build-depencency, librust-ring-0.16+default-dev, is not available there. See #1029931 for details in case you are interested. Jan

Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.

2023-01-29 Thread Jan Niehusmann
On Sun, Jan 29, 2023 at 04:28:54AM +, Peter Michael Green wrote: > Package: pushpin > Version: 1.36.0-1 > Severity: serious > > The new version of pushpin added a dependency on jsonwebtoken, > unfortunately jsonwebtoken depends in ring, which is only available > on x86* and arm*. There is

Bug#1005629: zurl: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

2022-06-07 Thread Jan Niehusmann
severity 1005629 normal thanks On Tue, Jun 07, 2022 at 09:57:35PM +0200, Lucas Nussbaum wrote: > I tried again and confirmed that it builds fine now. > > When doing those archive rebuilds, I retry failed builds and only file > bugs when they failed two times. Maybe there was an error on the

Bug#1005629: zurl: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2

2022-06-07 Thread Jan Niehusmann
Hi, I'm unable to reproduce this build error. As it happens in a network related test, I also tried it inside a container with networking blocked. https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zurl.html shows that automated builds do work, in general. I still suspect that

Bug#892058: Your Debian key is expiring

2021-12-12 Thread Jan Niehusmann
On Sun, Dec 05, 2021 at 05:36:12AM -0800, felix.lech...@lease-up.com wrote: > If you like this service, please leave a favorable comment here [2]. > > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892058 This service was really helpful. Otherwise I would have missed the deadline,

Bug#988588: ftp.debian.org: please REJECT rust-rustls-native-certs from NEW queue

2021-05-16 Thread Jan Niehusmann
Package: ftp.debian.org Severity: normal The package rust-rustls-native-certs I uploaded 3 days ago contains a diff from upstream which may be a bad idea (changing a dependency to an older version). I'm currently not sure what's the best way to fix the issue, so I can't just upload an updated

Bug#953668: [Pkg-rust-maintainers] Bug#953668: cargo fails to find default X.509 certificates to validate https on powerpc

2020-11-28 Thread Jan Niehusmann
Hi, On Thu, Mar 12, 2020 at 11:07:08AM +0100, Fabian Grünbichler wrote: > I am not sure whether we want to work around it in cargo (by defaulting > to that location, for example), but this is related to > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927889 > > libgit2 picks up an

Bug#975630: ITP: condure -- HTTP/WebSocket connection manager

2020-11-24 Thread Jan Niehusmann
Package: wnpp Severity: wishlist Owner: Jan Niehusmann * Package name: condure Version : 1.1.0 Upstream Author : Justin Karneges * URL : https://github.com/fanout/condure/ * License : Apache-2.0 Programming Lang: Rust Description : HTTP/WebSocket

Bug#975206: zurl: FTBFS: Error: need libzmq >= 2.0!

2020-11-19 Thread Jan Niehusmann
Control: reassign -1 libzmq3-dev 4.3.3-3 Control: forcemerge 975151 -1 This FTBFS was caused by a missing dependency in libzmq3-dev 4.3.3-3, which was already fixed in libzmq3-dev 4.3.3-4. On Thu, Nov 19, 2020 at 10:57:00AM +0100, Lucas Nussbaum wrote: > Source: zurl > Version: 1.11.0-2 >

Bug#956691: fixed in psi 1.3-6

2020-07-02 Thread Jan Niehusmann
Hi Laurent, On Thu, Jul 02, 2020 at 10:03:06AM +0200, Laurent Bigonville wrote: > Just for my understanding, why did you switch to libhunspell instead of > libenchant-2? > > As said it seems to have support for enchant-2 in the code (there are > references to HAVE_ENCHANT2) Mainly to be

Bug#863650: Fix available

2020-05-05 Thread Jan Niehusmann
Hi, I submitted a patch for this issue upstream: https://github.com/pam-pgsql/pam-pgsql/pull/16 Jan

Bug#938673: tnetstring: Python2 removal in sid/bullseye

2019-09-02 Thread Jan Niehusmann
On Fri, Aug 30, 2019 at 07:55:57AM +, Matthias Klose wrote: > Package: src:tnetstring [...] > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. There is already a

Bug#925396: unblock: mudlet/1:3.7.1-1.1

2019-03-24 Thread Jan Niehusmann
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package mudlet mudlet was removed from testing only because its dependency lua-sql was removed. As lua-sql was unblocked and re-added (see

Bug#859841: Bug#891872: transition: curl

2018-05-18 Thread Jan Niehusmann
Hi Emilio, On Mon, Apr 23, 2018 at 08:38:30PM +0200, Emilio Pozuelo Monfort wrote: > Hmm, I just realised libcurl3 ships libcurl.so.4, so that explains the > conflict. > I just found the rationale for this in > https://salsa.debian.org/debian/curl/merge_requests/2. That means this will > have >

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2018-04-26 Thread Jan Niehusmann
Dear readers of this long-standing bug ticket, durign the last 3 weeks there was no real progress, but the release team at least noticed the open transition request (#891872). Unfortunately, there are some conflicts with other transitions. ("That means this will have to wait until there are no

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2018-04-04 Thread Jan Niehusmann
Current state of affairs: - curl built against openssl 1.1 was uploaded to experimental https://tracker.debian.org/news/937117/accepted-curl-7580-3-source-amd64-all-into-experimental-experimental/ - zurl built against that version of curl and openssl 1.1 was uploaded to experimental

Bug#891872: transition: curl

2018-03-03 Thread Jan Niehusmann
Hi, On Fri, Mar 02, 2018 at 10:04:44AM +0100, Emilio Pozuelo Monfort wrote: > Also zurl seems to need Qt with openssl 1.1, which is only in experimental > atm. > That shouldn't be a blocker for this though (we can temporarily kick it from > testing if necessary). But let's wait a bit and see. I

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2018-02-15 Thread Jan Niehusmann
To keep this BTS entry up to date: Unfortunately, I didn't see any progress regarding the status of libcurl3 during the last ~3 weeks. :-( References: https://salsa.debian.org/debian/curl/merge_requests/2 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858398

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2018-01-22 Thread Jan Niehusmann
To keep this BTS entry up to date: There seems to be some progress towards a solution at https://salsa.debian.org/debian/curl/merge_requests/2 On Fri, Dec 29, 2017 at 01:58:05PM +0100, Jan Niehusmann wrote: > After another 3 weeks, the status of libcurl3 unfortunately didn't > change

Bug#879811: psi-translations: update to version 1.3

2018-01-12 Thread Jan Niehusmann
Hi Boris, > > It looks that you do not have enough free time to maintain this package. > > > > How about maintaining of src:psi and src:psi-translations packages under > > umbrella of Debian XMPP Maintainers team [1] using git repos [2] at Salsa > > [3]? > > > > In this case I would prepare a

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2017-12-29 Thread Jan Niehusmann
After another 3 weeks, the status of libcurl3 unfortunately didn't change at all. The discussion on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858398 continues really slowly, and there is no sign of actual progress :-( Jan

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2017-12-07 Thread Jan Niehusmann
Just a small update to people following this issue: The qt5 already updated to openssl 1.1, so the only remaining blocker is curl. In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858398 there is some discussion about the right way to update curl, but I hope some agreement will be reached,

Bug#859841: zurl: Please migrate to openssl1.1 in Buster

2017-10-26 Thread Jan Niehusmann
block 859841 by 858398 859671 thanks On Thu, Oct 12, 2017 at 11:44:44PM +0200, Sebastian Andrzej Siewior wrote: > this is a remainder about the openssl transition [0]. We really want to > remove libssl1.0-dev from unstable for Buster. I will raise the severity > of this bug to serious in a month.

Bug#879811: psi-translations: update to version 1.3

2017-10-26 Thread Jan Niehusmann
Hi Boris, On Thu, Oct 26, 2017 at 11:59:57AM +0300, Boris Pek wrote: > Please update package src:psi-translations to version 1.3 and keep it in sync > with src:psi package. Definitely a good idea, yes! Unfortunately, I currently don't have much spare time, so it may take some time. >

Bug#875119: [psi] Future Qt4 removal from Buster

2017-09-10 Thread Jan Niehusmann
Hi Lisandro, On Sat, Sep 09, 2017 at 10:21:11PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: Yes, thanks for the reminder. In fact, it should be relatively easy: The current version of psi (not yet

Bug#856964: Option search in dnssec-trigger.conf is ignored

2017-06-16 Thread Jan Niehusmann
This seems to be caused by a new option, set_search_domains, in /etc/dnssec.conf. It defaults to 'no', but if you set it to 'yes', search domains are properly added to /etc/resolv.conf, again. (Note: Make sure to look at /etc/dnssec.conf, not /etc/dnssec-trigger/dnssec.conf, which may be present

Bug#864716: Acknowledgement (initramfs-tools: Missing fbcon modules causes blank screen during password prompt)

2017-06-13 Thread Jan Niehusmann
Additional information, as noticed by the kind people on #debian-devel: This is only an issue because I'm using a custom kernel, which has fbcon as a module. Debian kernels should not be affected, which also explains why this issue wasn't reported earlier. Jan

Bug#864716: initramfs-tools: Missing fbcon modules causes blank screen during password prompt

2017-06-13 Thread Jan Niehusmann
Package: initramfs-tools Version: 0.130 Severity: normal Dear Maintainer, after upgrading from jessie to stretch and rebooting, I got a blank screen. Figured out the system was waiting for the hard disk passphrase ("Please unlock disk " prompt). After entering the password blindly, the

Bug#864695: python-qgis-common: missing conflict with python-qgis 2.4.0-1+b1

2017-06-13 Thread Jan Niehusmann
Hi, On Tue, Jun 13, 2017 at 08:16:36AM +0200, Sebastiaan Couwenberg wrote: > Conflicts is not appropriate in this situation, Breaks/Replaces with a > version is (the file was moved in QGIS 2.6.0). Sure - I meant 'conflict' in an abstract sense, not the Conflicts header. Thanks for fixing the

Bug#864695: python-qgis-common: missing conflict with python-qgis 2.4.0-1+b1

2017-06-12 Thread Jan Niehusmann
Package: python-qgis-common Version: 2.14.11+dfsg-3 Severity: important Dear Maintainer, while upgrading from jessie to stretch, I got the following error message: dpkg: error processing archive /var/cache/apt/archives/python-qgis-common_2.14.11+dfsg-3_all.deb (--unpack): trying to overwrite

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

2017-05-28 Thread Jan Niehusmann
Hi, On Sun, May 28, 2017 at 07:54:33PM +0200, Ivo De Decker wrote: > On Sun, May 28, 2017 at 02:39:00PM +0200, Jan Niehusmann wrote: > > May I suggest only removing runit-init from the runit source package, if > > the bug can't be fixed in time for the stretch release? > >

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

2017-05-28 Thread Jan Niehusmann
May I suggest only removing runit-init from the runit source package, if the bug can't be fixed in time for the stretch release? Because runit itself doesn't cause the issue discussed here, is useful on its own, and several packages depend on it. Thanks, Jan

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

2017-05-28 Thread Jan Niehusmann
BTW, I really think this doesn't need to be RC. (Or, at least, should be stretch-ignore, because removing all the reverse-dependencies would be worse than just shipping with runit-init.) I agree it's bad to leave a user with a broken system. But in this case, the user gets an appropriate

Bug#858345: ITP: tnetstring3 -- python3 library for data serialization using typed netstrings

2017-03-21 Thread Jan Niehusmann
Package: wnpp Severity: wishlist Owner: Jan Niehusmann <j...@debian.org> * Package name: tnetstring3 Version : 0.3.1 Upstream Author : Carlo Pires <carlopi...@gmail.com> * URL : https://pypi.python.org/pypi/tnetstring3 * License : MIT Programming

Bug#855867: unblock: mongrel2/1.11.0-6

2017-02-22 Thread Jan Niehusmann
-pick upstream patch. +One can send HUP signals to mongrel2 to make it reopen the log +files. Due to a bug, after receiving two such signals, mongrel2 +stopped working. This bug is fixed by the patch. + + -- Jan Niehusmann <j...@debian.org> Wed, 22 Feb 2017 12:14:48 +0100 + mo

Bug#834088: What's up with mongrel2?

2017-02-05 Thread Jan Niehusmann
Hi Niels, On Sun, Feb 05, 2017 at 10:44:00AM +, Niels Thykier wrote: > On Sat, 27 Aug 2016 20:16:57 +0300 Dmitry Bogatov wrote: > > Jan, could you please provide more information? I did not follow. As > Are there any news on this bug? It is listed as a possible blocker for

Bug#852317: Patch tested with debian package

2017-01-25 Thread Jan Niehusmann
Hi Alessandro, the upstream patch (also included in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852317#5 ) applies to the debian package, and fixes the issue. AFAIK today is the last day to upload a fixed version without an exception granted by the release team. I'll attach the patch

Bug#852317: libcurl3: Connection timeout on https streams

2017-01-23 Thread Jan Niehusmann
Package: libcurl3 Version: 7.52.1-1 Severity: important Tags: fixed-upstream, patch Dear Maintainer, with 7.52.1-1, I got hanging connections when trying to fetch SSL URLs using the multi_socket API. It works with 7.50.1-1, and I also noticed it works when using the current upstream master

Bug#851875: atop not installable if process accounting is stopped

2017-01-19 Thread Jan Niehusmann
Package: atop Version: 2.2.6-2 Severity: minor On Thu, Jan 19, 2017 at 01:02:16PM +0100, Marc Haber wrote: > On Thu, Jan 19, 2017 at 12:35:33PM +0100, Jan Niehusmann wrote: > > First I noticed that the installation failed because process accounting > > was not running. (I used the

Bug#850881: zurl: Please B-D on "libssl1.0-dev | libssl-dev (<< 1.1)" for stretch

2017-01-11 Thread Jan Niehusmann
Hi Niels, On Tue, Jan 10, 2017 at 10:20:32PM +0100, Jan Niehusmann wrote: > Am I missing something? Is this a good way to handle the situation? > Would it be possible to speed up the propagation of zurl/1.7.1-3 to > testing so I can upload zurl/1.7.1-4? Even though I didn't get an ans

Bug#850881: zurl: Please B-D on "libssl1.0-dev | libssl-dev (<< 1.1)" for stretch

2017-01-10 Thread Jan Niehusmann
Hi Niels, On Tue, Jan 10, 2017 at 09:36:57PM +0100, Niels Thykier wrote: > Package: zurl > Version: 7.51.0-1 > Severity: grave > Tags: sid stretch > > Hi, > > Please use ssl1.0 for stretch. > > We have requested the curl also reverts to ssl1.0 (please see > #850880). Since zurl is using a curl

Bug#846176: ITP: restic -- restic backup program

2016-11-29 Thread Jan Niehusmann
Hi Félix, On Tue, Nov 29, 2016 at 12:47:21AM +0100, Félix Sipma wrote: > * Package name: restic > Version : 0.3.0 > Upstream Author : Alexander Neumann > * URL : https://restic.github.io/ Did you notice that there is already an upstream ticket

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

2016-11-20 Thread Jan Niehusmann
On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote: > So far I do not know why using libssl1.1 together with a > libssl1.0.2-using Qt wouldn't work. Well I don't know enough about the dynamic linker and about the internals of openssl to know if (indirectly) linking to both libraries

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

2016-11-20 Thread Jan Niehusmann
On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote: > It would be a grave bug in such application if it does not have a > working version, yes. Whether or not it would be a serious bug in > lubcurl3 depends on how many and how important such applications are. > (And how difficult

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

2016-11-20 Thread Jan Niehusmann
On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote: > > Still, for 1.1 the SONAME change is definitely necessary. > > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and > compiled with OpenSSL 1.0 will probably suffice in that case. Wouldn't this still be a serious bug

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

2016-11-20 Thread Jan Niehusmann
On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote: > If SONAME change is needed it is needed when linking libcurl with > libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more > applications are affected due to the need of explicit initialization.) Upstream documentation

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

2016-11-11 Thread Jan Niehusmann
Package: libcurl3 Version: 7.51.0-1 Severity: serious Justification: Policy 8.1 Dear Maintainer, the curl ABI contains structs inherited from OpenSSL, e.g. in calls like: curl_easy_setopt(easy, CURLOPT_SSL_CTX_FUNCTION, _cb); Here, sslCtxFunction_cb is a function which takes an SSL_CTX * as a

Bug#841664: qconf generates broken configure containing non-posix substitutions

2016-10-21 Thread Jan Niehusmann
Package: qconf Version: 2.1-1 Severity: important Hi Boris, with 2.1-1, you "backported remove-bashism-from-configure.patch" to fix bashisms in the configure script contained in the qconf package. While this fixes the build of qconf itself, qconf still generates configure scripts containing

Bug#840177: Set INSTALL_ROOT to fix issue

2016-10-17 Thread Jan Niehusmann
It seems like dh_auto_install used to set INSTALL_ROOT (works in jessie), but now it doesn't, so the build fails in sid. But it's easy to set INSTALL_ROOT, manually. Just add it to the call of dh_auto_install in debian/rules: --- a/debian/rules +++ b/debian/rules @@ -22,7 +22,7 @@

Bug#834088: update-service doesn't work as expected

2016-08-13 Thread Jan Niehusmann
Control: reassign -1 runit Control: retitle -1 update-service doesn't work as expected mongrel2-run, from it's postinst script, just calls: update-service --add /etc/sv/mongrel2 >From the manpage of update-service, this looks like a valid command to add mongrel2 to the system-wide service

Bug#827954: ejabberd: sqlite3 support doesn't work because erlang-sqlite3 is too old

2016-06-23 Thread Jan Niehusmann
Package: ejabberd Version: 16.03-1~bpo8+1 Severity: normal The sqlite support of ejabberd is broken with the package of erlang-sqlite3 currently available in debian: Version 1.1.4 of erlang-sqlite3 doesn't contain the function sqlite3:changes, which is used by ejabberd. This results in error

Bug#804385: jessie-pu: package mongrel2/1.9.1-6

2016-02-26 Thread Jan Niehusmann
On Sat, Feb 20, 2016 at 02:16:07PM +, Adam D. Barratt wrote: > Please go ahead. Ok, I just uploaded the package: On Fri, Feb 26, 2016 at 11:11:48AM +, Debian FTP Masters wrote: > mongrel2_1.9.1-6+deb8u1_amd64.changes uploaded successfully to localhost > along with the files: >

Bug#804385: jessie-pu: package mongrel2/1.9.1-6

2016-02-20 Thread Jan Niehusmann
On Sat, Feb 20, 2016 at 12:17:57PM +, Adam D. Barratt wrote: > On Mon, 2015-12-28 at 19:18 +, Adam D. Barratt wrote: > > On 2015-11-21 19:05, Jan Niehusmann wrote: > > > On Sat, Nov 21, 2015 at 05:40:44PM +0100, Julien Cristau wrote: > > >> We like to see a

Bug#808063: mongrel2: switch from polarssl to mbedtls

2015-12-16 Thread Jan Niehusmann
On Tue, Dec 15, 2015 at 07:38:30PM +, James Cowgill wrote: > Yes that's right, sorry I didn't explain that totally before. Port is > probably a better word in the case of this package. I can probably have > a go at doing it if you want. It looks like Justin did the porting:

Bug#808063: mongrel2: switch from polarssl to mbedtls

2015-12-15 Thread Jan Niehusmann
Hi, On Tue, Dec 15, 2015 at 04:48:06PM +, James Cowgill wrote: > Please can you switch to mbedtls instead of using polarssl, now that > mbedtls has been accepted. As far as I know, mbedtls did not only change the library name, but also the API. So one can't simply 'switch' to mbedtls, but

Bug#808063: mongrel2: switch from polarssl to mbedtls

2015-12-15 Thread Jan Niehusmann
On Tue, Dec 15, 2015 at 07:38:30PM +, James Cowgill wrote: > Yes that's right, sorry I didn't explain that totally before. Port is > probably a better word in the case of this package. I can probably have > a go at doing it if you want. That would, of course, be great! To avoid duplication

Bug#801413: fixed in polarssl 1.3.14-0.1

2015-11-30 Thread Jan Niehusmann
Hi, as polarssl is is marked for autoremoval from testing on 2015-12-09 because of bug #801413, I wonder why the upload fixing the issue is only in experimental. Is there a reason for not pushing it to unstable? I'm asking because I'm the maintainer of two reverse dependencies. Jan

Bug#804385: jessie-pu: package mongrel2/1.9.1-6

2015-11-21 Thread Jan Niehusmann
15:46:43.0 +0100 @@ -1,3 +1,10 @@ +mongrel2 (1.9.1-7) UNRELEASED; urgency=medium + + * Comment out failing test caused by an expired certificate. +(Closes: Bug#804331) + + -- Jan Niehusmann <j...@debian.org> Sat, 07 Nov 2015 15:45:05 +0100 + mongrel2 (1.9.1-6) unstable;

Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

2015-11-07 Thread Jan Niehusmann
Hi, On Sat, Nov 07, 2015 at 02:30:09PM +, James Cowgill wrote: > I know. I was wondering if it could be fixed in stable? Well, for stable I'd just disable the failing test, instead of backporting the upstream fix. Commenting out the mu_assert line containing the error message would be

Bug#804385: jessie-pu: package mongrel2/1.9.1-6

2015-11-07 Thread Jan Niehusmann
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu Mongrel2 currently FTBFS in jessie, bug #804331 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804331 contains the details. The fix is trivial, it only affects a test suite run

Bug#802276: libzmq-java: Move the native library to libzmq-jni

2015-10-21 Thread Jan Niehusmann
Hi Emmanuel, On Mon, Oct 19, 2015 at 12:15:35AM +0200, Emmanuel Bourg wrote: > libzmq-java/3.1.0-4 contains currently zmq.jar and its underlying native > library libjzmq.so. The Java Policy recommends splitting the native library > into a separate package libzmq-jni. Also ideally the .so should

Bug#802278: libzmq-java: Missing Maven artifacts

2015-10-21 Thread Jan Niehusmann
Hi Emmanuel, On Mon, Oct 19, 2015 at 12:58:47AM +0200, Emmanuel Bourg wrote: > You can add them by: > > 1. build depending on maven-repo-helper instead of javahelper > > 2. replacing "--with javahelper" by "--with maven_repo_helper" on the dh line > of debian/rules > > 3. replacing

Bug#785146: libuecc has been uploaded

2015-10-13 Thread Jan Niehusmann
Update: libuecc has been uploaded. (Not by me, but by Steffen Moeller, after asking me for permission.) It's currently in the NEW queue: https://ftp-master.debian.org/new/libuecc_5-2.html Not yet closing the bug until the package is accepted. Jan

Bug#792252: vpim: rfc2425.rb calls String#each which is not available since ruby1.9

2015-07-13 Thread Jan Niehusmann
Package: vpim Version: 0.695-1.1 Severity: normal Dear Maintainer, while using vpim/icalendar I got an error message that an undefined method 'each' was called on a String. Seems like this method was removed in ruby1.9. The fix is trivial: Use each_line, instead. I found two places where this

Bug#785151: fritzing: A new upstream version is available

2015-05-12 Thread Jan Niehusmann
Package: fritzing Version: 0.9.0b+dfsg-1 Severity: wishlist Dear Maintainer, at http://fritzing.org/download/, version 0.9.2b is available for download. Compared to 0.9.0b, it contains some new part definitions, and a few bug fixes. -- To UNSUBSCRIBE, email to

Bug#785148: fritzing: watch file doesn't work

2015-05-12 Thread Jan Niehusmann
Package: fritzing Version: 0.9.0b+dfsg-1 Severity: minor Dear Maintainer, the watch file didn't notice the availability of fritzing 0.9.2b. In fact, uscan doesn't even find the currently packaged version: -- Found the following matching hrefs:

Bug#785146: ITP: libuecc -- small general-purpose ECC library

2015-05-12 Thread Jan Niehusmann
Package: wnpp Severity: wishlist libuecc is a general-purpose ECC library which uses a curve similar to djb's Curve25519 which is part of the NaCl library. Because of it's small footprint, this library is used in the wireless router software used by several free radio networks (Freifunk). For

Bug#760923: halt no longer powers off the machine

2015-05-08 Thread Jan Niehusmann
Hi, just my opinion, of course, but please let me add: - changing finger memory is difficult, so I keep entering 'halt' instead of 'poweroff' occasionally - if one doesn't notice the error, this will waste electricity - if it happens on a notebook just before putting it into a bag, one

Bug#774985: ITP: jzmq -- ZeroMQ Java bindings

2015-01-09 Thread Jan Niehusmann
Package: wnpp Serverity: wishlist This package will provide JNI-based Java bindings for 0MQ. URL: https://github.com/zeromq/jzmq License: LGPL-3+ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#761256: psi has forgotten all configured accounts

2014-09-14 Thread Jan Niehusmann
Hi Benjamin, On Fri, Sep 12, 2014 at 09:27:55AM +0200, Benjamin Peter wrote: I have no idea what lead to the situation, I made an update and now psi prompts to enter my account data although I had multiple already set up for years. I seems to have lost all account data. Psi changed the config

Bug#759952: Build failure is caused by parallel build

2014-09-14 Thread Jan Niehusmann
Hi, it seems like #759952 is caused by the parallel build. The output shows the following sequence of events: 1) the debian/rules target 'build-prep' executes cd hun-eng; make hun-eng.tei 2) make hun-eng.tei runs: cp hun-eng.tei.header hun-eng.tei ./szotar-dbf2tei.pl hun-eng.tei 3)

Bug#736066: Allow encfs into jessie?

2014-09-12 Thread Jan Niehusmann
Hi Holger, On Thu, Sep 11, 2014 at 06:42:32PM +0200, Holger Levsen wrote: I (probably too briefly) skimmed though the bug report, but couldn't find a usecase where an encrypted filestem container with broken crypto could be useful. Could you elaborate, please? As far as I understand the

Bug#736066: Allow encfs into jessie?

2014-09-11 Thread Jan Niehusmann
Hi, due to bug #736066, encfs was removed from jessie. I'd think it would be better to allow encfs into jessie for the following reasons: The bug report is about security issues, but these are not security issues of the software (as in: you can somehow hack into the computer wich is running the

Bug#755089: bacula: purging one director package removes bacula-dir.conf of other director package

2014-07-17 Thread Jan Niehusmann
Source: bacula Severity: important In the following sequence of events, the file /etc/bacula/bacula-dir.conf of the currently used director got removed: install bacula-director-sqlite3 replace bacula-director-sqlite3 with bacula-director-pgsql happily use bacula for several years :-) prune

Bug#754734: [src:psi] Incomplete debian/copyright

2014-07-14 Thread Jan Niehusmann
Hi Bastien, On Sun, Jul 13, 2014 at 08:24:56PM +, bastien ROUCARIES wrote: This file is dual licensed and you do not add copyright information on debian/copyright. Absolutely true. In fact, the whole copyright file needs some love. (DEP 5 formatting, checking for more files with differing

Bug#754156: mongrel2: Doesn't build on big endian machines

2014-07-08 Thread Jan Niehusmann
Package: mongrel2 Version: 1.9.1-2 Severity: normal Tags: pending Building mongrel2 fails on big endian machines with a failing test case: ERROR in test tests/radixmap_tests: RUNNING: ./tests/radixmap_tests FAILED: Failed to properly sort the RadixMap. This is because src/adt/radixmap.c

Bug#754161: mongrel2: build fails on kfreebsd

2014-07-08 Thread Jan Niehusmann
Package: mongrel2 Version: 1.9.1-3 Severity: normal Tags: pending On kfreebsd, build fails with the following message: src/bsd_specific.c:82:5: error: conflicting types for 'bsd_sendfile' int bsd_sendfile(int out_fd, int in_fd, off_t *offset, size_t count) { ^ In file included from

Bug#754194: mongrel2: FTBFS on armhf

2014-07-08 Thread Jan Niehusmann
Package: mongrel2 Version: 1.9.1-4 Severity: normal On armhf, the test suite immediately throws a segfault. Looking at the stack with gdb, I don't see an obvious reason for the segfault. Maybe the issue is caused by libtask being incompatible with armhf? (Mongrel2 contains a coroutine lib in

Bug#754194: Patch which seems to help

2014-07-08 Thread Jan Niehusmann
The following patch seems to help. At least the test suite passes on both armel and armhf. But I honestly don't know why... --- mongrel2-1.9.1.orig/src/task/asm.S +++ mongrel2-1.9.1/src/task/asm.S @@ -34,7 +34,7 @@ #endif #endif -#if defined(__linux__) defined(__arm__) +#if

Bug#751489: Gandi discount available, again

2014-06-17 Thread Jan Niehusmann
retitle 751489 developers-reference: Updates on Gandi discount for debian developers thanks It seems like the Gandi support team was not the right contact, and in fact, the discount is still available. Section 4.13.2 still needs an update, as the email address given there is no longer valid.

Bug#751489: developers-reference: gandi discount (section 4.13.2) no longer available

2014-06-13 Thread Jan Niehusmann
Package: developers-reference Version: 3.4.11 Severity: normal Hi, I just got the following answer from gandi support regarding the discount for debian developers: I am sorry, but this offer dates back from 2008, and is no longer available. So section 4.13.2 of the developers reference can be

Bug#744027: Please remove StartCom Certification Authority root certificate

2014-04-09 Thread Jan Niehusmann
On Wed, Apr 09, 2014 at 03:48:56PM +0200, Thijs Kinkhorst wrote: Whatever you and I think of this pricing structure, people free to chose any provider of certificates that matches their pricing interest and that people are knowingly or should be knowlingly buying a product that has a certain

Bug#740098: librxtx-java: setting speed to 38400 doesn't work on some (many?) USB-serial-adapters

2014-02-25 Thread Jan Niehusmann
Package: librxtx-java Version: 2.2pre2-11 Severity: normal Hi, I got an issue with 2.2pre2-11 not working, while 2.1.7r2-4 does. (And it's been this way since I upgraded the host from lenny to squeeze. Didn't have time to investigate back then, but now, while upgrading to wheezy, I had a look

Bug#740098: Patch to fix setting USB-serial adapters to 38400 bps

2014-02-25 Thread Jan Niehusmann
tag 740098 +patch thanks The following patch should fix the reported issue. On serial ports not supporting the TIOCGSERIAL/TIOCSSERIAL mechanism, this still means that the custom baud rates do not work, but at least 38400 works, again. Perhaps an even better fix would be switching to the newer

Bug#727055: ITP: pushpin -- HTTP reverse proxy server for streaming and long-polling services

2013-10-21 Thread Jan Niehusmann
Package: wnpp Serverity: wishlist Pushpin is an HTTP reverse proxy server that makes it easy to implement streaming and long-polling services. It communicates with backend web applications using regular, short-lived HTTP requests (GRIP protocol). This allows the backend applications to be written

Bug#715050: ITP: zurl -- HTTP client worker with ZeroMQ interface

2013-07-05 Thread Jan Niehusmann
Package: wnpp Serverity: wishlist Zurl is HTTP client worker with ZeroMQ interface, written in Qt/C++. Features: - Request HTTP and HTTPS URLs - Completely event-driven, using JDNS and QNetworkAccessManager - Handle thousands of simultaneous outbound connections - Two access methods:

Bug#590629: ITP: mongrel2 -- a small fast web server agnostic to applications and languages

2013-06-05 Thread Jan Niehusmann
Owner: Jan Niehusmann j...@debian.org Hi Miguel, On Thu, Mar 21, 2013 at 09:25:56AM -0300, Miguel Landaeta wrote: Hi Justin, [...] Please go ahead and take ownership of this ITP. As I work together with Justin on a mongrel2 package, and I'll probably be the one uploading it, I just set myself

Bug#710561: ITP: python-tnetstring -- python library for data serialization using typed netstrings

2013-05-31 Thread Jan Niehusmann
Package: wnpp Serverity: wishlist Tnetstring is a serialization format a lot like JSON but it uses a new syntax called typed netstrings that was proposed for use in the Mongrel2 webserver. It's designed to be simpler and easier to implement than JSON, with a happy consequence of also being faster

Bug#709407: psi: Psi constantly aborting

2013-05-23 Thread Jan Niehusmann
Hi Martín! I suspect this is an incompatibility between psi (or some lib psi uses) and glibc 2.17, as that's the only library version which is different in testing. Versions of packages psi depends on: ii libc62.17-3 [...] Unfortunately, I don't have a system with that

Bug#658318: usbmount: Mounts flash drives twice

2013-03-13 Thread Jan Niehusmann
Hi, it seems like this behaviour is caused by a leftover symlink at /etc/udev/rules.d/z60_usbmount.rules: $ ls -al /etc/udev/rules.d/z60_usbmount.rules lrwxrwxrwx 1 root root 17 Feb 4 2010 /etc/udev/rules.d/z60_usbmount.rules - ../usbmount.rules After removing this symlink, the double-mounts

Bug#701700: psi: I'd like to have a disable-option for each soundevent.

2013-02-26 Thread Jan Niehusmann
Hi Martin, On Tue, Feb 26, 2013 at 01:28:32PM +0100, Martin Teufel wrote: Since upstream is at version 0.15 and my patch isn't really compatible with that, I think it is a good idea to patch the debian version of 0.14. I'm sorry, but I think there's no way to get such a change into wheeze at

Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played

2013-02-11 Thread Jan Niehusmann
Hi Martin, On Sat, Feb 02, 2013 at 02:22:07PM +0100, Martin Teufel wrote: After some sound-notifications were played, the sounddevice somehow breaks. I.e. no more sounds are played (of course psi tries to) and I can't output any sound/music at all (e.g. with mplayer or something). Psi just

Bug#699619: psi: breaks audio after some sounds (maybe about 30 or 50) were played

2013-02-11 Thread Jan Niehusmann
On Mon, Feb 11, 2013 at 05:23:01PM +0100, Martin Teufel wrote: My problem with the situation: What _if_ aplay plays correctly all the time, but in psi it breaks the sound after a while? (At the moment, for me, it seems to be the case.) Maybe some kind of concurrency problem? Psi may call aplay

Bug#686329: atop crashes if /var/run/ is nearly full

2012-08-31 Thread Jan Niehusmann
Package: atop Version: 1.23-1+squeeze1 Severity: minor If the partition where the process accounting file, /var/run/atop/atop.acct is located, is close to full (98%, depending on kernel settings), the kernel stops writing process accounting entries. (Log message in kern.log: Process accounting

Bug#686329: atop crashes if /var/run/ is nearly full

2012-08-31 Thread Jan Niehusmann
Hi Marc, On Fri, Aug 31, 2012 at 02:39:22PM +0200, Marc Haber wrote: If you can reproduce this, please retry with a backport of atop 1.26. There have been changes in this area of atop. I can give you a backported package if you want to. It's easy to reproduce. With a command like echo 99 99

Bug#667841: RM: qca -- ROM; replaced by qca2, no longer useful

2012-04-06 Thread Jan Niehusmann
Package: ftp.debian.org Severity: normal For qt4, qca has been replaced by qca2. As qt3 is about to be removed, qca should go as well. As noted in #604339 by Felix Geyer, even now, qca isn't usable any longer, as it's only backand, qca-tls, was already removed. So there is no use keeping qca in

Bug#666161: psi: FTBFS if built twice in a row

2012-03-29 Thread Jan Niehusmann
Hi Stuart, On Thu, Mar 29, 2012 at 12:49:53PM +0100, Stuart Prescott wrote: dpkg-source: error: cannot represent change to psi-0.14/iris/lib/libirisnet.a: binary file contents changed dpkg-source: error: cannot represent change to psi-0.14/iris/lib/libiris.a: binary file contents changed

Bug#659448: psi: Can't add new color for nicks

2012-02-11 Thread Jan Niehusmann
Hello Kakadu, On Sat, Feb 11, 2012 at 01:11:30PM +0400, kakadu wrote: I can't add new colors for nicks in cenference rooms. Video with workaroud added. http://www.youtube.com/watch?v=OjIaEW4bYUU I can't add new nick color --- program doesn't save it. I guess it's just that the color picker

  1   2   3   >