Bug#1101090: axc :FTBFS:build failed (error: ‘-fcf-protection=full’ is not supported for this target)

on option on architectures that do not support it.I have tested this solution, and it works well.The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_axc_test_failed.patch Description: Binary data

Bug#1100843: feenox :FTBFS:build failed ( some test failed)

combined with the build logs, created a patch to modify these tests. I tested this solution, and it works effectively. The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_feenox_test_failed.patch Description: Binary data

Bug#1100094: kodi: Kodi fails to build with pipewire 1.4.0

Hi, this issue may have been solved upstream in the latest version. reference: https://github.com/xbmc/xbmc/commit/269053ebbfd3cc4a3156a511f54ab7f08a09a730 Gui-Yue Best regards

Bug#1099828: diamond-aligner :FTBFS:build failed ( error: ‘memcpy’ was not declared in this scope)

cally,and it works well.The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_diamond-aligner_missing_cstring.patch Description: Binary data

Bug#1099784: mercurial :FTBFS:build failed (ModuleNotFoundError: No module named 'distutils')

=0 My solution to this issue: This issue is caused by setuptools not being automatically installed on the RISC-V architecture and needs to be explicitly installed in debian/control. I have tested this solution,and it works well.The debpatch is in the attachment. Gui-Yue Best Regards fix_mercurial_failed_on_riscv.patch Description: Binary data

Bug#1098847: meli :FTBFS:build failed (error[E0063]: missing field `modifiers`)

ta -L native=/usr/lib/riscv64-linux-gnu -L native=/usr/lib/riscv64-linux-gnu` (exit status: 1) dh_auto_build: error: /usr/share/dh-rust/bin/cargo build returned exit code 101 make: *** [debian/rules:16: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=meli&arch=riscv64&ver=0.8.10%2Bdfsg-2%2Bb1&stamp=1740301953&raw=0 My solution to this issue: The error is caused by the modifiers field in the structure being a required field in the newer version of the IMAP library. My solution is to provide a default value to fill in this field.I have tested that locally,and it works well .The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_meli_build_failed_on_riscv64.patch Description: Binary data

Bug#1098501: haskell-gi-vte :FTBFS:build failed ( Could not load module ‘GI.GdkPixbuf.Objects.Pixbuf’)

epends list in gi-vte.cabal.I have tested that locally, and it works well.The debpatch is in the attachment. Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_haskell-gi-vte_build_failed_onriscv.patch Description: Binary data

Bug#1095672: g10k :FTBFS:build failed ( -race is not supported on linux/*)

ce" flag is only supported on amd64, arm64, ppc64el, and s390x. Therefore, my solution is to remove the "-race" flag on unsupported architectures. The debpatch is in the attachment. I have tested that locally,and it works well.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_-race_issue.patch Description: Binary data

Bug#1095462: sysprof :FTBFS:build failed

I apologize for using Chinese comments in the patch; please refer to this version of the patch. fix_sysprof_build_failed.patch Description: Binary data

Bug#1095462: sysprof :FTBFS:build failed ( error: ‘PERF_REG_EXTENDED_MASK’ undeclared (first use in this function))

, provide an appropriate default value (for example, 0ULL).The debpatch is in the attachment.I have tested it locally and it works well.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_sysprof_build_failed.patch Description: Binary data

Bug#1093771: lomiri-teleports-app:FTBFS:build failed ( error: cannot find library libtdjson.so.1.8.38)

so.1.8.38. By setting LD_LIBRARY_PATH=/usr/lib/$(DEB_HOST_MULTIARCH)/TDLib1.8.38:$LD_LIBRARY_PATH, the library can be properly recognized. The debpatch is in the attachment.I have tested that locally and it works well.Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_lomiri

Bug#1093147: elixir-lang:FTBFS:build failed ([31m** (ExUnit.TimeoutError) test timed out after 60000ms)

Source: elixir-lang Version: 1.18.1.dfsg-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear elixir-lang maintainer, The package elixir-lang build failed on riscv64.The crucial buildd log below: ``` 1) test

Bug#1092197: libxmp:FTBFS:build failed (/bin/sh: 1: rst2pdf: not found)

issue: The build failure was caused by the missing dependency "rst2pdf," so the issue can be resolved by adding "rst2pdf" as a dependency in debian/control. I have tested this solution locally, and it works well.The debpatch is in the attachment.Please let me know whether this solutio

Bug#1092152: bornagain:FTBFS:build failed on riscv64 (Example.specular.GaussianBeams.persist test failed)

=0 My solution to this issue: The issue arises because the tests for GaussianBeams on the RISC-V architecture exceed the acceptable threshold. My solution is to slightly increase the threshold to ensure the tests pass on the RISC-V architecture.The debpatch is in the attachment.Please let me

Bug#1089574: blender:FTBFS:build failure on riscv (error: #error Please add support for your architecture in BLI_build_config.h)

Hi Eric, I'd like to, but I see this work has been done, details can be found at https://projects.blender.org/blender/blender/commit/f662caf7226ca27921aabb50a41eaaec4c07d0ef .I mean that we can upgrade this package from upstream to fix this issue. Best regards, Gui-Yue Eric Long 于2024年12月

Bug#1090243: libkf5sane:: FTBFS: Could not find a package configuration file provided by "KSaneCore"

not include the /usr/lib/riscv64-linux-gnu/cmake/KSaneCore/KSaneCoreConfig.cmake file required by libkf5sane. Could the dependency on KSaneCore in the CMakeLists.txt file be updated to KSaneCore6 instead? Regards Gui-Yue

Bug#1090184: ipsvd:FTBFS:build failed on riscv64 (./chkshsgr || (cat warn-shsgr; exit 1) return exit1)

ested this solution locally, and it works well.The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards skip_chkshsgr_for_ipsvd.patch Description: Binary data

Bug#1089212: gnome-control-center:FTBFS:build failure on riscv (test-network-panel test timeout)

Hi, about https://salsa.debian.org/gnome-team/gnome-control-center/-/merge_requests/52 Perhaps, doubling the test timeout threshold specifically for RISC-V might be a better choice. Regards Gui-Yue

Bug#1089574: blender:FTBFS:build failure on riscv (error: #error Please add support for your architecture in BLI_build_config.h)

Source: blender Version: 4.3.0+dfsg-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear blender Maintainer, The package blender build failed because BLI_build_config.h does not support riscv64. The crucial b

Bug#1089212: gnome-control-center:FTBFS:build failure on riscv (test-network-panel test timeout)

Source: gnome-control-center Version: 1:47.2-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear gnome-control-center Maintainer, The package gnome-control-center build failed on riscv64 caused by test-netwo

Bug#1088654: xmountains FTBFS on !x86 (fix patch)

supported on the current target architecture (non-amd64 or i386). I have completed a patch that disables this compiler option on non-AMD architectures. I have tested the patch, and it works very effectively. Please let me know whether this solution can be accepted. Gui-Yue Best Regards

Bug#1088172: weakforced:FTBFS:build failure (undefined reference to `__atomic_load_16')

Source: weakforced Version: 2.10.2-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear weakforced Maintainer, The package weakforced build failed on all arch. The crucial buildd log below: ``` cp ../debian/

Bug#1087899: litecoin:FTBFS:build failure (error: too few arguments to function)

d with additional parameters, such as char *errorMsg and int errorMsgLen. I resolved the issue by adding the required parameters for the new version, while also incorporating conditional checks to ensure compatibility with older versions of miniupnpc.I have tested this solution

Bug#1087474: xtrkcad:FTBFS:build failure (error: ld returned 1 exit status)

orks well.The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best regards fix_xtrkcad_build_failure.patch Description: Binary data

Bug#1087474: fill crucial log

The crucial builddd log is here: ``` [100%] Linking C executable xtrkcad cd /<>/obj-aarch64-linux-gnu/app/bin && /usr/bin/cmake -E cmake_link_script CMakeFiles/xtrkcad.dir/link.txt --verbose=1 /usr/bin/ld: /<>/app/tools/lib/linux/libzip.a(zip_close.o): Relocations in generic ELF (EM: 62) /usr/bin/

Bug#1087010: prime-phylo:FTBFS:build failure (Imported target "MPI::MPI_Fortran" includes non-existent path )

this method, and it is very effective. The debpatch is in the attachment. This patch can automatically set MPIFORTRAN to the correct path based on the current architecture. Please let me know whether this solution can be accepted. Gui-Yue Best Regards fix_prime-phylo_configure_failed.patch Description: Binary data

Bug#1086345: desmume:FTBFS:build failure (error: ‘AT_HWCAP’ undeclared )

Source: desmume Version: 0.9.13-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear desmume Maintainer, The package desmume build failed on all architectures except ARM.The crucial buildd log below: ``` FAI

Bug#1085967: fix cif-tools build failure

buildd log is below: https://buildd.debian.org/status/fetch.php?pkg=cif-tools&arch=riscv64&ver=1.0.7-1%2Bb2&stamp=1729338657&raw=0 My solution to this issue: The error occurred because the relevant parts of this package are not compatible with the current version of libcifpp. So,we can modify this part code to be compatible with libcifpp.I have tested the solution locally,and it works well.The debpatch is in the attachment.Please let me know whether this solution can be accepted. Gui-Yue Best Regards mod-for-libcifpp.patch Description: Binary data

Bug#1085518: haskell-xml-conduit-writer:FTBFS:build failure (The variable when is not in scope)

Control.Monad (when)' can fix the issue. I have tested this solution locally,and it works well.The debpatch is in the attachment.Please let me know weather this solution can be accepted. Gui-Yue Best Regards haskell-xml-conduit-writer_fix_build_failure.patch Description: Binary data

Bug#1085279: python-websockets:FTBFS:build failure (TimeoutError)

operation to complete. We can resolve this test error by increasing the timeout threshold.I have tested that on local,and it works well.The debpatch is in the attachment.Please let me know wheather this solution can be accepted. Gui-Yue Best Regards fix_python-websockets_TimeOutError.patch Description: Binary data

Bug#1084508: linphone:FTBFS:build failure (compile failed)

ch.php?pkg=linphone&arch=riscv64&ver=5.2.0-4.3%2Bb4&stamp=1727424865&raw=0 My solution to this issue: The reason for the compilation failure is the incorrect parameter order of the calloc function. In the lp_new0 macro, the first parameter should be the number of elements, and the second parameter should be the size of each element, but the current definition has them in the reverse order. Modifying the macro definition will resolve this issue.I have test the solution locally ,and it works well.The deb-patch is in the attachment.Please let me know wheather this solution can be accepted. Gui-Yue Best Regards linphone_fix_compile_failed Description: Binary data

Bug#1082166: libopaque:FTBFS:build failure (‘-fcf-protection=full’ is not supported)

e host architecture is x86. If it is not x86, this CFLAG should be disabled.I have finished above work ,and i have tested that on local, it works well.The debpatch is in the attachment. Please let me know wheather this solution can be accepted. Gui-Yue Best Regards fix_libopaque_build_failure.patch Description: Binary data

Bug#1081819: liboprf:FTBFS:build failure (‘-fcf-protection=full’ is not supported)

: *** [debian/rules:18: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 ``` Gui-Yue Best Regards

Bug#1081819: liboprf:FTBFS:build failure (‘-fcf-protection=full’ is not supported)

Dear maintainer, I'll test that again.By the way, I noticed that this package has upgraded to 0.3.2-2,however the modifications i suggested seem not applied.Could you give me more information about this upgrade? Best wishes Gui-Yue

Bug#1081819: liboprf:FTBFS:build failure (‘-fcf-protection=full’ is not supported)

rily disabled this test. I have finished above work,and i have tested that locally,it works well. The debpatch is in the attachment.Please let me know wheather this solution can be accepted. Gui-Yue Best Regards fix_liboprf_build_failed.patch Description: Binary data

Bug#1081639: python-freecontact:FTBFS:build failure (cant find -lboost_python)

, it works well.Please let me know wheather the solution can be accepted.The patch is in the attachment. Gui-Yue Best Regards fix_python-freecontact_build_failure.patch Description: Binary data

Bug#1081426: Fix this for upstream

I have pull request this for upsteam: https://github.com/exult/exult/pull/560, and it has been accepted.

Bug#1081426: exult:FTBFS:build failure (syntax error)

is issue: We can fix this syntax error by changing line 206 of version.cc from``` out << "RISC-V" ``` to``` out << "RISC-V"; ```. l have tested this solution on local,and it works well.Please let me know wheather the solution can be accepted. The patch is in the attachment. Gui-Yue Best Regards fix_build_failure_on_riscv.patch Description: Binary data

Bug#1081259: libreoffice:FTBFS:build failure (test failed on riscv64)

d because NaN is not supported on the RISC-V platform.W e can skip this test when build on riscv64.I have tested this solution on local, and it works well.Please let me know wheather this solution can be accepted.The patch is in the attachment. Gui-Yue Best Regards fix_test_payloadNaN_failed_on_r

Bug#1079604: epics-base:FTBFS:build failure (not support riscv64)

t works well.The debdiff patch is in the attachment.Please let me know wheather this sotution can be accepted. Gui-Yue Best Regards support_for_riscv64.patch Description: Binary data

Bug#1078816: ruby-redcloth:FTBFS:build failure（test failed）

SC-V 64. I have tried this solution locally, and it works well. Please let me know whether this solution is acceptable. The debdiff patch is attached.The changes are mainly in debian/patches and debian/rules. Gui-Yue Best Regards Increase_test_threshold_for_RISC-V.debdiff Description: Binary data

Bug#1078501: ruby-stackprof:FTBFS:build failure（test failed）

f |2551 - 2546| (i.e. 5) should be less than or equal to 2, but the actual value was outside this range.I don't think this test works on RISC-V，I hope to skip this test on riscv64.After I skip this test, the package build successfully on my machine.Please let me know wheather this solution can

Bug#1078190: chiark-utils:FTBFS:build failure（compile failed）

ITS=64 -D_FILE_OFFSET_BITS=64" \". Replace that with "CMDLINE_CPPFLAGS="$(shell $(D_BUILDFLAGS) --get CPPFLAGS) -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64" \".This way the issue can be fixed. I have tested that in local, and it works well. Please let me know wheather this solution can be accepted. Gui-Yue Best Regards

Bug#1074586: mayavi2:FTBFS:build failure（UnicodeDecodeError）

Source: mayavi2 Version: 4.8.1-5 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear mayavi2 Maintainer, The package mayavi2 build failed on arch riscv64 caused by UnicodeDecodeError.The crucial buildd log belo

Bug#1074412: rust-apr:FTBFS:build failure（arguments to this function are incorrect）

rror: debian/rules binary-arch subprocess returned exit status 2 ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=rust-apr&arch=riscv64&ver=0.1.9-1&stamp=1699404678&raw=0 My solution to this issue: The error message indicates a type mismatch in the Rust code, where a *const i8 is being passed instead of the expected *const u8. This is due to differences in type definitions in C and Rust. Specifically, in C, char is often defined as i8 in Rust, while in Rust u8 is used for unsigned 8-bit integers.I can create a patch to replace `i8` with 'u8'.I have tested that on local and it works well.The patch is in the attachment, please let me know wheather this solution can be accepted. Gui-Yue Best Regards fix_incorrect_arguments.patch Description: Binary data

Bug#1074261: pocl:FTBFS:build failed（symbol diff）

Source: pocl Version: 6.0-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear pocl Maintainer, The package pocl build failed on arch mips64el,ppc64el,riscv64 and s390x caused by symbol diff.The crucial buildd

Bug#1072806: packagesearch:FTBFS:build failed（configure failed）

her this solution can be accepted. Gui-Yue Best Regards series Description: Binary data fix_configure_failed.patch Description: Binary data

Bug#1072667: picotool:FTBFS:build failed(picotool.1.in diff)

ps://salsa.debian.org/debian/picotool, and I have tested it; it works well. However, the debian/changelog has not been modified. Maybe you should update the changelog to trigger a rebuild. Gui-Yue Best Regards

Bug#1072615: mahimahi:FTBFS:build failed（error: ‘uint64_t’ does not name a type）

make it to support higher gcc version.I have tested this modification in local,and it works well. Please let me know wheather this solution can be accepted. The patch is in the attachment. Gui-Yue Best Regards fix_gcc11_error.patch Description: Binary data

Bug#1072005: coz-profiler:FTBFS:build failed（dwarf::format_error）

?pkg=coz-profiler&arch=riscv64&ver=0.2.2-3&stamp=1715249170&raw=0 My solution to this issue: Create a patch to modify the makefile to add CXXFLAG "-gdwarf-4" . I have tested this modification in local, and it works well.Please let me know wheather this solution can be accepte

Bug#1071928: gsocket:FTBFS:build failed(symbol diff on riscv64)

ar to the solution on amd64, ignore related symbol on riscv64.I have tested this modification in local, and it works well. Please let me know wheather this solution can be accepted. Gui-Yue Best Regards fix_symbol_on_riscv64.patch Description: Binary data

Bug#1071820: Add attachment

fix_loses_precision_error.patch Description: Binary data

Bug#1071820: blender:FTBFS:compile failed(error: cast from ‘void*’ to ‘CUdeviceptr’ loses precision)

2%2Bdfsg-1&stamp=1704028470&raw=0 My solution to this issue: Convert the problematic conversion code to a uintptr_t intermediate type.I have tested this modification in local ,and it works well.Please let me know wheather this patch can be accepted. The patch is in the attachment. Gui-Yue Best Regards

Bug#1071569: llvmlite:FTBFS:compile failed(test: plugin distutils failed with: exit code=134)

issue #917252, so I can modify the file debian/rules to view the auto-test as success. I have test this modification in local, and it work effectively.Please let me know wheather this patch can be accepted. The patch is in the attachment. Gui-Yue Best Regards fix_build_failure_on_riscv.patch Description: Binary data

Bug#1060191: Add attachment

I forgot to add the patch in the attachment,so add attachment in this mail. basic_support_for_riscv_and_loong.patch Description: Binary data

Bug#1060191: kcov:FTBFS:compile failed(error: #error Unsupported architecture)

Error 1 ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=kcov&arch=riscv64&ver=38%2Bdfsg-1&stamp=1581254367&raw=0 My solution to this issue: Add a patch(my patch is in the attachment) to add basic support for arch riscv and loong.By the way,I have includ

Bug#1060142: kafs-client:FTBFS:compile failed(cc: error: unrecognized command-line option ‘-m64’)

amp;stamp=1690546865&raw=0 My solution to this issue: add a patch to modify flag option "-m64". This solution is effective, and it has builded successfully in local.The patch is in the attachment. Please let me know wheather this solution can be accpted. Gui-Yue Best Regards fix_error_flag_m64.debdiff Description: Binary data

Bug#1013584: octave-iso2mesh: FTBFS: dh_missing: error: missing files, aborting

Source: octave-iso2mesh Version: 1.9.6+ds-7 Severity: serious Justification: FTBFS Tags: sid ftbfs Dear octave-iso2mesh Maintainer, About the issue reported, there is a solution that add "not-installed" file to /debian. This solution refers to Bug Report #964666. More details can be found in http

Bug#1059964: qmenu: FTBFS: qmenu.c compile failed(error: format not a string literal and no format arguments [-Werror=format-security])

parameter of "printw". The patch is in the attachment. This solution has succeed in local, please let me know if here need more tests. Gui-Yue Best Regards fix_build_failure_on_riscv64.debdiff Description: Binary data

Bug#1059910: openlibm:FTBFS:symbol different(' some symbols or patterns disappeared in the symbols file')

ocal, please let me know if here need more tests. Gui-Yue Best Regards openlibm_symbol_for_riscv64.debdiff Description: Binary data

Bug#939428: O: sslh -- Applicative protocol multiplexer

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the sslh package. The package description is: sslh lets one accept HTTPS, SSH, OpenVPN, tinc and XMPP connections on the same port. This makes it possible to connect to any of these servers on po

Bug#939425: O: memcached -- high-performance memory object caching system

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the memcached package. The package description is: Danga Interactive developed memcached to enhance the speed of LiveJournal.com, a site which was already doing 20 million+ dynamic page views per

Bug#939426: O: qstat -- Command-line tool for querying quake (and other) servers

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the qstat package. The package description is: Qstat provides a simple interface for querying servers for a number of games, including but not limited to quake, quakeworld, quake2, quake3arena, u

Bug#939424: O: inspircd -- Modular IRCd written in C++

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the inspircd package. The package description is: InspIRCd is a modular C++ IRC Daemon for several operating systems created to provide a stable, modern, lightweight irc server from scratch and pr

Bug#939427: O: rsnapshot -- local and remote filesystem snapshot utility

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the rsnapshot package. The package description is: rsnapshot is an rsync-based filesystem snapshot utility. It can take incremental backups of local and remote filesystems for any number of machi

Bug#939423: O: hping3 -- Active Network Smashing Tool

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the hping3 package. The package description is: hping3 is a network tool able to send custom ICMP/UDP/TCP packets and to display target replies like ping does with ICMP replies. It handles fragme

Bug#939422: O: flowscan -- flow-based IP traffic analysis and visualization tool

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the flowscan package. The package description is: FlowScan is a freely-available network traffic analysis and visualization tool which uses IP flow data to provide a continuous near real-time vie

Bug#939421: O: gdisk -- GPT fdisk text-mode partitioning tool

Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I intend to orphan the gdisk package. The package description is: GPT fdisk (aka gdisk) is a text-mode partitioning tool that works on Globally Unique Identifier (GUID) Partition Table (GPT) disks, rather than on

Bug#873758: stretch-pu: package memcached/1.4.33-1

Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The attached patch fix CVE-2017-9951 which has been not fixed via a DSA, as discussed with Salvatore Bonaccorso: https://bugs.d

Bug#872520: hplip-gui: root@178-83-145-250:/home/chofer# apt-get install hplip-gui

Package: hplip-gui Followup-For: Bug #872520 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this

Bug#835456: FTBFS: t/refhang.t test fail on s390x

Package: memcached Version: 1.4.31-1 Severity: serious Tags: upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just for the record, the upstream test suite fail on s390x https://buildd.debian.org/status/fetch.php?pkg=memcached&arch=s390x&ver=1.4.31-1&stamp=1471823136 I'll open a issue to

Bug#814228: New upstream release available

Package: siege Version: 3.0.8-1+b1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 New upstream are released since 3.0.8, please consider pakckaging the last version 3.1.4 released the 2016/02/06. - -- System Information: Debian Release: stretch/sid APT prefers unstable AP

Bug#803893: Please make the build reproducible (timestamps)

Package: goaccess Version: 1:0.9.4-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, First, thanks for maintaining this great log analyzer. While working on the "reproducible builds" effort

Bug#789528: RM: nc6 -- ROM; Dead upstream, alternatives exists

Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I propose to remove nc6 of the archive because upstream has abdandoned it and recommends to use alternatives: http://www.deepspace6.net/projects/netcat6.html I'm not aware of other packages d