Processed: severity of 919634 is normal
Processing commands for cont...@bugs.debian.org: > # not down for everyone > severity 919634 normal Bug #919634 [wiki.debian.org] wiki.debian.org: https://wiki.debian.org/ down Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 919634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919634: wiki.debian.org: https://wiki.debian.org/ down
Package: wiki.debian.org Severity: grave Justification: renders package unusable wiki web server is mis-configured. When I browse to: https://wiki.debian.org/ The web page returned says: Forbidden You are not allowed to access this!" OR when viewed as source, I see this: 403 Forbidden ForbiddenYou are not allowed to access this!
-- System Information: Debian Release: 9.6 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#917596: marked as done (vuls: FTBFS)
Your message dated Fri, 18 Jan 2019 05:35:25 + with message-id and subject line Bug#917596: fixed in vuls 0.6.1-1 has caused the Debian Bug report #917596, regarding vuls: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:vuls Version: 0.4.2+git20180531.0.399a087-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-arch dh build-arch --buildsystem=golang --with=golang dh_update_autotools_config -a -O--buildsystem=golang dh_auto_configure -a -O--buildsystem=golang dh_auto_build -a -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/future-architect/vuls github.com/future-architect/vuls/cache github.com/future-architect/vuls/commands github.com/future-architect/vuls/config github.com/future-architect/vuls/contrib/owasp-dependency-check/parser github.com/future-architect/vuls/models github.com/future-architect/vuls/oval github.com/future-architect/vuls/report github.com/future-architect/vuls/scan github.com/future-architect/vuls/util errors internal/race runtime/internal/atomic runtime/internal/sys runtime sync/atomic sync io [... snipped ...] github.com/aws/aws-sdk-go/service/sts github.com/aws/aws-sdk-go/aws/credentials/stscreds github.com/aws/aws-sdk-go/aws/credentials/endpointcreds github.com/aws/aws-sdk-go/aws/defaults github.com/aws/aws-sdk-go/aws/session github.com/aws/aws-sdk-go/private/protocol/restxml github.com/aws/aws-sdk-go/service/s3 github.com/google/subcommands github.com/mattn/go-runewidth github.com/gosuri/uitable/util/strutil github.com/gosuri/uitable/util/wordwrap github.com/gosuri/uitable os/signal github.com/nsf/termbox-go github.com/jroimartin/gocui github.com/kotakanbe/go-cve-dictionary/log github.com/kotakanbe/go-cve-dictionary/config github.com/kotakanbe/go-cve-dictionary/util gopkg.in/cheggaaa/pb.v1 github.com/kotakanbe/go-cve-dictionary/jvn github.com/kotakanbe/go-cve-dictionary/nvd github.com/kotakanbe/go-cve-dictionary/db golang.org/x/net/websocket github.com/nlopes/slack net/mail net/smtp text/template/parse text/template hash/fnv runtime/debug github.com/boltdb/bolt github.com/future-architect/vuls/cache os/exec github.com/mitchellh/go-homedir golang.org/x/crypto/curve25519 golang.org/x/crypto/ed25519/internal/edwards25519 golang.org/x/crypto/ed25519 golang.org/x/crypto/internal/subtle golang.org/x/crypto/internal/chacha20 golang.org/x/crypto/poly1305 golang.org/x/crypto/ssh golang.org/x/crypto/ssh/agent github.com/howeyc/gopass github.com/kotakanbe/go-pingscanner dh_auto_build: cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/<>/vuls-0.4.2\+git20180531.0.399a087/obj-x86_64-linux-gnu/src\" -v -p 1 github.com/future-architect/vuls github.com/future-architect/vuls/cache github.com/future-architect/vuls/commands github.com/future-architect/vuls/config github.com/future-architect/vuls/contrib/owasp-dependency-check/parser github.com/future-architect/vuls/models github.com/future-architect/vuls/oval github.com/future-architect/vuls/report github.com/future-architect/vuls/scan github.com/future-architect/vuls/util returned exit code 2 make: *** [debian/rules:4: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vuls.html where you can get a full build log if you need it. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: vuls Source-Version: 0.6.1-1 We believe that the bug you reported is fixed in the latest version of vuls, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for
Bug#917596: Bug #917596 in vuls marked as pending
Control: tag -1 pending Hello, Bug #917596 in vuls 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: https://salsa.debian.org/go-team/packages/vuls/commit/90d7db4d7f95e68f54e9aace6d8dec62bcc1f2b3 Add bts number (Closes: #917596) Signed-off-by: Nobuhiro Iwamatsu (this message was generated automatically) -- Greetings https://bugs.debian.org/917596
Processed: Bug #917596 in vuls marked as pending
Processing control commands: > tag -1 pending Bug #917596 [src:vuls] vuls: FTBFS Added tag(s) pending. -- 917596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919326: msmtp: account default not found: no configuration file available
Processing commands for cont...@bugs.debian.org:
> forcemerge 919323 919326
Bug #919323 {Done: Emmanuel Bouthenot } [msmtp] msmtp:
apparmor blocks reading configuration file ~/.msmtprc
Bug #919326 [msmtp] msmtp: account default not found: no configuration file
available
Severity set to 'important' from 'grave'
Marked Bug as done
Marked as fixed in versions msmtp/1.8.2-1.
Merged 919323 919326
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919323
919326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Hand #917712 over to cmdtest
Processing commands for cont...@bugs.debian.org: > reassign 917712 cmdtest Bug #917712 [src:gitano] gitano: FTBFS: dh_auto_test: make -j1 test returned exit code 2 Bug reassigned from package 'src:gitano' to 'cmdtest'. No longer marked as found in versions gitano/1.1.1-1. Ignoring request to alter fixed versions of bug #917712 to the same values previously set > retitle 917712 Yarn fails to parse markdown code blocks properly Bug #917712 [cmdtest] gitano: FTBFS: dh_auto_test: make -j1 test returned exit code 2 Changed Bug title to 'Yarn fails to parse markdown code blocks properly' from 'gitano: FTBFS: dh_auto_test: make -j1 test returned exit code 2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 917712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919326: msmtp: account default not found: no configuration file available
forcemerge 919323 919326
thanks
Hi,
On Mon, Jan 14, 2019 at 04:40:36PM -0600, Sergio Mendoza wrote:
[...]
> A few days ago, msmtp fails to work. It all seems to be related to the
> inability to read ~/.msmtprc file. In other words it seems that
Merging and closing this bug as it is fixed with the last upload.
Regards,
--
Emmanuel Bouthenot
mail: kolter@{openics,debian}.orggpg: 4096R/0x929D42C3
xmpp: kol...@im.openics.org irc: kolter@{freenode,oftc}
Bug#917898: marked as done (libvisual-0.4-dev: Broken include path in pkg-config file)
Your message dated Fri, 18 Jan 2019 03:52:02 + with message-id and subject line Bug#917898: fixed in libvisual 0.4.0-15 has caused the Debian Bug report #917898, regarding libvisual-0.4-dev: Broken include path in pkg-config file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917898 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libvisual-0.4-dev Version: 0.4.0-14 Severity: grave Justification: renders package unusable Hello, $ pkg-config --cflags libvisual-0.4 -I/usr/include/libvisual-0.4 $ ls /usr/include/libvisual-0.4 ls: cannot access '/usr/include/libvisual-0.4': No such file or directory Only /usr/include/libvisual exists. It's not clear to me why it was renamed, having the major/API version in the subdirectory name is good practice, so that in case a new version with a different API/ABI is made it can be installed in parallel. In any case, this will cause everyone who uses this package via 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, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvisual-0.4-dev depends on: ii libc6-dev [libc-dev] 2.27-5 ii libvisual-0.4-0 0.4.0-14 ii pkg-config0.29-4+b1 libvisual-0.4-dev recommends no packages. libvisual-0.4-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libvisual Source-Version: 0.4.0-15 We believe that the bug you reported is fixed in the latest version of libvisual, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joao Eriberto Mota Filho (supplier of updated libvisual package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 18 Jan 2019 00:28:02 -0200 Source: libvisual Binary: libvisual-0.4-dev libvisual-0.4-0 Architecture: source Version: 0.4.0-15 Distribution: unstable Urgency: medium Maintainer: Joao Eriberto Mota Filho Changed-By: Joao Eriberto Mota Filho Description: libvisual-0.4-0 - audio visualization framework libvisual-0.4-dev - audio visualization framework (development files) Closes: 917898 Changes: libvisual (0.4.0-15) unstable; urgency=medium . * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field. * debian/control: bumped Standards-Version to 4.3.0. * debian/copyright: updated packaging copyright years. * debian/libvisual-0.4-dev.install: reverted the path for include/ directory. I will use a symlink to fix the problem pointed in 0.4.0-13 revision. Thanks to Tim Müller . (Closes: #917898) * debian/libvisual-0.4-dev.links: added to create a symlink as a workaround to fix the include path called by each header file. Checksums-Sha1: 8f8253d2fad1bf4c74f753129c171b60f3bf9abf 1989 libvisual_0.4.0-15.dsc afea6aaed5fa09a2e3881bccaaa3b3563ed34aac 19668 libvisual_0.4.0-15.debian.tar.xz 7c521de49b2cfa94e1fb2adc6318dd0fb3f9f72b 4990 libvisual_0.4.0-15_source.buildinfo Checksums-Sha256: 4323a389ff277ec9634a2fc5081a33034e9c005e48e85e789f49e7014e20b3ec 1989 libvisual_0.4.0-15.dsc 235219038fa65b84c0300a9a0a4cc40f67081f159fa214218e18577a41ea4734 19668 libvisual_0.4.0-15.debian.tar.xz 4845fcc616f47efc5f97e8461f4b430ace4a08dd230c64c93b3f7211e5205c05 4990 libvisual_0.4.0-15_source.buildinfo Files: c6d0dd32899fade0817288a35061bc91 1989 devel optional libvisual_0.4.0-15.dsc 772fc92e2a9a4adab7de3c5f99d68320 19668 devel optional libvisual_0.4.0-15.debian.tar.xz e042228a395bf6eaa42af065109755b5 4990 devel optional libvisual_0.4.0-15_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#919625: neutron-fwaas-common: fails to remove: neutron-plugin-manage disable: error: argument --service-plugin: invalid choice: 'firewall_v2'
Package: neutron-fwaas-common
Version: 1:13.0.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
>From the attached log (scroll to the bottom...):
Removing neutron-fwaas-common (1:13.0.1-4) ...
usage: neutron-plugin-manage disable [-h]
[--service-plugin
{auto_allocate,dummy,flavors,log,loki,metering,network_ip_availability,port_forwarding,qos,revisions,router,segments,tag,timestamp,trunk}]
[--l3-extension
{fip_qos,port_forwarding}]
{enable,disable} ...
neutron-plugin-manage disable: error: argument --service-plugin: invalid
choice: 'firewall_v2' (choose from 'auto_allocate', 'dummy', 'flavors', 'log',
'loki', 'metering', 'network_ip_availability', 'port_forwarding', 'qos',
'revisions', 'router', 'segments', 'tag', 'timestamp', 'trunk')
dpkg: error processing package neutron-fwaas-common (--remove):
installed neutron-fwaas-common package post-removal script subprocess
returned error exit status 2
cheers,
Andreas
neutron-fwaas-common_1:13.0.1-4.log.gz
Description: application/gzip
Bug#919623: Remote code execution in scp support
Package: rssh
Version: 2.3.4-8
Severity: grave
Tags: security upstream
https://sourceforge.net/p/rssh/mailman/message/36519118/ is the upstream
report. The reporter indicated they asked for a CVE but didn't include it
in the message.
scp allows remote code execution inside the server environment via several
methods due to inadequate command-line verification. This bug has been
present since the beginning of rssh.
I have a completely untested patch but haven't had time to test it yet.
Attaching it to this report for whatever it's worth.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rssh depends on:
ii debconf [debconf-2.0] 1.5.69
ii libc6 2.28-4
ii openssh-server 1:7.9p1-4
rssh recommends no packages.
Versions of packages rssh suggests:
ii cvs 2:1.12.13+real-26
pn makejail
pn rdist
ii rsync 3.1.3-1
ii subversion 1.10.3-1+b1
-- Configuration Files:
/etc/logcheck/ignore.d.server/rssh [Errno 13] Permission denied:
'/etc/logcheck/ignore.d.server/rssh'
/etc/rssh.conf changed [not included]
-- debconf information excluded
diff --git a/util.c b/util.c
index 56f67ad..4dde1a0 100644
--- a/util.c
+++ b/util.c
@@ -268,6 +268,45 @@ static int rsync_e_okay( char **vec )
}
+/*
+ * scp_okay() - take the command line and check that it is a hopefully-safe scp
+ * server command line, accepting only very specific options.
+ * Returns FALSE if the command line should not be allowed, TRUE
+ * if it is okay.
+ */
+static int scp_okay( char **vec )
+{
+ int saw_file = FALSE;
+ int saw_end = FALSE;
+
+ for ( ; vec && *vec; vec++ ){
+ /* Allowed options. */
+ if ( !saw_end ) {
+ if ( strcmp(*vec, "-v") == 0 ) continue;
+ if ( strcmp(*vec, "-r") == 0 ) continue;
+ if ( strcmp(*vec, "-p") == 0 ) continue;
+ if ( strcmp(*vec, "-d") == 0 ) continue;
+ if ( strcmp(*vec, "-f") == 0 ) continue;
+ if ( strcmp(*vec, "-t") == 0 ) continue;
+ }
+
+ /* End of arguments. One more argument allowed after this. */
+ if ( !saw_end && strcmp(*vec, "--") == 0 ){
+ saw_end = TRUE;
+ continue;
+ }
+
+ /* No other options allowed, but allow file starting with -. */
+ if ( *vec[0] == '-' && !saw_end ) return FALSE;
+ if ( saw_file ) return FALSE;
+ saw_file = TRUE;
+ }
+
+ /* We must have seen a single file. */
+ return saw_file;
+}
+
+
/*
* check_command_line() - take the command line passed to rssh, and verify
* that the specified command is one the user is
@@ -283,8 +322,11 @@ char *check_command_line( char **cl, ShellOptions_t *opts )
return PATH_SFTP_SERVER;
if ( check_command(*cl, opts, PATH_SCP, RSSH_ALLOW_SCP) ){
- /* filter -S option */
- if ( opt_filter(cl, 'S') ) return NULL;
+ if ( !scp_okay(cl) ){
+ fprintf(stderr, "\ninsecure scp option not allowed.");
+ log_msg("insecure scp option in scp command line");
+ return NULL;
+ }
return PATH_SCP;
}
Processed: tagging 864113, tagging 888130, tagging 905449
Processing commands for cont...@bugs.debian.org: > tags 864113 + sid buster Bug #864113 [src:libgnome-keyring] libgnome-keyring: Please stop Build-Depending on libgcrypt11-dev transition package Added tag(s) buster and sid. > tags 888130 + experimental Bug #888130 [src:ruby-net-http-persistent] ruby-net-http-persistent: FTBFS on ruby2.5: ssl verification fails Added tag(s) experimental. > tags 905449 + sid buster Bug #905449 [libfsharp-core4.3-cil] libfsharp-core4.3-cil: It is impossible to configure libfsharp-core4.3-cil package Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 864113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864113 888130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888130 905449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: whitedune: diff for NMU version 0.30.10-2.2
Processing control commands: > clone -1 -2 Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the whitedune package Bug 916468 cloned as bug 919622 > reassign -2 dune 1.6.2-1 Bug #919622 [whitedune] dune: /usr/bin/dune is already provided by the whitedune package Bug reassigned from package 'whitedune' to 'dune'. No longer marked as found in versions whitedune/0.30.10-2.1. Ignoring request to alter fixed versions of bug #919622 to the same values previously set Bug #919622 [dune] dune: /usr/bin/dune is already provided by the whitedune package Marked as found in versions dune/1.6.2-1. > retitle -2 dune: needs Breaks+Replaces: whitedune (<< 0.30.10-2.2) Bug #919622 [dune] dune: /usr/bin/dune is already provided by the whitedune package Changed Bug title to 'dune: needs Breaks+Replaces: whitedune (<< 0.30.10-2.2)' from 'dune: /usr/bin/dune is already provided by the whitedune package'. > tags -2 = Bug #919622 [dune] dune: needs Breaks+Replaces: whitedune (<< 0.30.10-2.2) Removed tag(s) patch, buster, pending, and sid. -- 916468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916468 919622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#916468: whitedune: diff for NMU version 0.30.10-2.2
Control: clone -1 -2 Control: reassign -2 dune 1.6.2-1 Control: retitle -2 dune: needs Breaks+Replaces: whitedune (<< 0.30.10-2.2) Control: tags -2 = On Tue, 15 Jan 2019 21:16:00 +0100 Paul Gevers wrote: > I've prepared an NMU for whitedune (versioned as 0.30.10-2.2) and If whitedune is going to drop the symlink, and dune is not getting renamed, dune needs to add appropriate Breaks+Replaces. Andreas
Bug#916468: Conflict over /usr/bin/dune
On Tue, 18 Dec 2018 17:48:06 + Ian Jackson
wrote:
> Ian Jackson writes ("Re: Conflict over /usr/bin/dune"):
> > https://www.google.com/search?q=dune+software
> > https://en.wikipedia.org/wiki/Dune_(software)
> > https://www.google.com/search?q=%2Fusr%2Fbin%2Fdune
> >
> > Under the circumstances it seems obvious that, at the very least, the
> > ocaml build tool should not be allowed the name /usr/bin/dune.
>
> Perhaps I should have stated this explicitly, since it was not obvious
> unless you follow the links.
>
> `Dune' is not, as a piece of software, primarily either the ocaml
> build tool, or the 3D modeller.
>
> Mostly it is DUNE, a "modular C++ library for the solution of partial
> differential equations using grid-based methods". That's what you get
> if you visit the Wikipedia link I provided - not even a disambiguation
> link. The others don't rate a mention.
That C++ library is also something I was expecting to have this
(meta-)package called dune.
If the ocaml build system wants to stay within the theme, what about
"camel" ? And once they find out that there is already camel.apache.org,
rename it again to "hump" (which seems to be available).
Andreas
Bug#917898: libvisual-0.4-dev: Broken include path in pkg-config file
Hi Tim, Em seg, 31 de dez de 2018 às 11:54, Tim Müller escreveu: > > $ pkg-config --cflags libvisual-0.4 > -I/usr/include/libvisual-0.4 > > $ ls /usr/include/libvisual-0.4 > ls: cannot access '/usr/include/libvisual-0.4': No such file or directory > > Only /usr/include/libvisual exists. It's not clear to me why it was renamed, > having the major/API version in the subdirectory name is good practice, so > that in case a new version with a different API/ABI is made it can be > installed in parallel. I adopted libvisual some years ago. Originally, it was installing include files in '/usr/include/libvisual-0.4'. In november 2018, I created a test for autopkgtest (debian/tests/). The test called all .h files and failed because these headers called '/usr/include/libvisual'. So, I "fixed" the path for include files in 0.4.0-13 revision. I will revert this action and add a symlink to fix the problem without more noising. > In any case, this will cause everyone who uses this package via pkg-config > (e.g. gst-plugins-base) to FTBFS. > > Cheers > Tim Thanks! Cheers, Eriberto Hi Tim, I adopted
Bug#919617: python-gpiozero file conflict with python3-gpiozero
Package: python-gpiozero Version: 1.4.1-1 Severity: serious The 1.4.1-1 upload of gpiozero added the "pinout" utility, unfortunately it added it to both the python-gpiozero and python3-gpiozero packages. The result is a file conflict between the two packages. I see two possible solutions. 1. Drop the utility from one of the packages, if going down this road I would probablly drop it from the python-gpiozero package since python 2 is deprecated. 2. Install the utility with a different name or path in each package and then use the alternatives mechanism to select between them.
Bug#916952: marked as done (ppl FTBFS with swi-prolog 7.7.25+dfsg-2)
Your message dated Fri, 18 Jan 2019 00:35:22 + with message-id and subject line Bug#916952: fixed in ppl 1:1.2-4 has caused the Debian Bug report #916952, regarding ppl FTBFS with swi-prolog 7.7.25+dfsg-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ppl Version: 1:1.2-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html ... checking which interfaces are enabled... cxx c swi_prolog checking for swipl... /usr/bin/swipl swipl: Usage: 1) swipl [options] prolog-file ... [-- arg ...] 2) swipl [options] [-o executable] -c prolog-file ... 3) swipl --help Display this message (also -h) 4) swipl --version Display version information 4) swipl --arch Display architecture 6) swipl --dump-runtime-variables[=format] Dump link info in sh(1) format Options: -x state Start from state (must be first) -g goal Run goal (may be repeated) -t toplevel Toplevel goal -f file User initialisation file -F file Site initialisation file -l file Script source file -s file Script source file -p alias=pathDefine file search path 'alias' -O Optimised compilation --tty[=bool] (Dis)allow tty control --signals[=bool] Do (not) modify signal handling --threads[=bool] Do (not) allow for threads --debug[=bool] Do (not) generate debug info --quiet[=bool] (-q) Do (not) suppress informational messages --traditionalDisable extensions of version 7 --home=DIR Use DIR as SWI-Prolog home --stack_limit=size[BKMG] Specify maximum size of Prolog stacks --table_space=size[BKMG] Specify maximum size of SLG tables --pldoc[=port] Start PlDoc server [at port] ... dh_install -s --sourcedir=debian/tmp dh_install: -s/--same-arch is deprecated; please use -a/--arch instead dh_install: This feature will be removed in compat 12. dh_install: Cannot find (any matches for) "usr/lib/*/ppl/libppl_swiprolog.so" (tried in debian/tmp, debian/tmp) dh_install: libppl-swi missing files: usr/lib/*/ppl/libppl_swiprolog.so dh_install: Cannot find (any matches for) "usr/lib/*/ppl/libppl_swiprolog.a" (tried in debian/tmp, debian/tmp) dh_install: libppl-swi missing files: usr/lib/*/ppl/libppl_swiprolog.a dh_install: Cannot find (any matches for) "usr/share/ppl/ppl_swiprolog.*" (tried in debian/tmp, debian/tmp) dh_install: libppl-swi missing files: usr/share/ppl/ppl_swiprolog.* dh_install: missing files, aborting make: *** [debian/rules:162: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: ppl Source-Version: 1:1.2-4 We believe that the bug you reported is fixed in the latest version of ppl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Clarke (supplier of updated ppl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 23:43:15 + Source: ppl Binary: libppl14 libppl-dev ppl-dev libppl-c4 libppl-doc libppl-swi Architecture: source Version: 1:1.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: James Clarke Description: libppl-c4 - Parma Polyhedra Library (C interface) libppl-dev - Parma Polyhedra Library (development) libppl-doc - Parma Polyhedra Library: Documentation libppl-swi - Parma Polyhedra Library (SWI Prolog interface) libppl14 - Parma Polyhedra Library (runtime library) ppl-dev- Parma Polyhedra Library (development binaries) Closes: 849319 916952 Changes: ppl (1:1.2-4) unstable; urgency=medium . * Team upload. * fix_AC_CHECK_SWI_PROLOG.patch: New patch to fix build with swi-prolog 7.7.25+dfsg-2 (Closes: #916952) * Add pkg.ppl.no-swi-prolog profile to r
Bug#919578: marked as done (rozofs: FTBFS with undefined references to major, minor)
Your message dated Fri, 18 Jan 2019 00:56:21 + with message-id and subject line Bug#919568: Removed package(s) from experimental has caused the Debian Bug report #919578, regarding rozofs: FTBFS with undefined references to major, minor to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rozofs Version: 2.6.2-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, rozofs recently started to FTBFS in an up-to-date sid+experimental pbuilder environment: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/rozofs-2.6.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fmessage-length=0 -O3 -DNDEBUG -D_GNU_SOURCE -g -Wl,-z,relr o -Wl,-z,now -rdynamic CMakeFiles/storio.dir/sconfig.c.o CMakeFiles/storio.dir/storage.c.o CMakeFiles/storio.dir/sproto_nb.c.o CMakeFiles/storio.dir/sprotosvc_nb.c.o CMakeFiles/storio.dir/storio_nblock_init.c.o C MakeFiles/storio.dir/storio_north_intf.c.o CMakeFiles/storio.dir/storage_fd_cache.c.o CMakeFiles/storio.dir/storio.c.o CMakeFiles/storio.dir/storio_cache.c.o CMakeFiles/storio.dir/storio_bufcache.c.o CMakeFiles/s torio.dir/storio_disk_thread_intf.c.o CMakeFiles/storio.dir/storio_device_monitor.c.o CMakeFiles/storio.dir/storio_disk_thread.c.o CMakeFiles/storio.dir/storio_device_mapping.c.o CMakeFiles/storio.dir/storio_seri alization.c.o CMakeFiles/storio.dir/storio_fid_cache.c.o CMakeFiles/storio.dir/storio_crc32.c.o -o storio -L/build/rozofs-2.6.2/obj-x86_64-linux-gnu/rozofs ../../rozofs/librozofs.a -lpthread -luuid -lconfig -ln uma /usr/bin/ld: CMakeFiles/storio.dir/storio_device_monitor.c.o: in function `storio_device_get_major_and_minor': ./obj-x86_64-linux-gnu/src/storaged/./src/storaged/storio_device_monitor.c:488: undefined reference to `major' /usr/bin/ld: ./obj-x86_64-linux-gnu/src/storaged/./src/storaged/storio_device_monitor.c:489: undefined reference to `minor' collect2: error: ld returned 1 exit status Cheers, Andreas rozofs_2.6.2-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Version: 2.6.2-2+rm Dear submitter, as the package rozofs has just been removed from the Debian archive experimental we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/919568 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#918739: marked as done (node-duplexer2 FTBFS with nodejs 10.15.0)
Your message dated Fri, 18 Jan 2019 00:46:05 + with message-id and subject line Bug#919575: Removed package(s) from unstable has caused the Debian Bug report #918739, regarding node-duplexer2 FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-duplexer2 Version: 0.1.4-1 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-duplexer2.html ... mocha -R tap 1..14 ok 1 duplexer2 should interact with the writable stream properly for writing ok 2 duplexer2 should interact with the readable stream properly for reading ok 3 duplexer2 should end the writable stream, causing it to finish ok 4 duplexer2 should finish when the writable stream finishes ok 5 duplexer2 should end when the readable stream ends ok 6 duplexer2 should bubble errors from the writable stream when no behaviour is specified ok 7 duplexer2 should bubble errors from the readable stream when no behaviour is specified ok 8 duplexer2 should bubble errors from the writable stream when bubbleErrors is true ok 9 duplexer2 should bubble errors from the readable stream when bubbleErrors is true ok 10 duplexer2 should not bubble errors from the writable stream when bubbleErrors is false ok 11 duplexer2 should not bubble errors from the readable stream when bubbleErrors is false ok 12 duplexer2 should work with streams1 ok 13 duplexer2 should export the DuplexWrapper constructor not ok 14 duplexer2 should not force flowing-mode AssertionError [ERR_ASSERTION]: false == null at Context. (test/tests.js:195:12) at callFnAsync (/usr/lib/nodejs/mocha/lib/runnable.js:377:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:324:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at /usr/lib/nodejs/mocha/lib/runner.js:329:7 at done (/usr/lib/nodejs/mocha/lib/runnable.js:301:5) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:372:7) at Hook.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at next (/usr/lib/nodejs/mocha/lib/runner.js:304:10) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) # tests 14 # pass 13 # fail 1 make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Version: 0.1.4-1+rm Dear submitter, as the package node-duplexer2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/919575 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#896295: marked as done (python3-keras: keras fails to import)
Your message dated Fri, 18 Jan 2019 00:21:30 +
with message-id
and subject line Bug#896295: fixed in keras 2.2.4-1
has caused the Debian Bug report #896295,
regarding python3-keras: keras fails to import
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
896295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-keras
Version: 2.1.5-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python3-keras importing the module keras
into a python interpreter fails with the following error:
Using TensorFlow backend.
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/keras/__init__.py", line 3, in
from . import utils
File "/usr/lib/python3/dist-packages/keras/utils/__init__.py", line 6, in
from . import conv_utils
File "/usr/lib/python3/dist-packages/keras/utils/conv_utils.py", line 9, in
from .. import backend as K
File "/usr/lib/python3/dist-packages/keras/backend/__init__.py", line 84, in
from .tensorflow_backend import *
File "/usr/lib/python3/dist-packages/keras/backend/tensorflow_backend.py",
line 5, in
import tensorflow as tf
ModuleNotFoundError: No module named 'tensorflow'
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Source: keras
Source-Version: 2.2.4-1
We believe that the bug you reported is fixed in the latest version of
keras, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 896...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Stender (supplier of updated keras package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 17 Jan 2019 23:44:17 +0100
Source: keras
Binary: python3-keras keras-doc
Architecture: source all
Version: 2.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Daniel Stender
Description:
keras-doc - CPU/GPU math expression compiler for Python (docs)
python3-keras - deep learning framework running on Theano or TensorFlow
Closes: 896295
Changes:
keras (2.2.4-1) unstable; urgency=medium
.
* Team upload.
.
[ Stephen Sinclair ]
* New upstream version 2.2.4.
* debian/control:
+ update standards to 4.3.0.
+ add BD for new keras-related packages,
namely keras-preprocessing, keras-applications.
+ remove promise of TensorFlow packaging.
* debian/rules:
+ update tests to ignore.
+ fix cwd for running tests.
+ use find for removing unwanted files.
+ support DEB_BUILD_OPTIONS=nodoc.
+ remove bundled files and depend on libjs-jquery for docs.
+ remove bundled filed and depend on libjs-mustache for docs.
+ remove bundled files and depend on fonts-font-awesome for docs.
+ enable DH_VERBOSE=1.
+ add LANG=C.UTF-8 for links.
+ remove a commented DEB_BUILD_OPTIONS.
* debian/tests:
+ add autopkgtest for default config without specifying backend.
* debian/patches:
+ rebase patches.
+ ensure "docs" is not discovered as a module to install by setuptools.
+ Change default backend to theano (Closes: #896295).
* debian/copyright:
+ add all *.pyc and __pycache__ files to Files-Excluded.
+ update year to 2019.
* debian/gitlab-ci.yml:
+ add support for salsa gitlab CI.
* debian/clean:
+ add docs/sources, docs/html, docs/.pybuild and .pybuild.
* Specify keras-applications and keras-preprocessing versions.
* Do not call dh with mkdocs when nodoc.
.
[ Dmitry Shachnev ]
* Use dh_mkdocs instead of unbundling static files manually.
Checksums-Sha1:
c8263554ed70e5fc1fb009eb651e96e
Bug#919609: minetest-mod-pycraft: FTBFS in sid (module 'socket.cx64' not found)
Package: src:minetest-mod-pycraft Version: 0.20+git20180331.0376a0a+dfsg-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config -i dh_autoreconf -i debian/rules override_dh_auto_test make[1]: Entering directory '/<>/minetest-mod-pycraft-0.20+git20180331.0376a0a+dfsg' busted . * 0 successes / 0 failures / 1 error / 0 pending : 0.002579 seconds Error -> ./socket.lua @ 21 suite ./tests/pycraft_spec.lua ./socket.lua:21: module 'socket.cx64' not found: no field package.preload['socket.cx64'] no file '../socket/cx64.lua' no file './src/socket/cx64.lua' no file './src/socket/cx64/socket/cx64.lua' no file './src/socket/cx64/init.lua' no file '/usr/local/share/lua/5.2/socket/cx64.lua' no file '/usr/local/share/lua/5.2/socket/cx64/init.lua' no file '/usr/local/lib/lua/5.2/socket/cx64.lua' no file '/usr/local/lib/lua/5.2/socket/cx64/init.lua' no file '/usr/share/lua/5.2/socket/cx64.lua' no file '/usr/share/lua/5.2/socket/cx64/init.lua' no file './socket/cx64.lua' no file 'some/path/socket/cx64.lua' no file './csrc/socket/cx64.so' no file './csrc/socket/cx64/socket/cx64.so' no file '/usr/local/lib/lua/5.2/socket/cx64.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.2/socket/cx64.so' no file '/usr/lib/lua/5.2/socket/cx64.so' no file '/usr/local/lib/lua/5.2/loadall.so' no file './socket/cx64.so' no file 'some/path/socket/cx64.so' no file './csrc/socket.so' no file './csrc/socket/socket.so' no file '/usr/local/lib/lua/5.2/socket.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.2/socket.so' no file '/usr/lib/lua/5.2/socket.so' no file '/usr/local/lib/lua/5.2/loadall.so' no file './socket.so' no file 'some/path/socket.so' make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 make[1]: Leaving directory '/<>/minetest-mod-pycraft-0.20+git20180331.0376a0a+dfsg' make: *** [debian/rules:4: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minetest-mod-pycraft.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks.
Bug#917758: jabberd2: FTBFS: mysql-related errors
Control: forwarded -1 https://github.com/jabberd2/jabberd2/issues/193
Hi Lucas,
please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36:
> error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
>
> This is not a bug. MYSQL.reconnect was not part of the API, even in 5.5
> https://dev.mysql.com/doc/refman/5.5/en/c-api-auto-reconnect.html
Your relevant error seems to be (without terminal coloration ;-)):
authreg_mysql.c: In function 'ar_init':
authreg_mysql.c:631:9: error: 'MYSQL' {aka 'struct st_mysql'} has no member
named 'reconnect'
conn->reconnect = 1;
Regards,
Faustin
Bug#919373: kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14:
Control: forwarded -1 https://redmine.kannel.org/issues/795 Hi, This seems to be a bug (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36): > error: 'MYSQL_SERVER_VERSION' undeclared > > this looks like a bug. MYSQL_SERVER_VERSION is documented here: > https://dev.mysql.com/doc/refman/5.5/en/c-api-server-client-versions.html Regards, Faustin
Bug#918393: opensips FTBFS with MariaDB 10.3
Hi Adrian,
in case you did not saw this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36
> error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
>
> This is not a bug. MYSQL.reconnect was not part of the API, even in 5.5
> https://dev.mysql.com/doc/refman/5.5/en/c-api-auto-reconnect.html
Regards,
Faustin
Processed: Re: jabberd2: FTBFS: mysql-related errors
Processing control commands: > forwarded -1 https://github.com/jabberd2/jabberd2/issues/193 Bug #917758 [src:jabberd2] jabberd2: FTBFS: mysql-related errors Set Bug forwarded-to-address to 'https://github.com/jabberd2/jabberd2/issues/193'. -- 917758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14:
Processing control commands: > forwarded -1 https://redmine.kannel.org/issues/795 Bug #919373 [src:kannel] kannel: FTBFS with mariadb-10.3: gwlib/utils.c:602:14: error: 'MYSQL_SERVER_VERSION' undeclared Set Bug forwarded-to-address to 'https://redmine.kannel.org/issues/795'. -- 919373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918387: lua-sql FTBFS with MariaDB 10.3
Control: forwarded -1 https://github.com/keplerproject/luasql/issues/108 Hi, in case you did not saw this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36 > this looks like a bug. MYSQL_SERVER_VERSION is documented here: > https://dev.mysql.com/doc/refman/5.5/en/c-api-server-client-versions.html Regards, Faustin
Processed: Re: lua-sql FTBFS with MariaDB 10.3
Processing control commands: > forwarded -1 https://github.com/keplerproject/luasql/issues/108 Bug #918387 [src:lua-sql] lua-sql FTBFS with MariaDB 10.3 Set Bug forwarded-to-address to 'https://github.com/keplerproject/luasql/issues/108'. -- 918387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: opensips FTBFS with MariaDB 10.3
Processing commands for cont...@bugs.debian.org: > forwarded 918393 https://github.com/OpenSIPS/opensips/issues/1589 Bug #918393 [src:opensips] opensips FTBFS with MariaDB 10.3 Set Bug forwarded-to-address to 'https://github.com/OpenSIPS/opensips/issues/1589'. > End of message, stopping processing here. Please contact me if you need assistance. -- 918393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919529: CVE-2019-6256
On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote: > Control: found -1 2016.11.28-1 > > On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote: > > Source: liblivemedia > > Severity: grave > > Tags: security > > > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256 > > > > Cheers, > > Moritz > > Not sure if I'm missing something, but the PoC does not seem to work on > buster/sid. Quite possible, I hadn't reproduced it myself yet and upstream homepage wasn't that obvious wrt existing fixes. Cheers, Moritz
Bug#919500: golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494)
Am 17.01.2019 um 06:09 schrieb Arnaud Rebillout: > Dear Go team, > > I pushed a fix on Salsa, can you please review and upload these changes? > Thanks! Hi Arnaud, thanks for your fix, it's uploaded now with a minor change (I've removed the Debian version "-1" from the build dependency golang-goprotobuf-dev). Regards, Tobias signature.asc Description: OpenPGP digital signature
Bug#918163: Broken in Stretch
On Thu, Jan 17, 2019 at 12:39:26PM +, Martín Ferrari wrote: > tags 918163 stretch > thanks > > > On 03/01/2019 22:18, Moritz Muehlenhoff wrote: > > > The plugin is broken with Thunderbird 60 in stretch, after installation > > it's disabled and only prints "Sieve is incompatible with Thunderbird 60.4". > > There is something I only realise now about this.. The version already > in buster works OK, I thought I needed to update to 3.0 (which I will do > anyway for sid), what would be preferred for stable-updates? For stable-proposed-updates such Xul extensions are usually bumped to the latest version, see the release.debian.org pseudo bug for some examples. Cheers, Moritz
Bug#919415: isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev
Control: tags -1 + patch Control: forwarded -1 https://salsa.debian.org/mactel-team/isight-firmware-tools/merge_requests/1 On Tue, Jan 15, 2019 at 03:15:57PM +0100, Andreas Beckmann wrote: > Source: isight-firmware-tools > Version: 1.6-3 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > isight-firmware-tools build-depends on libgcrypt11-dev. This was a > transitional package, please use libgcrypt20-dev instead. I can confirm the fix seems to be as simple as just replacing libgcrypt11-dev with libgcrypt20-dev in the build-dependencies. (Atleast the package builds, I haven't done any other tests.) For your convenience I've submitted a merge request with the fix, and as a bonus also the translation update see above. Regards, Andreas Henriksson
Bug#919594: memkind: baseline violation on amd64 (and FTBFS everywhere else)
On Thu, Jan 17, 2019 at 08:04:09PM +0200, Adrian Bunk wrote: > Source: memkind > Version: 1.8.0-1 > Severity: serious > > https://buildd.debian.org/status/package.php?p=memkind&suite=sid > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/memkind.html > > memkind builds for no apparent reason with -msse4.2, Accent on "no apparent reason" -- there's only a single instruction, called as : _mm_crc32_u64() -- and it's #ifdefed out. > which is a baseline violation even on amd64. I've verified that the 1.8.0-1 packages work ok on an AMD Phenom2 (ie, without SSE4.2), thus there's no actual violation. You're right that this causes noise for people doing QA work like you, though, and it'd be good to patch this away. > Build failures on other architectures seem to be often > related to using an internal copy of jemalloc instead > of the version in Debian. Yeah, I've looked into using shipped jemalloc; this was not an option at the time I uploaded this to NEW as memkind needs jemalloc >= 5.0 which wasn't available then and the transition seemed unlikely in time for Buster. We do actually have 5.1 in now, though -- but, I'm talking to upstream to see if patches they applied atop of jemalloc are actually needed. The one for defrag seems unused, but I'm worried about the dlopen() one -- vanilla jemalloc can't be dlopened because of something something too much TLS data. No idea if you've heard of this problem; I'm mentioning this in case you did. I prepared _apparently_ ok patches that fix this and all portability problems for 64-bit archs, but only during some testing I noticed that those "obviously correct" patches break something. Thus, I'm asking upstream how to run the testsuite on machines without any kind of special hardware memkind is meant for so we have at least _some_ automated checks. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands ⢿⡄⠘⠷⠚⠋⠀ for Privacy. ⠈⠳⣄
Processed: Re: isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev
Processing control commands: > tags -1 + patch Bug #919415 [src:isight-firmware-tools] isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev Added tag(s) patch. > forwarded -1 > https://salsa.debian.org/mactel-team/isight-firmware-tools/merge_requests/1 Bug #919415 [src:isight-firmware-tools] isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev Set Bug forwarded-to-address to 'https://salsa.debian.org/mactel-team/isight-firmware-tools/merge_requests/1'. -- 919415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#896531: marked as done (libsbml5-perl: Can't locate loadable object for module LibSBML)
Your message dated Thu, 17 Jan 2019 23:00:13 + with message-id and subject line Bug#896531: fixed in libsbml 5.17.2+dfsg-1 has caused the Debian Bug report #896531, regarding libsbml5-perl: Can't locate loadable object for module LibSBML to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 896531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsbml5-perl Version: 5.16.0+dfsg-2 Severity: grave User: debian-p...@lists.debian.org Usertags: use-failure This package seems unusable: # perl -e 'use LibSBML' Can't locate loadable object for module LibSBML in @INC (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/lib/x86_64-linux-gnu/perl5/5.26/LibSBML.pm line 11. Compilation failed in require at -e line 1. BEGIN failed--compilation aborted at -e line 1. This is also the case on stretch and jessie. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libsbml Source-Version: 5.17.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of libsbml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 896...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libsbml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 12:12:21 +0100 Source: libsbml Binary: libsbml5-dev libsbml5 python3-sbml5 libsbml5-java libsbml5-perl libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc libsbml5-cil-doc libsbml5-perl-doc python3-sbml5-doc Architecture: source amd64 all Version: 5.17.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libsbml5 - System Biology Markup Language library libsbml5-cil - System Biology Markup Language library - CLI bindings libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation libsbml5-dev - System Biology Markup Language library - development files libsbml5-doc - System Biology Markup Language library -- documentation libsbml5-examples - System Biology Markup Language library -- example files libsbml5-java - System Biology Markup Language library - Java bindings libsbml5-octave - System Biology Markup Language library - Octave bindings libsbml5-perl - System Biology Markup Language library - Perl bindings libsbml5-perl-doc - System Biology Markup Language library -- Perl documentation python3-sbml5 - System Biology Markup Language library - Python3 bindings python3-sbml5-doc - System Biology Markup Language library - Python3 documentation Closes: 847013 896531 901455 911482 Changes: libsbml (5.17.2+dfsg-1) unstable; urgency=medium . [ gregor herrmann ] * Fix Perl installdir Closes: #896531 . [ Andreas Tille ] * New upstream version * Point Vcs fields to salsa.debian.org * Standards-Version: 4.3.0 * debhelper 12 * Deal with issue in doclets by removing docs/src/SBMLDoclet.java * Remove libsbml-java-doc since doc does not build properly Closes: #901455, #911482 * Provide Python3 instead of Python2 bindings (SBML can only provide either Python2 or Python3 - lets do the switch now) Closes: #847013 * Secure URI in copyright format * Drop useless get-orig-source target * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target * Remove trailing whitespace in debian/changelog * Do not parse d/changelog * Build-Depends: libnewlib-dev, check * Remove Matlab related options from debian/cmake_opts (thanks for the hint to Nicolas Mora) * WITH_R=off (we do not build an R package and something is wrong with the R build) * Do not provide Java doc since there are errors when creating it and this solution was suggested by the Debian Java team * Fix Perl interpreter path * d/copyright: examp
Bug#919049: marked as done (posix-cpu-timers: Unbreak timer rearming (regression))
Your message dated Thu, 17 Jan 2019 23:00:16 +
with message-id
and subject line Bug#919049: fixed in linux 4.19.16-1
has caused the Debian Bug report #919049,
regarding posix-cpu-timers: Unbreak timer rearming (regression)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.19.13-1
Severity: serious
Tags: upstream patch
Justification: Regression / Causes FTBFS on glibc (testfailures)
Control: affects -1 src:glibc
Control: found -1 4.20-1~exp1
Control: forwarded -1 https://lkml.org/lkml/2018/12/30/169
Upstream fix 0e334db6bb4b ("posix-timers: Fix division by zero bug")
in 4.20 and backported to 4.19.13 causes for instance glibc testsuite
to fail.
References:
https://lkml.org/lkml/2018/12/30/169
https://bugzilla.redhat.com/show_bug.cgi?id=1662602
https://bugzilla.kernel.org/show_bug.cgi?id=202123
https://lore.kernel.org/lkml/2019033500.840117...@linutronix.de/
#919019 might actually be caused by the same, but not verified yet, so
keeping them distinct.
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.19.16-1
We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings (supplier of updated linux package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 17 Jan 2019 18:56:17 +
Source: linux
Binary: linux-source-4.19 linux-support-4.19.0-2 linux-doc-4.19 linux-cpupower
libcpupower1 libcpupower-dev usbip hyperv-daemons lockdep liblockdep4.19
liblockdep-dev libbpf4.19 libbpf-dev linux-kbuild-4.19 linux-perf-4.19
linux-bootwrapper-4.19.0-2 linux-headers-4.19.0-2-common
linux-headers-4.19.0-2-common-rt linux-libc-dev linux-headers-4.19.0-2-all
linux-headers-4.19.0-2-all-alpha linux-config-4.19
kernel-image-4.19.0-2-alpha-generic-di nic-modules-4.19.0-2-alpha-generic-di
nic-wireless-modules-4.19.0-2-alpha-generic-di
nic-shared-modules-4.19.0-2-alpha-generic-di
serial-modules-4.19.0-2-alpha-generic-di
usb-serial-modules-4.19.0-2-alpha-generic-di
ppp-modules-4.19.0-2-alpha-generic-di pata-modules-4.19.0-2-alpha-generic-di
cdrom-core-modules-4.19.0-2-alpha-generic-di
scsi-core-modules-4.19.0-2-alpha-generic-di
scsi-modules-4.19.0-2-alpha-generic-di loop-modules-4.19.0-2-alpha-generic-di
btrfs-modules-4.19.0-2-alpha-generic-di ext4-modules-4.19.0-2-alpha-generic-di
isofs-modules-4.19.0-2-alpha-generic-di jfs-modules-4.19.0-2-alpha-generic-di
xfs-modules-4.19.0-2-alpha-generic-di fat-modules-4.19.0-2-alpha-generic-di
md-modules-4.19.0-2-alpha-generic-di
multipath-modules-4.19.0-2-alpha-generic-di
usb-modules-4.19.0-2-alpha-generic-di
usb-storage-modules-4.19.0-2-alpha-generic-di
input-modules-4.19.0-2-alpha-generic-di event-modules-4.19.0-2-alpha-generic-di
mouse-modules-4.19.0-2-alpha-generic-di
nic-pcmcia-modules-4.19.0-2-alpha-generic-di
pcmcia-modules-4.19.0-2-alpha-generic-di
nic-usb-modules-4.19.0-2-alpha-generic-di
sata-modules-4.19.0-2-alpha-generic-di i2c-modules-4.19.0-2-alpha-generic-di
crc-modules-4.19.0-2-alpha-generic-di crypto-modules-4.19.0-2-alpha-generic-di
crypto-dm-modules-4.19.0-2-alpha-generic-di
ata-modules-4.19.0-2-alpha-generic-di nbd-modules-4.19.0-2-alpha-generic-di
squashfs-modules-4.19.0-2-alpha-generic-di
virtio-modules-4.19.0-2-alpha-generic-di zlib-modules-4.19.0-2-alpha-generic-di
compress-modules-4.19.0-2-alpha-generic-di
fuse-modules-4.19.0-2-alpha-generic-di srm-modules-4.19.0-2-alpha-generic-di
linux-image-4.19.0-2-alpha-generic linux-headers-4.19.0-2-alpha-generic
linux-image-4.19.0-2-alpha-generic-dbg linux-image-4.19.0-2-alpha-smp
linux-headers-4.19.0-2-alpha-smp linux-image-4.19.0-2-alpha-smp-dbg
linux-headers-4.19.0-2-all-amd64 kernel-image-4.19.0-2-amd64-di
nic-modules-4.19.0-2-amd64-di nic-wireless-modules-4.19.0-2-amd64-di
nic-shared-modules-4.19.0-2-amd64-di serial-modules-4.19.0-2-amd64-di
usb-serial-
Bug#901455: marked as done (FTBFS in sid: package com.sun.tools.doclets.standard is not visible)
Your message dated Thu, 17 Jan 2019 23:00:13 + with message-id and subject line Bug#901455: fixed in libsbml 5.17.2+dfsg-1 has caused the Debian Bug report #901455, regarding FTBFS in sid: package com.sun.tools.doclets.standard is not visible to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 901455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libsbml Version: 5.16.0+dfsg-2 Severity: serious Control: block 901155 by -1 Dear Maintainer, During a recompilation as part of the octave-4.4 transition, libsbml failed to build (for a reason apparently unrelated to the transition): https://buildd.debian.org/status/fetch.php?pkg=libsbml&arch=amd64&ver=5.16.0%2Bdfsg-2%2Bb1&stamp=1528656933&raw=0 Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄ http://www.debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libsbml Source-Version: 5.17.2+dfsg-1 We believe that the bug you reported is fixed in the latest version of libsbml, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 901...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libsbml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 12:12:21 +0100 Source: libsbml Binary: libsbml5-dev libsbml5 python3-sbml5 libsbml5-java libsbml5-perl libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc libsbml5-cil-doc libsbml5-perl-doc python3-sbml5-doc Architecture: source amd64 all Version: 5.17.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libsbml5 - System Biology Markup Language library libsbml5-cil - System Biology Markup Language library - CLI bindings libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation libsbml5-dev - System Biology Markup Language library - development files libsbml5-doc - System Biology Markup Language library -- documentation libsbml5-examples - System Biology Markup Language library -- example files libsbml5-java - System Biology Markup Language library - Java bindings libsbml5-octave - System Biology Markup Language library - Octave bindings libsbml5-perl - System Biology Markup Language library - Perl bindings libsbml5-perl-doc - System Biology Markup Language library -- Perl documentation python3-sbml5 - System Biology Markup Language library - Python3 bindings python3-sbml5-doc - System Biology Markup Language library - Python3 documentation Closes: 847013 896531 901455 911482 Changes: libsbml (5.17.2+dfsg-1) unstable; urgency=medium . [ gregor herrmann ] * Fix Perl installdir Closes: #896531 . [ Andreas Tille ] * New upstream version * Point Vcs fields to salsa.debian.org * Standards-Version: 4.3.0 * debhelper 12 * Deal with issue in doclets by removing docs/src/SBMLDoclet.java * Remove libsbml-java-doc since doc does not build properly Closes: #901455, #911482 * Provide Python3 instead of Python2 bindings (SBML can only provide either Python2 or Python3 - lets do the switch now) Closes: #847013 * Secure URI in copyright format * Drop useless get-orig-source target * Respect DEB_BUILD_OPTIONS in override_dh_auto_test target * Remove trailing whitespace in debian/changelog * Do not parse d/changelog * Build-Depends: libnewlib-dev, check * Remove Matlab related options from debian/cmake_opts (thanks for the hint to Nicolas Mora) * WITH_R=off (we do not build an R package and something is wrong with the R build) * Do not provide Java doc since there are errors when creating it and this solution was suggested by the Debian Java team * Fix Perl interpreter path * d/copyright: examples have MIT license Checksums-Sha1: edd8fc8ff402de03e36348f9c942b9277b0194f4 2905 libsbml_5.17.2+dfsg-1.dsc 7cee78af915a454faf4362d1b02245b0ecc0bcc7 9530508 libsbml_5.17.2+dfsg.orig.tar.x
Bug#918014: apache2: Segfault in mod_filter only wehen started by systemd
Hello Dominik George, might this be also caused by "libcap-ng's use of pthread_atfork causes segfaults" [1]. A version of libcap-ng that should fix that issue should hit testing the next days. Maybe you can check if this fixes the crash you reported, too, or if it is a separate one? Kind regards, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808
Processed: Bug #918627 in node-cacache marked as pending
Processing control commands:
> tag -1 pending
Bug #918627 {Done: Xavier Guimard } [src:node-cacache]
node-cacache FTBFS with nodejs 10.15.0
Added tag(s) pending.
--
918627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#918627: marked as done (node-cacache FTBFS with nodejs 10.15.0)
Your message dated Thu, 17 Jan 2019 21:53:50 + with message-id and subject line Bug#918627: fixed in node-cacache 11.3.2-1 has caused the Debian Bug report #918627, regarding node-cacache FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-cacache Version: 10.0.4-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-cacache.html ... 270 passing (1m) 7 pending 2 failing 1) test/content.write.js Cannot call write after a stream was destroyed: Error: Cannot call write after a stream was destroyed at WriteStream.end (/usr/lib/nodejs/flush-write-stream/index.js:43:41) 2) test/put.js errors if input stream errors returns the error from input stream: Error: returns the error from input stream at pipe.then.catch.err (test/put.js:138:7) at tryCatcher (/usr/lib/nodejs/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/usr/lib/nodejs/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/usr/lib/nodejs/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/usr/lib/nodejs/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/usr/lib/nodejs/bluebird/js/release/promise.js:689:18) at Async._drainQueue (/usr/lib/nodejs/bluebird/js/release/async.js:133:16) at Async._drainQueues (/usr/lib/nodejs/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues [as _onImmediate] (/usr/lib/nodejs/bluebird/js/release/async.js:17:14) make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Source: node-cacache Source-Version: 11.3.2-1 We believe that the bug you reported is fixed in the latest version of node-cacache, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-cacache package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 22:36:06 +0100 Source: node-cacache Binary: node-cacache Architecture: source Version: 11.3.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 918627 Description: node-cacache - fast, fault-tolerant, disk-based, data-agnostic, content-addressa Changes: node-cacache (11.3.2-1) unstable; urgency=medium . * Team upload * Add upstream/metadata * Add figgy-pudding component * New upstream version 11.3.2 * Declare compliance with policy 4.3.0 * Add node-flush-write-stream (>= 1.0.3-1) in build dependencies. Fixes debci (Closes: #918627) * Update debian/copyright format url Checksums-Sha1: 527ebf14bcfe7e0342ba3e7c621d515d32b9555f 2901 node-cacache_11.3.2-1.dsc 862470112901c727a0e495a80744bd5baa1d6790 6420 node-cacache_11.3.2.orig-figgy-pudding.tar.gz 7fd150eeb898ee496a96e1ffac589704e76dcaf5 103816 node-cacache_11.3.2.orig.tar.gz 1f79912a7cd87e5658d31323f345da7a116fe59e 3052 node-cacache_11.3.2-1.debian.tar.xz Checksums-Sha256: db8fee65f128f28ca7f6613b91b97a5eb41e9a783116168ad3577b652a0c55d7 2901 node-cacache_11.3.2-1.dsc bded940a26d7db1f8330e2801a8c2c791e21cf4bab6d9c5975711b369e9dc36a 6420 node-cacache_11.3.2.orig-figgy-pudding.tar.gz ea369aa6bd4d545ecf9cf34af864303b70d5a4478488f7451201b9baa7e51548 103816 node-cacache_11.3.2.orig.tar.gz bb4695560ac10ca3e8a26727a0b09edbe71b8a9cc9b3ff4709482924b2b1895b 3052 node-cacache_11.3.2-1.debian.tar.xz Files: f5184095459033870e9aa6af4f8186a1 2901 javascript optional node-cacache_11.3.2-1.dsc 7f53ccd3715ef2dad1e851f55a8ad193 6420 javascript optional node-cacache_11.3.2.orig-figgy-pudding.tar.gz 59f12f6e50f2a9866e2664ed7d8479ff 103816 javascript optional node-cacache_11.3.2.orig.tar.gz 07ac24f08f75a37b5c11581efe2ebb9a 3052 javascript optional node-cacache_11.3.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEAN/li4tVV
Bug#918420: marked as done (node-jison-lex FTBFS with nodejs 10.15.0)
Your message dated Thu, 17 Jan 2019 21:01:05 + with message-id and subject line Bug#918420: fixed in node-jison-lex 0.3.4-3 has caused the Debian Bug report #918420, regarding node-jison-lex FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-jison-lex Version: 0.3.4-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-jison-lex.html ... test more() [35m⚡ SyntaxError: Unexpected token ( at new RegExpLexer (/build/1st/node-jison-lex-0.3.4/regexp-lexer.js:124:22) at exports.test more() (/build/1st/node-jison-lex-0.3.4/tests/regexplexer.js:322:17) at test (/usr/lib/nodejs/test/test.js:29:20) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7)[39m ... test generator with more complex lexer [35m⚡ SyntaxError: Unexpected token ( at new RegExpLexer (/build/1st/node-jison-lex-0.3.4/regexp-lexer.js:124:22) at exports.test generator with more complex lexer (/build/1st/node-jison-lex-0.3.4/tests/regexplexer.js:413:18) at test (/usr/lib/nodejs/test/test.js:29:20) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7) at Object.end (/usr/lib/nodejs/test/test.js:25:7) at test (/usr/lib/nodejs/test/test.js:41:28) at next (/usr/lib/nodejs/test/test.js:69:7)[39m ... Passed:40 Failed:0 Errors:2 make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Source: node-jison-lex Source-Version: 0.3.4-3 We believe that the bug you reported is fixed in the latest version of node-jison-lex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-jison-lex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 20:40:23 +0100 Source: node-jison-lex Binary: node-jison-lex Architecture: source Version: 0.3.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 918420 Description: node-jison-lex - lexical analyzer generator used by jison Changes: node-jison-lex (0.3.4-3) unstable; urgency=medium . * Team upload. * Add upstream/metadata * Disable 2 tests (Closes: 918420) * Bump debheper compatibility level to 11 * Declare compliance with policy 4.3.0 * Update VCS fields to salsa * Update debian/watch to use npm registry * Ignore tests when nocheck is set * Update debian/copyright: add Berne Convention comment * Change section to javascript Checksums-Sha1: 84c696930fc3a16444384829ef8e502eb480efec 2087 node-jison-lex_0.3.4-3.dsc e94b293aa16912d065e7b13bff4050c1b3970b2b 3148 node-jison-lex_0.3.4-3.debian.tar.xz Checksums-Sha256: 43ff148b369a79279879b75b2c7ea1489c0ddcc624d09c1449ced40b7fdf2e4b 2087 node-jison-lex_0.3.4-3.dsc 95fb7471889313e53816593fc5e7235e66714ed4b777a24e04e341f0bd97ccd6 3148 node-jison-lex_0.3.4-3.debian.tar.xz Files: e481c380e9b4503fedab522309ddf4d3 2087 javascript optional node-jison-lex_0.3.4-3.dsc 1a09e222ce6fe234970202aaa714ad54 3148 javascript optional node-jison-lex_0.3.4-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxA21cQHHlhZGRAZGVi aWFuLm9yZwAKCRD210ynyZnu6fNjD/4uOwBjrDmpdooH/W+8seNqL4i1MKPLr+Y+ JVqTqkMvMnTZ6BXfhlnAyIdKXEBpA8MDdMrfBV7W8ag8ZITMrFREgwMSXJAqwQGi RuIC/DG/
Bug#919500: marked as done (golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494))
Your message dated Thu, 17 Jan 2019 20:55:52 + with message-id and subject line Bug#919500: fixed in golang-github-grpc-ecosystem-grpc-gateway 1.6.4-2 has caused the Debian Bug report #919500, regarding golang-github-grpc-ecosystem-grpc-gateway: build dependency on golang-google-genproto-dev must be bumped to (>= 0.0~git20190111.db91494) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-grpc-ecosystem-grpc-gateway Version: 1.6.4-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=golang-github-grpc-ecosystem-grpc-gateway ... # github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor src/github.com/grpc-ecosystem/grpc-gateway/protoc-gen-grpc-gateway/descriptor/services.go:146:49: opts.ResponseBody undefined (type *annotations.HttpRule has no field or method ResponseBody) ... --- End Message --- --- Begin Message --- Source: golang-github-grpc-ecosystem-grpc-gateway Source-Version: 1.6.4-2 We believe that the bug you reported is fixed in the latest version of golang-github-grpc-ecosystem-grpc-gateway, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Rebillout (supplier of updated golang-github-grpc-ecosystem-grpc-gateway package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Jan 2019 12:03:44 +0700 Source: golang-github-grpc-ecosystem-grpc-gateway Binary: golang-github-grpc-ecosystem-grpc-gateway-dev golang-grpc-gateway Architecture: source Version: 1.6.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Arnaud Rebillout Description: golang-github-grpc-ecosystem-grpc-gateway-dev - gRPC to JSON proxy generator for Golang -- sources golang-grpc-gateway - gRPC to JSON proxy generator for Golang -- binaries Closes: 919500 Changes: golang-github-grpc-ecosystem-grpc-gateway (1.6.4-2) unstable; urgency=medium . * Team upload. * Set debian-branch to debian/sid in gbp.conf * Bump golang-google-genproto-dev to 0.0~git20190111~ (Closes: #919500) * Bump golang-goprotobuf-dev to 1.2.0 Checksums-Sha1: 1989fb435e44046c6de6e75476a753c2c6ea35e8 2764 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.dsc 9d24026b7a1fc537c5a3b8094ece1dc7a51360c8 3868 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.debian.tar.xz 2dc6d99badea1316646e98ec79622c5898cf31c8 7470 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2_amd64.buildinfo Checksums-Sha256: dd488c092e615e6bc688cf8b4dc3709e87424b50724fe913a9d1104399d830ec 2764 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.dsc 370dc7d212e2788f06d8c5c072f350c2a35f250308df5f148ae77a4c355a726c 3868 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.debian.tar.xz ff80ebc61c376ff3cecf37348c7a4b27a580410ec66f1d23d8139c087f9d3aca 7470 golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2_amd64.buildinfo Files: e769d1d95dcbcd6baff67e9cb041f7db 2764 devel optional golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.dsc c8473c4abbd026f69bc30556736b3bf5 3868 devel optional golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2.debian.tar.xz 2fe9b7548d416e4dd2a1f84e5686c3d9 7470 devel optional golang-github-grpc-ecosystem-grpc-gateway_1.6.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAlxA5xsACgkQEwLx8Dbr 6xku5xAAmTR7DTC+GC7csvJ+20JK6f/nA3cLninpV8C2SrOBOKtneWrLspUuYpfY 91mMuchulG3Or9FnETohI2lrvaG48s9AmTsxcMnRu4kzQpwkcPl1Clka3fnOjhH1 yx6wY7vg7Nqg3NF9dmbO596tOYxjsM7vTGvyqQz2Hg/aD+6TAqUvxH/kQUlkbFbF z9toa22Uwci9z3LClPHD/dfb7EmDxT56YMhBsoms8aFac4P0GxoehqYdmBpZ6PCM u7eecsghru5y40OEoa6BSRvIjm9y44owyAE2HsjoZCSZxO37/S2VDEah8fpYp0MT 8juqGmbcd1kC9jT/4OhzQrBhQNpr48sWB5i/mMZ2yGqKPr8xBBA5setitznPXmpR gwhST84AYA88vDSuBbWB4l9QcAk4grNIFt2EaQ7inbfq9/wYpxWuFVYA/jOqULV7 REownozNZ6i3Dyz976zU+ZNhDkLVdb7I43ln/gssB4UQ2JmObqTLzXehTCxNblMx b2BLH9Whi3QgN9zPus4GHcxarVGC+Lb/V40AZY+tTlZJz82MvH2AbH1qlSbCyc2I VO75aAhj8teXbP9D6em8kUIYuHWiF0IYmRukME8hcTxavySqaRQ
Bug#918627: Bug #918627 in node-cacache marked as pending
Control: tag -1 pending Hello, Bug #918627 in node-cacache 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: https://salsa.debian.org/js-team/node-cacache/commit/6f2420be3e74a867ab00188a306c46b5c671c823 Add node-flush-write-stream (>= 1.0.3-1) in build dependencies. Fixes debci Closes: #918627 (this message was generated automatically) -- Greetings https://bugs.debian.org/918627
Bug#917498: marked as done (libexplain: FTBFS (failing tests))
Your message dated Thu, 17 Jan 2019 21:51:52 +
with message-id
and subject line Bug#917498: fixed in libexplain 1.4.D001-8
has caused the Debian Bug report #917498,
regarding libexplain: FTBFS (failing tests)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libexplain
Version: 1.4.D001-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with autoreconf --no-parallel
dh_update_autotools_config -i
dh_autoreconf -i
configure.ac:1102: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected
in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
../../lib/autoconf/general.m4:2759: AC_RUN_IFELSE is expanded from...
configure.ac:1102: the top level
configure.ac:1102: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected
in body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
[... snipped ...]
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0642a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0643a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0644a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0645a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0646a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0648a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0649a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0650a.sh
This system does not VIDIOCGCAP, therefore this test is declared to pass by
default.
PASSED
PATH=`pwd`/bin:$PATH /bin/sh test/06/t0652a.sh
2,4c2,3
< the fp argument does not refer to an object that is open for writing;
< this is more likely to be a software error (a bug) than it is to be a
< user error
---
> the fildes argument does not refer to an object that is open for writing
> (O_RDONLY | O_LARGEFILE)
FAILED test of fputs("yuck", stdin);
make[1]: *** [Makefile:42571: t0652a] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libexplain.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: libexplain
Source-Version: 1.4.D001-8
We believe that the bug you reported is fixed in the latest version of
libexplain, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 917...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Henriksson (supplier of updated libexplain package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 17 Jan 2
Processed: severity of 918070 is grave
Processing commands for cont...@bugs.debian.org: > severity 918070 grave Bug #918070 [gitaly] gitaly: Expects gitlab socket directory Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 918070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911515: dvtm in backports
Hello? Dear maintainer of ncurses, could you please upload a backport of ncurses-term? pgpLomqpgPKeE.pgp Description: PGP signature
Bug#916966: merge request on salsa
Control: forwarded -1 https://salsa.debian.org/multimedia-team/linuxptp/merge_requests/1 Control: tags -1 + patch Sent a merge-request on salsa with a patch that fixes the problem by making sure (which defines clockid_t) is included before Regards, Andreas Henriksson
Processed: merge request on salsa
Processing control commands: > forwarded -1 > https://salsa.debian.org/multimedia-team/linuxptp/merge_requests/1 Bug #916966 [src:linuxptp] linuxptp FTBFS with glibc 2.28 Set Bug forwarded-to-address to 'https://salsa.debian.org/multimedia-team/linuxptp/merge_requests/1'. > tags -1 + patch Bug #916966 [src:linuxptp] linuxptp FTBFS with glibc 2.28 Added tag(s) patch. -- 916966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912633: Possible conflict betwwen courier-imap and courier-imap-ssl?
Markus Wanner wrote: > I removed courier-imap-ssl, as it's a transitional package in stretch, > already. It can be removed safely. I removed courier-imap-ssl and no i no longer get the "No supported cipher suite ..." error message. I no longer see this problem. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/
Bug#919582: marked as done (libhmsbeagle-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libhmsbeagle-opencl.so -> libhmsbeagle-opencl.so.21)
Your message dated Thu, 17 Jan 2019 19:34:24 + with message-id and subject line Bug#919582: fixed in libhmsbeagle 3.1.2+dfsg-3 has caused the Debian Bug report #919582, regarding libhmsbeagle-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libhmsbeagle-opencl.so -> libhmsbeagle-opencl.so.21 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhmsbeagle-dev Version: 3.1.2+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m33.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libhmsbeagle-opencl.so -> libhmsbeagle-opencl.so.21 (libhmsbeagle-dev) cheers, Andreas libhmsbeagle-dev_3.1.2+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libhmsbeagle Source-Version: 3.1.2+dfsg-3 We believe that the bug you reported is fixed in the latest version of libhmsbeagle, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated libhmsbeagle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 18:36:10 +0100 Source: libhmsbeagle Binary: libhmsbeagle-dev libhmsbeagle1v5 libhmsbeagle-java Architecture: source Version: 3.1.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libhmsbeagle-dev - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle-java - High-performance lib for Bayesian and Maximum Likelihood phylogen libhmsbeagle1v5 - High-performance lib for Bayesian and Maximum Likelihood phylogen Closes: 919582 Changes: libhmsbeagle (3.1.2+dfsg-3) unstable; urgency=medium . * Fix dankling symlink Closes: #919582 * debhelper 12 * Standards-Version: 4.3.0 Checksums-Sha1: b3ce93caeaa5273eaf6f0bc18cdaa08552a946bd 2398 libhmsbeagle_3.1.2+dfsg-3.dsc 1eab5a61cfae00f53e346d4cd69217fe65da48e6 36016 libhmsbeagle_3.1.2+dfsg-3.debian.tar.xz 7d46b79351d41239637d388ce05b4eb43255fdd2 14598 libhmsbeagle_3.1.2+dfsg-3_amd64.buildinfo Checksums-Sha256: d8d644709026f898e5df70302f41141e6cfa968e4a962b439831925bc9c1161c 2398 libhmsbeagle_3.1.2+dfsg-3.dsc 7414bd75759082e6c0f572cb44a75f527820d1bf720565ddbe8e8da435c0b2ec 36016 libhmsbeagle_3.1.2+dfsg-3.debian.tar.xz b19aa5b10b44d369fb59594400e50a7400b8539f60c2b27592f64b36be5d7bf3 14598 libhmsbeagle_3.1.2+dfsg-3_amd64.buildinfo Files: af807cc8f687cf489ac5c1b7a7a8fd8b 2398 libs optional libhmsbeagle_3.1.2+dfsg-3.dsc a910d17c38e70113200aa06c0e4b7799 36016 libs optional libhmsbeagle_3.1.2+dfsg-3.debian.tar.xz 260d201cf58f2a526f135deb7f41a3f4 14598 libs optional libhmsbeagle_3.1.2+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlxA06wRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFdIA//T/xQEr+jrDRAGVTki+jY5Me0oqgO1A9Q 7wN8piMn2QV8cD5DIuXV+4pSFLeuaNiPGb8tB7gDv9AXK4FyAH1HitHjG4FZbS+g O9q6G84XtW29Zoi+R94wvtKy/8duIVEJTFVW6sZPcMZOUCZVTAlbR/0F7mC/72nS PHzh8GpoTmvvhmUHZV243TuFEsR47Lt/foMPPJ3cgh46JQVvyyBGVse+Cp3+5gTw BClVlUt9Qz8XMjrJEGLn23gcrdiDkUesqFpoiWviPPHZl+cWu7FlNoG1WcEZiyjK dRuMrNkQVLJOYdQW2/BmHpWXNc6YtwcykXktbh5RGzSAuGYexubRcJcnMWpXkTlw Yybv4KW5fqVW4ZdLmW82qc4tPNJVRHGdTK2TDzJi662E0DBm7puDvhEYk60j6iMC CNg9Jp/Pa+85xk8l3LCkg38XywQ1YjInLZz/vD7fakHxrh6EuVuXL6OWh6nm5QBf osSrmpMDFN4yq9pqLWWqvAtLdg9hlsPtlE6bUwaGPLax/2/1c2lIlTBY+LSjf6LH 00S+BQni7T40BNDQ9vAz3mkTrd3fyfJpNBQjDpex/y2ogAjKYWnZyhb5KqOwLzfh WEi6uOkB16uIeZebjT8jUSZ+QnKUn3CxJxoQ+UXgO4eTqsrQudY8zXNRr9QqFSK+ guGb8pDi7rw= =00YB -END PGP SIGNATURE End Message ---
Processed: tagging 910295
Processing commands for cont...@bugs.debian.org: > tags 910295 + buster sid Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 918420 is forwarded to https://github.com/zaach/jison-lex/issues/27
Processing commands for cont...@bugs.debian.org: > forwarded 918420 https://github.com/zaach/jison-lex/issues/27 Bug #918420 [src:node-jison-lex] node-jison-lex FTBFS with nodejs 10.15.0 Set Bug forwarded-to-address to 'https://github.com/zaach/jison-lex/issues/27'. > thanks Stopping processing here. Please contact me if you need assistance. -- 918420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918931: fixed in metrohash 1.1.3-1
On Thu, 17 Jan 2019 18:20:41 +0100 Santiago Vila wrote: > Are you sure about the Bug number? Ouch, made a typo in changelog. Fixed, thanks. -- Best regards, Alexander Gerasiov Contacts: e-mail: g...@cs.msu.su WWW: http://gerasiov.net TG/Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Control: notfound -1 python3-httpretty/0.9.5-2 Control: tags -1 - upstream Control: affects -1 - src:dput On Fri, 2019-01-18 05:02 +11:00, Ben Finney wrote: > Control: reassign -1 python3-httpretty > Control: found -1 python3-httpretty/0.9.5-2 > Control: tags -1 + upstream > Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369 > Control: affects -1 + src:dput -- \ `\ _o__) Ben Finney
Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > notfound -1 python3-httpretty/0.9.5-2 Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request The source python3-httpretty and version 0.9.5-2 do not appear to match any binary packages No longer marked as found in versions python3-httpretty/0.9.5-2. > tags -1 - upstream Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Removed tag(s) upstream. > affects -1 - src:dput Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Removed indication that 910295 affects src:dput -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Control: clone -1 -2 Control: retitle -1 dput: FTBFS: tests fail to mock HTTP request Control: found -1 dput/1.0.2 Control: notforwarded -1 Control: summary -1 The HTTPretty library is failing to mock requests from Python's HTTPConnection. Control: outlook -1 Either correct the HTTPretty library; or re-work the DPut test cases to avoid HTTPretty. Control: block -1 by -2 Control: severity -2 important Control: tags -2 - ftbfs On Fri, 2019-01-18 05:02 +11:00, Ben Finney wrote: > Control: reassign -1 python3-httpretty > Control: found -1 python3-httpretty/0.9.5-2 > Control: tags -1 + upstream > Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369 > Control: affects -1 + src:dput -- \ `\ _o__) Ben Finney
Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > clone -1 -2 Bug #910295 [python3-httpretty] python3-httpretty: Fails to mock request sent with HTTPConnection Bug 910295 cloned as bug 919599 > retitle -1 dput: FTBFS: tests fail to mock HTTP request Bug #910295 [python3-httpretty] python3-httpretty: Fails to mock request sent with HTTPConnection Changed Bug title to 'dput: FTBFS: tests fail to mock HTTP request' from 'python3-httpretty: Fails to mock request sent with HTTPConnection'. > found -1 dput/1.0.2 Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Marked as found in versions dput/1.0.2. > notforwarded -1 Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request Unset Bug forwarded-to-address > summary -1 The HTTPretty library is failing to mock requests from Python's > HTTPConnection. Summary recorded from message bug 910295 message > outlook -1 Either correct the HTTPretty library; or re-work the DPut test > cases to avoid HTTPretty. Outlook recorded from message bug 910295 message > block -1 by -2 Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request 910295 was not blocked by any bugs. 910295 was not blocking any bugs. Added blocking bug(s) of 910295: 919599 > severity -2 important Bug #919599 [python3-httpretty] python3-httpretty: Fails to mock request sent with HTTPConnection Severity set to 'important' from 'serious' > tags -2 - ftbfs Bug #919599 [python3-httpretty] python3-httpretty: Fails to mock request sent with HTTPConnection Removed tag(s) ftbfs. -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 919599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Control: retitle -1 python3-httpretty: Fails to mock request sent with HTTPConnection On Fri, 2019-01-18 05:02 +11:00, Ben Finney wrote: > The HTTPretty library is failing to correctly mock requests sent using > the standard-library `http.client.HTTPConnection` class. > > I have registered a new bug report at the HTTPretty project bug > tracker for this. -- \ `\ _o__) Ben Finney
Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > retitle -1 python3-httpretty: Fails to mock request sent with HTTPConnection Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Changed Bug title to 'python3-httpretty: Fails to mock request sent with HTTPConnection' from 'dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known'. -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: mangler: B-D libg15-dev libg15daemon-client-dev are no longer available
Processing commands for cont...@bugs.debian.org: > tags 915768 + pending Bug #915768 [src:mangler] mangler: B-D libg15-dev libg15daemon-client-dev are no longer available Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 915768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919554: Indeed the chmod solves the problem
Thanks Michael. As a side note, I would like to point out that the 5.2.24 version of virtualbox in unstable is also set to 6755 but in this case it does not prevent to run correctly. I have no clue if it is also needed for 5.2.24, if not why not remove it or why it now breaks for 6.0.2. -- eric
Bug#915768: mangler: B-D libg15-dev libg15daemon-client-dev are no longer available
tags 915768 + pending thanks I've applied the patch and uploaded 1.2.5-4.1 to the DELAYED/2 queue. This only removes the g15 Build-Depends and adds --disable-g15 to debian/rules. Willam: Being that there's been no response from the maintainer for this bug in over a month for a bug of severity 'serious' it seems like this package could use 'salvaging'. Have a look at the Debian Developer's Reference, section 5.12 here: http://sejnfjrq6szgca7v.onion/doc/manuals/developers-reference/ch05.en.html#package-salvaging If you still have interest in fixing the other minor bugs, which it looks to me like you do, then try contacting the maintainer and/or file an ITS bug. I'm willing to sponsor uploads for you. Seems like you're already familiar with Debian packaging, but feel free to contact me if I can be of further help. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#919595: zsnapd: must be in contrib as it depends on contrib package
Package: zsnapd Version: 0.5.2-1 Severity: serious Justification: Policy 2.2.1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 zsnapd depends on zfsutils-linux, which is in contrib. Debian Policy § 2.2.1 says: > In addition, the packages in *main* > > * must not require or recommend a package outside of *main* for > compilation or execution (thus, the package must not declare a "Pre- > Depends", "Depends", "Recommends", "Build-Depends", "Build-Depends- > Indep", or "Build-Depends-Arch" relationship on a non-*main* package > unless that package is only listed as a non-default alternative for > a package in *main*), Please move zsnapd to contrib. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxAxMoACgkQLHwxRsGg ASHgJxAAgY68xpUJvi+9DjRLnUM7H9jt+x5/lhamaa2Del1YEakhIk9m4yctYAWm 3YI+aODptqAlY21kBDDB+ekRxjIBQCYSpBUp7bXdWCCMjGDMYIWpFq/T8BixsLmq LB08YTuvbP5xc3xTjngeP9pGe+51nmRlCliUE/dkjhgSNDp21dKzNrHnuMjaYzI6 pPPsDiRWpusVKEgFRBrrx4IICQk0Q6zyDdXfy0ZBwyvm7x9cxikohYK76PZ7vOVJ 0XijHJC9dtDDumIIOxqsRvdRtumh7VRErnAoG73HW/7/ERvZDoGlfGAB/xvsaW0U foxxJkK/P7vNCEVCNpQ67/SD+U4OkCXk2oaB+E/BcVC5EF2KGpP0O7syisXM3MBE pNc0+l7GgqD6CChT+RAMuhU1nWxpTNfv8xL6w/Y6rewZT/uEtNF3sNGp+Gj/OtXP e8nZyDS9C2XS5jWtjy0dwdkw0zO2kd2W4mECpXzgORpBDATE7cI4ApkUlltb1Wo6 5w9EP/yx/OU1ItNbS+ijOtwtQNkBv0guawL1FE1NI5IIQWCUA1OUjC7UUSoRz1+2 YBDgCehnvOmFFGQYb7UOAW9MhiYk9urK/fduDIgMYZZOOzroqyknHnGsnZK+IEJ9 dl713UH3oJLnMH2DGWfGhiVnYQiiIU0ZLQ9jxmjyWKI1tK8t3ms= =8DoW -END PGP SIGNATURE-
Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Control: reassign -1 python3-httpretty Control: found -1 python3-httpretty/0.9.5-2 Control: tags -1 + upstream Control: forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369 Control: affects -1 + src:dput On 16-Jan-2019, Ben Finney wrote: > I suspect there's something changed with the ‘httpretty’ testing > library; either that, or something changed in recent Python 3 > versions. The HTTPretty library is failing to correctly mock requests sent using the standard-library `http.client.HTTPConnection` class. I have registered a new bug report at the HTTPretty project bug tracker for this. -- \ “[F]reedom of speech does not entail freedom to have your ideas | `\accepted by governments and incorporated into law and policy.” | _o__) —Russell Blackford, 2010-03-06 | Ben Finney
Bug#919594: memkind: baseline violation on amd64 (and FTBFS everywhere else)
Source: memkind Version: 1.8.0-1 Severity: serious https://buildd.debian.org/status/package.php?p=memkind&suite=sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/memkind.html memkind builds for no apparent reason with -msse4.2, which is a baseline violation even on amd64. Build failures on other architectures seem to be often related to using an internal copy of jemalloc instead of the version in Debian.
Processed: Re: Bug#910295: dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known
Processing control commands: > reassign -1 python3-httpretty Bug #910295 [src:dput] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Bug reassigned from package 'src:dput' to 'python3-httpretty'. No longer marked as found in versions dput/1.0.2. Ignoring request to alter fixed versions of bug #910295 to the same values previously set > found -1 python3-httpretty/0.9.5-2 Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known The source python3-httpretty and version 0.9.5-2 do not appear to match any binary packages Marked as found in versions python3-httpretty/0.9.5-2. > tags -1 + upstream Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Added tag(s) upstream. > forwarded -1 https://github.com/gabrielfalcao/HTTPretty/issues/369 Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Set Bug forwarded-to-address to 'https://github.com/gabrielfalcao/HTTPretty/issues/369'. > affects -1 + src:dput Bug #910295 [python3-httpretty] dput FTBFS: tests fail: socket.gaierror: [Errno -2] Name or service not known Added indication that 910295 affects src:dput -- 910295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919591: libwin32-exe-perl: Incomplete debian/copyright?
Source: libwin32-exe-perl Version: 0.17-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Cyrille Bollu , ftpmas...@debian.org Hi, I just ACCEPTed libwin32-exe-perl from NEW but noticed it was missing attribution in debian/copyright for at least Mark Dootson. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Processed: [bts-link] source package src:wolfssl
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:wolfssl > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #918952 (http://bugs.debian.org/918952) > # Bug title: wolfssl: CVE-2018-16870 > # * https://github.com/wolfSSL/wolfssl/pull/1950 > # * remote status changed: (?) -> closed > # * closed upstream > tags 918952 + fixed-upstream Bug #918952 [src:wolfssl] wolfssl: CVE-2018-16870 Added tag(s) fixed-upstream. > usertags 918952 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 918952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918931: marked as done (fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm)
Your message dated Thu, 17 Jan 2019 17:00:14 + with message-id and subject line Bug#918931: fixed in metrohash 1.1.3-2 has caused the Debian Bug report #918931, regarding fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fasm Version: 1.73.06-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a debian/rules override_dh_install make[1]: Entering directory '/<>' mkdir -p debian/tmp (cd source/libc; fasm fasm.asm; gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -m32 fasm.o -o fasm) /bin/sh: 1: fasm: not found gcc: error: fasm.o: No such file or directory make[1]: *** [debian/rules:11: override_dh_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fasm.html The fasm executable has in fact disappeared from the current package: dpkg -L fasm | grep usr/bin I have a theory to explain how this happened, see next bug. Thanks. --- End Message --- --- Begin Message --- Source: metrohash Source-Version: 1.1.3-2 We believe that the bug you reported is fixed in the latest version of metrohash, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander GQ Gerasiov (supplier of updated metrohash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2019 15:31:24 +0300 Source: metrohash Binary: libmetrohash-dev libmetrohash1 Architecture: source amd64 Version: 1.1.3-2 Distribution: unstable Urgency: medium Maintainer: Alexander GQ Gerasiov Changed-By: Alexander GQ Gerasiov Description: libmetrohash-dev - hash functions for non-cryptographic use cases (headers) libmetrohash1 - hash functions for non-cryptographic use cases Closes: 918931 Changes: metrohash (1.1.3-2) unstable; urgency=medium . * d/control, d/copyrigh: Fix wrong strings. . metrohash (1.1.3-1) unstable; urgency=low . * Initial release (Closes: #918931) Checksums-Sha1: 5c1495cb80ba1187294f6e46613d1ebdb6082a2a 1565 metrohash_1.1.3-2.dsc ecd110357b9699e48f7df1a6da8695080df18a91 10587 metrohash_1.1.3.orig.tar.gz 20bd94a1c892e269b65f9b7a55ebdd72c49dbf90 2000 metrohash_1.1.3-2.debian.tar.xz 928d0f04db09b9b89667f24b43cddf1f197ca0e1 4948 libmetrohash-dev_1.1.3-2_amd64.deb f5ae285a8d7f40bd5b84f7f855b6dad931575c76 24084 libmetrohash1-dbgsym_1.1.3-2_amd64.deb eacc843af42fabaf3ae10f187801d8a5b1ef5459 7524 libmetrohash1_1.1.3-2_amd64.deb 0540a99176b86ce2654b01f0256f4b91150bb97e 5540 metrohash_1.1.3-2_amd64.buildinfo Checksums-Sha256: 8c4f27c2e96ad854ba400fa4c0d94f7900bed8314db1de91283827aaf831c3a8 1565 metrohash_1.1.3-2.dsc 43991740b3e065151dc46fa4336295480a27913c42b45a42bbf7c760cade4229 10587 metrohash_1.1.3.orig.tar.gz 962dbffb1b5842b1343762b0088693c381eaf5d9fc3733d6f9ff2a402474fdeb 2000 metrohash_1.1.3-2.debian.tar.xz 8ab4626de297fca74352038d1402651115099f0ddde10646de119f53c1481854 4948 libmetrohash-dev_1.1.3-2_amd64.deb 7e923a6e63cfe8253387d3d940dba5b998e808bd6ceb6f7d23c0eb2a6d956612 24084 libmetrohash1-dbgsym_1.1.3-2_amd64.deb 57cd2b66678bd5b72588a5fce5436dfda1998eabfcaa2b36c8766d8800a25acb 7524 libmetrohash1_1.1.3-2_am
Bug#918931: marked as done (fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm)
Your message dated Thu, 17 Jan 2019 17:00:13 + with message-id and subject line Bug#918931: fixed in metrohash 1.1.3-1 has caused the Debian Bug report #918931, regarding fasm: FTBFS because it build-depends on itself and the current version lacks /usr/bin/fasm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fasm Version: 1.73.06-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a create-stamp debian/debhelper-build-stamp fakeroot debian/rules binary-arch dh binary-arch dh_testroot -a dh_prep -a debian/rules override_dh_install make[1]: Entering directory '/<>' mkdir -p debian/tmp (cd source/libc; fasm fasm.asm; gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -m32 fasm.o -o fasm) /bin/sh: 1: fasm: not found gcc: error: fasm.o: No such file or directory make[1]: *** [debian/rules:11: override_dh_install] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -B" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fasm.html The fasm executable has in fact disappeared from the current package: dpkg -L fasm | grep usr/bin I have a theory to explain how this happened, see next bug. Thanks. --- End Message --- --- Begin Message --- Source: metrohash Source-Version: 1.1.3-1 We believe that the bug you reported is fixed in the latest version of metrohash, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alexander GQ Gerasiov (supplier of updated metrohash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Jan 2019 21:23:29 +0300 Source: metrohash Binary: libmetrohash-dev libmetrohash1 Architecture: source amd64 Version: 1.1.3-1 Distribution: unstable Urgency: low Maintainer: Alexander GQ Gerasiov Changed-By: Alexander GQ Gerasiov Description: libmetrohash-dev - hash functions for non-cryptographic use cases (headers) libmetrohash1 - compile-time library for optimizing integer division Closes: 918931 Changes: metrohash (1.1.3-1) unstable; urgency=low . * Initial release (Closes: #918931) Checksums-Sha1: 4b0dabacdfb53af4a1a2f78b4a522102005efdd9 1565 metrohash_1.1.3-1.dsc ecd110357b9699e48f7df1a6da8695080df18a91 10587 metrohash_1.1.3.orig.tar.gz ef5f13a9572c615da8976241200424ec8f7f9d41 1960 metrohash_1.1.3-1.debian.tar.xz c693e1eaec2e0935ef9534bb299729c3f83066ea 4856 libmetrohash-dev_1.1.3-1_amd64.deb fff22dd7f2bc47560db0635101a33d52a6119a93 24084 libmetrohash1-dbgsym_1.1.3-1_amd64.deb 6175744311f06641442ba17502fef1b75b06cd3b 7472 libmetrohash1_1.1.3-1_amd64.deb f426141e3b15032bf62fca9180edf28692dab483 5540 metrohash_1.1.3-1_amd64.buildinfo Checksums-Sha256: ef01902f61a37c59da1ffcc2102319afe73271af7ecaf10542f728d61021bae7 1565 metrohash_1.1.3-1.dsc 43991740b3e065151dc46fa4336295480a27913c42b45a42bbf7c760cade4229 10587 metrohash_1.1.3.orig.tar.gz 7da2a01d587b4e4c3e6c4edb50815e7325b1fb3900e32606c392f3f79e2a7980 1960 metrohash_1.1.3-1.debian.tar.xz 664ed24c744b69141f3dca8f1b4b907f69f36bd73a29c9050a812e7e01b05fb5 4856 libmetrohash-dev_1.1.3-1_amd64.deb 9eb5656c6d116f1690fd521e51a2704bb26a868083f3ed7e005bbd8ae40b853e 24084 libmetrohash1-dbgsym_1.1.3-1_amd64.deb 2bc790fd5813b798eaacaca224234951ed144d868f6c386942025d54a9bb1af8 7472 libmetrohash1_1.1.3-1_amd64.deb e696fb080d942bbee9037d5a97bc22e45a1d24638e42b3dad98492bdf6bd12e7 5540 metrohash_1.1.3-
Bug#919418: marked as done (kuttypy: FTBFS in sid (pyuic5: Command not found))
Your message dated Thu, 17 Jan 2019 17:06:10 +0100 with message-id <20190117160609.GA25260@localhost> and subject line bug was closed in 1.0-1, but 1.0-2 was uploaded too fast has caused the Debian Bug report #919418, regarding kuttypy: FTBFS in sid (pyuic5: Command not found) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919418 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kuttypy Version: 0.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with python3 dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i dh_auto_build -i make -j1 "INSTALL=install --strip-program=true" make[1]: Entering directory '/<>' ?. Using QT Version: PyQt5 pyuic5 pyrcc5 pylupdate5 3 for d in utilities; do make PYUIC=pyuic5 PYRCC=pyrcc5 PYLUPDATE=pylupdate5 PY_VERSION=3 -C $d all; done make[2]: Entering directory '/<>/utilities' for d in templates; do make -C $d all; done make[3]: Entering directory '/<>/utilities/templates' PYRCC=pyrcc5 pyuic5 --from-import dio.ui -o ui_dio.py make[3]: pyuic5: Command not found make[3]: *** [Makefile:26: ui_dio.py] Error 127 make[3]: Leaving directory '/<>/utilities/templates' make[2]: *** [Makefile:6: recursive_all] Error 2 make[2]: Leaving directory '/<>/utilities' make[1]: *** [Makefile:31: recursive_all] Error 2 make[1]: Leaving directory '/<>' dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit code 2 make: *** [debian/rules:4: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" but it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kuttypy.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- ... which prevented the bug report to be considered as fixed. thx -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70 signature.asc Description: PGP signature --- End Message ---
Bug#918445: marked as done (libgccjit-9-doc: missing Conflicts: libgccjit-8-doc)
Your message dated Thu, 17 Jan 2019 16:00:25 + with message-id and subject line Bug#918445: fixed in gcc-9 9-20190116-1 has caused the Debian Bug report #918445, regarding libgccjit-9-doc: missing Conflicts: libgccjit-8-doc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgccjit-9-doc Version: 9-20190103-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts libgccjit-9-doc needs to conflict with libgccjit-8-doc like it does with the older ones. Andreas libgccjit-8-doc=8.2.0-13_libgccjit-9-doc=9-20190103-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-9 Source-Version: 9-20190116-1 We believe that the bug you reported is fixed in the latest version of gcc-9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2019 09:42:19 +0100 Source: gcc-9 Binary: gcc-9-base libgcc1 libgcc1-dbg libgcc2 libgcc2-dbg libgcc-9-dev libgcc4 libgcc4-dbg lib64gcc1 lib64gcc1-dbg lib64gcc-9-dev lib32gcc1 lib32gcc1-dbg lib32gcc-9-dev libn32gcc1 libn32gcc1-dbg libn32gcc-9-dev libx32gcc1 libx32gcc1-dbg libx32gcc-9-dev gcc-9 gcc-9-multilib gcc-9-test-results gcc-9-plugin-dev gcc-9-hppa64-linux-gnu cpp-9 gcc-9-locales g++-9 g++-9-multilib libgomp1 libgomp1-dbg lib32gomp1 lib32gomp1-dbg lib64gomp1 lib64gomp1-dbg libn32gomp1 libn32gomp1-dbg libx32gomp1 libx32gomp1-dbg libitm1 libitm1-dbg lib32itm1 lib32itm1-dbg lib64itm1 lib64itm1-dbg libx32itm1 libx32itm1-dbg libatomic1 libatomic1-dbg lib32atomic1 lib32atomic1-dbg lib64atomic1 lib64atomic1-dbg libn32atomic1 libn32atomic1-dbg libx32atomic1 libx32atomic1-dbg libasan5 libasan5-dbg lib32asan5 lib32asan5-dbg lib64asan5 lib64asan5-dbg libx32asan5 libx32asan5-dbg liblsan0 liblsan0-dbg lib32lsan0 lib32lsan0-dbg libx32lsan0 libx32lsan0-dbg libtsan0 libtsan0-dbg libubsan1 libubsan1-dbg lib32ubsan1 lib32ubsan1-dbg lib64ubsan1 lib64ubsan1-dbg libx32ubsan1 libx32ubsan1-dbg libquadmath0 libquadmath0-dbg lib32quadmath0 lib32quadmath0-dbg lib64quadmath0 lib64quadmath0-dbg libx32quadmath0 libx32quadmath0-dbg libcc1-0 libgccjit0 libgccjit0-dbg libgccjit-9-doc libgccjit-9-dev gobjc++-9 gobjc++-9-multilib gobjc-9 gobjc-9-multilib libobjc-9-dev lib64objc-9-dev lib32objc-9-dev libn32objc-9-dev libx32objc-9-dev libobjc4 libobjc4-dbg lib64objc4 lib64objc4-dbg lib32objc4 lib32objc4-dbg libn32objc4 libn32objc4-dbg libx32objc4 libx32objc4-dbg gfortran-9 gfortran-9-multilib libgfortran-9-dev lib64gfortran-9-dev lib32gfortran-9-dev libn32gfortran-9-dev libx32gfortran-9-dev libgfortran5 libgfortran5-dbg lib64gfortran5 lib64gfortran5-dbg lib32gfortran5 lib32gfortran5-dbg libn32gfortran5 libn32gfortran5-dbg libx32gfortran5 libx32gfortran5-dbg gccgo-9 gccgo-9-multilib libgo14 libgo14-dbg lib64go14 lib64go14-dbg lib32go14 lib32go14-dbg libn32go14 libn32go14-dbg libx32go14 libx32go14-dbg libstdc++6 lib32stdc++6 lib64stdc++6 libn32stdc++6 libx32stdc++6 libstdc++-9-dev libstdc++-9-pic libstdc++6-9-dbg lib32stdc++-9-dev lib32stdc++6-9-dbg lib64stdc++-9-dev lib64stdc++6-9-dbg libn32stdc++-9-dev libn32stdc++6-9-dbg libx32stdc++-9-dev libx32stdc++6-9-dbg libstdc++-9-doc gnat-9 libgnat-9 libgnat-9-dbg libgnatvsn9-dev libgnatvsn9 libgnatvsn9-dbg gdc-9 gdc-9-multilib libgphobos-9-dev libgphobos76 libgphobos76-dbg lib64gphobos-9-dev lib64gphobos76 lib64gphobos76-dbg lib32gphobos-9-dev lib32gphobos76 lib32gphobos76-dbg libn32gphobos-9-dev libn32gphobos76 libn32gphobos76-dbg libx32gphobos-9-dev libx32gphobos76 libx32gphobos76-dbg gccbrig-9 libhsail-rt-9-dev libhsail-rt0 libhsail-rt0-dbg gcc-9-offload-nvptx libgomp-plugin-nvptx1 gcc-9-source Architecture: source amd64 all Version: 9-20190116-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Description: cpp-9 - GNU C prepr
Bug#918503: marked as done (glusterfs-common: support files not separated from shared library)
Your message dated Thu, 17 Jan 2019 16:00:27 +
with message-id
and subject line Bug#918503: fixed in glusterfs 5.2-2
has caused the Debian Bug report #918503,
regarding glusterfs-common: support files not separated from shared library
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glusterfs-common
Version: 5.2-1
Severity: serious
Justification: 8.2
Tags: patch
Control: block 881526 by -1
glusterfs-common combines shared libraries with a lot of other files and
even a glusterfs user. Doing so violates the Debian policy section 8.2:
| If your package contains files whose names do not change with each
| change in the library shared object version, you must not put them in
| the shared library package.
It is quite evident that the python module, firewalld integration,
logrotate.d snippet and many other files will not change with an soname
bump. Given that other packages (e.g. fio) link libglusterfs0, it is
evident that libglusterfs0 is not a private shared library. Therefore
glusterfs-common violates a policy must.
The attached patch fixes that. I'm filing it as a separate bug, because
the policy violation is much narrower in scope than #881526 is.
Helmut
diff --minimal -Nru glusterfs-5.2/debian/changelog
glusterfs-5.2/debian/changelog
--- glusterfs-5.2/debian/changelog 2018-12-27 12:47:15.0 +0100
+++ glusterfs-5.2/debian/changelog 2019-01-06 20:35:15.0 +0100
@@ -1,3 +1,10 @@
+glusterfs (5.2-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Split out libglusterfs0. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 06 Jan 2019 20:35:15 +0100
+
glusterfs (5.2-1) unstable; urgency=high
* New upstream release.
diff --minimal -Nru glusterfs-5.2/debian/control glusterfs-5.2/debian/control
--- glusterfs-5.2/debian/control2018-12-27 12:47:15.0 +0100
+++ glusterfs-5.2/debian/control2019-01-06 20:30:43.0 +0100
@@ -82,11 +82,9 @@
xfsprogs,
e2fsprogs,
psmisc
-Conflicts: libglusterfs0,
- libglusterfs-dev
+Conflicts: libglusterfs-dev
Breaks: glusterfs-server (<< 3.4.0~qa5)
Replaces: glusterfs-server (<< 3.4.0~qa5),
- libglusterfs0,
libglusterfs-dev
Description: GlusterFS common libraries and translator modules
GlusterFS is a clustered file-system capable of scaling to several
@@ -99,3 +97,22 @@
.
This package includes libglusterfs and glusterfs translator modules
common to both GlusterFS server and client framework.
+
+Package: libglusterfs0
+Architecture: any
+Pre-Depends: ${misc:Pre-Depends}
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends},
+Breaks: glusterfs-common (<< 5.2-1.1)
+Replaces: glusterfs-common (<< 5.2-1.1)
+Description: GlusterFS shared library
+ GlusterFS is a clustered file-system capable of scaling to several
+ petabytes. It aggregates various storage bricks over Infiniband RDMA
+ or TCP/IP interconnect into one large parallel network file
+ system. GlusterFS is one of the most sophisticated file system in
+ terms of features and extensibility. It borrows a powerful concept
+ called Translators from GNU Hurd kernel. Much of the code in GlusterFS
+ is in userspace and easily manageable.
+ .
+ This package contains libglusterfs.
diff --minimal -Nru glusterfs-5.2/debian/glusterfs-common.install
glusterfs-5.2/debian/glusterfs-common.install
--- glusterfs-5.2/debian/glusterfs-common.install 2018-12-27
12:47:15.0 +0100
+++ glusterfs-5.2/debian/glusterfs-common.install 2019-01-06
20:34:11.0 +0100
@@ -3,7 +3,18 @@
usr/sbin/gluster-mountbroker
usr/sbin/gf_attach
usr/sbin/gluster-setgfid2path
-usr/lib/*
+usr/lib/firewalld
+usr/lib/ocf
+usr/lib/python3
+usr/lib/*/glusterfs
+usr/lib/*/*.so
+usr/lib/*/*.la
+usr/lib/*/libgfapi.so.*
+usr/lib/*/libgfchangelog.so.*
+usr/lib/*/libgfdb.so.*
+usr/lib/*/libgfrpc.so.*
+usr/lib/*/libgfxdr.so.*
+usr/lib/*/pkgconfig
usr/share/doc/glusterfs/glusterfs-mode.el usr/share/emacs/site-lisp/
usr/share/doc/glusterfs/benchmarking/
libglusterfs/src/*.h usr/include/glusterfs/
diff --minimal -Nru glusterfs-5.2/debian/glusterfs-common.lintian-overrides
glusterfs-5.2/debian/glusterfs-common.lintian-overrides
--- glusterfs-5.2/debian/glusterfs-common.lintian-overrides 2018-12-27
12:47:15.0 +0100
+++ glusterfs-5.2/debian/glusterfs-common.lintian-overrides 2019-01-06
20:34:46.0 +0100
@@ -1,8 +1,7 @@
glusterfs-common: spelling-error-in-binary
usr/lib/*/glusterfs/*/xlator/features/gfid-access.s
Bug#907277: autoconf: AC_SEARCH_LIBS with AC_LANG([C++]) broken when using gcc 8
On 1/17/19, Paul Gevers wrote: > On 14-01-2019 11:57, Matthias Klose wrote: >> On 12.01.19 21:37, Chaim Zax wrote: >>> Because autoconf can be used outside a Debian environment this solution >>> might not work for everyone. Perhaps the AC_SEARCH_LIBS function should >>> be extended so function arguments needed to check a library could be >>> provided as well, or perhaps there is an other way to make it compatible >>> with g++ 8. >> >> g++ 8 got more strict. You could check if that's the case for g++ 9 as >> well (or >> gcc-snapshot). In any case, autoconf should be adjusted to avoid the >> warning/error. > > Do you happen to know why g++ 8 happens to fail on this library and > doesn't fail on other libraries we checked? Does g++ know which > libraries it includes and is it pickier on those? I'm not familiar with the library in question but the problem appears to be specific to these __atomic_xyz builtins which seem to get special treatment in g++. Other builtins I tested do not exhibit such failures. There is no obvious way to disable the error in GCC: -fno-buitlin appears not to affect these functions and -fpermissive does not resolve the error at the call site. AC_SEARCH_LIBS can present a simple interface based on the assumption that correct declarations are not required to test linking against a particular symbol in a library. Clearly this assumption is not valid for these particular functions in C++ mode, so it is likely that AC_SEARCH_LIBS simply cannot be used to reliably probe for __atomic_xyz functions in libatomic. In that case, configure authors must use an alternate approach. For example, - probing a different function from libatomic, if possible, - probing in C mode, if possible, - using AC_LINK_IFELSE with a valid test program, or - something else? Cheers, Nick
Bug#919087: marked as done (Please remove (build-)dependency on mongodb for buster)
Your message dated Thu, 17 Jan 2019 15:49:27 + with message-id and subject line Bug#919087: fixed in aodh 7.0.0-4 has caused the Debian Bug report #919087, regarding Please remove (build-)dependency on mongodb for buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mongodb Version: 1:3.4.15-1 Severity: serious Justification: Cannot be properly supported MongoDB should not be part of (at least) Buster for the following reasons: - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it to be included in Buster. - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch to SSPLv1 complicates matters. As discussed in #915537, we will not be distributing any SSPL-licensed software, and keeping the last AGPL-licensed version (3.6.8 or 4.0.3) without the ability to cherry-pick upstream fixes is not a viable option. (I am currently not considering distributing mongodb in non-free.) I will not request removal immediately, to allow other packages time to adjust their dependencies, but eventually auto-removal will kick in. That said, MongoDB 3.4 will probably remain in sid for as long as it is AGPL-licensed and supported upstream. Apollon [1] https://www.mongodb.com/support-policy --- End Message --- --- Begin Message --- Source: aodh Source-Version: 7.0.0-4 We believe that the bug you reported is fixed in the latest version of aodh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated aodh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Jan 2019 16:25:48 +0100 Source: aodh Binary: aodh-api aodh-common aodh-doc aodh-evaluator aodh-expirer aodh-listener aodh-notifier python3-aodh Architecture: source all Version: 7.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: aodh-api - OpenStack Telemetry (Ceilometer) Alarming - API server aodh-common - OpenStack Telemetry (Ceilometer) Alarming - common files aodh-doc - OpenStack Telemetry (Ceilometer) Alarming - doc aodh-evaluator - OpenStack Telemetry (Ceilometer) Alarming - alarm evaluator aodh-expirer - OpenStack Telemetry (Ceilometer) Alarming - expirer aodh-listener - OpenStack Telemetry (Ceilometer) Alarming - listener aodh-notifier - OpenStack Telemetry (Ceilometer) Alarming - alarm notifier python3-aodh - OpenStack Telemetry (Ceilometer) Alarming - Python libraries Closes: 919087 Changes: aodh (7.0.0-4) unstable; urgency=medium . * Removed mongodb build-depends (Closes: #919087). Checksums-Sha1: 302f6b0f447efc086ac325ebfb7de665034def9e 3823 aodh_7.0.0-4.dsc 00d0c34a3ee783d58936e344f8b22e9319742ec4 9412 aodh_7.0.0-4.debian.tar.xz d7ccb8404b4b5d620f93b1bfb750c48c4d683a6d 23356 aodh-api_7.0.0-4_all.deb db63cad27027bcfbba0f40509f368986dae924f1 38836 aodh-common_7.0.0-4_all.deb 6aef722ec14c1a49591c9c0984b82fae54a702eb 990916 aodh-doc_7.0.0-4_all.deb 182417bab801255cd5d5ea19b399df0bb9ec6e5a 8484 aodh-evaluator_7.0.0-4_all.deb dc5d080627d6226fe9bfca8835b3a3d477094076 8532 aodh-expirer_7.0.0-4_all.deb 0f903eaef371cf6cde00d71a8c435970c2f519c4 8492 aodh-listener_7.0.0-4_all.deb 666b78ca340469ff940016f08fbd1798150adace 8476 aodh-notifier_7.0.0-4_all.deb 64e3db50209958b743527c5468163275f04cb964 16667 aodh_7.0.0-4_amd64.buildinfo 8be2d0b590f18cb7251ea722fa9e18a650c13e27 92340 python3-aodh_7.0.0-4_all.deb Checksums-Sha256: 145ba2bcacc916aaf58f713123659c9021b2ce4a393568515aa45cf2501431ed 3823 aodh_7.0.0-4.dsc 14d6df3785143f27abdeb9969afabc0e2991d0b9354c9606b076f344936873b3 9412 aodh_7.0.0-4.debian.tar.xz d1e437a9abd0c50b5fc4857392afcce7590abef88df0e4131aaf246740b3e651 23356 aodh-api_7.0.0-4_all.deb cf8a0a6c1f8a7081f540763dcb135afba9539191479a8b69986ff21910be8689 38836 aodh-common_7.0.0-4_all.deb eb1cefd02b2d0898ba7d6f4d76c147be5b26c13bb5043e5bf9877ad208ecd0f5 990916 aodh-doc_7.0.0-4_al
Processed: Bug #919087 in aodh marked as pending
Processing control commands: > tag -1 pending Bug #919087 [aodh] Please remove (build-)dependency on mongodb for buster Added tag(s) pending. -- 919087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919087: Bug #919087 in aodh marked as pending
Control: tag -1 pending Hello, Bug #919087 in aodh 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: https://salsa.debian.org/openstack-team/services/aodh/commit/7a4cc1e936632cb7ecb2c1fcbbb5369ce82af993 Removed mongodb build-depends (Closes: #919087). (this message was generated automatically) -- Greetings https://bugs.debian.org/919087
Bug#916890: libopenmpi3: I cannot upgrade the lastest version
Package: libopenmpi3 Version: 3.1.3-5 Severity: important Dear Maintainer, When i try to upgrade the files, show: Unpacking libopenmpi3:amd64 (3.1.3-9) over (3.1.3-5) ... rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file or directory rm: cannot remove 'End': No such file or directory rm: cannot remove 'automatically': No such file or directory rm: cannot remove 'added': No such file or directory rm: cannot remove 'section': No such file or directory dpkg: warning: old libopenmpi3:amd64 package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/libopenmpi3_3.1.3-9_amd64.deb (--unpack): there is no script in the new version of the package - giving up Unpacking openmpi-common (3.1.3-9) over (3.1.3-5) ... rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file or directory rm: cannot remove 'End': No such file or directory rm: cannot remove 'automatically': No such file or directory rm: cannot remove 'added': No such file or directory rm: cannot remove 'section': No such file or directory dpkg: warning: old openmpi-common package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/openmpi-common_3.1.3-9_all.deb (--unpack): there is no script in the new version of the package - giving up Errors were encountered while processing: /var/cache/apt/archives/libopenmpi3_3.1.3-9_amd64.deb /var/cache/apt/archives/openmpi-common_3.1.3-9_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) dpkg: dependency problems prevent configuration of libopenmpi-dev:amd64: libopenmpi-dev:amd64 depends on libopenmpi3 (= 3.1.3-9); however: Version of libopenmpi3:amd64 on system is 3.1.3-5. libopenmpi-dev:amd64 depends on openmpi-common (>= 3.1.3-9); however: Version of openmpi-common on system is 3.1.3-5. [...] Errors were encountered while processing: libopenmpi-dev:amd64 openmpi-bin libhdf5-openmpi-dev libcoarrays-openmpi-dev:amd64 libhdf5-mpi-dev Reggards, Vinicius Couto -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:$ Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenmpi3 depends on: ii libc62.28-5 ii libevent-2.1-6 2.1.8-stable-4 ii libevent-pthreads-2.1-6 2.1.8-stable-4 ii libfabric1 1.6.2-2 ii libgcc1 1:8.2.0-14 ii libgfortran5 8.2.0-14 ii libhwloc-plugins 1.11.12-1 ii libhwloc51.11.12-1 ii libibverbs1 21.0-1 ii libnl-3-200 3.4.0-1 ii libnl-route-3-2003.4.0-1 ii libpmix2 3.1.0~rc4-1 ii libpsm-infinipath1 3.3+20.604758e7-6 ii libpsm2-211.2.68-4 ii libquadmath0 8.2.0-14 ii libstdc++6 8.2.0-14 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages libopenmpi3 recommends: iu openmpi-bin 3.1.3-9 libopenmpi3 suggests no packages. -- no debconf information Reggards, Vinicius Couto
Processed: block 850798 with 825501
Processing commands for cont...@bugs.debian.org:
> block 850798 with 825501
Bug #850798 {Done: Emmanuel Bourg } [libvorbis-java] tika:
FTBFS: Could not resolve dependencies for project
org.apache.tika:tika-parsers:jar:1.5
850798 was not blocked by any bugs.
850798 was not blocking any bugs.
Added blocking bug(s) of 850798: 825501
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
850798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#919167: marked as done (tmuxp FTBFS and completely broken with python-click 7.0-1)
Your message dated Thu, 17 Jan 2019 15:20:14 +
with message-id
and subject line Bug#919167: fixed in tmuxp 1.5.0a-1
has caused the Debian Bug report #919167,
regarding tmuxp FTBFS and completely broken with python-click 7.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
919167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tmuxp
Version: 1.4.0-2
Severity: important
Dear Maintainer,
when I start tmuxp it crashes immediately with the following output:
Traceback (most recent call last):
File "/usr/bin/tmuxp", line 11, in
load_entry_point('tmuxp==1.4.0', 'console_scripts', 'tmuxp')()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 487, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2728,
in load_entry_point
return ep.load()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2346,
in load
return self.resolve()
File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2352,
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
File "/usr/lib/python3/dist-packages/tmuxp/__init__.py", line 20, in
from . import config, util, cli
File "/usr/lib/python3/dist-packages/tmuxp/cli.py", line 550, in
help='Like -2, but indicates that the terminal supports 88 colours.')
File "/usr/lib/python3/dist-packages/click/decorators.py", line 151, in
decorator
_param_memo(f, ArgumentClass(param_decls, **attrs))
File "/usr/lib/python3/dist-packages/click/core.py", line 1808, in __init__
Parameter.__init__(self, param_decls, required=required, **attrs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1338, in __init__
self._parse_decls(param_decls or (), expose_value)
File "/usr/lib/python3/dist-packages/click/core.py", line 1841, in
_parse_decls
'parameter declaration, got %d' % len(decls))
TypeError: Arguments take exactly one parameter declaration, got 2
Tested in xterm and gnome-terminal.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tmuxp depends on:
ii python33.7.1-3
ii python3-pkg-resources 40.6.2-1
ii python3-tmuxp 1.4.0-2
tmuxp recommends no packages.
tmuxp suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tmuxp
Source-Version: 1.5.0a-1
We believe that the bug you reported is fixed in the latest version of
tmuxp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 919...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastien Delafond (supplier of updated tmuxp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 16 Jan 2019 18:00:23 +0100
Source: tmuxp
Binary: tmuxp python-tmuxp python3-tmuxp
Architecture: source
Version: 1.5.0a-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond
Changed-By: Sebastien Delafond
Description:
python-tmuxp - tmux session manager (Python 2)
python3-tmuxp - tmux session manager (Python 3)
tmuxp - tmux session manager
Closes: 919167
Changes:
tmuxp (1.5.0a-1) unstable; urgency=medium
.
* New upstream release (Closes: #919167)
Checksums-Sha1:
45e46e4081c67f56edd0db8485f5206e051c2888 1915 tmuxp_1.5.0a-1.dsc
f1078ba35c7651342b252052ea3cdccdee404704 612064 tmuxp_1.5.0a.orig.tar.xz
4e3e37e7ad15953bfa27388989f07302cc70d0bc 3344 tmuxp_1.5.0a-1.debian.tar.xz
5374194c42128991cc6587f1573818cdbea86201 8274 tmuxp_1.5.0a-1_amd64.buildinfo
Checksums-Sha256:
43f7d23d3c99f9833e492c56ed96466ce87f4fa5f74ebde05c5252fc367cc869 1915
tmuxp_1.5.0a-1.dsc
34a068fb867dd055a77cb7528347c29d720067a2238e71
Bug#915756: tweepy: diff for NMU version 3.6.0-1.1
Control: tags 915756 + patch
Control: tags 915756 + pending
Dear maintainer,
I've prepared an NMU for tweepy (versioned as 3.6.0-1.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
diff -Nru tweepy-3.6.0/debian/changelog tweepy-3.6.0/debian/changelog
--- tweepy-3.6.0/debian/changelog 2018-10-16 16:09:28.0 +0300
+++ tweepy-3.6.0/debian/changelog 2019-01-17 17:09:41.0 +0200
@@ -1,3 +1,10 @@
+tweepy (3.6.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for FTBFS with pip >= 10. (Closes: #915756)
+
+ -- Adrian Bunk Thu, 17 Jan 2019 17:09:41 +0200
+
tweepy (3.6.0-1) unstable; urgency=medium
* Team upload
diff -Nru tweepy-3.6.0/debian/patches/0001-1029-migrate-requirements-to-setup.py-reference-in-r.patch tweepy-3.6.0/debian/patches/0001-1029-migrate-requirements-to-setup.py-reference-in-r.patch
--- tweepy-3.6.0/debian/patches/0001-1029-migrate-requirements-to-setup.py-reference-in-r.patch 1970-01-01 02:00:00.0 +0200
+++ tweepy-3.6.0/debian/patches/0001-1029-migrate-requirements-to-setup.py-reference-in-r.patch 2019-01-17 17:09:41.0 +0200
@@ -0,0 +1,62 @@
+From 778bd7a31d2f5fae98652735e7844533589ca221 Mon Sep 17 00:00:00 2001
+From: Ben Cipollini
+Date: Wed, 18 Apr 2018 10:26:07 -0700
+Subject: #1029 - migrate requirements to setup.py, reference in
+ requirements.txt
+
+---
+ requirements.txt | 7 +++
+ setup.py | 11 ++-
+ 2 files changed, 9 insertions(+), 9 deletions(-)
+
+diff --git a/requirements.txt b/requirements.txt
+index 1444031..cd8c47d 100644
+--- a/requirements.txt
b/requirements.txt
+@@ -1,4 +1,3 @@
+-requests>=2.11.1
+-requests_oauthlib>=0.7.0
+-six>=1.10.0
+-PySocks>=1.5.7
++--index-url https://pypi.python.org/simple/
++
++-e .
+diff --git a/setup.py b/setup.py
+index 18c5910..5688c2f 100644
+--- a/setup.py
b/setup.py
+@@ -2,7 +2,6 @@
+ #from distutils.core import setup
+ import re, uuid
+ from setuptools import setup, find_packages
+-from pip.req import parse_requirements
+
+ VERSIONFILE = "tweepy/__init__.py"
+ ver_file = open(VERSIONFILE, "rt").read()
+@@ -14,9 +13,6 @@ if mo:
+ else:
+ raise RuntimeError("Unable to find version string in %s." % (VERSIONFILE,))
+
+-install_reqs = parse_requirements('requirements.txt', session=uuid.uuid1())
+-reqs = [str(req.req) for req in install_reqs]
+-
+ setup(name="tweepy",
+ version=version,
+ description="Twitter library for python",
+@@ -25,7 +21,12 @@ setup(name="tweepy",
+ author_email="twe...@googlegroups.com",
+ url="http://github.com/tweepy/tweepy";,
+ packages=find_packages(exclude=['tests','examples']),
+- install_requires=reqs,
++ install_requires=[
++ "requests>=2.11.1",
++ "requests_oauthlib>=0.7.0",
++ "six>=1.10.0",
++ "PySocks>=1.5.7",
++ ],
+ keywords="twitter library",
+ classifiers=[
+ 'Development Status :: 4 - Beta',
+--
+2.11.0
+
diff -Nru tweepy-3.6.0/debian/patches/series tweepy-3.6.0/debian/patches/series
--- tweepy-3.6.0/debian/patches/series 2018-10-16 16:09:28.0 +0300
+++ tweepy-3.6.0/debian/patches/series 2019-01-17 17:09:41.0 +0200
@@ -1,2 +1,3 @@
fix-python3-7.patch
change-find-packages.patch
+0001-1029-migrate-requirements-to-setup.py-reference-in-r.patch
Processed: tweepy: diff for NMU version 3.6.0-1.1
Processing control commands: > tags 915756 + patch Bug #915756 [src:tweepy] tweepy FTBFS with python-pip 18.1 Added tag(s) patch. > tags 915756 + pending Bug #915756 [src:tweepy] tweepy FTBFS with python-pip 18.1 Added tag(s) pending. -- 915756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915756 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919513: marked as done (CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445)
Your message dated Thu, 17 Jan 2019 15:04:22 + with message-id and subject line Bug#919513: fixed in ntpsec 1.1.3+dfsg1-1 has caused the Debian Bug report #919513, regarding CVE-2019-6442 CVE-2019-6443 CVE-2019-6444 CVE-2019-6445 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ntpsec Severity: grave Tags: security Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6442 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6443 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6444 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6445 Cheers, Moritz --- End Message --- --- Begin Message --- Source: ntpsec Source-Version: 1.1.3+dfsg1-1 We believe that the bug you reported is fixed in the latest version of ntpsec, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Richard Laager (supplier of updated ntpsec package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 04:17:46 -0600 Source: ntpsec Binary: ntpsec ntpsec-ntpdate ntpsec-ntpviz ntpsec-doc python3-ntp Architecture: source Version: 1.1.3+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Richard Laager Changed-By: Richard Laager Description: ntpsec - Network Time Protocol daemon and utility programs ntpsec-doc - Network Time Protocol documentation ntpsec-ntpdate - client for setting system time from NTP servers ntpsec-ntpviz - NTP statistics graphing utility python3-ntp - Python 3 NTP Helper Classes Closes: 919513 Changes: ntpsec (1.1.3+dfsg1-1) unstable; urgency=high . * New upstream version (Closes: 919513) - Lots of typo fixes, documentation cleanups, test targets. - CVE-2019-6442: "An authenticated attacker can write one byte out of bounds in ntpd via a malformed config request, related to config_remotely in ntp_config.c, yyparse in ntp_parser.tab.c, and yyerror in ntp_parser.y." - CVE-2019-6443: "Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd. - CVE-2019-6444: "process_control() in ntp_control.c has a stack-based buffer over-read because attacker-controlled data is dereferenced by ntohl() in ntpd." - CVE-2019-6445: "An authenticated attacker can cause a NULL pointer dereference and ntpd crash in ntp_control.c, related to ctl_getitem." * Drop debian/patches/fix-ntploggps.patch (merged upstream) * Refresh patches * Revert "Use python3-gps" At this time, python3-gps is only available in experimental. * Disable the waf PYTHON_GPS check * Update debian/copyright * Fix ntpdate.8 documentation of -B * Changes as of ntp_4.2.8p12+dfsg-3 have been merged as appropriate: - Update ntpdate.8 from ntpdate.html Thanks to Bernhard Schmidt - Update ntpdate.README.Debian Thanks to Bernhard Schmidt - As a notable exception, while the ntp package has removed the ntpdate hooks, I have not (yet?) done so in ntpsec. * Set Rules-Requires-Root: no * Sort debian/ntpsec.maintscript Checksums-Sha1: cb7a77e51c191d2cffac80dfdf15e020a1e0fc16 2385 ntpsec_1.1.3+dfsg1-1.dsc a4edb6006102f5c641d7c3a786c7bb8eaee91f49 2490447 ntpsec_1.1.3+dfsg1.orig.tar.gz 89a0f0c26e20893495478f6a4c4af013d3a3a674 44248 ntpsec_1.1.3+dfsg1-1.debian.tar.xz c4377c8a7c7cd5f16b8f3e174d9bf41405b27d25 9185 ntpsec_1.1.3+dfsg1-1_amd64.buildinfo Checksums-Sha256: 583ba864f845177857516279e1a08f60d9f52b4dd5176b91371da00ecc7b56ce 2385 ntpsec_1.1.3+dfsg1-1.dsc 5e5525ea8ea2e75ce9fb6dbf47cb4cd919e8929ee9f99f2e00bfcf3d2f1a7410 2490447 ntpsec_1.1.3+dfsg1.orig.tar.gz 98725fc86f92d6b0fc104bfc6b6310fde40c3c3dd756aabe156996b5cd7a8fc2 44248 ntpsec_1.1.3+dfsg1-1.debian.tar.xz 3ca0393599113f307e56f2c2f7da8c8f27f93cb62c4b6fb8c9be24edd7c9d59a 9185 ntpsec_1.1.3+dfsg1-1_amd64.buildinfo Files: 57b2538607e125e188f9c559be5b7677 2385 net optional ntpsec_1
Bug#918913: marked as done (nbconvert 5.4 breaks nbsphinx)
Your message dated Thu, 17 Jan 2019 14:46:09 + with message-id and subject line Bug#918913: fixed in nbconvert 5.4-2 has caused the Debian Bug report #918913, regarding nbconvert 5.4 breaks nbsphinx to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nbconvert, nbsphinx Control: found -1 nbconvert/5.4-1 Control: found -1 nbsphinx/0.4.1+ds-3 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of nbconvert the autopkgtest of nbsphinx fails in testing when that autopkgtest is run with the binary packages of nbconvert from unstable. It passes when run with only packages from testing. In tabular form: passfail nbconvert from testing5.4-1 nbsphinx from testing0.4.1+ds-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration of nbconvert to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=nbconvert https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbsphinx/1678109/log.gz autopkgtest [04:53:31]: test perform-doc: [--- Running Sphinx v1.7.9 making output directory... loading pickled environment... not yet created building [mo]: targets for 0 po files that are out of date building [html]: targets for 20 source files that are out of date updating environment: 20 added, 0 changed, 0 removed reading sources... [ 5%] a-normal-rst-file reading sources... [ 10%] allow-errors WARNING: could not open bibtex file /tmp/autopkgtest-lxc.3g0_jnfw/downtmp/autopkgtest_tmp/doc/references.bib. Notebook error: AttributeError in allow-errors.ipynb: 'NoneType' object has no attribute 'argv' autopkgtest [04:53:32]: test perform-doc: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: nbconvert Source-Version: 5.4-2 We believe that the bug you reported is fixed in the latest version of nbconvert, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated nbconvert package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 15:31:11 +0100 Source: nbconvert Binary: python-nbconvert python3-nbconvert jupyter-nbconvert python-nbconvert-doc Architecture: source all Version: 5.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Julien Puydt Description: jupyter-nbconvert - Jupyter notebook conversion (scripts) python-nbconvert - Jupyter notebook conversion (Python 2) python-nbconvert-doc - Jupyter notebook conversion (documentation) python3-nbconvert - Jupyter notebook conversion (Python 3) Closes: 918913 Changes: nbconvert (5.4-2) unstable; urgency=medium . * Add upstream patch (Closes: #918913) Checksums-Sha1: a8ee463458c7fb312849c188cae0f9de0bd9148a 3204 nbconvert_5.4-2.dsc aec2643f17e1381ddd6ba24dc511e6b5e1ff5b3b 7404 nbconvert_5.4-2.debian.tar.xz 3e9739f2c04b051c814aaa2c964e3ac565cc3f17 12592 jupyter-nbconvert_5.4-2_all.deb dc27ef95dcfeb2c51b665c709410c06c77ad37d8 16900 nbconvert_5.4-2_amd64.buildinfo 86ef7df31dc7ac0d44bc083a2eeb03251ae9b9f1 256400 python-nbconvert-doc_5.4-2_all.deb 35c6304a11dab0686e8ac62d0e064f68505b49f9 102712 python-nbconvert_5.4-2_all.deb 0847b3be315dcdf9a226bc2297cc0f1a7990d03a 102840 python3-nbconvert_5.4-2_all.deb Checksums-Sha256: 1fc771803b837cc405fd5adbdfc278396ae0f0947
Processed: user debian...@lists.debian.org, usertagging 917418, usertagging 919048, usertagging 912410 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 917418 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 919048 piuparts There were no usertags set. Usertags are now: piuparts. > usertags 912410 piuparts There were no usertags set. Usertags are now: piuparts. > affects 912410 + python3-igraph Bug #912410 [src:python-igraph] python-igraph's tests fail with Python 3.7 Added indication that 912410 affects python3-igraph > affects 919310 + kdiff3-qt Bug #919310 [kdiff3] kdiff3: ships documentation already in kdiff3-doc Added indication that 919310 affects kdiff3-qt > found 857680 llvm-7-examples/1:7.0.1-4 Bug #857680 [llvm-6.0-examples] llvm-3.8-examples: broken symlinks: /usr/share/doc/llvm-3.8-examples/Makefile.* -> ../../../lib/llvm-3.8/build/Makefile.* The source llvm-7-examples and version 1:7.0.1-4 do not appear to match any binary packages Marked as found in versions llvm-7-examples/1:7.0.1-4. > found 891591 lld/1:7.0-47 Bug #891591 [lld] lld: broken symlink: /usr/share/man/man1/lld.1.gz -> lld-5.0.1.gz The source lld and version 1:7.0-47 do not appear to match any binary packages Marked as found in versions lld/1:7.0-47. > found 857522 1:9.11.5.P1+dfsg-1 Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks: /usr/lib/x86_64-linux-gnu/liblwres-export.so -> /lib/x86_64-linux-gnu/liblwres-export.so.141, /usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10 Marked as found in versions bind9/1:9.11.5.P1+dfsg-1. > found 857653 liblld-7/1:7.0.1-4 Bug #857653 [liblld-6.0] liblld-4.0: missing liblld-4.0.so.1 The source liblld-7 and version 1:7.0.1-4 do not appear to match any binary packages Marked as found in versions liblld-7/1:7.0.1-4. > found 905282 python-lldb-7/1:7.0.1-4 Bug #905282 [python-lldb-6.0] python-lldb-6.0: broken symlinks: /usr/lib/llvm-6.0/lib/python2.7/site-packages/lldb/* The source python-lldb-7 and version 1:7.0.1-4 do not appear to match any binary packages Marked as found in versions python-lldb-7/1:7.0.1-4. > found 857954 2:1.02.155-1 Bug #857954 [libdevmapper-dev] libdevmapper-dev: broken symlink: /usr/lib//libdevmapper-event-lvm2.so -> /lib//libdevmapper-event-lvm2.so.2.02 Marked as found in versions lvm2/2.03.02-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 857522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857522 857653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857653 857680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857680 857954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857954 891591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891591 905282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905282 912410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912410 919310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919583: ebtables: broken symlinks: /sbin/ebtables{,-restore,-save} -> /usr/sbin/ebtables{,-restore,-save}
Package: ebtables Version: 2.0.10.4+snapshot20181205-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m33.7s ERROR: FAIL: Broken symlinks: /sbin/ebtables-restore -> /usr/sbin/ebtables-restore /sbin/ebtables-save -> /usr/sbin/ebtables-save /sbin/ebtables -> /usr/sbin/ebtables cheers, Andreas ebtables_2.0.10.4+snapshot20181205-1.log.gz Description: application/gzip
Bug#919582: libhmsbeagle-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libhmsbeagle-opencl.so -> libhmsbeagle-opencl.so.21
Package: libhmsbeagle-dev Version: 3.1.2+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m33.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libhmsbeagle-opencl.so -> libhmsbeagle-opencl.so.21 (libhmsbeagle-dev) cheers, Andreas libhmsbeagle-dev_3.1.2+dfsg-2.log.gz Description: application/gzip
Bug#907277: autoconf: AC_SEARCH_LIBS with AC_LANG([C++]) broken when using gcc 8
Hi Doko, Thanks for your reply. On 14-01-2019 11:57, Matthias Klose wrote: > On 12.01.19 21:37, Chaim Zax wrote: >> Because autoconf can be used outside a Debian environment this solution >> might not work for everyone. Perhaps the AC_SEARCH_LIBS function should >> be extended so function arguments needed to check a library could be >> provided as well, or perhaps there is an other way to make it compatible >> with g++ 8. > > g++ 8 got more strict. You could check if that's the case for g++ 9 as well > (or > gcc-snapshot). In any case, autoconf should be adjusted to avoid the > warning/error. Do you happen to know why g++ 8 happens to fail on this library and doesn't fail on other libraries we checked? Does g++ know which libraries it includes and is it pickier on those? Paul signature.asc Description: OpenPGP digital signature
Bug#919578: rozofs: FTBFS with undefined references to major, minor
Hi, On Thu, 17 Jan 2019, Andreas Beckmann wrote: > rozofs recently started to FTBFS in an up-to-date sid+experimental > pbuilder environment: FWIW, I filed earlier today an RM bug: https://bugs.debian.org/919568 So I don't plan to handle this bug. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Processed: 916909
Processing commands for cont...@bugs.debian.org: > affects 916909 + 0ad Bug #916909 [libnvtt2] libnvtt2/experimental: nvtt::InputOptions::setTextureLayout(nvtt::TextureType, int, int, int) removed without SONAME bump Added indication that 916909 affects 0ad > End of message, stopping processing here. Please contact me if you need assistance. -- 916909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919577: g++-8: Can't build GN tool due to bug in raw-string parsing
Processing control commands: > tags -1 + moreinfo Bug #919577 [g++-8] g++-8: Can't build GN tool due to bug in raw-string parsing Added tag(s) moreinfo. > severity -1 normal Bug #919577 [g++-8] g++-8: Can't build GN tool due to bug in raw-string parsing Severity set to 'normal' from 'serious' -- 919577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919577: g++-8: Can't build GN tool due to bug in raw-string parsing
Control: tags -1 + moreinfo
Control: severity -1 normal
works for me.
On 17.01.19 13:52, Allan Sandfeld Jensen wrote:
> const char kFormat_Help[] =
> R"(gn format [--dump-tree] (--stdin | )
>
> Formats .gn file to a standard format.
>
> The contents of some lists ('sources', 'deps', etc.) will be sorted to a
> canonical order. To suppress this, you can add a comment of the form "#
> NOSORT" immediately preceding the assignment. e.g.
>
> # NOSORT
> sources = [
> "z.cc",
> "a.cc",
> ]
> )";
Bug#918567: Maintaining dlib in Debian Science team (Was: dlib: FTBFS when built with dpkg-buildpackage -A)
Hi Hugo and Séverin On Wed, Jan 16, 2019 at 05:27:56PM +0100, Hugo Lefeuvre wrote: > > Of course I would be glad to maintain this package under the Debian Science > Team umbrella. Feel free to upload. Thanks for your both confirmation that the package can go into Debian Science. I've forked https://salsa.debian.org/hle/dlib to https://salsa.debian.org/science-team/dlib and uploaded the fixed package. I'd recommend you remove your old repository from Salsa soon. I've also added you both to the Debian Science team so you will have no problem to commit to the new repository (or any other Debian Science repository at your preference if you intend to help with other packages). BTW, I noticed that there is a new upstream version. While I usually try to get the latest upstream version if I'm doing team uploads I need to admit that I was not fully sure how you create the upstream tarballs of the multi-tarball source and thus left the source as is. It might be helpful for the future if you drop a debian/README.source with clear advise what to do. BTW, if you might maintain further science relevant packages I'd happily help to migrate these to the Debian Science team if you are interested. Kind regards Andreas. -- http://fam-tille.de
Bug#919578: rozofs: FTBFS with undefined references to major, minor
Source: rozofs Version: 2.6.2-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, rozofs recently started to FTBFS in an up-to-date sid+experimental pbuilder environment: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/rozofs-2.6.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fmessage-length=0 -O3 -DNDEBUG -D_GNU_SOURCE -g -Wl,-z,relr o -Wl,-z,now -rdynamic CMakeFiles/storio.dir/sconfig.c.o CMakeFiles/storio.dir/storage.c.o CMakeFiles/storio.dir/sproto_nb.c.o CMakeFiles/storio.dir/sprotosvc_nb.c.o CMakeFiles/storio.dir/storio_nblock_init.c.o C MakeFiles/storio.dir/storio_north_intf.c.o CMakeFiles/storio.dir/storage_fd_cache.c.o CMakeFiles/storio.dir/storio.c.o CMakeFiles/storio.dir/storio_cache.c.o CMakeFiles/storio.dir/storio_bufcache.c.o CMakeFiles/s torio.dir/storio_disk_thread_intf.c.o CMakeFiles/storio.dir/storio_device_monitor.c.o CMakeFiles/storio.dir/storio_disk_thread.c.o CMakeFiles/storio.dir/storio_device_mapping.c.o CMakeFiles/storio.dir/storio_seri alization.c.o CMakeFiles/storio.dir/storio_fid_cache.c.o CMakeFiles/storio.dir/storio_crc32.c.o -o storio -L/build/rozofs-2.6.2/obj-x86_64-linux-gnu/rozofs ../../rozofs/librozofs.a -lpthread -luuid -lconfig -ln uma /usr/bin/ld: CMakeFiles/storio.dir/storio_device_monitor.c.o: in function `storio_device_get_major_and_minor': ./obj-x86_64-linux-gnu/src/storaged/./src/storaged/storio_device_monitor.c:488: undefined reference to `major' /usr/bin/ld: ./obj-x86_64-linux-gnu/src/storaged/./src/storaged/storio_device_monitor.c:489: undefined reference to `minor' collect2: error: ld returned 1 exit status Cheers, Andreas rozofs_2.6.2-2.log.gz Description: application/gzip
Bug#919577: g++-8: Can't build GN tool due to bug in raw-string parsing
Package: g++-8
Version: 8.2.0-14
Severity: serious
Can not compile code with something looking like a precompiler directive inside
a raw-string. For instance code like this:
const char kFormat_Help[] =
R"(gn format [--dump-tree] (--stdin | )
Formats .gn file to a standard format.
The contents of some lists ('sources', 'deps', etc.) will be sorted to a
canonical order. To suppress this, you can add a comment of the form "#
NOSORT" immediately preceding the assignment. e.g.
# NOSORT
sources = [
"z.cc",
"a.cc",
]
)";
The compiler complains it doesn't understand the #NOSORT directive.
I can not reproduce the issue with upstream g++-8 or with g++-7, it appears to
be a serious
flaw in specifically this Debian version of g++-8.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages g++-8 depends on:
ii gcc-88.2.0-14
ii gcc-8-base 8.2.0-14
ii libc62.28-5
ii libgmp10 2:6.1.2+dfsg-4
ii libisl19 0.20-2
ii libmpc3 1.1.0-1
ii libmpfr6 4.0.2~rc1-1
ii libstdc++-8-dev 8.2.0-14
ii zlib1g 1:1.2.11.dfsg-1
g++-8 recommends no packages.
Versions of packages g++-8 suggests:
ii g++-8-multilib8.2.0-14
pn gcc-8-doc
pn libstdc++6-8-dbg
-- no debconf information
Bug#918626: marked as done (node-loader-utils FTBFS with nodejs 10.15.0)
Your message dated Thu, 17 Jan 2019 12:50:16 + with message-id and subject line Bug#918626: fixed in node-loader-utils 1.1.0-2 has caused the Debian Bug report #918626, regarding node-loader-utils FTBFS with nodejs 10.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 918626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918626 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-loader-utils Version: 1.1.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-loader-utils.html ... 89 passing (476ms) 1 failing 1) parseQuery() when passed string is any other string not starting with ? should throw an error: TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is ambiguous. The error message "A valid query string passed to parseQuery should begin with '?'" is identical to the message. at expectsError (assert.js:629:15) at Function.throws (assert.js:690:3) at Context.it (test/parseQuery.test.js:76:11) at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21) at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7) at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10) at /usr/lib/nodejs/mocha/lib/runner.js:560:12 at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14) at /usr/lib/nodejs/mocha/lib/runner.js:366:7 at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14) at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5) make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1 --- End Message --- --- Begin Message --- Source: node-loader-utils Source-Version: 1.1.0-2 We believe that the bug you reported is fixed in the latest version of node-loader-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 918...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-loader-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Jan 2019 13:24:56 +0100 Source: node-loader-utils Binary: node-loader-utils Architecture: source Version: 1.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 918626 Description: node-loader-utils - utils for webpack loaders Changes: node-loader-utils (1.1.0-2) unstable; urgency=medium . * Team upload * Add patch to fix error string. Fixes debci (Closes: #918626) * Bump debheper compatibility level to 11 * Declare compliance with policy 4.3.0 * Update VCS fields to salsa * Add Berne Convention comment in debian/copyright * Change section to javascript * Ignore tests in nocheck is set * Add upstream/metadata Checksums-Sha1: 143a7f66ff139487ecbe61b41748298267609658 2196 node-loader-utils_1.1.0-2.dsc ff034d1f7dcca3828559ad0b0126b7d2d630b0a6 2852 node-loader-utils_1.1.0-2.debian.tar.xz Checksums-Sha256: 699868e1c445ed6d72db56a1f36359cdc630843b217fe8bd050d75d78f4112eb 2196 node-loader-utils_1.1.0-2.dsc 389687905ab356ad6ad274d32de6ca0914d01cd1edd4f49b93920fbca85a3b2e 2852 node-loader-utils_1.1.0-2.debian.tar.xz Files: 01b9c005dfb0a73eded3a18dcf918767 2196 javascript optional node-loader-utils_1.1.0-2.dsc 852b86aebfbc3fcdc5d8298b57bd9e3e 2852 javascript optional node-loader-utils_1.1.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxAdd8QHHlhZGRAZGVi aWFuLm9yZwAKCRD210ynyZnu6RwaD/sEmhL1IuZkNXyqhasXnckbSE4IMLH64IHF 0Nf9Jdz1iK1AXHMgE4K/lV5UZjBFczz6Qw88/+XYnt+oBwTZYta6oYVZJpl3sm4y SzSsuP29BnspGXnVDnXZs/Xcq3q+tZj1ejigUmnwcmCxp9A6HCNkoThrGvJ1wDz3 IkWkGAxrbJtVgGM8qFoVmwmIH2PO6hDqn3TzHv+5afqMrtzmn0r0YRXDLrCYSYK9 KkYVss2WKMYlf1b3A7+6jLoecNbLJ54rBu4+KEM7yJvoJi21dhk0iemHA2KgcJg0 wXQnA80cbws0sCykhw3SQ6yKdCQuLtElnVVEmNOtMXCApf/jwfkZB8gDJUphMgyI b6Lt+nL+UScJxDZJE6zInyBg6rxUb11PPqJHhEgKyDQYzXMVPxis26tfxa/Xrp46 dno5k/cs/08r8WHLC7d5ajCM7zU8gvRKeZ8a03CA8lewIhOd7c6d63MBLm2uWUYD Tzo2dCRI7ukBMKl08yMkD3NQ66GcD63M2aAf0nvMRrsWpAJ647SpalEFnlYEc9th kUCEaLdJ/kXNmFElpQfb7O/e2/272So3yY1JHqmrVWe3T
Processed: Re: Bug#918163: Broken in Stretch
Processing commands for cont...@bugs.debian.org: > tags 918163 stretch Bug #918163 [xul-ext-sieve] Broken in Stretch Added tag(s) stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 918163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919554: Small fix
Hi!
A small fix:
Do it as root
cd /usr/lib/virtualbox/
chmod 0755 {VBox{Headless,Net{AdpCtl,DHCP,NAT},SDL,VolInfo},VirtualBox}
chmod 4755 {VBox{Headless,Net{AdpCtl,DHCP,NAT},SDL,VolInfo},VirtualBoxVM}
CU
Michael
--
,''`.
: :' : Michael Ott
`. `'e-mail: michael at k-c13 dot org
`-
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
signature.asc
Description: PGP signature
