Bug#1075908: ITS: cairocffi

Hi Boyuan, I’m not active in the Debian community and won’t be possible to find time to catch up and contribute again. Please move forward with your plan. Best, JC > On Jul 7, 2024, at 1:28 PM, Boyuan Yang wrote: > > Source: cairocffi > Severity: important > Version: 1.7.1-1 > X-Debbugs-CC: j

Bug#975881: Build of xt_ACCOUNT.ko failed for: 5.9.0-3-amd64

/include/generated/autoconf.h -rw-r--r-- 1 root root 138648 Nov 19 08:19 /usr/src/linux-headers-5.9.0-3-amd64/include/config/auto.conf -- Jean-Christophe DKMS make.log for xtables-addons-3.11 for kernel 5.9.0-3-amd64 (x86_64) Thu 26 Nov 2020 08:13:08 AM CET make: Entering directory '/usr/src

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

ll start clamav-daemon you have to set 'capability chown' > in '/etc/apparmor.d/usr.sbin.clamd' also. > > Thank you > Michael. > > Zitat von jean-christophe manciot : > > > I've just realized that lchown is only a system call, so it must be > &

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

I've just realized that lchown is only a system call, so it must be used from within /usr/bin/freshclam. On Thu, Oct 29, 2020 at 9:33 AM jean-christophe manciot wrote: > > I have tried to add to /etc/apparmor.d/local/usr.bin.freshclam: > capability dac_override, > > and res

Bug#972974: [Pkg-clamav-devel] Bug#972974: clamav-freshclam start faild.

The problem appears to be the apparmor or freshclam's profile for it. So > disabling apparmor should make freshclam work again. > Probably adding > | capability dac_override, > > to the profile will help, too. I will test it later today… > > Sebastian -- Jean-Christophe

Bug#972974: clamav-freshclam start faild.

9:15:31 hostname systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE Oct 27 09:15:31 hostname systemd[1]: clamav-daemon.service: Failed with result 'exit-code'. -- Jean-Christophe

Bug#967703: Existing proposal to port Pixelize to GTK3.

I already provided a "port" of pixelize to gtk3 as documented in . I tried to notify the official maintainer (com> or ) for this proposal but I did not received any feedback. Regards. JC

Bug#950780: Can't open DBIP database

An upstream request has been filed at netfilter-devel mailing list <https://marc.info/?l=netfilter-devel&m=158098795600650&w=2>. On Thu, Feb 6, 2020 at 12:01 PM jean-christophe manciot < actionmysti...@gmail.com> wrote: > Thanks, I'll take care of it. > > On T

Bug#950786: debian folder disappears on v2.3.0

it-cryptsetup ((v2.3.0))# ls debian ls: cannot access 'debian': No such file or directory This issue prevents us from building cryptsetup with debian tools, such as debuild. There was no such issue with previous tags. -- Jean-Christophe

Bug#950780: Can't open DBIP database

-BR.csv GeoLite2-Country-Locations-de.csv GeoLite2-Country-Locations-fr.csv GeoLite2-Country-Locations-ru.csv # /usr/lib/xtables-addons/xt_geoip_build -D /usr/share/xt_geoip -S . Can't open DBIP database This issue also happens with 3.8-1, but not with previous versions. -- Jean-Christophe

Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

Just for information, I just run a test on a Bullseye VM with sudo-ldap 1.8.29-1 and the issue is still present in this version.

Bug#949519: sudo-ldap: Fails to connect to LDAP : "ldap_sasl_bind_s(): Can't contact LDAP server"

Sorry, it looks like I forget to paste the presentation of my issue on reportbug. I used to use sudo-ldap on Stretch to grant some rights to some users on my servers. I recently upgrade one of these servers to Buster, and now sudo doesn't work anymore. It's always the same error : "ldap_sasl_

Bug#948999: pixelize: Proposal to update pixelize package

Package: pixelize Version: 1.0.0-1build1 Severity: wishlist Tags: newcomer Dear Maintainer, For some of my own needs I decided to port the program "pixelize" to a the latest version of GTK3 (the source code has not been touched since early 2009). In the process, I fixed a few bugs and added some

Bug#934350: Build of xt_ACCOUNT.ko failed for: 5.2.0-2-amd64 (x86_64) due to invalid kernel configuration

CONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno- sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-f rame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-bu -- Jean-Christophe

Bug#933177: network-manager-openvpn: unable to connect after upgrade to buster due to new OpenSSL minimum TLS version

age if accepted. I'll update that bug report as soon as the packet will be integrated. Best regards. -- Jean-Christophe Arnu

Bug#922234: Stretch stuck after loading initial ramdisk

I have the exact same problem on one of my servers. To be precise, no boot problem with Debian kernels up to 4.9.0-7 included. But I encounter the same issue whith 4.9.0-8 and 4.9.0-9 : a blank screen with a blinking cursor just after the 'Loading initial ramdisk ..." message. What is reall

Bug#918338: An error in debian/rules stops the build

t status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -i -I --build=binary --build=binary -j1 failed -- Jean-Christophe

Bug#914789: setpriv binary package is not built from util-linux source package

be installed E: Broken packages -- Jean-Christophe

Bug#912970: Max. recursion depth with nested structures exceeded

sions || exit 0 ; apt-show-versions -i' E: Sub-process returned an error code Reinstalling apt-show-versions throws the same error. This issue happened with the upgrade to perl & 5.28.0-3. -- Jean-Christophe

Bug#902191: Tha GeoLite Legacy Databases downloaded by geoip/xt_geoip_dl are obsolete and need to be replaced by GeoLite2 Free Databases

ented_country_geoname_id" as specified by Geonames <http://www.geonames.org/>. This has probably some consequences for the geoip/*xt_geoip_build* script. -- Jean-Christophe

Bug#897179: FTBFS: A build dependency is lacking: appstream-util (>= 0.7.7)

.. On Sun, Apr 29, 2018 at 5:23 PM Jeremy Bicha wrote: > On Sun, Apr 29, 2018 at 11:19 AM, jean-christophe manciot > wrote: > > There is a misunderstanding: this thread is about an up-to-date sid > chroot > > built of gimp. > > The build would not have failed in an

Bug#897179: FTBFS: A build dependency is lacking: appstream-util (>= 0.7.7)

discovered what triggered the issue and I tried to build it again in the same sid chroot with appstream-util 0.7.7 to confirm that the issue was solved. On Sun, Apr 29, 2018 at 5:11 PM Jeremy Bicha wrote: > On Sun, Apr 29, 2018 at 11:05 AM, jean-christophe manciot > wrote: > > No, it

Bug#897179: FTBFS: A build dependency is lacking: appstream-util (>= 0.7.7)

t; should also fix this issue for you. > > Jeremy > -- Jean-Christophe

Bug#897179: FTBFS: A build dependency is lacking: appstream-util (>= 0.7.7)

: appstream-util (>= 0.7.7), debhelper (>= 11), ... Cf. reported bug on bugzilla.gnome.org [2.10.0] FTBFS test-appdata.sh: • tag-invalid : timestamps are not in order [1448582400 before 1494460800] <https://bugzilla.gnome.org/show_bug.cgi?id=795658&

Bug#892547: closed by Guillem Jover (Re: Bug#892547: [Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build=)

ystem > Contact ow...@bugs.debian.org with problems > > > -- Forwarded message -- > From: Guillem Jover > To: jean-christophe manciot , > 892547-d...@bugs.debian.org > Cc: > Bcc: > Date: Sat, 10 Mar 2018 14:06:10 +0100 > Subject: Re: Bug#892547: [Feat

Bug#892547: [Feature Request] Add architecture dependent keywords to dpkg-buildpackage --build=

],[arch2],...[archn] For instance: - --build=amd64 - --build=amd64,arm64 ... It must be possible to combine those architecture keywords with other existing build keywords such as: - all - source For instance: - --build=amd64,all - --build=amd64,arm64,all ... -- Jean-Christophe Manciot

Bug#890978: babl: FTBFS: aclocal segfaults

moreinfo unreproducible > > On Wed, 21 Feb 2018 at 10:52:58 +0100, jean-christophe manciot wrote: > > make[1]: Entering directory '/home/actionmystique/src/Babl/babl-build/ > > babl-0.1.44-1' > > dh_autoreconf --as-needed > > libtoolize: putting auxiliary files

Bug#890978: FTBFS: aclocal failed with exit status: 139

'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' Segmentation fault (core dumped) autoreconf: aclocal failed with exit status: 139 dh_autoreconf: autoreconf -f -i returned exit code 139 make[1]: *** [debian/rules:18: override_dh_autoreconf] Error 2 -- Jean-Christophe

Bug#890821: [Pkg-libvirt-maintainers] Bug#890821: Multiple tests fail with: Could not define storage pool: operation failed: pool 'tmp' is already defined with uuid 00000000-1111-2222-3333-44444444444

Sorry about reporting that already filed issue. On Mon, Feb 19, 2018 at 12:40 PM, Guido Günther wrote: > control: forcemerge -1 890821 > > Hi Jean-Christophe, > you filed several FTBS bugs during the last months and these were either > related to your build environment or alread

Bug#890822: Test #435: RunCMake.CPack_RPM Failed

t; Call Stack (most recent call first): actual-err> actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Modules/CPackRPM.cmake:2774 (cpack_rpm_generate_package) actual-err> actual-err> This warning is for project developers. Use -Wno-dev to suppress it. actual-err> actual-err> actual-err> actual-err> CPackRPM: Will use GENERATED spec file: actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Build/Tests/RunCMake/RPM/CPack/EXTRA_SLASH_IN_PATH-build/_CPack_Packages/Linux/RPM/SPECS/extra_slash_in_path-applications.spec actual-err> actual-err> actual-err> CPackRPM: Will use GENERATED spec file: actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Build/Tests/RunCMake/RPM/CPack/EXTRA_SLASH_IN_PATH-build/_CPack_Packages/Linux/RPM/SPECS/extra_slash_in_path-headers.spec actual-err> actual-err> actual-err> CMake Warning (dev) at actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Modules/CPackRPM.cmake:2298 actual-err> (message): actual-err> actual-err> CPackRPM:Warning: debuginfo package was requested but will not be generated actual-err> as no source files were found! Component: 'libs'. actual-err> actual-err> Call Stack (most recent call first): actual-err> actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Modules/CPackRPM.cmake:2774 (cpack_rpm_generate_package) actual-err> actual-err> This warning is for project developers. Use -Wno-dev to suppress it. actual-err> actual-err> actual-err> actual-err> CPackRPM: Will use GENERATED spec file: actual-err> /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Build/Tests/RunCMake/RPM/CPack/EXTRA_SLASH_IN_PATH-build/_CPack_Packages/Linux/RPM/SPECS/extra_slash_in_path-libs.spec actual-err> actual-err> actual-err> '; actual-err> actual-err> CPack result: ''; actual-err> actual-err> config file: 'set(RPM_EXECUTABLE "/usr/bin/rpm") actual-err> actual-err> set(RPMBUILD_EXECUTABLE "/usr/bin/rpmbuild")' Call Stack (most recent call first): /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Tests/RunCMake/RunCMake.cmake:146 (run_cmake) /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Tests/RunCMake/CPack/CPackTestHelpers.cmake:77 (run_cmake_command) /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Tests/RunCMake/CPack/CPackTestHelpers.cmake:95 (run_cpack_test_common_) /home/actionmystique/src/Cmake/cmake-build/cmake-3.10.2-1/Tests/RunCMake/CPack/RunCMakeTest.cmake:25 (run_cpack_test) -- SOURCE_PACKAGE--type - PASSED -- RPM/SOURCE_PACKAGE--type - PASSED -- SUGGESTS-MONOLITHIC-type - PASSED -- RPM/SUGGESTS-MONOLITHIC-type - PASSED -- SYMLINKS-MONOLITHIC-type - PASSED -- RPM/SYMLINKS-MONOLITHIC-type - PASSED -- SYMLINKS-COMPONENT-type - PASSED -- RPM/SYMLINKS-COMPONENT-type - PASSED -- USER_FILELIST-MONOLITHIC-type - PASSED -- RPM/USER_FILELIST-MONOLITHIC-type - PASSED Start 436: RunCMake.CPack_7Z 436/491 Test #436: RunCMake.CPack_7Z .. Passed1.71 sec ... 99% tests passed, 1 tests failed out of 491 Label Time Summary: Label1= 0.03 sec*proc (1 test) Label2= 0.03 sec*proc (1 test) Total Test time (real) = 1620.73 sec The following tests FAILED: 435 - RunCMake.CPack_RPM (Failed) -- Jean-Christophe

Bug#890821: Multiple tests fail with: Could not define storage pool: operation failed: pool 'tmp' is already defined with uuid 00000000-1111-2222-3333-444444444444

/tests/checkprops.py", line 25, in testCheckProps self.assertEqual([], fail) File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python2.7/unittest/case.py", line 743, in assertListEqual self.assertSequenceEqual(list1, list2, msg, seq_type=list) File "/usr/lib/python2.7/unittest/case.py", line 725, in assertSequenceEqual self.fail(msg) File "/usr/lib/python2.7/unittest/case.py", line 410, in fail raise self.failureException(msg) AssertionError: Lists differ: [] != [ - [] + [, + , + , + , + , + , + , + , + , + , + , + , + ] This means that there are XML properties that are untested in the test suite. This could be caused by a previous test suite failure, or if you added a new property and didn't extend the test suite. Look into extending clitest.py and/or xmlparse.py. -- Ran 437 tests in 34.657s FAILED (failures=5, errors=9) make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1 make[1]: Leaving directory '/home/actionmystique/src/Virt-manager/virt-manager-build/virt-manager-1.4.3-1' make: *** [debian/rules:4: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 debuild: fatal error at line 1152: dpkg-buildpackage -rfakeroot -us -uc -ui -i -I --build=binary --build=binary -j1 -mJean-Christophe Manciot < manciot.jeanchristo...@gmail.com> failed -- Jean-Christophe

Bug#889543: CMake Error: The following variables are used in this project, but they are set to NOTFOUND.

Thanks for your swift reply. The build env is a sid chroot and: liblz4-dev: Installed: 0.0~r131-2+b1 On Sun, Feb 4, 2018 at 11:54 AM, Ondřej Surý wrote: > Hi Jean-Christophe, > > what is your build environment? > > Is liblz4-dev installed? > > Cheers, > -- > On

Bug#888571: python3-apt depends on python3 (<< 3.6)

6~), On Mon, Jan 29, 2018 at 8:45 PM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > @Axel Beckert > > >> That's wrong. The corresponding sources _are_ shown on >> https://packages.debian.org/source/sid/python-apt. It's the files >> called p

Bug#888571: python3-apt depends on python3 (<< 3.6)

wnloader. You're right here. I downloaded the python-apt binaries with Google chrome 64.0.3282.119 (Official Build) (64-bit) on Linux. I have just reported that issue to Google. -- Jean-Christophe Manciot

Bug#888661: "configure: error: glm/glm.hpp not found. install glm" although libglm-dev is installed

Error 25 make[1]: Leaving directory '/home/actionmystique/src/LibreOffice/libreoffice-5.4.4-1' debian/rules:1956: recipe for target 'build' failed make: *** [build] Error 2 Although: # apt-cache policy libglm-dev libglm-dev: Installed: 0.9.8.4-1.1 Full build

Bug#888571: python3-apt depends on python3 (<< 3.6)

und on https://packages.debian.org/source/sid/python-apt. -- Jean-Christophe

Bug#887986: [Pkg-libvirt-maintainers] Bug#887986: build-aux/test-driver: line 107: 28464 Aborted (core dumped)

a custom chroot without further details > fails > control: severit -1 minor > > Hi, > On Mon, Jan 22, 2018 at 12:21:33PM +0100, jean-christophe manciot wrote: > >Package: libvirt > >Version: 4.0.0-1 > >Sources: [1]https://packages.debian.org/source/sid/lib

Bug#887910: Downloads are sometimes incorrect

dn-fastly.deb.debian.org/debian/pool/main/a/apr-util/apr-util_1.6.1-1.dsc I have also verified that the *IPv6 address remained constant for all downloads*, i.e 2a04:4e42::204 in this case. -- Jean-Christophe Manciot

Bug#887889: Can't open debian/tmp/usr/lib/x86_64-linux-gnu/libapr-1.la: No such file or directory.

ailed make[1]: *** [override_dh_auto_install] Error 1 make[1]: Leaving directory '/home/actionmystique/src/Apr/apr-1.6.3-1' debian/rules:18: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 -- Jean-Christophe Manciot

Bug#883571: [pkg-gnupg-maint] Bug#883571: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake line 3930

> Control: tags 883571 + unreproducible moreinfo > > On Wed 2017-12-06 14:25:08 +0100, jean-christophe manciot wrote: > > Just renaming a tag won't solve any issue. > > there are issues that are solved by renaming tags, especially if you're > using git-buildpackage.

Bug#883571: [pkg-gnupg-maint] Bug#883571: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake line 3930

Just renaming a tag won't solve any issue. Of course it is still there. On Tue, Dec 5, 2017 at 7:46 PM, Daniel Kahn Gillmor wrote: > On Tue 2017-12-05 12:07:12 +0100, jean-christophe manciot wrote: > > It seems that the git repository has not been updated with > debian/2.4.5

Bug#883571: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake line 3930

ibtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/bin/automake line 3930. autoreconf: automake failed with exit status: 255 dh_autoreconf: autoreconf -f -i returned exit code 1 debian/rules:6: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 debuild: fatal error at line 1151: dpkg-buildpackage -rfakeroot -us -uc -ui -i -I --build=binary --build=binary failed gbp:error: 'debuild -i -I --no-sign --build=binary' failed: it exited with 29 It seems that the git repository has not been updated with debian/2.4.5-1... Regards. -- Jean-Christophe Manciot

Bug#880308: dh_install: Cannot find (any matches for) "usr/lib/xorg/modules/extensions/libvnc.so" (tried in ., debian/tmp)

Package: tigervnc Version: 1.7.0+dfsg-7 I encountered the exact same issue when building it in a clean sid chroot. A workaround is to build it in a stretch chroot indeed. -- Jean-Christophe Manciot

Bug#880713: KeyError: 32019

ian/rules:22: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/home/actionmystique/src/Git/git-git-buildpackage' debian/rules:18: recipe for target 'build' failed make: *** [build] Error 2 d

Bug#880664: Conflicting types for 'FcObjectTypeHash' & 'FcObjectTypeLookup'

/cdbs/1/class/makefile.mk:77: recipe for target 'debian/stamp-makefile-build' failed make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Whole build log is attached. -- Jean-Christophe Manciot - Bui

Bug#879269: KeyError: 32019

ving directory '/home/actionmystique/src/Git/git-git-buildpackage' debian/rules:21: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 make[1]: Leaving directory '/home/actionmystique/src/Git/git-git-buildpackage' debian/rules:17: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 The whole build log is attached. -- Jean-Christophe Manciot git-buildpackage.build Description: Binary data

Bug#876658: Bug#877996: ERROR: appinfo

Package: glib2.0 Version: 2.54.1-1 Installing gnome-terminal in the sid chroot does solve this issue. On Sun, Oct 8, 2017 at 6:12 PM, Simon McVittie wrote: > Control: merge 876658 877996 > > On Sun, 08 Oct 2017 at 13:11:45 +0200, jean-christophe manciot wrote: > > ERROR: ap

Bug#877923: conflicting types for 'FcObjectTypeHash'

js.c:31:1: note: previous declaration of 'FcObjectTypeLookup' was here FcObjectTypeLookup (register const char *str, register FC_GPERF_SIZE_T len); ^~ Makefile:638: recipe for target 'fcobjs.lo' failed Full build log is attached. -- Jean-Christophe fontconfig.2.12.3-0.2_amd64.build Description: Binary data

Bug#863608: invalid application of ‘sizeof’ to incomplete type ‘cipher_ctx_t {aka struct evp_cipher_ctx_st}’

6:30 PM, Jörg Frings-Fürst wrote: > tags 863608 + moreinfo > thanks > > > Hello Jean-Christophe, > > > first thank you for spending your time helping to make Debian better > with this bug report. > > Do you build openvpn from a Ubuntu source? This line from your

Bug#876551: dh_installdocs: Unknown package libblkid1-udeb given via -N/--no-package

t status 2 -- Jean-Christophe Manciot

Bug#876520: debuild signs despite --no-sign or --unsigned-buildinfo

debsign failed gbp:error: 'debuild -i -I --no-sign --build=binary' failed: it exited with 29 According to Guillem Jover : "This would be a problem with debuild, which disables signing by default via -us -uc, signs then by itself with debsign, and does not understand itself --un

Bug#876334: A few tests fail during build

I've just tried to replace libssl-dev by libssl1.0-dev, and it does not change anything. On Thu, Sep 21, 2017 at 11:08 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > Hello Daniele, > > Is it possible that the latest libssl-dev has an impact on this issue?

Bug#876334: A few tests fail during build

.0.2l-2 On Thu, Sep 21, 2017 at 10:55 AM, Daniele Tricoli wrote: > Hello Jean-Christophe, > > On Thursday, September 21, 2017 9:08:12 AM CEST jean-christophe manciot > wrote: > > Package: python-urllib3 > > Version: debian/1.21.1-1 > > Sources: > > http

Bug#876334: A few tests fail during build

n.throw(*exc_info) File "/usr/local/lib/python2.7/dist-packages/tornado/http1connection.py", line 168, in _read_message quiet_exceptions=iostream.StreamClosedError) File "/usr/local/lib/python2.7/dist-packages/tornado/gen.py", line 870, in run value = future

Bug#876024: dpkg-buildpackage tries to sign buildinfo despite --unsigned-buildinfo or --no-sign passed to debuild

Sorry Guillem Jover, I missed your message which has been spammed by gmail for an unknown reason. You must be right It must be an issue with debuild. On Mon, Sep 18, 2017 at 11:17 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > I've made some progress: > - la

Bug#876024: dpkg-buildpackage tries to sign buildinfo despite --unsigned-buildinfo or --no-sign passed to debuild

clear-sign failed: Permission denied debsign: gpg error occurred! Aborting On Mon, Sep 18, 2017 at 9:55 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > @Osamu Aoki > You say --no-sign and --unsigned-buildinfo options are unsupported by > dpkg-buildpackage,

Bug#876024: dpkg-buildpackage tries to sign buildinfo despite --unsigned-buildinfo or --no-sign passed to debuild

.buildinfo file. On Mon, Sep 18, 2017 at 1:35 AM, Osamu Aoki wrote: > Hi, > > On Sun, Sep 17, 2017 at 07:58:16PM +0200, Guillem Jover wrote: > > Control: reassign -1 devscripts > > > > Hi! > > > > On Sun, 2017-09-17 at 15:36:00 +0200, jean-christophe

Bug#876024: dpkg-buildpackage tries to sign buildinfo despite --unsigned-buildinfo or --no-sign passed to debuild

line 1053: running debsign failed gbp:error: 'debuild -i -I --no-sign --build=binary' failed: it exited with 29 -- Jean-Christophe Manciot

Bug#874782: UFW build error: AssertionError: not thrown

In the meantime, I successfully built it in a sid chroot. The first attempt was made iwithn another environment (Ubuntu 17.04). You can close this report. On Fri, Sep 15, 2017 at 8:45 PM, Jamie Strandboge wrote: > On Sat, 2017-09-09 at 16:36 +0200, jean-christophe manciot wrote: > >

Bug#874782: UFW build error: AssertionError: not thrown

In the meantime, I successfully built it in a clean sid chroot. The first attempt was made iwithn another environment (Ubuntu 17.04). You can close this report. On Sun, Sep 17, 2017 at 11:34 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > In the meantime, I successfully

Bug#875552: Latest libksba release is not available on packages.debian.org/source/sid//libksba

Package: libksba Version: 1.3.5-3 On https://anonscm.debian.org/git/pkg-gnutls/libksba.git: git-libksba# git describe --abbrev=0 --tags 1.3.5-3 On https://packages.debian.org/source/sid//libksba: 1.3.5-2 -- Jean-Christophe Manciot

Bug#874796: Glib2 build fails as non-root & root user

work-around: Add the files to > > debian/not-installed" does not work. > > For a workaround, change "--fail-missing" in debian/rules to > "--list-missing". > > Emilio > -- Jean-Christophe

Bug#874796: Glib2 build fails as non-root & root user

Package: glib2.0 Version: 2.53.7-1 sources: https://packages.debian.org/source/sid/glib2.0 Even the workaround "For a short-term work-around: Add the files to debian/not-installed" does not work. On Sun, Sep 10, 2017 at 12:05 PM, jean-christophe manciot < actionmysti...@gma

Bug#874796: Glib2 build fails as non-root & root user

s. My debhelper is 10.7.2. On Sat, Sep 9, 2017 at 10:01 PM, Michael Biebl wrote: > Am 09.09.2017 um 20:25 schrieb jean-christophe manciot: > > Package: glib2.0 > > Version: 2.53.6-1 > > sources: https://packages.debian.org/source/sid/glib2.0 > > > > What do

Bug#874796: Glib2 build fails as non-root & root user

atures. That's why dh_missing is failing. > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > > -- Jean-Christophe

Bug#874782: UFW build error: AssertionError: not thrown

Package: ufw Version: 0.35-5 sources: https://packages.debian.org/source/sid/ufw Building with: dpkg-buildpackage --unsigned-source --unsigned-changes --build=binary -m"Jean-Christophe Manciot " leads to: =

Bug#857060: Hunk #1 FAILED at 231

don wrote: > On Mon, Sep 4, 2017 at 12:23 PM jean-christophe manciot < > actionmysti...@gmail.com> wrote: > >> >>- What parameters have you used with gbp to successfully build from >>sources? >> >> gbp buildpackage --git-verbose --git-pristine-tar &

Bug#857060: Hunk #1 FAILED at 231

12:47 PM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > package ntopng > tags 857060 > > >- What parameters have you used with gbp to successfully build from >sources? >- your repo is behind sid: debian/2.4+dfsg1-3 vs debian/2.4+dfsg1-4 > &g

Bug#857060: Hunk #1 FAILED at 231

package ntopng tags 857060 - What parameters have you used with gbp to successfully build from sources? - your repo is behind sid: debian/2.4+dfsg1-3 vs debian/2.4+dfsg1-4 On Mon, Sep 4, 2017 at 12:23 PM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > &g

Bug#857060: Hunk #1 FAILED at 231

- What parameters have you used with gbp to successfully build from sources? - your repo is behind sid: debian/2.4+dfsg1-3 vs debian/2.4+dfsg1-4 On Sat, Sep 2, 2017 at 6:58 PM, Ludovico Cavedon wrote: > package ntopng > tags 857060 + unreproducible > thanks > > Hi

Bug#874038: Removing package from repository with reprepro is not operative

0/libssl1.0.2_1.0.2l-2+9_amd64.deb'! There have been errors! *It does not seem possible to correct these self-generated errors*: # reprepro -Vb . deleteunreferenced # Nothing happens. Is there another way to restore the database consistency? -- Jean-Christophe Manciot

Bug#867546: gbp:error: Pristine-tar couldn't checkout "libvirt_3.5.0.orig.tar.xz": fatal: Path 'libvirt_3.5.0.orig.tar.xz.delta' does not exist in 'refs/heads/pristine-tar'

format:%an%x00%ae%x00%ad%x00%cn%x00%ce%x00%cd%x00%s%x00%f%x00%b%x00', '-z', '--date=raw', '--no-renames', '--name-status', '27f71ee9b902a0447287e55fe92ea687415527fe'] gbp:debug: Determined compression type 'xz' gbp:debug: ['git', 'show-ref', 'refs/heads/pristine-tar'] gbp:debug: /usr/bin/pristine-tar [] ['checkout', '/home/actionmystique/src/Libvirt/libvirt_3.5.0.orig.tar.xz'] gbp:error: Pristine-tar couldn't checkout "libvirt_3.5.0.orig.tar.xz": fatal: Path 'libvirt_3.5.0.orig.tar.xz.delta' does not exist in 'refs/heads/pristine-tar' pristine-tar: git show refs/heads/pristine-tar:libvirt_3.5.0.orig.tar.xz.delta failed -- Jean-Christophe Manciot

Bug#866675: ssh does not follow the order of specific identity files in /etc/ssh/ssh_config despite IdentitiesOnly being set

key: pkalg ssh-rsa blen 535 debug1: Authentication succeeded (publickey). -- Jean-Christophe

Bug#863608: invalid application of ‘sizeof’ to incomplete type ‘cipher_ctx_t {aka struct evp_cipher_ctx_st}’

(type *) malloc(sizeof(type))); \ ^~~~ Full build log is attached. -- Jean-Christophe openvpn_2.4.0-6.build Description: Binary data

Bug#861642: Some SSL tests fail during build

OR: test_simple (test.contrib.test_pyopenssl.TestHTTPS) ... *SSLError: ("bad handshake: Error([('SSL routines', 'ssl3_get_server_certificate', 'certificate verify failed')],)",)* *SSLError: [SSL: TLSV1_ALERT_UNKNOWN_CA] tlsv1 alert unknown ca (_ssl.c:590)* ...

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

@christian.ehrha...@canonical.com You're right. Thanks. On Thu, Apr 27, 2017 at 2:26 PM, Christian Ehrhardt < christian.ehrha...@canonical.com> wrote: > > On Thu, Apr 27, 2017 at 1:00 PM, jean-christophe manciot < > actionmysti...@gmail.com> wrote: > >> As pr

Bug#861175: [Python-modules-team] Bug#861175: cairocffi: Please drop Build-Depends and Recommends on xcffib

, AFAIR the package is outdated with respect to the source in g.d.o that might fix already a random FTBFS. You might start from that. Thanks, JC > Le 27 avr. 2017 à 19:20, Sandro Tosi a écrit : > > Hey Jean-Christophe, > do you have time to work on this or would you be ok with me having

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

09 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > @christian.ehrha...@canonical.com > Your "pull-debian-source qemu" does not use gbp built-in feature to use > the upstream branch for downloading the sources and instead downloads them >

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

he issue seems to come from the sources in the upstream branch of qemu git repository. On Wed, Apr 26, 2017 at 5:20 PM, Christian Ehrhardt < christian.ehrha...@canonical.com> wrote: > > On Wed, Apr 26, 2017 at 5:10 PM, jean-christophe manciot < > actionmysti...@gmail.com

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

rha...@canonical.com> wrote: > > ​On Wed, Apr 26, 2017 at 1:43 PM, jean-christophe manciot < > actionmysti...@gmail.com> wrote: > >> Please try it for yourself all the way to the end. > > > Please note that your remaining Error is about > 1 out of 2 hunks FAIL

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/02_kfreebsd.patch/ --reject-file=- < git-qemu.orig.YF8TNQ/debian/patches/02_kfreebsd.patch gave error exit status 1 dpkg-buildpackage: error: dpkg-source -i -I -b git-qemu gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I' failed: it exited with 29 Please try it for yourself all the way to the end. Probably worth noting I use the latest: gbp --version gbp 0.8.14 Regards. Jean-Christophe

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

, 2017 at 10:38 AM, Michael Tokarev wrote: > 26.04.2017 11:37, jean-christophe manciot wrote: > > Have you even tried to build qemu with gbp? > > I think I didn't, at least I don't remember I tried. > Regular dpkg-buildpackage works just fine for me. > > Thanks, > > /mjt > -- Jean-Christophe

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

Have you even tried to build qemu with gbp? On Wed, Apr 26, 2017 at 7:32 AM, Michael Tokarev wrote: > Since apparently there's nothing wrong with the repository > itself, and with the generated packages, I'm closing this > bugreport. > > Thanks! > > /mjt > -- Jean-Christophe

Bug#860826: Cannot build seabios from git repository

-buildpackage --build=binary -m"Jean-Christophe Manciot " leads to: ... dh_clean debian/rules build [ ! -d .git ] || { echo "Directory .git exists, aborting" >&2; exit 1; } *Directory .git exists, aborting* debian/rules:55: recipe for target 'build/env-stamp&#x

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

ed by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/02_kfreebsd.patch/ --reject-file=- < git-qemu-debian.orig.vZdRrL/debian/patches/02_kfreebsd.patch gave error exit status 1 dpkg-buildpackage: error: dpkg-source -i -I -b git-qemu-debian gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I' failed: it exited with 29 -- Jean-Christophe

Bug#858065: Hunk #1 FAILED at 317

dpkg-source: info: if patch 'Disable-use-of-namespaces-by-default.patch' is correctly applied by quilt, use 'quilt refresh' to update it dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/Disable-use-of-namespaces-by-default.patch/ --reject-file=- < git-libvirt.orig.9l_nR5/debian/patches/Disable-use-of-namespaces-by-default.patch gave error exit status 1 dpkg-buildpackage: error: dpkg-source -i -I -b git-libvirt gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I' failed: it exited with 29 *No such issue with tag=debian/3.0.0-3* -- Jean-Christophe

Bug#857621: closed by Colin Watson (Re: Bug#857621: error: dereferencing pointer to incomplete type ‘DSA {aka struct dsa_st}’)

I downgraded openssl to 1.0.2k-1~bpo8+1 and I am now able to build openssh 1:7.4p1-7. On Mon, Mar 13, 2017 at 6:05 PM, Colin Watson wrote: > On Mon, Mar 13, 2017 at 05:43:11PM +0100, jean-christophe manciot wrote: > > On Mon, Mar 13, 2017 at 3:13 PM, Colin Watson > wrote: > >

Bug#857621: closed by Colin Watson (Re: Bug#857621: error: dereferencing pointer to incomplete type ‘DSA {aka struct dsa_st}’)

- openssl 1.1.0e-1 - openssh 1:7.4p1-7, which is the version I'm trying to build. How is that possible? -- Jean-Christophe

Bug#857621: closed by Colin Watson (Re: Bug#857621: error: dereferencing pointer to incomplete type ‘DSA {aka struct dsa_st}’)

uot;libssl1.0-dev | libssl-dev (<< 1.1.0~)"), so I think you must be > attempting to build without the build-dependencies properly satisfied. > > -- > Colin Watson [cjwat...@debian.org] > > -- Forwarded message -- > From: jean-christophe manciot &g

Bug#857621: error: dereferencing pointer to incomplete type ‘DSA {aka struct dsa_st}’

recipe for target 'sshkey.o' failed make[2]: *** [sshkey.o] Error 1 make[2]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh/debian/build-deb' debian/rules:140: recipe for target 'override_dh_auto_build-arch' failed make[1]: *** [override_dh_auto_build-arch] Error 2 make[1]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/OpenSSH/git-openssh' debian/rules:121: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I' failed: it exited with 29 -- Jean-Christophe

Bug#857590: fatal: Path 'ntopng_2.4+dfsg1.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar'

-renames', '--name-status', '07ac79750b1c23cfcbbd54b0d8e722b58c271f79'] gbp:debug: Determined compression type 'gzip' gbp:debug: ['git', 'show-ref', 'refs/heads/pristine-tar'] gbp:debug: /usr/bin/pristine-tar [] ['checkout', '/home/actionmystique/Program-Files/Ubuntu/Ntop/ntopng_2.4+dfsg1.orig.tar.gz'] gbp:error: Pristine-tar couldn't checkout "ntopng_2.4+dfsg1.orig.tar.gz": fatal: Path 'ntopng_2.4+dfsg1.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar' pristine-tar: git show refs/heads/pristine-tar:ntopng_2.4+dfsg1.orig.tar.gz.delta failed -- Jean-Christophe

Bug#857587: fatal: Path 'ppp_2.4.7.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar'

27;, '--name-status', '7590e9d3e7158eefbfdb598092a622509322ae87'] gbp:debug: Determined compression type 'gzip' gbp:debug: ['git', 'show-ref', 'refs/heads/pristine-tar'] gbp:debug: /usr/bin/pristine-tar [] ['checkout', '/home/actionmystique/Program-Files/Ubuntu/Network-Manager/ppp_2.4.7.orig.tar.gz'] gbp:error: Pristine-tar couldn't checkout "ppp_2.4.7.orig.tar.gz": fatal: Path 'ppp_2.4.7.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar' pristine-tar: git show refs/heads/pristine-tar:ppp_2.4.7.orig.tar.gz.delta failed -- Jean-Christophe

Bug#857576: fatal: Path 'osinfo-db-tools_1.1.0.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar'

tus', '58349839f7efab73c5ff7af8fe729e6cab1103cc'] gbp:debug: Determined compression type 'gzip' gbp:debug: ['git', 'show-ref', 'refs/heads/pristine-tar'] gbp:debug: /usr/bin/pristine-tar [] ['checkout', '/home/actionmystique/Program-Files/Ubuntu/Libosinfo/osinfo-db-tools_1.1.0.orig.tar.gz'] gbp:error: Pristine-tar couldn't checkout "osinfo-db-tools_1.1.0.orig.tar.gz": fatal: Path 'osinfo-db-tools_1.1.0.orig.tar.gz.delta' does not exist in 'refs/heads/pristine-tar' pristine-tar: git show refs/heads/pristine-tar:osinfo-db-tools_1.1.0.orig.tar.gz.delta failed I confirm that osinfo-db-tools_1.1.0.orig.tar.gz.delta does not exist in 'refs/heads/pristine-tar'. -- Jean-Christophe

Bug#857060: Hunk #1 FAILED at 231

' dh_clean dpkg-source -i -I -b git-ntopng dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building ntopng using existing ./ntopng_2.4+dfsg1.orig.tar.gz patching file configure.seed Hunk #1 FAILED at 231. 1 out of 1 hunk FAILED dpkg-source: info: the pa

Bug#856711: "netlink/genl/genl.h: No such file or directory" although libnl-3-dev is installed

ude/libnl3/netlink/genl/genl.h # apt-cache policy libnl-3-dev libnl-3-dev: Installed: 3.2.27-1 -- Jean-Christophe Manciot

Bug#856347: error: cannot read git-qemu/debian/control: No such file or directory

ixman/|^roms/.*/ *dpkg-source: error: cannot read git-qemu/debian/control: No such file or directory* dpkg-buildpackage: error: dpkg-source -i -I --before-build git-qemu gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: 'debuild -i -I' failed: it exited with 29 How can we generate debian/control from debian/control.in? Regards. -- Jean-Christophe

Bug#852686: [Aptitude-devel] Bug#852686: Bug#852686: aptitude.xml:753: parser error : Opening and ending tag mismatch: keycombo line 746 and para

The reason is that I distribute many stable and unstable packages through 2 PPA <https://gitlab.com/jean-christophe-manciot/ppa> channels. I would be rather strange to publish an unstable release without its preceding stable version Also, in the case of aptitude, I try to publish only

Bug#852686: [Aptitude-devel] Bug#852686: Bug#852686: aptitude.xml:753: parser error : Opening and ending tag mismatch: keycombo line 746 and para

OK. On Thu, Jan 26, 2017 at 6:02 PM, Axel Beckert wrote: > Hi, > > jean-christophe manciot wrote: > > The reason is that I distribute many stable and unstable packages > through 2 > > PPA <https://gitlab.com/jean-christophe-manciot/ppa> channels. > > Then

Bug#852686: aptitude.xml:753: parser error : Opening and ending tag mismatch: keycombo line 746 and para

: Premature end of data in tag chapter line 646 ^ aptitude.xml:12823: parser error : Premature end of data in tag book line 194 ^ unable to parse aptitude.xml Makefile:982: recipe for target 'docbook-man-stamp' failed -- Jean-Christophe

Bug#852666: [Aptitude-devel] Bug#852666: "Can't figure out where Google Mock lives" although it is installed

On Thu, Jan 26, 2017 at 10:47 AM, Axel Beckert wrote: > Probably installing a newer version of google-mock. Hello Axel, Building and installing google-mock 1.8.0-6 solves this issue indeed. Thanks for your help. JC -- Jean-Christophe

  1   2   3   4   >