Bug#1067661: condor: unable to install condor on armhf in Ubuntu

My apologies. I cut and pasted the wrong bug number. However, thank you for the patch. I have included it in the upcoming 23.6.2 release in Debian. I have also incorporated this patch upstream. -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for

Bug#887139: d-i daily 2018-01-14 amd64 damages UEFI setup on Fujitsu Lifebook AH532

A kernel-based workaround for the underlying issue has now landed in all currently supported linux-stable branches: linux-6.8: 6.8-rc7 (f45812cc23fb74bef62d4eb8a69fe7218f4b9f2a) linux-6.7: 6.7.9(cbf12e716a52d260fabecdca7d5f6e7cd07aed6c) linux-6.6: 6.6.21

Bug#887139: d-i daily 2018-01-14 amd64 damages UEFI setup on Fujitsu Lifebook AH532

On Sun, 14 Jan 2018 13:38:11 +0100 Karsten Merker wrote: Machine: Fujitsu Lifebook AH532, first version (with BIOS version 1.09) [...] How can one bring the NVRAM back into a sane state that allows getting into the setup and booting from external devices? I personally had luck with doing a

Bug#1057843: Guidelines for affected users

anyone who last updated 3 weeks ago would have encountered, nor in the current bookworm-security version. -- Tim Connors

Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

I haven't been able to reproduce this on a Debian 12 container. For those that are still seeing this problem, is it always reproducible? If there is a race, is there a way to force this (e.g. via apt settings or manual package install ordering with dpkg etc.)? Thanks, Tim.

Bug#1033231: fixed in postgrey 1.37-2

Hello! After a little testing i can confirm that postgrey is installed fine: The user is created with uid=119 and gid=130, /etc/postgrey contains the files whitelist_clients and whitelist_recipients and the daemon seems to be running fine. Thanks a lot! Cheers, tim Tested version: 1.37-2

Bug#1033678: installation-reports: Unbootable install: MBR partition unusable with UEFI

On 3/29/2023 6:21 PM, Dima Kogan wrote: Package: installation-reports Severity: grave Hi. I just installed a bookworm candidate. This worked OK through partitioning and reboot, but I cannot boot into the system. This is an amd64 recent-ish laptop. The disk is a PCIe SSD, not SATA. I'm

Bug#1031179: Acknowledgement (libzvbi-dev: libzvbi.h unusable - missing version.h include)

Upstream issue: https://github.com/zapping-vbi/zvbi/issues/40

Bug#1031179: libzvbi-dev: libzvbi.h unusable - missing version.h include

Package: libzvbi-dev Version: 0.2.40-1 Severity: grave Tags: upstream Justification: renders package unusable Trying to build GStreamer (gst-plugins-bad) against the latest version results in In file included from ../subprojects/gst-plugins-bad/ext/teletextdec/gstteletextdec.h:26,

Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

ut the few remaining changed files. Regards, Tim OpenPGP_signature Description: OpenPGP digital signature

Bug#1019865: evolution Hangs and goes to 100% CPU usage on compose

Am Sonntag, dem 15.01.2023 um 13:10 -0500 schrieb Jeremy Bicha: > On Sun, Dec 11, 2022 at 9:29 AM Jeremy Bicha > wrote: > > Could y'all verify whether you still have this issue? > > > > Please upgrade to Evolution 3.46.2 which just landed in Testing > > today. > > Please log out and log back in

Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Hi Lucas, maybe @dkg has time to update the packaging ? Regards, Tim On 14.01.23 23:51, Lucas Nussbaum wrote: Hi Tim, I can't find that new version (0.21.2) in Debian? Lucas On 14/01/23 at 20:19 +0100, Tim Rühsen wrote: Hey Lucas, could you try with the latest release v0.21.2 ? I am

Bug#1028857: libpsl: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Hey Lucas, could you try with the latest release v0.21.2 ? I am working on Debian sid, and can't reproduce the issue. But I will examine the logs and/or try to build from the debian sources (in the next days). Regards, Tim On 14.01.23 13:59, Lucas Nussbaum wrote: Source: libpsl Version

Bug#1012428: gnome-shell-common: drmModeAddFB2WithModifiers Failed

Hi Jeremy, I am not, I switched to Mate for a desktop and they have gone away. Thanks! Tim McConnell On Sun, 2022-12-11 at 09:40 -0500, Jeremy Bicha wrote: > Many things have changed in Debian in the past 6 months. Are you > still > experiencing this issue? > > Thank you,

Bug#1019865: Hangs and goes to 100% CPU usage on compose

I am observing the same behaviour, but only when I click the request read receipt option. Do you guys maybe have the option to always request a read receipt turned on?

Bug#1017944: Doesn't affect buster

Guess we're finding out where everyone's update windows are. Some though may report before resolving the issue or somewhat after. Or people may not have noticed yet if they haven't rebooted or attempted to start a new guest. It doesn't affect buster hosts. bullseye is impacted.

Bug#1014435: libvirt-daemon-system-systemd: virbr0 default fails to connect

Package: libvirt-daemon-system-systemd Version: 8.4.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, Virbr0 won't connect to external network.It did once, I was able to install Debian from a net install image. Now it tells me the

Bug#1014189: devhelp: can't launch DevHelp GUI

Package: devhelp Version: 41.2-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, What led up to the situation?Attempt to launch Dev Help from Icon or via command line. What exactly did you do (or not do) that was effective (or

Bug#1012428: gnome-shell-common: drmModeAddFB2WithModifiers Failed

Package: gnome-shell-common Version: 42.1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, What led up to the situation? Do not know, my logs are getting multiple reports of this error(?) What exactly did you do (or not do) that

Bug#1010771: suricata: recieve erros after adding rule list

Package: suricata Version: 1:6.0.5-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: tmcconnell...@gmail.com Dear Maintainer, What led up to the situation? Followed the instructions from suricata.readthedocs.io to add rules for the IDS What exactly did you do (or not do)

Bug#995838: [htcondor-debian] Bug#995838: Should condor be removed?

I have a build of the recent 9.0.7 release. I want to run it through our integration tests before uploading later this week. ...Tim -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences Univer

Bug#995838: [htcondor-debian] Bug#995838: Should condor be removed?

I plan to upload a new version this weekend. -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 5

Bug#997031: nvidia-cuda-gdb: buster-backports /usr/bin/cuda-gdb 'Segmentation fault' at startup

Package: nvidia-cuda-gdb Version: 11.2.152~11.2.2-2~bpo10+1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: 10.11 APT prefers oldstable-updates APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (500, 'oldoldstable') Architecture:

Bug#990069: Still broken in ssh 8.4p1-5, libc6 2.31-13

1 2020 /etc/init.d/ssh -rwxr-xr-x 1 root root 4056 Mar 13 2021 /etc/init.d/ssh.dpkg-new and ssh isn't yet started - I did that manually because I knew the problem was going to arise. -- Tim Connors

Bug#994033: mpd: Fails to find ldd libraries from libraspberrypi0 that have moved

Package: mpd Version: 0.22.6-1 Severity: grave Justification: renders package unusable Dear Maintainer, AN upgrade to rasbian stable ahs moved some ldd files included in the libraspberrypi0 packages and now mpd fails to start. OK# ldd /usr/bin/mpd | grep -w not | cat libvchiq_arm.so => not

Bug#993147: libstatgrab FTBFS: ./configure: line 7892: syntax error near unexpected token `ac_fn_check_decl'

This is fixed in libstatgrab 0.92.1: https://github.com/libstatgrab/libstatgrab/releases/tag/LIBSTATGRAB_0_92_1 Or this specific patch should fix it too: https://github.com/libstatgrab/libstatgrab/commit/1205aed6593b83f69297512b89c7813d77be89d4 Tim. On Fri, Aug 27, 2021 at 11:34:36PM +0200

Bug#968747: vim-gtk3: vim (when linked to vim-gtk3 or vim-nox) fails to start due to undefined symbol

Package: vim-gtk3 Version: 2:8.2.0716-3 Severity: grave Justification: renders package unusable After dist-upgrading Debian testing to bullseye/sid, vim/ex/gvim/etc. no longer started: vim: symbol lookup error: /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0: undefined symbol: XML_SetHashSalt A

Bug#961438: Fix for: grcompiler FTBFS on i386: compare_PigLatinTest_v2 failed

A fix for this bug is in upstream commit a9e6dec <https://github.com/silnrsi/grcompiler/commit/a9e6dec71cbc11c5d637fa342e51867330001862>, and has been tested against 32 and 64 bit xenial boxes which were both exhibiting the same bug described here. -- Tim Eves Writing Systems Technology

Bug#961444: Fix for grcompiler FTBFS on architectures where char is unsigned

the -128 <->127 range. -- Tim Eves Writing Systems Technology - SIL International

Bug#961445: Fixes in upstream repo commits.

have tested this on on 32bit emulated MIPS system running Debian 10 and it passes all the regression tests. -- Tim Eves Writing Systems Technology - SIL International

Bug#950168: pstack always fails with "crawl: Input/output error"

int why it may fail on amd64 and not on x86 here. Regards, Tim signature.asc Description: OpenPGP digital signature

Bug#950168: pstack always fails with "crawl: Input/output error"

(errno is 5). strace and gdb work well. Web searches so far didn't help. Any ideas / hints ? Regards, Tim -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386

Bug#948283: tinyproxy: If no PidFile is configured logrotate will change the owner of the root directory

case. It was a nasty surprise, because it didn't happen immediately after the configuration change, but with a bit of delay. Best regards Tim Düsterhus

Bug#948283: tinyproxy: If no PidFile is configured logrotate will change the owner of the root directory

t be fully exploitable by the `tinyproxy` user it breaks systemd-tmpfiles: Jan 06 01:57:53 debian-2gb-fsn1-1 systemd-tmpfiles[282]: Detected unsafe path transition / → /var during canonicalization of /var. Thus I feel the severity of `critical` is justified for this bug report. Best regards Tim

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

On 3/17/19 11:11 PM, Daniel Kahn Gillmor wrote: > On Sun 2019-03-17 13:14:54 +0100, Tim Rühsen wrote: >> Fixed it by building my own libiconv on MinGW systems. It really is >> straight forward and possibly no extra Debian package is needed. > > Thanks for the feedback, Tim.

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

Fixed it by building my own libiconv on MinGW systems. It really is straight forward and possibly no extra Debian package is needed. Regards, Tim On Sat, 16 Mar 2019 21:02:26 +0100 =?UTF-8?Q?Tim_R=c3=bchsen?= wrote: > Please do not remove this package, the first CI builds (MinGW cross >

Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

Please do not remove this package, the first CI builds (MinGW cross builds) already break (GNU Wget / Wget2). Well, it's already gone from buster... please add it back or provide a another way to convert charsets within cross-compiled Windows executables. Regards, Tim signature.asc

Bug#917898: libvisual-0.4-dev: Broken include path in pkg-config file

pkg-config (e.g. gst-plugins-base) to FTBFS. Cheers Tim -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8

Bug#908800: Bug #908800 in tracker marked as pending

Control: tag -1 pending Hello, Bug #908800 in tracker 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#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

back to true; then I installed your latest package, and it seems to work fine! Thanks for all your patient work on this. Tim <><

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

. When I switched javascript.options.baselinejit back to true, Firefox instantly crashed. (But, of course, it's recoverable again via -safe-mode.) Setting only javascript.options.ion back to true *doesn't* crash Firefox, or prevent it from starting. Tim <><

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

, but I did it again today, and the most recent file in that directory contains just the line: Crash ID: bp-a47d7854-9ea2-4c6b-b432-4b98e0180918 Is that what you're looking for? Tim <><

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

file. Where is it meant to be? Tim <><

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

anks Mike Cheers, Tim <><

Bug#908449: firefox-esr_60.2.0esr-1~deb9u2.1_i386.deb not working

ore information. Tim <><

Bug#907363: src:mozjs52: FTBFS on i386: various test failures

On 10/09/18 20:46, Simon McVittie wrote: > Maybe compiling with -ffloat-store and/or -fexcess-precision=standard > would help? firefox-esr seems to be compiled to assume SSE2, which is > itself a RC bug (#908396) but might have been used to address this. > > I have tried building with various

Bug#907896: tracker-miners FTBFS in autopkgtest with latest glib2.0

This test failure seems to be specific to the schroot environment. I cannot reproduce outside of a schroot. Glib mime-type detection is failing, as its unable to locate/open the test file, when calling get_content_type().

Bug#907896: tracker-miners FTBFS in autopkgtest with latest glib2.0

I think it might be better to just write some random text to the test file, so that all versions of glib continue to return "text/plain". Just checking that with upstream, but can prepare a patch.

Bug#894282: openssl: Missing quotes in c_rehash

This also affects the build currently in experimental. Which is breaking my experimental sbuild chroots. Can the patch be uploaded there also.

Bug#881915: libidn FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available

I can make up a new upstream release. Let me know if there is something that should be applied before. With Best Regards, Tim signature.asc Description: OpenPGP digital signature

Bug#785782: False sighting (will re-close) - problem was actually an invisible primary display

OK it turned out the gmd3 login prompt dialog wasn't actually absent... the issue was due to my install actually thinking the machine had two heads, when it didn't (7700K i7; CPU's integrated graphics on an Asrock H270 Pro4 mobo, one monitor attached to VGA port... but the freshly installed system

Bug#785782: Issue re-sighted: gdm3 starts but no login prompt after fresh installs

t else you want/need to see/try... For now I'm switching to lightdm (which does put up a useful login prompt) but I can easily hop back to gdm3 to try things. Tim

Bug#868905: [htcondor-debian] Bug#868905:

Hi Michael, I incorporated your patch into the Debian build. I am currently waiting for my upload to be accepted into sid. Thank you, ...Tim On 07/25/2017 08:48 PM, Michael Hudson-Doyle wrote: > I fixed this in Ubuntu with this pa

Bug#870316: sawfish-merlin-ugliness: almost completely broken after upgrade to stretch

lly happened a long time ago upstream.) I assume this causes the loading of merlin.uglicon in ugliness.jl to fail, losing that file's functionality too. The attached patch seems to fix it. Tim Bagot -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable'), (

Bug#868905: [htcondor-debian] Bug#868905:

Hi Michael, Could you send the patch the me directly? The bug tracking system apparently stripped the patch from the message. Thank you for looking into this. I was about to start working on this problem. I'd like to get this resolved soon. ...Tim On 07/25/2017 08:48 PM, Michael Hudson-Doyle

Bug#864377: docker.io: Failure to install (cannot start daemon)

configure docker.io: apt-get --with-new-pkgs -f upgrade Regards, Tim signature.asc Description: OpenPGP digital signature

Bug#864377: docker.io: Failure to install (cannot start daemon)

Just an idea... aufs too old (not matching the kernel version) ? # uname -a Linux blitz-lx 4.11.0-1-amd64 #1 SMP Debian 4.11.6-1 (2017-06-19) x86_64 GNU/Linux # dpkg -l '*aufs*' un aufs-dev (no description available) ii aufs-dkms

Bug#864377: docker.io: Failure to install (cannot start daemon)

On Mon, 26 Jun 2017 17:37:48 -0400 Antoine Beaupre wrote: > Control: notfound -1 1.13.1~ds1-2 > Control: tags -1 unreproducible > > Similarly: I installed 1.13.1~ds1-2 from sid on stretch and it installs > fine. > > Any more details on how to reproduce this? Which init

Bug#853258: docker.io: uses sleep to query user in maintainer script

see what other packages like mysql does with the potential to delete user data as Antoine says. Tag: +more_research_required Tim. signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#860446: gravit segmentation violation

not architecture specific? Nils: can I check which graphics drivers you are using, in case it is relevant? Meanwhile someone should try running gravit on another i386 system... -- Tim Retout <dioc...@debian.org>

Bug#860011: spim: diff for NMU version 8.0+dfsg-6.1

Please find attached the NMU diff for spim 8.0+dfsg-6.1, which I have uploaded as a zero-day NMU, as per devref 5.11.1: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu-guidelines Kind regards, -- Tim Retout <dioc...@debian.org> diff -Nru spim-8.0+dfsg/debian/cha

Bug#860011: xspim

a more recent version of flex. -- Tim Retout <dioc...@debian.org>

Bug#859262: synaptic + orca going silent

ing via "Mark all upgrades"; I didn't seem to have the same problems when just installing a new package. I'm attaching a log with various error messages that orca printed to the console; sorry I've not narrowed it down further yet! Hope that helps, -- Tim Retout <dioc...@debian.

Bug#860011: xspim

e at least the CLI program still works... -- Tim Retout <t...@retout.co.uk>

Bug#856024: armhf bootstrap + molly-guard

don't think there's anything specifically wrong with how molly-guard is using dpkg-divert, so I'm merging this bug in with the relevant multistrap bug (#591518). Hope that's all right. Kind regards, On 18 April 2017 at 15:28, Tim Retout <dioc...@debian.org> wrote: > tags 856024 - unrep

Bug#856024: armhf bootstrap + molly-guard

there a step in your install process where preinst scripts get run? If this is the issue, I'm now trying to work out what to do about it... the preinst does seem to be the right place according to Policy Appendix G. Kind regards, -- Tim Retout <dioc...@debian.org> config Description: Binary data

Bug#856024: armhf bootstrap + molly-guard

ssage "also in package molly-guard 0.6.4"). For any recently-installed stretch system, molly-guard should definitely have been using diversions. -- Tim Retout <dioc...@debian.org>

Bug#856024: armhf bootstrap + molly-guard

(?), because systemd-sysv should not otherwise complain that molly-guard installed /sbin/halt. I'm wondering if there's something specific to armhf (seems unlikely) or the particular bootstrap process. Kind regards, -- Tim Retout <dioc...@debian.org>

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

On 30 Mar 2017, at 3:54 AM, Michael Stapelberg <stapelb...@debian.org> wrote: > > Hi Tim, > > "Potter, Tim" <timothy.pot...@hpe.com> writes: >> Hi Ricardo. Thanks for the bug report. I messed up by uploading some of >> the Docker 1.13 >> d

Bug#857842: [pkg-go] Bug#857842: Fails to build -- test errors

causes it to fail for me when building inside Docker so I need to run pbuilder on bare metal. Tim. signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#857953: bash: debian/rules execute $(STRIP) even when empty

ild -b -uc -us $(DEB_BUILD_OPTIONS) is empty by default here. Regards, Tim -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cor

Bug#856705: [dko...@debian.org: Bug#856705: graywolf: License violation]

svd_solve, and then freed. ---Tim ++-+ | R. Timothy Edwards (Tim) | email: t...@opencircuitdesign.com| | Open Circuit Design| web: http://opencircuitdesign.com | | 19412

Bug#854548: still not fixed: Correction

xrdp-sesman is starting, but xrdp fails to start and automatically stops xrdp-sesman. output of journalctl -xn is: Failed at step RUNTIME_DIRECTORY spawning /usr/sbin/xrdp-sesman: File exists Actually, "socksetup" is now called more than once, which could be avoided by removing one line from

Bug#854548: still not fixed

I believe the bug is not yet fixed. xrdp-service is now starting, but starting xrdp leads to an error. Proposed fix is to remove the line "RuntimeDirectory=xrdp" from xrdp.service: --- a/instfiles/xrdp.service +++ b/instfiles/xrdp.service @@ -7,7 +7,6 @@ After=network.target xrdp-sesman.service

Bug#855407: docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1)

lines to avoid this happening until Docker 1.13 hits unstable. Regards, Tim. > On 18 Feb 2017, at 2:36 AM, Roland Kammerer <dev@gmail.com> wrote: > > Package: docker.io > Version: 1.11.2~ds1-6 > Severity: grave > Justification: renders package unusable > &g

Bug#855922: [pkg-go] Bug#855922: containerd: 0.2.3 ds1-1 breaks docker 1.11 - unable to start containerd

erimental - my apologies. I've done a new upload with a Breaks line to avoid this bug occurring until I finish testing 1.13 and uploading to unstable. Regards, Tim. > > > > -- System Information: > Debian Release: 9.0 > APT prefers unstable > APT policy: (500, 'un

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

On 18 Feb 2017, at 5:33 AM, Evgeni Golov <evg...@debian.org> wrote: > > Hi Tim, > > On Wed, Feb 15, 2017 at 10:52:22PM +, Potter, Tim wrote: >>> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me. >> >> Hi everyone. This uploa

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

On 16 Feb 2017, at 9:56 AM, Chris Lamb <la...@debian.org> wrote: > > Potter, Tim wrote: > >> On 16 Feb 2017, at 9:06 AM, Chris Lamb <la...@debian.org> wrote: > >> Hi everyone. This upload is part of updated build dependencies for Docker >> 1.13.0.

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

ibnetwork all are tightly coupled and need to be upgrade in lockstep to avoid build failures which unfortunately is hard to achieve in practice. I'm hoping that once 1.13 is in unstable I can keep it up to date incrementally instead of having to spend months going

Bug#852418: libpsl5 (runtime library) depends against -dev package

I am the package maintainer, but can't upload. Does creating a new version (on collab-maint/libpsl) help, or should we wait until Daniel (uploader) is awake (maybe ~3-4 hours from now, but no promise). Sorry, but I am somewhat inexperienced regarding this situation. Regards, Tim On Tuesday

Bug#847997: [pkg-go] Bug#847997: golang-github-jessevdk-go-flags-dev: Cannot be co-installed golang-go-flags-dev

> On 14 Dec 2016, at 4:38 AM, Hilko Bengen <ben...@debian.org> wrote: > > Hi Tim, > >> I think I'll probably ask the FTP Masters very nicely to remove the >> new package rather than mess with the reverse dependencies. > > Keep in mind that golang-go-flag

Bug#847997: [pkg-go] Bug#847997: golang-github-jessevdk-go-flags-dev: Cannot bo co-installed golang-go-flags-dev

. Regards, Tim. On 13 Dec 2016, at 10:43 AM, Hilko Bengen <ben...@debian.org> wrote: > > Package: golang-github-jessevdk-go-flags-dev > Version: 1.1-1 > Severity: grave > Control: tag -1 patch > > Dear Maintainer, > > when trying to install golang-gi

Bug#828269: [htcondor-debian] Bug#828269: Info from upstream

on December 1st. Let me know if you need anything more, ...Tim On 11/04/2016 06:31 AM, Michael Hanke wrote: > Relaying information from upstream's triaging: > > > > I concluded that the problem was not with HTCondor. It had to do with the > following packages: libglo

Bug#844285: pidgin: steals (warps) mouse cursor (not just focus) when new message comes in [SEC=UNCLASSIFIED]

Package: pidgin Version: 2.11.0-0+deb8u1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, Like bugs #399786 and #518339, the mouse is warped to an open conversation window when a new message comes into that conversation. Typing a password at the time, and your

Bug#837402: [htcondor-debian] Bug#837402: Fix for the Condor PIE FTBFS

Hello, Thank you for this fix. We needed to add -fnoPIC because of the severe performance impact on the benchmarks. Adding the -fPIE as well has a minimal performance impact. I will apply this patch to our upstream sources. ...Tim On 11/04/2016 06:14 AM, Adrian Bunk wrote: Control: tags -1

Bug#837940: gnome-twitch-player-backend-mpv-opengl: immediate segmentation fault

t the segfault happens directly on selecting the backend, not on playback, is that correct? Were you selecting it from the settings dialog[1] outside of a stream, or when you were prompted to select one when trying to watch a stream? Does the same happen when you try the other one of the two methods

Bug#837940: gnome-twitch-player-backend-mpv-opengl: immediate segmentation fault

prompted to select one when trying to watch a stream? Does the same happen when you try the other one of the two methods? Sincerely, Tim Dengel [1] You can reach that dialog by clicking on the "gnome-twitch" item in gnome's "task bar" and then selecting "settings"

Bug#835360: rkt: FTBFS on several architectures

building on all architectures pretty soon. Tim. [1] https://github.com/coreos/rkt/blob/v1.14.0/configure.ac#L49 [2] https://golang.org/doc/go1.7 signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#835698: [pkg-go] Bug#835698: golang-x-text: FTBFS: dh_auto_test: go test -v -p 1 golang.org/x/text golang.org/x/text/cases golang.org/x/text/collate golang.org/x/text/collate/build golang.org/x/te

This was fixed by a recent upload of version 0.0~git20160816.0.d69c40b-1 but this bug wasn't closed in d/changelog. Tim. On 28 Aug 2016, at 8:24 PM, Lucas Nussbaum <lu...@debian.org> wrote: > > Source: golang-x-text > Version: 0.0~git20160606.0.a4d77b4-1 > Severity: serio

Bug#830729: [pkg-go] Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

On 2 Aug 2016, at 4:22 AM, Tianon Gravi <tia...@debian.org> wrote: > > On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support) > <timothy.pot...@hpe.com> wrote: >> Patch attached to fix this, but it's a bit icky (and has been replaced by a >> shell out to

Bug#830729: [pkg-go] Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

her means. > cmd := exec.Command("sh", "-c", "eval echo ~$USER") Patch attached to fix this, but it's a bit icky (and has been replaced by a shell out to call getent in a later version. Tim. 830729-golang-github-mitchellh-go-homedir.patch Description: Binary data signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#830519: [pkg-go] Bug#830519: docker-swarm: FTBFS: docker/swarm/api/flusher.go:8:2: cannot find package "github.com/docker/docker/pkg/ioutils"

Rebuilds cleanly now so closing this bug. Tim. signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#820249: [pkg-go] Bug#820249: Please switch from softhsm to softhsm2

I've just pushed a patch for this to the package repository on alioth. Tim. signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#830119: akonadi-server: Akonadi fails to start after upgrade

Package: akonadi-server Version: 4:16.04.2-3 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrading this morning, Kmail shows an empty window while being busy with something. $ akonadictl restart ... ProcessControl: Application

Bug#801247: pinentry-gnome3: No PIN dialog

ts. I suppose the fix would involve either pinentry-gnome3 getting the dbus session from the X session in some way (if that's possible), or extending the functionality of "updatestartuptty" to also update dbus session used by gpg-agent when starting the pinentry command. Cheers,

Bug#815319: Fix for upgrade process

Ignore my previous message -- Seems my testing was done with INTERFACES being set in /etc/defaults/isc-dhcp-server... (whoops!) After reverting my configs/init.d scripts to the originals, and more thorough testing, I've determined adding the below code in /etc/init.d/isc-dhcp-server after

Bug#815319: Fix for upgrade process

I believe the broken upgrade is due to a scoping issue when $INTERFACESv4 isn't defined in /etc/defaults/isc-dhcp-server ($DHCPD_DEFAULT). To fix the upgrade process an update is needed to the /etc/init.d/isc-dhcp-server file on 4.3.4-1 to define $INTERFACESv4 before sourcing $DHCPD_DEFAULT,

Bug#824855: irony-mode: Unable to load irony-mode

l below. Critically, this is the change: (autoload 'irony-mode "irony" ; <-- used to be "irony-mode" here "Minor mode for clang based C/C++ completion." t) Kind regards, Tim. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy

Bug#820149: [#820149] Fixed by uploading newer upstream version

This FTBFS should be fixed by the upload of the newer version in #812838. Tim. signature.asc Description: Message signed with OpenPGP using GPGMail

Bug#734688: Logs are not rotated for a month

inds a base file whose .gz already exists, recursively call itself again to start rotating down to the current file, which can then be compressed and resume where we were? Sorry no patches, already after my bedtime, and this has already been languishing in my todo list for a couple of weeks. -- Tim Connors

  1   2   3   4   5   6   7   >