Processed: pending

Processing control commands: > tag -1 pending Bug #936091 [src:aff4] aff4: please package new upstream release (needed by rekall), port to python3 Added tag(s) pending. -- 936091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936091 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#651313: marked as done (desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3)

Your message dated Mon, 23 Sep 2019 15:03:56 + with message-id and subject line Bug#651313: fixed in desktopnova 0.8.1-1.2 has caused the Debian Bug report #651313, regarding desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3 to be marked as done. This means that

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Mon, Sep 23, 2019 at 11:58:18AM -0400, Sam Hartman wrote: > Mark> #935910 is now fixed in apt 1.8.4 in unstable and with that > Mark> installed I can no longer reproduce #934491. The APT > Mark> maintainers have said that adding a Breaks for the fixed > Mark> version of apt is

Bug#935381: python-pyramid-multiauth: diff for NMU version 0.8.0-1.1

Control: tags 935381 + patch Control: tags 935381 + pending Dear maintainer, I've prepared an NMU for python-pyramid-multiauth (versioned as 0.8.0-1.1) and uploaded it. Regards. -- WBR, wRAR diff -Nru python-pyramid-multiauth-0.8.0/debian/changelog

Processed: python-pyramid-multiauth: diff for NMU version 0.8.0-1.1

Processing control commands: > tags 935381 + patch Bug #935381 [src:python-pyramid-multiauth] Please drop the Python 2 subpackage Bug #938090 [src:python-pyramid-multiauth] python-pyramid-multiauth: Python2 removal in sid/bullseye Added tag(s) patch. Added tag(s) patch. > tags 935381 + pending

Bug#940973: marked as done (libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember)

Your message dated Mon, 23 Sep 2019 17:05:03 + with message-id and subject line Bug#940973: fixed in libarchive-zip-perl 1.66-2 has caused the Debian Bug report #940973, regarding libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember to be

Bug#941008: loggerhead, multiple dependency issues.

On Mon, Sep 23, 2019 at 12:50:14PM +0100, peter green wrote: > Package: loggerhead > Version: 1.19~bzr479+dfsg-3 > Severity: serious > > Loggerhead has multiple dependency issues. > > The loggerhead source package build-depends on python-subunit which is no > longer built by the subunit source

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

> "Mark" == Mark Hindley writes: Mark> Julian, Mark> On Wed, Sep 11, 2019 at 02:28:55PM +0100, Mark Hindley wrote: >> > I don't think it's reasonable to ship this package with C/R/P > >> libsystemd0. >> >> I understand that you don't like it. However, for libelogind0

Bug#940973: marked as pending in libarchive-zip-perl

Control: tag -1 pending Hello, Bug #940973 in libarchive-zip-perl 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#941030: python3-os-apply-config: missing Breaks+Replaces: python-os-apply-config

Package: python3-os-apply-config Version: 10.4.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

On Mon, 23 Sep 2019 13:02:04 +0100, Chris Lamb wrote: > This has been fixed upstream here: > > https://github.com/farblos/perl-Archive-Zip/commit/b0179cbbfeb276ceac0f424d32acf56811b01568 Thanks for the analysis! I've now uploaded -2 with this patch (minus 2 not applying but irrelevant hunks)

Bug#928175: postfix: [Regression/Stretch] No more delivers mails to mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 3.1.12-0+deb9u1

On Monday, September 23, 2019 9:48:52 AM EDT Axel Beckert wrote: ... > Anyway, quite a lot might have happenend since I reported the issue > and the RRD-based monitoring logs from back then are not that fine > granulate anymore, so that I will try to upgrade again and see if the > issue arrises

Bug#938874: yum-metadata-parser: Python2 removal in sid/bullseye

On Sun, Sep 22, 2019 at 00:51:34 +0900, Kentaro Hayashi wrote: > I'm not familiar with yum-metadata-parser at all, but > I'm not willing to remove createrepo (it depends yum-metadata-parser) > So, I've tried to fix this issue by adding python3 version. Adding Python 3 support to

Bug#935381: marked as done (Please drop the Python 2 subpackage)

Your message dated Mon, 23 Sep 2019 15:50:27 + with message-id and subject line Bug#935381: fixed in python-pyramid-multiauth 0.8.0-1.1 has caused the Debian Bug report #935381, regarding Please drop the Python 2 subpackage to be marked as done. This means that you claim that the problem has

Bug#938090: marked as done (python-pyramid-multiauth: Python2 removal in sid/bullseye)

Your message dated Mon, 23 Sep 2019 15:50:27 + with message-id and subject line Bug#935381: fixed in python-pyramid-multiauth 0.8.0-1.1 has caused the Debian Bug report #935381, regarding python-pyramid-multiauth: Python2 removal in sid/bullseye to be marked as done. This means that you

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

It may be worth mentioning that Ubuntu's security team has disabled CVE-2019-14822.patch in the stable releases for now. -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj

Bug#936091: pending

Control: tag -1 pending A (Python-only) pyaff4 package has been uploaded to unstable and is waiting in NEW. See https://salsa.debian.org/pkg-security-team/pyaff4 for the corresponding Salsa repository. Cheers, -Hilko

Bug#651313: desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3

forgot to update control file and some dconf syntax changed a lot, I had to patch the patch... I hope I didn't mess up things, in case please send me an email and I'll fix it up G. diff -Nru desktopnova-0.8.1/debian/changelog desktopnova-0.8.1/debian/changelog ---

Bug#941028: python3-os-refresh-config: missing Breaks+Replaces: python-os-refresh-config

Package: python3-os-refresh-config Version: 10.1.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails

Processed: Bug#940973 marked as pending in libarchive-zip-perl

Processing control commands: > tag -1 pending Bug #940973 [src:libarchive-zip-perl, src:strip-nondeterminism] libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember Added tag(s) pending. -- 940973:

Bug#918572: check FTBFS on ppc*: test failure

Hello, Thanks for pointing out there is still the issue. I realized my test was using version 0.10.0-3 instead of 0.12.0-0.1 ! As one of the failing test: ../../tests/check_check_master.c:749:F:Core Tests:test_check_all_ftypes:125: For test 125:Simple Tests:test_ck_assert_ldouble_eq_tol

Bug#941006: FTBFS on multiple architectures

Source: spice Version: 0.14.2-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hello, It seems that spice FTBFS armel, armhf and ppc64el since 0.14.2 due to the test-qxl-parsing test This is preventing the package from migrating in

Bug#940902: doesn't read the data

Hi Ana, On Sun, Sep 22, 2019 at 11:11:47PM +0200, Ana Guerrero Lopez wrote: > > thanks a lot for thorough testing the package! > > > > The situation is as follows: Upstream is dead so we probably become > > upstream in Debian. I has done my best to port it to Python3 with the > > help of

Processed: Bug#939881 marked as pending in rabbitmq-server

Processing control commands: > tag -1 pending Bug #939881 [src:rabbitmq-server] FTBFS: trying to run :rabbitmqctl on Elixir v1.9.1 but supports only >= 1.6.6 and < 1.8.0 Added tag(s) pending. -- 939881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939881 Debian Bug Tracking System Contact

Bug#939881: marked as pending in rabbitmq-server

Control: tag -1 pending Hello, Bug #939881 in rabbitmq-server 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#940217: marked as done (suricata: missing Breaks+Replaces: suricata-update (<< 1.0.5-3))

Your message dated Mon, 23 Sep 2019 12:25:46 +0200 with message-id <40169a5a-25a4-3ff6-45fb-d7d00181c...@debian.org> and subject line Re: Bug#940217: suricata: missing Breaks+Replaces: suricata-update (<< 1.0.5-3) has caused the Debian Bug report #940217, regarding suricata: missing

Bug#939881: marked as done (FTBFS: trying to run :rabbitmqctl on Elixir v1.9.1 but supports only >= 1.6.6 and < 1.8.0)

Your message dated Mon, 23 Sep 2019 10:49:15 + with message-id and subject line Bug#939881: fixed in rabbitmq-server 3.7.18-1 has caused the Debian Bug report #939881, regarding FTBFS: trying to run :rabbitmqctl on Elixir v1.9.1 but supports only >= 1.6.6 and < 1.8.0 to be marked as done.

Bug#875207: marked as done ([tipp10] Future Qt4 removal from Buster)

Your message dated Mon, 23 Sep 2019 10:05:00 + with message-id and subject line Bug#875207: fixed in tipp10 2.1.0-3 has caused the Debian Bug report #875207, regarding [tipp10] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Sam, Many thanks for this. On Mon, Sep 23, 2019 at 11:58:18AM -0400, Sam Hartman wrote: Mark> I have tried the approach suggested by Laurent of using Mark> elogind with libsystemd0 and I could not get the sd-*(3) APIs Mark> to function correctly. > What trouble did you run into? That

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

> "Mark" == Mark Hindley writes: >> If we are going to use c/r/p libsystemd0, is there some way we >> can limit the potential damage to people who have positively >> indicated that they want to run a non-default init system? One >> of the concerns is what happens if apt

Processed: [bts-link] source package src:weechat

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:weechat > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Mon, Sep 23, 2019 at 03:03:57PM -0400, Sam Hartman wrote: > Foo-package depends on the latest libsystemd0. I'm running unstable or > testing. The latest libsystemd0 isn't building on my arch yet. But > elogind is simpler and has build fine on my arch. I install foo-package > and suddenly

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Mon, Sep 23, 2019 at 03:34:50PM -0400, Sam Hartman wrote: > Hi. > I've looked a bit at the systemd code as compared to the elogind code. > > One of the major reasons that libsystemd0 cannot be used as a > replacement for libelogind0 is that elogind does not have compatible > cgroup naming. >

Bug#934599: Quotation request

The Sales Department, Please provide us with quotation for HP Laser Toner Cartridges listed below: (6) HP 651A Black Original LaserJet Toner Cartridge, CE340A (6) HP 651A Cyan Original LaserJet Toner Cartridge, CE341A (6) HP 651A Yellow Original LaserJet Toner Cartridge, CE342A (6) HP 651A

Bug#934242: state of the crystalhd package

This is just a kind of memo for a new maintainer: *) currently the active tree is https://github.com/dbason/crystalhd - last commit was 4 Jun 2018 with a kernel module change *) a firmware-crystalhd package with bcm70012fw.bin and bcm70015fw.bin is needed in non-free for the module to work *)

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Hi. I've looked a bit at the systemd code as compared to the elogind code. One of the major reasons that libsystemd0 cannot be used as a replacement for libelogind0 is that elogind does not have compatible cgroup naming. The systemd (and elogind) libraries do some operations over dbus. But other

Bug#897675: marked as done (libtcd: not binNMU safe)

Your message dated Mon, 23 Sep 2019 19:33:57 + with message-id and subject line Bug#897675: fixed in libtcd 2.2.2-2.1 has caused the Debian Bug report #897675, regarding libtcd: not binNMU safe to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

> "Mark" == Mark Hindley writes: Mark> On Mon, Sep 23, 2019 at 03:03:57PM -0400, Sam Hartman wrote: >> Foo-package depends on the latest libsystemd0. I'm running >> unstable or testing. The latest libsystemd0 isn't building on my >> arch yet. But elogind is simpler and has

Processed: block 933645 with 939038

Processing commands for cont...@bugs.debian.org: > block 933645 with 939038 Bug #933645 [release.debian.org] transition: libvpx 933645 was not blocked by any bugs. 933645 was not blocking any bugs. Added blocking bug(s) of 933645: 939038 and 939039 > thanks Stopping processing here. Please

Bug#880154: marked as done (python-turbogears2: please provide Python3 module)

Your message dated Mon, 23 Sep 2019 21:23:10 + with message-id and subject line Bug#940921: Removed package(s) from unstable has caused the Debian Bug report #880154, regarding python-turbogears2: please provide Python3 module to be marked as done. This means that you claim that the problem

Bug#874834: marked as done ([avogadro] Future Qt4 removal from Buster)

Your message dated Mon, 23 Sep 2019 21:37:00 + with message-id and subject line Bug#941040: Removed package(s) from unstable has caused the Debian Bug report #874834, regarding [avogadro] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#875195: marked as done ([stretchplayer] Future Qt4 removal from Buster)

Your message dated Mon, 23 Sep 2019 21:37:04 + with message-id and subject line Bug#875195: fixed in stretchplayer 0.503-4 has caused the Debian Bug report #875195, regarding [stretchplayer] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has

Bug#941046: bbdb: byte-compilation and startup broken with unversioned emacs

Package: bbdb Version: 2.36-4.1 Severity: serious Justification: package does not load -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 debian/bbdb.emacsen-install was never updated for unversioned emacs. This means the package fails to byte compile, which in turn causes the startup file to bail

Processed: found 941018 in 1.5.19-4+deb10u1, found 941018 in 1.5.14-3+deb9u2, affects 941018

Processing commands for cont...@bugs.debian.org: > found 941018 1.5.19-4+deb10u1 Bug #941018 [ibus] ibus 1.5.21-1 does not work with qt5 applications Marked as found in versions ibus/1.5.19-4+deb10u1. > found 941018 1.5.14-3+deb9u2 Bug #941018 [ibus] ibus 1.5.21-1 does not work with qt5

Bug#874834: [Help] [avogadro] Future Qt4 removal from Buster

On Sun, Sep 08, 2019 at 10:32:40PM +0200, Moritz Mühlenhoff wrote: > On Wed, Dec 13, 2017 at 02:54:07PM +0100, Andreas Tille wrote: > > control: tags -1 help > > > > Hi, > > > > I've moved avogadro packaging from SVN to Git. I also had a look into > > the Qt5 migration. The Git repository[1]

Bug#916614: marked as done (mkdocs-bootswatch: Incompatible with mkdocs 0.17)

Your message dated Mon, 23 Sep 2019 21:21:49 + with message-id and subject line Bug#940923: Removed package(s) from unstable has caused the Debian Bug report #916614, regarding mkdocs-bootswatch: Incompatible with mkdocs 0.17 to be marked as done. This means that you claim that the problem

Bug#910679: marked as done (cegui-mk2 should build-depend on updated pyside-tools package)

Your message dated Mon, 23 Sep 2019 21:00:13 + with message-id and subject line Bug#910679: fixed in cegui-mk2 0.8.7-3~exp1 has caused the Debian Bug report #910679, regarding cegui-mk2 should build-depend on updated pyside-tools package to be marked as done. This means that you claim that

Bug#940166: marked as done (python-mlt: converted to Python 3 without following Python modules packaging policy)

Your message dated Mon, 23 Sep 2019 21:00:18 + with message-id and subject line Bug#940166: fixed in mlt 6.16.0-5 has caused the Debian Bug report #940166, regarding python-mlt: converted to Python 3 without following Python modules packaging policy to be marked as done. This means that you

Bug#875227: [voxbo] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:12:21PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: voxbo > Version: 1.8.5~svn1246-2 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as

Bug#940679: pandas: random test crashes

There's also a few more of these: https://salsa.debian.org/science-team/pandas/commit/c6fc5d5ccbec7ca833ca6d2556ab7013aff4b065 However, the above fix doesn't work: cdef attributes can't have default values.

Bug#941041: unbound: FTBFS with nettle 3.5.1, accesses ECC curves directly

Package: unbound Version: 1.9.3-1 Tags: upstream Severity: serious _verify_nettle_ecdsa() (in validator/val_secalgo.c) uses the addresses of nettle_secp_256r1 and nettle_secp_384r1 directly. As the comment in ecc- curve.h explains, "Due to ABI subtleties, applications should not refer to these

Processed: fixed 941046 in 3.0

Processing commands for cont...@bugs.debian.org: > fixed 941046 3.0 Bug #941046 [bbdb] bbdb: byte-compilation and startup broken with unversioned emacs Marked as fixed in versions bbdb/3.0. > thanks Stopping processing here. Please contact me if you need assistance. -- 941046:

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote: > On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote: > > Hello, > > > > When I looked I elogind a while back I was able to build a package without > > having a public libelogind0, I basically had that in my debian/rules file:

Bug#941055: dtkwm FTBFS: Project ERROR: set DTK_MODULE_NAME first

Source: dtkwm Version: 2.0.9-3 Severity: serious Tags: ftbfs dtkwm fails to build from source in unstable. A build ends with: |dh_auto_build | make -j16 | make[1]: Entering directory '/build/1st/dtkwm-2.0.9' | cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile

Bug#941057: c-t-b-mipsen tries to build targets which are not configured for this package

Package: src:cross-toolchain-base-mipsen Verson: 7 Severity: serious Tags: sid bullseye c-t-b-mipsen tries to build targets which are not configured for this package. The autopkg test is copied from the cross-toolchain-base package, and doesn't build any mips targets. The purpose of the

Bug#940983: [Pkg-rust-maintainers] Bug#940983: rust-sha-1: rebuilding results in broken dependencies.

On Sun, Sep 22, 2019 at 11:07:57PM +0100, peter green wrote: > Package: rust-sha-1 > Version: 0.8.1-2 > Severity: serious > > If rust-sha-1 is re-built, the version mentioned in virtual package names in > the provides changes from "0.4" to "0.8", but the version mentioned in the > virtual

Bug#936764: jhbuild: Python2 removal in sid/bullseye

jhbuild master now works with Python 3. There are likely still bugs as the test coverage isn't that good. ./autogen.sh --with-python=python3 The python-pygraphviz dep can be dropped, I can't find any usage of it in the code base.

Bug#940992: firefoxdriver: does not work with firefox > 47 at all

Package: firefoxdriver Version: 3.14.1-1 Severity: grave Justification: unusable by everyone This is what happens when you try to use firefoxdriver in the most obvious way from python on buster: | $ dpkg -l python3-selenium | ... | ii python3-selenium 3.14.1+dfsg1-1 all Python3

Bug#875207: [tipp10] Future Qt4 removal from Buster

Hi Reiner, Am 21.09.19 um 00:45 schrieb Reiner Herrmann: > I attached a patch that builds tipp10 with Qt5. > I tested building with pbuilder and did a few tests of the program, > and it looks to me like everything is working. This is great news. > As porting the download modules would have been

Bug#928175: postfix: [Regression/Stretch] No more delivers mails to mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 3.1.12-0+deb9u1

Hi Scott, thanks for having a look at this. Scott Kitterman wrote: > I'm unable to explain this either. The behavior of message_size_limit = 0 is > undocumented Oh, ok. > (and was changed in 3.4 because of problems it was causing). Ok, so this change is not yet in there. > What's your

Bug#941008: loggerhead, multiple dependency issues.

Package: loggerhead Version: 1.19~bzr479+dfsg-3 Severity: serious Loggerhead has multiple dependency issues. The loggerhead source package build-depends on python-subunit which is no longer built by the subunit source package. The loggerhead source package build-depends on python-bzrlib.tests

Processed: Re: Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

Processing commands for cont...@bugs.debian.org: > notfound 940973 strip-nondeterminism/1.6.0-1 Bug #940973 [src:libarchive-zip-perl, src:strip-nondeterminism] libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember No longer marked as found in

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

This is a regression due to the fix of , i.e. this commit: https://salsa.debian.org/debian/ibus/commit/76df93dc Also reported upstream: https://github.com/ibus/ibus/issues/2137 And in Ubuntu: https://launchpad.net/bugs/1844853 -- Gunnar Hjalmarsson

Bug#928175: Forgot the attachement

Forgot the attachement. Here it is. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486

Bug#928175: postfix: [Regression/Stretch] No more delivers mails to mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 3.1.12-0+deb9u1

Hi Scott, Scott Kitterman wrote: > > procmail itself has last been updated with the dist-upgrade of that box > > from Jessie to Stretch. [...] > Since we've failed to find a likely culprit in postfix and these are procmail > errors relating possibly to file sytem issues, is there any chance of a

Bug#940963: [Pkg-samba-maint] Bug#940963: samba doesn't start anymore

Le dim. 22 sept. 2019 à 19:27, Elimar Riesebieter a écrit : > > Control: severity -1 grave > Control: reassign -1 samba-common-bin > > * Elimar Riesebieter [2019-09-22 13:00 +0200]: > > > Package: samba > > Version: 2:4.10.8+dfsg-1 > > Severity: normal > > > > > > This server runs sysvinit! > >

Bug#928175: postfix: [Regression/Stretch] No more delivers mails to mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 3.1.12-0+deb9u1

On Mon, 29 Apr 2019 14:46:18 +0200 Axel Beckert wrote: > Package: postfix > Version: 3.1.12-0+deb9u1 > Severity: grave > Affects: procmail > Justfication: causes data loss (after a few days), breaks (more or less) unrelated packages (procmail) > > Dear Debian Postfix Maintainers, > >* What

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

Package: ibus Version: 1.5.21-1 Severity: serious After upgrading from 1.5.19-4 to 1.5.21-1 all may qt5 ibus stop working with ibus (for example anki, kate, konsole, ...). If one switches to say chinese, nothing happens , the default keyboard remains to input method. Switching input method in

Processed: Re: desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3

Processing control commands: > tags -1 patch pending Bug #651313 [desktopnova-module-gnome] desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3 Added tag(s) pending. -- 651313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651313 Debian Bug Tracking System Contact

Bug#651313: desktopnova-module-gnome: desktopnova seems to be not compatible with Gnome 3

control: tags -1 patch pending Lets do it G. On Tue, 08 Jan 2013 16:46:24 +0100 Andrea Capriotti wrote: > Hi, > > there's a patch (attached) for that and it works: > > https://bugs.launchpad.net/desktopnova/+bug/780079 > > I did a backport for Debian unstable version of desktopnova (0.8.1):

Bug#940992: firefoxdriver: does not work with firefox > 47 at all

Hi, the error below does not depend to firefox driver. The firefoxdriver ist a leftover for older firefox versions. The package documentation[3] describes how to enable the geckodriver and there is a bug[1] (#874207) filed for firefox too. The packge firefoxdriver will be removed with the next

Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

Control: tags -1 + confirmed Control: forwarded -1 https://github.com/ibus/ibus/issues/2137 Indeed a regression. Thanks, Boyuan Yang 在 2019-09-23一的 15:29 +0200，Gunnar Hjalmarsson写道： > This is a regression due to the fix of ;, > i.e. this commit: > >

Processed: Re: Bug#941018: ibus 1.5.21-1 does not work with qt5 applications

Processing control commands: > tags -1 + confirmed Bug #941018 [ibus] ibus 1.5.21-1 does not work with qt5 applications Added tag(s) confirmed. > forwarded -1 https://github.com/ibus/ibus/issues/2137 Bug #941018 [ibus] ibus 1.5.21-1 does not work with qt5 applications Set Bug forwarded-to-address

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

notfound 940973 strip-nondeterminism/1.6.0-1 affects 940973 + strip-nondeterminism tags 940973 + fixed-upstream forwarded 940973 https://github.com/redhotpenguin/perl-Archive-Zip/issues/51 thanks Chris Lamb wrote: > Will investigate soon. This appears to be happening as libarchive-zip-perl 1.66

Bug#940963: [Pkg-samba-maint] Bug#940963: Bug#940963: samba doesn't start anymore

Hai, If people want a temporary fix for this one. Add my repo for 4.10 (builded for buster) wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add - echo "deb http://apt.van-belle.nl/debian buster-samba410 main contrib non-free" | sudo tee -a

Bug#940127: ghostscript makes c2esp autopkgtest timeout

On 22/09/2019 13:25, Brian Potkin wrote: Would this do? cat /usr/share/cups/data/form_russian.pdf | gs -dQUIET -dPARANOIDSAFER -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=cups -r600x600 -dDEVICEWIDTHPOINTS=595