Bug#1065183: marked as pending in python-fsquota
Control: tag -1 pending Hello, Bug #1065183 in python-fsquota reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-fsquota/-/commit/3dc5d640ab05fd347eb654cb9fba874a2eb05a9b add libtirpc-dev to Build-Depends (Closes: #1065183) (this message was generated automatically) -- Greetings https://bugs.debian.org/1065183
Bug#1013644: erlang-p1-tls: FTBFS: test failed
Hi Lucas, unfortunately I am unable to reproduce this error. How do you suggest to continue here? Best wishes -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- OpenPGP_signature Description: OpenPGP digital signature
Bug#1002346: python-transitions: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13
forwarded 1002346 https://github.com/pytransitions/transitions/issues/559 tags 1001479 + confirmed upstream pending fixed-upstream tags 1002346 + confirmed upstream pending fixed-upstream thanks This is a duplicate of #1001479, which I have forwarded upstream and which was fixed there already, I'm just waiting for a new release. Best wishes Philipp
Bug#1001425: marked as pending in python-odoorpc
Control: tag -1 pending Hello, Bug #1001425 in python-odoorpc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-odoorpc/-/commit/5b3388ca726c6b2e9db1518a68f00e13125f8313 add patch to become compatible with Python 3.10 (Closes: #1001425) (this message was generated automatically) -- Greetings https://bugs.debian.org/1001425
Bug#1001425: python-odoorpc: (autopkgtest) needs update for python3.10: module 'collections' has no attribute 'MutableMapping'
Hi, there is a patch available at https://github.com/OCA/odoorpc/pull/67/commits/7335e594b02ce7645beefa67d541d5b34df0daaf, I will give that a try. Regards -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- OpenPGP_signature Description: OpenPGP digital signature
Bug#998108: firefox freezes shortly after start
Hi, I am affected by the same problem. After downgrading to firefox=93.0-1 from snapshot.debian.org the problem is gone. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- OpenPGP_signature Description: OpenPGP digital signature
Bug#972500: hamster-time-tracker does not launch on Buster using the backported package
Hi, Am 19.10.20 um 17:39 schrieb Raphael Hertzog: > Philipp, you uploaded the backport. Can you have a look at this report? sure, I will do that tomorrow. Since hamster was not part of buster I did not test an old hamster profile with the new hamster-time-tracker. @Ulrike: could you please give it a try with your existing config+data temporarily renamed? Best wishes Philipp
Bug#945061: uninstallable due to Thunderbird security update to version 68
Package: xul-ext-sogo-connector Severity: grave Hi, due to the security update introducing Thunderbird 68, xul-ext-sogo-connector has become uninstallable and thus unusable in all suites from oldstable to unstable. Could you please package sogo-connector 68? (old-)stable updates would also be greatly appreciated. I'd be happy to help test updated packages. Best wishes Philipp
Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev
Hi, Am 26.02.19 um 08:54 schrieb Andreas Tille: >>> to Git. Is there any reason not to upload this and simply fix #883619. >>> Looks like a pretty low hanging fruit to fix an RC bug and save the >>> package for Buster that I can not imagine nobody else would have >>> harvested it. >> >> It's only downstream dependency is colmap. If colmap is happy with the new >> version then it sounds like a good idea to upload it, especially if it fixes >> an RC bug. > > I mean: There is no *effective* change since the Build-Depends we set is > fullfilled anyway by the existing packages. Its just that it is > explicitly declared in the package metadata. IMO that's a valid fix for buster, but does not fix the underlying issue for sid / buster+1. The next time a newer version of eigen3 is uploaded, you'll have the same "problem" all over again: adjust the build dep and upload to get a corresponding rebuild. Updating eigen3 renders ceres and similar packages unusable until rebuilt, please read through the discussion in #868355 to understand what I mean. The eigen3 maintainer and I are happy to simply rebuild affected packages after every eigen3 update, but Emilio considers it an upstream bug. Unfortunately I could not find anybody able to shed more light on the eigen3 topic. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#917589: erlang-p1-pkix: FTBFS (failing tests)
Am 29.12.18 um 11:20 schrieb Philipp Huebner: >> I tried to build this package in buster but it failed: > I uploaded a new upstream version which builds fine in my pbuilder > chroot as well as on the buildds, yet it fails again on > reproducible-builds. I wonder what's different. Okay, I think I found the culprit: ca-certificates is missing from Build-Depends. Preparing a fixed package now. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#917589: erlang-p1-pkix: FTBFS (failing tests)
Hi, > Dear maintainer: > > I tried to build this package in buster but it failed: I uploaded a new upstream version which builds fine in my pbuilder chroot as well as on the buildds, yet it fails again on reproducible-builds. I wonder what's different. I'm tempted to lower the severity as it obviously does not FTBFS on the buildds. Best wishes, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#903630: closing 903630
close 903630 thanks ejabberd 18.06 is now available in Testing.
Bug#903028: closing 903028
close 903028 0.2018.07.13~dfsg0-1 thanks The problem has been solved upstream and a fixed versions is now in unstable.
Bug#903630: erlang-p1-xmpp 1.2.2 breaks ejabberd 18.04
Am 12.07.2018 um 10:25 schrieb pitchum: > Maybe this issue will be solved when ejabberd 18.06 reaches testing. Certainly! ejabberd 18.06 should have entered testing at the same time as all the erlang-p1-* packages, I'll try to find out what is preventing that. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#903028: ejabberd-contrib: FTBFS with ejabberd >= 18.06
Source: ejabberd-contrib Severity: grave Tags: upstream ejabberd 18.06 is the first release to ship without jlib.hrl and ejabberd.hrl, causing ejabberd-contrib to FTBFS because several modules have not been updated yet. Upstream report: https://github.com/processone/ejabberd-contrib/issues/251
Bug#895371: ejabberd: conffile edited using ucf
Am 16.04.2018 um 10:17 schrieb Jonas Smedegaard:
> Excerpts from Philipp Huebner's message of april 16, 2018 9:38 am:
>> On Tue, 10 Apr 2018 19:39:14 +0200 Jonas Smedegaard wrote:
>>> The file /etc/default/ejabberd is registered as a conffile, but is
>>> also manipulated using ucf in postinst script. That is illegal,
>>> according to Policy § 10.7.3
>>
>> thanks for pointing this out!
>>
>> However, this is rather unfortunate, the current setup has been well
>> tested and in use for ages.
>>
>> Do you have an idea on how to achieve this in a policy-conform way?
>>
>> Not touching ejabberd.yml would mean to remove the debconf templates
>> for configuring ejabberd, not declaring ejabberd.yml a conffile would
>> mean putting in some extra effort for handling changes. Are
>> non-conffiles even allowed in /etc ?
>
> Debian Policy distinguishes between "configuration file" and "conffile"
> and describes, particular at §10.7.3, how to handle either. I believe
> the first step is to *not* ship the configuration file below /etc if it
> should not be a conffile ("man dh_installdeb" documents how any file
> below /etc shipped with a package is registered as a conffile).
>
> "man ucf" contains some documentation on transitioning from conffile to
> non-conffile. I believe that involves collecting md5sums of most
> possible previous pristine states (i.e. configfile as shipped unedited
> with the package) as possible.
>
>
> Hope that helps,
It does, and only now I realized you're talking about
/etc/default/ejabberd and not ejabberd.yml, so the problem is only a
fraction as tough as I thought, because we're already handling
ejabberd.yml the correct way and can simply duplicate that.
Should be fixed soon(ish)!
Thx again,
--
.''`. Philipp Huebner
: :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F
`. `'`
`-
signature.asc
Description: OpenPGP digital signature
Bug#895371: ejabberd: conffile edited using ucf
Hi Jonas, On Tue, 10 Apr 2018 19:39:14 +0200 Jonas Smedegaard wrote: > The file /etc/default/ejabberd is registered as a conffile, but is also > manipulated using ucf in postinst script. That is illegal, according to > Policy § 10.7.3 thanks for pointing this out! However, this is rather unfortunate, the current setup has been well tested and in use for ages. Do you have an idea on how to achieve this in a policy-conform way? Not touching ejabberd.yml would mean to remove the debconf templates for configuring ejabberd, not declaring ejabberd.yml a conffile would mean putting in some extra effort for handling changes. Are non-conffiles even allowed in /etc ? Best wishes, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#885273: Fwd: Bug#885273: diffuse: Depends on unmaintained pygtk
> Thanks for giving me a heads up. I plan on tackling a bunch of issues > by re-writing most of Diffuse to use Python 3, the GObject bindings, and > handle word wrap. That's great news! > Unfortunately this is a rather big task so it will > take some time to complete. Hopefully, I will have something that is an > improvement over the Python 2 implementation of Diffuse by the end of > 2018. Given Debian's release cadence so far, I expect the next Debian > release to be around the end of 2019. Is that close to when you expect > Debian's next release to happen? Yes, maybe a few months earlier. BTW, I believe the Thai translations in https://bugs.debian.org/793352 are complete and waiting to be included, but I didn't realize that until a few days ago. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#884344: ejabberd: After updating to latest erlang packages, ejabberd refuses to start
Hi, since the security patch in Erlang should not have any impact for ejabberd and because I don't have this problem on my Stretch ejabberd servers I doubt it is a generic issue and thus I will lower the severity. Please make sure that epmd and all other erlang processes are stopped before trying to start ejabberd again. If necessary, kill them manually. Please also check whether AppArmor is enabled (dmesg | grep -i apparmor). Have you tried rebooting the server yet? Without access to your ejabberd logs + dmesg I cannot really help you. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#875664: piuparts.debian.org: Syntax error in post_purge_exceptions
Hi, all of the packages I looked at on https://piuparts.debian.org/sid/unclassified_failures.html currently fail because of this. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#875664: piuparts.debian.org: Syntax error in post_purge_exceptions
Package: piuparts.debian.org Severity: serious Justification: 2 Hi, I don't know much about piuparts, but this does not look like a bug in my package but in piuparts itself: https://piuparts.debian.org/sid/fail/ejabberd_17.08-1.log 0m35.6s DEBUG: Command ok: ['chroot', '/srv/piuparts.debian.org/tmp/tmpV2p584', 'dpkg', '--purge', 'ejabberd'] 0m35.6s INFO: Running scripts post_purge 0m35.6s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpV2p584', 'tmp/scripts/post_purge_exceptions'] 0m35.6s DUMP: tmp/scripts/post_purge_exceptions: 38: tmp/scripts/post_purge_exceptions: Syntax error: ")" unexpected (expecting ";;") 0m35.6s ERROR: Command failed (status=2): ['chroot', '/srv/piuparts.debian.org/tmp/tmpV2p584', 'tmp/scripts/post_purge_exceptions'] tmp/scripts/post_purge_exceptions: 38: tmp/scripts/post_purge_exceptions: Syntax error: ")" unexpected (expecting ";;") I have checked all maintainer scripts of the ejabberd package with shellcheck and they appear to be clean. This is blocking the transition to testing, hence the severity. Regards, Philipp
Bug#870041: ceres-solver FTBFS on mips*: bundle_adjustment_test (OTHER_FAULT)
Hi, for the time being, ceres is not supported on mips* by upstream. I have thus filed #873477 and will reduce the severity here. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#868787: erlang-p1-cache-tab: FTBFS on mips, mipsel and powerpc: undefined symbol: __sync_add_and_fetch_8'
Hi, > erlang-p1-cache-tab FTBFS on mips, mipsel and powerpc with this error > while running the testsuite: >> Failed to load NIF /<>/priv/lib/ets_cache: Failed to load NIF >> library: '/<>/priv/lib/ets_cache.so: undefined symbol: >> __sync_add_and_fetch_8' (load_failed) > > This happens because these architectures do not implement 64-bit atomics > natively. The fix is to use libatomic (part of GCC) which provides > helper routines for these missing atomics, implemented using locks. > > The attached patch does this by: > - Linking against libatomic > - Switching from __sync_add_and_fetch to __atomic_add_fetch > > One side effect of this is that libatomic is pulled in on every > architecture. If you don't like this, you can use -Wl,--as-needed. awesome, will test this ASAP, thx! Best wishes, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#867723: ejabberd: `dpkg-reconfigure ejabberd` fails with `Can't register admin user`
Am 08.07.2017 um 23:33 schrieb Soren Stoutner: > Package: ejabberd > Version: 17.04-1~exp2 I just tried this version, and it still works for me! > root@mail:/home/soren# dpkg-reconfigure ejabberd > > The ejabberd database has been backed up to > /var/backups/ejabberd-2017-07-08T14:08:25.vzaIOQ/ejabberd-database. > > Replacing config file /etc/ejabberd/ejabberd.yml with new version > Waiting for ejabberd to register admin user > Can't register admin user "so...@ejabberd.stoutner.com". This message also appears if there's a conflict because the account already exists. Please try manually with ejabberdctl register "$USER" "$HOST" "$PASSWD" and check with ejabberdctl registered_users "$HOST" Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#867723: ejabberd: `dpkg-reconfigure ejabberd` fails with `Can't register admin user`
Hi, please note that this problem does not render the package unusable, you can still create your own configuration and get a working ejabberd, all that's broken here is the "automatic" base setup using dpkg-reconfigure. > Can't register admin user "so...@ejabberd.stoutner.com". Does ejabberd.stoutner.com correctly resolve to the host you're installing ejabberd on? > A 1.5 MB `erl_crash.dump` file is created in `/var/log/ejabberd`. I > can upload the file to a webserver and link to it if it is valuable > for troubleshooting. In order to really help you I would need the following files: * /etc/ejabberd/* * /etc/default/ejabberd * /var/log/ejabberd/* * /etc/hostname * /etc/hosts Best wishes, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#851066: flashplugin-nonfree: Mismatch between detected and available versions (Download file not available at people.debian.org)
Hi, > This patch adds a new option to update-flashplugin-nonfree: > > > --using > Specifies the name of a local tar file instead of attempting to > discover and download the latest version. This file is presumed to be a tar > file downloaded by hand from Adobe.com, containing the flash plugin > appropriate for your machine arch. No checks are performed to ensure the > tar file is authentic; you should download such plugins *only* from > Adobe.com. > I put that patch in a package, seems to be working okay. If anybody else would like to grab it: https://apt.debalance.de/pool/main/f/flashplugin-nonfree/ Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#863652: system-config-lvm: crash on stretch, python gtk bug?
severity 863652 normal thanks Am 29.05.2017 um 21:25 schrieb gregory bahde: > Package: system-config-lvm > Version: 1.1.18-3 > Severity: critical > Justification: causes serious data loss > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > > Dear sir, just discovered that sysmtem-config-lvm was crashing on my system: > It didn't occur during an operation as it crashes pretty quickly It doesn't crash for me, and you shouldn't have any data loss while only viewing your system, thus severity "critical" is way too high. If you think you do have data loss because of this, please explain. > Ready to help and provide more info. Great! Please describe which desktop environment you are using and how exactly you launched system-config-lvm. Your "as root" statement scares me a little: surely you didn't log into X as root? Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#828404: libpam-mount: FTBFS with openssl 1.1.0
Hi, according to the upstream changelog, this is fixed in the latest release (2.16). Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#839351: erlang-p1-sqlite3: FTBFS: /usr/share/dh-rebar/make/dh-rebar.Makefile:125: recipe for target 'rebar_compile' failed
This problem is caused by a regression in rebar, see #840431 for details. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#837236: elixir-lang: FTBFS: Uncaught error in rebar_core: {'EXIT',
Hi, this is most likely just a missing build-dependency on erlang-crypto. I've had the same problem with many of my erlang packages. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#836888: erlang-redis-client: FTBFS: Uncaught error in rebar_core
Hi, somewhere along the chain of build-depends a dependency on erlang-crypto must have been removed. Listing it explicitly fixes this. I wouldn't be surprised if more Erlang packages have a bug like this now. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#835411: Packages FTBFS with new eigen3
Hi, On Wed, 24 Aug 2016 18:09:42 +0200 Anton Gladky wrote: > it looks like the eigen-upstream has a patch already, > but AFAIK it does not solve all problems. > > I discussed it with Philipp already and I will apply the > patch as far as it will be ready. the remaining issues in ceres-solver have been fixed by it's upstream, so all I would require here is this patch to be applied: https://bitbucket.org/eigen/eigen/commits/a89a95507d61/ Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#835037: ceres-solver: FTBFS with eigen3 >> 3.3~beta1
Source: ceres-solver Version: 1.11.0~dfsg0-5 Severity: serious Tags: upstream Justification: Policy 2.1 As found out through reproducible builds, ceres-solver FTBFS since eigen3 3.3~beta2 was uploaded: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log Building with eigen3 3.3~beta1 works without problems.
Bug#811987: fixed in ceres-solver 1.11.0~dfsg0-4
Hi, Am 12.08.2016 um 19:55 schrieb Santiago Vila: > Still FTBFS: > > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.11.0~dfsg0-5.rbuild.log this appears to be a different bug due to a new eigen3 release and not related to the bug you reopened. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#815640: erlang-p1-stun: Depends on erlang-p1-fast-tls which is gone
Hi, Am 23.02.2016 um 09:55 schrieb Andreas Beckmann: > during a test with piuparts I noticed your package is no longer > installable in experimental: > > it depends on erlang-p1-fast-tls which was recently removed since it is > a duplicate of erlang-p1-tls this is correct and will be fixed with the next upload, it's already corrected in git. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#803914: fixed in ejabberd-contrib 0.2015.10.26~dfsg0-1
Am 05.11.2015 um 04:47 schrieb Andreas Beckmann: > This fixes only one half of the problem. ejabberd still needs to add > Breaks+Replaces against ejabberd-mod-http-upload. I filed #804008, so ejabberd-mod-http-upload will be gone from the archive soon. Why would I need to add Breaks+Replaces then? As Ralf wrote: "An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality." So why should I add Breaks+Replaces towards a soon non-existent package? Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#803947: enigmail: completely broken after upgrade of gnupg2 to 2.1.9
This issue seems to be similar to the current RC bugs in gnupg2: #795639 and #796931 Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#803914: ejabberd-mod-http-upload and ejabberd: error when trying to install together
Hi On 03.11.2015 08:08, Ralf Treinen wrote: > dpkg: error processing archive > /var/cache/apt/archives/ejabberd-mod-http-upload_0.2015.10.02~dfsg0-1_amd64.deb > (--unpack): > trying to overwrite > '/usr/lib/x86_64-linux-gnu/ejabberd/ebin/mod_http_upload.beam', which is also > in package ejabberd 15.10-1 > Processing triggers for libc-bin (2.19-22) ... > Processing triggers for man-db (2.7.4-1) ... > Errors were encountered while processing: > > /var/cache/apt/archives/ejabberd-mod-http-upload_0.2015.10.02~dfsg0-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks for catching this! mod_http_upload has been included upstream with the 15.10 release, I'll prepare an updated ejabberd-contrib package and have ejabberd-mod-http-upload removed from the archive. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#803947: enigmail: completely broken after upgrade of gnupg2 to 2.1.9
Package: enigmail Version: 2:1.8.2-4 Severity: grave Justification: renders package unusable Hi, after upgrade of gnupg2 to 2.1.9 enigmail becomes pretty much useless, at least when used under KDE / Plasma 5. Encrypting/Decrypting doesn't work anymore and key-management is seriously impacted as there's no longer any popup window asking for the passphrase of the private key. Downgrading to gnupg2=2.0.28-3 gnupg-agent=2.0.28-3 gpgsm=2.0.28-3 scdaemon=2.0.28-3 solves all problems. extensions.enigmail.useGpgAgent is set to false, but this setting seems to be ignored with newer gnupg2 versions. This behaviour was observed on several independent computers all running KDE / Plasma 5. Regards, Philipp -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (250, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages enigmail depends on: ii gnupg1.4.19-6 ii gnupg2 2.0.28-3 ii icedove 38.3.0-2 ii libc62.19-22 Versions of packages enigmail recommends: ii gnupg-agent 2.0.28-3 ii gnupg2 2.0.28-3 ii pinentry-gnome3 [pinentry-x11] 0.9.6-4 ii pinentry-qt [pinentry-x11] 0.9.6-4 enigmail suggests no packages. -- no debconf information
Bug#801415: ejabberd: maintainer is not maintainer
Hi On 12.10.2015 14:54, Konstantin Khomoutov wrote: > On Fri, 09 Oct 2015 22:33:59 +0200 Dominik George > wrote: >> Please update the maintainer field or orphan the package. > > While I'm dissatisfied, to put it mildly, with what the submitter > wrote in this bug report regarding me being «unable to respond to any > requests», the crux of their report -- that I'm not really packaging > ejabberd for some time -- is true, and I'm of course fine with > officially resigning if it's deemed the right thing to do with those > doing actual packaging. > > Hence I'd like to hear opinions from Philipp and Rhonda about what > should I do next (if I should). Personally I don't mind in this case who is listed as maintainer and who is listed as uploader, anybody who looks into the changelog or the PTS can see at once who the most active uploader recently is and direct questions accordingly. What annoys me more is that this bug will block the migration to testing soon and hence delay the availabilty of ejabberd 15.09 in Jessie Backports. Back in March 2014 I actually e-mailed Konstantin with a request similar to this bug report: [...] >> If you're too busy, that's okay, but if this isn't going to change >> in the near future it would be very nice of you to orphan the >> package so other's can take over. > > Before I comment on this please understand that I'm not about > offending you. I'm not the native speaker so what I intend to write > might not sound quite polite but I don't really want to insult you! > > The problem with your statement is that while I understand it's > really bad for the community that I'm abstraining from doing my > maintainership work (and I do feel guilty for this, honest!), so far > other people did little but prodding me about this. Prodding *is* > good but talk is cheap while finding time to do quality packaging > work is hard. Hence currently I'm quite confident that merely > orphaning the package will do nothing to it because the only active > community member -- my uploader Rhonda -- has no time either to do > packaging work for ejabberd. > > Another contributing factor for me not resigning is that before I > even embarked on maintaining ejabberd in Debian I made friends with > three of ejabberd's core developers (one of them, its initial author, > resigned since then) and with jabber.ru staff (jabber.ru is arguably > the largest public XMPP server running ejabberd), and with Erlang > maintainer (with him I even periodically meet face-to-face) [*]. > This places me in a somewhat unique position which many times proved > its usefulness: it allows me to solve various problems quickly > because I'm typically able to ask the relevant persons for help > directly rather than spending time in bug trackers etc. I mean, this > makes me useful exactly for maintaining ejabberd and tkabber -- my > two source packages in Debian. The fact I'm Erlang-literate also > helped several times. > >> Please get back to me about this. > > Sure. The bottom line of my thoughts is that if you feel like > really do the packaging work and not merely hand-waving (like did > most who contacted me about the stagnation of my work) I'll hand it > over to you and will try to help you solve problems should they > arise. > > Otherwise let's see if I will find time to get things done myself as > I did not yet abandon this hope. ;-) > > [*] That's because I helped develop the Tkabber XMPP client which has > been concieved by the same gang of folks back then. I then actually did step in and began to help ;) Anyway, Konstantin's reasoning appeared and still appears very sound to me and he still checks in at the Packaging MUC from time to time and is still reachable, so I am fine with him staying listed as the maintainer. He has done a great job maintaining ejabberd for quite some time. Just as well I wouldn't mind switching places (Uploader vs. Maintainer) with Konstantin. The idea of orphaning the package however is pure nonsense, as it is currently well-maintained. Another option would be to create some kind of team address and put that in the maintainer field. I'd like to hear Rhonda's opinion on this as well. On 12.10.2015 15:03, Dominik George wrote: > Am Montag, 12. Oktober 2015, 15:54:45 schrieb Konstantin Khomoutov: >> Another room of interest is pkg-ejabb...@deb.at which is dedicated >> to packaging ejabberd for Debian. Maybe this quote is incomplete, but I wonder why you didn't point him to ejabb...@chat.deb.at instead, that being Rhonda's channel for the official ejabberd packaging for Debian. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
On 26.07.2015 10:03, Philipp Huebner wrote:
> It looks like a tiny patch to doc/doxygen/CMakeLists.txt could fix this.
And it does indeed.
Regards,
--
.''`. Philipp Huebner
: :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F
`. `'`
`-
Index: deal.ii-8.1.0/doc/doxygen/CMakeLists.txt
===
--- deal.ii-8.1.0.orig/doc/doxygen/CMakeLists.txt
+++ deal.ii-8.1.0/doc/doxygen/CMakeLists.txt
@@ -144,7 +144,7 @@ ADD_CUSTOM_TARGET(doxygen ALL
ADD_DEPENDENCIES(documentation doxygen)
INSTALL(FILES
- ${CMAKE_CURRENT_BINARY_DIR}/deal.tag
+ ${CMAKE_CURRENT_BINARY_DIR}/deal.II/deal.tag
DESTINATION ${DEAL_II_DOCHTML_RELDIR}/doxygen
COMPONENT documentation
)
signature.asc
Description: OpenPGP digital signature
Bug#789975: FTBFS: CMake Error at doc/doxygen .. INSTALL cannot find .. doc/doxygen/deal.tag
Source: deal.ii Version: 8.1.0-4 Followup-For: Bug #789975 Hi, hitting the same problem here: CMake Error at doc/doxygen/cmake_install.cmake:36 (file): file INSTALL cannot find "/debian/rebuild/deal.ii-8.1.0/obj-x86_64-linux-gnu/doc/doxygen/deal.tag". Call Stack (most recent call first): doc/cmake_install.cmake:52 (include) cmake_install.cmake:39 (include) debalance@carter:/debian/rebuild/deal.ii-8.1.0$ find . -iname deal.tag ./obj-x86_64-linux-gnu/doc/doxygen/deal.II/deal.tag It looks like a tiny patch to doc/doxygen/CMakeLists.txt could fix this. Regards, Philipp -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764451: libpam-mount: Fails to run mount: invalid option -- '-p'
Hi On 18/12/14 20:07, Christian Kastner wrote: > would you be willing to upload the fix to DELAYED/5 so that we can see > this bug closed soon? Yes, I just did. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#764451: libpam-mount: Fails to run mount: invalid option -- '-p'
Hi On 16/12/14 22:30, Christian Kastner wrote: >> I attached a debdiff for an NMU which drops the -p option. I'd >> appreciate it an affected user could test this. For convenience, you can >> find an amd64 version of the package here: >> >> http://www.kvr.at/debian/pool/main/libp/libpam-mount/libpam-mount_2.14-1.1_amd64.deb > > did anyone manage to get this tested? It's working fine for me, but my > pam_mount.conf is quite trivial. I can confirm that this new version fixes the problem. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#764451: libpam-mount: Fails to run mount: invalid option -- '-p'
Hi, On 16/12/14 22:30, Christian Kastner wrote: > did anyone manage to get this tested? It's working fine for me, but my > pam_mount.conf is quite trivial. I will test this later today. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#764974: ejabberd: postinst uses /usr/share/doc content (Policy 12.3)
Hi, On 05/11/14 05:23, udoprog wrote: > I've been working on a patch for this, it can be found here: > https://github.com/udoprog/pkg-ejabberd/commit/d1baef0327b2652f268b731f6dae215abe4d9678.patch > Tested with: > dpkg --path-exclude=/usr/share/doc/ejabberd/examples/ejabberd.yml.example > -i thanks, I will include it soon with the next upload! Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#764974: ejabberd: postinst uses /usr/share/doc content (Policy 12.3)
Hi, there's nothing new you're telling us, it's already in this bugreport and on the TODO list for the next upload. Setting the urgency to serious and thus threatening to have ejabberd removed from Testing because of this isn't gonna help, so what are you trying to achieve here? This bug has been present since the stable release at least. Feel free to provide a working+tested patch that fixes it. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#658896: Still an issue
Hi, I can confirm that Carlos' simple patch in [0] fixes the issue, but so does the recently uploaded libldap-2.4-2 package version 2.4.40-1. The code that Carlos suggested to patch was removed, so the patch doesn't apply anymore because it isn't needed any longer. Personally I would recommend adding Carlos' patch for the wheezy package. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658896#104 Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#757858: ejabberd: Upgrade from 2.1.x to 14.05 causes inconsistent conf of Mnesia db in /etc/default/ejabberd
Hi, thank you for this important information! Could you please clarify whether this is internal behaviour of ejabberd or related to handling the configuration files? For example, was EJABBERD_NODE previously set (manually / automatically) in /etc/default/ejabberd or not? Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#747673: Horrid default cipher settings without option to adjust them to sane values
Hi, ejabberd 2.1.11-1 is pretty much useless by now, look at the RC bugs #746029 and #746073. Nevertheless I would like to know how you retrieved this information and if it still applies to 14.05. If so I will forward it to upstream, although you're welcome to do it yourself at https://support.process-one.net/ Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#746029: ejabberd RC bug
Hi, ejabberd releases prior to 14.05 don't work with Erlang/OTP >= R17. I am working on a package for 14.05 and will upload a first version to experimental once erlang-p1-sip has been accepted into unstable. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#745583: erlang-xmlrpc: FTBFS without .git
Hi, thanks for reporting this! I used git-buildpackage and even when combined with pbuilder/cowbuilder this doesn't happen, but I am able to reproduce this with the package in the archive and plain pbuilder. I'll try to patch out that behaviour and upload a fixed version soon. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#648891: munin-node: upgrade to perl 5.14 breaks munin-node
Package: munin-node Version: 1.4.6-1 Severity: grave Justification: renders package unusable I just upgraded my unstable system which brought perl 5.14 with it, when munin stopped working, saying "there are n nodes with any plugins". Checking the log of munin-node revealed this: 2011/11/16-09:05:02 [5995] 2011/11/16-09:05:02 [6069] Can't locate auto/POSIX/getpwuid.al in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl) at /usr/share/perl5/Munin/Node/OS.pm line 32\n ...propagated at /usr/share/perl5/Munin/Common/Timeout.pm line 66, line 76. It is clearly visible that munin-node tries to use perl 5.12 which is not installed anymore. Regards, Philipp -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages munin-node depends on: ii adduser 3.113 ii gawk1:3.1.8+dfsg-0.1 ii libnet-server-perl 0.99-3 ii lsb-base3.2-28 ii munin-common1.4.6-1 ii perl5.14.2-3 ii procps 1:3.2.8-11 Versions of packages munin-node recommends: ii libnet-snmp-perl 6.0.1-2 Versions of packages munin-node suggests: ii acpi 1.5-3 ii ethtool 1:3.0-1 ii hdparm ii libcache-cache-perl ii libcrypt-ssleay-perl ii libdbd-mysql-perl ii libdbd-pg-perl ii liblwp-useragent-determined-perl ii libnet-irc-perl ii libnet-ssleay-perl1.42-1+b1 ii libtext-csv-xs-perl ii libwww-perl 6.03-1 ii libxml-simple-perl ii lm-sensors1:3.3.1-1 ii logtail ii munin 1.4.6-1 ii munin-java-plugins1.4.6-1 ii munin-plugins-extra 1.4.6-1 ii mysql-client ii net-tools 1.60-24.1 ii python2.7.2-9 ii ruby 4.8 ii ruby1.8 [ruby]1.8.7.352-2 ii smartmontools 5.41+svn3365-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#566740: iscsitarget-source: Module does not compile against 2.6.32 kernel (squeeze)
Hi, I can confirm that the mentioned patch works. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` HP: http://www.debalance.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Bug#567528: python-kde4: Uninstallable package due to unfulfilled dependency
Hi, please fix this bug, it really freaks me out. I can't use plasma applets that need plasma-scriptengine-python, my own package kanyremote is uninstallable, and more. And how did you manage to create this: "python-kde4: Depends: python-sip4 (>= ) but 4.10-2 is to be installed" I've never seen that before. Regards, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` HP: http://www.debalance.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Bug#569261: FTBFS: failed to change mode of debian/anyremote-data/…
Hi, thanks KiBi, I had already noticed that but was (and am) lacking the time to fix it. I was wondering why it builds fine for me in pbuilder but fails on the buildds. Once I thought about what difference between me and the buildds is, realization hit me ;) I won't have time to fix this before sunday, so if someone would like to do an NMU, go for it. Best wishes, -- .''`. Philipp Huebner : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` HP: http://www.debalance.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Bug#540113: python-kde4: package not installable because of strange python-qt4 dependency
Package: python-kde4 Version: 4:4.2.4-2 Severity: grave Justification: renders package unusable The package has got this dependency on python-qt4: python-qt4 (>= 4.5.1-1), python-qt4 (<< 4.5.1-1+~) This makes the package uninstallable in sid because there was a NMU to python-qt4, which is now 4.5.1-1.1 . The following packages have unmet dependencies: python-kde4: Depends: python-qt4 (< 4.5.1-1+~) but 4.5.1-1.1 is to be installed E: Broken packages -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (700, 'experimental'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-kde4 depends on: ii kdebase-runtime 4:4.2.4-2 runtime components from the offici ii kdelibs5 4:4.2.4-1 core libraries for all KDE 4 appli ii kdepimlibs5 4:4.2.4-1 core libraries for KDE PIM 4 appli ii libc6 2.9-23 GNU C Library: Shared libraries ii libgcc1 1:4.4.1-1 GCC support library ii libphonon44:4.5.2-1 Qt 4 Phonon module ii libplasma34:4.2.4-1 library for the KDE 4 Plasma deskt ii libqt4-network4:4.5.2-1 Qt 4 network module ii libqt4-svg4:4.5.2-1 Qt 4 SVG module ii libqt4-xml4:4.5.2-1 Qt 4 XML module ii libqtcore44:4.5.2-1 Qt 4 core module ii libqtgui4 4:4.5.2-1 Qt 4 GUI module ii libsoprano4 2.3.0+dfsg.1-2 libraries for the Soprano RDF fram ii libstdc++64.4.1-1The GNU Standard C++ Library v3 ii phonon4:4.5.2-1 Qt 4 Phonon module metapackage ii python2.5.4-2An interactive high-level object-o pn python-qt4 (no description available) pn python-sip4(no description available) ii python-support1.0.3 automated rebuilding support for P ii python2.5 2.5.4-1An interactive high-level object-o python-kde4 recommends no packages. python-kde4 suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532574: python-kde4: Upgrading to python-qt4 4.5.1 breaks python-kde4
Hello, I'm the maintainer of kanyremote. Because of this bug, I can't upload it's new upstream version. It segfaults right at the beginning, because with the new release upstream switched from python-qt3/kde3 to python-qt4/kde4. Downgrading python-qt4 as mentioned before made the program work, so I would also think that this bug belongs to python-qt4 rather than python-kde4. However, I'm not a python expert, I just would appreciate very much if this problem could somehow be solved soon, as downgrading manually doesn't really help. Regards, -- .''`. Philipp Hübner : :' : pgp fp: BA61 0B0A 2626 D49C BFC6 1C18 1619 74E4 C259 E0E8 `. `'` HP: http://debalance.funpic.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
