Bug#823910: debian-policy: document Build-Depends-Arch/Build-Conflicts-Arch and when it's safe to use them
Control: tag -1 + patch Hi, On Wed, 13 Jul 2016 18:52:32 +0200 Lucas Nussbaum wrote: > There are now packages in the archive relying on Build-Depends-Arch > (the botch package, at least). src:botch maintainer here. There is also src:fltk1.1, src:fltk1.3, src:libpsl, src:ncbi-tools6 and src:stk. In the past, also src:mplayer used to use it but that was reverted with the upload of 2:1.3.0-1. Though I don't think that how many packages are using Build-Depends-Arch already should not be a measure whether the field should be documented in policy because right now packages using it are facing several disadvantages like missing wanna-build support. This currently makes using the field a bad choice for Debian package maintainers. > This does not seem to raise issues. Yes it does. I just made a source-only upload of src:botch which specifies Build-Depends, Build-Depends-Indep and Build-Depends-Arch. It declares a Build-Depends-Arch on libdose3-ocaml-dev which is currently uninstallable in Debian unstable. Since wanna-build doesn't support Build-Depends-Arch the source package is repeatedly queued for compilation but the compilation fails each and every time because the build dependencies cannot be satisfied. What should instead happen is, that wanna-build detects that the build dependencies are not satisfiable and puts src:botch into bd-uninstallable. Right now, the endless retries lead to an infinite FTBFS loop of src:botch on each and every architecture. This wastes buildd time and spams my inbox with FTBFS emails. > It's not supported in the version of sbuild in stable, but is supposed in the > sbuild branch used on buildds. With my sbuild maintainer hat on: sbuild in unstable and testing, as well as sbuild in jessie-backports does support Build-Depends-Arch and I have no intention of dropping support for it. pbuilder seems to support it since version 0.222 which is not part of Jessie either but just as sbuild is in unstable, testing and jessie-backports. Lintian supports it since 2.5.15 which is in jessie, testing and unstable. Dpkg supports it since 1.16.10 which is in wheezy (!!), jessie, testing and unstable. Dose3 supports it since 3.3 which is in jessie, testing and unstable. I also volunteered to implement Build-Depends-Arch support for wanna-build but Aurélien Jarno informed me in #debian-buildd that such patches would only be merged if Debian Policy were changed to allow Build-Depends-Arch. Now as Jakub Wilk has pointed out, footnote 55 to to §7.7 reads: | There is no Build-Depends-Arch; this role is essentially met with | Build-Depends. Anyone building the build-indep and binary-indep targets is | assumed to be building the whole package, and therefore installation of all | build dependencies is required. | | The autobuilders use dpkg-buildpackage -B, which calls build, not build-arch | since it does not yet know how to check for its existence, and binary-arch. | The purpose of the original split between Build-Depends and | Build-Depends-Indep was so that the autobuilders wouldn't need to install | extra packages needed only for the binary-indep targets. But without a | build-arch/build-indep split, this didn't work, since most of the work is | done in the build target, not in the binary target. But this information is outdated now. dpkg-buildpackage -B now calls build-arch and dpkg-buildpackage -A calls build-indep. Furthermore, the build-arch and build-indep targets are considered mandatory by policy §4.9. Instead, I'd like to make a case for inclusion of Build-Depends-Arch and Build-Conflicts-Arch here: - the fields add symmetry to the existing Build-Depends-Indep and Build-Conflicts-Indep fields - the mapping of Build-*-Indep to the build-indep target makes one expect there to also be a Build-*-Arch field - this mapping also makes the proposed fields logical and well fitted without surprised - it will avoid installing useless dependencies for architecture dependent builds - it allows separation of build dependencies needed for build-indep and build-arch builds from those that are needed for (for example) the clean target - it is already supported by much software in the archive, most importantly it is supported by package builders and installability testers Please find attached a patch that documents Build-Depends-Arch and Build-Conflicts-Arch. Thanks! cheers, josch From e917008ce295400781b8073bacb6e40162f99ce7 Mon Sep 17 00:00:00 2001 From: Johannes Schauer Date: Sun, 18 Sep 2016 09:09:12 +0200 Subject: [PATCH] Document Build-Depends-Arch and Build-Conflicts-Arch (closes: #823910) --- policy.sgml | 68 + 1 file changed, 32 insertions(+), 36 deletions(-) diff --git a/policy.sgml b/policy.sgml index 9cd182b..1b5ec35 100644 --- a/policy.sgml +++ b/policy.sgml @@ -505,8 +505,9 @@ must not require or recommend a package outside of main for compilation or execution
Bug#838181: usbmuxd: Please announce supported hardware using AppStream
Package: usbmuxd Version: 1.1.0-2 Severity: wishlist User: p...@hungry.com Usertags: appstream-modalias Hi. The usbmuxd package is one of the packages in the Debian archive that should be proposed for installation when a given hardware dongle is inserted or available. Thanks to the appstream system, this can now be announced in a way other tools can use and act on. I've written the isenkram system to ask the current user if hardware specific packages should be installed when a new dongle is installed or already present on a machine, and isenkram now uses appstream as one source for hardware to package mappings. You can read more about this on my blog, http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html >. Instructions on how to create the metadata XML file can be found in https://wiki.debian.org/AppStream/Guidelines >. It would be great if you could add an appstream metainfo file to the usbmuxd package, with content similar to this: [...] usb:v05ACp129[0-9A]d* If there are other hardware ids also supposed by the package, please add those too. :) -- Happy hacking Petter Reinholdtsen
Bug#812933: please package a newer version
We have integrated JSXC into FreedomBox. However, we are eagerly looking forward to using the newer version. Thank you for the package. -- Sunil signature.asc Description: OpenPGP digital signature
Bug#635748: [pgadmin3] Does not respect system background colors in "Object browser"
2016-09-17 20:30 GMT+02:00 Rimas Kudelis : > Hi, > > 2016-09-17 20:52, Guillaume Lelarge rašė: > > You're right on the issue. Unfortunately, there won't be any more > > pgadmin3 releases. The dev team is working on pgadmin4 right now, > > which is a complete rewrite of pgAdmin. A GA release should be > > available at the end of September if all goes according to plan. > > > > But still, thank you for your patch and your attention to this kind of > > details. They are important to us. I'd have been happy to apply it if > > there would be another release of pgadmin3. > > > > Yeah, I saw that pgadmin4 is on the way. However, perhaps it would make > sense to apply this at least as a Debian patch, since I doubt that > pgadmin4 will become available in official Debian or Ubuntu repositories > anytime soon. Or will it? > > No idea. I don't maintain the Debian package. -- Guillaume. http://blog.guillaume.lelarge.info http://www.dalibo.com
Bug#518218: po4a: [xml] Add support for translator credits
Hi, https://bugs.debian.org/518218 On Wed, Sep 14, 2016 at 10:34:23PM +0200, Martin Quinson wrote: > Hello Osamu, > > I'm doing some basic bug triage in po4a, and it seems that you have a > working patch for this bug. Could you please share it so that I can > add it to the package? I have found a good solution to this wishlist bug but that is not the patch to the po4a tool. So the solution is to add some "Howto" for the localization of the XML/SGML document via po4a :-) Due to the limitation of addendum feature as present in the po4a (see Message #10) and unstable nature of the application of the locale special patch files (see Message #10 and Message #18), I concluded that the best way to add arbitrary locale specific XML content via entity reference. This is implemented in maint-guide. Its main English XML file starts with: | | | |http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [ | %trans; | %common; | %version; |]> | | | | | | Josip Rodin joy...@debian.org < |contrib>original contents | Osamu Aoki os...@debian.org updated contents | |&othercredit; | HERE IS THE TRICK After normal po4a processing to get the translated text, say "fr", build script changes: | %trans; line with the following via sed: | %trans; The po/en.ent is following: | | | So nothing wild happens. The po/fr.ent is manually generated as the following: | | |Frédéric Dumontf |rederic.dum...@easynet.betraduction française |Mohammed Adnène Trojetteadn+...@diwi.orgtraduction française |David Prévotdavi |d...@tilapin.orgtraduction française |les membres de la liste debian-l10n- |frenchdebian-l10n-fre...@lists.debian.orgtr |aduction française |'> | | |http://fr.wikipedia.org/wiki/Autoconf";> |http://fr.wikipedia.org/wiki/GNU_Automake";> |http://fr.wikipedia.org/wiki/CMake";> |http://fr.wikipedia.org/wiki/C_(langage)"> |http://fr.wikipedia.org/wiki/C++";> |http://fr.wikipedia.org/wiki/Executable_and_Linkable_Format";> |http://fr.wikipedia.org/wiki/GNU_gettext";> |http://fr.wikipedia.org/wiki/Autotools";> |http://fr.wikipedia.org/wiki/Bibliothèque_logicielle";> |http://fr.wikipedia.org/wiki/GNU_Libtool";> |http://fr.wikipedia.org/wiki/UTF-8";> | | |http://wiki.debian.org/fr/HelpDebian";> | | | | As you can see here, the translator credit is added via entity file and also some URL references can be overriden by this approach. Please note, this approach does not require any changes to po4a nor rely on the addendum feature of po4a. If one wishes to migrate to the new gettext 0.19 as the po conversion tool for XML, this approach is usable. Of course, I normalize the XML file by extracting URL references and making them as a auto-generated entity file to get the 2nd part of this localization feature. See the actual code in: https://anonscm.debian.org/cgit/ddp/maint-guide.git/tree/ Regards, Osamu PS: The po4a data directory is in po/ instead of po4a/
Bug#838182: override: inform-mode:editors/optional
Package: ftp.debian.org Severity: normal The ‘inform-mode’ package does not conflict with any package in higher priorities. It also is useful to those who are not yet aware of the package and discover it. For both these reasons it should not be “Priority: extra”. Instead it should be “Priority: optional”. -- \ “I knew things were changing when my Fraternity Brothers threw | `\ a guy out of the house for mocking me because I'm gay.” | _o__) —postsecret.com, 2010-01-19 | Ben Finney signature.asc Description: PGP signature
Bug#838183: libjs-jsxc: Images and CSS files should be in the main package directory
Package: libjs-jsxc Version: 1.0.0~dfsg-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Maintainer, Currently, the files in libjs-jsxc package are split into two areas: /usr/share/javascript/jsxc and /usr/share/libjs-jsxc. This leads to problems: 1) /usr/share/javascript directory is served by javascript-common package under /javascript on the web server. Files placed in /usr/shared/javascript/jsxc are available by default, at least with Apache2, while the remaining files outside the directory are not available. This requires a simple page that is using this library to create symlinks into the /usr/share/libjs-jsxc directory and serve them instead of simply adding
Bug#792622: missing licenses in debian/copyright
Samuel Thibault, on Thu 02 Jun 2016 11:31:49 +0200, wrote: > It is really non-technical work, a matter of using the check-copyright > script Sorry, I meant licencecheck. Samuel
Bug#837340: May not have been systemd problem
Has been OK recently, after various Sid upgrades to KDE and Xorg.
Bug#838184: chdist: compare-bin-packages not always uses the latest versions
Package: devscripts Version: 2.16.7 Severity: important Dear Maintainer, using "chdist compare-bin-packages" I was quite surprised to learn not always the newest version of the respective DIST is taken into account. How to repeat: * Create two DISTs, for the sake of this example called "wheezy-plain" and "wheezy-security" # chdist create wheezy-plain # chdist create wheezy-security * Populate the respective sources.list as follows wheezy-plain: | deb http://ftp.de.debian.org/debian wheezy main contrib non-free | deb-src http://ftp.de.debian.org/debian wheezy main contrib non-free wheezy-security: | deb http://ftp.de.debian.org/debian wheezy main contrib non-free | deb-src http://ftp.de.debian.org/debian wheezy main contrib non-free | deb http://security.debian.org wheezy/updates main contrib non-free | deb-src http://security.debian.org wheezy/updates main contrib non-free * Update the DISTs # chdist apt-get wheezy-plain update # chdist apt-get wheezy-security update * Compare them # chdist compare-bin-packages wheezy-plain wheezy-security |& grep tcpreplay Background: The tcpreplay package was updated after the last wheezy point release. Expected output: | tcpreplay 3.4.3-2+wheezy1 3.4.3-2+wheezy2 ^ Actual output: | W: Package tcpreplay is already listed for wheezy-security. Not overriding. | tcpreplay 3.4.3-2+wheezy1 3.4.3-2+wheezy1 ^ Analysis: The additional warning message gives the right hint: If a binary package is seen several times, only the first occurence is taken into account. Even if any later has a higher version. Suggested fix: The patch attached implements the expected behaviour: If the second occurence has a higher version number, that one is used. If the version number is identical, also the warning is suppressed. Additionally, the patch contains a safeguard in case there there is no version number. Feel free to drop that. The compare_src_bin function probably needs a fix, too. I could however not trigger this. Background: I maintain local backports and forks of several packages in Debian. This needs a tool to notify about new versions in Debian that require according work. I moved from an ugly hand-written solution to something based on chdist and found regressions. Justification: Besides this is unexpected behaviour and does not match the output of apt-cache policy on both sides (after some parsing) ... Assuming more people do track Debian in a similar way, they will face the same problem: They might not learn about updates that are necessary on their site, perhaps leading to something between functionality loss, or a security issue not getting fixed. Please also fix this in a stable point release: The patch applies to jessie as well (with an offset). Christoph -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- Not present -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.20 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages devscripts depends on: ii dpkg-dev 1.18.10 ii libc62.23-5 ii perl 5.22.2-5 pn python3:any Versions of packages devscripts recommends: ii apt 1.3~rc4 pn at ii curl7.50.1-1 ii dctrl-tools 2.24-2 pn debian-keyring pn dput | dupload pn equivs ii fakeroot1.21-2 ii file1:5.28-4 ii gnupg 1.4.20-6 ii gnupg2 2.1.11-7 ii libdistro-info-perl 0.14 ii libencode-locale-perl 1.05-1 ii liblwp-protocol-https-perl 6.06-2 pn libsoap-lite-perl ii liburi-perl 1.71-1 ii libwww-perl 6.15-1 pn licensecheck ii lintian 2.5.47 ii man-db 2.7.5-1 ii patch 2.7.5-1 ii patchutils 0.3.4-1 ii python3-debian 0.1.29 ii python3-magic 1:5.28-4 ii sensible-utils 0.0.9 ii strace 4.12-3 ii unzip 6.0-20 ii wdiff 1.2.2-1+b1 ii wget1.18-2+b1 ii xz-utils5.1.1alpha+20120614-2.1 Versions of packages devscripts suggests: pn bsd-mailx | mailx ii build-essential 12.2 pn cvs-buildpackage pn devscripts-el ii diffoscope 60 pn dose-extra pn gnuplot ii gpgv
Bug#731016: Software solution
Jiri brought to my attention that that asus provide firmware upgrade which solved his problem. I found at https://www.asus.com/Optical-Drives-Storage/AN300_External_HDD/HelpDesk _Download/ utilities which correspond my HDD, i.e.: 1. firmware upgrade utility 2. virtual cd removal utility I succeeded to run them under windows (wine didn't helped...). And ... it worked! After the firmware upgrade the block device was generated, though the partition was not recognized. I used the second utility and removed the virtual cd and everything is getting mounted in linux! Ido
Bug#792622: missing licenses in debian/copyright
Samuel Thibault writes: > It is really non-technical work, a matter of using the check-copyright > script to check that the various licences are referenced in > debian/copyright (there is no hard need to reference files exactly, > the only minimal need is knowing which licences end up in the gnumach > binary). What check-copyright script do you mean? https://packages.debian.org/search?searchon=contents&keywords=check-copyright&mode=filename&suite=unstable&arch=any shows only these: * /usr/share/gnulib/check-copyright in gnulib 20140202+stable-2. It only checks the licenses of gnulib modules, which gnumach does not use. The latest version is online at http://git.savannah.gnu.org/cgit/gnulib.git/plain/check-copyright and has no functional differences. * /usr/share/gocode/src/github.com/syncthing/syncthing/script/check-copyright.go in golang-github-syncthing-syncthing-dev 0.14.4+dfsg1-1. It ignores licenses and only checks for missing copyright notices.
Bug#829520: RFS: mbpfan/1.9.1-1 ITP
On 08/31, Herminio Hernandez, Jr. wrote: Mentors, I am trying to convert my package using git. I am running into the lintian error gbp:error: Can't determine upstream version from changelog Mentors, I am trying to convert my package using git. I am running into the lintian error gbp:error: Can't determine upstream version from changelog Mentors, I am trying to convert my package using git. I am running into the lintian error gbp:error: Can't determine upstream version from changelog Mentors, I am trying to convert my package using git. I am running into the lintian error gbp:error: Can't determine upstream version from changelog Mentors, I am trying to convert my package using git. I am running into the lintian error gbp:error: Can't determine upstream version from changelog Mentors, I am trying to convert my package using git. I am running into the lintian error W: mbpfan source: source-nmu-has-incorrect-version-number 1.9.1-1 Based on what I read here: https://lintian.debian.org/tags/source-nmu-has-incorrect-version-number.html I tried to change the version to -0.1 in the changelog. Now I am getting this error gbp:error: upstream/0 is not a valid treeish If can point into the right direction I would appreciate it. Thanks! Herminio Aug 31, 2016 at 2:43 PM, Sean Whitton > wrote: > > > Dear Herminio, > > > > [please CC the RFS so that your e-mail gets recorded and others can > > provide feedback as well as me -- use reply-to-all] > > > > On Tue, Aug 30, 2016 at 10:23:09PM -0700, Herminio Hernandez, Jr. wrote: > > > I have combined the patches using combinediff. I know you want me to > > convert to > > > git. Can you recommend good documentation to convert my package? Thanks! > > > > One easy way is to do this: > > > > apt-get install git-buildpackage > > gbp import-dsc mbpfan_1.9.1-1.dsc > > > > -- > > Sean Whitton > > signature.asc Description: PGP signature
Bug#838185: chdist: Mute some Perl warnings
Package: devscripts
Version: 2.16.7
Severity: minor
Dear Maintainer,
the chdist program emits several "Use of uninitialized value"
warnings. Please consider the patch attached to mute those I triggered
easily and pretty often.
Don't be concerned about the patch offsets, this is supposed to be on
top of the other patch I just sent.
Christoph
-- Package-specific info:
--- /etc/devscripts.conf ---
--- ~/.devscripts ---
Not present
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.20 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages devscripts depends on:
ii dpkg-dev 1.18.10
ii libc62.23-5
ii perl 5.22.2-5
pn python3:any
Versions of packages devscripts recommends:
ii apt 1.3~rc4
pn at
ii curl7.50.1-1
ii dctrl-tools 2.24-2
pn debian-keyring
pn dput | dupload
pn equivs
ii fakeroot1.21-2
ii file1:5.28-4
ii gnupg 1.4.20-6
ii gnupg2 2.1.11-7
ii libdistro-info-perl 0.14
ii libencode-locale-perl 1.05-1
ii liblwp-protocol-https-perl 6.06-2
pn libsoap-lite-perl
ii liburi-perl 1.71-1
ii libwww-perl 6.15-1
pn licensecheck
ii lintian 2.5.47
ii man-db 2.7.5-1
ii patch 2.7.5-1
ii patchutils 0.3.4-1
ii python3-debian 0.1.29
ii python3-magic 1:5.28-4
ii sensible-utils 0.0.9
ii strace 4.12-3
ii unzip 6.0-20
ii wdiff 1.2.2-1+b1
ii wget1.18-2+b1
ii xz-utils5.1.1alpha+20120614-2.1
Versions of packages devscripts suggests:
pn bsd-mailx | mailx
ii build-essential 12.2
pn cvs-buildpackage
pn devscripts-el
ii diffoscope 60
pn dose-extra
pn gnuplot
ii gpgv 1.4.20-6
pn libauthen-sasl-perl
ii libfile-desktopentry-perl0.22-1
ii libnet-smtp-ssl-perl 1.03-1
pn libterm-size-perl
ii libtimedate-perl 2.3000-2
pn libyaml-syck-perl
ii mozilla-devscripts 0.47
ii mutt 1.7.0-1
ii openssh-client [ssh-client] 1:7.3p1-1
pn reprotest
pn svn-buildpackage
ii w3m 0.5.3-29
-- no debconf information
--- /usr/bin/chdist
+++ /tmp/chdist
@@ -500,7 +507,7 @@
# Escaped versions
my @esc_vers = @versions;
foreach my $vers (@esc_vers) {
-$vers =~ s|\+|\\\+|;
+$vers =~ s|\+|\\\+| if (defined ($vers));
}
# Do compare
@@ -585,7 +592,7 @@
foreach my $package (@all_packages) {
my $line = "$package ";
my $status = "";
- my $details;
+ my $details = "";
foreach my $type (@comp_types) {
if ( $packages{$type}{$package} ) {
signature.asc
Description: Digital signature
Bug#838186: [handbrake] No audio in output file
Package: handbrake Version: 0.10.5+ds1-2+b1 Severity: important --- Please enter the report below this line. --- Dear maintainers: Transcoding a video using HandBrake renders an audioless file. Please find partial log output below (tried deleting config file and using a default - normal- profile to no avail). Regards, Antonio [AVAudioResampleContext @ 0x7f3e6c00f640] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] hb_audio_resample_update: avresample_open() failed (Argumento inválido) [09:11:25] Last error repeated 36 times [09:11:25] hb_audio_resample_update: avresample_open() failed (Argumento inválido) [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [AVAudioResampleContext @ 0x7f3e6c008900] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [AVAudioResampleContext @ 0x7f3e6c008a60] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [AVAudioResampleContext @ 0x7f3e6c008dc0] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [AVAudioResampleContext @ 0x7f3e6c009120] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [AVAudioResampleContext @ 0x7f3e6c009200] Invalid input channel layout: 0 [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed [09:11:25] decavcodec: hb_audio_resample_update() failed --- System information. --- Architecture: amd64 Kernel: Linux 4.6.0-1-amd64 Debian Release: stretch/sid 900 testing ftp.pt.debian.org 500 xenial ppa.launchpad.net 500 wilyppa.launchpad.net 500 unstableftp.pt.debian.org 500 trusty ppa.launchpad.net 500 stable update.devolo.com 500 stable kxstudio.linuxaudio.org 500 stable dl.google.com 500 sid linux.dropbox.com 500 lucid ppa.launchpad.net --- Package information. --- Depends (Version) | Installed ==-+- libass5(>= 0.13.0) | 0.13.2-1 libavcodec57 (>= 7:3.1.3) | OR libavcodec-extra57(>= 7:3.1.3) | libavformat57 (>= 7:3.1.3) | libavresample3(>= 7:3.1.3) | libavutil55 (>= 7:3.1.3) | libbluray1(>= 1:0.2.2) | libc6(>= 2.14) | libcairo2 (>= 1.10.0) | libdbus-glib-1-2 (>= 0.78) | libdvdnav4 (>= 4.9.0~~gita5c13254) | libdvdread4 (>= 4.1.3) | libgdk-pixbuf2.0-0 (>= 2.22.0) | libglib2.0-0 (>= 2.37.3) | libgstreamer-plugins-base1.0-0 (>= 1.0.0) | libgstreamer1.0-0 (>= 1.4.0) | libgtk-3-0 (>= 3.9.12) | libgudev-1.0-0(>= 146) | libnotify4 (>= 0.7.3) | libpango-1.0-0 (>= 1.14.0) | libsamplerate0 (>= 0.1.7) | libswscale4 (>= 7:3.1.3) | libtheora0(>= 1.0) | libvorbis0a (>= 1.1.2) | libvorbisenc2 (>= 1.1.2) | libx264-148| libx265-87(>= 2.0) | libx265-87(<< 2.1) | Recommends (Version) | Installed ==-+-=== gstreamer1.0-libav
Bug#805370: Any answer from mpage upstream regarding the copyright situation?
Hi Eriberto, in [1] you wrote that you will contact mpage upstream regarding the copyright situation. Did you ever receive a reply? Thanks Adrian [1] https://lists.debian.org/debian-legal/2015/10/msg00057.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
Bug#838187: Zooming out crashes xli 1.17.0+20061110-4+b2
Package: xli Version: 1.17.0+20061110-4+b2 Severity: important Hi I have stumbled upon another bug in xli. Actually quite similar to 274310 that I reported in 2004, and that was fixed later that year. I originally reproduced this with an image I cannot share, but I found out that I can reproduce the same crash using the following command: echo -e "P6\n1 1\n255\n\0377\0377\0377" | pnmscale -width=147594 -height=2 > test.pnm valgrind ./xli -dumpcore ./test.pnm When the window pops up, focus it and press < to zoom out. The valgrind log looks like this: ./test.pnm is a 147594x2 Raw PPM image with 256 levels Default gamma for ITRUE image is 1.00 ==10372== Conditional jump or move depends on uninitialised value(s) ==10372==at 0x8054885: processImage (misc.c:262) ==10372==by 0x804B596: main (xli.c:350) ==10372== Building XImage...done Have adjusted image from 1.00 to display gamma of 2.20 Image decoder scaling is now 1 ./test.pnm is a 147594x2 Raw PPM image with 256 levels Default gamma for ITRUE image is 1.00 Zooming image by 50%...73797 1 ==10372== ==10372== Process terminating with default action of signal 8 (SIGFPE) ==10372== Integer divide by zero at address 0x62B6DDFA ==10372==at 0x806A9E3: buildIndex (zoom.c:25) ==10372==by 0x806AC36: zoom (zoom.c:87) ==10372==by 0x8054903: processImage (misc.c:159) ==10372==by 0x804B596: main (xli.c:350) The first complaint about uninitialized data actually shows up before trying to zoom out, so that looks like a second issue. Looking into the source code and my dear old friend buildIndex() I can quickly determine what the cause is, *rwidth == 1, which causes a division by zero in the loop. *rwidth = width * zoom / 100; index= (unsigned int *)lmalloc(sizeof(unsigned int) * *rwidth); for (a = 0; a < *rwidth; a++) *(index + a) = a * (width - 1) / (*rwidth - 1); I'm not sure how you guys want to fix this though. :) / Sebastian
Bug#838188: ocaml: temporary preprocessed file paths make the ocaml compiler produce unreproducible output
Source: ocaml
Version: 4.02.3-7.1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
Hi,
currently, ocaml embeds the file paths of temporary files that a
preprocessor created into the debug output. This makes several source
packages in Debian unreproducible. To see the effect, look for example
at this diffoscope output of src:botch:
│ ├── data.tar.xz
│ │ ├── data.tar
│ │ │ ├──
./usr/lib/debug/.build-id/03/28382a2670552f3318cc61bdebc13bbeef8f2f.debug
│ │ │ │ ├── readelf --wide --symbols {}
│ │ │ │ │ @@ -56,15 +56,15 @@
│ │ │ │ │ 52: 00830838 0 NOTYPE LOCAL DEFAULT 25
caml_startup__9
│ │ │ │ │ 53: 00830868 0 NOTYPE LOCAL DEFAULT 25
caml_startup__10
│ │ │ │ │ 54: 00830898 0 NOTYPE LOCAL DEFAULT 25
caml_startup__11
│ │ │ │ │ 55: 008308c8 0 NOTYPE LOCAL DEFAULT 25
caml_startup__12
│ │ │ │ │ 56: 0 FILELOCAL DEFAULT ABS
std_exit.ml
│ │ │ │ │ 57: 005c4430 0 NOTYPE LOCAL DEFAULT 15
caml_negf_mask
│ │ │ │ │ 58: 005c4440 0 NOTYPE LOCAL DEFAULT 15
caml_absf_mask
│ │ │ │ │ -59: 0 FILELOCAL DEFAULT ABS
/tmp/ocamlpp29daa7
│ │ │ │ │ +59: 0 FILELOCAL DEFAULT ABS
/tmp/ocamlpp4dfb7e
│ │ │ │ │ 60: 005c4450 0 NOTYPE LOCAL DEFAULT 15
caml_negf_mask
│ │ │ │ │ 61: 005c4460 0 NOTYPE LOCAL DEFAULT 15
caml_absf_mask
│ │ │ │ │ 62: 00836558 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__30
│ │ │ │ │ 63: 00836570 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__31
│ │ │ │ │ 64: 00836588 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__32
│ │ │ │ │ 65: 008365c0 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__2
│ │ │ │ │ 66: 00836668 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__5
│ │ │ │ │ @@ -87,15 +87,15 @@
│ │ │ │ │ 83: 008367e0 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__23
│ │ │ │ │ 84: 008367f8 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__24
│ │ │ │ │ 85: 00836810 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__25
│ │ │ │ │ 86: 00836820 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__26
│ │ │ │ │ 87: 00836868 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__27
│ │ │ │ │ 88: 00836880 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__28
│ │ │ │ │ 89: 008368c8 0 NOTYPE LOCAL DEFAULT 25
camlAnnotate$2dstrong__29
│ │ │ │ │ -90: 0 FILELOCAL DEFAULT ABS
/tmp/ocamlpp21639f
│ │ │ │ │ +90: 0 FILELOCAL DEFAULT ABS
/tmp/ocamlppfd0623
│ │ │ │ │ 91: 005c4470 0 NOTYPE LOCAL DEFAULT 15
caml_negf_mask
│ │ │ │ │ 92: 005c4480 0 NOTYPE LOCAL DEFAULT 15
caml_absf_mask
│ │ │ │ │ 93: 00836fc0 0 NOTYPE LOCAL DEFAULT 25
camlSrcGraphExtras__43
│ │ │ │ │ 94: 00836fd8 0 NOTYPE LOCAL DEFAULT 25
camlSrcGraphExtras__44
│ │ │ │ │ 95: 00836ff0 0 NOTYPE LOCAL DEFAULT 25
camlSrcGraphExtras__45
│ │ │ │ │ 96: 00837008 0 NOTYPE LOCAL DEFAULT 25
camlSrcGraphExtras__46
│ │ │ │ │ 97: 00837028 0 NOTYPE LOCAL DEFAULT 25
camlSrcGraphExtras__9
I see two ways to fix this problem.
- instead of choosing a random temporary file name for the preprocessor
output, choose a stable file name
- do not include the path to the temporary file created by the
preprocessor in the debug information
I like the latter option because knowing this path is useless anyway
because the file is only temporary. Unfortunately, I was unable to
figure out a good way to implement this solution.
So instead, I implemented a solution that calculates the path of the
temporary files from the MD5 sum of the preprocessor name and the input
file path. The idea is, that running the same preprocessor on the same
file path should produce the same output and thus choosing the same
filename should not pose any problem. I chose to calculate a hash
instead of using the bare string values because the file paths contain
characters like the slash which must not appear in file names and also
because it allows a stable temporary filename length no matter the
length of the input path.
Here is the patch:
--- a/driver/pparse.ml
+++ b/driver/pparse.ml
@@ -19,9 +19,17 @@ type error =
exception Error of error
Bug#838189: The name "tox" is fully misleading and should be better "python-tox"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Source: tox Severity: normal I set this bug to normal instead of wishlist as it currently blocks somehow packaging of other packages. The name "tox" of this package is extremely misleading as normal use associate [0] with this name. More over, it is somewhat python specific so it is better named python-tox. While it might be possible to work around the packaging block, that would produce a complete mess. So I ask you to please rename the package (back) to python-tox. I believe that this will take some time so please don't defere it to long. [0] https://en.wikipedia.org/wiki/Tox_%28protocol%29 - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.7 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGcBAEBCgAGBQJX3lazAAoJEKZ8CrGAGfas5EcL/04KAH9eu1AKZHQZAA+Db8d9 8V5IafDkU4od/VNuGIzNGcMVbToGSbFHy1Ggn/AqpuStY/iBhEUDqPDhR6w800Kp Hqwn7PHgRUR41SDv6om0QUasu7T3Py86qrk2h5jSkQoeQWrzvoBCjhRSHVTmZrjH 90hWNrMNM+bvpsth8+17f2KCpaWb9/ACi/4VQh5CXRq4FtmjW8og6e4CkloRrhsp 8KsL1tNDpMoPm7lLtabfC/S+afHnL53m/n/cy+jsArVKlUMy7ENfKvZlxEYQOej7 f0FeJZHvuPbTBoBY6jSYmSc9iXrWC8pknhkxEjUy9+gJB/by+3PXwJLQNKkB2T+Y oM9Dbs6Me2zV/AfrguunDcmbv/I0Rcmnp1nvchUZdg+voTCbnD7TUpFURj7WeJxT 5OOn5zzFhf1bF+JPi9Cx3Eg1ARmfUBb9GHnKaH8FXcRI6cOaPqorYrP315gzDPUJ xO8e4L34XfZB7AcIxXtkFJFlrJ9RYOqOE5DU5J7Vfg== =/BLl -END PGP SIGNATURE-
Bug#838190: mysql-server-5.5: Troubles starting MySQL during and after security update
Package: mysql-server-5.5
Version: 5.5.52-0+deb8u1
Severity: normal
Dear Maintainer,
The problem didn't happen on all systems and I'm not sure what exactly is going
wrong. During a apt-get upgrade run MySQL failed to upgrade..
Some weird stuff:
syslog:
mysqld_safe[22411]: 160918 10:22:05 [Note] /usr/sbin/mysqld (mysqld
5.5.52-0+deb7u1-log) starting as process 22431 ...
mysqld_safe[22411]: 160918 10:22:05 [Note] /usr/sbin/mysqld (mysqld
5.5.52-0+deb7u1-log) starting as process 22445 ...
Why is it trying to start twice as two different processes?
mysqld_safe[22580]: ERROR: 1064 You have an error in your SQL syntax; check
the manual that corresponds to your MySQL server version for the right syntax
to use near 'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER
SET utf8 NOT ' at line 1
mysqld_safe[22580]: 160918 10:22:08 [ERROR] Aborting
mysqld_safe[13729]: ERROR: 1050 Table 'plugin' already exists
I now ran MySQL manually by executing mysqld but I'd like to solve this
properly.
Gr,
Olaf
-- System Information:
Debian Release: 8.6
APT prefers stable
APT policy: (500, 'stable'), (1, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mysql-server-5.5 depends on:
ii adduser3.113+nmu3
ii debconf [debconf-2.0] 1.5.56
ii initscripts2.88dsf-59
ii libc6 2.19-18+deb8u6
ii libdbi-perl1.631-3+b1
ii libgcc11:4.9.2-10
ii libstdc++6 4.9.2-10
ii lsb-base 4.1+Debian13+nmu1
ii mysql-client-5.5 5.5.52-0+deb8u1
ii mysql-common 5.5.52-0+deb8u1
ii mysql-server-core-5.5 5.5.52-0+deb8u1
ii passwd 1:4.2-3+deb8u1
ii perl 5.20.2-3+deb8u6
ii psmisc 22.21-2
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages mysql-server-5.5 recommends:
ii libhtml-template-perl 2.95-1
Versions of packages mysql-server-5.5 suggests:
ii heirloom-mailx [mailx] 12.5-4
pn tinyca
-- debconf information:
mysql-server/no_upgrade_when_using_ndb:
mysql-server-5.5/nis_warning:
mysql-server-5.5/postrm_remove_databases: false
mysql-server-5.5/start_on_boot: true
mysql-server-5.5/really_downgrade: false
mysql-server/password_mismatch:
mysql-server/error_setting_password:
Bug#838060: po.m4: warning: AM_PROG_MKDIR_P: this macro is deprecated, and will soon be removed.
Thank you both :-)
Bug#838191: systemd user units do not honor resource limits set in /etc/security/limits.conf
Package: systemd Version: 231-6 Severity: normal Dear Maintainer, I wanted to set resource limits from a systemd _user_ unit, with: LimitRTPRIO=96 LimitMEMLOCK=infinity Raising resource limits with ulimit(3) or setrlimit(2) is a privileged operation, however users are normally allowed to set resource limits within the boundaries set by hard limits in /etc/security/limits.conf. Currently this practice does not work with systemd user units. For example, I have these settings in limits.conf: --- * hard rtprio 96 * hard memlockunlimited --- The output of running prlimit from a shell is as follows: --- RESOURCE DESCRIPTION SOFT HARD UNITS ... MEMLOCKmax locked-in-memory address space 65536 unlimited bytes ... RTPRIO max real-time priority 096 ... --- And users are able to change the soft limit with ulimit from the shell. However "systemd --user" seems to ignore the hard limits, see the unit below (copied to /usr/lib/systemd/user/prlimit_defaults.service): --- [Unit] Description=Test setting limits [Service] ExecStart=/usr/bin/prlimit --- Starting the unit with "systemctl --user start prlimit_defaults.service" results in this output: --- Started Test setting limits. RESOURCE DESCRIPTION SOFT HARD UNITS ... MEMLOCKmax locked-in-memory address space 65536 65536 bytes ... RTPRIO max real-time priority 0 0 ... --- The limits are ignored and of course raising them does not work either: --- [Unit] Description=Test setting limits [Service] ExecStart=/usr/bin/prlimit # These work fine when running the unit as a system service, # but they don't have effect when using "systemctl --user" LimitRTPRIO=96 LimitMEMLOCK=infinity --- After a precious suggestion by Mantas Mikulėnas (grawity in #debian-systemd) I verified that this is happening because /etc/pam.d/systemd-user does not load pam_limits.so. The following change fixes the issue: --- --- /etc/pam.d/systemd-user.orig2016-09-17 17:40:19.787522246 +0200 +++ /etc/pam.d/systemd-user 2016-09-17 15:13:17.035405264 +0200 @@ -7,5 +7,6 @@ session required pam_selinux.so close session required pam_selinux.so nottys open session required pam_loginuid.so +session required pam_limits.so @include common-session-noninteractive session optional pam_systemd.so --- After adding pam_limits and the settings in limits.conf, the units from above have the expected behavior. The mechanism explained in systemd-user.conf(5) to set default limits for all user units also works now; before it didn't. For instance these values in /etc/systemd/user.conf were completely ignored without the changes from above: --- DefaultLimitMEMLOCK=infinity DefaultLimitRTPRIO=96 --- I guess that too was because user.conf limits are meant to be within some system-wide limits (see the P.S. below). I can send a patch for /etc/pam.d/systemd-user against the systemd Debian package to address the issue, but I have a doubt: can this also be considered a bug in the upstream src/login/systemd-user.m4? If so I will send a standalone patch which applies _before_ debian/Adjust-systemd-user-pam-config-file-for-Debian.patch this way it will be easier to have it merged upstream. Thanks, Antonio P.S. After I wrote the report above I found out that another way to solve the problem is to set system-wide limits in /etc/systemd/system.conf (or /lib/systemd/system.conf.d/nn_SOMETHING.conf), e.g.: [Manager] DefaultLimitMEMLOCK=65536:infinity DefaultLimitRTPRIO=0:96 and these limits will also apply to "systemd --user" (and so /etc/systemd/user.conf will work too within these limits); maybe this is even the "official" systemd way to solve the problem, but it does not give the ability to set per-user or per-group limits, so I still think that the report above is valid. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable A
Bug#838193: Improved Multi-Arch support for python.
Package: python3-minimal
Version: 3.5.1-4
A package marked "Multi-Arch: same" that distributes python modules and
makes use of dh-python will lead to the following crash when multiple
architectures are installed together:
Setting up gir1.2-ibus-1.0:i386 (1.5.11-1) ...
dpkg-query: error: --listfiles needs a valid package name but
'gir1.2-ibus-1.0' is not: ambiguous package name 'gir1.2-ibus-1.0' with
more than one installed instance
Use --help for help about querying packages.
Traceback (most recent call last):
File "/usr/bin/py3compile", line 290, in
main()
File "/usr/bin/py3compile", line 270, in main
options.force, options.optimize, e_patterns)
File "/usr/bin/py3compile", line 154, in compile
for fn, versions_to_compile in filter_files(files, e_patterns,
versions):
File "/usr/bin/py3compile", line 106, in filter_files
for fn in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
for fn in files:
File "/usr/share/python3/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of gir1.2-ibus-1.0
dpkg: error processing package gir1.2-ibus-1.0:i386 (--configure):
subprocess installed post-installation script returned error exit status 1
This is a result of invoking py3compile or py3clean on an ambiguously
specified package. dh-python can and should disambiguate the package by
specifying an architecture and I am submitting a patch to that effect.
However, I believe the correct behavior for py3clean and py3compile would
be to clean or compile only the packages uniquely provided by a given
instance of a package. This would ensure the correct behavior for python
modules that are distributed exclusively for a specific architecture, as
well as modules that are common to all architectures. I've attached a
patch that implements this behavior.
Additionally, in the case of an ambiguous package specification, this patch
will turn what is currently a severe failure requiring a human to repair
into
a minor redundancy that will go away over time as packages are built
against a newer dh-python that does not provide ambiguous package
specifications to
py3clean and py3compile.
This would solve or at least help alleviate the following bugs:
bug #770265
bug #810551
bug #812228
Please apply this patch.
=== modified file 'debian/changelog'
--- debian/changelog 2016-06-03 14:42:29 +
+++ debian/changelog 2016-09-18 07:15:37 +
@@ -1,3 +1,10 @@
+python3-defaults (3.5.1-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Compiling/cleaning support for Multi-Arch:same.
+
+ -- Joe Crayne Sun, 18 Sep 2016 03:14:34 -0400
+
python3-defaults (3.5.1-4) unstable; urgency=medium
* Bump standards version.
=== modified file 'debpython/files.py'
--- debpython/files.py 2013-07-14 12:09:52 +
+++ debpython/files.py 2016-09-18 06:53:34 +
@@ -44,7 +44,11 @@
def from_package(package_name, extensions=('.py',)):
-"""Generate *.py file names available in given package."""
+"""Generate *.py file names available in given package.
+
+This function is deprecated because it is not Multi-Arch aware.
+Use uniquely_from_package() instead.
+"""
extensions = tuple(extensions) # .endswith doesn't like list
process = Popen("/usr/bin/dpkg -L %s" % package_name,
shell=True, stdout=PIPE)
@@ -56,6 +60,56 @@
if line.endswith(extensions):
yield line
+def uniquely_from_package(package_name, extensions=('.py',)):
+"""Generate *.py file names uniquely provided by a given package.
+
+The given package should specify an architecture using dpkg's pkg:arch
+syntax. If other instances of the package are installed, the contents
+of those instances will be excluded, most likely causing the resulting
+list to be empty.
+
+In the case that the package is not uniquely specified due to the
+architecture being omited, an architecture will be chosen arbitrarily
+and no files will be excluded on non-uniqueness grounds. This behavior
+makes this function safe to call in the "don't care" scenario when all
+architecture varients provide the same *.py files and we don't care
+which one is selected.
+"""
+pkg,*arch = package_name.split(':')
+process = Popen("dpkg-query -f'${Architecture}\n' -W %s" % pkg,
+shell=True,stdout=PIPE)
+stdout, stderr = process.communicate()
+if process.returncode != 0:
+raise Exception("cannot determine installed architectures for %s" % pkg)
+stdout = str(stdout, 'utf-8')
+other_archs = list()
+for x in stdout.splitlines():
+if not x in arch:
+other_archs.append(x)
+# Now we ensure:
+# 1. package_name specifies a package and an architecture.
+# 2. other_archs is a list of architecture instances to exclude from our output.
+package_name, other_archs = pk
Bug#838192: zfs-dkms: ZFS fails to build when version <> spl version
Package: zfs-dkms Version: 0.6.5.7-2 Severity: grave Justification: renders package unusable Dear Maintainer, spl was recently updated to version 0.6.5.8 zfs-dkms required to have the same version number than the spl package. When there is a higher version istalled, the zfs-package does not build. Thanks -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.59 ii dkms 2.2.1.0+git20160527-1 ii lsb-release9.20160629 ii spl-dkms 0.6.5.8-1 Versions of packages zfs-dkms recommends: ii zfs-zed 0.6.5.7-2 ii zfsutils-linux 0.6.5.7-2 zfs-dkms suggests no packages. -- debconf information: zfs-dkms/stop-build-for-unknown-kernel: true zfs-dkms/stop-build-for-32bit-kernel: true * zfs-dkms/note-incompatible-licenses:
Bug#835985: nmh: please make the build reproducible
[re-adding 835...@bugs.debian.org to cc] Alexander Zangerl wrote: > done, upload eta 15 min. would have been a bit easier if the patch > hadn't contained Extra Stuff(tm). Eek, no idea what happened there. You should have asked me to re-do it for you. Sorry about that. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#802587: at least, warn about absence of libgtest library package
> There exists no corresponding library binary package libgtest1. Correct and for a good reason you mentioned below. > This is in accordance with a recommendation of the upstream authors, [...] > but it is in conflict with the well-established standard way > of how libraries are distributed in Debian. This is incorrect. Header-only libraries are present in the Debian archive, such as libboost-dev or libeigen3-dev. A -dev package does not automatically have an accompanying shlib package. > Somehow I discovered that there is a libgtest-dev in Debian, and a > FindGTest in cmake. So I installed libgtest-dev on my system, removed > ThirdParty/gtest from my project, changed CMakeList.txt files, tried > to rebuild the project, saw that FindGTest did not find the library, > investigated the problem, and finally discovered that libgtest-dev > is deceptive in that it does not pull in the binary without which > it is useless. This has nothing to do with libgtest-dev being deceptive, but with you failing to understand how modern integration of GTest with CMake is supposed to happen in accordance with upstream recommendations. Modern integration uses ExternalProject_Add to fetch the gtest source, build its byproducts somewhere in the build-tree and either point FindGTest to this location or set the GTEST_* variables manually. You were right to strip ThirdParty/gtest from the source tree but did not modify the CMake list files appropriately. If upstream uses ExternalProject_Add (which they should), then all you have to do is modify it to use /usr/src/gtest instead of the vendored or downloaded version. Otherwise, you'd have to investigate where the gtest source are utilized in the CMake list files and modify the path there. This bug should be tagged as won't fix. Ghis
Bug#812228: Multi-Arch support for dh-python
I've attached a patch that will make dh-python Multi-Arch aware by making
use of the environment variable DPKG_MAINTSCRIPT_ARCH which is provided in
the environment by dpkg.
Specifying the architecture this way will prevent a failure that requires
the human administrator to fix. With version 3.5.1-4 of python3-minimal it
will unfortunately redundantly compile packages when multiple architecture
variants provide the same python modules. However, I've submitted a patch
to python3-minimal that would correct that behavior.
See bug #838193 for the changes I propose to python3-minimal.
diff --git a/autoscripts/postinst-py3compile b/autoscripts/postinst-py3compile
index 95b..3d22fc7 100644
--- a/autoscripts/postinst-py3compile
+++ b/autoscripts/postinst-py3compile
@@ -1,3 +1,3 @@
if which py3compile >/dev/null 2>&1; then
- py3compile -p #PACKAGE# #ARGS#
+ py3compile -p #PACKAGE#:$DPKG_MAINTSCRIPT_ARCH #ARGS#
fi
diff --git a/autoscripts/prerm-py3clean b/autoscripts/prerm-py3clean
index c0aadfa..45c8cf2 100644
--- a/autoscripts/prerm-py3clean
+++ b/autoscripts/prerm-py3clean
@@ -1,6 +1,6 @@
if which py3clean >/dev/null 2>&1; then
- py3clean -p #PACKAGE# #ARGS#
+ py3clean -p #PACKAGE#:$DPKG_MAINTSCRIPT_ARCH #ARGS#
else
- dpkg -L #PACKAGE# | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, or next; unlink $_ or die $! foreach glob($_)'
+ dpkg -L #PACKAGE#:$DPKG_MAINTSCRIPT_ARCH | perl -ne 's,/([^/]*)\.py$,/__pycache__/\1.*, or next; unlink $_ or die $! foreach glob($_)'
find /usr/lib/python3/dist-packages/ -type d -name __pycache__ -empty -print0 | xargs --null --no-run-if-empty rmdir
fi
diff --git a/debian/changelog b/debian/changelog
index 253edae..a1dd124 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,14 @@
-dh-python (2.201609XX) UNRELEASED; urgency=medium
+dh-python (2.201609XX+nmu1) UNRELEASED; urgency=medium
+ [ Piotr Ożarowski ]
* pybuild.pm:
- enable --test-{nose,pytest,tox} if appropriate pypy-* build
dependency is set
- -- Piotr Ożarowski Wed, 07 Sep 2016 22:39:27 +0200
+ [ Joe Crayne ]
+ * python3 autoscripts: support for Multi-Arch: same.
+
+ -- Joe Crayne Sun, 18 Sep 2016 03:11:04 -0400
dh-python (2.20160818) unstable; urgency=medium
Bug#792622: missing licenses in debian/copyright
This message applies to gnumach 2:1.7+git20160809-2. The following files are not used by "dpkg-buildpackage -uc -b -nc", i.e. their atimes do not change during this binary-arch build, and the build succeeds even if they are removed. ./ChangeLog.0 ./ChangeLog.00 ./DEVELOPMENT ./ddb/db_mp.h ./ddb/tr.h ./debian/watch ./device/dev_master.h ./doc/fdl.texi ./doc/gpl.texi ./doc/stamp-vti ./i386/i386/ast_types.h ./i386/i386/cpu.h ./i386/i386/kttd_machdep.h ./i386/i386/lock.h ./i386/i386/sched_param.h ./i386/include/mach/i386/cthreads.h ./kern/act.h ./kern/refcount.h ./kern/shuttle.h ./linux/dev/README ./linux/dev/drivers/net/Space.c ./linux/dev/drivers/net/auto_irq.c ./linux/dev/drivers/net/net_init.c ./linux/dev/drivers/net/wavelan.p.h ./linux/dev/drivers/scsi/eata_dma.c ./linux/dev/drivers/scsi/g_NCR5380.c ./linux/dev/glue/net.c ./linux/dev/include/asm-i386/smp.h ./linux/dev/include/asm-i386/uaccess.h ./linux/dev/include/linux/etherdevice.h ./linux/dev/include/linux/if.h ./linux/dev/include/linux/modversions.h ./linux/dev/include/linux/netdevice.h ./linux/dev/include/linux/notifier.h ./linux/dev/include/linux/pm.h ./linux/dev/include/linux/skbuff.h ./linux/dev/include/linux/threads.h ./linux/dev/net/core/dev.c ./linux/pcmcia-cs/clients/3c574_cs.c ./linux/pcmcia-cs/clients/3c589_cs.c ./linux/pcmcia-cs/clients/ax8390.h ./linux/pcmcia-cs/clients/axnet_cs.c ./linux/pcmcia-cs/clients/fmvj18x_cs.c ./linux/pcmcia-cs/clients/nmclan_cs.c ./linux/pcmcia-cs/clients/ositech.h ./linux/pcmcia-cs/clients/pcnet_cs.c ./linux/pcmcia-cs/clients/smc91c92_cs.c ./linux/pcmcia-cs/clients/xirc2ps_cs.c ./linux/pcmcia-cs/glue/ds.c ./linux/pcmcia-cs/glue/pcmcia.c ./linux/pcmcia-cs/glue/pcmcia_glue.h ./linux/pcmcia-cs/glue/wireless_glue.h ./linux/pcmcia-cs/include/linux/crc32.h ./linux/pcmcia-cs/include/linux/slab.h ./linux/pcmcia-cs/include/pcmcia/bulkmem.h ./linux/pcmcia-cs/include/pcmcia/bus_ops.h ./linux/pcmcia-cs/include/pcmcia/ciscode.h ./linux/pcmcia-cs/include/pcmcia/cisreg.h ./linux/pcmcia-cs/include/pcmcia/cistpl.h ./linux/pcmcia-cs/include/pcmcia/cs.h ./linux/pcmcia-cs/include/pcmcia/cs_types.h ./linux/pcmcia-cs/include/pcmcia/driver_ops.h ./linux/pcmcia-cs/include/pcmcia/ds.h ./linux/pcmcia-cs/include/pcmcia/mem_op.h ./linux/pcmcia-cs/include/pcmcia/ss.h ./linux/pcmcia-cs/include/pcmcia/version.h ./linux/pcmcia-cs/modules/bulkmem.c ./linux/pcmcia-cs/modules/cirrus.h ./linux/pcmcia-cs/modules/cistpl.c ./linux/pcmcia-cs/modules/cs.c ./linux/pcmcia-cs/modules/cs_internal.h ./linux/pcmcia-cs/modules/ds.c ./linux/pcmcia-cs/modules/ene.h ./linux/pcmcia-cs/modules/i82365.c ./linux/pcmcia-cs/modules/i82365.h ./linux/pcmcia-cs/modules/o2micro.h ./linux/pcmcia-cs/modules/pci_fixup.c ./linux/pcmcia-cs/modules/ricoh.h ./linux/pcmcia-cs/modules/rsrc_mgr.c ./linux/pcmcia-cs/modules/smc34c90.h ./linux/pcmcia-cs/modules/ti113x.h ./linux/pcmcia-cs/modules/topic.h ./linux/pcmcia-cs/modules/vg468.h ./linux/pcmcia-cs/modules/yenta.h ./linux/pcmcia-cs/wireless/hermes.c ./linux/pcmcia-cs/wireless/hermes.h ./linux/pcmcia-cs/wireless/hermes_rid.h ./linux/pcmcia-cs/wireless/ieee802_11.h ./linux/pcmcia-cs/wireless/orinoco.c ./linux/pcmcia-cs/wireless/orinoco.h ./linux/pcmcia-cs/wireless/orinoco_cs.c ./linux/src/COPYING ./linux/src/drivers/net/3c501.c ./linux/src/drivers/net/3c503.c ./linux/src/drivers/net/3c503.h ./linux/src/drivers/net/3c505.c ./linux/src/drivers/net/3c505.h ./linux/src/drivers/net/3c507.c ./linux/src/drivers/net/3c509.c ./linux/src/drivers/net/3c515.c ./linux/src/drivers/net/3c59x.c ./linux/src/drivers/net/8390.c ./linux/src/drivers/net/8390.h ./linux/src/drivers/net/ac3200.c ./linux/src/drivers/net/apricot.c ./linux/src/drivers/net/at1700.c ./linux/src/drivers/net/atp.c ./linux/src/drivers/net/atp.h ./linux/src/drivers/net/de4x5.c ./linux/src/drivers/net/de4x5.h ./linux/src/drivers/net/de600.c ./linux/src/drivers/net/de620.c ./linux/src/drivers/net/de620.h ./linux/src/drivers/net/depca.c ./linux/src/drivers/net/depca.h ./linux/src/drivers/net/e2100.c ./linux/src/drivers/net/eepro.c ./linux/src/drivers/net/eepro100.c ./linux/src/drivers/net/eexpress.c ./linux/src/drivers/net/epic100.c ./linux/src/drivers/net/eth16i.c ./linux/src/drivers/net/eth82586.h ./linux/src/drivers/net/ewrk3.c ./linux/src/drivers/net/ewrk3.h ./linux/src/drivers/net/fmv18x.c ./linux/src/drivers/net/hamachi.c ./linux/src/drivers/net/hp-plus.c ./linux/src/drivers/net/hp.c ./linux/src/drivers/net/hp100.c ./linux/src/drivers/net/hp100.h ./linux/src/drivers/net/i82586.h ./linux/src/drivers/net/intel-gige.c ./linux/src/drivers/net/kern_compat.h ./linux/src/drivers/net/lance.c ./linux/src/drivers/net/myson803.c ./linux/src/drivers/net/natsemi.c ./linux/src/drivers/net/ne.c ./linux/src/drivers/net/ne2k-pci.c ./linux/src/drivers/net/ni52.c ./linux/src/drivers/net/ni52.h ./linux/src/drivers/net/ni65.c ./linux/src/drivers/net/ni65.h ./linux/src/drivers/net/ns820.c ./linux/src/drivers/net/pci-scan.c ./linux/src/drivers/net/pci-scan.h ./linux/src/drivers/net/pcnet32.c ./lin
Bug#838194: support for network-manager-strongswan 1.4?
Package: strongswan-nm
Version: 5.5.0-1
Severity: wishlist
Tags: patch
Hi Yves,
I would like to upgrade the network-manager-strongswan package
for Stretch to version 1.4.0, but this requires 2 patches to
charon-nm. See https://www.strongswan.org/download.html and
the attachment.
Do you think it would be possible to add these patches to
strongswan 5.5.0?
Of course I see that upstream plans to release strongswan 5.5.1
(including the patches) in about 3 weeks. Adding the patches to
5.5.0 now would save the time.
Thanx very much
Harri
From 9e74a0952e27e3ac0055b0831919aaddfef1e1b5 Mon Sep 17 00:00:00 2001
From: Tobias Brunner
Date: Mon, 5 Sep 2016 10:54:07 +0200
Subject: [PATCH] nm: Enforce min. length for PSKs in backend
---
src/charon-nm/nm/nm_service.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/src/charon-nm/nm/nm_service.c b/src/charon-nm/nm/nm_service.c
index 5991c24..c0c78ef 100644
--- a/src/charon-nm/nm/nm_service.c
+++ b/src/charon-nm/nm/nm_service.c
@@ -428,6 +428,16 @@ static gboolean connect_(NMVPNPlugin *plugin, NMConnection *connection,
{
user = identification_create_from_string((char*)str);
str = nm_setting_vpn_get_secret(vpn, "password");
+ if (auth_class == AUTH_CLASS_PSK &&
+strlen(str) < 20)
+ {
+g_set_error(err, NM_VPN_PLUGIN_ERROR,
+ NM_VPN_PLUGIN_ERROR_BAD_ARGUMENTS,
+ "pre-shared key is too short.");
+gateway->destroy(gateway);
+user->destroy(user);
+return FALSE;
+ }
priv->creds->set_username_password(priv->creds, user, (char*)str);
}
}
--
1.9.1
From f201d86debb12731b634625a0278e289e3e05e10 Mon Sep 17 00:00:00 2001
From: Tobias Brunner
Date: Mon, 5 Sep 2016 14:34:07 +0200
Subject: [PATCH] nm: Pass external gateway to NM
This seems to be required by newer versions.
---
src/charon-nm/nm/nm_service.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/src/charon-nm/nm/nm_service.c b/src/charon-nm/nm/nm_service.c
index c0c78ef..0fe10e0 100644
--- a/src/charon-nm/nm/nm_service.c
+++ b/src/charon-nm/nm/nm_service.c
@@ -88,12 +88,19 @@ static void signal_ipv4_config(NMVPNPlugin *plugin,
GValue *val;
GHashTable *config;
enumerator_t *enumerator;
- host_t *me;
+ host_t *me, *other;
nm_handler_t *handler;
config = g_hash_table_new(g_str_hash, g_str_equal);
handler = priv->handler;
+ /* NM apparently requires to know the gateway */
+ val = g_slice_new0 (GValue);
+ g_value_init (val, G_TYPE_UINT);
+ other = ike_sa->get_other_host(ike_sa);
+ g_value_set_uint (val, *(uint32_t*)other->get_address(other).ptr);
+ g_hash_table_insert (config, NM_VPN_PLUGIN_IP4_CONFIG_EXT_GATEWAY, val);
+
/* NM requires a tundev, but netkey does not use one. Passing the physical
* interface does not work, as NM fiddles around with it. So we pass a dummy
* TUN device along for NM to play with... */
--
1.9.1
signature.asc
Description: OpenPGP digital signature
Bug#837751: scribus: When I try to do "get Image" for a graphics frame, scribus segfaults
On Wed, Sep 14, 2016 at 04:40:57PM +0200, Wojciech Zabolotny wrote: > > I assume by your "whenever" that it is steadily reproducible. > > Can you try to temporary move away your ~/.scribus and see if the bug is > > reproducible? > > > Indeed, renaming of ~/.scribus has cured the problem. I couldn't reproduce the segfault with your .sla, and if I looked up the upstream bug tracker correctly nobody else experienced segfaults recently. According to the core dump the crash happens somewhere in the middle of dbus, and I couldn't even figure how it reached that point (here gdb says "Backtrace stopped: previous frame inner to this frame (corrupt stack?)" after #14). Anyway, I'm tempted to close this bug as it was really easily "fixed" by moving away your ~/.scribus directory. probably some file in there somehow was corrupted or got invalid data in your computer. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#792622: missing licenses in debian/copyright
Hello, Kalle Olavi Niemitalo, on Sun 18 Sep 2016 12:57:24 +0300, wrote: > The following files are not used by "dpkg-buildpackage -uc -b > -nc", i.e. their atimes do not change during this binary-arch > build, and the build succeeds even if they are removed. These shouldn't pose problem, better keep them: > ./ChangeLog.0 > ./ChangeLog.00 > ./DEVELOPMENT > ./ddb/db_mp.h > ./ddb/tr.h > ./debian/watch > ./device/dev_master.h > ./doc/fdl.texi > ./doc/gpl.texi > ./doc/stamp-vti > ./i386/i386/ast_types.h > ./i386/i386/cpu.h > ./i386/i386/kttd_machdep.h > ./i386/i386/lock.h > ./i386/i386/sched_param.h > ./i386/include/mach/i386/cthreads.h > ./kern/act.h > ./kern/refcount.h > ./kern/shuttle.h These are from linux, so basically GPLv2. Network drivers are indeed not used in Debian anymore because we use netdde. > ./linux/dev/README > ./linux/dev/drivers/net/Space.c > ./linux/dev/drivers/net/auto_irq.c > ./linux/dev/drivers/net/net_init.c > ./linux/dev/drivers/net/wavelan.p.h > ./linux/dev/drivers/scsi/eata_dma.c > ./linux/dev/drivers/scsi/g_NCR5380.c > ./linux/dev/glue/net.c > ./linux/dev/include/asm-i386/smp.h > ./linux/dev/include/asm-i386/uaccess.h > ./linux/dev/include/linux/etherdevice.h > ./linux/dev/include/linux/if.h > ./linux/dev/include/linux/modversions.h > ./linux/dev/include/linux/netdevice.h > ./linux/dev/include/linux/notifier.h > ./linux/dev/include/linux/pm.h > ./linux/dev/include/linux/skbuff.h > ./linux/dev/include/linux/threads.h > ./linux/dev/net/core/dev.c > ./linux/pcmcia-cs/clients/3c574_cs.c > ./linux/pcmcia-cs/clients/3c589_cs.c > ./linux/pcmcia-cs/clients/ax8390.h > ./linux/pcmcia-cs/clients/axnet_cs.c > ./linux/pcmcia-cs/clients/fmvj18x_cs.c > ./linux/pcmcia-cs/clients/nmclan_cs.c > ./linux/pcmcia-cs/clients/ositech.h > ./linux/pcmcia-cs/clients/pcnet_cs.c > ./linux/pcmcia-cs/clients/smc91c92_cs.c > ./linux/pcmcia-cs/clients/xirc2ps_cs.c > ./linux/pcmcia-cs/glue/ds.c > ./linux/pcmcia-cs/glue/pcmcia.c > ./linux/pcmcia-cs/glue/pcmcia_glue.h > ./linux/pcmcia-cs/glue/wireless_glue.h > ./linux/pcmcia-cs/include/linux/crc32.h > ./linux/pcmcia-cs/include/linux/slab.h > ./linux/pcmcia-cs/include/pcmcia/bulkmem.h > ./linux/pcmcia-cs/include/pcmcia/bus_ops.h > ./linux/pcmcia-cs/include/pcmcia/ciscode.h > ./linux/pcmcia-cs/include/pcmcia/cisreg.h > ./linux/pcmcia-cs/include/pcmcia/cistpl.h > ./linux/pcmcia-cs/include/pcmcia/cs.h > ./linux/pcmcia-cs/include/pcmcia/cs_types.h > ./linux/pcmcia-cs/include/pcmcia/driver_ops.h > ./linux/pcmcia-cs/include/pcmcia/ds.h > ./linux/pcmcia-cs/include/pcmcia/mem_op.h > ./linux/pcmcia-cs/include/pcmcia/ss.h > ./linux/pcmcia-cs/include/pcmcia/version.h > ./linux/pcmcia-cs/modules/bulkmem.c > ./linux/pcmcia-cs/modules/cirrus.h > ./linux/pcmcia-cs/modules/cistpl.c > ./linux/pcmcia-cs/modules/cs.c > ./linux/pcmcia-cs/modules/cs_internal.h > ./linux/pcmcia-cs/modules/ds.c > ./linux/pcmcia-cs/modules/ene.h > ./linux/pcmcia-cs/modules/i82365.c > ./linux/pcmcia-cs/modules/i82365.h > ./linux/pcmcia-cs/modules/o2micro.h > ./linux/pcmcia-cs/modules/pci_fixup.c > ./linux/pcmcia-cs/modules/ricoh.h > ./linux/pcmcia-cs/modules/rsrc_mgr.c > ./linux/pcmcia-cs/modules/smc34c90.h > ./linux/pcmcia-cs/modules/ti113x.h > ./linux/pcmcia-cs/modules/topic.h > ./linux/pcmcia-cs/modules/vg468.h > ./linux/pcmcia-cs/modules/yenta.h > ./linux/pcmcia-cs/wireless/hermes.c > ./linux/pcmcia-cs/wireless/hermes.h > ./linux/pcmcia-cs/wireless/hermes_rid.h > ./linux/pcmcia-cs/wireless/ieee802_11.h > ./linux/pcmcia-cs/wireless/orinoco.c > ./linux/pcmcia-cs/wireless/orinoco.h > ./linux/pcmcia-cs/wireless/orinoco_cs.c > ./linux/src/COPYING > ./linux/src/drivers/net/3c501.c > ./linux/src/drivers/net/3c503.c > ./linux/src/drivers/net/3c503.h > ./linux/src/drivers/net/3c505.c > ./linux/src/drivers/net/3c505.h > ./linux/src/drivers/net/3c507.c > ./linux/src/drivers/net/3c509.c > ./linux/src/drivers/net/3c515.c > ./linux/src/drivers/net/3c59x.c > ./linux/src/drivers/net/8390.c > ./linux/src/drivers/net/8390.h > ./linux/src/drivers/net/ac3200.c > ./linux/src/drivers/net/apricot.c > ./linux/src/drivers/net/at1700.c > ./linux/src/drivers/net/atp.c > ./linux/src/drivers/net/atp.h > ./linux/src/drivers/net/de4x5.c > ./linux/src/drivers/net/de4x5.h > ./linux/src/drivers/net/de600.c > ./linux/src/drivers/net/de620.c > ./linux/src/drivers/net/de620.h > ./linux/src/drivers/net/depca.c > ./linux/src/drivers/net/depca.h > ./linux/src/drivers/net/e2100.c > ./linux/src/drivers/net/eepro.c > ./linux/src/drivers/net/eepro100.c > ./linux/src/drivers/net/eexpress.c > ./linux/src/drivers/net/epic100.c > ./linux/src/drivers/net/eth16i.c > ./linux/src/drivers/net/eth82586.h > ./linux/src/drivers/net/ewrk3.c > ./linux/src/drivers/net/ewrk3.h > ./linux/src/drivers/net/fmv18x.c > ./linux/src/drivers/net/hamachi.c > ./linux/src/drivers/net/hp-plus.c > ./linux/src/drivers/net/hp.c > ./linux/src/drivers/net/hp100.c > ./linux/src/drivers/net/hp100.h > ./linux/src/drivers/net/i82586.h > ./linux/src/drivers/net/intel-gige.c > ./linux
Bug#692105: Removing c-cpp-reference from Debian?
reassign 692105 ftp.debian.org retitle 692105 RM: c-cpp-reference -- RoQA; orphaned, dead upstream, obsolete thanks On Sun, Sep 18, 2016 at 12:00:49AM +0200, Pino Toscano wrote: > In data domenica 18 settembre 2016 00:18:41 CEST, Adrian Bunk ha scritto: > > I would like to get an opinion from you as maintainers of KDevelop > > on removal of c-cpp-reference from Debian. > > > > It seems to be a 15-20 year old reference for KDevelop that comes from > > http://kdevelop.org > > s/comes/it used to come/ > > Considering the times the kdevelop.org website has changed since that > guide was picked, I really doubt it can be found anywhere else. > > > Does it make any sense for KDevelop today? > > It seems updated last in KDE 3 times at best, and I I'm pretty sure > recent versions of kdevelop don't even know about it. So no, it does > not make sense, especially ... > > > After a quick look at the C part there are tutorial parts that are > > still useful today, but there are many (including better) tutorials > > available online. > > ... because of this. Thanks for your comments, I'm requesting removal. 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#770265: submitted patches
Control: reassign -1 dh-python This is actually a bug in dh-python and python3-minimal. I've submitted fixes at bug #812228 and bug #838193.
Bug#836567: [Aptitude-devel] Bug#836567: aptitude: [PATCH] aborts on encountering new DepCompareOp flags
On Sat, Sep 17, 2016 at 10:32:53PM -0400, Aaron M. Ucko wrote:
> > On a first glance, using the module operator rather than bitwise
> > operations looks a bit odd.
>
> It's unconventional, but should optimize to bitwise masking in practice
> because the modulus is a constant power of two. Using an explicit mask
> would be cleaner, but AFAICT apt's headers don't predefine one.
From the apt side I can confirm that I 'recently' added new flags
(specifically in 8c7af4d4 on Thu Jul 16 11:15:25 2015).
The flags are more for internal record keeping rather than needing to be
checked explicitly, but the context ("subsumes") scares me a bit:
MultiArchImplicit can be subsumed although it is unlikely that it ever
will. Those dependencies are needed to translate MultiArch to
SingleArch, which means e.g. Breaks&Replaces != this_version for
M-A:same packages on all other architecture siblings.
ArchSpecific is similar. It sounds like it would be important to check,
but the dependencies are formed in a way that this works without
a resolver 'thinking' about (– for your and my [mostly my really] safety
I will spare you the details on how that is done).
So, why the flags at all? MultiArch worked without them just fine, the
problem they solve is if you for some reason need to know which
dependency was explicitly written in the Packages stanza (and how) vs.
a dependency libapt invented, which is nontrivial to figure out if you
just get handed a dependency and are supposed to tell if its invented or
not, but apt e.g. needs that for its external solver/planner support or
'apt depends foo'.
I /guess/ you will be fine by ignoring these flags in the usecases of
the subsumes method, but that might not be the case for future flags
(who knows what I will do next… *evil laughter*) and if that would be my
method I would opt for not subsuming if the flags do not match
(excluding or – although, not sure if that is really true in all cases,
but that works for a while now, so I will accept that as given without
thinking about it). In practice these dependencies will not be subsumed
in most (= I would say all, but if you are an 'evil' maintainer you can
do it. Practical use is subzero through) cases even if you would allow
it anyhow.
Hope that adding some context helps here.
Best regards
David Kalnischkies
signature.asc
Description: PGP signature
Bug#835581: Possible fix for the FTBFS in node-es6-promise
On Sun, 28 Aug 2016, Julien Puydt wrote: > I don't have a stretch box handy, but /usr/bin/compile-modules comes from the > node-es6-module-transpiler package. Testing has node-es6-module-transpiler > version 0.10.0.1, which depends on node-ast-util (in testing 0.6.0-1), which > depends on node-ast-types (in testing 0.9.0-1). > > Things get interesting there : node-ast-types 0.9.0-1 has no RC bug for > itself, but triggers errors in other packages! See #835704, about a FTBFS in > node-ast-util, for example. > > You don't have the typical message of this problem (a missing ./fork module), > but my guess is that whenever an exception is triggered in compile-modules, > that is treated by printing the help, thus hiding the real issue. > > I prepared node-ast-types 0.9.0-2 for unstable today -- can you check it makes > your FTBFS for node-es6-promise vanish? Hello. node-es6-promise builds fine on stretch right now. However, if this was not really a bug in node-es6-promise, it would be better (instead of just closing it) if we could reassign to the proper package and also send "affects 835581 src:node-es6-promise" to control@b.d.o. This way, this bug will still be shown in the web page for node-es6-promise, as it made the package to FTBFS. Thanks.
Bug#838197: sphinxcontrib-docbookrestapi: FTBFS: ImportError: Failed to import test module: test_utils
Source: sphinxcontrib-docbookrestapi Version: 0.2.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, sphinxcontrib-docbookrestapi fails to build from source in unstable/amd64: [..] Preparing to unpack .../48-python-tidylib_0.2.4~dfsg-4_all.deb ... Unpacking python-tidylib (0.2.4~dfsg-4) ... Selecting previously unselected package libsubunit-perl. Preparing to unpack .../49-libsubunit-perl_1.1.0-3_all.deb ... Unpacking libsubunit-perl (1.1.0-3) ... Selecting previously unselected package python-extras. Preparing to unpack .../50-python-extras_0.0.3-3_all.deb ... Unpacking python-extras (0.0.3-3) ... Selecting previously unselected package python-linecache2. Preparing to unpack .../51-python-linecache2_1.0.0-2_all.deb ... Unpacking python-linecache2 (1.0.0-2) ... Selecting previously unselected package python-mimeparse. Preparing to unpack .../52-python-mimeparse_0.1.4-1_all.deb ... Unpacking python-mimeparse (0.1.4-1) ... Selecting previously unselected package python-traceback2. Preparing to unpack .../53-python-traceback2_1.4.0-3_all.deb ... Unpacking python-traceback2 (1.4.0-3) ... Selecting previously unselected package python-unittest2. Preparing to unpack .../54-python-unittest2_1.1.0-6.1_all.deb ... Unpacking python-unittest2 (1.1.0-6.1) ... Selecting previously unselected package python-testtools. Preparing to unpack .../55-python-testtools_1.8.0-3_all.deb ... Unpacking python-testtools (1.8.0-3) ... Selecting previously unselected package python-subunit. Preparing to unpack .../56-python-subunit_1.1.0-3_all.deb ... Unpacking python-subunit (1.1.0-3) ... Selecting previously unselected package python3-extras. Preparing to unpack .../57-python3-extras_0.0.3-3_all.deb ... Unpacking python3-extras (0.0.3-3) ... Selecting previously unselected package python3-linecache2. Preparing to unpack .../58-python3-linecache2_1.0.0-2_all.deb ... Unpacking python3-linecache2 (1.0.0-2) ... Selecting previously unselected package python3-mimeparse. Preparing to unpack .../59-python3-mimeparse_0.1.4-1_all.deb ... Unpacking python3-mimeparse (0.1.4-1) ... Selecting previously unselected package python3-pbr. Preparing to unpack .../60-python3-pbr_1.8.0-4.1_all.deb ... Unpacking python3-pbr (1.8.0-4.1) ... Selecting previously unselected package python3-traceback2. Preparing to unpack .../61-python3-traceback2_1.4.0-3_all.deb ... Unpacking python3-traceback2 (1.4.0-3) ... Selecting previously unselected package python3-unittest2. Preparing to unpack .../62-python3-unittest2_1.1.0-6.1_all.deb ... Unpacking python3-unittest2 (1.1.0-6.1) ... Selecting previously unselected package python3-testtools. Preparing to unpack .../63-python3-testtools_1.8.0-3_all.deb ... Unpacking python3-testtools (1.8.0-3) ... Selecting previously unselected package python3-subunit. Preparing to unpack .../64-python3-subunit_1.1.0-3_all.deb ... Unpacking python3-subunit (1.1.0-3) ... Selecting previously unselected package subunit. Preparing to unpack .../65-subunit_1.1.0-3_all.deb ... Unpacking subunit (1.1.0-3) ... Selecting previously unselected package python-fixtures. Preparing to unpack .../66-python-fixtures_1.3.1-2_all.deb ... Unpacking python-fixtures (1.3.1-2) ... Selecting previously unselected package python-testrepository. Preparing to unpack .../67-python-testrepository_0.0.20-2_all.deb ... Unpacking python-testrepository (0.0.20-2) ... Selecting previously unselected package python3-fixtures. Preparing to unpack .../68-python3-fixtures_1.3.1-2_all.deb ... Unpacking python3-fixtures (1.3.1-2) ... Selecting previously unselected package python3-testrepository. Preparing to unpack .../69-python3-testrepository_0.0.20-2_all.deb ... Unpacking python3-testrepository (0.0.20-2) ... Selecting previously unselected package testrepository. Preparing to unpack .../70-testrepository_0.0.20-2_all.deb ... Unpacking testrepository (0.0.20-2) ... Setting up python-linecache2 (1.0.0-2) ... Setting up libjs-jquery (1.12.4-1) ... Setting up madison-lite (0.22) ... Setting up libapt-inst2.0:amd64 (1.3~rc4) ... Setting up python-setuptools (27.1.2-1) ... Setting up python3-linecache2 (1.0.0-2) ... Setting up python-extras (0.0.3-3) ... Setting up libhttp-date-perl (6.02-1) ... Setting up libtidy5 (1:5.2.0-2) ... Setting up libjs-underscore (1.8.3~dfsg-1) ... Setting up python-mimeparse (0.1.4-1) ... Setting up libencode-locale-perl (1.05-1) ... Setting up apt-utils (1.3~rc4) ... Setting up libio-html-perl (1.001-1) ... Setting up python3-six (1.10.0-3) ... Setting up python-tz (2015.7+dfsg-0.1) ... Setting up python-imagesize (0.7.1-1) ... Setting up libjs-sphinxdoc (1.4.6-1) ... Setting up python3-extras (0.0.3-3) ... Se
Bug#838186: [handbrake] No audio in output file
Hi there, first, what version of reportbug have you used to submit this bug report? The version numbers for the ffmpeg (and many other) libraries are not reported in the template. Am Sonntag, den 18.09.2016, 09:17 +0100 schrieb Antonio Marcos López Alonso: > Debian Release: stretch/sid > 900 testing ftp.pt.debian.org > 500 xenial ppa.launchpad.net > 500 wilyppa.launchpad.net > 500 unstableftp.pt.debian.org > 500 trusty ppa.launchpad.net > 500 stable update.devolo.com > 500 stable kxstudio.linuxaudio.org > 500 stable dl.google.com > 500 sid linux.dropbox.com > 500 lucid ppa.launchpad.net Erm, this doesn't really read like a valid combination of package sources that we might want to support. Please make sure all library packages that are reported as dependencies for handbrake are the ones from the official Debian mirrors. Thanks! - Fabian signature.asc Description: This is a digitally signed message part
Bug#838196: gnote: FTBFS: note.hpp:127:14: error: cannot convert 'const Glib::RefPtr' to 'bool' in return
Source: gnote Version: 3.20.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, gnote fails to build from source in unstable/amd64: [..] checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking whether UID '1000' is supported by ustar format... yes checking whether GID '1000' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking whether make supports nested variables... (cached) yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether ln -s works... yes checking for itstool... itstool checking for xmllint... xmllint checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... none checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... none checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for a working dd... /bin/dd checking how to truncate binary pipes... /bin/dd bs=4096 count=1 checking for mt... no checking if : is a manifest tool... no checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes ch
Bug#837946: same with 0.8.3-1
As I tried to say before, the problem appeared with latest 0.8.3, and downgrading did not help. Here's the same backtrace from 0.8.3-1: > Thread 1 "aptitude" received signal SIGABRT, Aborted. > 0xf7727d09 in __kernel_vsyscall () > @@gdb> bt > @gdb> #0 0xf7727d09 in __kernel_vsyscall () > #1 0xf6cc5c19 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54 > #2 0xf6cc7117 in __GI_abort () at abort.c:89 > #3 0x5679d309 in subsumes (d2=..., d1=...) at > ../../../../src/generic/apt/apt.cc:1182 > #4 or_group_subsumes (d1=..., d2=..., cache=) at > ../../../../src/generic/apt/apt.cc:1205 > #5 0x5679f002 in internal_is_interesting_dep (cache=0x586f1440, d=...) at > ../../../../src/generic/apt/apt.cc:1303 > #6 is_interesting_dep (d=..., cache=0x586f1440) at > ../../../../src/generic/apt/apt.cc:1344 > #7 0x567c2865 in aptitude_resolver_version::dep_iterator::applicable > (dep=..., prv=..., prv_open=false, cache=0x586f1440) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:283 > #8 0x567bbcda in aptitude_resolver_version::dep_iterator::applicable > (this=0xffccb4f8) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:302 > #9 0x567bbdb9 in aptitude_resolver_version::dep_iterator::normalize > (this=0xffccb4f8) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:317 > #10 0x567bd095 in aptitude_resolver_version::dep_iterator::operator++ > (this=0xffccb4f8) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:529 > #11 0x568ab9b7 in aptitude_universe::dep_iterator::operator++ > (this=) at > ../../../../src/generic/apt/aptitude_resolver_universe.h:1246 > #12 generic_problem_resolver::generic_problem_resolver > (this=, _step_score=, _broken_score= out>, _unfixed_soft_score=, infinity=, > _full_solution_score=, _unfixed_soft_cost=..., > _future_horizon=, _initial_state=..., _universe=...) at > ../../../../src/generic/problemresolver/problemresolver.h:3782 > #13 0x5689a73c in aptitude_resolver::aptitude_resolver (this=0x5a171308, > step_score=-10, broken_score=-100, unfixed_soft_score=-200, infinity=100, > resolution_score=50, unfixed_soft_cost=..., future_horizon=50, > _cost_settings=..., initial_installations=..., cache=0x586f1440, > _policy=0x5883a050) at ../../../../src/generic/apt/aptitude_resolver.cc:731 > #14 0x56814ac1 in resolver_manager::create_resolver (this=0x5a082cb8) at > ../../../../src/generic/apt/resolver_manager.cc:968 > #15 0x56816da3 in resolver_manager::maybe_create_resolver (this=0x5a082cb8, > consider_policybroken=true) at > ../../../../src/generic/apt/resolver_manager.cc:805 > #16 0x56817718 in resolver_manager::reset_resolver (this=, > consider_policybroken=) at > ../../../../src/generic/apt/resolver_manager.cc:218 > #17 0x566ef2a4 in do_package_run () at ../../src/ui.cc:1817 > #18 0xf748445c in cwidget::widgets::widget::handle_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #19 0xf7456b88 in > cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) () > from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #20 0xf7488b3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #21 0xf743321c in cwidget::widgets::menubar::handle_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #22 0xf7488b3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #23 0xf73fab51 in > cwidget::toplevel::input_thread::get_input_event::dispatch() () from > /usr/lib/i386-linux-gnu/libcwidget.so.3 > #24 0xf73f1bef in cwidget::toplevel::mainloop(int) () from > /usr/lib/i386-linux-gnu/libcwidget.so.3 > #25 0x566ef4ae in ui_main () at ../../src/ui.cc:3134 > #26 0x565f83ab in main (argc=, argv=) at > ../../src/main.cc:1427 #Regards/Marcel
Bug#838195: lintian: Check for PACKAGE.maintscript files that include "maint-script-parameters".
Package: lintian
Severity: wishlist
Tags: patch
Hi,
Attached is the following:
commit 767c26eb22eb0b7ee5ed04ef06be9daed12446e3
Author: Chris Lamb
Date: Sun Sep 18 11:19:14 2016 +0100
Check for PACKAGE.maintscript files that include
"maint-script-parameters".
checks/debhelper.desc | 8
checks/debhelper.pm| 10
++
.../debian/debian/maintscript | 2 ++
t/tests/maintscript-includes-maint-script-parameters/desc | 6 ++
t/tests/maintscript-includes-maint-script-parameters/tags | 1 +
5 files changed, 27 insertions(+)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
>From 767c26eb22eb0b7ee5ed04ef06be9daed12446e3 Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Sun, 18 Sep 2016 11:19:14 +0100
Subject: [PATCH] Check for PACKAGE.maintscript files that include
"maint-script-parameters".
---
checks/debhelper.desc | 8
checks/debhelper.pm| 10 ++
.../debian/debian/maintscript | 2 ++
t/tests/maintscript-includes-maint-script-parameters/desc | 6 ++
t/tests/maintscript-includes-maint-script-parameters/tags | 1 +
5 files changed, 27 insertions(+)
create mode 100644 t/tests/maintscript-includes-maint-script-parameters/debian/debian/maintscript
create mode 100644 t/tests/maintscript-includes-maint-script-parameters/desc
create mode 100644 t/tests/maintscript-includes-maint-script-parameters/tags
diff --git a/checks/debhelper.desc b/checks/debhelper.desc
index 9b9d046..3317d56 100644
--- a/checks/debhelper.desc
+++ b/checks/debhelper.desc
@@ -361,3 +361,11 @@ Info: The listed target in debian/rules command is a likely misspelling.
Implementation detail: The typo is detected by using "Levenshtein
edit distance". Therefore, if the typo involve several characters,
Lintian may not detect it.
+
+Tag: maintscript-includes-maint-script-parameters
+Severity: normal
+Certainty: possible
+Info: Lines in a debian/*.maintscript correspond to
+ dpkg-maintscript-helper(1) commands and parameters. However, the
+ "maint-script-parameters" should not be included as debhelper will add those
+ automatically. See dh_installdeb(1) for more information.
diff --git a/checks/debhelper.pm b/checks/debhelper.pm
index ad80fc8..be8fd25 100644
--- a/checks/debhelper.pm
+++ b/checks/debhelper.pm
@@ -354,6 +354,16 @@ sub run {
_tag_if_executable($file);
} elsif ($basename =~ m/^ex\.|\.ex$/i) {
tag 'dh-make-template-in-source', $file;
+} elsif ($basename =~ m/^(?:(.*)\.)?maintscript$/) {
+next unless $file->is_open_ok;
+my $fd = $file->open;
+while (<$fd>) {
+if (m/-- "\$@"\s*$/) {
+tag 'maintscript-includes-maint-script-parameters',
+$basename, "(line $.)";
+}
+}
+close($fd);
} elsif ($basename =~ m/^(?:.+\.)?debhelper(?:\.log)?$/){
# The regex matches "debhelper", but debhelper/Dh_Lib does not
# make those, so skip it.
diff --git a/t/tests/maintscript-includes-maint-script-parameters/debian/debian/maintscript b/t/tests/maintscript-includes-maint-script-parameters/debian/debian/maintscript
new file mode 100644
index 000..9d5ecd5
--- /dev/null
+++ b/t/tests/maintscript-includes-maint-script-parameters/debian/debian/maintscript
@@ -0,0 +1,2 @@
+rm_conffile /etc/correct.conf 0.2~ foo
+rm_conffile /etc/incorrect.conf 0.2~ foo -- "$@"
diff --git a/t/tests/maintscript-includes-maint-script-parameters/desc b/t/tests/maintscript-includes-maint-script-parameters/desc
new file mode 100644
index 000..0313ac0
--- /dev/null
+++ b/t/tests/maintscript-includes-maint-script-parameters/desc
@@ -0,0 +1,6 @@
+Testname: maintscript-includes-maint-script-parameters
+Sequence: 6000
+Version: 1.0
+Description: Check for dh_installdeb .maintscript files
+Test-For:
+ maintscript-includes-maint-script-parameters
diff --git a/t/tests/maintscript-includes-maint-script-parameters/tags b/t/tests/maintscript-includes-maint-script-parameters/tags
new file mode 100644
index 000..ca38ca0
--- /dev/null
+++ b/t/tests/maintscript-includes-maint-script-parameters/tags
@@ -0,0 +1 @@
+W: maintscript-includes-maint-script-parameters source: maintscript-includes-maint-script-parameters maintscript (line 2)
--
2.9.3
Bug#811846: #811846: status?
Hello Pino, Am Sonntag, den 18.09.2016, 07:06 +0200 schrieb Pino Toscano: > Hi, > > what's the status of this bug (xbase64 that FTBFS with GCC 6)? > Because of it, xbase64 was removed from testing a couple of months > ago, The package is uploaded to mentors and Adrian is looking for it. > and now it will prevent calligra (which ships a sybase access driver > for kexi) to migrate to testing. > Ok. I have Adrian add as CC. > Any way I can help with this? > Many thanks. Please ask Adrian for it. > Thanks, Cu Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#805667: ITA
Control tags 827300 +patch On Fri, Jun 03, 2016 at 01:01:13AM +0200, Dominik George wrote: > Hi, Hi Dominik, > I have started to update this package to the new 0.9.9 upstream version in > collab-maint. what is the status of this work? Currently Guacamole is not in testing, and therefore on course for not being included in stretch. If 0.9.9 is not ready for upload soon, can you make at least the minimum changes for not having Guacamole dropped completely from stretch? These would be: - the trivial fix for #827300 (remove the -Werror from src/protocols/ssh/Makefile.am) - a fix for #832846 (I have no clue about that one, but Emmanuel or Mike might be able to help) - looking at the upstream changelog, a 0.8.3 -> 0.8.4 update seems to be a low hanging fruit - when doing the uploads, please also change the maintainer field of the packages The perfect solution would be 0.9.9 in stretch, but having 0.8.4 in stretch would at least be better than not having Guacamole in stretch. > Cheers, > Nik Thanks 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#837708: thunar: Segfault after file rename
Hello, I was affected by this bug from some time, and about one week ago I found something that did the trick for me: http://tqdev.com/2016-xubuntu-16-04-thunar-crashes-on-rename I did these steps: * apt-get source thunar * apt-get build-dep thunar * Manually patch the file as in the blog post * debuild -us -uc * dpkg -i $THE_PATCHED_PACKAGES_(ONLY_THE_ONES_I_ALREADY_HAD_INSTALLED) And tried the new thunar for a week. This solved for me. Maybe the maintainers can test and packaged it more cleanly (I did this only for me). Thank you in advance! PS: I was going to test this patch for a week and then file a bug here in the BTS, but Chris Tillman got it first :D) signature.asc Description: This is a digitally signed message part
Bug#835992: 835992
Hi. spl 0.6.5.8 only not solve the problem! zfs 0.6.5.8 also required Holger...
Bug#838047: libwacom2: segfault in libwacom from gnome-shell
Source: libwacom Version: segfault with gnome-shell Followup-For: Bug #838047 Dear Maintainer, same problem for me with a Wacom Graphire 2. Same error message as for previous reporter. Regards -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#838198: 9base: FTBFS on hurd-i386: fatal error:can't create y.tab.h, :1
Package: 9base
Severity: important
Version: 1:6-7
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
X-Debbugs-CC: debian-h...@lists.debian.org
The package fails to build on hurd-i386 because of incorrect values
supplied to fopen() and missing (__GNU__)-defines.
Failing build log:
https://buildd.debian.org/status/package.php?p=9base&suite=sid
The supplied patch fixes this.
TODO: Write a Hurd-specific disksize()-function in lib9/_p9dir.c
Cheers,
Ola Ekström
diff -rupN 9base-6-original/lib9/date.c 9base-6-new/lib9/date.c
--- 9base-6-original/lib9/date.c 2010-06-04 10:46:05.0 +
+++ 9base-6-new/lib9/date.c 2016-09-17 06:11:07.0 +
@@ -8,7 +8,7 @@
#define _HAVETMZONE 1
#define _HAVETMTZOFF 1
-#if defined(__linux__)
+#if defined(__linux__) || defined(__GNU__)
# undef _HAVETMZONE
# undef _HAVETMTZOFF
diff -rupN 9base-6-original/lib9/dirfwstat.c 9base-6-new/lib9/dirfwstat.c
--- 9base-6-original/lib9/dirfwstat.c 2010-06-04 10:46:05.0 +
+++ 9base-6-new/lib9/dirfwstat.c 2016-09-17 06:11:54.0 +
@@ -4,7 +4,7 @@
#include
#include
-#if defined(__FreeBSD__) || defined(__APPLE__) || defined(__OpenBSD__) || defined(__linux__)
+#if defined(__FreeBSD__) || defined(__APPLE__) || defined(__OpenBSD__) || defined(__linux__) || defined(__GNU__)
/* do nothing -- futimes exists and is fine */
#elif defined(__SunOS5_9__)
diff -rupN 9base-6-original/lib9/dirread.c 9base-6-new/lib9/dirread.c
--- 9base-6-original/lib9/dirread.c 2010-06-04 10:46:05.0 +
+++ 9base-6-new/lib9/dirread.c 2016-09-17 06:07:55.0 +
@@ -6,7 +6,7 @@
extern int _p9dir(struct stat*, struct stat*, char*, Dir*, char**, char*);
-#if defined(__linux__) || defined(__FreeBSD_kernel__)
+#if defined(__linux__) || defined(__FreeBSD_kernel__) || defined(__GNU__)
static int
mygetdents(int fd, struct dirent *buf, int n)
{
diff -rupN 9base-6-original/lib9/libc.h 9base-6-new/lib9/libc.h
--- 9base-6-original/lib9/libc.h 2010-06-04 10:46:05.0 +
+++ 9base-6-new/lib9/libc.h 2016-09-17 21:04:11.0 +
@@ -594,10 +594,17 @@ extern void freenetconninfo(NetConnInfo
#define MCACHE 0x0010 /* cache some data */
#define MMASK 0x0017 /* all bits on */
-#define OREAD 0 /* open for read */
-#define OWRITE 1 /* write */
-#define ORDWR 2 /* read and write */
-#define OEXEC 3 /* execute, == read but check execute permission */
+#if defined(__GNU__)
+ #define OREAD O_RDONLY /* open for read */
+ #define OWRITE O_WRONLY /* write */
+ #define ORDWR O_RDWR /* read and write */
+ #define OEXEC O_EXEC /* execute, == read but check execute permission */
+#else
+ #define OREAD 0 /* open for read */
+ #define OWRITE 1 /* write */
+ #define ORDWR 2 /* read and write */
+ #define OEXEC 3 /* execute, == read but check execute permission */
+#endif
#define OTRUNC 16 /* or'ed in (except for exec), truncate file first */
#define OCEXEC 32 /* or'ed in, close on exec */
#define ORCLOSE 64 /* or'ed in, remove on close */
diff -rupN 9base-6-original/lib9/u.h 9base-6-new/lib9/u.h
--- 9base-6-original/lib9/u.h 2010-06-04 10:46:05.0 +
+++ 9base-6-new/lib9/u.h 2016-09-17 06:09:40.0 +
@@ -58,7 +58,7 @@ extern "C" {
typedef long p9jmp_buf[sizeof(sigjmp_buf)/sizeof(long)];
-#if defined(__linux__)
+#if defined(__linux__) || defined(__GNU__)
# include
# if defined(__Linux26__)
# include
Bug#837895: lightdm-gtk-greeter: GUI does not run, black screen, on startup
Package: lightdm-gtk-greeter
Version: 2.0.1-2
Followup-For: Bug #837895
I can confirm this bug on another platform. I also updated packages
before rebooting today.
Initially a mouse symbol appears in the middle of the screen, then
after a few seconds is displayed in the left upper corner.
When - despite the black screen - typing in credentials (username tab
password enter), first a cursor ('_') appears in the left upper
corner of the screen and after a few seconds a mouse symbol again.
Thus it seems the greeter does react somehow.
When installing lightdm-kde-greeter as a replacement, I can login
to Mate (and some things there don't work well).
If I can help testing something, please let me know.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: armhf (armv7l)
Kernel: Linux 4.6.0-1-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lightdm-gtk-greeter depends on:
ii libc6 2.23-5
ii libcairo2 1.14.6-1+b1
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-02.49.6-1
ii libgtk-3-0 3.21.5-3
ii liblightdm-gobject-1-0 1.18.2-2
ii libx11-62:1.6.3-1
Versions of packages lightdm-gtk-greeter recommends:
ii adwaita-icon-theme [gnome-icon-theme-symbolic] 3.21.91-1
ii desktop-base8.0.2
ii gnome-themes-standard 3.20.2-3
ii policykit-1 0.105-16
lightdm-gtk-greeter suggests no packages.
-- no debconf information
Bug#831240: google-perftools: FTBFS: Running death test 0 hangs
severity 831240 serious tags 831240 patch thanks On Fri, 16 Sep 2016, Lucas Nussbaum wrote: > On 15/09/16 at 19:39 +0200, Santiago Vila wrote: > > Version 2.2.1-0.3 is the first one that does not *always* fail for me. > > This is a great achievement indeed. > > > > Now it builds sometimes, but 3/11 is not a very good ratio. > > I'm not sure, no. It's indeed possible that it's still failing randomly. Ok, based on available data, this package still FTBFS randomly, so I'm raising the severity to serious again. Since there is a new upstream release, maybe it does not make much sense to try to debug this in the current version. So I suggest the maintainer to disable the tests (trivial but untested patch attached) for this release and reenable them for the next upstream version. I don't use this package myself, and it is not my intention or desire to see it autoremoved for the sake of removing it. Everything I ask is that it builds ok, so if anybody reading this wants to see this package in stretch in its current form please consider contacting the maintainer and/or disabling the tests in a NMU. Upstream is willing to help here, but if the maintainer seems to be MIA, there is not much else we can do. Thanks.--- a/debian/rules +++ b/debian/rules @@ -22,7 +22,7 @@ DEB_INSTALL_CHANGELOGS_ALL := ChangeLog ifeq (,$(findstring nocheck, $(DEB_BUILD_OPTIONS))) # List of architectures for which test execution is enabled -TEST_ARCHS=i386 amd64 +TEST_ARCHS= ifneq (,$(findstring $(DEB_HOST_ARCH), $(TEST_ARCHS))) DEB_MAKE_CHECK_TARGET := check endif # TEST_ARCHS
Bug#811846: #811846: status?
On 09/18/2016 12:41 PM, Jörg Frings-Fürst wrote: >> what's the status of this bug (xbase64 that FTBFS with GCC 6)? >> Because of it, xbase64 was removed from testing a couple of months >> ago, > > The package is uploaded to mentors and Adrian is looking for it. > >> and now it will prevent calligra (which ships a sybase access driver >> for kexi) to migrate to testing. >> > > Ok. I have Adrian add as CC. Sorry guys, was busy this weekend. Will look at it in a few hours :). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 signature.asc Description: OpenPGP digital signature
Bug#837994: [debian-mysql] Bug#837994: Bug#837994: mysql-5.5: FTBFS on armhf
Yeah, we'll look into it some more. I've seen the sort of sudden exits without errors before if a host runs out of memory, but the requirements for building 5.5 are low and shouldn't have changed significantly. -- Lars - car...@debian.org wrote: > Control: severity -1 important > > Hi Lars, hi all, > > It finally worked on another buildd, namely henze, > https://db.debian.org/machines.cgi?host=henze > > I'm lowering the severity to important since we have now all builds. > But before eventually closing it would be nice if we can get an idea > why it failed on the other attempts on the other buildds. > > Regards, > Salvatore
Bug#832301: [832391] firefox: Please reenable GTK3 support
Hello, I also second this request, for whatever it's worth. As of now with Debian unstable I don't have GTK+3 in Firefox and can see no way to install/enable it. Cheers!
Bug#837946: [Aptitude-devel] Bug#837946: same with 0.8.3-1
Control: found -1 0.8.3-1 Hi Marcel, Marcel Partap wrote: > As I tried to say before, the problem appeared with latest 0.8.3, > and downgrading did not help. Ah, sorry, missed that then. > Here's the same backtrace from 0.8.3-1: Thanks! Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#838199: freeorion-data: Cannot upgrade to 0.4.6~RC1-1 in unstable if kodi is installed, too.
Package: freeorion-data Version: 0.4.5+git20160707-2 Severity: important I cannot upgrade freeorion to 0.4.6~RC1-1 in unstable, as it depends on fonts- roboto-unhinted. The problem is that I have installed the kodi package, which depends on fonts-roboto-hinted. However, fonts-roboto-hinted conflicts with fonts-roboto-unhinted. Hence only one of these packages can be installed. Version 0.4.5+git20160707-2 (currently in testing) does not depend on fonts- roboto-*. P.S.: I'm not sure if this ticket should be filed against freeorion, kodi or fonts-roboto. I'm also not sure what's the right severity for a dependency problem. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (999, 'unstable'), (998, 'testing'), (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (350, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.4-0 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freeorion-data depends on: ii fonts-dejavu 2.37-1 pn python:any freeorion-data recommends no packages. Versions of packages freeorion-data suggests: pn freeorion
Bug#837284: libimage-info-perl: diff for NMU version 1.28-1.3
Control: tags 837284 + patch Control: tags 837284 + pending Dear maintainer, I've prepared an NMU for libimage-info-perl (versioned as 1.28-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Tanita Tikaram: World Outside Your Window diff -u libimage-info-perl-1.28/debian/changelog libimage-info-perl-1.28/debian/changelog --- libimage-info-perl-1.28/debian/changelog +++ libimage-info-perl-1.28/debian/changelog @@ -1,3 +1,12 @@ +libimage-info-perl (1.28-1.3) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "FTBFS: Can't locate inc/Module/Install.pm in @INC": +call perl with "-I." in debian/rules. +(Closes: #837284) + + -- gregor herrmann Sun, 18 Sep 2016 13:23:13 +0200 + libimage-info-perl (1.28-1.2) unstable; urgency=medium * Non-maintainer upload. diff -u libimage-info-perl-1.28/debian/rules libimage-info-perl-1.28/debian/rules --- libimage-info-perl-1.28/debian/rules +++ libimage-info-perl-1.28/debian/rules @@ -27,7 +27,7 @@ build: build-stamp build-stamp: dh_testdir - $(PERL) Makefile.PL INSTALLDIRS=vendor + $(PERL) -I. Makefile.PL INSTALLDIRS=vendor $(MAKE) $(MAKE) test touch $@ signature.asc Description: Digital Signature
Bug#838194: [Pkg-swan-devel] Bug#838194: support for network-manager-strongswan 1.4?
On dim., 2016-09-18 at 11:57 +0200, Harald Dunkel wrote: > Package: strongswan-nm > Version: 5.5.0-1 > Severity: wishlist > Tags: patch > > Hi Yves, > > I would like to upgrade the network-manager-strongswan package > for Stretch to version 1.4.0, but this requires 2 patches to > charon-nm. See https://www.strongswan.org/download.html and > the attachment. > > Do you think it would be possible to add these patches to > strongswan 5.5.0? > > Of course I see that upstream plans to release strongswan 5.5.1 > (including the patches) in about 3 weeks. Adding the patches to > 5.5.0 now would save the time. If you can't wait 3 weeks, I guess including patches should be doable. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#838056: nvidia-texture-tools: Embedded libsquish library now available in debian)
On 2016-09-17 00:57 +, Debian Bug Tracking System wrote: OK. The change in nvidia-texture-tools is in fact a valid buffer overflow fix. However it is incomplete and should currently look like the code below: #if SQUISH_USE_SIMD Vec4 m_unweighted[17]; Vec4 m_metric; Vec4 m_metricSqr; Vec4 m_xxsum; Vec4 m_xsum; Vec4 m_besterror; #else Vec3 m_unweighted[17]; Vec3 m_metric; Vec3 m_metricSqr; Vec3 m_xxsum; Vec3 m_xsum; float m_besterror; #endif However that only applied in v1.7 which ntt is using, because that contained an incorrect <=16 test. In the current 1.13 the <=16 test has been corrected to <16 so the overflow no longer occurs. This is the correct fix, so this version should work fine if used by ntt. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: Digital signature
Bug#838200: (gnome-software:15001): Gs-ERROR **: CSS parsing error: not a number
Package: gnome-software Version: 3.20.2-2 Severity: important Dear Maintainer, When I run gnome-sofware I have an error: $ gnome-software (gnome-software:15001): Gs-ERROR **: CSS parsing error: not a number Trappe pour point d'arrêt et de trace -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-software depends on: ii appstream0.10.0-2 ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii gnome-software-common3.20.2-2 ii gsettings-desktop-schemas3.21.4-2 ii libappstream-glib8 0.6.2-1 ii libatk1.0-0 2.21.90-2 ii libc62.23-5 ii libcairo-gobject21.14.6-1+b1 ii libcairo21.14.6-1+b1 ii libenchant1c2a 1.6.0-11+b1 ii libfwupd10.7.3-1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.49.6-1 ii libgnome-desktop-3-123.21.90-3 ii libgtk-3-0 3.21.5-3 ii libgtkspell3-3-0 3.0.9-1 ii libjson-glib-1.0-0 1.2.2-1 ii liblimba00.5.6-2 ii libpackagekit-glib2-18 1.1.1-1 ii libpango-1.0-0 1.40.2-1 ii libpangocairo-1.0-0 1.40.2-1 ii libpolkit-gobject-1-00.105-16 ii libsoup2.4-1 2.55.90-1 ii libsqlite3-0 3.14.1-1 ii packagekit 1.1.1-1 gnome-software recommends no packages. Versions of packages gnome-software suggests: pn fwupd pn limba -- no debconf information
Bug#824684: Service is not enabled
Fix: (testing/unstable) systemctl enable arno-iptables-firewall systemctl start arno-iptables-firewall stable: see https://debianforum.de/forum/viewtopic.php?f=37&t=155905&p=1104968#p1104968
Bug#838198: 9base: FTBFS on hurd-i386: fatal error:can't create y.tab.h, :1
sam/_libc.h has: OREAD = 0, OWRITE = 1, ORDWR = 2, OCEXEC = 4, but it looks like nothing #includes that file, so perhaps that doesn't have to be patched. Have you tested sam on the Hurd? If these flags are sent in the Topen and Tcreate requests of the 9P protocol, then changing their values breaks compatibility between network hosts that run different implementations. Do the Debian packages support that protocol?
Bug#838201: bash FTCBFS: unsatisfiable cross Build-Depends: locales
Source: bash Version: 4.3-15 Tags: patch User: helm...@debian.org Usertags: rebootstrap Since glibc 2.24-3, locales-all no longer Provides: locales. Thus bash's Build-Depends on locales is no longer cross satisfiable. After a bit more investigation, it turned out that: * bash really needs locales (which contain locale sources) and not locales-all. Thus satisfying the dependency with locales-all was wrong. * bash only uses locales for testing (i.e. unless DEB_BUILD_OPTIONS contains nocheck). * The time Build-Depends is also unneeded when skipping tests. Thus the right solution to making bash cross buildable again seems to be marking locales (and while we are at it also time) with the profile. Please consider applying the attached patch. Helmut diff --minimal -Nru bash-4.3/debian/changelog bash-4.3/debian/changelog --- bash-4.3/debian/changelog 2016-06-23 21:06:40.0 +0200 +++ bash-4.3/debian/changelog 2016-09-18 13:44:16.0 +0200 @@ -1,3 +1,10 @@ +bash (4.3-15.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Mark locales and time dependencies with . Closes: #-1 + + -- Helmut Grohne Sun, 18 Sep 2016 13:39:02 +0200 + bash (4.3-15) unstable; urgency=medium * Apply upstream patches 043 - 046. Fixes: diff --minimal -Nru bash-4.3/debian/control bash-4.3/debian/control --- bash-4.3/debian/control 2015-01-28 17:13:32.0 +0100 +++ bash-4.3/debian/control 2016-09-18 13:44:04.0 +0200 @@ -4,8 +4,8 @@ Maintainer: Matthias Klose Standards-Version: 3.9.6 Build-Depends: autoconf, autotools-dev, bison, libncurses5-dev, - texinfo, texi2html, debhelper (>= 5), locales, gettext, sharutils, time, - xz-utils, dpkg-dev (>= 1.16.1) + texinfo, texi2html, debhelper (>= 5), locales , gettext, sharutils, + time , xz-utils, dpkg-dev (>= 1.16.1) Build-Depends-Indep: texlive-latex-base, ghostscript, texlive-fonts-recommended Homepage: http://tiswww.case.edu/php/chet/bash/bashtop.html Vcs-Browser: https://code.launchpad.net/~doko/+junk/pkg-bash-debian
Bug#809571: This is fixed upstream
This bug was fixed upstream in https://github.com/eldy/awstats/commit/6ca56baf8e5819787c128e5ccd741701cb84bfdd but nobody closed the bug on SourceForge. Marius Gedminas -- Unix for stability; Macs for productivity; Palm for mobility; Windows for Solitaire
Bug#837784: scribus: Some EPS files are rotated when I export the poster to a PDF file
Control: forwarded -1 https://bugs.scribus.net/view.php?id=14289 On Wed, Sep 14, 2016 at 04:43:02PM +0200, Wojciech M. Zabołotny wrote: > I was preparing a poster with included EPS files prepared with Inkscape > After the poster was ready, I have exported it to the PDF file. > It appeared, that some EPS figure got rotated by 90 degrees. wow. Well, I forwarded it upstream, see the above link. Thank you for your report. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#835206: [Packaging] Bug#835206: munin: diff for NMU version 2.0.25-2.1
Control: tags 835206 + pending thanks Hi, On Wed, Aug 31, 2016 at 09:23:41PM +0200, gregor herrmann wrote: > + * Fix "FTBFS with '.' removed from perl's @INC": > +add patch from Dominic Hargreaves to call perl with "-I.". > +(Closes: #835206) I've prepared a new upstream release now and included this patch from Dominik as well, now only waiting for upstream to do a tar.gz release too, so that our pristine-tar matches the real one… ;-) -- cheers, Holger signature.asc Description: Digital signature
Bug#835393: ITPs are wishlist, and please coordinate openvas packaging
On Sat, Sep 17, 2016 at 11:17:14PM +0300, Adrian Bunk wrote: > severity 838124 wishlist > thanks > > Please work together when re-adding OpenVAS to Debian. Hi, Don't worry. szlin and I are working together to bring OpenVAS to Debian. -- ChangZhuo Chen (陳昌倬) Debian Developer (https://nm.debian.org/public/person/czchen) Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B signature.asc Description: PGP signature
Bug#818107: [Python-apps-team] Bug#818107: doconce: please package the latest upstream version (and update the homepage)
Hi Francesco, hi everybody, I had a quick look and it seems upstream doesn't prepare releases anymore, offering simply the latest github master as a tarball to the users. Is this correct? Should we still package something? What do more experienced packagers than me think about it? Best Klaus Am 17.09.2016 um 10:26 schrieb Francesco Poli: > On Wed, 22 Jun 2016 23:00:44 +0200 Francesco Poli wrote: > >> On Sun, 13 Mar 2016 20:07:14 +0100 Francesco Poli (wintermute) wrote: >> >> [...] >>> the version currently packaged for Debian seems to be fairly outdated >> [...] >> >> Hello, >> is there any progress on this issue [1]? >> >> [1] https://bugs.debian.org/818107 >> >> Please let me know. >> Thanks for your time! > > > Ping? > > > > > ___ > Python-apps-team mailing list > python-apps-t...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-apps-team > signature.asc Description: OpenPGP digital signature
Bug#837055: fftw: diff for NMU version 2.1.5-4.1
Control: tags 837055 + pending
Dear maintainer,
I've prepared an NMU for fftw (versioned as 2.1.5-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: Tom Waits: Jack Kerouac on the Road
diff -Nru fftw-2.1.5/debian/changelog fftw-2.1.5/debian/changelog
--- fftw-2.1.5/debian/changelog 2016-07-12 23:16:24.0 +0200
+++ fftw-2.1.5/debian/changelog 2016-09-18 14:15:51.0 +0200
@@ -1,3 +1,13 @@
+fftw (2.1.5-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "FTBFS due to bfnnconv.pl failing to execute m-ascii.pl (.
+removed from @INC in perl)":
+add patch adding "./" to the require() calls in FAQ/bfnnconv.pl.
+(Closes: #837055)
+
+ -- gregor herrmann Sun, 18 Sep 2016 14:15:51 +0200
+
fftw (2.1.5-4) unstable; urgency=medium
* Team upload
diff -Nru fftw-2.1.5/debian/patches/perl-cwd-in-inc.patch fftw-2.1.5/debian/patches/perl-cwd-in-inc.patch
--- fftw-2.1.5/debian/patches/perl-cwd-in-inc.patch 1970-01-01 01:00:00.0 +0100
+++ fftw-2.1.5/debian/patches/perl-cwd-in-inc.patch 2016-09-18 14:15:48.0 +0200
@@ -0,0 +1,21 @@
+Description: require() sripts with ./
+ After cwd was removed from perl's @INC (CVE-2016-1238),
+ bfnnconv.pl doesn't find its "subscripts" anymore.
+ require them with "./" prefixed.
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/837055
+Forwarded: no
+Author: gregor herrmann
+Last-Update: 2016-09-18
+
+--- a/FAQ/bfnnconv.pl
b/FAQ/bfnnconv.pl
+@@ -61,7 +61,7 @@
+
+ open(U,">$prefix.xrefdb-new");
+
+-for $x (@outputs) { require("m-$x.pl"); }
++for $x (@outputs) { require("./m-$x.pl"); }
+
+ &call('init');
+
diff -Nru fftw-2.1.5/debian/patches/series fftw-2.1.5/debian/patches/series
--- fftw-2.1.5/debian/patches/series 2016-07-11 08:55:51.0 +0200
+++ fftw-2.1.5/debian/patches/series 2016-09-18 14:06:40.0 +0200
@@ -4,3 +4,4 @@
05_ac_define_syntax.diff
info-syntax
fix-texi2html-perl522.patch
+perl-cwd-in-inc.patch
signature.asc
Description: Digital Signature
Bug#838202: rakarrack was working in AVlinux but in new version of AVlinux the GUI doesn't show up?
Package: rakarrack Version: 0.6.1-4 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.6-rt13-avl2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rakarrack depends on: ii jackd 5 ii libasound21.1.2-1 ii libc6 2.23-4 ii libfltk1.11.1.10-22+b1 ii libfontconfig12.11.0-6.5 ii libfreetype6 2.6.3-3+b1 ii libgcc1 1:6.1.1-11 ii libjack0 [libjack-0.116] 2:0.124.2~20151211-2~xenial1 ii libsamplerate00.1.8-8 ii libsndfile1 1.0.25-10 ii libstdc++66.1.1-11 ii libx11-6 2:1.6.3-1 ii libxft2 2.3.2-1 ii libxpm4 1:3.5.11-1+b1 ii libxrender1 1:0.9.9-2 ii zlib1g1:1.2.8.dfsg-2+b1 rakarrack recommends no packages. rakarrack suggests no packages. -- no debconf information
Bug#838012: Pending fixes for bugs in the gitlab-ci-multi-runner package
tag 838012 + pending thanks Some bugs in the gitlab-ci-multi-runner package are closed in revision bb6d7e921981c6a6b187e98382f3c88345b24287 in branch 'master' by Dmitry Smirnov The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/gitlab-ci-multi-runner.git/commit/?id=bb6d7e9 Commit message: Add "gitlab-runner-helper" to prebuilt image (Closes: #838012) Thanks, Bastian Blank.
Bug#837055: fftw: diff for NMU version 2.1.5-4.1
On Sun, Sep 18, 2016 at 02:27:15PM +0200, gregor herrmann wrote: > I've prepared an NMU for fftw (versioned as 2.1.5-4.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Thanks! please feel free to speed it up to 0-day! @Thibaut: please push your last changes to the git repository, and a tag of your last upload. Either I'll just import the delta using the 2.1.5-4 from the archive. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#837055: fftw: diff for NMU version 2.1.5-4.1
On Sun, 18 Sep 2016 12:38:01 +, Mattia Rizzolo wrote: > On Sun, Sep 18, 2016 at 02:27:15PM +0200, gregor herrmann wrote: > > I've prepared an NMU for fftw (versioned as 2.1.5-4.1) and > > uploaded it to DELAYED/2. Please feel free to tell me if I > > should delay it longer. > Thanks! please feel free to speed it up to 0-day! Thank you; done. Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Willi Resetarits & Stubnblues: Blotz in da Vitrin signature.asc Description: Digital Signature
Bug#838203: valgrind: unusable on armhf: assertion 'sizeof(TTEntryC) <= 88' failed
Package: valgrind Version: 1:3.12.0~svn20160714-1+b1 Severity: important Dear Maintainer, I've just attempted to use valgrind on the armel porterbox, harris.debian.org. Here's what I got: ->8 $ valgrind ls ==29583== Memcheck, a memory error detector ==29583== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==29583== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==29583== Command: ls ==29583== valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) <= 88' failed. Segmentation fault -8< -- System Information: Debian Release: 8.0 Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages valgrind depends on (semi-manually compiled list from the porterbox): $ dpkg -l | grep libc ii libc-bin 2.24-2 ii libc-dev-bin 2.24-3 ii libc-l10n 2.24-2 ii libc6:armhf2.24-3 ii libc6-dbg:armhf2.24-3 ii libc6-dev:armhf2.24-3 ii libc6 2.23-1 ii libc6-dbg 2.23-1
Bug#838204: jackrabbit: CVE-2016-6801: CSRF in Jackrabbit-Webdav using empty content-type
Source: jackrabbit Version: 2.3.6-1 Severity: important Tags: security upstream fixed-upstream Hi, the following vulnerability was published for jackrabbit. CVE-2016-6801[0]: CSRF in Jackrabbit-Webdav using empty content-type For the 2.12.x this has been fixed upstream in 2.12.3, cf. [1], and there are patches for older branches as well. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2016-6801 [1] https://marc.info/?l=oss-security&m=147386022804406&w=2 Regards, Salvatore
Bug#837786: mutter: Issues repainting the display on mouse movement
Hi I have run into the same problem. I can't add anything, only video of how it looks like on my system: https://youtu.be/4Fxuzm-FvbE Marek
Bug#838205: psutils FTCBFS: uses build architecture compiler
Source: psutils Version: 1.17.dfsg-3 Tags: patch User: helm...@debian.org Usertags: rebootstrap psutils fails to cross build from source, because it uses the build architecture compiler. Even though cdbs passes a suitable CC environment variable, the upstream build system chooses to override that. After passing CC as a command line variable, the cross build succeeds. Please consider applying the attached patch. Helmut diff --minimal -Nru psutils-1.17.dfsg/debian/changelog psutils-1.17.dfsg/debian/changelog --- psutils-1.17.dfsg/debian/changelog 2016-08-27 03:59:27.0 +0200 +++ psutils-1.17.dfsg/debian/changelog 2016-09-18 14:41:23.0 +0200 @@ -1,3 +1,10 @@ +psutils (1.17.dfsg-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Pass CC as a cmdline option to make. (Closes: #-1) + + -- Helmut Grohne Sun, 18 Sep 2016 14:41:00 +0200 + psutils (1.17.dfsg-3) unstable; urgency=medium * Orphan package diff --minimal -Nru psutils-1.17.dfsg/debian/rules psutils-1.17.dfsg/debian/rules --- psutils-1.17.dfsg/debian/rules 2016-08-27 03:59:27.0 +0200 +++ psutils-1.17.dfsg/debian/rules 2016-09-18 14:40:56.0 +0200 @@ -4,6 +4,10 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk +include /usr/share/dpkg/architecture.mk +ifeq ($(origin CC),default) +CC = $(DEB_HOST_GNU_TYPE)-gcc +endif # Include cdbs rules files. include /usr/share/cdbs/1/class/makefile.mk @@ -11,7 +15,7 @@ CURDIR := $(shell pwd) DEB_MAKE_CLEAN_TARGET = realclean -DEB_MAKE_BUILD_TARGET = prefix=/usr all +DEB_MAKE_BUILD_TARGET = prefix=/usr CC=$(CC) all DEB_MAKE_INSTALL_TARGET = prefix=$(CURDIR)/debian/psutils/usr \ MANDIR=$(CURDIR)/debian/psutils/usr/share/man/man1 \ install
Bug#838206: linux-image-4.7.0-1-amd64: [Linux Kernel 4.7] Power issue: Intel i7 CPU frequency get maxed on display idle
Package: src:linux Version: 4.7.2-1+s1 Severity: important Hello, I'm facing a power issue with the Linux 4.7 kernel. Every time the system goes idle (the configured delay passes and the display goes black), the frequency of all cores get maxed, even if all cores are idle. Evident symptoms are the fan spinning loudly and the errors logged in journal stating the thermal threshold being surpassed and the CPU throttled. In detail, the frequency of all cores raises from ~800 MHz to 2.6 GHz for all 8 cores of my i7. I can reproduce the behavior 100% of times, by connecting via ssh to the affected system and launching powertop. The issue does not exists in Linux 4.6 (to wich I will stick for now), so I guess the problem resides in kernel, not in other packages. You have all system information here below (gathered by repotbug). Ask any further info if needed. Thank you! -- Alessio Gaeta -- Package-specific info: ** Version: Linux version 4.7.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 20160803 (Debian 5.4.1-1) ) #1 SMP Debian 4.7.2-1 (2016-08-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=UUID=325f7845-cb20-4f45-9328-6a9ce9133f5a ro acpi_backlight=vendor quiet ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded (currently expected). ** Kernel log: [4.649062] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [4.649104] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [4.649285] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [4.650851] asus_wmi: ASUS WMI generic driver loaded [4.652548] asus_wmi: Initialization: 0x1 [4.652753] asus_wmi: SFUN value: 0x1a0af7 [4.653693] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input17 [4.662844] asus_wmi: Number of fans: 0 [4.669120] acpi_call: module verification failed: signature and/or required key missing - tainting kernel [4.677496] Non-volatile memory driver v1.3 [4.718296] ath: phy0: Enable LNA combining [4.720944] ath: phy0: ASPM enabled: 0x42 [4.720953] ath: EEPROM regdomain: 0x60 [4.720956] ath: EEPROM indicates we should expect a direct regpair map [4.720961] ath: Country alpha2 being used: 00 [4.720964] ath: Regpair used: 0x60 [4.725655] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [4.725958] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xc900010c, irq=17 [4.750243] [drm] Memory usable by graphics device = 2048M [4.750248] [drm] Replacing VGA console driver [4.750890] Console: switching to colour dummy device 80x25 [4.756320] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [4.756323] [drm] Driver supports precise vblank timestamp query. [4.758406] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem [4.758974] intel_rapl: Found RAPL domain package [4.758977] intel_rapl: Found RAPL domain core [4.758979] intel_rapl: Found RAPL domain uncore [4.778466] ACPI: Video Device [GFX0] (multi-head: yes rom: yes post: no) [4.778897] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4c/LNXVIDEO:00/input/input18 [4.779487] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [4.779909] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input19 [4.784877] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [4.892652] snd_hda_intel :00:1b.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.892659] [drm] Initialized i915 1.6.0 20160425 for :00:02.0 on minor 0 [4.893710] fbcon: inteldrmfb (fb0) is primary device [4.923758] random: nonblocking pool is initialized [4.982716] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null) [5.099244] Console: switching to colour frame buffer device 170x48 [5.101549] i915 :00:02.0: fb0: inteldrmfb frame buffer device [5.128538] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input15 [5.128596] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input16 [5.128647] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input20 [5.309850] bbswitch: version 0.8 [5.309860] bbswitch: Found integrated VGA device :00:02.0: \_SB_.PCI0.GFX0 [5.309866] bbswitch: Found discrete VGA device :01:00.0: \_SB_.PCI0.PEGR.GFX0 [5.309881] ACPI Warning: \_SB.PCI0.PEGR.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95) [5.310017] bbswitch: detected an Optimus _DSM function [5.310031] pci :01:00.0: enabling device ( -> 0003) [5.310090] bbswitch: Succesfully loaded. Discrete card :01:00.0 is on [5.310788] bbswitch: disabling discrete graphics [5.310798] ACPI Warning: \_SB
Bug#836588: [Cupt-devel] Bug#836588: cupt: FTBFS on armel/armhf: test failures
Control: tags -1 + unreproducible Hi Emilio, On 04.09.2016 12:17, Emilio Pozuelo Monfort wrote: > Your package failed to build on armel/armhf. Logs at > https://buildd.debian.org/status/package.php?p=cupt&suite=unstable Thank you for the report. I cannot reproduce the issue (that is, on the armhf porterbox harris.d.o the test suit passes). Any chance that at the time of the build some toolchain packages were in an inconsistent shape or had know issues? Can I do anything else with this bug before requesting to give-back the package on arhmf and armel?
Bug#838207: move pkg-config file zapojit-0.0.pc to a multiarch path
Source: libzapojit
Version: 0.0.3-1
Tags: patch
Control: affects -1 + src:gnome-online-miners
User: helm...@debian.org
Usertags: rebootstrap
gnome-online-miners fails to cross build from source, because it cannot
find zapojit-0.0.pc. During cross compilation, pkg-config does not
consider /usr/lib/pkgconfig. Please move zapojit-0.0.pc to a multiarch
path. The attached patch achieves that by adding a suitable --libdir.
Beyond moving the files it does not try to add more multiarch
capabilities, but that would be welcome nonetheless. Please consider
applying it.
Helmut
diff --minimal -Nru libzapojit-0.0.3/debian/changelog
libzapojit-0.0.3/debian/changelog
--- libzapojit-0.0.3/debian/changelog 2013-03-24 14:26:26.0 +0100
+++ libzapojit-0.0.3/debian/changelog 2016-09-18 14:49:31.0 +0200
@@ -1,3 +1,10 @@
+libzapojit (0.0.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Pass multiarch --libdir to configure. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 18 Sep 2016 14:49:10 +0200
+
libzapojit (0.0.3-1) unstable; urgency=low
* New upstream release.
diff --minimal -Nru libzapojit-0.0.3/debian/gir1.2-zpj-0.0.install
libzapojit-0.0.3/debian/gir1.2-zpj-0.0.install
--- libzapojit-0.0.3/debian/gir1.2-zpj-0.0.install 2012-06-25
04:13:44.0 +0200
+++ libzapojit-0.0.3/debian/gir1.2-zpj-0.0.install 2016-09-18
14:52:28.0 +0200
@@ -1 +1 @@
-usr/lib/girepository-1.0/*.typelib
+usr/lib/*/girepository-1.0/*.typelib
diff --minimal -Nru libzapojit-0.0.3/debian/libzapojit-0.0-0.install
libzapojit-0.0.3/debian/libzapojit-0.0-0.install
--- libzapojit-0.0.3/debian/libzapojit-0.0-0.install2012-06-25
03:57:22.0 +0200
+++ libzapojit-0.0.3/debian/libzapojit-0.0-0.install2016-09-18
14:49:42.0 +0200
@@ -1 +1 @@
-usr/lib/libzapojit*.so.*
+usr/lib/*/libzapojit*.so.*
diff --minimal -Nru libzapojit-0.0.3/debian/libzapojit-dev.install
libzapojit-0.0.3/debian/libzapojit-dev.install
--- libzapojit-0.0.3/debian/libzapojit-dev.install 2012-06-25
03:57:22.0 +0200
+++ libzapojit-0.0.3/debian/libzapojit-dev.install 2016-09-18
14:49:51.0 +0200
@@ -1,4 +1,4 @@
usr/include/libzapojit-*/zpj/
-usr/lib/libzapojit*.so
-usr/lib/pkgconfig/zapojit*
+usr/lib/*/libzapojit*.so
+usr/lib/*/pkgconfig/zapojit*
usr/share/gir-1.0/*.gir
diff --minimal -Nru libzapojit-0.0.3/debian/rules libzapojit-0.0.3/debian/rules
--- libzapojit-0.0.3/debian/rules 2012-06-25 03:57:22.0 +0200
+++ libzapojit-0.0.3/debian/rules 2016-09-18 14:49:07.0 +0200
@@ -1,5 +1,6 @@
#!/usr/bin/make -f
+include /usr/share/dpkg/architecture.mk
include /usr/share/cdbs/1/class/autotools.mk
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/rules/utils.mk
@@ -14,3 +15,5 @@
common-binary-predeb-arch:: list-missing
DEB_DH_MAKESHLIBS_ARGS_$(libzapojit) = -- -c4
+
+DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
Bug#834249: openbabel: diff for NMU version 2.3.2+dfsg-2.4
Control: tags 834249 + pending Dear maintainer, I've prepared an NMU for openbabel (versioned as 2.3.2+dfsg-2.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Cássia Eller: Top Top diff -Nru openbabel-2.3.2+dfsg/debian/changelog openbabel-2.3.2+dfsg/debian/changelog --- openbabel-2.3.2+dfsg/debian/changelog 2016-08-02 11:44:00.0 +0200 +++ openbabel-2.3.2+dfsg/debian/changelog 2016-09-18 14:49:09.0 +0200 @@ -1,3 +1,11 @@ +openbabel (2.3.2+dfsg-2.4) unstable; urgency=medium + + * Non-maintainer upload. + * Fix "FTBFS in testing": build with -std=gnu++98. +(Closes: #834249) + + -- gregor herrmann Sun, 18 Sep 2016 14:49:09 +0200 + openbabel (2.3.2+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. diff -Nru openbabel-2.3.2+dfsg/debian/rules openbabel-2.3.2+dfsg/debian/rules --- openbabel-2.3.2+dfsg/debian/rules 2014-09-20 14:29:56.0 +0200 +++ openbabel-2.3.2+dfsg/debian/rules 2016-09-13 23:07:32.0 +0200 @@ -11,6 +11,7 @@ export CFLAGS := $(shell dpkg-buildflags --get CFLAGS) $(CPPFLAGS) export CXXFLAGS := $(shell dpkg-buildflags --get CXXFLAGS) $(CPPFLAGS) export LDFLAGS := $(shell dpkg-buildflags --get LDFLAGS) +export DEB_CXXFLAGS_MAINT_APPEND = -std=gnu++98 DH_AUTO_CONFIGURE_OPTS := -DCMAKE_BUILD_TYPE=None \ -DPYTHON_BINDINGS=ON -DPERL_BINDINGS=ON \ signature.asc Description: Digital Signature
Bug#836903: RFS: qevercloud/3.0.2+ds-1 [ITP] -- Unofficial Evernote Cloud API library for Qt
Hello,
2016-09-17 22:31 GMT+08:00 Sean Whitton :
> Hello Boyuan,
>
> On Wed, Sep 14, 2016 at 12:23:48PM +0800, Boyuan Yang wrote:
>> Yes, they are up-to-date now. The package on debian-mentors is also
>> updated.
>
> The packaging is in great shape. Here's a review for you.
Thank you for your detailed review!
All the statements below are fixed/adjusted.
> Must-fixes:
> ---
>
> 1. The changelog entry won't close the ITP unless you put a # in front of
> the bug number!
That is indeed my mistake. Fixed.
> 2. We need to test building something against your new shared library,
> and we'll need to confirm that the right dependencies get generated for
> it by dpkg-shlibdeps. If you haven't done so already, could you update
> your nixnote packaging to use your new qevercloud shlib, please?
The new version (2.0~beta9+dfsg-1) was pushed to GitHub, mentors
and debomatic-amd64.
Source package changed (ds -> dfsg) due to unclear license status (as
discussed previously in nixnote2 RFS).
> 3. In a recent commit you renamed debian/{*.symbols => *.symbols.amd64}.
> So now you are not providing any symbols files for other architectures.
> But for a shared library, you need to provide a symbols or shlibs file
> for all the reasons described in ch. 8 of the Debian Policy Manual.
>
> I assume that you did this rename because the symbols files is
> architecture-dependent. That probably means it's very fragile: changes
> which don't break the ABI might change the symbols file. This is a
> known issue with C++ shared libs.[1]
It was indeed because of architecture-dependent symbols of C++.
>
> You need to make the symbols file less fragile (some suggestions
> involving sed(1) here[2]) so that it will work for all archs, or switch
> to a shlibs file instead. README.md suggests that upstream is aware of
> the issue of ABI compatibility, so shlibs files might be enough.
Anyway I switched to shlibs using dh_makeshlibs. It is reasonable for
this package to depend on upstream to keep ABI comaptibility, but I
will also try to test symbol files on each release (even it is not included
in the tarball, it can be stored in the git history).
> Suggestions:
>
>
> 1. Please add Forwarded: headers to the patches.
Added (mostly Forwarded: not-needed).
> 2. It seems like debhelper's cmake buildsystem
> (/usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm) should handle
> what your 0001 patch does. Are there situations where we wouldn't want
> GNUInstallDirs? If not, please submit a bug against debhelper.
I was trying to bypass problem No.12 using this patch but failed. After that
I forgot to remove this patch (since it will not harm anything).
This patch is removed now.
> 3. README.md suggests that there is doxygen documentation available for
> generation and install. Please consider installing this in a new
> qevercloud-doc binary package.
The new qevercloud-doc added.
I dropped the tex / pdf / postscript files in the -doc package because
they are not that
useful when html files are provided as well.
> 4. Since you added a "Section:" field to each binary package, the
> "Section: libs" at the top of the file does nothing. Better to remove
> it.
Now I declared the Section in the source package section and removed
the duplicated Section:libs in binary packages.
> 5. Since debhelper 10 has just been released, consider using compat
> level 10.
Just switched.
> 6. Are you sure you need the debian/*.dirs files? Have you tried
> building without them? They are very rarely necessary these days.
Those files are leftovers from original upstream debian packaging
scripts and are (of course) not useful at all in this situation.
Now removed.
> 7. In your rules file you make a lot of explicit calls to dh_auto_*.
> When you do something like this
>
> override_dh_auto_clean:
> dh_auto_clean
> rm -rf $(_QEVERCLOUD_QT5_BUILDDIR)
>
> it's fine, because it's clear to a reader that you are appending to an
> automatic command. However, when you do this:
>
> custom_regenerate_source_code:
> (cd $(_QEVERCLOUD_GENERATOR_DIR); cmake .;)
> dh_auto_build --buildsystem=makefile -- -C
> $(_QEVERCLOUD_GENERATOR_DIR)
> mkdir -p QEverCloud/src/generated
> etc.
>
> the dh_auto_build line is quite hard to understand -- someone would need
> to look up the makefile buildsystem. It would be better to replace that
> with an explicit call to $(MAKE). In dh_auto_build(1) it says "If it
> doesn't work, you're encouraged to skip using dh_auto_build at all, and
> just run the build process manually."
That is reasonable indeed. Switched to call $(MAKE).
> 8. Perhaps rename custom_regenerate_source_code to include the name of
> what you're regenerating, e.g. custom_regenerate_from_thrift.
A meaningful name can be helpful. Fixed.
> 9. Your rules file contains some very long lines. Consider inserting
> line breaks between long arguments.
Lines has been wrapped inside 80
Bug#838199: freeorion-data: Cannot upgrade to 0.4.6~RC1-1 in unstable if kodi is installed, too.
Control: reassign -1 fonts-roboto-hinted On 18.09.2016 13:26, Christian Klein wrote: > Package: freeorion-data > Version: 0.4.5+git20160707-2 > Severity: important > > I cannot upgrade freeorion to 0.4.6~RC1-1 in unstable, as it depends on fonts- > roboto-unhinted. The problem is that I have installed the kodi package, which > depends on fonts-roboto-hinted. However, fonts-roboto-hinted conflicts with > fonts-roboto-unhinted. Hence only one of these packages can be installed. > > > Version 0.4.5+git20160707-2 (currently in testing) does not depend on fonts- > roboto-*. > > P.S.: I'm not sure if this ticket should be filed against freeorion, kodi or > fonts-roboto. I'm also not sure what's the right severity for a dependency > problem. Hello, thanks for the report. I can rule out that this is a bug in kodi or freeorion. In my opinion fonts-roboto-hinted should not conflict with fonts-roboto-unhinted because both packages provide different files in different directories. Hence I'm going to reassign the bug to fonts-roboto-hinted. If the package was split some time ago then using a versioned Breaks + Replaces is usually the preferred solution. Just conflicting seems wrong in this case. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#838203: valgrind: unusable on armhf: assertion 'sizeof(TTEntryC) <= 88' failed
On Sun, 2016-09-18 at 14:44 +0200, Eugene V. Lyubimkin wrote: > Package: valgrind > Version: 1:3.12.0~svn20160714-1+b1 > Severity: important > > Dear Maintainer, > > I've just attempted to use valgrind on the armel porterbox, > harris.debian.org. Here's what I got: > > ->8 > $ valgrind ls > ==29583== Memcheck, a memory error detector > ==29583== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. > ==29583== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright > info > ==29583== Command: ls > ==29583== > > valgrind: m_transtab.c:2459 (vgPlain_init_tt_tc): Assertion 'sizeof(TTEntryC) > <= 88' failed. > Segmentation fault > -8< This is upstream valgrind svn r15912: Fix incorrect assertion re sizeof TTEntryC on arm-linux. Fixes #362935. https://bugs.kde.org/show_bug.cgi?id=362935
Bug#837742: diffoscope: debian/tests/basic-command-line fails
control: tag -1 pending On Wed, Sep 14, 2016 at 08:49:27PM +1200, Michael Hudson-Doyle wrote: > On 14 September 2016 at 17:03, Mattia Rizzolo wrote: > > Be aware that that's not the only thing failing there. I > > failed to debug that last time, and I wanted to actually try it again > > with more time resources for the next upload. > > > > I've had a poke at this and the "'nm' not available in path. Falling back > to binary comparison' clued me into the difference: binutils is already > installed in the testbed for the debian tests but not the Ubuntu ones (for > the successful run of the pytest test, both binutils and binutils-multiarch > are installed as part of installing autopkgtest-satdep, but in Debian only > binutils-multiarch is). If I run the tests with adt-run --shell, wait for > the failing test and then log into the box and install binutils, the tests > then pass. > What I can't say is whether this indicates a bug in diffoscope or just that > these tests should be skipped if nm is not there... diffoscope behaves as expected here: it doesn't fail. Just that the tests are expecting it to do a successful "full" comparison by unpacking the ar archive, but lacking nm, it can only a boring binary comparison. So, I've instructed those tests to be skipped when nm is missing. It's hard to notice them, nm is in binutils, and binutils is in build-essential. I really don't have a single chroot (or real system for what it matters) around here without build-essential installed :D Thank you! Now my plan is to get the tests to fully pass in jessie-backports too, and avoid things like this: https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?h=60_bpo8%2b1&id=8b803f7a67c1c788bc442e35d8c3ddce91ead871 Then I'll happily do another release :) [hint: this is a subtle invitation to help out ;)] -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#838208: libiodbc2 FTCBFS: uses build architecture pkg-config
Source: libiodbc2 Version: 3.52.9-2 Tags: patch User: helm...@debian.org Usertags: rebootstrap libiodbc2 fails to cross build from source, because it uses the build architecture pkg-config. Thus it fails finding gtk and that results in missing files. It seems that ./admin/gtk-2.0.m4 has its own code for discovering which $PKG_CONFIG to use rather than using a standard autoconf macro. Thus it does not default to use the triplet-prefixed pkg-config and does not consider the PKG_CONFIG environment variable either. The attached patch forces the right pkg-config via the corresponding cache variable. Please consider applying the patch or fixing the .m4 file to use standard (working) checks. Helmut diff --minimal -Nru libiodbc2-3.52.9/debian/changelog libiodbc2-3.52.9/debian/changelog --- libiodbc2-3.52.9/debian/changelog 2014-05-29 13:06:37.0 +0200 +++ libiodbc2-3.52.9/debian/changelog 2016-09-18 15:16:20.0 +0200 @@ -1,3 +1,10 @@ +libiodbc2 (3.52.9-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Force using triplet-prefixed pkg-config. (Closes: #-1) + + -- Helmut Grohne Sun, 18 Sep 2016 15:09:02 +0200 + libiodbc2 (3.52.9-2) unstable; urgency=medium * Set SYSTEM_DIR to the odbc multiarch path. (Closes: #749427) diff --minimal -Nru libiodbc2-3.52.9/debian/rules libiodbc2-3.52.9/debian/rules --- libiodbc2-3.52.9/debian/rules 2014-05-29 13:06:37.0 +0200 +++ libiodbc2-3.52.9/debian/rules 2016-09-18 15:14:11.0 +0200 @@ -1,8 +1,9 @@ #!/usr/bin/make -f -DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +include /usr/share/dpkg/architecture.mk export DEB_CFLAGS_MAINT_APPEND = -DSYSTEM_DIR=\"/usr/lib/$(DEB_HOST_MULTIARCH)/odbc\" +export ac_cv_path_PKG_CONFIG=$(DEB_HOST_GNU_TYPE)-pkg-config %: dh $@ --parallel --with autoreconf,pkgkde_symbolshelper
Bug#837264: libsys-info-base-perl: FTBFS: Couldn't do SPEC: No such file or directory at builder/lib/Build.pm line 42.
Control: tag -1 patch
On Sat, Sep 10, 2016 at 09:23:30AM +0200, Lucas Nussbaum wrote:
> Source: libsys-info-base-perl
> Version: 0.7804-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160910 qa-ftbfs
> Justification: FTBFS on amd64
> > Couldn't do SPEC: No such file or directory at builder/lib/Build.pm line 42.
> > /usr/share/cdbs/1/class/perl-build.mk:68: recipe for target 'Build' failed
The attached patch fixes this. It's probably a bit early for pushing
this upstream as cwd removal from @INC isn't done in upstream Perl yet
(it's currently slated for 5.26).
--
Niko Tyni nt...@debian.org
>From d37e8eaa84e91c03b3f15ab873cc081152dd8b39 Mon Sep 17 00:00:00 2001
From: Niko Tyni
Date: Sun, 18 Sep 2016 16:23:59 +0300
Subject: [PATCH] Make the build process work without cwd in @INC
Bug-Debian: https://bugs.debian.org/837264
---
builder/lib/Build/Spec.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builder/lib/Build/Spec.pm b/builder/lib/Build/Spec.pm
index 394132a..1808fc5 100644
--- a/builder/lib/Build/Spec.pm
+++ b/builder/lib/Build/Spec.pm
@@ -15,7 +15,7 @@ BEGIN {
sub spec {
my %opt = @_;
-my $file = 'SPEC';
+my $file = './SPEC';
my $spec = do $file;
my %rv =
--
2.9.3
Bug#837786: mutter: Issues repainting the display on mouse movement
Hello, another datapoint: I'm experiencing the same issue on an AMD Pitcairn (7870) using radeonsi. -- M
Bug#823100: ghostscript: includes two files claimed to be under a non-free Unicode license
Hi Francesco, Quoting Francesco Poli (wintermute) (2016-04-30 21:32:26) > I noticed that two files included in the ghostscript source package > are documented in the debian/copyright file as distributed under the > terms of a non-free Unicode license. > > The two files are: > > Files: base/ConvertUTF.c >base/ConvertUTF.h > Copyright: 2001-2004, Unicode, Inc > License: Unicode [...] > At the very least, this license does not grant any permission to > modify the files (thus failing DFSG#3). Moreover, the license grant > seems to attempt to restrict use to "products supporting the Unicode > Standard" (thus failing DFSG#6). > See also https://lists.debian.org/debian-legal/2015/12/msg0.html > where an FTP Assitant confirmed that files which restrict "use to only > that of implementing a standard" are not fit for Debian main. > > Therefore, the two files under discussion appear to be non-free. Seems you are right. > However, this issue could possibly be easy to solve. > If Unicode Inc has published new versions of the two files in > more recent times, the updated versions should be under the > current unicode.org public license, as explained in > http://www.unicode.org/copyright.html#Exhibit1 > > Please check whether newer versions of those files are released > in one of the Unicode web site areas mentioned in the cited Exhibit1. > The newer versions could perhaps be used as replacements for the > non-free ones. Unfortunately, upstream seems to have _dropped_ the code due to being buggy and unmaintained since 2004, according to http://unicode.org/forum/viewtopic.php?f=9&t=90 - summarized at http://stackoverflow.com/questions/2685004/why-does-unicode-org-no-longer-offer-a-reference-utf-8-16-32-converter Above forum discussion mentions only version numbers (up to 1.4 and a possible alpha of 1.5), the year I found by looking at latest available snapshot of the code at archive.org and the timestamps of that page: https://web.archive.org/web/20081228105917/http://www.unicode.org/Public/PROGRAMS/CVTUTF/ This gets worse: Seems many more packages embed this code: https://codesearch.debian.net/search?q=ConversionResult+ConvertUTF8toUTF16 I have reported this upstream. Will register at the secure-testing team as a case of Embedded Code Copy as well. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#837873: Headers Needed by android-platform-external-libunwind
The header files needed when building android-platform-external-libunwind includes: * 7zCrc.h * 7zTypes.h * Sha256.h * Xz.h * XzCrc64.h
Bug#837751: Fwd: [mat...@debian.org: Re: Bug#837751: scribus: When I try to do "get Image" for a graphics frame, scribus segfaults]
Dear Mattia, Yes, I'm the same person. I don't know why CERN mailer does not accept your address. However, some time ago the same happened to my University e-mail - I couldn't send e-mail to any CERN address. Regarding the bug - the problem has also disappeared in the affected system. I'm afraid it could be caused by a partial update? After I've performed the next "apt-get update; apt-get dist-upgrade", I was not able to reprodecue this bug any more. So probably you can mark this bug as "fixed" or even as "invalid". With best regards, Wojtek On 18.09.2016 14:13, Mattia Rizzolo wrote: The cern.ch SMTP doesn't like my mail setup (or I wonder anybody's, if the issue is that the debian.org domain has no SPF record..) See the bounce I received: https://volatile.mapreri.org/2016-09-18/6d35f3e5d7186d5276b26ef8760628cb/Inbox.pdf So I'm forwarding your email to your other address, assuming you are the same person :) If you reply to this email, please put the bug address in CC. - Forwarded message from Mattia Rizzolo - Date: Sun, 18 Sep 2016 10:03:33 + From: Mattia Rizzolo To: Wojciech Zabolotny Cc:837...@bugs.debian.org Subject: Re: Bug#837751: scribus: When I try to do "get Image" for a graphics frame, scribus segfaults Message-ID:<20160918100333.7ivomcgoblhak...@chase.mapreri.org> User-Agent: Every email client sucks, this one just sucks less. On Wed, Sep 14, 2016 at 04:40:57PM +0200, Wojciech Zabolotny wrote: I assume by your "whenever" that it is steadily reproducible. Can you try to temporary move away your ~/.scribus and see if the bug is reproducible? Indeed, renaming of ~/.scribus has cured the problem. I couldn't reproduce the segfault with your .sla, and if I looked up the upstream bug tracker correctly nobody else experienced segfaults recently. According to the core dump the crash happens somewhere in the middle of dbus, and I couldn't even figure how it reached that point (here gdb says "Backtrace stopped: previous frame inner to this frame (corrupt stack?)" after #14). Anyway, I'm tempted to close this bug as it was really easily "fixed" by moving away your ~/.scribus directory. probably some file in there somehow was corrupted or got invalid data in your computer. -- Wojciech M Zabolotny, PhD Faculty Coordinator for International Student Mobility Faculty of Electronics and Information Technology Warsaw University of Technology
Bug#838206: linux-image-4.7.0-1-amd64: [Linux Kernel 4.7] Power issue: Intel i7 CPU frequency get maxed on display idle
Control: tag -1 moreinfo On Sun, 2016-09-18 at 14:46 +0200, Alessio Gaeta wrote: > Package: src:linux > Version: 4.7.2-1+s1 > Severity: important > > Hello, > > I'm facing a power issue with the Linux 4.7 kernel. > > Every time the system goes idle (the configured delay passes and the display > goes black), the frequency of all cores get maxed, even if all cores are idle. > > Evident symptoms are the fan spinning loudly and the errors logged in journal > stating the thermal threshold being surpassed and the CPU throttled. > > In detail, the frequency of all cores raises from ~800 MHz to 2.6 GHz for all > 8 > cores of my i7. I can reproduce the behavior 100% of times, by connecting via > ssh to the affected system and launching powertop. > > The issue does not exists in Linux 4.6 (to wich I will stick for now), so I > guess the problem resides in kernel, not in other packages. > > You have all system information here below (gathered by repotbug). Ask any > further info if needed. Thank you! [...] Please test with bbswitch and acpi_call removed. Ben. -- Ben Hutchings Klipstein's 4th Law of Prototyping and Production: A fail-safe circuit will destroy others. signature.asc Description: This is a digitally signed message part
Bug#838209: ITP: sejda -- command line tool to manipulate PDF documents
Package: wnpp Owner: Andrea Vacondio Severity: wishlist * Package name: sejda Version : 2.6.0 Upstream Author : Andrea Vacondio * URL : http://www.sejda.org/ * License : (AGPLv3) Programming Lang: (Java) Description : command line tool to manipulate PDF documents Sejda is a java library and command line interface providing a set of tasks (split, merge, rotate, crop, compress, etc...) to manipulate existing PDF documents. It's very active, particularly important considering the upcoming PDF 2.0 spec, and maintained on GitHub ( https://github.com/torakiki/sejda). It provides a long list of PDF tasks http://www.sejda.org/development/available-tasks/ and it's battle tested as PDF engine for the open source desktop tool called PDFsam ( http://www.pdfsam.org) and the online service https://www.sejda.com/
Bug#782075: gnome-tweak-tool: Crashes Gnome when reducing Number of Workspaces
control: found -1 mutter/3.21.91-2 Hi Andreas Henriksson, I think I found how to reproduce this: In a freshly installed Stretch system (my main machine) this happens only if you've set in the Gnome Tweak Tool: Desktop - Icons on Desktop - On After this as previously described: Workspaces - Workspace Creation - Static Workspaces - Number of Workspaces - Reduce by one --> the Desktop wallpaper gets black for a short time, then everything is back to normal. Workspaces - Number of Workspaces - Reduce by one --> Gnome session crashes Further observations from my fresh installation tests on my main machine: New Jessie installation, no changes --> crash reproducible Update to Stretch, still no changes --> no crash
Bug#829076: general: Random freezes but the mouse can still move
Hi John, On Thu, 30 Jun 2016 11:37:24 +0200 John wrote: > Package: general > Severity: grave > Justification: causes non-serious data loss > > I'm running the current 64-bit Debian with the Cinnamon desktop and have been experiencing 'freezes' for about > a month now. The mouse still moves around but clicking on any window produces no response. However right-clicking > on any window (eg Firefox) brings up the context menu for the desktop!?This looks more like a bug in the window manager rather than a general bug. I'd recommend to reassign it. > > I run a twin-screen set-up and looking at the screens which were timed-out I noticed that the times on the two > screens were different! One was reading 11:03 and the other 11:16!Like if one of the screens stop updating? > > After a few minutes both screens were frozen and I had to Ctrl+Alt+F1, kill the x-session-manager which resulted > in the login screen and the system wsudo gedit /var/log/syslogas usable again.. > > >From this I conclude that the problem is OS-related and not driver-related (as a twin-screen set-up is configured > in the OS).From this I conclude that the OS part (kernel and basic utilities) are still running correctly but the window manager stops dispatching events, maybe due to a buggy program catching the focus and incorrectly handling the X events. I'd recommend again to reassign this bug to the window manager package. There you will probably find a better chance to get help. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#837145: libsdl-perl: autopkgtest failure: t/core_audiospec.t Bad plan
On Fri, Sep 09, 2016 at 11:00:32AM +0300, Niko Tyni wrote: > Package: libsdl-perl: > Version: 2.546-2 > User: debian-p...@lists.debian.org > Usertags: autopkgtest > > This package is failing its autopkgtest checks on current sid. > > I haven't really found out what's happening yet, but it may be caused > by perl 5.22.2-4, which removed cwd from @INC. Nope, the regression is caused by something starting to pull in the separate libtest-simple-perl package. > t/core_audiospec.t .. skipped: (no reason given) > [...] > > t/core_audiospec.t(Wstat: 0 Tests: 10 Failed: 0) > Parse errors: Bad plan. You planned 0 tests but ran 10. The test script breaks with newer versions of Test::More. We don't see it in builds because it only gets run when AUTOMATED_TESTING=1, which is the case with pkg-perl-autopkgtest but not with regular builds. It looks like Test::More is internally counting the test cases it has seen, but threading breaks this with newer versions of Test::More. This is not supposed to happen: Test::More et al advertise multiple thread support. I haven't managed to distill it down to a simple test case. I suspect it's something to do with the way SDL XS code uses threads. For now, I suggest we set AUTOMATED_TESTING=0 in debian/tests/pkg-perl/smoke-env, even if that's somewhat unsatisfactory. -- Niko Tyni nt...@debian.org
Bug#824429: libc6: In certain locale combinations mbsrtowcs cannot recover from EILSEQ
tags 824429 upstream forwarded 824429 https://sourceware.org/bugzilla/show_bug.cgi?id=20617 thanks * Christoph Biedl: > It might be questionable whether this is a bug in glibc at all. But at > least it's surprising behaviour. > > The reproducer below calls mbstowcs two times, first time with > an illegal UTF-8 sequence, second time a correct one. > > Now if the caller's environment is set to something UTF-8-ish like > "en_US.UTF-8" or "de_DE.UTF-8", also the second and any further > mbsrtowcs invocation fail with EILSEQ. Note setting LC_CTYPE to an > empty string is also required to make this happen. POSIX and C11 explicitly say that the conversion state is undefined after EILSEQ. There does not appear to be a way to reset the internal (global) conversion state used by mbsrtowcs, so a NULL argument for the conversion state pointer is rarely useful. We should probably add a warning in glibc for that case. Filed upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=20617
Bug#838210: fuel-umm: fails to install: fuel-umm.postinst: cannot create /etc/init/rc-sysinit.override: Directory nonexistent
Package: fuel-umm Version: 9.0+dfsg1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package fuel-umm. (Reading database ... (Reading database ... 6852 files and directories currently installed.) Preparing to unpack .../fuel-umm_9.0+dfsg1-2_all.deb ... Unpacking fuel-umm (9.0+dfsg1-2) ... Setting up fuel-umm (9.0+dfsg1-2) ... /var/lib/dpkg/info/fuel-umm.postinst: 6: /var/lib/dpkg/info/fuel-umm.postinst: cannot create /etc/init/rc-sysinit.override: Directory nonexistent dpkg: error processing package fuel-umm (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: fuel-umm cheers, Andreas fuel-umm_9.0+dfsg1-2.log.gz Description: application/gzip
Bug#521781: Re: Bug#521781: atop logrotate job stops system process accounting
close #521781 thanks On Sun, Aug 07, 2016 at 04:36:56PM +0200, Marc Haber wrote: > In the absense of this information, I'm going to close this bug by the > end of August 2016. Doing so now. Greetings MArc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#833997: atop: process accounting does not work
Hi Martin,
do you still see this issue? Upstream wants to know whether:
- does atopacctd runs as a process at that time?
- what is its state ('ps -l' output about atopacctd)?
- what is the output of the command "ls -l /var/run/pacct_*" ?
I currently have the case on a system that just has been recently
rebooted:
[2/426]mh@testsid99:~$ uptime
16:42:45 up 3:11, 1 user, load average: 0,00, 0,00, 0,00
[3/427]mh@testsid99:~$ pgrep atopacctd
688
[4/428]mh@testsid99:~$ ps -l 688
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD
5 S 0 688 1 0 60 -20 - 1046 - ? 0:00
/usr/sbin/atopacctd
[5/429]mh@testsid99:~$ ls -l /run/pacct_s*
-rw--- 1 root root 0 Sep 18 13:31 /run/pacct_source
/run/pacct_shadow.d:
total 4,0K
-rw-r--r-- 1 root root 0 Sep 18 13:31 00.paf
-rw-r--r-- 1 root root 7 Sep 18 13:31 current
[6/430]mh@testsid99:~$
ATOP - testsid99 2016/09/18
16:43:56 -
5s elapsed
PRC | sys0.00s | user 0.00s | | | #proc
92 | #trun 1 | #tslpi97 | #tslpu 0 | #zombie0 | clones
0 | | | no procacct |
CPU | sys 0% | user 0% | irq 0% | |
| idle200% | wait 0% | | steal 0% | guest 0%
| | curf 2.19GHz | curscal ?% |
CPL | avg10.00 | | avg50.00 | avg15 0.00 |
| | csw 92 | | intr 68 |
| | numcpu 2 | |
MEM | tot 1.0G | free 167.2M | cache 714.2M | dirty 0.0M | buff
21.5M | slab 64.7M | slrec 55.3M | shmem 3.0M | shrss 0.0M | shswp
0.0M | vmbal 0.0M | hptot 0.0M | hpuse 0.0M |
SWP | tot 1.2G | free1.2G | | |
| | | | |
| vmcom 118.6M | | vmlim 1.7G |
NET | transport | tcpi 1 | tcpo 1 | udpi 0 | udpo
0 | tcpao 0 | tcppo 0 | | tcprs 0 | tcpie 0
| tcpor 0 | udpnp 0 | udpie 0 |
NET | network | ipi1 | | ipo1 | ipfrw
0 | deliv 1 | | | |
| icmpi 0 | | icmpo 0 |
NET | ens3 | sp0 Mbps | pcki 1 | pcko 1 | si0
Kbps | so1 Kbps | | coll 0 | mlti 0 | erri
0 | erro 0 | drpi 0 | drpo 0 |
Greetings
Marc
--
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#805370: Any answer from mpage upstream regarding the copyright situation?
Hi Adrian, I think that I forgot this issue. I will try contact the upstream. Thanks for your poke. Regards, Eriberto 2016-09-18 5:23 GMT-03:00 Adrian Bunk : > Hi Eriberto, > > in [1] you wrote that you will contact mpage upstream regarding the > copyright situation. > > Did you ever receive a reply? > > Thanks > Adrian > > [1] https://lists.debian.org/debian-legal/2015/10/msg00057.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 >
Bug#838211: general: black screen after suspending
Package: general Severity: important Dear Maintainer, Thanks and good work. I suspend my laptop to not miss work of the college, so, I just call him later and continue my work, it was expected. Sometimes, he turns on the screen, but, black screen, doesn't respond, and I have to restart it by force (which means, removing the battery and put again). So, most of my work isn't lost due to software that save automatically, but rather always lose. I use debian a short time and do not know what it can be. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#837946: also occurs with no action queued on startup
The previous backtrace was from the crash that comes about when previewing actions (even when none are queued). It also occurs when marking package for install/upgrade that create conflict, with following backtrace: > Thread 1 "aptitude" received signal SIGABRT, Aborted. > 0xf76f9d09 in __kernel_vsyscall () > @@gdb> bt > @gdb> #0 0xf76f9d09 in __kernel_vsyscall () > #1 0xf6c94c19 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54 > #2 0xf6c96117 in __GI_abort () at abort.c:89 > #3 0x567c0309 in subsumes (d2=..., d1=...) at > ../../../../src/generic/apt/apt.cc:1182 > #4 or_group_subsumes (d1=..., d2=..., cache=) at > ../../../../src/generic/apt/apt.cc:1205 > #5 0x567c2002 in internal_is_interesting_dep (cache=0x57fdba38, d=...) at > ../../../../src/generic/apt/apt.cc:1303 > #6 is_interesting_dep (d=..., cache=0x57fdba38) at > ../../../../src/generic/apt/apt.cc:1344 > #7 0x567e5865 in aptitude_resolver_version::dep_iterator::applicable > (dep=..., prv=..., prv_open=false, cache=0x57fdba38) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:283 > #8 0x567decda in aptitude_resolver_version::dep_iterator::applicable > (this=0xffe41e28) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:302 > #9 0x567dedb9 in aptitude_resolver_version::dep_iterator::normalize > (this=0xffe41e28) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:317 > #10 0x567e0095 in aptitude_resolver_version::dep_iterator::operator++ > (this=0xffe41e28) at > ../../../../src/generic/apt/aptitude_resolver_universe.cc:529 > #11 0x568ce9b7 in aptitude_universe::dep_iterator::operator++ > (this=) at > ../../../../src/generic/apt/aptitude_resolver_universe.h:1246 > #12 generic_problem_resolver::generic_problem_resolver > (this=, _step_score=, _broken_score= out>, _unfixed_soft_score=, infinity=, > _full_solution_score=, _unfixed_soft_cost=..., > _future_horizon=, _initial_state=..., _universe=...) at > ../../../../src/generic/problemresolver/problemresolver.h:3782 > #13 0x568bd73c in aptitude_resolver::aptitude_resolver (this=0x5994c268, > step_score=-10, broken_score=-100, unfixed_soft_score=-200, infinity=100, > resolution_score=50, unfixed_soft_cost=..., future_horizon=50, > _cost_settings=..., initial_installations=..., cache=0x57fdba38, > _policy=0x57e49e00) at ../../../../src/generic/apt/aptitude_resolver.cc:731 > #14 0x56837ac1 in resolver_manager::create_resolver (this=0x598206f0) at > ../../../../src/generic/apt/resolver_manager.cc:968 > #15 0x56839da3 in resolver_manager::maybe_create_resolver (this=0x598206f0, > consider_policybroken=false) at > ../../../../src/generic/apt/resolver_manager.cc:805 > #16 0x568772ae in resolver_manager::maybe_create_resolver (this=0x598206f0) > at ../../../../src/generic/apt/resolver_manager.h:474 > #17 0x56717d4a in sigc::internal::signal_emit0::emit > (impl=0x59820908) at /usr/include/sigc++-2.0/sigc++/signal.h:790 > #18 0x567b3b99 in sigc::signal0::emit (this=0x57fdbafc) at > /usr/include/sigc++-2.0/sigc++/signal.h:2705 > #19 sigc::signal0::operator() (this=0x57fdbafc) at > /usr/include/sigc++-2.0/sigc++/signal.h:2713 > #20 aptitudeDepCache::end_action_group (this=0x57fdba38, undo=0x599120a0) at > ../../../../src/generic/apt/aptcache.cc:2336 > #21 0x567b3f68 in aptitudeDepCache::action_group::~action_group > (this=0xffe42970, __in_chrg=) at > ../../../../src/generic/apt/aptcache.cc:195 > #22 0x567b4185 in aptitudeDepCache::mark_install (this=0x57fdba38, Pkg=..., > AutoInst=true, ReInstall=false, undo=0x599120a0) at > ../../../../src/generic/apt/aptcache.cc:1197 > #23 0x566967dd in pkg_item::do_select (this=0x599ba498, undo=0x599120a0) at > ../../src/pkg_item.cc:159 > #24 0x56696e66 in pkg_item::select (this=0x599ba498, undo=0x599120a0) at > ../../src/pkg_item.cc:165 > #25 0x566a5db3 in pkg_tree_node::dispatch_key (this=0x599ba498, k=..., > owner=0x57e28088) at ../../src/pkg_node.cc:54 > #26 0x56695793 in pkg_item::dispatch_key (this=0x599ba498, k=..., > owner=0x57e28088) at ../../src/pkg_item.cc:404 > #27 0xf7450f83 in cwidget::widgets::tree::handle_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #28 0x56687bab in menu_tree::handle_key (this=0x57e28088, k=...) at > ../../src/menu_tree.cc:430 > #29 0x566a94e1 in pkg_tree::handle_key (this=0x57e28088, k=...) at > ../../src/pkg_tree.cc:363 > #30 0xf7457b3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #31 0xf743d404 in cwidget::widgets::table::handle_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #32 0xf7457b3b in cwidget::widgets::widget::dispatch_key(cwidget::config::key > const&) () from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #33 0xf7425c38 in > cwidget::widgets::passthrough::handle_key(cwidget::config::key const&) () > from /usr/lib/i386-linux-gnu/libcwidget.so.3 > #34 0xf7457b3b in cwidge
