Bug#939808: exim4: Very problematic default DKIM_SIGN_HEADERS

tags #939808 upstream thanks Hi, it would probably be a good idea to discuss this with upstream. I don't think that Debian should do a local patch here. Greetings Marc On Mon, Sep 09, 2019 at 04:10:33AM +0200, Guillem Jover wrote: > The default DKIM_SIGN_HEADERS macro contains many headers

Bug#892939: 4.19.0-6

This error still exist in latest Debian Stable kernel Linux ci547 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64 GNU/Linux

Bug#939813: tasksel: selected packages marked for removal on apt full-upgrade

Package: tasksel Version: 3.53 Severity: critical Justification: breaks unrelated software Dear Maintainer, The real packages that are installed from the metapackages that tasksel uses will be marked for automatic removal after the next full system upgrade because neither the metapackages nor

Bug#807169: README.Debian / advice about plugins

Quack, First, sorry you did not get a reply at the time and thanks for your input. I think this is still relevant so I will reply. On Sun, 06 Dec 2015 13:42:33 +0100 Daniel Pocock wrote: It seems that a lot of functionality (e.g. tagging, iCalendar support) is not in Redmine itself and this

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

$ sudo systemctl status docker.service ● docker.service - Docker Application Container Engine    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)    Active: failed (Result: exit-code) since Sun 2019-09-08 21:16:42 MST; 58s ago Docs: https://docs.docker.com  

Bug#939494: xdvik-ja: Do not display \includegraphics'ed EPS

Bug #939494 can be fixed by the following patch to xdvik-ja. --- xdvik-ja-22.87.03+j1.42/texk/xdvik/psgs.c.orig 2016-07-14 20:54:54.0 +0900 +++ xdvik-ja-22.87.03+j1.42/texk/xdvik/psgs.c 2019-09-09 02:53:38.931370029 +0900 @@ -561,6 +561,11 @@ ">> setuserparams .locksafe "

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

Oops sorry about that. Sep 08 20:48:33 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Sep 08 20:48:33 life systemd[1]: Stopped Docker Application Container Engine. Sep 08 20:48:33 life systemd[1]: docker.socket: Succeeded. Sep 08 20:48:33 life systemd[1]: Closed

Bug#932168: Correct version of libc-dev not found on security.debian.org

The error I encountered was only slightly different, instead of deb9u2, I got it on deb9u3: Unable to correct missing packages. E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.9.168-1+deb9u3_amd64.deb 404 Not Found The solution I found was

Bug#939810: dkopp FTCBFS: uses the build architecture pkg-config

Source: dkopp Version: 6.5-1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs dkopp fails to cross build from source, because the upstream Makefile hard codes the build architcture pkg-config. Please consider applying the attached patch. Helmut ---

Bug#939812: ophcrack FTCBFS: uses the build architecture qmake

Source: ophcrack Version: 3.8.0-2 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs ophcrack fails to cross build from source, because it runs the build architecture qmake. When searching for qmake from autoconf, one should be using AC_PATH_TOOL to add $ac_tool_prefix, but

Bug#939811: fastqtl FTCBFS: does not pass cross tools to make

Source: fastqtl Version: 2.184+dfsg-6 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs fastqtl fails to cross build from source, because it does not pass cross tools to make. The easiest way of doing so is using dh_auto_build. Even then it continues to fail, because it invokes

Bug#848816: dgit: detect gbp export-dir configuration, and prefill build-products-dir

Hello, On Sun 08 Sep 2019 at 06:52PM +01, Ian Jackson wrote: > Sean Whitton writes ("Re: Bug#848816: dgit: detect gbp export-dir > configuration, and prefill build-products-dir"): >> I think you're right, but I think we've discussed this before. I was in >> favour of having that config

Bug#939629: links2: Problem displaying a websit

Package: links2 Version: 2.20.1-1 Followup-For: Bug #939629 Dear Maintainer, Many thanks for the reply and all you did. And thanks for Mikulas for feedback on this bug. I confirm that the solution suggested by Mikulas works properly. The page is again displayed. Do you want me t close this

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

On 9/9/19 10:49 AM, Felicia P wrote: Oops sorry about that. Sep 08 20:48:33 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Sep 08 20:48:33 life systemd[1]: Stopped Docker Application Container Engine. Sep 08 20:48:33 life systemd[1]: docker.socket:

Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected

Package: firmware-iwlwifi Version: 20190717-2 Followup-For: Bug #934781 I did some further digging - in my case, at least, the problem seems to be triggered by some relatively recent kernel change. I combed through the system journal for the last few months, and the problem first starts appearing

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

On 9/9/19 9:59 AM, Felicia P wrote:   Drop-In: /etc/systemd/system/docker.service.d    └─override.conf Please have a look at this file, you probably want to remove it. Docs:https://docs.docker.com   Process: 715918 ExecStart=/usr/sbin/dockerd -H unix:// $DOCKER_OPTS

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

Hi Arnaud I removed the custom ExecStart and attempted to restart docker.  Here is the relevant output from journalctl: Sep 08 19:04:37 life systemd[1]: Starting Docker Socket for the API. Sep 08 19:04:37 life systemd[1]: Listening on Docker Socket for the API. Sep 08 19:04:37 life systemd[1]:

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

On 9/9/19 9:06 AM, Felicia P wrote: Hi Arnaud I removed the custom ExecStart and attempted to restart docker.  Here is the relevant output from journalctl: Sep 08 19:04:37 life systemd[1]: Starting Docker Socket for the API. Sep 08 19:04:37 life systemd[1]: Listening on Docker Socket for the

Bug#938823: wicd and Python 3 (was: "wicd" utf8 and too many APs nightmare/bug)

Hi Guido, (Cc'ing the according Debian bug report #938823 to get these things documented publicly.) Guido Maria Serra wrote: > hello hello... I patched it to fully work on python3 > https://github.com/zeph/wicd ... Thanks! That was a good base to work on. > how do I package to test it on my

Bug#816693: ftp.debian.org: Please add new 'perl6' section

Hi! On Fri, 2016-03-04 at 14:02:44 +0100, Dominique Dumont wrote: > Package: ftp.debian.org > Severity: wishlist > rakudo packaging teams is packaging perl6 compiler (rakudo) and > will package several Perl6 modules packages. > > It would make sense to use a 'perl6' section for all these

Bug#939809: ftp.debian.org: Please provide more informative NEW graphs

Package: ftp.debian.org Severity: wishlist Hi! The NEW queue web page points to some graphs about the queue itself over time . The problem is that this only shows whether there's been progress as long as there has been no new uploads, or the processing

Bug#939808: exim4: Very problematic default DKIM_SIGN_HEADERS

Source: exim4 Source-Version: 4.92.2-2 Severity: important Tags: patch Hi! The default DKIM_SIGN_HEADERS macro contains many headers that make sending mails to mailing lists or (re)sending mails on someone's behalf pretty much infeasible. This has big impact on systems with strict DKIM and DMARC

Bug#939539: docker.io: Failed to start Docker Application Container Engine.

On 9/6/19 1:21 PM, Felicia wrote: Package: docker.io Version: 18.09.5+dfsg1-1 Severity: important Dear Maintainer, After a recent upgrade to linux-image-5.2.0-2-amd64 docker no longer starts with the following reported by systemd:   Hi Felicia, can you give us more logs regarding your

Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional need for --new

Hello, On Sun 08 Sep 2019 at 06:48PM +01, Ian Jackson wrote: > Sean Whitton writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention > occasional need for --new"): >> On Thu 05 Sep 2019 at 04:50PM +01, Ian Jackson wrote: >> > +=head1 GENERAL TIPS >> > + >> > +The first time a package is

Bug#939789: faketime: Fails to parse "strict" timestamps with error message "Success"(!)

Control: severity -1 minor Thanks Hello Wolfgang, thanks for your quick response! With your calls, you should not use the '-f' parameter. Without '-f', the timestamp is passed on to date/gdate for parsing, which yields the following for me on Debian Buster x86_64: That changes the behavior:

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

Package: gimp Version: 2.10.8-2+b1 Followup-For: Bug #939768 Hello, I'm also using testing (bullseye) and I can confirm this bug too. Here's what I think happened: GIMP 2.10.8-2 was built on sid (which had GEGL 0.4.12 at the time). Testing also had GEGL 0.4.12, so there was no version mismatch

Bug#939766: [pkg-cryptsetup-devel] Bug#939766: cryptsetup-initramfs: Trying to boot linux-image-5.2.0-2-amd64 fails, linux-image-4.19.0-5-amd64 works.

Control: tag -1 moreinfo Hi, On Mon, 09 Sep 2019 at 00:53:44 +0200, Alexander Brock wrote: > but on my machine there is no /bin/libc.so.[0-9.-]+ instead it is in > /usr/lib/x86_64-linux-gnu. (I assume you meant ‘/lib.*/libc\.so\.[0-9.-]+’.) How did you end up with a system where

Bug#939807: sbcl build-depends on package that is cruft in unstable and gone in testing.

Package: sbcl Version: 2:1.5.6-1 Severity: serious sbcl build-depends on texlive-generic-recommended which is no longer built by texlive-base. The old texlive-generic-recommended is still present in unstable as a cruft package, but is completely gone from testing. Please update your

Bug#433270: processing

it's been 4 years since there's been any activity on this oneis anyone still actually working on it?

Bug#677350: please accept the parenthesed syntax subject(section), e.g. man ls(1)

Control: tag -1 fixed-upstream On Sat, Apr 28, 2018 at 06:26:03AM +0800, Paul Wise wrote: > On Wed, 13 Jun 2012 12:32:04 +0100 Colin Watson wrote: > > Is it still worth it if you have to go to the effort of quoting it > > anyway? > > Yes, it is much easier to type two quote characters and paste

Bug#939096: RFS: oomd/0.1.0-1 [ITP] -- userspace Out-Of-Memory (OOM) killer for Linux systems

On Sun, Sep 8, 2019 at 9:51 PM Yangfl wrote: > https://www.debian.org/doc/debian-policy/ch-opersys.html says "The > default behaviour is to enable autostarting your package’s daemon", > IIUC. Apologies for not making it clear but my message was about the situation where a daemon needs

Bug#939717: [PATCH] Workaround invalid characters provided during installation

Hi Wolfgang, Le 08/09/2019 à 07:39, Wolfgang Schweer a écrit : > On Sat, Sep 07, 2019 at 10:36:10PM -1000, David Prévot wrote: > I've checked the patch via running 'cf-agent -I -Dinstallation,di' on > the main server. As far as I can tell, another change is needed to get a > valid workaround:

Bug#939690: libasound2-plugins:amd64: HDMI plugin missing

* Simon Richter [2019-09-07 22:53 +0200]: > Package: libasound2-plugins > Version: 1.1.8-1 > Severity: normal > > Hi, > > aplay -L reports that I have two HDMI audio channels: > > hdmi:CARD=PCH,DEV=0 > HDA Intel PCH, HDMI 0 > HDMI Audio Output > hdmi:CARD=PCH,DEV=1 > HDA Intel

Bug#939748: Additional information.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It is sad to see this. It is the same reason that I refuse to use GTK3. I hope that you can contact upstream to preserve bitmaps. Or at least compile a separate package with bitmap support. The problem is that most TrueType fonts are rendered

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

Package: gimp Version: 2.10.8-2+b1 Followup-For: Bug #939768 Dear Maintainer, * What led up to the situation? Any attempt to open or create an image file results in segmentation fault and exit from the software. * What exactly did you do (or not do) that was effective (or

Bug#939715: manual upgrades prevented

Am So., 8. Sept. 2019 um 20:21 Uhr schrieb Karsten : > > Am 08.09.19 um 19:28 schrieb Lisandro Damián Nicanor Pérez Meyer: > > Please ru it again with: > > LANG=C aptitude update > > > > And re send the output. We don't read german :-) > > > > Thanks! > > Yes - that's of course correct. > But i am

Bug#939737: emacs: please package newer release 26.3

"Héctor Orón Martínez" writes: > Package: emacs > Version: 1:26.1+1-3.3 > Severity: wishlist > > Dear Maintainer, > > Please consider packaging newer emacs 26.3 release: > https://lists.gnu.org/archive/html/emacs-devel/2019-08/msg00577.html It's in progress, but right now I'm working on

Bug#939766: cryptsetup-initramfs: Trying to boot linux-image-5.2.0-2-amd64 fails, linux-image-4.19.0-5-amd64 works.

I searched for clues why that libgcc_s.so.1 is not added and found the script: /usr/share/initramfs-tools/hooks/cryptroot it contains the line: LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" but on my machine there is no

Bug#935578: [Pkg-rust-maintainers] Bug#935578: bat: bacula-console-qt already ships /usr/sbin/bat (and /usr/share/man/man1/bat.1.gz)

Andreas Beckmann wrote on 24/08/2019: > Package: bat > Version: 0.11.0-2 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install > because it tries to overwrite other packages files. > > Since

Bug#939805: painintheapt with only pubsub configured does not work

Package: painintheapt Version: 0.20181201-1 Severity: normal Dear Maintainer, If configured with pubsub_service and pubsub_node then painintheapt prints "xep_0060" and exits with status code 1. -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500,

Bug#863920: man -d -l : too many irrelevant lines are output

Control: tag -1 fixed-upstream On Thu, Jun 01, 2017 at 11:48:38PM +, Bjarni Ingi Gislason wrote: > about the output of "man -d -l ". > > The location of the is already known. > > There are so many irrelevant lines about where the location of the input > file could be, that it makes

Bug#880380: Salsa MR

Submitted MR to salsa that should fix this. I can't reproduce the error any more after installing this fix on a server that had the issue before, though I cannot say with 100% certainty every possible way to trigger the bug are handled by these 2 backported commits.

Bug#939804: erlang: FTBFS on hppa - escript: exception error: bad argument

Source: erlang Version: 1:20.3.8.8+dfsg-1 Severity: normal Dear Maintainer, Since version 1:20.3.8.8+dfsg-1, erlang has failed to build on hppa. It fails with a bad argument exception running escript: escript /<>/lib/erl_docgen/priv/bin/github_link.escript diameter_codec.xml \

Bug#939798: floppy support in d-i [Was: Re: Bug#939798: kickseed: remove floppy support]

On 9/8/19 11:43 PM, Holger Wansing wrote: I assume, this bugreport was motivated by bug #880122 by Chris Lamb from 2017, which proposed to remove floppy support from hw-detect package, since floppies appear to no longer be widely used for ages:

Bug#936036: fd-find: shell completion does not works

On Thu, 29 Aug 2019 wrote:> Shell completion does not work (tested in zsh and bash), because of the > executable name in Debian (fdfind and not fd as in upstream). > I have completion when i type fd (which is a command not found), but nothing > with fdfind. Thanks for your report. This is easy

Bug#898949: schroot: PAM config should use common-session-noninteractive

On 07/09/2019 10:30, Simon McVittie wrote: On Thu, 17 May 2018 at 19:36:11 +0200, Ansgar Burchardt wrote: On systems with libpam-systemd installed using common-session will create a logind session which schroot should not do. In particular, creating a logind session results in

Bug#939803: RM: netanim -- RoQA; depends on qt4, unmaintained

Package: ftp.debian.org Severity: normal Please remove netanim. The package in the archive was a single upload back in 2012 and no followup to any of the bugs. Current upstream releases are compatible with Qt5, but the version in the archive still uses Qt4, which is going away. Cheers,

Bug#939770: wireshark: Wrong path in pre-install notification

Hi Justin, On Sun, Sep 8, 2019 at 11:48 PM Justin B Rye wrote: > > Balint Reczey wrote: > >> I suggest to change path in the question and make it clear that the > >> file will only exist after the package is installed – even though a > >> text mentioning it might be shown before installation is

Bug#880380: Problematic in buster

Buster ships with postgresql 11 and this problem is currently experienced in stable production systems. Although it appears upstream has fixed this by now they have never released a new version containing the fix, 2.4.0 is broken. See also a similar bug in fedora[1] and the commit references

Bug#939802: buster-pu: package guile-2.2/2.2.4+1-2

Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu This should fix the FTBFS that's already been fixed in sid. diff -Nru guile-2.2-2.2.4+1/debian/changelog guile-2.2-2.2.4+1/debian/changelog --- guile-2.2-2.2.4+1/debian/changelog

Bug#939801: xtables-addons-source: xtables-addons-2.12.0 fails to compile (kernel 5.2.0-0.bpo.2-amd64)

Package: xtables-addons-source Version: 2.12-0.1 Severity: serious Justification: Policy 4.15 Dear maintainer, whenever attempting to compile xtables-addons-dkms, the following occurs reproducibly: root@h2182426:/var/lib/dkms/xtables-addons/2.12/build# make make all-recursive make[1]:

Bug#939539: Bug 939539

I forgot to mention I also did: $ sudo apt remove --purge docker.io $ sudo rm -rf /var/lib/docker $ sudo apt install docker.io To make sure it was a clean installation 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

Bug#939797: Remove Bug 939797

Please remove this bug.  There is an option in Settings -> Configure Dolphin -> Startup -> Show filter bar which resolves this issue 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

Bug#939798: floppy support in d-i [Was: Re: Bug#939798: kickseed: remove floppy support]

Hi Adrian, John Paul Adrian Glaubitz wrote: > On 9/8/19 10:53 PM, Miguel Figueiredo wrote: > > Package: kickseed > > tags: patch > > > > in attachment, patch to remove floppy support from the kickseed package. > > Why does floppy support need to be removed? It might be usable for any of > the

Bug#939539: Bug 939539

If I run the following from the command line: $ sudo /usr/sbin/dockerd -H fd:// it produces the following output: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd According to other forum posts I've read, one recommendation was to

Bug#939770: wireshark: Wrong path in pre-install notification

Balint Reczey wrote: >> I suggest to change path in the question and make it clear that the >> file will only exist after the package is installed – even though a >> text mentioning it might be shown before installation is completed. Thanks for taking the trouble to deal with this! The patch

Bug#934665: upload grpc and protobuf to unstable

On Sun, Sep 8, 2019 at 3:03 PM Pirate Praveen wrote: > Now autopkgtest results for packages in experimental is also available. > > See https://release.debian.org/britney/pseudo-excuses-experimental.html > > Migration status for protobuf (3.6.1.3-2 to 3.9.1-2): BLOCKED: > Rejected/violates

Bug#936045: Can not reproduce anymore ...

As in the subject - my bt headset now works with 12.99.2-1. Can someone close that bug? Regards, Dietz signature.asc Description: This is a digitally signed message part.

Bug#862751: updated repository link

https://codeberg.org/themusicgod1/evacuated-babelify is available as a non-NSA/Microsoft walled garden link.

Bug#918905: logrotate fails to start becauset OVS is not started yet

Control: reassign -1 openvswitch-switch Control: notfound -1 3.14.0-4 Control: affects -1 logrotate logrotate failed cause the openvswitch postrotate invocation failed. The definition is in /etc/logrotate.d/openvswitch-switch, which is part of the package openvswitch-switch. Please share the

Bug#939698: [pkg-php-pear] Bug#939698: lintian: warning about pkg-php-tools versioned dependency conflicts with cme suggestion

On Sun, 8 Sep 2019 21:57:49 +0200 Mathieu Parent wrote: > Le dim. 8 sept. 2019 à 02:25, David Prévot a écrit : > > > > Le 07/09/2019 à 11:00, Antonio Ospite a écrit : > > > Package: lintian > > […] > > > one of my packages build-depends on pkg-php-tools, and I used to have > > > that as a

Bug#939800: librtlsdr-dev: Incomplete pkg-config file

Package: librtlsdr-dev Version: 0.6-1 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Hello Maitland, while trying to build tfrec (https://github.com/baycom/tfrec) I came across the problem that pkg-config does not provide the

Bug#939798: kickseed: remove floppy support

On 9/8/19 10:53 PM, Miguel Figueiredo wrote: Package: kickseed tags: patch in attachment, patch to remove floppy support from the kickseed package. Why does floppy support need to be removed? It might be usable for any of the architectures we use in Debian Ports like m68k or powerpc. Unless

Bug#939799: hw-detect: remove floppy support

On 9/8/19 10:56 PM, Miguel Figueiredo wrote: Package: hw-detect Version: 1.138 tags: patch in attachment, patch to remove floppy support from the hw-detect package. There is no reason to drop floppy support for loading firmware. Please keep in mind that Debian isn't an x86-only distribution.

Bug#939770: wireshark: Wrong path in pre-install notification

Control: tags -1 confirmed patch Control: found -1 1.2.9-2 Dear English Localization Team, Please review the attached patch for fixing the issue reported below. The current template can be found here: https://salsa.debian.org/debian/wireshark/blob/debian/master/debian/templates Thank you,

Bug#794410: debian-installer: Installer hangs during 'select and install software'

thank you. i had the same problem (installer always hangs during "select and install software" - around 10% of the progress) my laptop: LENOVO ideapad 100 i install in legacy mode (mbr, not UEFI). i tried with debian 8, 9 and 10: same problem. so i read the comments, and in the BIOS i put:

Bug#875184: [sofa-framework] Future Qt4 removal from Buster

On Sun, Sep 08, 2019 at 08:41:40AM +0200, Andreas Tille wrote: > On Sat, Sep 07, 2019 at 10:43:53PM +0200, Moritz Mühlenhoff wrote: > > > > The current releases on https://github.com/sofa-framework claim to be Qt5 > > compatible. Is anyone working on updating the package or should it be > >

Bug#939375: dub depends on unavailable default-d-compiler

Hi! Am Mi., 4. Sept. 2019 um 11:17 Uhr schrieb Matthias Klose : > > Package: dub > Version: 1.16.0-1 > Severity: serious > Tags: sid bullseye > > dub depends on the unavailable package default-d-compiler. Maybe that one > should > be built from the dh-dlang source. If you touch that package,

Bug#939799: hw-detect: remove floppy support

Package: hw-detect Version: 1.138 tags: patch in attachment, patch to remove floppy support from the hw-detect package. -- Best regards / Melhores cumprimentos, Miguel Figueiredo diff --git a/debian/hw-detect.templates b/debian/hw-detect.templates index c413e88e..b9854bd1 100644 ---

Bug#939798: kickseed: remove floppy support

Package: kickseed tags: patch in attachment, patch to remove floppy support from the kickseed package. -- Best regards / Melhores cumprimentos, Miguel Figueiredo diff --git a/cmdline.sh b/cmdline.sh index 72dcd72..e1e3f74 100644 --- a/cmdline.sh +++ b/cmdline.sh @@ -28,12 +28,6 @@

Bug#939797: dolphin: Filter bar always present in new Dolphin window

Package: dolphin Version: 4:18.08.0-1 Severity: minor Dear Maintainer, When a new Dolphin window is launched the filter bar is always open. If I close the filter bar and then close Dolphin, then reopen Dolphin, the filter bar is opened again. It appears that there is no way to prevent the

Bug#932379: apt-mirror doesn't grab *.xz i18n Translation files

I agree with Justin Pasher, but if you look a little lower in the text of the program "apt-mirror", you can see a similar code, but for all 3 archive formats: sub find_dep11_files_in_release ... if ( $filename =~

Bug#939740: libwxgtk3.0-gtk3-0v5: -10 is not compatible with -9 [symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in file libwx_gtk3u_core-3.0.so.0 with link time reference]

Control: tag -1 +pending On Sun, Sep 08, 2019 at 12:00:57PM +0200, Andreas Metzler wrote: > ametzler@argenau:/tmp/HUGIN$ ldd -r /usr/bin/hugin > /dev/null > symbol _ZNK8wxWindow21GetContentScaleFactorEv version WXU_3.0 not defined in > file libwx_gtk3u_core-3.0.so.0 with link time reference >

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

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] contains a branch qt5. I > tried my best to adapt cmake to finalise the

Bug#939048: transition: glibc

On 2019-09-08 22:23, Paul Gevers wrote: > Control: tags -1 confirmed > > Hi Aurelien, > > Let's have this going. Ok, I have just uploaded it. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc

Bug#849308: state of wireguard mainline inclusion?

Version: 0.0.20190905-1 Over in 849...@bugs.debian.org, Daniel Kahn Gillmor wrote: > I do plan for putting wireguard into buster-backports, since i expect > the upstream inclusion issues to be resolved one way or another by the > time of bullseye release. If anyone wants to help out by adding it

Bug#935607: lintian: classify "Starting $DESC" in init.d scripts

tags 935607 + moreinfo retitle 935607 lintian: classify "Starting $DESC" / use of $VERBOSE (etc.) in init.d scripts thanks Hi Dmitry, > When we see, which of these styles is majority, we can proclaim other > unwanted and to be fixed. ... but, unless I'm missing something you can surely do that

Bug#939768: gimp: It's the gegl mismatch...

Package: gimp Version: 2.10.8-2+b1 Followup-For: Bug #939768 Dear Maintainer, Some discussion on the GIMP IRC channel: what's your gegl version? (you can see with $ gimp -v) using GEGL version 0.4.12 (compiled against version 0.4.14) is that mismatch relevant? in this case, probably not

Bug#921017: wireguard: doesn't always set all allowed-ips

Control: tags 921017 + moreinfo unreproducible Hi Piotr-- On Thu 2019-01-31 18:15:04 +0100, Piotr Ożarowski wrote: > I have multiple peers defined in /etc/wireguard/wg0.conf > but setting AllowedIPs doesn't fully work for some of them > if I use `wg setconf`… and works perfectly fine if I do

Bug#939795: flatpak: After updating to Debian 9.10, Pithos 1.4.1 which runs as a flatpak no longer works. Keep getting 502 Bad Gateway error. If I restore back to Debian 9.9 it works fine.

On Sun, 08 Sep 2019 at 15:04:24 -0500, jtl wrote: > After updating to Debian 9.10, Pithos 1.4.1 > which runs as a flatpak no longer works. Keep getting 502 Bad Gateway > error. What do you do that results in a 502 Bad Gateway error? Updating Pithos? Running it? Something else? Where did you

Bug#875144: [qscintilla2] Future Qt4 removal from Buster

Hi, On Sat, Sep 09, 2017 at 11:07:32PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: qscintilla2 > Version: 2.9.3+dfsg-4 > 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

Bug#939048: transition: glibc

Control: tags -1 confirmed Hi Aurelien, Let's have this going. Paul @ginggs, I don't mind if you beat me to the binNMU's ;) signature.asc Description: OpenPGP digital signature

Bug#716414: ubiupdatevol: Prevent null pointer dereference

You can find a patch posted to upstream at http://lists.infradead.org/pipermail/linux-mtd/2019-September/091479.html

Bug#939741: FTBFS with OCaml 4.08.0 (safe strings)

Control: block 939741 by 897129 I agree. coq-doc acquired a new dependency in the 8.9 release, so that’ll need to get packaged first.

Bug#921962: Please remove obsolete 'xm' completion file

On Sat, 23 Feb 2019 10:52:43 -0300 "Gabriel F. T. Gomes" wrote: > > Thanks for the information. I have forwarded this upstream as > https://github.com/scop/bash-completion/pull/284 This has been integrated into bash-completion 2.9, which is now available in Debian unstable as 1:2.9-1 (not

Bug#935057: RM: afl -- ROM; upstream not actively developed anymore

It was removed two weeks ago, so it'll need to go back through New. Scott K On Sunday, September 8, 2019 4:02:17 PM EDT Paul Tagliamonte wrote: > Amazing! Thank you for your hard work and willingness to help! Very cool! > > Cc'ing ftpmaster so no one actions it while its in limbo > > Paul > >

Bug#939796: ITP: lxqt-kcm-integration -- Integration package for several KDE control modules into LXQt

Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name: lxqt-kcm-integration Version : 0.0.1 Upstream Author : Alf Gaida * URL : https://github.com/lxqt/lxqt-kcm-integration * License : (LGPL2+) Programming Lang: (desktop files) Description

Bug#939794: ghostscript breaks fig2dev autopkgtest: compare arrow tips with template failed unexpectedly

Source: ghostscript, fig2dev Control: found -1 ghostscript/9.28~~rc2~dfsg-1 Control: found -1 fig2dev/1:3.2.7a-7 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of

Bug#935057: RM: afl -- ROM; upstream not actively developed anymore

Amazing! Thank you for your hard work and willingness to help! Very cool! Cc'ing ftpmaster so no one actions it while its in limbo Paul On Sun, Sep 8, 2019, 2:39 PM Nils Dagsson Moskopp < nils+debian-report...@dieweltistgarnichtso.net> wrote: > Paul Tagliamonte writes: > > > Well, seeing as

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

On Sun, Sep 08, 2019 at 09:53:34PM +0200, Paul Gevers wrote: > Thanks for letting us know. I'll trigger a test run with lxml and crmsh > from unstable. If that succeeds as expected, than please close this bug > with the version of crmsh that fixed the issue. Will do, thanks. Did not know about

Bug#939698: [pkg-php-pear] Bug#939698: lintian: warning about pkg-php-tools versioned dependency conflicts with cme suggestion

Le dim. 8 sept. 2019 à 02:25, David Prévot a écrit : > > Le 07/09/2019 à 11:00, Antonio Ospite a écrit : > > Package: lintian > […] > > one of my packages build-depends on pkg-php-tools, and I used to have > > that as a versioned dependency, as suggested by this lintian warning: > > > > W:

Bug#934384: libvma: FTBFS: some symbols or patterns disappeared

On 10/08/2019 17:46, Niko Tyni wrote: > Source: libvma > Version: 8.8.1.really.8.7.7-1 > Severity: serious > Tags: ftbfs > > This package fails to build on current sid/amd64. > >>From my build log: > > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: > see diff output

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

On Sun, Sep 08, 2019 at 09:25:48PM +0200, Paul Gevers wrote: > Source: crmsh > Version: 4.1.0-2 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org > Tags: sid bullseye > User: debian...@lists.debian.org > Usertags: needs-update > Control: affects -1 src:lxml >

Bug#939791: [Debian-ha-maintainers] Bug#939791: crmsh: autopkgtest needs update for new version of lxml

Hi Valentin, On 08-09-2019 21:47, Valentin Vidić wrote: > Indeed, I updated crmsh to 4.1.0-3 in unstable to fix this problem > and autopkgtest is passing for unstable now. Thanks, I failed to spot that. > The only problem is > that it now needs the same version of lxml in testing to pass there.

Bug#931803: cpio -tvF

On Wed, 10 Jul 2019 23:24:43 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > > I do cpio -tvF and the screen flashes. I did not understand this bug report, nor was I able to reproduce it. Could you describe it in other words, and perhaps explain how I can reproduce it? I never saw the

Bug#935057: RM: afl -- ROM; upstream not actively developed anymore

Paul Tagliamonte writes: > Well, seeing as how Daniel Is the maintainer, perhaps one of you can take > over as maintainer and rename / reassign this bug to an adoption. > > How does that sound, all? If no one is willing, I can be a maintainer, but I have no experience. I have been asking

Bug#939789: faketime: Fails to parse "strict" timestamps with error message "Success"(!)

Hi Ben, thanks for reporting this. Please be advised that a newer release is available upstream, which however likely is not related to your issue. With your calls, you should not use the '-f' parameter. Without '-f', the timestamp is passed on to date/gdate for parsing, which yields the

Bug#939793: plplot breaks coyote autopkgtest: times out

Grr, I forgot the attachment, and I forgot that there is a transition involved. Let me run the test with coyote from unstable as the test passes there. Paul On 08-09-2019 21:34, Paul Gevers wrote: > I copied some of the output at the bottom of this report Openbox-Message: Unable to find a valid

Bug#939793: plplot breaks coyote autopkgtest: times out

Source: plplot, coyote Control: found -1 plplot/5.15.0+dfsg-3 Control: found -1 coyote/2019.02.25-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update timeout Dear maintainers, With a recent upload of

Bug#939791: crmsh: autopkgtest needs update for new version of lxml

Source: crmsh Version: 4.1.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:lxml Dear maintainers, With a recent upload of lxml the autopkgtest of crmsh

  1   2   3   >