Bug#1040988: fixed in picom 10.2-2

On Tue, 26 Dec 2023 16:19:12 + Debian FTP Masters wrote: * Fix infinite loop with GNOME (Closes: #1040988) Upstream also added: https://github.com/yshui/picom/commit/7366553be2b825495c5b1e09be09d0fabde4b9b4 Otherwise, picom won't start at the beginning of a session (no windows

Bug#1027382: Please, minimize your build chroots

On 2023-01-28 13:59, Adrian Bunk wrote: I am not saying that trying to force maintainers to spend time on such issues by making them release critical is better, but you are also creating extra work and frustration for the people who are doing QA work in Debian. It also pushes some maintainers

Bug#1027382: Please, minimize your build chroots

On 2023-01-28 00:20, Santiago Vila wrote: Release Policy exists as a canonical list of what should be RC and > what not, and it's intended to avoid stupid discussions like this one. Extending build-essential is easier than asking many people to do pointless work to satisfy a set of

Bug#1023697: Keep out of testing

On Thu, 10 Nov 2022 22:45:57 +0100 Bastian Germann wrote: As a new maintainer has stepped up, this cannot be the reason anymore to dump the package. Actually, with the next version of swupdate (one of those handful) I wanted to switch from OpenSSL to SWUpdate. As there are no real plan to

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

On 2022-10-29 09:23, Salvatore Bonaccorso wrote: So question is,.. would it make sense to request that linux-image-amd64 depends on the signed | unsigned version? No unfortunately we cannot do that. The reason is similar to what lead to

Bug#968997: fwupdmgr: "Successfully" updates BIOS firmware, no effect on reboot

On Fri, 10 Sep 2021 10:35:31 +0200 Julian Andres Klode wrote: Control: reassign -1 shim Control: affects -1 fwupd On Fri, Sep 10, 2021 at 09:27:11AM +0200, Norbert Schulz wrote: > Package: fwupd > Version: 1.2.14-1~deb10u1 > Followup-For: Bug #968997 > > Dear Maintainer, > > this bug still

Bug#1013581: Please rebuild to pick up the new libXi.6 dependency.

Version: 3.19-9 On 6/24/22 13:39, Peter Pentchev wrote: If this is the case, could you just request a binNMU? Hm, that's actually an interesting idea... I'll look into it, and, in that case, sorry for bothering you! :) So yeah, I will look into it and probably close this bug accordingly. I

Bug#1013581: Please rebuild to pick up the new libXi.6 dependency.

On 6/24/22 13:05, Peter Pentchev wrote: Source: xnee Version: 3.19-8 Severity: serious X-Debbugs-Cc: r...@debian.org Hi, First of all, thanks for taking care of cnee/xnee in Debian! At some point recently, the XIQueryVersion() function from the X11 API moved to a separate library, libXi.so.6,

Bug#1012275: closing 1012275

❦ 3 June 2022 20:48 +02, Salvatore Bonaccorso: > close 1012275 101.0-1 Unfortunately, Firefox is not buildable due to depending on a version of Cargo not available in unstable. -- Don't diddle code to make it faster - find a better algorithm. - The Elements of Programming Style

Bug#1008323: bpftrace: fix FTBFS

❦ 11 April 2022 21:14 +02, Hector Oron: > According to https://github.com/iovisor/bpftrace/issues/2068 > > I applied the following patch to make the package build: Thanks! I will use the more minimal patch found here instead: https://github.com/iovisor/bpftrace/pull/2174 -- Make sure

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

severity -1 important fixed -1 1:2.2.7-1~bpo11+1 thanks ❦ 24 March 2022 17:24 +01, Arturo Borrero Gonzalez: > This exact same setup was previously working, and actually, the next version > works just fine. > Not sure if this has anything to do with the kernel version warning at the >

Bug#965696: libwhisker2-perl: diff for NMU version 2.5-1.2

Thanks! If you want to take over this package, be my guest! On January 1, 2022 6:35:04 PM GMT+01:00, gregor herrmann wrote: >Control: tags 965696 + patch >Control: tags 965696 + pending >Control: tags 999044 + patch >Control: tags 999044 + pending > > >Dear maintainer, > >I've prepared an NMU

Bug#995212: ungoogled-chromium? [

❦ 14 December 2021 09:13 GMT, Jeff Blake: > Unless there are licensing or technical objections, I would suggest building > with upstream > bundled clang to avoid all sorts of incompatibilities and obviate the need > for extra patching > (stable's clang is often too old and upstream currently

Bug#997218: keepalived: FTBFS: if.h:44:5: error: redeclaration of enumerator ‘IFF_UP’

ersion 2.2.1 * [ecf662d] Keepalived has now support for systemd notify - -- Alexander Wirt Mon, 25 Jan 2021 09:04:08 +0100 + [ Vincent Bernat ] + * Non-maintainer upload. + * New upstream version 2.2.4. Closes: #980563. +- Fix FTFBS. Closes: #997218. + * d/rules: enable systemd as a

Bug#998108: Tracking this bug down

❦ 4 November 2021 23:39 +01, Eugen Dedu: > Maybe I am wrong, but, for me, the simplest method to track this bug > down is to check the changes between the two versions, 93.0 and > 93.0-1+b1. Firefox code has not changed, only one or some libraries > it depends on. I thought that the only

Bug#993658: qemu-user-static does not work through binfmt since 6.0

❦ 4 September 2021 15:49 +03, Michael Tokarev: >> Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads) > > Can you please check if it works with not-so-fresh kernel > (eg the one from bullseye)? > > I wont able to do this until late evening today. > > I'm guessing this is the upstream way to

Bug#993658: qemu-user-static does not work through binfmt since 6.0

Package: qemu-user-static Version: 1:6.1+dfsg-4 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Since 6.0, qemu-user-static does not seem to work properly through binfmt. I am a bit lost on how to diagnose that: 13:23 ❱ cat /proc/sys/fs/binfmt_misc/qemu-aarch64 enabled

Bug#990079: tagging 935548, tagging 986803, tagging 989479, tagging 990079, tagging 990528, tagging 990525 ...

❦ 17 July 2021 23:30 +02, Sebastian Ramacher: > # can be fixed via DSAs > tags 935548 + bullseye-ignore > tags 986803 + bullseye-ignore > tags 989479 + bullseye-ignore > tags 990079 + bullseye-ignore > tags 990528 + bullseye-ignore > tags 990525 + bullseye-ignore > tags 990691 + bullseye-ignore

Bug#984767: dh-virtualenv: Can't build packages with compat >= 12 as --buildsystem doesn't work

severity 984767 normal tag 984767 + moreinfo thanks ❦ 8 mars 2021 08:55 +01, Johann Queuniet: > I have issues with building packages with dh-virtualenv using a compat > of 12 or higher, ending up with the following error: > > ``` > debian/rules binary > dh binary --with python-virtualenv

Bug#984939: marked as pending in python-netaddr

Control: tag -1 pending Hello, Bug #984939 in python-netaddr 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:

Bug#980438: do not depend on the non-public binutils ABI

❦ 19 janvier 2021 10:57 +01, Vincent Bernat: >> bpftrace should not depend on the non-public binutils ABI. This always >> generated >> an upper dependency on libbinutils. If you think it's worth having this >> dependency, please statically link with libbinutils and re

Bug#980438: do not depend on the non-public binutils ABI

❦ 19 janvier 2021 08:33 +01, Matthias Klose: > bpftrace should not depend on the non-public binutils ABI. This always > generated > an upper dependency on libbinutils. If you think it's worth having this > dependency, please statically link with libbinutils and record the the version > used in

Bug#977549: bpftrace: all programs fail with Segmentation fault

clone 977549 -1 reassign -1 libbpfcc retitle -1 libbpfcc: please compile with -DENABLE_LLVM_SHARED=on severity -1 normal found -1 0.17.0-8 block 977549 by -1 thanks ❦ 16 décembre 2020 16:48 +01, Emanuele Rocca: > Package: bpftrace > Version: 0.11.3-3 > Severity: grave > Justification: renders

Bug#972134: chromium: please, consider moving the package to team-maintainance to properly maintain it

❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff: > Michael has been heroically keeping up with this beast of a codebase for > years, > but we clearly need a broader base to sustain it going forward. In the past, it was team-maintained. I don't remember exactly, but I think there was a

Bug#970810: python3-venv is gone

❦ 6 octobre 2020 12:32 +03, Jyrki Pulliainen: > Now, python3.8-venv contains the ensurepip module. But to me it is very > unclear if python3.8-venv is going to disappear? It also makes depending on > these packages generally a lot more brittle: I'd rather depend on > python3-venv than

Bug#972138: error: The name org.freedesktop.Accounts was not provided by any .service files

Package: flatpak Version: 1.8.2-2 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! After upgrading to 1.8.2-2, I cannot run any Flatpak. I have tried com.spotify.Client and us.zoom.Zoom and both of them are returning the following error: error: The name

Bug#957989: xnee: ftbfs with GCC-10

❦ 23 juillet 2020 12:59 +03, Peter Pentchev: >> > If you add "-fcommon" to gcc-10 it should work. >> >> this would be a work-around, not a fix. > > Hi, > > Fix proposed: > > https://savannah.gnu.org/bugs/index.php?58810 > > https://salsa.debian.org/debian/xnee/-/merge_requests/1 Thanks! I'll

Bug#962320: facter crashes with "free(): invalid pointer"

Package: libfacter3.11.0 Version: 3.11.0-4.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {0, 1431634051, 94476679444720, 139623352393688, 0, 94476679915560, 94476680133744,

Bug#958450: chromium: Please update chromium to 81.0.4044.113 for security reasons

On Wed, 22 Apr 2020 11:55:00 +0300 jim_p wrote: > As the title suggests, please update chromium to 81.0.4044.113 (or later), > because it includes a patch for CVE-2020-6457, which is a critical security > issue. More info here >

Bug#937429: pyeos: Python2 removal in sid/bullseye

❦ 24 avril 2020 20:54 +02, Moritz Mühlenhoff: >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2removal >> >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >>

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

Package: libgcc1 Version: 1:10-20200202-1 Followup-For: Bug #950551 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! On both my systems running unstable, libgcc-s1 is installed, but I don't have /usr/lib/x86_64-linux-gnu/libgcc_s.so.1. So, it seems something removes it. I have no clue on

Bug#949178: linux-image-5.4.0-2-amd64: system freeze with i915 with error: 0000:00:02.0: Resetting rcs0 for hang on rcs0

❦ 17 janvier 2020 20:23 +01, Davide Prina : > Jan 15 11:37:33 prinad03 kernel: [ 9354.966794] i915 :00:02.0: GPU > HANG: ecode 9:1:0x, hang on rcs0 You may want to follow this thread. 5.3 and 5.4 seem to be difficult kernels for Intel graphic cards. It's unknown if 5.5 will fix it

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

Hello Michael, I was able to hit the bug again. It seems I have to go to another wifi network, then back to my home network to hit the bug. On the client-side, I get: janv. 06 18:57:13 zoro NetworkManager[75721]: [1578333433.9474] dhcp4 (wlp3s0): activation: beginning transaction (timeout in

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

❦ 29 décembre 2019 13:40 +01, Michael Biebl : > Can you provide a full, verbose debug log: > > https://wiki.gnome.org/Projects/NetworkManager/Debugging > > Which dhcp client do you use: internal, isc-dhcp-client, ...? I am using the internal client. Unfortunately, I am not able to reproduce the

Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

Package: network-manager Followup-For: Bug #947613 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! I've got the same problem. Comparing the output of "journalctl -u NetworkManager" on both versions, the only difference I am able to spot is that with 1.22.2-1, I have these lines: déc. 29

Bug#923782: Relax dependency on faraday to allow updating ruby-faraday

Package: ruby-puppet-forge Followup-For: Bug #923782 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! With the provided patch, I am able to use librarian-puppet without any issue. Unless someone protests, I'll do a NMU next week to fix this bug. - -- System Information: Debian Release:

Bug#921484: Origin of background.js and manifest.json not documented?

Package: webext-browserpass Version: 2.0.22-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! I am curious to know why there is a debian/background.js as well as a debian/manifest.json? They are not documented in debian/copyright. The manifest seems to have a bogus

Bug#915636: python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0

❦ 13 décembre 2018 11:54 +0100, Vincent Bernat : >> find attached my NMU .debian.tar using the updated 16.1.0 version. >> As I found no documentation what you +ds version removed from the >> upstream TAR ball, I'm using the pristine upstream TAR ball. >> >> Upstre

Bug#915636: python3-virtualenv: incompatible with python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0

❦ 5 décembre 2018 15:12 +0100, Philipp Hahn : > find attached my NMU .debian.tar using the updated 16.1.0 version. > As I found no documentation what you +ds version removed from the > upstream TAR ball, I'm using the pristine upstream TAR ball. > > Upstream moved most files to the src/

Bug#915043: nikto: missing build on all

❦ 29 novembre 2018 16:51 -0200, Eriberto Mota : > I've prepared an NMU for nikto (versioned as 1:2.1.5-3.1) and > uploaded it to DELAYED/10. Please feel free to tell me if I > should delay it longer. Thanks. You can upload it right now if you want. -- What I tell you three times is true.

Bug#906978: Bug is in pysnmp4

❦ 10 septembre 2018 14:32 +0200, Thomas Goirand : > Upstream updated the issue and write it's an problem with pysnmp4: > > https://github.com/etingof/pysnmp/issues/193 > > The issue is fixed in the master branch of pysnmp, but there's no > release for it yet. > > Should we reasign the bug? I'll

Bug#906955: isync: can't verify some ssl certificate(e.g. imap.gmail.com)

Package: isync Version: 1.3.0-1 Followup-For: Bug #906955 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! I run into the same problem. Here is a patch fixing the issue for me: https://sourceforge.net/p/isync/isync/merge-requests/2/ I don't know why it worked with OpenSSL 1.1.0. I didn't

Bug#905403: graphite-api ftbfs

❦ 4 août 2018 07:33 +0200, Matthias Klose : > Package: src:graphite-api > Version: 1.1.3-3 > Severity: serious > Tags: sid buster > > missing build dependencies? > > running build_ext > tests (unittest.loader._FailedTest) ... ERROR > >

Bug#903663: python3-numpy: Should not depend on python3.7

Package: python3-numpy Followup-For: Bug #903663 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! Why does python3-numpy depend on Python 3.7? It should work with any Python 3.x package. As a number of packages are uninstalled when python3.7 is installed, it would be convenient to not have

Bug#872413: kpatch: Please package new upstream version

❦ 15 avril 2018 09:58 +0200, Simon Ruderich  : >> As the package is not currently usable with our kernel, or even the >> one in stable, I am bumping the severity. Since you already worked a >> lot on this, would you be interested to prepare an upload for 0.5.0? If >> yes, we

Bug#894533: cookiecutter: please drop catchlog dependency

❦ 5 avril 2018 09:25 +0200, Gianfranco Costamagna  : > I uploaded the package in deferred/5, as Team upload. > > Unfortunately I can't push because the 1.6.0-1 upload hasn't been > pushed yet, so I'll attach the debdiff between the current package in > unstable and the

Bug#887579: marked as pending

82dfdb4c190f9ae7e3a0dd99c6e88333e8fa38c5 Author: Vincent Bernat <vinc...@bernat.im> Date: Thu Jan 18 08:53:38 2018 +0100 Fix crashing test with recent python-hypothesis diff --git a/debian/changelog b/debian/changelog index 0378bc0..e5e57f8 100644 --- a/debian/changelog +++ b/debian/changelog @

Bug#880352: marked as pending

072b98813bec20e0ded34389e91078fd369270d9 Author: Vincent Bernat <ber...@debian.org> Date: Sun Nov 26 19:06:57 2017 +0100 d/rules: clean generated C files. Closes: #880352 diff --git a/debian/changelog b/debian/changelog index 6f64715..94ade01 100644 --- a/debian/changelog +++ b/debian/cha

Bug#881096: marked as pending

30e52d38eb1f96ae111049aefca3871bba47ab4d Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Nov 11 21:23:48 2017 +0100 d/patches: remove tests using deprecated ciphers. Closes: #881096 diff --git a/debian/changelog b/debian/changelog index 33bae7b..be7f973 100644 --- a/debian/changelog +++ b/

Bug#881096: marked as pending

fd7facb7998eee7e7eea9c74335ab5b9c8e28104 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Nov 11 21:39:41 2017 +0100 d/changelog: still a bug to be fixed diff --git a/debian/changelog b/debian/changelog index be7f973..2079fc5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,

Bug#882125: incompatible with pidgin apparmor profile

Package: pidgin-sipe Version: 1.23.0-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! AppArmor is now enabled by default in Debian and pidgin comes with an AppArmor profile. When pidgin-sipe is installed, we get this error: /usr/bin/pidgin: line 7:

Bug#871127: marked as pending

e3f36dfe611bae5e6e4424762b3bd0300f01a73c Author: Vincent Bernat <vinc...@bernat.im> Date: Mon Sep 18 19:15:52 2017 +0200 New upstream version diff --git a/debian/changelog b/debian/changelog index 1420be4..8abb790 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +pytest-mock (1

Bug#854701: python-asyncssh: FTBFS randomly (failing tests)

❦ 7 mars 2017 14:04 +0100, Santiago Vila  : > To double-check, I just build this package today 100 times and it > failed 72 times. Could you try again with 1.11.0-1 in unstable? I am unable to get any failure, but wasn't able to get them in the first place. -- Replace

Bug#871692: [pkg-go] Bug#871692: gobgp FTBFS on arm64: Test killed with quit: ran too long (10m0s).

❦ 10 août 2017 20:29 +0300, Adrian Bunk  : > https://buildd.debian.org/status/fetch.php?pkg=gobgp=arm64=1.22-1=1502350034=0 time="2017-08-10T07:25:14Z" level=debug msg="failed to connect: function not implemented" Key=127.0.0.1 Topic=Peer I suspect the running kernel doesn't

Bug#867396: marked as pending

3010d920ae44d29f03aa9acd93f9de897864cc6c Author: Vincent Bernat <ber...@debian.org> Date: Thu Jul 6 20:00:24 2017 +0200 Fix python3-cerealizer Depends field. Closes: #867396 diff --git a/debian/changelog b/debian/changelog index 7204666..962493d 100644 --- a/debian/changelog +++ b/debian/changelog @

Bug#840516: patterns are deprecated

❦ 8 mai 2017 10:38 GMT, Stephane Bortzmeyer  : > There are several reasons why graphite-web does not work with Django > 1.10 (the current version in sid). One of them is that it uses the > "patterns" variable: This seems to have been fixed upstream (but unreleased):

Bug#861388: [Pkg-roundcube-maintainers] Bug#861388: roundcube: CVE-2017-8114: security issue in virtualmin and sasl drivers

❦ 1 mai 2017 23:57 +0200, Guilhem Moulin  : >> the following vulnerability was published for roundcube. >> >> CVE-2017-8114[0]: >> security issue in virtualmin and sasl drivers > > Thanks, pushed. Sandro, Vincent, would you mind tagging & uploading? Done. Thanks! --

Bug#861366: Etherpuppet, unusuable on systems with unsigned char.

❦ 28 avril 2017 02:04 +0100, peter green  : > Etherpuppet has a bug with it's command line parsing that makes it > unusable on systems with unsigned char. Someone found an upstream fix > for me and submitted it to a raspbian bug report. > > A debdiff can be found at >

Bug#859655: [pkg-go] Bug#859655: golang-go.crypto: CVE-2017-3204

❦ 14 avril 2017 15:07 -0400, anarcat  : > I looked into this during the Montreal BSP, and it's unclear what we > should do here, considering there has been multiple new uploads since > the stretch freeze. > > The patch is pretty long: > >

Bug#857473: [Pkg-roundcube-maintainers] Bug#857473: roundcube: XSS issue in handling of a style tag inside of an svg element

❦ 14 mars 2017 04:16 +0100, Guilhem Moulin  : >> 1.2.4 roundcube release fixed a XSS issue in handling of a style tag >> inside of an svg element. > > Thanks for the ping and the pointers! I applied the fix to 1.2.3 > (unstable) and 1.1.5 (jessie-backports). > > Could

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

❦ 10 mars 2017 09:29 GMT, Simon McVittie  : >> I suppose that's why I am in copy (the other actions are pretty obvious >> and I suppose Scott will apply them soon; I can also do that if he's >> unavailable). > > The other reason I wanted to Cc you is because as sponsor, you were

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

❦ 10 mars 2017 00:18 GMT, Simon McVittie  : > Third bug: libraries with different SONAME versioning packaged together > --- > > Lintian has done its best to advise the maintainer not to do this, but >

Bug#855906: [pkg-go] Bug#855906: golang-codegangsta-cli: FTBFS: FAIL: TestCommandYamlFileTestDefaultValueFileWins (0.00s) helpers_test.go:10: Expected 15 (type int) - Got 7 (type int)

❦ 4 mars 2017 17:38 -0300, Martín Ferrari  : > Vincent, are you requesting an unblock exception for this package? There > are a bunch of other packages that are going to be removed from testing > if this does not migrate. I just sent the unblock request. -- Write and test a

Bug#855906: golang-codegangsta-cli: FTBFS: FAIL: TestCommandYamlFileTestDefaultValueFileWins (0.00s) helpers_test.go:10: Expected 15 (type int) - Got 7 (type int)

❦ 23 février 2017 16:57 +0800, Chris Lamb  : > dh_auto_test: go test -v -p 1 github.com/codegangsta/cli > github.com/codegangsta/cli/altsrc returned exit code 1 > debian/rules:4: recipe for target 'build' failed > make: *** [build] Error 1 > dpkg-buildpackage: error:

Bug#855208: [pkg-go] Bug#855208: docker still broken

❦ 24 février 2017 12:34 -0800, Norbert Kiesel  : > What else can I do to get docker working again? You can install the one from experimental. It works fine with runc and containerd from unstable. At this point, Tim should just upload it to unstable. -- Use variable names

Bug#854851: marked as pending

0 + +binaryornot (0.4.0-1) unstable; urgency=medium + + * New upstream release. + * Bump Standards-Version. + * Use PYBUILD_NAME in d/rules. + * Add missing Build-Depends on python-{chardet,hypothesis}. + + -- Vincent Bernat <ber...@debian.org> Sun, 15 Nov 2015 23:05:18 +0100

Bug#854084: binaryornot: Non-determistically FTBFS due to unreliable timing in tests

Control: severity -1 normal <#secure method=pgpmime mode=sign> ❦ 4 février 2017 09:25 +1300, Chris Lamb  : > […] > > == > ERROR: test_never_crashes (tests.test_check.TestDetectionProperties) >

Bug#851707: [pkg-gnupg-maint] Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

❦ 3 février 2017 12:14 +0100, Werner Koch  : >> I am fixing with this patch. Only lightly tested. > > FWIW, I forgot to push a fix I had in my local repo. Just did this, put > also not tested. This is basically the same as yours but w/o any > delay. I think your patch is

Bug#851707: pinentry-gtk-2 frequently fails to grab the keyboard under awesome

Control: tags -1 + patch ❦ 2 février 2017 10:50 +0200, Lauri Niskanen <a...@ape3000.com> : > I can reproduce this bug with awesomewm on Arch Linux. I get the same > error message as Vincent Bernat. > > As a workaround I changed my pinentry program to pinentry-gn

Bug#851020: marked as pending

ebe72f778cded72cd09bcbc99f80e446c2fd3535 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Jan 21 21:00:28 2017 +0100 Add a patch to fix FTBFS due to agent-related test failure diff --git a/debian/changelog b/debian/changelog index ecd7f31..31ebb61 100644 --- a/debian/changelog +++ b/debian/cha

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Control: clone -1 -2 Control: retitle -2 pinentry-gtk-2 frequently fails to grab the keyboard under awesome <#secure method=pgpmime mode=sign> ❦ 17 janvier 2017 20:34 +0100, Vincent Lefevre  : >> ** (pinentry-gtk-2:21583): CRITICAL **: could not grab keyboard: not >>

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

❦ 17 janvier 2017 12:13 +0100, Vincent Lefevre  : >> I have the same behaviour with awesome. My setup didn't change since >> quite some time but this behaviour is recent while neither awesome nor >> pinentry-gtk2 has been updated. I got the behavior immediately after >>

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

❦ 11 janvier 2017 01:47 -0500, Daniel Kahn Gillmor  : > On Tue 2017-01-10 20:58:16 -0500, Vincent Lefevre wrote: >> On 2017-01-10 18:26:57 -0500, Daniel Kahn Gillmor wrote: >>> what window manager are you using? >> >> fvwm > > hm, both Vincent and gi1242 are using fvwm.

Bug#850023: marked as pending

a0a9ef3eebe1fd45a60af6b4e8c29ec04c276077 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Jan 7 08:43:18 2017 +0100 Build-Depends on python-typing diff --git a/debian/changelog b/debian/changelog index 4850af3..49f2d76 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,12 @@ -ruame

Bug#850023: ImportError when importing ruamel.yaml

❦ 6 janvier 2017 22:51 GMT, Chris Lamb  : > So, the binary package is missing a Depends on `python-typing`. > > However, it looks like this "should" work: > >install_requires=dict( >[…] >py27=["ruamel.ordereddict", "typing"], >[…] >) This seems

Bug#849994: [Pkg-roundcube-maintainers] Bug#849994: roundcube-core: install fails; Class 'Patchwork\Utf8\Bootup' not found

❦ 3 janvier 2017 11:13 +0200, Guilhem Moulin  : > If that's indeed the case, we should lower the severity as if this bug > doesn't apply to 1.2.3+dfsg.1-1 it shouldn't prevent its inclusion in > Stretch. The Version: is correctly set, so it shouldn't be needed. -- Be

Bug#824738: marked as pending

087e956bbdb6bda9de89037998bcbca3bfc7e238 Author: Vincent Bernat <vinc...@bernat.im> Date: Sun Dec 25 10:49:00 2016 +0100 Switch to pybuild diff --git a/debian/changelog b/debian/changelog index 459e56d..5299080 100644 --- a/debian/changelog +++ b/debian/changelog @@ -6,6 +6,8 @@ simpleparse (2

Bug#847325: Unable to copy symlinks with copy_file

❦ 8 décembre 2016 02:08 GMT, Ben Hutchings  : > (Annoyingly, I couldn't reproduce this at first because I tried just > adding nouveau to /etc/initramfs-tools/modules. Since mkinitramfs does > *not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was > not

Bug#847287: [Pkg-roundcube-maintainers] Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

❦ 7 décembre 2016 12:08 +0100, Guilhem Moulin  : >> Is the tag for debian/1.1.5+dfsg.1-1_bpo8+1? The diff for it is pretty >> big. > > 1.1.5+dfsg.1-1_bpo8+1 is the current version from jessie-backports (since > April 29). The diff between 1.1.5+dfsg.1-1_bpo8+1 and

Bug#847287: [Pkg-roundcube-maintainers] Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

❦ 7 décembre 2016 11:27 +0100, Guilhem Moulin  : >>> Unfortunately 1.2.x has many dependencies that aren't in >>> jessie-backports yet. I personally don't have the time nor energy to >>> maintain said dependencies, so we asked backports folks for an exception >>> to stick

Bug#847312: [Pkg-roundcube-maintainers] Bug#847312: roundcube: maintainer address bounces

❦ 7 décembre 2016 09:52 +0100, Chris Lamb  : > I tried to send an email to this package address, and I got: > >Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > As per

Bug#847287: [Pkg-roundcube-maintainers] Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

❦ 7 décembre 2016 00:30 +0100, Guilhem Moulin  : >> Version: 1.1.4+dfsg.1-1~bpo8+1 >> […] >> So probably it is important to update to upstream version 1.2.3 > > Unfortunately 1.2.x has many dependencies that aren't in > jessie-backports yet. I personally don't have the

Bug#843853: Uninstallabel due to dependency on libgstreamer-plugins-bad1.0-0 (< 1.8.4)

Package: gstreamer1.0-vaapi Version: 1.8.3-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! gstreamer-vaapi is currently uninstallable (in unstable only) due to its dependency on libgstreamer-plugins-bad1.0-0. - -- System Information: Debian Release: stretch/sid APT

Bug#843644: Root cause

❦ 9 novembre 2016 11:32 +0100, Vincent Bernat <ber...@debian.org> : >> Sandro: I don't think I can fix this properly from the cryptography >> side since these constants are actually gone from libssl, but since >> they only need to _exist_ and not actually _

Bug#843644: Root cause

❦ 8 novembre 2016 18:35 GMT, Tristan Seligmann  : > Sandro: I don't think I can fix this properly from the cryptography > side since these constants are actually gone from libssl, but since > they only need to _exist_ and not actually _work_ in order to import > the

Bug#842979: Missing dependency on python-jtextfsm

Package: python-napalm-base Version: 0.18.0-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have missed this dependency (which replaces gtextfsm). Will package it shortly. - -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500,

Bug#835241: marked as pending

f3e6ab3d77a427bf97e5fdcf11fdd1aa525439e9 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Sep 3 12:32:16 2016 +0200 New upstream release diff --git a/debian/changelog b/debian/changelog index 9e742d0..b4f4f0d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +pytest-mock

Bug#835241: bug 835241 is forwarded to https://github.com/pytest-dev/pytest-mock/issues/61

❦ 11 octobre 2016 11:10 CEST, Petter Reinholdtsen  : > The upstream fix for this is available as > https://github.com/pytest-dev/pytest-mock/pull/36 >. > > There do not seem to be a new upstream release with the > fix included. I was expecting a new release soon, but since

Bug#839393: exabgp: FTBFS sometimes (failing tests)

❦ 1 octobre 2016 14:17 CEST, Santiago Vila  : > I tried to build this package in stretch with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: > >

Bug#830609: marked as pending

f5a148c97a4d2b5f050f09970a6258f0a0b8b3ff Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Sep 17 09:48:28 2016 +0200 d/rules: prevent network access by defining https_proxy diff --git a/debian/changelog b/debian/changelog index 9ed029b..5954e5b 100644 --- a/debian/changelog +++ b/debian/cha

Bug#837025: marked as pending

cb45779f6fb7ffdd0b3c6d7cab4012a023b635a9 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Sep 10 14:23:55 2016 +0200 Fix FTBFS due to a target having both ":" and "::" variants This is likely due to a change in cdbs. diff --git a/debian/changelog b/debian/changelog ind

Bug#814696: marked as pending

fbe03c704a5516d314935eae15be37088ab05430 Author: Vincent Bernat <vinc...@bernat.im> Date: Sat Sep 10 14:08:26 2016 +0200 Replace manual use of localedef by localehelper package diff --git a/debian/changelog b/debian/changelog index b2233c9..641d3ae 100644 --- a/debian/changelog +++ b/debian/cha

Bug#830568: python-asyncssh: accesses the internet during build

❦ 4 septembre 2016 10:13 CEST, Chris Lamb  : >> > Oh! I thought we were discussing whether it was a bug at all […] not the >> > severity of the bug itself. >> >> This is why I think the issue should be discussed more broadly. > > To be clear, I was referring to that it was

Bug#830568: python-asyncssh: accesses the internet during build

❦ 3 septembre 2016 23:37 CEST, Chris Lamb  : >> If your bug was wishlist, I would just ignore it. It is severity serious >> and I have to handle it. Maybe it is legitimate. Maybe not. > > Oh! I thought we were discussing whether it was a bug at all — hence the > time you spent

Bug#830568: python-asyncssh: accesses the internet during build

❦ 4 septembre 2016 01:03 CEST, Santiago Vila  : >> [...] information leak [...] > > This is not just a privacy issue but also a reproducibility issue. > > It is bad that a package leaks information to the external world, > but it is even worse, I would say, that information

Bug#830568: python-asyncssh: accesses the internet during build

❦ 3 septembre 2016 21:22 CEST, Chris Lamb  : >> The policy says "may not". I am not a native speaker, but for me, this >> is not like "must not". Since you are a native speaker, I think you know >> better: is it optional or not? > > May I suggest an alternative approach…? We

Bug#830568: python-asyncssh: accesses the internet during build

❦ 3 septembre 2016 15:46 CEST, Chris Lamb  : >> Was this MBF discussed somewhere? > > I don't consider it to be a MBF — I haven't been systematically working > my way through the archive and I've really only filed a handful of bugs; > mostly quasi-duplicates due to Sphinx

Bug#830568: python-asyncssh: accesses the internet during build

❦ 9 juillet 2016 15:26 CEST, Chris Lamb  : > Source: python-asyncssh > Version: 1.5.6-1 > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access > > Dear Maintainer, > > Whilst python-asyncssh builds successfully on unstable/amd64,

Bug#834367: systemctl daemon-reexec (as run on systemd upgrade) causes all keystrokes to go to text console in addition to X (including passwords)

❦ 15 août 2016 00:53 CEST, Josh Triplett  : > [Severity and tag due to the likely possibility of exposing user > passwords this way. If this occurs with the version in jessie as well, > it'll require a security update.] I think this is fairly recent. I stumbled upon your

Bug#832118: ruby-puppet-forge: FTBFS: psych.rb:471:in `initialize': No such file or directory @ rb_sysopen - /usr/lib/ruby/locales/config.yaml (Errno::ENOENT)

❦ 22 juillet 2016 16:11 CEST, Chris Lamb  : > ruby-puppet-forge fails to build from source in unstable/amd64: It also fails to run. This seems due to the introduction of ruby-gettext-setup. The config.yaml file from locales/config.yaml should be installed in

  1   2   3   4   >