Bug#879123: glee: source for configure is missing
On Thu, Oct 19, 2017 at 10:52:41PM +0200, Markus Koschany wrote: > I am quoting: > > https://sources.debian.net/src/glee/5.4.0-2/configure/ > > The license is very liberal. You can argue that it should be mentioned > in debian/copyright but that does not make the file non-free or > unsuitable for Debian main. The license is a lie. It is clear that there is some source file that was used to generate configure. Thus configure is a derivative work of that file. As Adrian pointed out, very likely the FSF isn't the copyright holder for that source file and very likely this permissive "you can do anything" license does not apply to the source file. Saying that a generated configure script is free software is kinda stupid. The essence of free software is to provide users with the ability to modify it and this freedom is lost when all they have is the generated file. > This is not true. The configure file is human readable and the preferred > source of modification in this case. Please also note that the author of > glee licensed his work under the more liberal BSD-2-clause license. You > cannot compare two very distinct issues like minified JS files and > automake files and claim consensus has been reached already. I have worked with *lots* of configure scripts and I can say that I never preferred modifying the generated script. Since configure scripts don't have reasonable indentation, the program structure is completely lost. Looking at them feels a lot like reading a binary disassembly. I contend that "human readable" is not a reasonable assessment either. > Again quoted out of context and not relevant in this case. The source is > the configure script. Period. Please feel free to discuss this on > debian-devel or move it to the CTTE. I am willing to oppose this > nonsense and harmful misinterpretation of Debian's Policy whenever and > wherever I can. If you insist on disucssing this in a larger scope, chances are a ftp master will notice and remove glee from stable (given Ximin's findings) as it is not clear whether glee is distributable at all. Do you realize that my original motivation in reporting this bug was that I found a build issue with glee and wanted to write a patch? The absence of source makes that difficult and makes DFSG#3 rather theoretical. Why does DFGS#3 assure a "right to modify" when modification is often impratical? I start to wonder whether we should start a GR to clarify DFSG#3 that modification should be practical. Helmut
Bug#879123: glee: source for configure is missing
On Fri, Oct 20, 2017 at 4:52 AM, Markus Koschany wrote: > This is not true. The configure file is human readable and the preferred > source of modification in this case. Please also note that the author of > glee licensed his work under the more liberal BSD-2-clause license. You > cannot compare two very distinct issues like minified JS files and > automake files and claim consensus has been reached already. ... > Again quoted out of context and not relevant in this case. The source is > the configure script. Period. Please feel free to discuss this on > debian-devel or move it to the CTTE. I am willing to oppose this > nonsense and harmful misinterpretation of Debian's Policy whenever and > wherever I can. The configure file is almost always generated from another file and never modified, so it can never be the preferred form for modification. This is obviously the case here. I don't understand your reasoning, could you explain it? -- bye, pabs https://wiki.debian.org/PaulWise
Bug#875492: marked as done ([exfalso] Package lacks dependencies)
Your message dated Fri, 20 Oct 2017 03:09:06 +
with message-id
and subject line Bug#875492: fixed in quodlibet 3.9.1-1.2
has caused the Debian Bug report #875492,
regarding [exfalso] Package lacks dependencies
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.)
--
875492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exfalso
Version: 3.9.1-1
Severity: grave
--- Please enter the report below this line. ---
Hi,
since the upgrade to version 3.9.1-1, exfalso does not start anymore on
my machine. I get the following error:
(0)fuddl@flutschi:~$ exfalso
Traceback (most recent call last):
File "/usr/bin/exfalso", line 15, in
sys.exit(main())
File "/usr/lib/python2.7/dist-packages/quodlibet/exfalso.py", line
27, in main
quodlibet.init(config_file=config_file)
File "/usr/lib/python2.7/dist-packages/quodlibet/_init.py", line 56,
in init
_init_gtk()
File "/usr/lib/python2.7/dist-packages/quodlibet/_init.py", line 274,
in _init_gtk
from quodlibet.qltk import ThemeOverrider, gtk_version
File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/__init__.py",
line 540, in
from .msg import Message, ErrorMessage, WarningMessage
File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/msg.py", line
15, in
from quodlibet.qltk.window import Dialog
File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/window.py",
line 16, in
from quodlibet.qltk.x import Button
File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/x.py", line 20,
in
from quodlibet.util.thread import call_async, Cancellable
File "/usr/lib/python2.7/dist-packages/quodlibet/util/thread.py",
line 14, in
raise ImportError("python-futures is missing: %r" % e)
ImportError: python-futures is missing: ImportError('No module named
concurrent.futures',)
So I apt install python-concurrent.futures. After that, I see the
following error:
(0)fuddl@flutschi:~$ exfalso
E: 0.176: errorreport.main.errorhook: update.py:20::
ImportError: No module named feedparser
So I apt install python-feedparser and it runs fine. Please fix the
missing dependencies.
Cheers - Fuddl
--- System information. ---
Architecture:
Kernel: Linux 4.12.0-1-amd64
Debian Release: buster/sid
500 unstableftp.uni-erlangen.de
1 experimentalftp.uni-erlangen.de
--- Package information. ---
Depends (Version) | Installed
===-+-
gir1.2-gtk-3.0 | 3.22.20-1
gir1.2-soup-2.4 (>= 2.44) | 2.59.90.1-1
python (>= 2.7.3-4+deb7u1) | 2.7.13-2
python-faulthandler | 2.4-1
python-gi | 3.24.1-3
python-gi-cairo | 3.24.1-3
python-mutagen(>= 1.32) | 1.38-1
python:any (<< 2.8) |
python:any(>= 2.7.5-5~) |
libjs-sphinxdoc(>= 1.0) | 1.5.6-2
sphinx-rtd-theme-common | 0.2.4-1
Recommends (Version) | Installed
-+-===
python-musicbrainzngs (>= 0.5) | 0.6-2
Suggests (Version) | Installed
===-+-===
brasero | 3.12.2-1
OR k3b |
OR xfburn |
gir1.2-gstreamer-1.0| 1.12.2-1
libmodplug1 | 1:0.8.9.0-1
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: quodlibet
Source-Version: 3.9.1-1.2
We believe that the bug you reported is fixed in the latest version of
quodlibet, 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 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings (supplier of updated quodlibet 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, 20 Oct 2017 03:0
Bug#879175: androidsdk-tools: Duplicate of android-platform-tools-swt
Source: androidsdk-tools Version: 22.2+git20130830~92d25d6-4 Severity: serious It looks like source:androidsdk-tools has been replaced by source:android-platform-tools-swt. Although a bit confusing, it looks like the newer android-platform-tools-swt corresponds with version 25. Can we go ahead and remove androidsdk-tools? On the other hand, the newer android-platform-tools-swt hasn't been buildable since January. But the tools are deprecated and apparently removed in newer Android SDK versions anyway. Thanks, Jeremy Bicha
Processed: Re: libswt-webkit-gtk-3-jni: Missing dependency on libwebkitgtk-1.0-0
Processing commands for cont...@bugs.debian.org: > retitle 879170 libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep Bug #879170 [src:swt-gtk] libswt-webkit-gtk-3-jni: Missing dependency on Changed Bug title to 'libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep' from 'libswt-webkit-gtk-3-jni: Missing dependency on'. > End of message, stopping processing here. Please contact me if you need assistance. -- 879170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877683: [Pkg-dns-devel] Bug#877683: jessie version of dns-root-data lacks new ksk in root.ds
On Thu 2017-10-19 18:12:38 -0400, Daniel Kahn Gillmor wrote: > after a bit of investigation, it looks like we're also missing a few > other commits, which i'll try to cherry-pick and build later tonight. I've just pushed a series of cherry-picks to master-jessie at https://anonscm.debian.org/git/pkg-dns/dns-root-data.git (commit ID ce9844f1ee8547ee816e95d4e5f990940689e8f7), which i think is now ready to go. The package builds properly from there for me on a jessie system and produces the expected two lines in root.ds. I've gone ahead and opened a ticket (https://bugs.debian.org/879161) with the release team about getting a new release into jessie. --dkg signature.asc Description: PGP signature
Processed: Re: Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated
Processing control commands: > clone -1 -2 Bug #871964 [src:swt-gtk] swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated Bug 871964 cloned as bug 879170 > retitle -2 libswt-webkit-gtk-3-jni: Missing dependency on Bug #879170 [src:swt-gtk] swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated Changed Bug title to 'libswt-webkit-gtk-3-jni: Missing dependency on' from 'swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated'. -- 871964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871964 879170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#871964: swt-gtk: Build-depends on libwebkitgtk-dev which is deprecated
Control: clone -1 -2 Control: retitle -2 libswt-webkit-gtk-3-jni: Missing dependency on libwebkitgtk-1.0-0 Control: reassign -2 libswt-webkit-gtk-3-jni Control: tags -2 +stretch On Tue, Oct 17, 2017 at 5:12 PM, Adrian Bunk wrote: > On Sat, Aug 12, 2017 at 11:43:58PM -0400, Jeremy Bicha wrote: >>... >> The package does build successfully without the libwebkitgtk-dev >> build-dependency. > > But the resulting library will still dynamically load it. > >> It feels to me like the libswt-webkit-gtk-3-jni was already broken >> since it doesn't have a dependency on any webkitgtk library > > The missing dependency sounds like a bug. > >> (I think >> the correct one would be libwebkitgtk-3.0-0 but that is still part of >> the deprecated libraries which are being removed.) > > It does use libwebkitgtk-1.0-0: > https://sources.debian.net/src/swt-gtk/3.8.2-4/webkitgtk.h/ > > I just tried, and it does work when libwebkitgtk-1.0-0 is installed > (and fails without). Ok, I am filing a new bug because the missing dependency should be fixed in stretch. This link says that Eclipse / swt-gtk 4.4 (released in 2014) has initial support for gtk3 and webkit2gtk: https://www.eclipse.org/swt/R4_4/new_and_noteworthy.html Unfortunately, eclipse and swt-gtk are very outdated in Debian: https://bugs.debian.org/681726 $ reverse-depends -r sid libswt-webkit-gtk-3-jni === * eclipse-rcp —so outdated it really needs to be removed from Buster before release if it's not upgraded regardless of this bug * tuxguitar * vuze — already removed from testing, see https://bugs.debian.org/870987 * zekr — already removed from testing, see https://bugs.debian.org/866659 Thank you, Jeremy Bicha
Bug#879123: glee: source for configure is missing
Ximin Luo: > On Thu, 19 Oct 2017 22:52:41 +0200 Markus Koschany wrote: >> [..] The configure file is human readable and the preferred >> source of modification in this case. Please also note that the author of >> glee licensed his work under the more liberal BSD-2-clause license. You >> cannot compare two very distinct issues like minified JS files and >> automake files and claim consensus has been reached already. >> > > With respect, can you point to any concrete evidence of this configure file > being "the preferred source of modification"? It is definitely *not* the case > for *most* configure files of this type, so you need to supply some evidence > if you're going to argue yours is special. > Unfortunately we have a bigger problem: - rwxrwxr-x 1,105,245 GLee.c - rwxrwxr-x 955,258 GLee.h * [This file was automatically generated by GLeeGen 7.0 These files are clearly not source code. But luckily it should be possible to regenerate them from the git repo I mentioned: > [..] https://github.com/kallisti5/glee > X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: block 877683 with 879161
Processing commands for cont...@bugs.debian.org: > block 877683 with 879161 Bug #877683 [dns-root-data] jessie version of dns-root-data lacks new ksk in root.ds 877683 was not blocked by any bugs. 877683 was not blocking any bugs. Added blocking bug(s) of 877683: 879161 > thanks Stopping processing here. Please contact me if you need assistance. -- 877683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877683: [Pkg-dns-devel] Bug#877683: jessie version of dns-root-data lacks new ksk in root.ds
On Thu 2017-10-19 23:23:08 +0200, Sergio Gelato wrote: > * Daniel Kahn Gillmor [2017-10-19 15:44:40 -0400]: >> However, i'm not convinced that dnssec-dsfromkey is at fault, because i >> think the versions of dnssec-dsfromkey in stretch and buster both have >> the same behavior. > > It turns out the following change from version 2017020200 of the package > was not included in the jessie backport: > > * Rewrite DS creation check to xml2 and ldnsutils, as neither xmllint > nor bind9utils handle multiple DNSKEY in one file correctly Thanks for the pointer. This isn't the only problem, though, as the build verification still isn't working out quite right. after a bit of investigation, it looks like we're also missing a few other commits, which i'll try to cherry-pick and build later tonight. --dkg signature.asc Description: PGP signature
Bug#879123: glee: source for configure is missing
On Thu, 19 Oct 2017 22:52:41 +0200 Markus Koschany wrote: > [..] The configure file is human readable and the preferred > source of modification in this case. Please also note that the author of > glee licensed his work under the more liberal BSD-2-clause license. You > cannot compare two very distinct issues like minified JS files and > automake files and claim consensus has been reached already. > With respect, can you point to any concrete evidence of this configure file being "the preferred source of modification"? It is definitely *not* the case for *most* configure files of this type, so you need to supply some evidence if you're going to argue yours is special. Actually, screw it, no need to bother, upstream moved to CMake: https://github.com/kallisti5/glee If you look through the log you'll notice upstream added the configure file in the very first commit, as GLeeScripts/linux/linuxfiles/configure Then the next edit to it was commit 65df404ebdb253e0aa7429405196df4104dda9b6 which deleted the file as being "unused". So it looks like we'll never get the source code to the file (unless the author is still contactable and has it saved privately somewhere.) Anyway just update to the latest version (from 2011, lol) and use CMake. To re-iterate my first point though, if in the future this issue crops up again, you need to supply evidence that ./configure is "preferred source of modification" because that contradicts all other experience of autotools files. A git history log of the author hand-editing the file *more times* than regenerating the file from configure.ac would suffice. Also licenses are not relevant to *whether a file is actually source code or not*. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
Processed: fixed in Alioth
Processing control commands: > tags -1 patch fixed-upstream pending Bug #878596 [python-theano] theano: FTBFS on big-endian systems - test_pooling_with_tensor_vars fails Added tag(s) patch, fixed-upstream, and pending. -- 878596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878596: fixed in Alioth
Control: tags -1 patch fixed-upstream pending Ready for upload (the GPU tests again haven't been run, but this shouldn't touch those parts).
Bug#877683: [Pkg-dns-devel] Bug#877683: jessie version of dns-root-data lacks new ksk in root.ds
* Daniel Kahn Gillmor [2017-10-19 15:44:40 -0400]: > However, i'm not convinced that dnssec-dsfromkey is at fault, because i > think the versions of dnssec-dsfromkey in stretch and buster both have > the same behavior. It turns out the following change from version 2017020200 of the package was not included in the jessie backport: * Rewrite DS creation check to xml2 and ldnsutils, as neither xmllint nor bind9utils handle multiple DNSKEY in one file correctly
Processed: easytag corrupts ogg files and causes data loss
Processing control commands: > severity -1 grave Bug #855251 [easytag] easytag corrupt ogg files Bug #878009 [easytag] easytag fails to add tags to .ogg files Severity set to 'grave' from 'normal' Severity set to 'grave' from 'normal' -- 855251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855251 878009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879123: glee: source for configure is missing
Am 19.10.2017 um 22:34 schrieb Adrian Bunk:
> On Thu, Oct 19, 2017 at 08:23:24PM +0200, Markus Koschany wrote:
>> ...
>> In my opinion the configure script of glee is DFSG-compliant and
>> suitable for main. The license states:
>>
>> # Copyright (C) 2003 Free Software Foundation, Inc.
>> # This configure script is free software; the Free Software Foundation
>> # gives unlimited permission to copy, distribute and modify it.
>
> According to debian/copyright the FSF is not a copyright holder of glee,
> and the licence is likely not what you quote.
>
> Whoever wrote the configure.{ac,in} would actually be relevant here.
I am quoting:
https://sources.debian.net/src/glee/5.4.0-2/configure/
The license is very liberal. You can argue that it should be mentioned
in debian/copyright but that does not make the file non-free or
unsuitable for Debian main.
>
>> It is correct that configure scripts are usually auto-generated but we
>> have never treated the absence of those files as RC issues. In
>> consequence this means that all automake packages which cannot use
>> dh-autoreconf are unsuitable for main.
>
> You are mixing two related but separate issues.
>
> Problems when using dh-autoreconf are a grey area, but these are being
> sorted out with autoreconf usually being used now (in earlier times
> autoreconf was nearly never done in Debian).
>
> No configure.{ac,in} at all is a pretty clear situation,
> and also very rare.
Nope, you are mixing two unrelated issues. dh-autoreconf is the default
with compat level 10 now. That does not mean at all, it would render
packages without dh-autoreconf or with earlier compat levels non
DFSG-compliant.
>
>> Thus I believe the resolution of
>> this bug report would be of general importance to the Debian project and
>> should be discussed on debian-devel at least.
>
> The topic has already been discussed there countless times,
> most recently for things like minified JavaScript.
This is not true. The configure file is human readable and the preferred
source of modification in this case. Please also note that the author of
glee licensed his work under the more liberal BSD-2-clause license. You
cannot compare two very distinct issues like minified JS files and
automake files and claim consensus has been reached already.
>
>> However I am in favor of closing this bug report as "not-a-bug".
>
> In NEW this bug alone would be sufficient for a direct reject[1]:
>
> Source missing
> Your package contains files that need source but do not have it. These
> include PDF and PS files in the documentation, or auto-generated files.
>
> Source package missing source
> Source packages are part of the distribution. As such source must be
> present for all files in the source package itself, ...
Again quoted out of context and not relevant in this case. The source is
the configure script. Period. Please feel free to discuss this on
debian-devel or move it to the CTTE. I am willing to oppose this
nonsense and harmful misinterpretation of Debian's Policy whenever and
wherever I can.
Regards,
Markus
signature.asc
Description: OpenPGP digital signature
Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"
Guillem Jover wrote... > TBH, I was not aware that anyone was running Dpkg modules in taint > mode. Well, I do as well, in some private code. I can and probably will change that, though. > If people are really running this code in taint mode, I'm willing to > discuss which parts of the API would make sense to cover or not, and > what tradeoffs related to performance to take, etc. Honestly, I cannot decide neither on this particular case nor in the general. On the one hand, given the fact a author of a code library never knows where and how people will actually use it, it's prudent to play safe and write all libraries so they run in taint mode as well. On the other hand, certainly a lot of existing Perl libraries do not follow that principle anyway and you might consider that approach, while desirable, not feasible. Also, there might be a readability tradeoff which I consider even worse than performance. (I could benchmark the cost of "use strict" and "use warnings" one day, I bet they're worse.) It's one of the many things where I consider Perl beyond repair. The language is fairly sloppy but today safeguards like taint mode should be turned on by default to mitigate at least the worst issues that exist. But nobody is willing to fix the massive breakage that would happen then, so it's not going to happen. ¢¢ Christoph signature.asc Description: Digital signature
Bug#877683: [Pkg-dns-devel] Bug#877683: jessie version of dns-root-data lacks new ksk in root.ds
On Wed 2017-10-04 14:45:30 +0200, Sergio Gelato wrote: > * Sergio Gelato [2017-10-04 11:26:02 +0200]: >> The corresponding package in stretch-updates looks OK. Could it be that the >> one in jessie-updates needs to be built with a newer version of bind9utils? > > Indeed it seems that jessie's (including jessie-updates') dnssec-dsfromkey > only processes the first key in the file. I can also confirm that the jessie package only has the first key. However, i'm not convinced that dnssec-dsfromkey is at fault, because i think the versions of dnssec-dsfromkey in stretch and buster both have the same behavior. So more digging needs to be done to figure out why this is happening on jessie. --dkg signature.asc Description: PGP signature
Bug#879123: glee: source for configure is missing
On Thu, Oct 19, 2017 at 08:23:24PM +0200, Markus Koschany wrote:
>...
> In my opinion the configure script of glee is DFSG-compliant and
> suitable for main. The license states:
>
> # Copyright (C) 2003 Free Software Foundation, Inc.
> # This configure script is free software; the Free Software Foundation
> # gives unlimited permission to copy, distribute and modify it.
According to debian/copyright the FSF is not a copyright holder of glee,
and the licence is likely not what you quote.
Whoever wrote the configure.{ac,in} would actually be relevant here.
> It is correct that configure scripts are usually auto-generated but we
> have never treated the absence of those files as RC issues. In
> consequence this means that all automake packages which cannot use
> dh-autoreconf are unsuitable for main.
You are mixing two related but separate issues.
Problems when using dh-autoreconf are a grey area, but these are being
sorted out with autoreconf usually being used now (in earlier times
autoreconf was nearly never done in Debian).
No configure.{ac,in} at all is a pretty clear situation,
and also very rare.
> Thus I believe the resolution of
> this bug report would be of general importance to the Debian project and
> should be discussed on debian-devel at least.
The topic has already been discussed there countless times,
most recently for things like minified JavaScript.
> However I am in favor of closing this bug report as "not-a-bug".
In NEW this bug alone would be sufficient for a direct reject[1]:
Source missing
Your package contains files that need source but do not have it. These
include PDF and PS files in the documentation, or auto-generated files.
Source package missing source
Source packages are part of the distribution. As such source must be
present for all files in the source package itself, ...
> Regards,
>
> Markus
cu
Adrian
[1] https://ftp-master.debian.org/REJECT-FAQ.html
--
"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
Processed: fixed-upstream, not patch
Processing commands for cont...@bugs.debian.org: > tags 871587 - patch Bug #871587 [src:maildrop] maildrop FTBFS with libcourier-unicode-dev 2.0-1 Bug #879131 [src:maildrop] Looks like transition didn't go according to plan Removed tag(s) patch. Removed tag(s) patch. > tags 871587 fixed-upstream Bug #871587 [src:maildrop] maildrop FTBFS with libcourier-unicode-dev 2.0-1 Bug #879131 [src:maildrop] Looks like transition didn't go according to plan Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 871587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871587 879131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"
-=| Damyan Ivanov, 18.10.2017 20:20:16 + |=-
> During discussion, Matt S. Trout suggested on IRC that the check for
> a valid package name is better written as $input =~
> /\A([A-Za-z]\w*(?:::\w+)*)\Z/. If no hierarchy is possible, then
> /\A([A-Za-z]\w*/ would be enough.
I forgot an additional suggestion from Matt for replacing a big string
eval with a much smaller one.
Here it is:
## old code
eval qq{
pop \@INC if \$INC[-1] eq '.';
require Dpkg::Vendor::$name;
\$obj = Dpkg::Vendor::$name->new();
};
unless ($@) {
$OBJECT_CACHE{$vendor} = $obj;
return $obj;
}
## new code
pop @INC if $INC[-1] eq '.';
(my $path = my $class = "Dpkg::Vendor::${name}") =~ s/\::/\//g
my $obj = eval { require "${path}.pm"; $class->new };
return $OBJECT_CACHE{$vendor} = $obj if $obj;
Cheers,
dam
Bug#879131: Looks like transition didn't go according to plan
Control: reassign -1 src:maildrop Control: forcemerge 871587 -1 On Thu, Oct 19, 2017 at 03:23:19PM -0400, Anthony DeRobertis wrote: > Source: courier-unicode > Severity: serious > > TLDR: Don't Breaks/Replaces libcourier-unicode1, it prevents install of > at least maildrop (or upgrade). >... What breaks the install of maildrop is that the binNMU failed. This is due to #871587. 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
Processed: Re: Bug#879131: Looks like transition didn't go according to plan
Processing control commands: > reassign -1 src:maildrop Bug #879131 [src:courier-unicode] Looks like transition didn't go according to plan Bug reassigned from package 'src:courier-unicode' to 'src:maildrop'. Ignoring request to alter found versions of bug #879131 to the same values previously set Ignoring request to alter fixed versions of bug #879131 to the same values previously set > forcemerge 871587 -1 Bug #871587 [src:maildrop] maildrop FTBFS with libcourier-unicode-dev 2.0-1 Bug #879131 [src:maildrop] Looks like transition didn't go according to plan Marked as found in versions maildrop/2.8.4-2. Added tag(s) sid, patch, and buster. Merged 871587 879131 -- 871587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871587 879131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879131: Looks like transition didn't go according to plan
Source: courier-unicode Severity: serious TLDR: Don't Breaks/Replaces libcourier-unicode1, it prevents install of at least maildrop (or upgrade). libcourier-unicode4 breaks libcourier-unicode1 << 1.4-4. The archive currently has -3+b1, so they're not co-installable. This makes it impossible to (for example) install both Courier and maildrop. It looks like you planned to have 1.4-5 enter the archive — which would be co-installable. At least the package tracker says you uploaded that on Aug 7. I'm guessing it was ignored because you also uploaded 2.0-1 the same day (again according to the package tracker). I found a copy using snapshot.d.o, but it appears you changed the package name to libcourier-unicode3 to match the soversion. Normally desired, but that also means it won't satisfy the dependency from maildrop on -unicode1. There appears to be no reason for libcourier-unicode4 to Breaks/Replaces libcourier-unicode1. They have different soversions and no conflicting files. Dropping that Breaks/Replaces would fix the (presumably) unwanted conflict with maildrop. I think it's just maildrop broken by this. So probably not worth the effort to get 1.4-5 actually in to the archive (which would, I think, require uploading it built from a new source package). 1.4 will be dropped when maildrop's maintainers update their package. But even so, it'd be nice to drop the Breaks/Replaces unless there is actually a good reason to have it. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#879045: marked as done (xracer: hangs when program exit)
Your message dated Thu, 19 Oct 2017 19:34:15 + with message-id and subject line Bug#879045: fixed in xracer 0.96.9.1-9 has caused the Debian Bug report #879045, regarding xracer: hangs when program exit 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.) -- 879045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xracer Version: 0.96.9.1-8+b1 Severity: grave Justification: renders package unusable Dear Maintainer, after completing the three laps of the inbuilt track, the game stops with error: xracer:player.c:201: fatal error: function not implemented Received user signal. Received child termination signal. At this point it just hangs and never exits. Unfortunately it also doesn't release the mouse. To exit, you have to switch to a virtual terminal and kill it. This hang might pose a big problem for unexperienced users. Best Regards, Andrej Mernik -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=sl_SI.UTF-8, LC_CTYPE=sl_SI.UTF-8 (charmap=UTF-8), LANGUAGE=sl (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xracer depends on: ii freeglut3 2.8.1-3 ii libc6 2.24-11+deb9u1 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libice6 2:1.0.9-2 ii libjpeg62-turbo 1:1.5.1-2 ii libsm62:1.2.2-1+b3 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxi62:1.7.9-1 ii libxmu6 2:1.1.2-2 ii netpbm2:10.0-15.3+b2 xracer recommends no packages. Versions of packages xracer suggests: pn xracer-tools -- no debconf information --- End Message --- --- Begin Message --- Source: xracer Source-Version: 0.96.9.1-9 We believe that the bug you reported is fixed in the latest version of xracer, 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 879...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated xracer 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, 20 Oct 2017 01:55:34 +0800 Source: xracer Binary: xracer xracer-tools Architecture: source amd64 all Version: 0.96.9.1-9 Distribution: unstable Urgency: low Maintainer: Ying-Chun Liu (PaulLiu) Changed-By: Ying-Chun Liu (PaulLiu) Description: xracer - Futuristic racing game xracer-tools - Futuristic racing game - developer tools Closes: 879045 Changes: xracer (0.96.9.1-9) unstable; urgency=low . * Add debian/quilt_patches/0160_fix_hang.patch - Fix hang (Closes: #879045) * Update all -p0 patches to -p1 * Bump Standards-Version to 4.1.1: nothing needs to be changed. Checksums-Sha1: c8a80d3b339b66799c0615c5234112d93700f7f0 1980 xracer_0.96.9.1-9.dsc 300f151b6e746541c3cd5286280f66a4a798126b 28896 xracer_0.96.9.1-9.debian.tar.xz 551b7685bc47dace6d19a6fba34075bcec8a5f1e 318672 xracer-dbgsym_0.96.9.1-9_amd64.deb 4de92b54ce65f1c67439f0aada34b35ed4f7c030 53012 xracer-tools_0.96.9.1-9_all.deb 915b83e98b3c133e0d251c9384208c9f968b3f43 10234 xracer_0.96.9.1-9_amd64.buildinfo 7097690d646fff34527194ac7f2acb13e7699196 864492 xracer_0.96.9.1-9_amd64.deb Checksums-Sha256: ed94a416046a6abd2c33bb95676d625228435372fa09dcbbb9f84432fab2b62f 1980 xracer_0.96.9.1-9.dsc 35d5a1725cf7f011893be5f64ae07b06953339b3a834915f24315cfed27c7977 28896 xracer_0.96.9.1-9.debian.tar.xz 5d109d9aa7b7a472ced8216886c96da713dde6fe11dcb2756bb62caa309c0c6f 318672 xracer-dbgsym_0.96.9.1-9_amd64.deb 34b8e498d661e45610556ae5b8d6dbb95f1b18b96365b4d6d5824aa4fdb72a55 53012 xracer-tools_0.96.9.1-9_all.deb 8cd8d5b4b7739ee140c49e37945d4bf03a3232a5ec08b6d10388342951cda54d 10234 xracer_0.96.9.1-9_amd64.buildinfo aca9a1d79e9c9fec7e66b357628a8af23bdc72e26004dfa6c5e4786515832f3d 864492 xracer_0.96.9.1-9_amd64.deb Files:
Processed: forcibly merging 878834 878929
Processing commands for cont...@bugs.debian.org: > forcemerge 878834 878929 Bug #878834 [libfreetype6] freetype: Upgrade to 2.8.1 breaks font rendering in various applications Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering Bug #878929 [libfreetype6] libfreetype6: font rendering broken in electron applications Severity set to 'serious' from 'normal' Added indication that 878929 affects thunderbird Added tag(s) patch, fixed-upstream, and upstream. Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering Merged 878834 878870 878929 > thanks Stopping processing here. Please contact me if you need assistance. -- 878834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878834 878870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878870 878929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879127: lwresd is now a dangling symlink when bind9 isn't installed
Package: lwresd Version: 1:9.10.6+dfsg-2 Severity: serious bind9 (1:9.10.6+dfsg-2) unstable; urgency=medium ... * Replace lwresd with symlink instead of hard copy (Closes: #868538) Unfortunately this created an even bigger problem: lwresd is now a dangling symlink when bind9 isn't installed.
Bug#879045: xracer: hangs when program exit
retitle 879045 xracer: hangs when program exit
thanks
Hi,
I've fix the bug. Please see the attached patch.
The program hangs in the busy loop in xracer-0.96.9/src/sound.c:135
while (pid >= 0)
#ifdef HAVE_SCHED_YIELD
sched_yield ()
#endif
;
pid does changed to -1 by receiving a signal. But the optimizer
optimized that variable and makes the loop always true.
Thus the patch is to volatile the pid variable.
Please see testO3.c as an example in this mail. Compile it with -O0 and
-O3 will show the different behaviour. That is the reason of this bug.
Yours,
Paul
--
PaulLiu (劉穎駿)
E-mail: Ying-Chun Liu (PaulLiu)
Description: Fix hanging when program exits.
The program hangs at exit(). It is because the sound process doesn't
exit its busy loop. Basically it is because the variable which controls
the busy loop is optimized by the compiler. Thus we need to volatile that
variable.
Bug-Debian: http://bugs.debian.org/879045
Author: Ying-Chun Liu (PaulLiu)
Last-Update: 2017-10-19
Index: xracer-0.96.9.1/xracer-0.96.9/src/sound.c
===
--- xracer-0.96.9.1.orig/xracer-0.96.9/src/sound.c
+++ xracer-0.96.9.1/xracer-0.96.9/src/sound.c
@@ -72,7 +72,7 @@
/* If there is a sound process running, this contains the process
* ID, else it contains -1.
*/
-static int pid = -1;
+static volatile int pid = -1;
/* Address of shared memory. */
static struct xrSoundSharedMemory *shm = 0;
#include
#include
#include
static int flag = -1;
void loop() {
printf ("Loop started\n");
while (flag == -1) ;
printf ("Loop exited\n");
}
void handler(int x) {
printf ("Signal received\n");
flag = 0;
}
int main() {
printf ("Program PID = %d\n", getpid());
printf ("Please send a SIGUSR1 to stop this program.\n");
signal(SIGUSR1, handler);
loop();
return 0;
}
signature.asc
Description: OpenPGP digital signature
Processed: xracer: hangs when program exit
Processing commands for cont...@bugs.debian.org: > retitle 879045 xracer: hangs when program exit Bug #879045 [xracer] xracer: Fatal error: function not implemented Changed Bug title to 'xracer: hangs when program exit' from 'xracer: Fatal error: function not implemented'. > thanks Stopping processing here. Please contact me if you need assistance. -- 879045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879123: glee: source for configure is missing
Am 19.10.2017 um 19:58 schrieb Helmut Grohne: > Source: glee > Version: 5.4.0-2 > Severity: serious > Justification: missing source > > The configure file claims that it was generated using autoconf. Yet the > corresponding source configure.in or configure.ac is missing from the > source package. This makes the package unsuitable for main in principle. > > Fortunately, the packaging does not appear to be using configure. So > repacking the tarball and removing configure looks like a viable option. > > Helmut Wow. Seriously? I am adding the debian-devel-games mailing list to CC in case I have missed an important discussion and would like to ask other team members for more input. In my opinion the configure script of glee is DFSG-compliant and suitable for main. The license states: # Copyright (C) 2003 Free Software Foundation, Inc. # This configure script is free software; the Free Software Foundation # gives unlimited permission to copy, distribute and modify it. It is correct that configure scripts are usually auto-generated but we have never treated the absence of those files as RC issues. In consequence this means that all automake packages which cannot use dh-autoreconf are unsuitable for main. Thus I believe the resolution of this bug report would be of general importance to the Debian project and should be discussed on debian-devel at least. However I am in favor of closing this bug report as "not-a-bug". Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#866635: cyclograph: depends on libwebkitgtk-3.0-0 which is deprecated
On Sat, Jul 22, 2017 at 9:13 PM, Jeremy Bicha wrote: > On Sat, Jul 22, 2017 at 4:09 PM, Federico Brega wrote: >> Another solution could be a nmu since I've already pushed the >> packaging of the latest version of the packag on the pkg-runnign-devel >> git repository, but the debian maintainers in the group are probably >> busy to upload it. > > I am not a Debian Developer so I can't upload the version for you. But > could you ask Debian Mentors? I think there should be several sponsors > who would be interested in uploading a fix for an RC bug. I am now a Debian Developer so I can help sponsor this upload for you because I am eager to help resolve this issue and get webkit1 out of Debian. Thanks, Jeremy Bicha
Bug#879123: glee: source for configure is missing
Source: glee Version: 5.4.0-2 Severity: serious Justification: missing source The configure file claims that it was generated using autoconf. Yet the corresponding source configure.in or configure.ac is missing from the source package. This makes the package unsuitable for main in principle. Fortunately, the packaging does not appear to be using configure. So repacking the tarball and removing configure looks like a viable option. Helmut
Processed: [bts-link] source package src:psycopg2
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:psycopg2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #876931 (http://bugs.debian.org/876931) > # Bug title: psycopg2 FTBFS with Sphinx 1.6: Could not import extension > dbapi_extension > # * https://github.com/psycopg/psycopg2/pull/599 > # * remote status changed: open -> closed > # * closed upstream > tags 876931 + fixed-upstream Bug #876931 [src:psycopg2] psycopg2 FTBFS with Sphinx 1.6: Could not import extension dbapi_extension Added tag(s) fixed-upstream. > usertags 876931 - status-open Usertags were: status-open. Usertags are now: . > usertags 876931 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 876931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#876274: marked as done (wordpress: 9 security bugs in wordpress 4.8.1 and earlier)
Your message dated Thu, 19 Oct 2017 17:32:51 + with message-id and subject line Bug#876274: fixed in wordpress 4.7.5+dfsg-2+deb9u1 has caused the Debian Bug report #876274, regarding wordpress: 9 security bugs in wordpress 4.8.1 and earlier 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.) -- 876274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wordpress Version: 4.8.1+dfsg-1 Severity: grave Tags: security Justification: user security hole Wordpress 4.8.2 is out which fixes 9 security issues[1] $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi). WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. Reported by Slavco A cross-site scripting (XSS) vulnerability was discovered in the oEmbed discovery. Reported by xknown of the WordPress Security Team. A cross-site scripting (XSS) vulnerability was discovered in the visual editor. Reported by Rodolfo Assis (@brutelogic) of Sucuri Security. A path traversal vulnerability was discovered in the file unzipping code. Reported by Alex Chapman (noxrnet). A cross-site scripting (XSS) vulnerability was discovered in the plugin editor. Reported by 陈瑞琦 (Chen Ruiqi). An open redirect was discovered on the user and term edit screens. Reported by Yasin Soliman (ysx). A path traversal vulnerability was discovered in the customizer. Reported by Weston Ruter of the WordPress Security Team. A cross-site scripting (XSS) vulnerability was discovered in template names. Reported by Luka (sikic). A cross-site scripting (XSS) vulnerability was discovered in the link modal. Reported by Anas Roubi (qasuar). 1: https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: wordpress Source-Version: 4.7.5+dfsg-2+deb9u1 We believe that the bug you reported is fixed in the latest version of wordpress, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated wordpress 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: Sat, 07 Oct 2017 07:11:32 +1100 Source: wordpress Binary: wordpress wordpress-l10n wordpress-theme-twentysixteen wordpress-theme-twentyfifteen wordpress-theme-twentyseventeen Architecture: source all Version: 4.7.5+dfsg-2+deb9u1 Distribution: stretch-security Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Description: wordpress - weblog manager wordpress-l10n - weblog manager - language files wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files Closes: 876274 877629 Changes: wordpress (4.7.5+dfsg-2+deb9u1) stretch-security; urgency=medium . * Backport patches from 4.8.2 Closes: #876274 - CVE-2017-14723 $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi) Changeset 41472, 41498 - CVE-2017-14724 Cross-site scripting (XSS) vulnerability in the oEmbed discovery Changeset 41451 - CVE-2017-14726 Cross-site scripting (XSS) vulnerability in the visual editor Changeset 41436 - CVE-2017-14719 Path traversal vulnerability in the file unzipping code Changeset 41459 - CVE-2017-14721 Cross-site scripting (XSS) vulnerability in the plugin editor Changeset 41413
Bug#876315: marked as done (CVE-2017-14339)
Your message dated Thu, 19 Oct 2017 17:33:15 + with message-id and subject line Bug#876315: fixed in yadifa 2.2.3-1+deb9u1 has caused the Debian Bug report #876315, regarding CVE-2017-14339 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.) -- 876315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yadifa Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14339 Cheers, Moritz --- End Message --- --- Begin Message --- Source: yadifa Source-Version: 2.2.3-1+deb9u1 We believe that the bug you reported is fixed in the latest version of yadifa, 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 876...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Schade (supplier of updated yadifa 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, 18 Oct 2017 16:12:17 CEST Source: yadifa Binary: yadifa libyadifa-dev Architecture: source amd64 Version: 2.2.3-1+deb9u1 Distribution: stretch-security Urgency: medium Maintainer: Markus Schade Changed-By: Markus Schade Description: libyadifa-dev - development libraries and header files for YADIFA yadifa - Internet Domain Name Server Closes: 876315 Changes: yadifa (2.2.3-1+deb9u1) stretch-security; urgency=medium . * Fixes an issue where a maliciously crafted message may block the server. Closes: #876315, CVE-2017-14339 * Update build dependency for debhelper. Checksums-Sha256: cb95a0d59a84d2dd84362b59bbb9754dafddce4bae547f7146cd8047cc55811c 1880 yadifa_2.2.3-1+deb9u1.dsc bdf87b9120753416d164d92808f240d80ab1c88b001f6c159f42042bb0ccaab0 17556 yadifa_2.2.3-1+deb9u1.debian.tar.xz 7ffbe6cd51f9d11201997402f3814feef4cbbac71b400f4849b27dfc1e7a8983 563880 libyadifa-dev_2.2.3-1+deb9u1_amd64.deb dc5503d65b46edeeb0ebcdca5443f2b280fee4790037947e20c0bc17358d9502 2426180 yadifa-dbgsym_2.2.3-1+deb9u1_amd64.deb 42bc660c165369916e9f8b60adaaaf6e4f18c4b73c09bebdec437d258f08e010 5515 yadifa_2.2.3-1+deb9u1_amd64.buildinfo 1b2093f37dbdca60dc987828d36aa3d2bc6355be9e2fc1429286714d32c9f5b8 497880 yadifa_2.2.3-1+deb9u1_amd64.deb 4a7de1a1c17606c99e1f4ad2f9989268713283cd83eb6edfe0f283fe00a96e46 3672934 yadifa_2.2.3.orig.tar.gz Checksums-Sha1: 0166bcac6ff3d63a56896652bf42fae41144150b 1880 yadifa_2.2.3-1+deb9u1.dsc e9d8ff6a19cea90a0f98d8aee90b8d17f5dc9108 17556 yadifa_2.2.3-1+deb9u1.debian.tar.xz 4469f49d042fe7ebbea67a4d07fd1adefe4fef4a 563880 libyadifa-dev_2.2.3-1+deb9u1_amd64.deb 85cd3c466c2fb6f937ca3d456994a1e2fb2a4780 2426180 yadifa-dbgsym_2.2.3-1+deb9u1_amd64.deb b38e1c45e41a1ae0a400df7e5d804185c72d8287 5515 yadifa_2.2.3-1+deb9u1_amd64.buildinfo 76c5f7f276354a01ba22a545a7127947976e9300 497880 yadifa_2.2.3-1+deb9u1_amd64.deb 0c36c8aad0b06236f04d7eb3e26865922323677a 3672934 yadifa_2.2.3.orig.tar.gz Files: b6f68db59bdf62ae009113d112f5bb5b 1880 net optional yadifa_2.2.3-1+deb9u1.dsc 5d63b2d2c941e761e5d90b00691e3ec1 17556 net optional yadifa_2.2.3-1+deb9u1.debian.tar.xz 6ffdac4f10de20dc0604a2db7039951a 563880 libdevel optional libyadifa-dev_2.2.3-1+deb9u1_amd64.deb 712c8d7c964517b54deb8e9772a80ab7 2426180 debug extra yadifa-dbgsym_2.2.3-1+deb9u1_amd64.deb 6cea9415a5b4e2846829eb52205c7f0d 5515 net optional yadifa_2.2.3-1+deb9u1_amd64.buildinfo f90408859fde446c8a153ba374ecb565 497880 net optional yadifa_2.2.3-1+deb9u1_amd64.deb 5684ee4e7cdddbd241f2918fd35c4ed3 3672934 net optional yadifa_2.2.3.orig.tar.gz -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJZ52FGAAoJEPNPCXROn13ZqqYQAIne+77l49WJ+uWE0YT/ZZ0p +z3FWdCdDYyk4VphmT+Oz1442qUC56oUJs+2gr+R4H77EDD+5cPMOasfFBkcafPI 3V+lRsqVDuyJuT4TnvxdqDLdjYeeiM1NmGrhifQkfmoxo3haGDjzBenMj7PBGMaY D7kUd3TYsPEj8egMPTyqGz0Q1rbj2yWU79//7puSHd30YiYCqk0eFWBmdCfx8HZt temsAzjV9USe/k4A6/XGk8JKk3r/jOxn39OuYfVL6Slku3R8wYRyRAf1xQVyYR2l Jq9x5HX/1cBNxvLrJAfvQXLx22welhVPvdxrBLR6LUHznoG2gqExLJT2bxXeNxKq ZpqknzN1oVOSnvaGxEZ3YGDu7Jmg8XbGpY/YVHteJXlPLH3t7QJ/SQq2B4ibmJtb EFUZ961fZF/QGuqZXXVRGI2I6a6eBrsa6WevrtgDV6Fih9zxY1eRzE9RRfiVJvcr 4hPQXtAZgJpAf5PKo/kHKwIOtD9n86+nu85Tpn+U2fez6iPg41RMce2o1PRCKxzo 6PP
Bug#878402: [debian-mysql] Bug#878402: Bug#878402: Security fixes from the October 2017 CPU
Hi Lars, On Thu, Oct 19, 2017 at 10:23:15AM +0200, Lars Tangvald wrote: > > > On 10/19/2017 10:09 AM, Emilio Pozuelo Monfort wrote: > > On 18/10/17 20:46, Salvatore Bonaccorso wrote: > > > Hi lars, > > > > > > On Wed, Oct 18, 2017 at 03:51:26PM +0200, Lars Tangvald wrote: > > > > Hi, > > > > > > > > 5.5.58 packages for Debian 7 and 8 are built, and pass the test suite. > > > > Attached are debdiff files for Wheezy and Jessie (source is also pushed > > > > to > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__anonscm.debian.org_cgit_pkg-2Dmysql_mysql-2D5.5.git&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=HPjEzLhETPj8fl9HCxxISaaV3f5tXDpGXDR3R2IELxg&m=00T7TUZCwXkig-wYCf-35nC5VNSQmjNOsNq0TOBoXBs&s=MPjTux6yCV6-5Si_VECXoTwgZxgsyNIHfNSpH1nq2ws&e= > > > > ) > > > > As before, we unfortunately don't have a DD in our team that can > > > > sponsor the > > > > upload, so we need assistance with that. > > > I will look into it for jessie-security then. > > > > > > > I'm not sure if the security team still handles Debian8, or if the lts > > > > team > > > > does now? > > > Yes, Debian 8 Jessie is still yet handled by the security team. > > And I will take of Debian 7 (wheezy). Thanks for preparing the update! > > > > Cheers, > > Emilio > Thanks for the help to both of you! :) FTR, I just released DSA-4002-1 for mysql-5.5 in jessie-security. Thanks for preparing the import. Regards, Salvatore
Bug#877683: [Pkg-dns-devel] Bug#877683: jessie version of dns-root-data lacks new ksk in root.ds
Sergio Gelato wrote: > Package: dns-root-data > Version: 2017072601~deb8u1 > Severity: serious > > The version of this package that is currently in jessie-updates still only > lists the old key 19036 in /usr/share/dns/root.ds. Confirmed, I see the two keys in /usr/share/dns/root.key but not in root.ds. > If I understood correctly, > starting a week from now the root zone will only be signed with the new key > 20326. The root KSK rollover was postponed: https://www.icann.org/news/announcement-2017-09-27-en The root zone is currently being signed with the same KSK it always has been signed with. The roll might be re-scheduled and performed in the first quarter of 2018, but there is currently no definite date for the rollover. -- Robert Edmonds edmo...@debian.org
Processed: Re: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallbac
Processing commands for cont...@bugs.debian.org: > fixed 877962 0.10.0-1 Bug #877962 [prosody] prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua Marked as fixed in versions prosody/0.10.0-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 877962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877962: marked as done (prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua)
Your message dated Thu, 19 Oct 2017 17:47:47 +0200 with message-id and subject line Re: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallbac has caused the Debian Bug report #877962, regarding prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua 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.) -- 877962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: prosody Version: 0.10~hg745e0a783055-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../prosody_0.10~hg745e0a783055-3_amd64.deb ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of stop. Unpacking prosody (0.10~hg745e0a783055-3) over (0.9.12-2) ... dpkg: error processing archive /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is also in package prosody-modules 0.0~hg20170929.c53cc1ae4788+dfsg-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of start. Errors were encountered while processing: /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb cheers, Andreas prosody-modules=0.0~hg20170929.c53cc1ae4788+dfsg-1_prosody=0.10~hg745e0a783055-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- fixed 877962 0.10.0-1--- End Message ---
Bug#879088: marked as done (Please make libbabeltrace-ctf{1,-dev} provides versioned)
Your message dated Thu, 19 Oct 2017 15:33:55 +
with message-id
and subject line Bug#879088: fixed in babeltrace 1.5.3-3
has caused the Debian Bug report #879088,
regarding Please make libbabeltrace-ctf{1,-dev} provides versioned
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.)
--
879088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: babeltrace
Version: 1.5.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-ker...@lists.debian.org
libbabeltrace1 (= 1.5.3-2) merges the contents of libbabletrace-ctf1 into
the libbabeltrace1 package. This makes packages like gdb uninstallable.
Similarly, libbabeltrace-dev having absorbed libbabeltrace-ctf-dev makes
the linux source package (the Linux kernel), and probably other important
packages like gdb, unbuildable.
Making the Linux kernel unbuildable is particularly undesirable, because
it has frequent security updates.
Please do one of these as soon as possible:
* revert this change; or
* introduce a transitional (empty) libbabeltrace-ctf1 in section oldlibs with
Depends: libbabeltrace1 (= ${binary:Version}) and a transitional
libbabeltrace-ctf-dev with Depends: libbabeltrace-dev (= ${binary:Version}),
then report bugs in anything that build-depends on libbabeltrace-ctf-dev
asking them to migrate to build-depending on libbabeltrace-dev.
The transitional packages can be removed when nothing (Build-)Depends
on them, but not before.
As https://tracker.debian.org/pkg/babeltrace says, babeltrace is currently
involved in a planned transition (to a new Python version), so this was
not a great time to be making disruptive changes to it. Please be careful
with this sort of packaging change.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: babeltrace
Source-Version: 1.5.3-3
We believe that the bug you reported is fixed in the latest version of
babeltrace, 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 879...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Jeanson (supplier of updated babeltrace 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, 19 Oct 2017 10:45:25 -0400
Source: babeltrace
Binary: babeltrace libbabeltrace1 libbabeltrace-dev python3-babeltrace
Architecture: source
Version: 1.5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Jon Bernard
Changed-By: Michael Jeanson
Description:
babeltrace - Trace conversion program
libbabeltrace-dev - Babeltrace development files
libbabeltrace1 - Babeltrace conversion libraries
python3-babeltrace - Babeltrace Python 3 bindings
Closes: 879088
Changes:
babeltrace (1.5.3-3) unstable; urgency=medium
.
* [c0ecf19] Add versioned provides for ctf (Closes: #879088)
Checksums-Sha1:
43ca4c6bbaa6303a0ef08155abb43abe20f16ccb 2304 babeltrace_1.5.3-3.dsc
4c886908f5998483f91991d929be34d0fdec8e1c 10748 babeltrace_1.5.3-3.debian.tar.xz
a1047a58fd1eaee400656afcb86a495f6c425a39 6945
babeltrace_1.5.3-3_source.buildinfo
Checksums-Sha256:
2e81af4125d418ed679a2ece23e0c83e1b0c674ef3d4f3c07f3ab219df910a5e 2304
babeltrace_1.5.3-3.dsc
60bc797636df75fe8eb26506c65eef5ccd67d03aab27ebef8450c51ea34b6881 10748
babeltrace_1.5.3-3.debian.tar.xz
b1dfbf2903ec42c13e172ee63cc57ce88ca918d5098f62351eb3d49a7c9b 6945
babeltrace_1.5.3-3_source.buildinfo
Files:
a622b5c8a8e9279bd977e3d866e5a436 2304 libs optional babeltrace_1.5.3-3.dsc
222651c07666212bf129f2c41a8bb3c5 10748 libs optional
babeltrace_1.5.3-3.debian.tar.xz
9cefc5a3134c0a2ee006c0efd109805e 6945 libs optional
babeltrace_1.5.3-3_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEmGYkMkK2Qid54gtihlYfRSGA/P4FAlnovYEUHG1qZWFuc29u
QHVidW50dS5jb20ACgkQhlYfRSGA/P7hMg/+OjQZ3BkNANjOljD6r+HWeFtElBIz
zk9M25DzZ5qG/TNxoboNR1K3UV03qPBEt4FH1KyfnzhEm/P66ptMHAxq+AqzNDa4
mu6W1+suJ9vtVYx4mZLgbR5ytYCaDT67Hr94ejXMBe+MP5B6juEtI7UkGCD9snbw
Cy0MnzjCVH/YKI7ha574aJtdo/JkbLd0aZeTdsLbtHH0vxXdrcRhcEQhysrJxGC4
GCf9w09S+aLjMe+dvvfvt+IrCwcNw+fE/LByAv9bwsuO7c6UDvVtbRD3MzccU2+Q
O3Y7dzO3ASg5u1NM0CSQVsN7y9gFwxtefsTvqSaCw0r/U8Pk9T73M8J6P93NMd4s
Bug#879045: xracer: Fatal error: function not implemented
On 2017年10月19日 01:48, Andrej Mernik wrote: > Package: xracer > Version: 0.96.9.1-8+b1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > after completing the three laps of the inbuilt track, the game stops with > error: > > xracer:player.c:201: fatal error: function not implemented > Received user signal. > Received child termination signal. > > At this point it just hangs and never exits. Unfortunately it also doesn't > release the mouse. To exit, you have to switch to a virtual terminal and kill > it. > > This hang might pose a big problem for unexperienced users. > > Best Regards, > Andrej Mernik > Hi Andrej, Thanks for reporting this bug. I can reproduce it. And it is a quite funny bug. The problem is actually the C optimizer is more powerful nowadays. So this bug is because a static variable modified by 2 threads. One thread is using busy wait on that variable. And makes the optimizer thinks that wait loop to be always true. The fix is to mark that static variable volatile to not let the optimizer optimize it. I'll fix this bug soon. Many Thanks, Paul -- PaulLiu (劉穎駿) E-mail: Ying-Chun Liu (PaulLiu) signature.asc Description: OpenPGP digital signature
Bug#872847: marked as done (fritzing: fails to bulid against libgit2 0.26.0)
Your message dated Thu, 19 Oct 2017 15:05:36 + with message-id and subject line Bug#872847: fixed in fritzing 0.9.3b+dfsg-4.1 has caused the Debian Bug report #872847, regarding fritzing: fails to bulid against libgit2 0.26.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.) -- 872847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fritzing Version: 0.9.3b+dfsg-4 Severity: normal Dear Maintainer, A new version of libgit2 0.26.0 has been added to Experimental. It appears that the version of fritzing in unstable won't build against this version [1]. >From what I can see Debian has the latests version of Fritzing. So if this problem is due to upsteam not supporting 0.26.0 can you please follow up with them to get the version of libgit2 required updated to the latest version. Thanks, Russell 1. https://people.debian.org/~infinity0/libgit2/fritzing_0.9.3b+dfsg-4_amd64-2017-08-01T11:37:39Z.build.xz -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fritzing depends on: ii fritzing-data 0.9.3b+dfsg-4 ii libc6 2.24-11 ii libgcc1 1:6.3.0-18 ii libgit2-240.25.1+really0.24.6-1 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libqt5concurrent5 5.7.1+dfsg-3+b1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5network55.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5serialport5 5.7.1~20161021-2 ii libqt5sql55.7.1+dfsg-3+b1 ii libqt5sql5-sqlite 5.7.1+dfsg-3+b1 ii libqt5svg55.7.1~20161021-2+b2 ii libqt5widgets55.7.1+dfsg-3+b1 ii libqt5xml55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii zlib1g1:1.2.8.dfsg-5 fritzing recommends no packages. Versions of packages fritzing suggests: ii fritzing-parts 0.9.3b-1 -- no debconf information --- End Message --- --- Begin Message --- Source: fritzing Source-Version: 0.9.3b+dfsg-4.1 We believe that the bug you reported is fixed in the latest version of fritzing, 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 872...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated fritzing 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, 19 Oct 2017 14:43:00 + Source: fritzing Binary: fritzing fritzing-data Architecture: source Version: 0.9.3b+dfsg-4.1 Distribution: unstable Urgency: medium Maintainer: Enrique Hernández Bello Changed-By: Peter Michael Green Description: fritzing - Easy-to-use electronic design software fritzing-data - Easy-to-use electronic design software (data files) Closes: 872847 Changes: fritzing (0.9.3b+dfsg-4.1) unstable; urgency=medium . * Non-maintainer upload. * Set new "proxy" parameter in git_remote_connect to NULL (Closes: 872847) * Bump libgit2 build-dependency to >= 0.25 due to above patch. Checksums-Sha1: ecffb39f45ebce4ae689bc2118c17913b210ad32 2181 fritzing_0.9.3b+dfsg-4.1.dsc a188b63ae4e6176913f7311ab1b50b1a90d6ec49 22536 fritzing_0.9.3b+dfsg-4.1.debian.tar.xz 57ea6bd43ff55f566ff91a9c83b942cbcb7d1e6c 9956 fritzing_0.9.3b+dfsg-4.1_source.buildinfo Checksums-Sha256: 248792c3ecd7fd7e4a256b0b3ab5c44102c73eed797c40f6686ef034fdb25714 2181 fritzing_0.9.3b+dfsg-4.1.dsc 2317dc3fa68fbda6dda4d4f961f6138d931487d01cb2bb53dafbf90745ac219f 22536 fritzing_0.9.3b+dfsg-4.1.debian.tar.xz 2759edbea52f384dc8d1fafab2d2592fd08f5d460c74540cb8b47f85ac4af33a 9956 fritzing_0.9.3b+dfsg-4.1_source.buildinfo Files: 77a3094184e7cd13f0b27e6a78b1f94f 2181 electronics optional fritzing_0.9.3b
Bug#878747: marked as done (gst-plugins-bad1.0 FTBFS with libopenjp2-7-dev 2.3)
Your message dated Thu, 19 Oct 2017 15:06:51 + with message-id and subject line Bug#878747: fixed in gst-plugins-bad1.0 1.12.3-2 has caused the Debian Bug report #878747, regarding gst-plugins-bad1.0 FTBFS with libopenjp2-7-dev 2.3 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.) -- 878747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gst-plugins-bad1.0 Version: 1.12.2-1 Severity: serious https://buildd.debian.org/status/package.php?p=gst-plugins-bad1.0&suite=sid ... In file included from gstopenjpegdec.h:29:0, from gstopenjpegdec.c:27: gstopenjpeg.h:42:12: fatal error: openjpeg-2.2/openjpeg.h: No such file or directory # include ^ compilation terminated. --- End Message --- --- Begin Message --- Source: gst-plugins-bad1.0 Source-Version: 1.12.3-2 We believe that the bug you reported is fixed in the latest version of gst-plugins-bad1.0, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated gst-plugins-bad1.0 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, 19 Oct 2017 15:35:50 +0200 Source: gst-plugins-bad1.0 Binary: gstreamer1.0-plugins-bad-doc gstreamer1.0-plugins-bad gstreamer1.0-plugins-bad-dbg libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-bad1.0-dev gir1.2-gst-plugins-bad-1.0 Architecture: source amd64 all Version: 1.12.3-2 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages Changed-By: Sebastian Dröge Description: gir1.2-gst-plugins-bad-1.0 - GObject introspection data for the GStreamer libraries from the " gstreamer1.0-plugins-bad - GStreamer plugins from the "bad" set gstreamer1.0-plugins-bad-dbg - GStreamer plugins from the "bad" set (debug symbols) gstreamer1.0-plugins-bad-doc - GStreamer documentation for plugins from the "bad" set libgstreamer-plugins-bad1.0-0 - GStreamer development files for libraries from the "bad" set libgstreamer-plugins-bad1.0-dev - GStreamer development files for libraries from the "bad" set Closes: 878747 Changes: gst-plugins-bad1.0 (1.12.3-2) unstable; urgency=medium . * debian/patches/0001-openjpeg-Support-building-with-openjpeg-2.3.patch: + Fix build against openjpeg 2.3 (Closes: #878747). Checksums-Sha1: 36e8a3e339d27dcf0ff25a10994bb22e19292c74 4857 gst-plugins-bad1.0_1.12.3-2.dsc 276125bb83095ad1b9bf17daf40e67886a354320 34384 gst-plugins-bad1.0_1.12.3-2.debian.tar.xz 38f439e81a49a5e9ad048ac571f53e9e0dfc62cf 1572912 gir1.2-gst-plugins-bad-1.0_1.12.3-2_amd64.deb f01de1cd6af43d722ad2ef6f9ca42769e4e0c048 29237 gst-plugins-bad1.0_1.12.3-2_amd64.buildinfo db0c6d49fd0082f92c6d40a48b165fd0efd3b8b5 12043456 gstreamer1.0-plugins-bad-dbg_1.12.3-2_amd64.deb e983567cd722cc4558189aa22c2b8c9719eec4c0 1807536 gstreamer1.0-plugins-bad-doc_1.12.3-2_all.deb fab21095068822f30ff9265cd9837b1070bc5737 3100864 gstreamer1.0-plugins-bad_1.12.3-2_amd64.deb a5d4dd3ae1d88af30a4d9afac22dd7e25e32098f 1950720 libgstreamer-plugins-bad1.0-0_1.12.3-2_amd64.deb 78fa7c391cb656d699aad3bc07a1ed9ffeed08be 1684000 libgstreamer-plugins-bad1.0-dev_1.12.3-2_amd64.deb Checksums-Sha256: 09809f2f7a3b08cc6be417a11e59a268938801f30f23acf92e6ec3fe7431a637 4857 gst-plugins-bad1.0_1.12.3-2.dsc 09fd74295e37a4d333236d8aede7d4ea727ffc0e551825e5ca4738c08014069f 34384 gst-plugins-bad1.0_1.12.3-2.debian.tar.xz 5d5a7b49bfd245b8ae44c6c9aad69601f2d002f5b0380949b958477213e594d8 1572912 gir1.2-gst-plugins-bad-1.0_1.12.3-2_amd64.deb 40a2ad5f404fea58a49e77617288f757c34c6edb316a9f8a5e9bbe764974ce75 29237 gst-plugins-bad1.0_1.12.3-2_amd64.buildinfo 0f79f789144dce9f73c28c5e097009fa86d7d42c43e335d020ad466fd623e3e0 12043456 gstreamer1.0-plugins-bad-dbg_1.12.3-2_amd64.deb fa6ddef7f08bb9f4404688d0fab4bf3d2e0695b550ad9b9241f89a11153a2d2e 1807536 gstreamer1.0-plugins-bad-doc_1.12.3-2_all.deb 312a71890f7e5003ff8e34388c7e19c40768e30d90d30da0e815fc1f331ee450 3100864 gstreamer1.0-plugins-bad_1.12.3-2_amd64.deb 0627d8
Bug#879088: babeltrace: package merge makes gdb, linux-perf etc. uninstallable
On 2017-10-19 04:18, Adrian Bunk wrote:
> Control: retitle -1 Please make libbabeltrace-ctf{1,-dev} provides versioned
>
> On Thu, Oct 19, 2017 at 08:28:46AM +0100, Simon McVittie wrote:
>> ...
>> Please do one of these as soon as possible:
>> ...
>
> None of these is required.
>
> Making the libbabeltrace-ctf{1,-dev} provides versioned is all that is
> required to fix the versioned (build) dependencies.
>
> cu
> Adrian
>
Sorry for that mess, I will upload a fixed package with the versioned
provides. Thanks for pointing me in the right direction.
Cheers,
Michael
Bug#872847: NMU uploaded for Fritzing FTBFS
Based on the positive feedback from Ximin Luo I have uploaded my FTBFS fix for
fritzing as a NMU. A debdiff of what was finally uploaded is attatched (which
other than the changelog is the same as the raspbian debdiff I linked earlier).
diff -Nru fritzing-0.9.3b+dfsg/debian/changelog
fritzing-0.9.3b+dfsg/debian/changelog
--- fritzing-0.9.3b+dfsg/debian/changelog 2017-01-23 16:27:29.0
+
+++ fritzing-0.9.3b+dfsg/debian/changelog 2017-10-19 14:43:00.0
+
@@ -1,3 +1,11 @@
+fritzing (0.9.3b+dfsg-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Set new "proxy" parameter in git_remote_connect to NULL (Closes: 872847)
+ * Bump libgit2 build-dependency to >= 0.25 due to above patch.
+
+ -- Peter Michael Green Thu, 19 Oct 2017 14:43:00 +
+
fritzing (0.9.3b+dfsg-4) unstable; urgency=medium
* created a shell script to launch fritzing with a special pwd.
diff -Nru fritzing-0.9.3b+dfsg/debian/control
fritzing-0.9.3b+dfsg/debian/control
--- fritzing-0.9.3b+dfsg/debian/control 2016-11-01 12:05:59.0 +
+++ fritzing-0.9.3b+dfsg/debian/control 2017-09-21 02:29:48.0 +
@@ -11,7 +11,7 @@
libqt5svg5-dev,
zlib1g-dev,
libboost-dev,
- libgit2-dev (>= 0.24.1),
+ libgit2-dev (>= 0.25),
sqlite3
Standards-Version: 3.9.8
Vcs-Browser: https://bazaar.launchpad.net/~ehbello/fritzing/debian/changes
diff -Nru fritzing-0.9.3b+dfsg/debian/patches/add-proxy-parameter.diff
fritzing-0.9.3b+dfsg/debian/patches/add-proxy-parameter.diff
--- fritzing-0.9.3b+dfsg/debian/patches/add-proxy-parameter.diff
1970-01-01 00:00:00.0 +
+++ fritzing-0.9.3b+dfsg/debian/patches/add-proxy-parameter.diff
2017-09-21 02:28:07.0 +
@@ -0,0 +1,14 @@
+Description: Set new "proxy" parameter in git_remote_connect to NULL
+Author: Peter Michael Green
+
+--- fritzing-0.9.3b+dfsg.orig/src/version/partschecker.cpp
fritzing-0.9.3b+dfsg/src/version/partschecker.cpp
+@@ -123,7 +123,7 @@ bool PartsChecker::newPartsAvailable(con
+ */
+ git_strarray customheaders;
+ customheaders.count = 0;
+-error = git_remote_connect(remote, GIT_DIRECTION_FETCH, &callbacks,
&customheaders);
++error = git_remote_connect(remote, GIT_DIRECTION_FETCH, &callbacks,NULL,
&customheaders);
+ if (error) {
+ partsCheckerResult.partsCheckerError = PARTS_CHECKER_ERROR_REMOTE;
+ partsCheckerResult.errorMessage = QObject::tr("Unable to access
network site for '%1'. %2").arg(repoPath).arg(sBoilerPlate1);
diff -Nru fritzing-0.9.3b+dfsg/debian/patches/series
fritzing-0.9.3b+dfsg/debian/patches/series
--- fritzing-0.9.3b+dfsg/debian/patches/series 2017-01-23 16:27:29.0
+
+++ fritzing-0.9.3b+dfsg/debian/patches/series 2017-09-21 02:27:39.0
+
@@ -4,3 +4,4 @@
git-remote-connect.patch
no-isystem-for-gcc6.patch
fritzing.desktop.patch
+add-proxy-parameter.diff
Bug#867681: software-properties-gtk: trusted.gpg file created by this package produces gpg error for 'apt-get update'
Dear Maintainer, we confirm the problem adding keys (but not repos) via gui. Updating generate to us errors on the same keys described in this post http://forums.debian.net/viewtopic.php?t=134409#p652757 Deleting /etc/apt/trusted.gpg file and adding keys via apt-key workaroud the problem ... Regards! Guido
Bug#877962: prosody: fails to upgrade from 'sid' - trying to overwrite /usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua
Hi, > From the attached log (scroll to the bottom...): > > Preparing to unpack .../prosody_0.10~hg745e0a783055-3_amd64.deb ... > invoke-rc.d: could not determine current runlevel > invoke-rc.d: policy-rc.d denied execution of stop. > Unpacking prosody (0.10~hg745e0a783055-3) over (0.9.12-2) ... > dpkg: error processing archive > /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb ( > --unpack): > trying to overwrite > '/usr/lib/prosody/modules/mod_mam/fallback_archive.lib.lua', which is > also in package prosody-modules 0.0~hg20170929.c53cc1ae4788+dfsg-1 > dpkg-deb: error: subprocess paste was killed by signal (Broken > pipe) > invoke-rc.d: could not determine current runlevel > invoke-rc.d: policy-rc.d denied execution of start. > Errors were encountered while processing: > /var/cache/apt/archives/prosody_0.10~hg745e0a783055-3_amd64.deb > with the latest version in sid (0.10.0-1) this shouldn't be the case anymore. This bug actually blocks the transition to testing. Kind regards, Dan smime.p7s Description: S/MIME cryptographic signature
Processed: fix severity and tags
Processing commands for cont...@bugs.debian.org:
> severity 857662 important
Bug #857662 {Done: Laurent Bigonville } [cron] cron broken in
SELinux enforced mode due to system_u login mapping removal
Severity set to 'important' from 'grave'
> tag 857662 - stretch buster sid
Bug #857662 {Done: Laurent Bigonville } [cron] cron broken in
SELinux enforced mode due to system_u login mapping removal
Removed tag(s) buster, sid, and stretch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
857662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reopening 878852
Processing commands for cont...@bugs.debian.org:
> reopen 878852
Bug #878852 {Done: Julien Cristau } [postgresql-9.6]
Remove postgresql-9.6 from testing
Bug reopened
Ignoring request to alter fixed versions of bug #878852 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
878852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#879094: marked as done (marble: FTBFS in unstable - missing symbols)
Your message dated Thu, 19 Oct 2017 15:15:45 +0300 with message-id <20171019121545.d6xh477zyaoxm3yu@localhost> and subject line Already fixed in experimental has caused the Debian Bug report #879094, regarding marble: FTBFS in unstable - missing symbols 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.) -- 879094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879094 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: marble Version: 4:16.08.3-1 Severity: serious Tags: sid buster Hi, marble currently FTBFS in unstable with this error: > dh_makeshlibs '-Xusr/lib/libkdeinit5_*' # [-a] > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: no debian/symbols file used as basis for generating > debian/libmarblewidget-qt5-25/DEBIAN/symbols > --- new_symbol_file (libmarblewidget-qt5-25_4:16.08.3-1_amd64) > +++ dpkg-gensymbolsMV7mBX 2017-10-19 10:09:31.773007994 + > @@ -4001,8 +4001,8 @@ > _ZN6MarbleeqERKNS_16GeoDataLatLonBoxES2_@Base 4:15.08.0 > _ZN6MarbleeqERKNS_19GeoDataLatLonAltBoxES2_@Base 4:15.08.0 > _ZN6MarbleneERKNS_16GeoDataLatLonBoxES2_@Base 4:15.08.0 > - _ZN6QColorC1EPKc@Base 4:15.08.0 > - _ZN6QColorC2EPKc@Base 4:15.08.0 > +#MISSING: 4:16.08.3-1# _ZN6QColorC1EPKc@Base 4:15.08.0 > +#MISSING: 4:16.08.3-1# _ZN6QColorC2EPKc@Base 4:15.08.0 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI21QPersistentModelIndexE6appendERKS0_@Base 4:15.08.0 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI5QIconE6appendEOS0_@Base 4:16.04.3 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI5QIconE6appendERKS0_@Base 4:15.08.0 > dh_makeshlibs: failing due to earlier errors > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target > 'pre_binary-arch_dh_makeshlibs' failed > make[1]: *** [pre_binary-arch_dh_makeshlibs] Error 2 > make[1]: Leaving directory '/<>' > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target > 'debian/dhmk_binary-arch' failed > make: *** [debian/dhmk_binary-arch] Error 2 > dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess > returned exit status 2 Full logs can be found on the reproducible builds pages for marble. James signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 4:17.08.1-1 marble (4:17.08.1-1) experimental; urgency=medium ... * Update symbols files ... -- Maximiliano Curia Mon, 18 Sep 2017 15:06:41 +0200 https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/marble.html 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--- End Message ---
Bug#877823: marked as done (gcc-7-cross-ports build depends on removed transitional package realpath)
Your message dated Thu, 19 Oct 2017 12:00:40 + with message-id and subject line Bug#877823: fixed in gcc-7-cross-ports 7 has caused the Debian Bug report #877823, regarding gcc-7-cross-ports build depends on removed transitional package realpath 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.) -- 877823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-7-cross-ports Version: 6 Severity: serious gcc-7-cross-ports build depends on the transitional package realpath, removed in coreutils 8.28-1. The realpath program is part of the (essential) coreutils package since 8.23-1. --- End Message --- --- Begin Message --- Source: gcc-7-cross-ports Source-Version: 7 We believe that the bug you reported is fixed in the latest version of gcc-7-cross-ports, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-7-cross-ports 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, 18 Oct 2017 13:27:00 +0200 Source: gcc-7-cross-ports Binary: gcc-7-cross-base-ports gcc-7-alpha-linux-gnu-base libgcc1-alpha-cross libgcc-7-dev-alpha-cross gcc-7-alpha-linux-gnu gcc-7-plugin-dev-alpha-linux-gnu cpp-7-alpha-linux-gnu g++-7-alpha-linux-gnu libgomp1-alpha-cross libitm1-alpha-cross libatomic1-alpha-cross gobjc++-7-alpha-linux-gnu gobjc-7-alpha-linux-gnu libobjc4-alpha-cross libobjc-7-dev-alpha-cross gfortran-7-alpha-linux-gnu libgfortran4-alpha-cross libgfortran-7-dev-alpha-cross gccgo-7-alpha-linux-gnu libgo11-alpha-cross libstdc++6-alpha-cross libstdc++-7-dev-alpha-cross libstdc++-7-pic-alpha-cross gdc-7-alpha-linux-gnu gnat-7-alpha-linux-gnu gnat-7-sjlj-alpha-linux-gnu libgnat-7-alpha-cross gcc-7-hppa-linux-gnu-base libgcc-7-dev-hppa-cross libgcc4-hppa-cross gcc-7-hppa-linux-gnu gcc-7-plugin-dev-hppa-linux-gnu cpp-7-hppa-linux-gnu g++-7-hppa-linux-gnu libgomp1-hppa-cross libatomic1-hppa-cross gobjc++-7-hppa-linux-gnu gobjc-7-hppa-linux-gnu libobjc4-hppa-cross libobjc-7-dev-hppa-cross gfortran-7-hppa-linux-gnu libgfortran4-hppa-cross libgfortran-7-dev-hppa-cross libstdc++6-hppa-cross libstdc++-7-dev-hppa-cross libstdc++-7-pic-hppa-cross gdc-7-hppa-linux-gnu gnat-7-hppa-linux-gnu gnat-7-sjlj-hppa-linux-gnu libgnat-7-hppa-cross gcc-7-m68k-linux-gnu-base libgcc-7-dev-m68k-cross libgcc2-m68k-cross gcc-7-m68k-linux-gnu gcc-7-plugin-dev-m68k-linux-gnu cpp-7-m68k-linux-gnu g++-7-m68k-linux-gnu libgomp1-m68k-cross libatomic1-m68k-cross gobjc++-7-m68k-linux-gnu gobjc-7-m68k-linux-gnu libobjc4-m68k-cross libobjc-7-dev-m68k-cross gfortran-7-m68k-linux-gnu libgfortran4-m68k-cross libgfortran-7-dev-m68k-cross libstdc++6-m68k-cross libstdc++-7-dev-m68k-cross libstdc++-7-pic-m68k-cross gdc-7-m68k-linux-gnu gnat-7-m68k-linux-gnu gnat-7-sjlj-m68k-linux-gnu libgnat-7-m68k-cross gcc-7-mips64-linux-gnuabi64-base libgcc1-mips64-cross libgcc-7-dev-mips64-cross lib32gcc1-mips64-cross lib32gcc-7-dev-mips64-cross libn32gcc1-mips64-cross libn32gcc-7-dev-mips64-cross gcc-7-mips64-linux-gnuabi64 gcc-7-multilib-mips64-linux-gnuabi64 gcc-7-plugin-dev-mips64-linux-gnuabi64 cpp-7-mips64-linux-gnuabi64 g++-7-mips64-linux-gnuabi64 g++-7-multilib-mips64-linux-gnuabi64 libgomp1-mips64-cross lib32gomp1-mips64-cross libn32gomp1-mips64-cross libatomic1-mips64-cross lib32atomic1-mips64-cross libn32atomic1-mips64-cross gobjc++-7-mips64-linux-gnuabi64 gobjc++-7-multilib-mips64-linux-gnuabi64 gobjc-7-mips64-linux-gnuabi64 gobjc-7-multilib-mips64-linux-gnuabi64 libobjc4-mips64-cross libobjc-7-dev-mips64-cross lib32objc4-mips64-cross lib32objc-7-dev-mips64-cross libn32objc4-mips64-cross libn32objc-7-dev-mips64-cross gfortran-7-mips64-linux-gnuabi64 gfortran-7-multilib-mips64-linux-gnuabi64 libgfortran4-mips64-cross libgfortran-7-dev-mips64-cross lib32gfortran4-mips64-cross lib32gfortran-7-dev-mips64-cross libn32gfortran4-mips64-cross libn32gfortran-7-dev-mips64-cross gccgo-7-mips64-linux-gnuabi64 gccgo-7-multilib-mips64-linux-gnuabi64 libgo11-mips64-cross lib32go
Bug#879088: babeltrace: package merge makes gdb, linux-perf etc. uninstallable
On Thu, 19 Oct 2017 at 11:18:28 +0300, Adrian Bunk wrote:
> Control: retitle -1 Please make libbabeltrace-ctf{1,-dev} provides versioned
>
> On Thu, Oct 19, 2017 at 08:28:46AM +0100, Simon McVittie wrote:
> >...
> > Please do one of these as soon as possible:
> >...
>
> None of these is required.
>
> Making the libbabeltrace-ctf{1,-dev} provides versioned is all that is
> required to fix the versioned (build) dependencies.
Yes, or that, if the archive and the various apt frontends do the right
thing for versioned Provides. They are not currently allowed by Policy
(#761219) but hopefully that is just a case of Policy lagging behind
reality.
Thanks for the reminder that versioned Provides are finally a thing now!
smcv
Bug#868538: marked as done (File conflict between bind9-dbgsym lwresd-dbgsym)
Your message dated Thu, 19 Oct 2017 11:18:55 + with message-id and subject line Bug#868538: fixed in bind9 1:9.10.6+dfsg-2 has caused the Debian Bug report #868538, regarding File conflict between bind9-dbgsym lwresd-dbgsym 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.) -- 868538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bind9 Version: 1:9.10.3.dfsg.P4-12.3 Severity: serious Control: affects -1 bind9-dbgsym lwresd-dbgsym # apt-get install bind9-dbgsym lwresd-dbgsym ... dpkg: error processing archive /var/cache/apt/archives/lwresd-dbgsym_1%3a9.10.3.dfsg.P4-12.3_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/.build-id/69/bfa43a691a466a05ec512f8316c88cdd98cbe1.debug', which is also in package bind9-dbgsym 1:9.10.3.dfsg.P4-12.3 The problem is that /usr/sbin/lwresd and /usr/sbin/named are the same binary but shipped in different packages. --- End Message --- --- Begin Message --- Source: bind9 Source-Version: 1:9.10.6+dfsg-2 We believe that the bug you reported is fixed in the latest version of bind9, 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 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated bind9 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, 19 Oct 2017 09:35:03 + Source: bind9 Binary: bind9 bind9utils bind9-doc bind9-host libbind-dev libbind9-141 libdns190 libirs141 libisc189 liblwres141 libisccc140 libisccfg144 dnsutils lwresd libbind-export-dev libdns-export190 libdns-export190-udeb libirs-export141 libirs-export141-udeb libisc-export189 libisc-export189-udeb libisccc-export140 libisccc-export140-udeb libisccfg-export144 libisccfg-export144-udeb Architecture: source Version: 1:9.10.6+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian DNS Packaging Changed-By: Ondřej Surý Description: bind9 - Internet Domain Name Server bind9-doc - Documentation for BIND bind9-host - Version of 'host' bundled with BIND 9.X bind9utils - Utilities for BIND dnsutils - Clients provided with BIND libbind-dev - Static Libraries and Headers used by BIND libbind-export-dev - Development files for the exported BIND libraries libbind9-141 - BIND9 Shared Library used by BIND libdns-export190 - Exported DNS Shared Library libdns-export190-udeb - Exported DNS library for debian-installer (udeb) libdns190 - DNS Shared Library used by BIND libirs-export141 - Exported IRS Shared Library libirs-export141-udeb - Exported IRS library for debian-installer (udeb) libirs141 - DNS Shared Library used by BIND libisc-export189 - Exported ISC Shared Library libisc-export189-udeb - Exported ISC library for debian-installer (udeb) libisc189 - ISC Shared Library used by BIND libisccc-export140 - Command Channel Library used by BIND libisccc-export140-udeb - Command Channel Library used by BIND (udeb) libisccc140 - Command Channel Library used by BIND libisccfg-export144 - Exported ISC CFG Shared Library libisccfg-export144-udeb - Exported ISC CFG library for debian-installer (udeb) libisccfg144 - Config File Handling Library used by BIND liblwres141 - Lightweight Resolver Library used by BIND lwresd - Lightweight Resolver Daemon Closes: 645437 868538 874232 878228 879017 879018 Changes: bind9 (1:9.10.6+dfsg-2) unstable; urgency=medium . [ Timo Aaltonen ] * d/copyright: Add Bv9ARM.pdf to Files-Excluded. . [ Ondřej Surý ] * Replace lwresd with symlink instead of hard copy (Closes: #868538) * Fix the symbols file to compensate for missing bsdcompat symbol on kFreeBSD (Closes: #879017) * Re-enable threading support on kFreeBSD (Closes: #879018) * Drop Multi-Arch: same header from libbind-dev (Closes: #874232) * Remove transitional host package (Closes: #645437, #878228) Checksums-Sha1: 4a553f9aa606d29afbd1cce1f34683a6b6483c1d 3884 bind9_9.10.6+dfsg-2.dsc c91c96e076ed58d03558b11c374cef8361025df5 84744 bind9_9.10.6+dfsg-2.debian.tar.xz ccf9d0c2d378d7867ee8a8e23b89c1c8533c8e39 18914 bind9_9.10.6+dfsg-2_am
Bug#878932: marked as done (generator-scripting-language: Incomplete debian/copyright?)
Your message dated Thu, 19 Oct 2017 11:01:21 + with message-id and subject line Bug#878932: fixed in generator-scripting-language 4.1.5-2 has caused the Debian Bug report #878932, regarding generator-scripting-language: Incomplete debian/copyright? 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.) -- 878932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: generator-scripting-language Version: 4.1.5-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Luca Boccassi Hi, I just ACCEPTed generator-scripting-language from NEW but noticed it was missing attribution in debian/copyright for at least Todd Miller within sflstr.c. (This is not 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 `- --- End Message --- --- Begin Message --- Source: generator-scripting-language Source-Version: 4.1.5-2 We believe that the bug you reported is fixed in the latest version of generator-scripting-language, 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 878...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Boccassi (supplier of updated generator-scripting-language 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, 19 Oct 2017 11:20:30 +0100 Source: generator-scripting-language Binary: generator-scripting-language generator-scripting-language-examples Architecture: source Version: 4.1.5-2 Distribution: unstable Urgency: medium Maintainer: Luca Boccassi Changed-By: Luca Boccassi Description: generator-scripting-language - Generator Scripting Language code generator generator-scripting-language-examples - Examples for the Generator Scripting Language code generator Closes: 878932 879023 Changes: generator-scripting-language (4.1.5-2) unstable; urgency=medium . * Add copyright notice for sflstr.c and MIT license. (Closes: #878932) * Add fix-sparc64.patch to fix FTBS on Sparc 64. (Closes: #879023) * Add fix-mips64el.patch to fix FTBS on mips64el. * Bump Standards-Version to 4.1.1, no changes. Checksums-Sha1: 65049e3dc7601486b7f381f9bc2b81dc7da738df 1765 generator-scripting-language_4.1.5-2.dsc d6862aa4b04a151b127da9ec8b0de2303b96072b 3960 generator-scripting-language_4.1.5-2.debian.tar.xz f1ce72fcfa6a858d806be05b30a2a650f47669ce 6407 generator-scripting-language_4.1.5-2_source.buildinfo Checksums-Sha256: c2e646fb696e7414365e317df3e142ae934119605f3afb2fcfcc0c531651296a 1765 generator-scripting-language_4.1.5-2.dsc fae50238380898c6b326243eeb2d2d0e82beafefaf52b32fb13e0d8d993c25af 3960 generator-scripting-language_4.1.5-2.debian.tar.xz 6364c5ec996515196a8da8a7b2796d83286f9d472fc8b9c4d5363e0cc25f4270 6407 generator-scripting-language_4.1.5-2_source.buildinfo Files: 4c09a64ca55b756d8d40533e76f92f7f 1765 devel optional generator-scripting-language_4.1.5-2.dsc 9d4216005c0ca8e8c07b59aaf98d9972 3960 devel optional generator-scripting-language_4.1.5-2.debian.tar.xz 31dd924f2174a60325c4f97697637e79 6407 devel optional generator-scripting-language_4.1.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCgAvFiEE6g0RLAGYhL9yp9G8SylmgFB4UWIFAlnofLARHGJsdWNhQGRl Ymlhbi5vcmcACgkQSylmgFB4UWItlgf/WvpaWphafWBSmE9brKWUikBtOdPXu7gS cHDi+sAS8xyHVF+RiCyJwRn1oNbKk1wHk7pFhW7HbnVQObUgvQwQT5JszVPyz9kR XnvKKLqAiTmGe6tbMaxg+WanOw4jPJV0xem0/KvhG0rrPO0TXNYmef58rmOqfa/Y WEiR+hU5gGlmTW/iEIWcrUz6fd4HOuEdwoUKmIFoH09RzvUE/TWsKHsCZMNyNJYU czUd69Lf8bTfLkskDtFreWb03d2uBHDhtyUWOL3AoovsT9pQnFATSwIUdryqUbx2 RnIWnpRdLp62rJG2GAkAtTus5nlTEg/s1JsqMeNY1vHe00Lb38E0/Q== =JPVr -END PGP SIGNATURE End Message ---
Processed: block distcc/exp -> unstable
Processing commands for cont...@bugs.debian.org: > block 787472 by 785990 Bug #787472 [src:distcc] distcc: push 3.2 RC1 in unstable 787472 was not blocked by any bugs. 787472 was not blocking any bugs. Added blocking bug(s) of 787472: 785990 > thanks Stopping processing here. Please contact me if you need assistance. -- 787472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877567: marked as done (llvm-toolchain-3.9 FTBFS on mipsel)
Your message dated Thu, 19 Oct 2017 10:22:22 + with message-id and subject line Bug#877567: fixed in llvm-toolchain-4.0 1:4.0.1-8 has caused the Debian Bug report #877567, regarding llvm-toolchain-3.9 FTBFS on mipsel 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.) -- 877567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-3.9 Version: 1:3.9.1-17 Severity: serious https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-3.9&arch=mipsel ... /usr/bin/ld: BFD (GNU Binutils for Debian) 2.29.1 internal error, aborting at ../../bfd/merge.c:910 in _bfd_merged_section_offset /usr/bin/ld: Please report this bug. collect2: error: ld returned 1 exit status tools/llvm-shlib/CMakeFiles/LLVM.dir/build.make:274: recipe for target 'lib/libLLVM-3.9.so.1' failed make[4]: *** [lib/libLLVM-3.9.so.1] Error 1 In #874674 it was discovered that this is just a bad error handling for "out of memory" in ld. llvm-toolchain-3.9 (1:3.9.1-16) unstable; urgency=medium ... [ Matthias Klose ] ... * On amd64, s390x, arm64 and ppc64el, build with -g1 instead of -g. ... -- Sylvestre Ledru Fri, 08 Sep 2017 11:57:07 +0200 This is also what debian/rules does, and it is pretty weird: ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el s390x)) opt_flags += -g1 else opt_flags += -g endif -g is equal to -g2, so this change reduces the amount of debug information generated on some 64bit architectures - these are architectures where -g is supposed to not cause any problems. mipsel being the only failing release architecture makes sense considering that -g is used on 32bit, and mipsel is missing in the list of gsplit dwarf architectures. There are three alternative approaches, either would make sense and should fix the mipsel build (untested): 1. go back to -g everywhere and remove ENABLE_SPLIT_DWARF_ARCHS, that's then actually required on all 32bit architectures: ifeq ($(DEB_HOST_ARCH_BITS),32) CXXFLAGS_EXTRA += -gsplit-dwarf endif 2. remove all gsplit dwarf usage and reverse the -g1 handling so that it makes sense: ifeq ($(DEB_HOST_ARCH_BITS),32) opt_flags += -g1 else opt_flags += -g endif 3. remove all gsplit dwarf usage and use -g1 on all architectures: opt_flags += -g1 --- End Message --- --- Begin Message --- Source: llvm-toolchain-4.0 Source-Version: 1:4.0.1-8 We believe that the bug you reported is fixed in the latest version of llvm-toolchain-4.0, 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 877...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-4.0 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, 18 Oct 2017 16:37:25 +0200 Source: llvm-toolchain-4.0 Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools llvm-4.0-doc llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev Architecture: source amd64 all Version: 1:4.0.1-8 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang-4.0 - C, C++ and Objective-C compiler (LLVM based) clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation clang-4.0-examples - Clang examples clang-format-4.0 - Tool to format C/C++/Obj-C code clang-tidy-4.0 - clang-based C++ linter tool libclang-4.0-dev - clang library - Development package libclang-common-4.0-dev - clang library - Common development package libclang1-4.0 - C interface to the clang library libclang1-4.0-dbg - clang library libfuzzer-4.0-dev - Library for coverage-guided fuzz testing liblld-4.0 - LLVM-based linker, library liblld-4.0-dbg - LLVM-based linker, debugging libraries liblld-4.0-dev - LLVM-based linker, header files liblldb-4.0 - Next generation
Bug#879094: marble: FTBFS in unstable - missing symbols
Source: marble Version: 4:16.08.3-1 Severity: serious Tags: sid buster Hi, marble currently FTBFS in unstable with this error: > dh_makeshlibs '-Xusr/lib/libkdeinit5_*' # [-a] > dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: no debian/symbols file used as basis for generating > debian/libmarblewidget-qt5-25/DEBIAN/symbols > --- new_symbol_file (libmarblewidget-qt5-25_4:16.08.3-1_amd64) > +++ dpkg-gensymbolsMV7mBX 2017-10-19 10:09:31.773007994 + > @@ -4001,8 +4001,8 @@ > _ZN6MarbleeqERKNS_16GeoDataLatLonBoxES2_@Base 4:15.08.0 > _ZN6MarbleeqERKNS_19GeoDataLatLonAltBoxES2_@Base 4:15.08.0 > _ZN6MarbleneERKNS_16GeoDataLatLonBoxES2_@Base 4:15.08.0 > - _ZN6QColorC1EPKc@Base 4:15.08.0 > - _ZN6QColorC2EPKc@Base 4:15.08.0 > +#MISSING: 4:16.08.3-1# _ZN6QColorC1EPKc@Base 4:15.08.0 > +#MISSING: 4:16.08.3-1# _ZN6QColorC2EPKc@Base 4:15.08.0 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI21QPersistentModelIndexE6appendERKS0_@Base 4:15.08.0 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI5QIconE6appendEOS0_@Base 4:16.04.3 > #MISSING: 4:16.08.2# (optional=templinst|arch=!amd64 !armhf > !i386)_ZN7QVectorI5QIconE6appendERKS0_@Base 4:15.08.0 > dh_makeshlibs: failing due to earlier errors > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target > 'pre_binary-arch_dh_makeshlibs' failed > make[1]: *** [pre_binary-arch_dh_makeshlibs] Error 2 > make[1]: Leaving directory '/<>' > /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target > 'debian/dhmk_binary-arch' failed > make: *** [debian/dhmk_binary-arch] Error 2 > dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess > returned exit status 2 Full logs can be found on the reproducible builds pages for marble. James signature.asc Description: OpenPGP digital signature
Bug#878402: [debian-mysql] Bug#878402: Bug#878402: Security fixes from the October 2017 CPU
On 10/19/2017 10:09 AM, Emilio Pozuelo Monfort wrote: On 18/10/17 20:46, Salvatore Bonaccorso wrote: Hi lars, On Wed, Oct 18, 2017 at 03:51:26PM +0200, Lars Tangvald wrote: Hi, 5.5.58 packages for Debian 7 and 8 are built, and pass the test suite. Attached are debdiff files for Wheezy and Jessie (source is also pushed to https://urldefense.proofpoint.com/v2/url?u=https-3A__anonscm.debian.org_cgit_pkg-2Dmysql_mysql-2D5.5.git&d=DwICaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=HPjEzLhETPj8fl9HCxxISaaV3f5tXDpGXDR3R2IELxg&m=00T7TUZCwXkig-wYCf-35nC5VNSQmjNOsNq0TOBoXBs&s=MPjTux6yCV6-5Si_VECXoTwgZxgsyNIHfNSpH1nq2ws&e= ) As before, we unfortunately don't have a DD in our team that can sponsor the upload, so we need assistance with that. I will look into it for jessie-security then. I'm not sure if the security team still handles Debian8, or if the lts team does now? Yes, Debian 8 Jessie is still yet handled by the security team. And I will take of Debian 7 (wheezy). Thanks for preparing the update! Cheers, Emilio Thanks for the help to both of you! :) -- Lars
Bug#879083: marked as done (FTBFS virtualbox 5.2)
Your message dated Thu, 19 Oct 2017 09:24:54 + (UTC) with message-id <1926566396.183383.1508405094...@mail.yahoo.com> and subject line Re: Bug#879083: FTBFS virtualbox 5.2 has caused the Debian Bug report #879083, regarding FTBFS virtualbox 5.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.) -- 879083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: virtualbox Version: 5.2.0-dfsg Severity: serious Tag: experimental Hi, virtualbox currently FTBFS in experimental, see https://buildd.debian.org/status/fetch.php?pkg=virtualbox&arch=all&ver=5.2.0-dfsg-1%7Eexp1&stamp=1508354297&raw=0 Regards, Daniel --- End Message --- --- Begin Message --- Hello, >virtualbox currently FTBFS in experimental, see >https://buildd.debian.org/status/fetch.php?pkg=virtualbox&arch=all&ver=5.2.0-dfsg-1%7Eexp1&stamp=1508354297&raw=0 I'm fully aware of this, actually this is why I did upload in experimental patches welcome! (I'm already discussing the issue with upstream and mail list since yesterday) such bugs are useless to me, because I'll likely forget to close them, and I monitor build failures! G.--- End Message ---
Bug#867439: marked as done (python3-mimeparse: missing dependencies)
Your message dated Thu, 19 Oct 2017 09:05:08 +
with message-id
and subject line Bug#867439: fixed in python-mimeparse 0.1.4-3.1
has caused the Debian Bug report #867439,
regarding python3-mimeparse: missing dependencies
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.)
--
867439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mimeparse
Version: 0.1.4-1
Severity: serious
Tags: patch
Due to a cut'n'paste error there are no dependencies.
Fix:
--- debian/control.old 2017-07-06 16:46:30.0 +
+++ debian/control 2017-07-06 16:46:36.0 +
@@ -25,7 +25,7 @@
Package: python3-mimeparse
Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
Description: Parse mime-types and quality parameters - python 3.x
This module provides basic functions for parsing mime-type names and
matching them against a list of media-ranges.
--- End Message ---
--- Begin Message ---
Source: python-mimeparse
Source-Version: 0.1.4-3.1
We believe that the bug you reported is fixed in the latest version of
python-mimeparse, 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 867...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated python-mimeparse 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: Tue, 17 Oct 2017 09:49:45 +0300
Source: python-mimeparse
Binary: python-mimeparse python3-mimeparse
Architecture: source
Version: 0.1.4-3.1
Distribution: unstable
Urgency: medium
Maintainer: Mathias Ertl
Changed-By: Adrian Bunk
Description:
python-mimeparse - Parse mime-types and quality parameters - python 2.x
python3-mimeparse - Parse mime-types and quality parameters - python 3.x
Closes: 867439
Changes:
python-mimeparse (0.1.4-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix the python3-mimeparse dependencies. (Closes: #867439)
Checksums-Sha1:
a8f0d603739b12e79d9032062b188d84d4f67bf7 2181 python-mimeparse_0.1.4-3.1.dsc
54cd71c3522853a97eaf63df3726369f39b5a253 2928
python-mimeparse_0.1.4-3.1.debian.tar.xz
Checksums-Sha256:
c1b7b03fc6abe18c9857622c8222acdf790a64a4aefe4af71e81736b985c346b 2181
python-mimeparse_0.1.4-3.1.dsc
62e2d0040c8daa02977c2a3cce6c6ee3c0348f75be0bdbc21d96a72766897411 2928
python-mimeparse_0.1.4-3.1.debian.tar.xz
Files:
12936b1af3798554725d3cad38fd5179 2181 python optional
python-mimeparse_0.1.4-3.1.dsc
950f475c12b85047eae15e6fb15a90f5 2928 python optional
python-mimeparse_0.1.4-3.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlnlqOUACgkQiNJCh6LY
mLEHgw/+Mqez7P7mrqCLvtT6g6Fvd3BwDoZpPSO1qWC53umkK/U4P7Pezd1U9ldD
fsYOAX/tA27FWS2KqOyIr5VrAs+/JZGEGldQ/TRAgktyKAK59+9wSa7nhx/fpecX
tfqDWRLMlQS3NBrk2PvdjnBbba63NIjMaE5mviNQNSbfJWtxea7wruSUtntn/L+A
K3uThw+ABnnZ04CchBcazUROHVVQrJiX0DB19VzFZoGoqkOep4NURzUtZoMwnH1+
RRTfCD0Nbnulseo/4y4jEr6u5beMf3L30WbMkN9NqX04LevTxh3EqXOeBMZqIvmz
gDgu4bKvfUue2FxBe5l5MRBg/2gD7FHntVq8oXKZBCu5unh56/LtsDnaY1X32D01
7X+ijd7OezfiZZ4z/HqRAxF/M6SxDb+xSBVG/O5a+IfCD9Jx89i+PF3F8UqhOtf6
Kr4CCm9w9pmO47P49DTnMoq7Hag2ym4bb/Re6LxwR4AIkiPEOjc+P5BJ5LEJPv1N
G7P53XWqS9G1z6cPTLovMugaLwZ1Hb/RHK5uJ6Lw+fsgsVRKNAaJGcuS+5xKG0V+
rLR6KZRu5xyRbj1iQXJeF8bXiWwYRA75kBuG67s1JQk428DN0YU+Yke6rd89Ip6g
svo2/s+Db5/h/lY9qHk9dxWZPVSgphsY9Q/rDEBVXLKhGegsilc=
=Unho
-END PGP SIGNATURE End Message ---
Bug#878852: marked as done (Remove postgresql-9.6 from testing)
Your message dated Thu, 19 Oct 2017 10:39:05 +0200 with message-id <4aea2171-f29f-bcfe-5aae-d2cf4b983...@debian.org> and subject line Re: Bug#878852: Remove postgresql-9.6 from testing has caused the Debian Bug report #878852, regarding Remove postgresql-9.6 from testing 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.) -- 878852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-9.6 Version: 9.6.5-1 Severity: serious postgresql-9.6 is being replaced by postgresql-10, it can already be removed from testing. There's a few dependencies that are updated in unstable, but have not transitioned yet: postgresql-mysql-fdw orafce postgresql-pllua Waiting for NEW processing: pgextwlist Fixed in experimental: repmgr Unfixed, but in the works: skytools3 Release team: For the unblocking the python3.6-as-default transition, please consider removing postgresql-9.6 pgextwlist repmgr skytools3 from testing, and speeding up the transition of postgresql-mysql-fdw orafce postgresql-pllua Thanks, Christoph --- End Message --- --- Begin Message --- On 10/17/2017 11:11 AM, Christoph Berg wrote: > Package: postgresql-9.6 > Version: 9.6.5-1 > Severity: serious > > postgresql-9.6 is being replaced by postgresql-10, it can already be > removed from testing. > Hi Christoph, Added a remove hint for pg96 and its rdeps. Cheers, Julien--- End Message ---
Bug#876828: postgresql-ocaml FTBFS with PostgreSQL 10
Control: retitle -1 postgresql-ocaml FTBFS with PostgreSQL rc versions Control: severity -1 normal Re: Adrian Bunk 2017-09-26 <150641643465.13114.8728573493110444680.reportbug@localhost> > Source: postgresql-ocaml > Version: 2.0.5-3 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/postgresql-ocaml.html > ... > /usr/bin/ocamlopt.opt unix.cmxa -I /usr/lib/ocaml/ocamlbuild > /usr/lib/ocaml/ocamlbuild/ocamlbuildlib.cmxa myocamlbuild.ml > /usr/lib/ocaml/ocamlbuild/ocamlbuild.cmx -o myocamlbuild > findlib: [WARNING] cannot read directory /usr/lib/ocaml/METAS: No such file > or directory > Failure: > Unable to find versions from line 'PostgreSQL 10rc1' (cmd: 'pg_config > --includedir --libdir --version'. postgresql-ocaml builds now that PostgreSQL 10.0 has been released. Still, this should be fixed so it doesn't fail again once PostgreSQL 11rc1 is uploaded next year... Christoph
Processed: Re: Bug#876828: postgresql-ocaml FTBFS with PostgreSQL 10
Processing control commands: > retitle -1 postgresql-ocaml FTBFS with PostgreSQL rc versions Bug #876828 [src:postgresql-ocaml] postgresql-ocaml FTBFS with PostgreSQL 10 Changed Bug title to 'postgresql-ocaml FTBFS with PostgreSQL rc versions' from 'postgresql-ocaml FTBFS with PostgreSQL 10'. > severity -1 normal Bug #876828 [src:postgresql-ocaml] postgresql-ocaml FTBFS with PostgreSQL rc versions Severity set to 'normal' from 'serious' -- 876828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#879088: babeltrace: package merge makes gdb, linux-perf etc. uninstallable
Processing control commands:
> retitle -1 Please make libbabeltrace-ctf{1,-dev} provides versioned
Bug #879088 [src:babeltrace] babeltrace: package merge makes gdb, linux-perf
etc. uninstallable
Changed Bug title to 'Please make libbabeltrace-ctf{1,-dev} provides versioned'
from 'babeltrace: package merge makes gdb, linux-perf etc. uninstallable'.
--
879088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#879088: babeltrace: package merge makes gdb, linux-perf etc. uninstallable
Control: retitle -1 Please make libbabeltrace-ctf{1,-dev} provides versioned
On Thu, Oct 19, 2017 at 08:28:46AM +0100, Simon McVittie wrote:
>...
> Please do one of these as soon as possible:
>...
None of these is required.
Making the libbabeltrace-ctf{1,-dev} provides versioned is all that is
required to fix the versioned (build) dependencies.
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
Bug#878402: [debian-mysql] Bug#878402: Bug#878402: Security fixes from the October 2017 CPU
On 18/10/17 20:46, Salvatore Bonaccorso wrote: > Hi lars, > > On Wed, Oct 18, 2017 at 03:51:26PM +0200, Lars Tangvald wrote: >> Hi, >> >> 5.5.58 packages for Debian 7 and 8 are built, and pass the test suite. >> Attached are debdiff files for Wheezy and Jessie (source is also pushed to >> https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git) >> As before, we unfortunately don't have a DD in our team that can sponsor the >> upload, so we need assistance with that. > > I will look into it for jessie-security then. > >> I'm not sure if the security team still handles Debian8, or if the lts team >> does now? > > Yes, Debian 8 Jessie is still yet handled by the security team. And I will take of Debian 7 (wheezy). Thanks for preparing the update! Cheers, Emilio
Processed: Correct the found version
Processing commands for cont...@bugs.debian.org: > notfound 879083 5.2.0-dfsg Bug #879083 [virtualbox] FTBFS virtualbox 5.2 There is no source info for the package 'virtualbox' at version '5.2.0-dfsg' with architecture '' Unable to make a source version for version '5.2.0-dfsg' No longer marked as found in versions 5.2.0-dfsg. > found 879083 5.2.0-dfsg-1~exp1 Bug #879083 [virtualbox] FTBFS virtualbox 5.2 There is no source info for the package 'virtualbox' at version '5.2.0-dfsg-1~exp1' with architecture '' Unable to make a source version for version '5.2.0-dfsg-1~exp1' Marked as found in versions 5.2.0-dfsg-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 879083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#879053: RM: pygoocanvas -- RoQA; unmaintained, obsolete
Processing commands for cont...@bugs.debian.org: > block 879053 with 785565 Bug #879053 [ftp.debian.org] RM: pygoocanvas -- RoQA; unmaintained, obsolete 879053 was blocked by: 785562 879053 was not blocking any bugs. Added blocking bug(s) of 879053: 785565 > thanks Stopping processing here. Please contact me if you need assistance. -- 879053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 878837 ldc Bug #878837 [sambamba] sambamba: FTBFS with ldc 1.4.0 Bug reassigned from package 'sambamba' to 'ldc'. No longer marked as found in versions sambamba/0.6.6-1. Ignoring request to alter fixed versions of bug #878837 to the same values previously set > forcemerge 879039 878837 Bug #879039 [ldc] Crash via "Assertion `decl->ir->irGlobal != NULL' failed" Bug #879039 [ldc] Crash via "Assertion `decl->ir->irGlobal != NULL' failed" Added tag(s) buster and sid. Bug #878837 [ldc] sambamba: FTBFS with ldc 1.4.0 Set Bug forwarded-to-address to 'https://github.com/ldc-developers/ldc/issues/2357'. Added indication that 878837 affects sambamba Marked as found in versions ldc/1:1.4.0-3. Merged 878837 879039 > affects 878837 src:sambamba Bug #878837 [ldc] sambamba: FTBFS with ldc 1.4.0 Bug #879039 [ldc] Crash via "Assertion `decl->ir->irGlobal != NULL' failed" Added indication that 878837 affects src:sambamba Added indication that 879039 affects src:sambamba > thanks Stopping processing here. Please contact me if you need assistance. -- 878837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878837 879039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878581: marked as done (pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory)
Your message dated Thu, 19 Oct 2017 09:38:12 +0200 with message-id <20171019073812.ogbdzlsxci62s...@msg.df7cb.de> and subject line Re: Bug#878581: pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory has caused the Debian Bug report #878581, regarding pglogical FTBFS: fatal error: pglogical_compat.h: No such file or directory 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.) -- 878581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878581 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pglogical Version: 2.0.1-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html ... debian/rules override_dh_auto_build make[1]: Entering directory '/build/1st/pglogical-2.0.1' pg_buildext build build-%v ### build 10 ### make[2]: Entering directory '/build/1st/pglogical-2.0.1/build-10' pglogical_apply.o pglogical_conflict.o pglogical_manager.o pglogical.o pglogical_node.o pglogical_relcache.o pglogical_repset.o pglogical_rpc.o pglogical_functions.o pglogical_queue.o pglogical_fe.o pglogical_worker.o pglogical_sync.o pglogical_sequences.o pglogical_executor.o pglogical_dependency.o pglogical_apply_heap.o pglogical_apply_spi.o pglogical_output_config.o pglogical_output_plugin.o pglogical_output_proto.o pglogical_proto_json.o pglogical_proto_native.o pglogical_monitoring.o /build/1st/pglogical-2.0.1/compat100/pglogical_compat.o sed 's/__PGLOGICAL_VERSION__/2.0.1/;s/__REQUIRES__//' /build/1st/pglogical-2.0.1/pglogical.control.in > /build/1st/pglogical-2.0.1/pglogical.control gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -Wmissing-format-attribute -Wformat-security -fno-strict-aliasing -fwrapv -fexcess-precision=standard -g -g -O2 -fdebug-prefix-map=/build/postgresql-10-Wvqwf1/postgresql-10-10.0=. -fstack-protector-strong -Wformat -Werror=format-security -fno-omit-frame-pointer -fPIC -fPIC -I/usr/include/postgresql -I -I. -I/build/1st/pglogical-2.0.1 -I/usr/include/postgresql/10/server -I/usr/include/postgresql/internal -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I/usr/include/libxml2 -I/usr/include/mit-krb5 -c -o pglogical_apply.o /build/1st/pglogical-2.0.1/pglogical_apply.c In file included from /build/1st/pglogical-2.0.1/pglogical_proto_native.h:20:0, from /build/1st/pglogical-2.0.1/pglogical_conflict.h:22, from /build/1st/pglogical-2.0.1/pglogical_apply.c:62: /build/1st/pglogical-2.0.1/pglogical_output_plugin.h:20:10: fatal error: pglogical_compat.h: No such file or directory #include "pglogical_compat.h" ^~~~ compilation terminated. : recipe for target 'pglogical_apply.o' failed make[2]: *** [pglogical_apply.o] Error 1 --- End Message --- --- Begin Message --- Version: 2.1.0-1 Re: Adrian Bunk 2017-10-14 <150800749854.6287.16219608579091251260.reportbug@localhost> > Source: pglogical > Version: 2.0.1-1 > Severity: serious > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical.html 2.1.0-1 looks good now. Christoph--- End Message ---
Bug#879088: babeltrace: package merge makes gdb, linux-perf etc. uninstallable
Source: babeltrace
Version: 1.5.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: debian-ker...@lists.debian.org
libbabeltrace1 (= 1.5.3-2) merges the contents of libbabletrace-ctf1 into
the libbabeltrace1 package. This makes packages like gdb uninstallable.
Similarly, libbabeltrace-dev having absorbed libbabeltrace-ctf-dev makes
the linux source package (the Linux kernel), and probably other important
packages like gdb, unbuildable.
Making the Linux kernel unbuildable is particularly undesirable, because
it has frequent security updates.
Please do one of these as soon as possible:
* revert this change; or
* introduce a transitional (empty) libbabeltrace-ctf1 in section oldlibs with
Depends: libbabeltrace1 (= ${binary:Version}) and a transitional
libbabeltrace-ctf-dev with Depends: libbabeltrace-dev (= ${binary:Version}),
then report bugs in anything that build-depends on libbabeltrace-ctf-dev
asking them to migrate to build-depending on libbabeltrace-dev.
The transitional packages can be removed when nothing (Build-)Depends
on them, but not before.
As https://tracker.debian.org/pkg/babeltrace says, babeltrace is currently
involved in a planned transition (to a new Python version), so this was
not a great time to be making disruptive changes to it. Please be careful
with this sort of packaging change.
Thanks,
smcv
Processed: Re: Bug#879043: dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’
Processing commands for cont...@bugs.debian.org: > reassign 879043 dahdi-source 1:2.11.1.0.20170917~dfsg-1 Bug #879043 [justin hallett ] dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’ Warning: Unknown package 'justin' Warning: Unknown package 'hallett' Warning: Unknown package '' Bug reassigned from package 'justin hallett ' to 'dahdi-source'. No longer marked as found in versions 1:2.11.1.0.20170917~dfsg-1. Ignoring request to alter fixed versions of bug #879043 to the same values previously set Bug #879043 [dahdi-source] dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’ Marked as found in versions dahdi-linux/1:2.11.1.0.20170917~dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 879043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879083: FTBFS virtualbox 5.2
Package: virtualbox Version: 5.2.0-dfsg Severity: serious Tag: experimental Hi, virtualbox currently FTBFS in experimental, see https://buildd.debian.org/status/fetch.php?pkg=virtualbox&arch=all&ver=5.2.0-dfsg-1%7Eexp1&stamp=1508354297&raw=0 Regards, Daniel
