Bug#787151: fontconfig-config: 65-nonlatin.conf should have Takao font config
Package: fontconfig-config Version: 2.11.0-6.3 Severity: normal Dear Maintainer, Actually, 65-nonlatin.conf has a lot of font entries. But there is no entries for fonts-takao-gothic and fonts-takao-mincho. So we should add TakaoPMincho (for serif) and TakaoPGochic (for sans-serif) to 65-nonlatin.conf becasue fonts-takao package is already into debian/sid. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (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 fontconfig-config depends on: ii debconf [debconf-2.0] 1.5.56 ii fonts-dejavu-core 2.35-1 ii ucf3.0030 fontconfig-config recommends no packages. fontconfig-config suggests no packages. -- debconf information: fontconfig/subpixel_rendering: Automatic fontconfig/hinting_type: Native fontconfig/enable_bitmaps: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786982: jessie-pu: package libraw/0.16.0-9+deb8u1
Hi! On Thu, May 28, 2015 at 9:43 PM, Adam D. Barratt wrote: > In that case, please feel free to go ahead. Uploaded. Cheers. -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#783890: Merged upstream: Add skip-install-mime option to bundlebuilder
An upstream patch to the source package sugar-toolkit-gtk3 is available to help with this bug: https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/e8553c13a11e53ea78928ac4ab547b460eb22de5 -- James Cameron http://quozl.linux.org.au/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706065: libvte-2.90-common: /etc/profile.d/vte.sh is not sourced by interactive shells
Am 29.05.2015 um 08:52 schrieb Fabian Greffrath: > Good morning, > > Am Donnerstag, den 28.05.2015, 23:24 +0200 schrieb Michael Biebl: >> Yes, please. > > done, sorry for the mess. /o\ no worries. >> Just tested Martin's patch and it applies to path the >> gnome-3-14 and gnome-3-16 branch without conflicts. I also gave it a >> quick test and it works as expected, so I intend to pull that patch from >> bgo. > > Great! Couldn't we even get rid of the script snippet entirely, then? I > wonder why upstream removed this code in the first place and decided to > rely on a shell-dependant script snippet solution that requires explicit > user configuration at all? I'd keep it. Conceptually the script solution has some advantages, and if users want to opt into that, it's fine. > BTW, there are currently three incarnations of vte in the archive. Is > there a specific reason for that? Right, we incidentally just discussed that situation the last couple of days on IRC vte is for gtk2, will need a bit longer to get rid of. vte2.91 is the successor of vte3 (confusing, I know) and we should get rid of vte3. Will hopefully find some time to file bugs against the rdeps of vte3 to migrate to vte2.91. If someone wants to beat me to it, I wouldn't complain :-) Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#786863: jessie-pu: package debian-lan-config/0.19
Control: tags -1 + pending On 2015-05-28 18:50, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2015-05-28 at 16:27 +0200, Andreas B. Mundt wrote: I hope this is in a better shape now, a new debdiff is attached. Thanks. Please feel free to upload. Uploaded and flagged for acceptance. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786389: jessie-pu: package mate-netbook/1.8.1-4+deb8u1
Control: tags -1 + pending On 2015-05-29 0:27, Mike Gabriel wrote: Hi Adam, On Do 28 Mai 2015 19:59:00 CEST, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2015-05-21 at 10:35 +0200, Mike Gabriel wrote: + * Add 0002_preserve_configuration.patch. Ensure Window Picker +applet doesn't override mate-maximus. (Closes: #785090). -> Basically, applet A should not mess with settings of applet B. Especially not, if the user cannot do anything about it. Please go ahead. The package has arrived in stable-new. I've just flagged it for acceptance into p-u. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774351: sbuild: patch to fail when hooks fail
Hi!
A friend of mine recently ran into this issue too, so I tried to come up
with a quick & dirty patch to make hooks abort the build if they fail. I
haven't tested it yet, mind you. In any case, patch is attached. When I
hear back from either my friend, or from anyone reading this, that the
patch works, I'll clean it up and resubmit.
--
|8]
From 2fc906196c67cb71fb79f8e517b28d830f59d4fc Mon Sep 17 00:00:00 2001
From: Gergely Nagy
Date: Fri, 29 May 2015 09:01:24 +0200
Subject: [PATCH] Sbuild::Build: Abort when a hook fails
Signed-off-by: Gergely Nagy
---
lib/Sbuild/Build.pm | 48 ++--
1 file changed, 30 insertions(+), 18 deletions(-)
diff --git a/lib/Sbuild/Build.pm b/lib/Sbuild/Build.pm
index cda5cf3..00513a7 100644
--- a/lib/Sbuild/Build.pm
+++ b/lib/Sbuild/Build.pm
@@ -367,9 +367,11 @@ sub run_chroot_session {
# Run pre build external commands
$self->check_abort();
- $self->run_external_commands("pre-build-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+my $returnval;
+ $returnval = $self->run_external_commands("pre-build-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command failed") if (!$returnval);
$self->check_abort();
if (!$session->begin_session()) {
@@ -512,9 +514,10 @@ sub run_chroot_session_locked {
# Run specified chroot setup commands
$self->check_abort();
- $self->run_external_commands("chroot-setup-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+ my $returnval = $self->run_external_commands("chroot-setup-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command failed") if (!$returnval);
$self->check_abort();
@@ -702,9 +705,11 @@ sub run_fetch_install_packages {
# Run specified chroot cleanup commands
$self->check_abort();
- $self->run_external_commands("chroot-cleanup-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+ my $returnval = $self->run_external_commands("chroot-cleanup-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command failed") if (!$returnval);
+$self->check_abort();
if ($self->get('Pkg Status') eq "successful") {
$self->log_subsection("Post Build");
@@ -715,9 +720,11 @@ sub run_fetch_install_packages {
# Run post build external commands
$self->check_abort();
- $self->run_external_commands("post-build-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+ my $returnval = $self->run_external_commands("post-build-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command failed") if (!$returnval);
+$self->check_abort();
}
};
@@ -1473,9 +1480,12 @@ sub build {
return 0;
}
-$self->run_external_commands("starting-build-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+my $returnval;
+$returnval = $self->run_external_commands("starting-build-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command failed") if (!$returnval);
+$self->check_abort();
$self->set('Build Start Time', time);
$self->set('Build End Time', $self->get('Build Start Time'));
@@ -1666,9 +1676,11 @@ sub build {
$self->log("Build finished at $finish_date\n");
-$self->run_external_commands("finished-build-commands",
- $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
- $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+my $retval = $self->run_external_commands("finished-build-commands",
+ $self->get_conf('LOG_EXTERNAL_COMMAND_OUTPUT'),
+ $self->get_conf('LOG_EXTERNAL_COMMAND_ERROR'));
+$self->request_abort ("External command fail
Bug#787152: Section 11.5/11.6 - Replace Boot-up method from init to systemd
Package: debian-faq Section 11.5/11.6 - Replace Boot-up method from init to systemd. Proposed change in patch file attached. --- customizing.sgml2015-05-29 14:15:36.792753648 +0800 +++ customizing.sgml.new2015-05-29 15:08:09.037752850 +0800 @@ -52,96 +52,32 @@ Every distribution seems to have a different boot-up method. Tell me about Debian's. -Like all Unices, Debian boots up by executing the program init -As of this writing, the unstable release for Debian GNU/Linux is -replacing sysvinit with https://wiki.debian.org/systemd";>.. -The configuration file for init (which is /etc/inittab) -specifies that the first script to be executed should be -/etc/init.d/rcS. This script runs all of the scripts in -/etc/rcS.d/ by forking subprocess -to perform initialization such as to check and to mount file systems, -to load modules, to start the network services, to set the clock, and to -perform other initialization. - -After completing the boot process, init executes all start -scripts in a directory specified by the default runlevel (this runlevel -is given by the entry for id in /etc/inittab). -Like most System V compatible Unices, Linux has 7 runlevels: - - 0 (halt the system), - 1 (single-user mode), - 2 through 5 (various multi-user modes), and - 6 (reboot the system). - -Debian systems come with id=2, which indicates that the default -runlevel will be '2' when the multi-user state is entered, and the -scripts in /etc/rc2.d/ will be run. - -Debian uses dependency-based boot ordering through /etc/init.d/, as well as -parallel concurrent booting through the use of The scripts in any of the directories, /etc/rcN.d/ -are just symbolic links back to scripts in /etc/init.d/. However, -the names of the files in each of the /etc/rcN.d/ -directories are selected to indicate the way the scripts in -/etc/init.d/ will be run. Specifically, before entering any -runlevel, all the scripts beginning with 'K' are run; these scripts kill -services. Then all the scripts beginning with 'S' are run; these scripts -start services. The two-digit number following the 'K' or 'S' indicates -the order in which the script is run. Lower numbered scripts are executed -first. - -This approach works because the scripts in /etc/init.d/ all -take an argument which can be either `start', `stop', `reload', `restart' -or `force-reload' and will then do the task indicated by the argument. -These scripts can be used even after a system has been booted, to control -various processes. - -For example, with the argument `reload' the command - /etc/init.d/sendmail reload -sends the sendmail daemon a signal to reread its configuration file. - -Note that /etc/init.d/ scripts, What other facilities are provided - to customize the boot process besides - rc.local? - -The rc.local script is executed at the end of each multiuser -runlevel. In Debian it is configured to do nothing. This provides -customisation of the boot process, but might not be sufficient -for all situations. - -Suppose a system needs to execute script foo on start-up, -or on entry to a particular (System V) runlevel. Then the system -administrator should: - - Enter the script foo into the directory /etc/init.d/. - Run the Debian command update-rc.d with appropriate - arguments, to specify which runlevels should start the service, and which - runlevels should stop the service. - Consider rebooting the system to check that the service starts - correctly (assuming that you've asked for it to be started in the - default runlevel). Otherwise, manually start it by running - `/etc/init.d/foo start'. - - -One might, for example, cause the script foo to execute at -boot-up, by putting it in /etc/init.d/ and running -update-rc.d foo defaults 19. The argument `defaults' refers -to the default runlevels, which means (at least in absence of any LSB comment -block to the contrary) to start the service in runlevels 2 through 5, -and to stop the service in runlevels 0, 1 and 6. -(Any LSB Default-Start and Default-Stop directives in foo take -precedence when using the sysv-rc version of update-rc.d, but are -ignored by the current (v0.8.10) file-rc version of update-rc.d.) -The argument `19' ensures that foo is called after all -scripts whose number is less than 19 have completed, and before all scripts -whose number is 20 or greater. +Like most Linux distributions, Debian boots up by executing the program +systemd. Systemd provides the concept of targets similar to runlevel +which was found from Unices and previous version of Debian GNU/Linux. You may +check the default target by the command + + systemctl get-default + +During boot-up, systemd start the services or other targets listed in the +default target file /lib/systemd/system/default.target. These +services and targets files are installed during Debian package installation. +If you explicitly do not wish to run the services during boot-up, instead of +remove the installed package, you can run the comma
Bug#786565: [Pkg-mozext-maintainers] Bug#786565: iceweasel: breaks xul-ext-requestpolicy
>> I suppose Iceweasel 38 will migrate to Jessie soon, as Firefox's >> new/next ESR release is version 38. > > That’s not likely to happen with the next point release (scheduled in > less than two weeks), but probably with the following one (due in a few > months). Good to know. Seems like Fx31 ESR is supported until Fx40 is released as stable, see https://www.mozilla.org/en-US/firefox/organizations/faq/ >> Is that a problem for continuity in the debian repo? > > Going back to 0.5 now that 1.0 is in unstable is not straightforward, > but since we are merely preparing the next stable release (Stretch, > probably due in two years), RP 1.0 (or more) will probably be stable at > that time ;). Yes, that's what I suppose as well. Regards Martin signature.asc Description: OpenPGP digital signature
Bug#787153: Section 15.3 - Remove Obsolete section - Faster booting
Package: debian-faq Version: 8.0 Faster booting was an objective of Wheezy which has been completed and even superceded by systemd. Suggest to remove the whole section. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624375: tritium: debian-menu.py left behind on purge
reopen 624375 thanks On dpkg -P tritium the directory /var/lib/tritium still remains. I think it would be listed in the package contents (the debian/dirs file if using debhelper) so that dpkg will then remove it, if sysadmin hasn't put anything else there. (blackbox is an example of this sort of thing. It has nothing else in menu directory /etc/X11/blackbox and gives it in package contents.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#779030: python-eventlet: Fall back to old behavior if SSLContext() not available.
Hi Corey, Is this bug still relevant after the upload of eventlet 0.17.4-2 in Sid? Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787154: postgresql-client-common: Cannot start with port changed in postgresql.auto.conf (through alter system)
Package: postgresql-client-common Version: 168.pgdg80+1 Severity: normal Dear Maintainer, * What led up to the situation? I did an alter system set port=5433. This created a postgresql.auto.conf, which seems not to be parsed by debian tools. I think the postgresql.auto.conf should be automatically parsed if present by PgCommon, as PostgreSQL does. -- System Information: Debian Release: stretch/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-1-amd64 (SMP w/1 CPU core) 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 postgresql-client-common depends on: ii netbase 5.3 ii pgdg-keyring 2014.1 Versions of packages postgresql-client-common recommends: ii libreadline6 6.3-8+b3 ii lsb-release 4.1+Debian13+nmu1 postgresql-client-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787042: util-linux: FTBFS on kFreeBSD due to missing F_DUPFD_CLOEXEC
Hello Steven Chamberlain! On Thu, May 28, 2015 at 11:16:19PM +0100, Steven Chamberlain wrote: > Andreas Henriksson wrote: > > Wrote a long mail, scrapped it for this summary: > > Though you say you have no time for kfreebsd, you've written many > long emails complaining about it and that seems ironic and counter- > productive all round. > > Likewise I didn't want to waste much time arguing with you. With > https://bugs.debian.org/785796#45 you forgot to actually copy any > kfreebsd maintainers on the mail, but I did find it anyway when > looking into the FTBFS. That and your other mails I've seen came over > as quite offensive, and if I haven't replied to you that's why. Personally I find this time around has been the absolutely most productive attempt. People from the kfreebsd camp has actually started to reply to mails! Thats a great step forward in my book! The reason I've spent alot of time writing mails is because I want to find someone with interest to take care of kfreebsd. I hope you don't find that offensive. I'm asking around where to find kfreebsd people (which actually replies), and people keep telling me to just continue writing mails I hope you can see that while I've never cared for kfreebsd myself it's been quite upsetting that I've not managed to get anyone to even reply to mails. That's why I've given up on even CCing debian-bsd. If we can turn this around, then my mood will be much better! If you feel offended then I'm sorry for that. Not sure you should expect me to change all that much without someone else lenging me a helping hand though. I hope you can see that me being stressed to find time for things I actually want to get done, means I'm not very receptive to having to spend time on things I care very little about. Help is welcome! > > I did meanwhile look to address this specific issue long-term via glibc, > without needing changes to util-linux (https://bugs.debian.org/785796#65). > It seems that won't work as Debian buildds don't support that feature > yet and another issue blocks them from being upgraded. > > > Anyone holding their breath waiting for me to do (further) > > kfreebsd work should prepare themselves for dissapointment. > > Guillem's workaround in https://bugs.debian.org/787042#5 would be > sufficient to resolve the current situation with Debian sid. I don't > think it's suitable for upstreaming and should be only temporary. > > He has meanwhile produced something else which may be more appropriate > for upstreaming. But I wouldn't necessarily have waited for that when > you have one build-essential package FTBFS and another uninstallable. Haven't found where the updated patch went yet (maybe I'm just too stressed). I think I've managed to wrestle the BTS so that the *closed* bug no longer should prevent testing migration. Will try to have a look at patches as soon as I find some time after verifying testing migration has completed. As already mentioned; Help welcome! My time is very limited. Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780093: [Pkg-libvirt-maintainers] Bug#780093: is this patch the fix for this problem
On Wed, May 27, 2015 at 05:14:00PM +, Nigel Kukard wrote: > On 05/27/2015 05:09 PM, Guido Günther wrote: > > Hi, > > On Wed, May 27, 2015 at 09:11:16AM +0200, Han Boetes Edis GmbH wrote: > >> Since I still see this problem I searched around a bit: Is this patch the > >> fix for this problem? Please also check the reply, it mentions one change > >> too much has been made. > >> > >> https://www.redhat.com/archives/libvir-list/2014-December/msg00304.html > > Do you have a configuration comparable to Torstens? If so it's possible, > > I'd be happy about any tests with this patch since I still did not get > > around to do some investigation. > > Is there a reason why this was not committed upstream? it looks like the > patch was not submitted as required in the review, should the correct > course of action not be to resubmit it upstream, and if its included we > can include it in the Debian package? It seems it just got forgotten. If the patch helps to get a better error message for the problems in this bug I'm happy to address Jiri's review comments and resubmit it. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787084: impact on dependencies
Since the code change a section from a class template it will have an impact on any client using this code. In other word some platforms will FTBFS if -latomic is not added to the link line (technically there were already FTBFS because of a missing symbols anyway). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786874: postgresql kann nicht „??fnen“, indeed…
Hi, this is the same bug as: https://wiki.postgresql.org/wiki/May_2015_Fsync_Permissions_Bug#I.27ve_hit_this_bug_and_I_can.27t_restart_Postgres._What_do_I_do.3F I *can* restart, but the upgrade isn’t in wheezy yet; the workaround described there works for me though. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787155: nm.debian.org: Mail archive doesn't understand MIME messages
Package: nm.debian.org Severity: normal In the online Mail archive like [1], clicking will open the message body. Unfortunately, for multi-part MIME messages (of which there are plenty because we require GPG sigs), only garbage is shown: [, ] [1] https://nm.debian.org/am/display-mail-archive/tvincent I don't think this would be hard to fix, but my python fu failed. It's probably ok to just show the first part and ignore the others, or do some filtering on the MIME type. Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#787156: libstrongswan: configuration file for logcheck ignores completely outdated (useless)
Package: libstrongswan Version: 5.2.1-6 Severity: normal Dear Maintainer, with the release of jessie, I had to upgrade several machines from freeswan (in wheezy) to strongswan (in jessie). After some struggling with configuration files (my freeswan configuration was not compatible with strongswan and I had to reconfigure my IPSec VPN from scratch) I got it to work properly, and it now works flawlessly again. However, I started receiving huge reports from logcheck from all machines in the IPSec network. I inspected the log files, and indeed all the log lines being caught and reported by logcheck are absolutely normal, the bulk of them being essentially charon doing its job of establishing connections, checking certificates, rekeying etc.. I then set out to see what was missing from the regexps in the strongswan ignore files in /etc/logcheck/ignore.d.* and to my surprise I noticed that the "strongswan" files in there are actually verbatim copies from the package of some old version of freeswan, the ignore patterns being about pluto, the IKEv1 in freeswan. I will now (with some patience) set out to create ignore patterns for my local installations of stronswan, and install them on my machines. If they may be of any help, when done I can send them to you as a skeleton for updated logcheck ignore files. In the meanwhile, I recommend that you either remove altogether the current stronswan files in the /etc/logcheck/ignore.d.* directories, or replace them with empty placeholders, until you have something more useful to put in them. This problem affects versions in jessie, sid and experimental. Thanks, bye Giacomo Mulas -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.2-jak (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libstrongswan depends on: ii libc6 2.19-18 ii libcap2 1:2.24-8 ii libgmp10 2:6.0.0+dfsg-6 Versions of packages libstrongswan recommends: ii libstrongswan-standard-plugins 5.2.1-6 Versions of packages libstrongswan suggests: ii libstrongswan-extra-plugins 5.2.1-6 -- Configuration Files: /etc/logcheck/ignore.d.paranoid/strongswan [Errno 13] Permesso negato: u'/etc/logcheck/ignore.d.paranoid/strongswan' /etc/logcheck/ignore.d.server/strongswan [Errno 13] Permesso negato: u'/etc/logcheck/ignore.d.server/strongswan' /etc/logcheck/ignore.d.workstation/strongswan [Errno 13] Permesso negato: u'/etc/logcheck/ignore.d.workstation/strongswan' /etc/logcheck/violations.ignore.d/strongswan [Errno 13] Permesso negato: u'/etc/logcheck/violations.ignore.d/strongswan' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787121: vlc: VLC doesn't play some MPEG files
Control: tags -1 + moreinfo On 2015-05-28 17:00:50, Gary Dale wrote: > Package: vlc > Version: 2.2.0~rc2-2 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > I recently downloaded some video files and tried to play them using VLC. The > files > played back badly, with a thin band of choppy video at the top, and the rest > of the > screen straight green. > >* What exactly did you do (or not do) that was effective (or ineffective)? > Tried Kaffeine. Same result. However KMplayer and Totem played it properly and > Avidemux was able to open it. Avidemux reports it as 4CC Mpeg, 960x544 with > stereo > MP2 sound at 48,000 Hz. Please provide the output of vlc -vvv while playing the file. > Versions of packages vlc-nox depends on: ... > ii libbasicusageenvironment0 2:2014.07.25-dmo1 > ii libbluray1 2:0.6.0-dmo2 ... > ii libdca00.0.5-dmo2 ... > ii libdvbpsi9 1.2.0-dmo1 ... > ii libebml4 1.3.0-dmo1 ... > ii libgroupsock1 2:2014.07.25-dmo1 ... > ii libmatroska6 1.4.1-dmo1 ... > ii libpostproc52 10:2.3.1-dmo1 ... > ii libx264-1423:0.142.2452+git08d36b3-dmo1 Please remove all dmo libraries from your system and try to reproduce it with the packages provided by Debian. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#756326: xserver-xorg-video-intel: that happened here too
Package: xserver-xorg-video-intel Version: 2:2.99.917-1 Followup-For: Bug #756326 Dear Maintainer, apt-get dist-upgrade removed xserver-xorg-video-intel from this Debian Sid system, resulting in X being a bit sluggish. re-installing fixes that. quoting from /var/log/apt/history.log Start-Date: 2015-05-06 07:37:55 Commandline: apt-get dist-upgrade Install: libx265-43:i386 (1.5-1, automatic), libisl13:i386 (0.14-2, automatic), gcc-5-base:i386 (5.1.1-4, automatic), libgphoto2-po rt12:i386 (2.5.7-5, automatic) Upgrade: console-setup:i386 (1.124, 1.125), libcap-ng0:i386 (0.7.4-2, 0.7.4-3), xserver-xorg-video-tdfx:i386 (1.4.6-1, 1.4.6-1+b1), slime:i386 (2.10.1-3, 2.13-1), xserver-xorg-video-vmware:i386 (13.1.0-1, 13.1.0-1+b1), gcj-4.9-jre:i386 (4.9.2-10, 4.9.2-16), node js-dev:i386 (0.10.29~dfsg-2, 0.10.38~dfsg-1), libzvbi0:i386 (0.2.35-3, 0.2.35-6), libzvbi-common:i386 (0.2.35-3, 0.2.35-6), ftp:i38 6 (0.17-31, 0.17-33), libsane:i386 (1.0.24-9, 1.0.24-9+b1), libdjvulibre21:i386 (3.5.25.4-4+b1, 3.5.27.1-1), libcloog-isl4:i386 (0. 18.2-1+b2, 0.18.3-1), libatk1.0-data:i386 (2.14.0-1, 2.16.0-2), libfile-which-perl:i386 (1.17-1, 1.18-1), xserver-xorg-video-sisusb :i386 (0.9.6-2+b2, 0.9.6-2+b3), keyboard-configuration:i386 (1.124, 1.125), vlc-plugin-samba:i386 (2.2.0-1, 2.2.1-1), xserver-xorg- core:i386 (1.16.4-1, 1.17.1-2), libdjvulibre-text:i386 (3.5.25.4-4, 3.5.27.1-1), gcc-4.9-base:i386 (4.9.2-10, 4.9.2-16), xserver-xo rg-video-mga:i386 (1.6.4-1, 1.6.4-1+b1), libgcc-4.8-dev:i386 (4.8.4-1, 4.8.4-2), libquadmath0:i386 (4.9.2-10, 5.1.1-4), console-set up-linux:i386 (1.124, 1.125), gcc-4.8-base:i386 (4.8.4-1, 4.8.4-2), xserver-common:i386 (1.16.4-1, 1.17.1-2), g++-4.9:i386 (4.9.2-1 0, 4.9.2-16), libatomic1:i386 (4.9.2-10, 5.1.1-4), libgcc-4.9-dev:i386 (4.9.2-10, 4.9.2-16), libgcj15:i386 (4.9.2-10, 4.9.2-16), xs erver-xorg-video-nouveau:i386 (1.0.11-1, 1.0.11-1+b1), xserver-xorg-video-openchrome:i386 (0.3.3-1+b2, 0.3.3-1+b3), libstdc++-4.9-d ev:i386 (4.9.2-10, 4.9.2-16), libitm1:i386 (4.9.2-10, 5.1.1-4), libstdc++6:i386 (4.9.2-10, 5.1.1-4), cl-swank:i386 (2.10.1-3, 2.13- 1), gir1.2-atk-1.0:i386 (2.14.0-1, 2.16.0-2), libasan0:i386 (4.8.4-1, 4.8.4-2), libasan1:i386 (4.9.2-10, 4.9.2-16), libgphoto2-6:i3 86 (2.5.4-1.1+b2, 2.5.7-5), libtk8.6:i386 (8.6.2-1, 8.6.4+dfsg-2), vlc-plugin-notify:i386 (2.2.0-1, 2.2.1-1), telnet:i386 (0.17-36, 0.17-40), libatspi2.0-0:i386 (2.14.0-1, 2.16.0-1), libgomp1:i386 (4.9.2-10, 5.1.1-4), xserver-xorg-video-fbdev:i386 (0.4.4-1+b2, 0 .4.4-1+b3), nodejs:i386 (0.10.29~dfsg-2, 0.10.38~dfsg-1), tk8.6:i386 (8.6.2-1, 8.6.4+dfsg-2), libgfortran3:i386 (4.9.2-10, 5.1.1-4) , gcj-4.9-jre-headless:i386 (4.9.2-10, 4.9.2-16), libtiff5:i386 (4.0.3-12.3, 4.0.3-13), xserver-xorg-video-radeon:i386 (7.5.0-1, 7. 5.0-1+b1), vlc:i386 (2.2.0-1, 2.2.1-1), libcilkrts5:i386 (4.9.2-10, 5.1.1-4), libio-socket-ssl-perl:i386 (2.013-1, 2.014-1), xserve r-xorg-video-qxl:i386 (0.1.1-2+b1, 0.1.1-2+b2), xserver-xorg-video-vesa:i386 (2.3.3-1+b3, 2.3.3-1+b4), libatk1.0-0:i386 (2.14.0-1, 2.16.0-2), xserver-xorg-video-trident:i386 (1.3.7-1, 1.3.7-1+b1), liblexical-sealrequirehints-perl:i386 (0.007-1+b2, 0.009-1), libg cc1:i386 (4.9.2-10, 5.1.1-4), libtcl8.6:i386 (8.6.2+dfsg-2, 8.6.4+dfsg-2), tcl8.6:i386 (8.6.2+dfsg-2, 8.6.4+dfsg-2), cpp-4.8:i386 ( 4.8.4-1, 4.8.4-2), cpp-4.9:i386 (4.9.2-10, 4.9.2-16), gcc-4.8:i386 (4.8.4-1, 4.8.4-2), gcc-4.9:i386 (4.9.2-10, 4.9.2-16), libavcode c56:i386 (11.3-1, 11.3-2), libubsan0:i386 (4.9.2-10, 5.1.1-4), libgcj15-awt:i386 (4.9.2-10, 4.9.2-16), at-spi2-core:i386 (2.14.0-1, 2.16.0-1), vlc-nox:i386 (2.2.0-1, 2.2.1-1) Remove: xserver-xorg-video-savage:i386 (2.3.7-2+b2), xserver-xorg-video-r128:i386 (6.9.2-1+b2), xserver-xorg-video-geode:i386 (2.11.16-7), xserver-xorg-video-neomagic:i386 (1.2.8-1+b2), xserver-xorg-video-modesetting:i386 (0.9.0-1+b1), xserver-xorg-video-siliconmotion:i386 (1.7.7-2+b2), xserver-xorg-video-cirrus:i386 (1.5.2-2+b1), xserver-xorg-video-intel:i386 (2.21.15-2+b2), xserver-xorg-video-mach64:i386 (6.9.4-2), xserver-xorg-video-all:i386 (7.7+8), xserver-xorg-video-ati:i386 (7.5.0-1) End-Date: 2015-05-06 07:38:28 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 24 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2544344 May 5 00:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.0.0-2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-18) ) #1 SMP Debian 4.0.4-1 (2015-05-26) Xorg X server log files on system: -- -rw-r--r-- 1 root root 29987 Oct 5 201
Bug#769960: GDM3: blank screen: could this be an LLVM Pipe issue?
2015-05-15 20:46 GMT+03:00 Martin-Éric Racine : > Everything seems to point towards this being caused by LLVM Pipe, > which should kick in whenever gnome-session is lauched on > non-accelerated hardware. > > Help on how to debug the issue from this particular angle is welcome. Sure enough, removing libgl1-mesa-dri (which pulls libllvm3.5) at least made something appear on screen after restarting gdm3: "Oh no! something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again. [ Log Out ]" Now, I'm wondering what differences between LLVM 3.4 and 3.5 could cause this. Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787157: [bts] bts show fails completly due to ssl issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: devscripts Version: 2.15.4 Severity: normal See the following: ~> bts -m show XX bts: couldn't download http://bugs.debian.org/762709: 500 Can't connect to bugs.debian.org:443 (certificate verify failed) The following certificates (and only them) are enabled in ca-certificates: - - CAcert/class3.crt - - CAcert/root.crt - - mozilla/USERTrust_RSA_Certification_Authority.crt There is several stuff wrong with bts here: 1. The URL in the error message should not be http when it really uses https. With http, that error makes no sense. 2. Looking at bugs.debian.org via gnutls-cli shows that the certificate-tree is: - O=The USERTRUST Network,CN=USERTrust RSA Certification Authority - O=Gandi,CN=Gandi Standard SSL CA 2 - CN=bugs.debian.org There is no Gandi certificate in ca-certificates but as the root certificate is valid, it should not fail 3. All Debian domains already utilizing DANE, so there is no reason to not use it. That is much more trustable than some random and extraordinary SSL certificate issuing companies with no real reason why one should trust them. Please fix bts to do SSL in a way that is usable and give proper error messages. - -- Package-specific info: - --- /etc/devscripts.conf --- - --- ~/.devscripts --- BTS_CACHE_MODE=full BTS_INCLUDE_RESOLVED=no DEBSIGN_KEYID=0x79D0B06F4E20AF1C - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.5 (SMP w/8 CPU cores) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages devscripts depends on: ii dpkg-dev 1.18.0 ii libc62.19-18 ii perl 5.20.2-6 ii python3 3.4.2-2 pn python3:any Versions of packages devscripts recommends: ii at 3.1.16-1 ii curl7.42.1-2 ii dctrl-tools 2.24-1 ii debian-keyring 2015.05.17 ii dput0.9.6.4 ii equivs 2.0.9 ii fakeroot1.20.2-1 ii file1:5.22+15-2 ii gnupg 1.4.19-3 pn libdistro-info-perl ii libencode-locale-perl 1.03-1 ii libjson-perl2.61-1 ii liblwp-protocol-https-perl 6.06-2 ii libsoap-lite-perl 1.11-1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lintian 2.5.31 ii man-db 2.7.0.2-5 ii patch 2.7.5-1 ii patchutils 0.3.4-1 ii python3-debian 0.1.27 pn python3-magic ii sensible-utils 0.0.9 ii strace 4.10-1 ii unzip 6.0-17 ii wdiff 1.2.2-1 ii wget1.16.3-2 ii xz-utils5.1.1alpha+20120614-2+b3 Versions of packages devscripts suggests: ii bsd-mailx [mailx]8.1.2-0.20150408cvs-1 ii build-essential 11.7 pn cvs-buildpackage pn debbindiff pn devscripts-el ii gnuplot 4.6.6-2 ii gpgv 1.4.19-3 ii libauthen-sasl-perl 2.1600-1 ii libfile-desktopentry-perl0.07-1 ii libnet-smtp-ssl-perl 1.01-3 ii libterm-size-perl0.207-1+b2 ii libtimedate-perl 2.3000-2 ii libyaml-syck-perl1.27-2+b2 ii mutt 1.5.23-3.3~ket ii openssh-client [ssh-client] 1:6.7p1-6.1~securityfix pn svn-buildpackage ii w3m 0.5.3-21 - -- no debconf information - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCgAGBQJVaCduAAoJEKZ8CrGAGfasa+YL/jmWh9nLQvWsBaZkSO81aZZ9 sjmvkY8YaA4/Fh/Gzm9uGqDXoe969JOZAfnvjo1VIAU0Jg0oHE2dGNB9WJCgUf4D yvL15LtluLPL9wkU+sz/8m3/Njtkgcq+bbTnQAkzkq5daObB+m6H/N6RYPerUi/3 XeW4QPuxAWWYhgYj8I1E2QzWGC0Mgl8M/8CciU/5fdpnAB/JtVx1rDAz/2Zg2wYE 36KBChlY1ap2bCvyK8arLm9rVLCVA84TDVylFLZy7bM9n/8deEZpPWGh1xpV4iy6 mGcdlRl5lOxHyhhgdjkGJRRNJrv1PwK90WRS5aqHAaVZYMzDWvm0hdu9zFZoj7/f pvoTk3YHSsAtyp368GTYdpx+VWpWVPkGqsl9kAobbeLv+B5MnF9vYw3WOjEXJmQ2 +8S20Trmv2F+hXKXSSlf6q8R+ncpMvz9UpaixGwYriEUDKXmiAPA0RSrI1gfK0CP ijRIUa2OJ3MFWKU8yiyXxO3emGXOY7J2AHrbfnKXAQ== =61Wc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782123: ganeti: Does not clean up on failed migrations
Control: tags -1 upstream Hi Joerg, Apologies for the late reply. On 10:22 Wed 08 Apr , Joerg Jaspert wrote: > this at least happens with the extstorage interface and the bug from > me yesterday, #782073, though it appears it may happen with all > failures pre-migration: Ganeti does not clean up. > > In this case it does not undo the disk changes done (which led to the > other bug), so the exported disk is still on the host it had selected > when trying the last migration. Indeed, the migration/failover code only performs cleanup actions for DRBD only. I will forward this upstream. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787122: xtrlock: please make the build reproducible
tags -1 moreinfo quit On 28/05/15 22:01, Dhole wrote: > While working on the “reproducible builds” effort [1], we have noticed > that xtrlock could not be built reproducibly. > > The attached patch fixes the files mtime before building the binary > packages. Once applied, xtrlockcan be built reproducibly in our current > experimental framework. This seems a bizarre thing to be doing in the middle of a build. Surely reproducibility of builds shouldn't care about the timestamps of files? Regards, Matthew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787158: perl/experimental: restore the symlinks on privlib/privarch
Package: perl Version: 5.22.0~rc2-1 Re-thinking this change in the current 5.22 packaging: commit 854e9f16b0e2a4ae1b04a9c15261248988da7a22 Author: Niko Tyni Date: Sat May 23 19:24:26 2015 +0300 Use the full version instead of the short one for privlib and archlib The old setup required symlinks /usr/share/perl/5.20 -> 5.20.2 /usr/lib//perl/5.20 -> 5.20.2 but there's no value in those as long as the core packages stay at the same upstream version, which the dependencies already ensures. I think we've introduced a chance for long lived Perl programs to have @INC changed underneath them. This is the same thing the 'perl-major-upgrade' trigger was designed for (see #230308), but this time for minor upgrades. While this is not expected to affect stable->stable upgrades (because Perl upstream has a shorter release cycle than we do), it's still suboptimal. IIRC the change was prompted by the need to move the symlinks somewhere from perl-base due to the libperl multiarch/multiversion changes. I think having the symlinks in libperl5.22 (for archlib) and perl-modules-5.22 (privlib) should work fine. -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787157: [bts] bts show fails completly due to ssl issue
Hi Klaus! * Klaus Ethgen , 2015-05-29, 09:46: See the following: ~> bts -m show XX bts: couldn't download http://bugs.debian.org/762709: 500 Can't connect to bugs.debian.org:443 (certificate verify failed) The following certificates (and only them) are enabled in ca-certificates: - CAcert/class3.crt - CAcert/root.crt - mozilla/USERTrust_RSA_Certification_Authority.crt There is several stuff wrong with bts here: 1. The URL in the error message should not be http when it really uses https. With http, that error makes no sense. bts(1) connects to to bugs.d.o via HTTP, which only then redirects to HTTPS. This is something we should fix. In the mean time, you can put BTS_SERVER=https://bugs.debian.org in your ~/.devscripts. 2. Looking at bugs.debian.org via gnutls-cli shows that the certificate-tree is: - O=The USERTRUST Network,CN=USERTrust RSA Certification Authority - O=Gandi,CN=Gandi Standard SSL CA 2 - CN=bugs.debian.org There is no Gandi certificate in ca-certificates but as the root certificate is valid, it should not fail No, that's not right. The root CA for bugs.d.o is AddTrust_External_Root. 3. All Debian domains already utilizing DANE, so there is no reason to not use it. Heh, patches welcome. Have fun implementing DANE validation. ;-) -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787024: transition: libaqbanking
Hi, Am 28.05.2015 00:35, schrieb Emilio Pozuelo Monfort: On 27/05/15 23:11, Micha Lenk wrote: [...] As AqBanking's API seems to have stabilized recently, do you recommend to transition the -dev package to the new name libaqbanking-dev instead? If so, is there anything to keep in mind if the old package libaqbanking34-dev already has a Provides: libaqbanking-dev (it has it actually long since)? The reverse dependencies currently all build-depend on libaqbanking34-dev. Please rename it to libaqbanking-dev. [...] I renamed it and uploaded it to experimental as libaqbanking 5.6.0beta-2. It is currently in NEW. The following reverse dependencies will be impacted by this transition: abtransfers gnucash kmymoney BTW do the rdeps build against the new version? Or do they need code changes? I didn't try, but as I am following upstream closely I don't expect that any code changes are needed. The SONAME bump was done as a precaution measure because some symbols were temporarily added to the library that got removed in libaqbanking 5.5.1-1 (only in experimental). Regards, Micha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787044: libdebian-installer: please make new Build-Depends: check optional via build profiles
Hello, Johannes Schauer (2015-05-29): > If one wants to build build-essential from scratch without relying on > packages from the archive (bootstrap scenario) then one has to > recursively build its build dependencies, the build dependencies of > these, and so on and so forth. The set of source package one then > ends up with is currently at least 818 source packages big for Debian > unstable amd64. I say "at least" because A|B type dependencies and > "Provides:" relationships allow different selections to satisfy > dependencies. The maximum number is 1135 source packages. > > src:libdebian-installer is in the smaller set. So it is *not* optional > by choosing a different alternative or Provides. It is also required > whether or not one relies on existing Architecture:all packages or > not. You can see a list of all source packages in the transitively > build-essential set here: > > http://bootstrap.debian.net/essential.html > > That page does not yet provide an explanation which dependency path > makes them being included because I didn't yet have the time to > generate this information. But for src:libdebian-installer, the > reason is, that it is in the strong dependency set of src:cdebconf > which in turn is needed by build-essential because of > libdebconfclient0 which is needed by base-passwd. Thanks for the dependency chain explanation. That kind of information will really be valuable to have extracted in an automated fashion. > > > [1] https://wiki.debian.org/BuildProfileSpec > > > > How stable is this spec, > > the syntax itself was set in stone (in the wiki page) at 2014-08-31 (which was > during the bootstrap sprint in paris) together with guillem who encoded this > in > dpkg. All changes you see to that spec after this date are either > > - rewording to make hard to understand parts easier to read > > - add examples > > - expand the table of software that implements the syntax > > - adding new ideas of scenarios build profiles can be used in > > As the main author of the spec I'd say that the only things that could > possibly > be changed during this release cycle are the amount of permissible build > profile names (if the need for a new one comes up). This would not affect the > patch submitted by Helmut in this bug because the "nocheck" build profile name > was always needed and part of the spec. > > The spec staying stable in its core (the syntax and fields) is furthermore > enforced by the fact that if something were to change now, then it would delay > the possibility of uploading packages with build profiles again until after > the > release of Stretch in ~2 years. And we really don't want that :) > > So there is no plan to touch this thing in any other way than making things > more clear in places where it was not. Well, I hope it's more stable than the last time I saw people try and push stuff past release people and insist on having stuff deployed on Debian infra… until it was figured out that woops some changes were needed. I suppose having support merged into dpkg improves chances for that to no longer happen. > The syntax is not policy yet (bug #757760) but I'd compare this situation to > Multi-Arch which is also not policy yet but also has always only existed as a > wiki page and still is widely used in the archive. I plan to help getting > build > profiles into policy during this release cycle. Drawing parallels with multi-arch isn't likely going to reassure people. Quite the contrary. ;p > > and how much is that syntax supported by Debian's tools > > You can see an overview of tool support for the build profile syntax in the > table at the top of the spec: > > https://wiki.debian.org/BuildProfileSpec > > Most notably, build profile support is missing in pbuilder until somebody > applies the latest patch which fixes that situation in bug #740577. Until then > one should either build without a chroot or use sbuild. > > >/infra? > > It's hard to test our infrastructure before things get deployed but luckily > another package using the build profile syntax in its Build-Depends has been > uploaded recently: gem2deb. That helped us spot some remaining bits which did > not support the new syntax (#786400 and #787093) but as you can see, the > former > is fixed and the latter has a working patch and since I'm in contact with > Antonio I think it will be applied quickly. Yeah, I noticed the dd@ thread a little bit after replying. I think it'd be safer to wait a bit until the dust settles before applying this kind of patches in d-i packages. Mraw, KiBi. signature.asc Description: Digital signature
Bug#787159: openjdk-7: javadoc doesn't sort the annotations and enums in package-tree.html
Source: openjdk-7
Version: 7u79-2.5.5-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain randomness
The package-tree.html files generated by the javadoc tool display class
trees for interfaces, classes, annotations and enums. The interfaces and
classes trees are sorted alphabetically, but not the annotation and the
enum trees. This can be seen on the API documentation for the java.lang
package [1].
The actual order used is not deterministic and varies with the build
environment, this prevents several packages from being reproducible (for
example easymock [2] and mockito [3]).
This issue is caused by the buildTree method in the
com.sun.tools.doclets.internal.toolkit.util.ClassTree class [4], it
sorts the interfaces and the classes but forgets the other types. I'm
attaching a patch fixing this issue.
Emmanuel Bourg
[1] http://docs.oracle.com/javase/7/docs/api/java/lang/package-tree.html
[2] https://reproducible.debian.net/rb-pkg/unstable/amd64/easymock.html
[3] https://reproducible.debian.net/rb-pkg/unstable/amd64/mockito.html
[4]
http://hg.openjdk.java.net/jdk7u/jdk7u/langtools/file/jdk7u80-b32/src/share/classes/com/sun/tools/doclets/internal/toolkit/util/ClassTree.java#l114
Description: Sort the enums and the annotations in the package-tree.html files
Author: Emmanuel Bourg
Forwarded: no
---
openjdk/langtools/src/share/classes/com/sun/tools/doclets/internal/toolkit/util/ClassTree.java
+++
openjdk/langtools/src/share/classes/com/sun/tools/doclets/internal/toolkit/util/ClassTree.java
@@ -163,6 +163,15 @@
for (Iterator> it = subclasses.values().iterator();
it.hasNext(); ) {
Collections.sort(it.next());
}
+
+Collections.sort(baseEnums);
+for (Iterator> it = subEnums.values().iterator();
it.hasNext(); ) {
+Collections.sort(it.next());
+}
+Collections.sort(baseAnnotationTypes);
+for (Iterator> it =
subAnnotationTypes.values().iterator(); it.hasNext(); ) {
+Collections.sort(it.next());
+}
}
/**
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
Pirate Praveen (2015-05-12): > package: live-installer > severity: critical > version: 49 > > I had to install grub manually going into console (control+alt f1), > mount the install disk and use dpkg -i to install grub twice. One was > i386 lxde edition of jessie on virtual box and second was amd64 version > of cinnamon+nonfree on a dell laptop. I used dd to make the usb disk > bootable. In both cases internet connection was not available. I think > it is something to do with configuring the disk as an apt source properly. > > This is very disappointing as live + install is very useful. Raphael, since you're one of the few who touched non-l10n areas of live-installer recently, any chance you could have a look? And to answer the question in [1], no you can't have a fix in a point release until it's fixed in unstable. 1. https://lists.debian.org/debian-boot/2015/05/msg00668.html It might be useful to provide a log so that we understand what's happening here. Mraw, KiBi. signature.asc Description: Digital signature
Bug#781105: pgagent: SQL jobstep deadlock
A fix for this bug has been committed to upstream git: http://git.postgresql.org/gitweb/?p=pgagent.git;a=commitdiff;h=f9bf1ccb27ebcfce00e7a6d467bc0e1b5ee9555e -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#773833: Syslinux mbr location still not fixed / backport to 4.0 / jessie?
Hi,
this bug is marked as fixed in 5.0~a3, but I can't find the commit that
fixes it? Looking at the git master version, it seems this is still
broken as well?
http://live.debian.net/gitweb/?p=live-build.git;a=blob;f=scripts/build/binary_hdd;h=f5d42068110b9f3b19bc456a1c460046466957e9;hb=HEAD#l173
Furthermore, are there any plans to backport this fix to Jessie / 4.0?
Right now, the Jessie version is simply broken for hdd images. If this
is the plan, I've attached a patch against 4.0.5 that fixes this, as
well as another issue with hdd images and LB_BUILD_WITH_CHROOT=false.
This is the same patch I linked on IRC yesterday, but this is probably a
better place to
keep it.
Gr.
Matthijs
diff -ru build.orig/binary_hdd build/binary_hdd
--- build.orig/binary_hdd 2015-05-28 17:47:16.751149941 +0200
+++ build/binary_hdd 2015-05-28 18:38:25.448557872 +0200
@@ -191,7 +191,7 @@
if [ "${LB_BOOTLOADER}" = "syslinux" ]
then
- dd if=chroot/usr/lib/${_BOOTLOADER}/mbr.bin of=${FREELO} bs=440 count=1
+ dd if=chroot/usr/lib/${_BOOTLOADER}/mbr/mbr.bin of=${FREELO} bs=440 count=1
fi
;;
@@ -203,7 +203,7 @@
if [ "${LB_BOOTLOADER}" = "syslinux" ]
then
- dd if=/usr/lib/${_BOOTLOADER}/mbr.bin of=${FREELO} bs=440 count=1
+ dd if=/usr/lib/${_BOOTLOADER}/mbr/mbr.bin of=${FREELO} bs=440 count=1
fi
;;
esac
diff -ru build.orig/binary_syslinux build/binary_syslinux
--- build.orig/binary_syslinux 2015-05-28 17:47:16.751149941 +0200
+++ build/binary_syslinux 2015-05-28 18:41:06.211358157 +0200
@@ -180,9 +180,9 @@
;;
*)
-if [ ! -e "/usr/share/$(echo ${_BOOTLOADER} | tr [a-z] [A-Z])" ]
+if [ ! -e "/usr/lib/$(echo ${_BOOTLOADER} | tr [a-z] [A-Z])" ]
then
- Echo_error "/usr/share/$(echo ${_BOOTLOADER} | tr [a-z] [A-Z])"
+ Echo_error "/usr/lib/$(echo ${_BOOTLOADER} | tr [a-z] [A-Z]) - no such directory"
exit 1
fi
;;
signature.asc
Description: Digital signature
Bug#787160: RM: gnome-themes -- ROM; dead upstream, unmaintained, no rdeps
Package: ftp.debian.org Severity: normal Hi, please remove gnome-themes from the archive. It's dead upstream and hasn't seen any love downstream as well. There aren't any rdeps, so can be removed safely. Please make sure to not remove the gnome-accessibility-themes binary packages which are built from src:gnome-themes-standard. Thanks, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787161: RM: gnome-themes-extras -- ROM; dead upstream, unmaintained, no rdeps
Package: ftp.debian.org Severity: normal Hi, as like with gnome-themes [1], I'd also want to request the removal of gnome-themes-extras. Same reasons and circumstances apply (unmaintained, dead upstream, no rdeps). Thanks, Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787160 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787162: g++-mingw-w64-i686: error adding symbols: File format not recognized
Package: g++-mingw-w64-i686 Version: 4.9.1-19+14.3 Severity: important Dear Maintainer, sorry if this is the wrong package to report this bug. I have a regression in jessie compared to wheezy. The following link line does not work anymore for me: $ /usr/bin/i686-w64-mingw32-g++ -Wl,--whole-archive CMakeFiles/countlevels.dir/objects.a -Wl,--no-whole-archive -o countlevels.exe -Wl,--out-implib,libcountlevels.dll.a -Wl,--major-image-version,0,--minor-image-version,0 ../NDPRead.lib .../NDPRead.lib: error adding symbols: File format not recognized collect2: error: ld returned 1 exit status NDPRead.lib is a private lib, I cannot redistribute it. I suspect it has been build with Visual Studio (which version I do not know). It used to work just fine from wheezy. For references: $ objdump -h NDPRead.lib | head In archive NDPRead.lib: NDPRead.dll: file format pe-i386 Sections: Idx Name Size VMA LMA File off Algn 0 .debug$S 0041 008c 2**0 CONTENTS, READONLY, DEBUGGING 1 .idata$2 0014 00cd 2**2 CONTENTS, ALLOC, LOAD, RELOC, DATA -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (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 g++-mingw-w64-i686 depends on: ii gcc-mingw-w64-base 4.9.1-19+14.3 ii gcc-mingw-w64-i686 4.9.1-19+14.3 ii libc6 2.19-18 ii libcloog-isl4 0.18.2-1+b2 ii libgmp102:6.0.0+dfsg-6 ii libisl100.12.2-2 ii libmpc3 1.0.2-1 ii libmpfr43.1.2-2 ii zlib1g 1:1.2.8.dfsg-2+b1 g++-mingw-w64-i686 recommends no packages. Versions of packages g++-mingw-w64-i686 suggests: pn gcc-4.9-locales -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787163: At the new package tracker the section bugs not shown
Package: tracker.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Since some day the section with the bugs are not more shown. - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/6 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) -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJVaDb8AAoJEAn4nzyModJdbpYP/02G425LtV+cvXb3cSdJwP7P MRq0YBpcxTcw31c/+pX/qQXUdSknoxTMyRY5ZESbksXpyRGU9Fb8ikwZ2Te5JrLb 1kACiJflsbyPlzPgLj81KAiB6EVY9BlV9rerM0r8nM2n2YJ6qggv2Q73M7xLNMlA A/3XtBAZY95qJS1Cmh8vhC5y5SWqRphTeeajv1006k9L6JBLmM9sCOpl184zqrtj z8kBzI2RoUbBGn64sAOU8/VKGJmZ3TLTUOw8kfpVEb1/xQcqVbxzNMprIUkzrVuU tJawRd78idOxQi2O+cxxIeO6egvn/dXlgFax2AV2nrj4FJtcvb2P3hKPWXDRl9v4 oDpgngHTW0qD2Ny303akTwnyjXPoSTLzPVY+nh/HWnkChD9csgTCT65Sr0YV/dG2 fD1BMGgfJgM7lUbSdt+OPWH/wFL7bmoXm7x87MqmgfS6jK+pT9iT4AEWc0C1NYIH 15Se1Az2biUt73bSzjowTPmYy75LA8Hc2FBk4M53/AZ6awX/oMkzOuZm7OZDbUmh E3DZIpUPcSsTZq91VAaaXeB77I7SoNx8KNclhhB7RCDkCw+MCPHg8Ue+/sBGXu1s iCsUHqRuKZCdX0dAkoEoW5Amv3IHhVx6RKIo9OxxODOtrM33Lw0RDGgsl/GbBavO 26i0x4MU+HX3sXqLrRxO =8xvs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
On Friday 29 May 2015 02:46 PM, Cyril Brulebois wrote: > It might be useful to provide a log so that we understand what's > happening here. Just tested with "Graphical Install" from boot menu and grub install is working. So we can mention it as a work around. I will now try live install again and provide logs. signature.asc Description: OpenPGP digital signature
Bug#784000: [Pkg-fglrx-devel] Bug#784000: fglrx-driver: 32bit opengl does not work
Am 02.05.2015 um 01:38 schrieb tester: Package: fglrx-driver Version: 1:14.12-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I update to this driver, based on the AMD hype about it. The 32bit opengl does not work under wine, but opengl does work in a 64bit prefix. The 32bit packages are loaded , I have no idea why it doesnt work. This is on t a testing or Jessie install with this driver being the only thing not from the jessie repo *** End of the template - remove these template lines *** What is your output of: dpkg -l|egrep "fglrx|amd|ati|wine" -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail: pmatth...@debian.org patr...@linux-dev.org */ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787042: util-linux: FTBFS on kFreeBSD due to missing F_DUPFD_CLOEXEC
If something FTBFS on kfreebsd please just send a short note to us anyway, and if it's an essential package it's in our interest to get around to fixing it. It doesn't affect testing migrations meanwhile. You clearly had some other things to say but it might have been better to discuss that in a separate thread on debian-bsd and/or other lists; so that the bug log is as clear and easy to follow as possible. Given how trivial bug #785796 really is, I wish it had been handled with much less effort all round. Andreas Henriksson wrote: > Haven't found where the updated patch went yet (maybe I'm just too stressed). To solve the immediate problem, we just need util-linux to build, it wouldn't even need to be entirely functional. Guillem's "patch 1" would do that, though it is messy and shouldn't be upstreamed or permanent: https://bugs.debian.org/cgi-bin/bugreport.cgi?filename=kfreebsd-fcntl-dupfd-cloexec.patch;msg=5;att=1;bug=787042 (it could probably go away in the very next util-linux upload) His much cleaner fixes are patches 2 and 3 - these look OK to go upstream - with those you should no longer need patch 1: https://lists.debian.org/debian-bsd/2015/05/msg00050.html my testing feedback is here: https://lists.debian.org/debian-bsd/2015/05/msg00051.html A longer-term fix is that we add support for F_DUPFD_CLOEXEC, but that requires work on the buildds which will take several days. > I think I've managed to wrestle the BTS so that the *closed* bug no > longer should prevent testing migration. I think that was a BTS quirk of the bug not having either a 'found' or 'fixed' version. Being marked as 'done' makes no difference to it. Also the snapshot of BTS data is taken at around 1800 UTC so changes after that don't get considered until the *next* day's Britney run. Looks okay to migrate now, and sysvinit-utils too. Regards, -- Steven Chamberlain ste...@pyro.eu.org signature.asc Description: Digital signature
Bug#787162: g++-mingw-w64-i686: error adding symbols: File format not recognized
Control: found -1 2.25-5+5.2 Control: fixed -1 2.25-7+6 Control: affects -1 src:gcc-mingw-w64 Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=17910 Control: tags -1 patch fixed-upstream On Fri, May 29, 2015 at 12:00 PM, Stephen Kitt wrote: > Control: reassign -1 binutils-mingw-w64-i686 right ! > Hi Mathieu, > > Le 29/05/2015 11:41, Mathieu Malaterre a écrit : >> >> sorry if this is the wrong package to report this bug. I have a >> regression in jessie compared to wheezy. The following link line does >> not work anymore for me: >> >> $ /usr/bin/i686-w64-mingw32-g++ -Wl,--whole-archive >> CMakeFiles/countlevels.dir/objects.a -Wl,--no-whole-archive -o >> countlevels.exe -Wl,--out-implib,libcountlevels.dll.a >> -Wl,--major-image-version,0,--minor-image-version,0 ../NDPRead.lib >> .../NDPRead.lib: error adding symbols: File format not recognized >> collect2: error: ld returned 1 exit status >> >> NDPRead.lib is a private lib, I cannot redistribute it. I suspect it >> has been build with Visual Studio (which version I do not know). >> >> It used to work just fine from wheezy. > > > Could you try downgrading binutils-mingw-w64-i686 (only) to the wheezy > version? indeed that work also. so working versions are 2.22-8+2+b1 (wheezy) & 2.25-7+6 (sid), buggy version is 2.25-5+5.2 (jessie) I've just tested the patch: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=patch;h=cdb602b17548eeebb5e700c507d734ea5f887a49;hp=6f98576f29a70ed947f102015df0388bccc6aa1a It works locally. It is a nasty bug, since it render mingw64 package very limited (at least for me). 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786395: drag and drop to bookmarks in side pane does not work
Hi, > I cannot add files as a bookmark (not sure if this has been the intention, > it did not work before applying this patch) Yes, it didn't work before as well. I think this is a feature: bookmarks are for quick access to the folders, not files. > BAD: I cannot add new folderish bookmarks via drag'n'drop to the bookmark > section -> not good... Oh indeed, this is broken, it doesn't work now in 1.10 (the commit has been pushed on Mar 21, 2014). Previously, you could drag a folder to the empty space in bookmarks section, then a horizontal line appeared and you could drop the new folder there so it would become a new bookmarks. Now that line doesn't appear and you can only drop the new folder into one of the existing bookmarks - which will move the dragged folder into that bookmarked folder... Thanks for finding it. We'll need to figure out how to fix this in 1.10...
Bug#787162: g++-mingw-w64-i686: error adding symbols: File format not recognized
Control: reassign -1 binutils-mingw-w64-i686 Hi Mathieu, Le 29/05/2015 11:41, Mathieu Malaterre a écrit : sorry if this is the wrong package to report this bug. I have a regression in jessie compared to wheezy. The following link line does not work anymore for me: $ /usr/bin/i686-w64-mingw32-g++ -Wl,--whole-archive CMakeFiles/countlevels.dir/objects.a -Wl,--no-whole-archive -o countlevels.exe -Wl,--out-implib,libcountlevels.dll.a -Wl,--major-image-version,0,--minor-image-version,0 ../NDPRead.lib .../NDPRead.lib: error adding symbols: File format not recognized collect2: error: ld returned 1 exit status NDPRead.lib is a private lib, I cannot redistribute it. I suspect it has been build with Visual Studio (which version I do not know). It used to work just fine from wheezy. Could you try downgrading binutils-mingw-w64-i686 (only) to the wheezy version? Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787162: Fwd: Bug#787162: g++-mingw-w64-i686: error adding symbols: File format not recognized
Control: found -1 2.25-5+5.2 Control: fixed -1 2.25-7+6 Control: affects -1 src:gcc-mingw-w64 second try... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787156: libstrongswan: configuration file for logcheck ignores completely outdated (useless)
Am Freitag, 29. Mai 2015, 10:10:41 schrieben Sie: > I will now (with some patience) set out to create ignore patterns for my > local installations of stronswan, and install them on my machines. If they > may be of any help, when done I can send them to you as a skeleton for > updated logcheck ignore files. In the meanwhile, I recommend that you > either remove altogether the current stronswan files in the > /etc/logcheck/ignore.d.* directories, or replace them with empty > placeholders, until you have something more useful to put in them. It will be much appreciated if you can send your patterns - unfortunately, I am currently not using logcheck in production myself (time constraints), and therefore don't notice those issues. best regards, Rene signature.asc Description: This is a digitally signed message part.
Bug#787164: ITP: berkshelf -- Manages a Cookbook's, or an Application's, Cookbook dependencies
Package: wnpp Severity: wishlist Owner: Hleb Valoshka <375...@gmail.com> * Package name: berkshelf Version : 3.2.4 Upstream Author : Berkshelf Core Team * URL : http://berkshelf.com/ * License : Apache-2.0 Programming Lang: Ruby Description : Manages a Cookbook's, or an Application's, Cookbook dependencies berkshelf for chef cookbooks is like apt for debs. - it widely used in usual chef workflow - i plan to maintain it inside ruby-pkg-extras -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787129: apt-setup-udeb: No contrib and non-free by default
Control: tag -1 moreinfo Cyril Brulebois (2015-05-29): > Paul van der Vlis (2015-05-28): > > deb cdrom:[Debian GNU/Linux 8.0.0 _Jessie_ - Official amd64 DVD Binary-1 > > 20150425-12:54]/ jessie contrib main > > > > deb http://ftp.nl.debian.org/debian/ jessie main > > deb-src http://ftp.nl.debian.org/debian/ jessie main > > > > deb http://security.debian.org/ jessie/updates main contrib > > deb-src http://security.debian.org/ jessie/updates main contrib > > > > # jessie-updates, previously known as 'volatile' > > deb http://ftp.nl.debian.org/debian/ jessie-updates main contrib > > deb-src http://ftp.nl.debian.org/debian/ jessie-updates main contrib > > Without having looked at the code path yet, I'd appreciate seeing an > installer syslog (/var/log/installer). (Still happy to see a log; tagging accordingly.) The mirror line is built depending on whether contrib/non-free are requested, and we end up with main only. Security and jessie-updates are built differently, the generators look whether contrib and/or non-free are enabled in sources.list.new already and enable them accordingly. Since there's already a contrib entry due to the cdrom line, that's how it ends up in the jessie/updates and jessie-updates entries. This leaves us with the following question: why does the cdrom: line contain contrib. To which I don't have an immediate answer. Mraw, KiBi. signature.asc Description: Digital signature
Bug#787165: python-pip: some pip commands don't work: freeze, list, maybe others
Package: python-pip Version: 1.5.6-6 Severity: important For instance: root@t410:~# pip freeze Exception: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/usr/lib/python2.7/dist-packages/pip/commands/freeze.py", line 74, in run req = pip.FrozenRequirement.from_dist(dist, dependency_links, find_tags=find_tags) File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 299, in from_dist assert len(specs) == 1 and specs[0][0] == '==' AssertionError Storing debug log for failure in /root/.pip/pip.log root@t410:~# pip list apsw (3.8.6.post1) archivemail (0.9.0) argparse (1.2.1) BeautifulSoup (3.2.1) beautifulsoup4 (4.1.3) Exception: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/usr/lib/python2.7/dist-packages/pip/commands/list.py", line 80, in run self.run_listing(options) File "/usr/lib/python2.7/dist-packages/pip/commands/list.py", line 142, in run_listing self.output_package_listing(installed_packages) File "/usr/lib/python2.7/dist-packages/pip/commands/list.py", line 151, in output_package_listing if dist_is_editable(dist): File "/usr/lib/python2.7/dist-packages/pip/util.py", line 367, in dist_is_editable req = FrozenRequirement.from_dist(dist, []) File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 299, in from_dist assert len(specs) == 1 and specs[0][0] == '==' AssertionError -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (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 python-pip depends on: ii ca-certificates 20141019 ii python2.7.9-1 ii python-colorama 0.3.3-1 ii python-distlib0.2.0-2 ii python-html5lib 0.999-3 ii python-pkg-resources 16.0-2 ii python-requests 2.4.3-6 ii python-setuptools 16.0-2 ii python-six1.9.0-3 pn python:any Versions of packages python-pip recommends: ii build-essential 11.7 pn python-dev-all ii python-wheel 0.24.0-1 python-pip suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787093: autopkgtest: dpkg-deb chokes with build profiles in Build-Depends:
Hi,
On Fri, May 29, 2015 at 02:52:10AM +0200, Guillem Jover wrote:
> Hi!
>
> On Thu, 2015-05-28 at 20:14:29 -0300, Antonio Terceiro wrote:
> > From 14e2a91d48397546d2cc303082322e49f41c57f8 Mon Sep 17 00:00:00 2001
> > From: Antonio Terceiro
> > Date: Thu, 28 May 2015 20:10:23 -0300
> > Subject: [PATCH] Reduce build profiles when installing dependencies
>
> > Build-Depends: lines using build profiles cannot be transformed as-is to
> > Depends: lines. Luckily Dpkg::Deps already knows how to process build
> > profiles so we just need to tell it to do that.
>
> > diff --git a/runner/adt-run b/runner/adt-run
> > index 71255d0..b97e6c5 100755
> > --- a/runner/adt-run
> > +++ b/runner/adt-run
> > @@ -971,7 +971,8 @@ fi
> > perl = subprocess.Popen(['perl', '-'], stdin=subprocess.PIPE,
> > stdout=subprocess.PIPE)
> > code = '''use Dpkg::Deps;
> > - $dep = deps_parse('%s', reduce_arch => 1, host_arch =>
> > '%s');
> > + $dep = deps_parse('%s', reduce_arch => 1, host_arch =>
> > '%s',
> > +reduce_profiles => 1);
> >print $dep->output(), "\\n";
> >''' % (deps, self.dpkg_arch)
>
> If this is indeed parsing Build-Depends, you probably also want
> “build_dep => 1” there.
Thanks for the tip.
In a part of the time, that code will be parsing Build-Depends that will
be turned into Depends: of a fake package that is installed to pull in test
dependencies. In that case, besides build_dep, is that anything else we
need to pass to be sure that the end result is compatible with Depends: ?
--
Antonio Terceiro
signature.asc
Description: Digital signature
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
On Friday 29 May 2015 03:30 PM, Pirate Praveen wrote: > I will now try live > install again and provide logs. > When I choose "save debug logs" option and choose web, I can only see "hardware-summary" and "partman", which is not very useful. Should this be filed as another bug? When I look at /var/log/ only these files are present. When I chroot into /target, not much useful info in /var/log as well When I run apt-cache policy grub-pc there is no candidate present because the installation media is not selected as an apt source. When I execute a shell from installer menu and run apt-cdrom add and exit. grub install succeeds. So all we need to do is run apt-cdrom add if they choose not to use a network mirror. signature.asc Description: OpenPGP digital signature
Bug#786773: ruby-activesupport: Tries to overwrite files from `ruby-activesupport-3.2`
On Mon, May 25, 2015 at 03:06:03PM +0200, Paul Menzel wrote: > Dear Antonio, > > > Am Montag, den 25.05.2015, 10:00 -0300 schrieb Antonio Terceiro: > > On Mon, May 25, 2015 at 02:37:37PM +0200, Paul Menzel wrote: > > > Package: ruby-activesupport > > > Version: 4.1.10-1 > > > Severity: normal > > > > Having the package `ruby-activesupport-3.2` (3.2.19-1) installed, > > > installing the package `ruby-activesupport` (4.1.10-1) fails. > > > > > > Entpacken von ruby-activesupport (2:4.1.10-1) ... > > > dpkg: Fehler beim Bearbeiten des Archivs > > > /var/cache/apt/archives/ruby-activesupport_2%3a4.1.10-1_all.deb > > > (--unpack): > > > Versuch, »/usr/lib/ruby/vendor_ruby/active_support.rb« zu > > > überschreiben, welches auch in Paket ruby-activesupport-3.2 3.2.19-1 ist > > > dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal > > > (Datenübergabe unterbrochen (broken pipe)) getötet > > > > > > (Tries to overwrite `/usr/lib/ruby/vendor_ruby/active_support.rb` also > > > present in package ruby-activesupport-3.2 3.2.19-1.) > > > > > > Please add the corresponding lines to `Breaks` and `Conflicts` meta > > > data(?). > > > > ruby-activesupport used to have Conflicts/Breaks against > > ruby-activesupport-3.2; but ruby-activesupport-3.2 is only present in > > wheezy, and the `ruby` from jessie already conflicts with it so > > ruby-activesupport-3.2 should have been removed during some upgrade. > > I see. > > > How up to date is your system? > > It’s up to date. But as I still have some RoR 3.2 applications, I put > the RoR/Active* packages on hold to stay at 3.2. In that case you should not install ruby-activesupport. -- Antonio Terceiro signature.asc Description: Digital signature
Bug#787166: [systemd] Make /var/log/journal nocow
Package: systemd Version: 215-18 Severity: wishlist Please set /var/log/journal as nocow to avoid extreme fragmentation and slow performance on CoW filesystems like btrfs. $ chattr +C /var/log/journal --- System information. --- Architecture: amd64 Kernel: Linux 4.0.0-1-amd64 Debian Release: stretch/sid 500 unstablehttpredir.debian.org --- Package information. --- Depends(Version) | Installed -+-= libacl1(>= 2.2.51-8) | 2.2.52-2 libaudit1 (>= 1:2.2.1) | 1:2.4-1+b1 libblkid1(>= 2.17.2) | 2.26.2-5 libc6 (>= 2.17) | libcap2(>= 2.10) | libcryptsetup4 (>= 2:1.4.3) | libdbus-1-3 (>= 1.1.1) | libgcrypt11 (>= 1.5.1) | libkmod2 (>= 5~) | liblzma5(>= 5.1.1alpha+20120614) | libpam0g (>= 0.99.7.1) | libselinux1 (>= 2.1.9) | libsystemd-daemon0 (= 208-6) | libsystemd-journal0(= 208-6) | libudev1(>= 189) | libwrap0 (>= 7.6-4~) | libsystemd-login0 (= 208-6) | util-linux (>= 2.19.1-2) | initscripts (>= 2.88dsf-17) | sysv-rc | udev | acl | adduser | libcap2-bin | Recommends (Version) | Installed =-+-=== libpam-systemd| 215-18 Suggests(Version) | Installed =-+-=== systemd-ui| --- Output from package bug script --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786763: redmine: error messages during update of ruby-rails packages
Control: reassign -1 dpkg On Mon, May 25, 2015 at 02:07:37PM +0200, Jörg-Volker Peetz wrote: > Antonio Terceiro wrote on 05/25/2015 13:48: > > > > I'm sorry but I cannot see what is the problem; did you forget to > > include the actual error messages? > > > Hi Antonio, > > it's further down: > > Setting up ruby-activesupport (2:4.1.10-1) ... > dpkg: cycle found while processing triggers: > chain of packages whose triggers are or may be responsible: > redmine -> redmine > packages' pending triggers which are or may be unresolvable: > libc-bin: ldconfig > redmine: /usr/lib/ruby/vendor_ruby > dpkg: error processing package libc-bin (--configure): > triggers looping, abandoned > dpkg: cycle found while processing triggers: > chain of packages whose triggers are or may be responsible: > redmine -> redmine -> redmine > packages' pending triggers which are or may be unresolvable: > redmine: /usr/lib/ruby/vendor_ruby > dpkg: error processing package redmine (--configure): > triggers looping, abandoned > > ... > > Errors were encountered while processing: > libc-bin > redmine > E: Sub-process /usr/bin/dpkg returned an error code (1) > Failed to perform requested operation on package. Trying to recover: > Setting up libc-bin (2.19-18) ... That looks like a problem in dpkg. Did you try upgrading dpkg before upgrading the rest of the system? Or trying again after the above happened? -- Antonio Terceiro signature.asc Description: Digital signature
Bug#784943: jessie-pu: package ruby-defaults/1:2.1.5+deb8u1
On Thu, May 28, 2015 at 06:54:05PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sun, 2015-05-10 at 19:59 -0300, Antonio Terceiro wrote: > > This adds a Conflicts: against ruby-activesupport-2.3 to help with > > upgrade paths from wheezy; a similar change was made before the release > > for ruby-activesupport-3.2. > > Please go ahead. Done. -- Antonio Terceiro signature.asc Description: Digital signature
Bug#787167: port of debian-goodies' python scripts to python3
Package: debian-goodies Severity: wishlist Tags: patch Submitter: Alexandre Detiste The attached mail has been received at debian-good...@packages.debian.org. Forwarding to the BTS for not getting lost. Thanks to Alexandre for the patch! 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 --- Begin Message --- Hi, Here is a port of the 3 python applets included in debian-goodies: - popbugs - checkrestart - which-pkg-broke https://github.com/a-detiste/debian-goodies/commit/fcce6fe64b194513304f782cd2946eafc2aedf23 Alexandre Detiste --- End Message ---
Bug#784942: autopkgtest: fails to read Files: from perfectly valid .changes file
On Tue, May 26, 2015 at 06:31:15PM +0200, Martin Pitt wrote: > Control: tag -1 unreproducible > > Hey Antonio, > > sorry for the late response. > > Antonio Terceiro [2015-05-10 19:45 -0300]: > > I am missing anything? > > > > $ adt-run --user debci --output-dir /tmp/adt-run > > ../build-area/ruby-defaults_2.1.5.0_amd64.changes --- schroot > > debci-unstable-amd64 > > adt-run: error: ../build-area/ruby-defaults_2.1.5.0_amd64.changes is > > invalid and does not contain Files: > > [20]$ cat ../build-area/ruby-defaults_2.1.5.0_amd64.changes > > I tried that .changes files, and it works correctly here. Maybe just > pasting it into the email destroyed some subtle whitespace? Can you > attach the file instead? > > I also got ruby-defaults 2.1.5.0 from the archive, sbuilt it, and ran > adt-run on the binary unsigned .changes, which also worked. > > If you can still reproduce this, I can also send you some patch for > enhancing debugging in runner/adt-run files_from_dsc() -- it seems the > parse_rfc822() runs into a corner case? I can still reproduce it, yes: $ adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run: error: ruby-defaults_2.1.5.0_amd64.changes is invalid and does not contain Files: [20]$ debsign ruby-defaults_2.1.5.0_amd64.changes [...] Successfully signed dsc and changes files $ adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run [07:57:45]: version 3.14.2 adt-run [07:57:45]: command line: /usr/bin/adt-run --user debci --output-dir /tmp/adt-run ruby-defaults_2.1.5.0_amd64.changes --- schroot debci-unstable-amd64 adt-run [07:57:46]: testbed dpkg architecture: amd64 adt-run [07:57:46]: source ruby-defaults_2.1.5.0.dsc OK [...] adt-run [07:57:59]: test smoke-test: ---] adt-run [07:57:59]: test smoke-test: - - - - - - - - - - results - - - - - - - - - - smoke-test PASS The original ruby-defaults_2.1.5.0_amd64.changes, without the signature, is attached. -- Antonio Terceiro Format: 1.8 Date: Sun, 10 May 2015 19:39:16 -0300 Source: ruby-defaults Binary: ruby ruby-dev ruby-all-dev libruby libtcltk-ruby ri ruby-full Architecture: source all Version: 1:2.1.5.0 Distribution: experimental Urgency: medium Maintainer: Antonio Terceiro Changed-By: Antonio Terceiro Description: libruby- Libraries necessary to run Ruby libtcltk-ruby - Tcl/Tk interface for Ruby ri - Ruby Interactive reference ruby - Interpreter of object-oriented scripting language Ruby (default v ruby-all-dev - Ruby development environment (all versions supported in Debian) ruby-dev - Header files for compiling extension modules for Ruby (default ve ruby-full - Ruby full installation (default version) Changes: ruby-defaults (1:2.1.5.0) experimental; urgency=medium . [ Lucas Nussbaum ] * Drop myself from Uploaders. . [ Antonio Terceiro ] * ruby Conflicts: ruby-activesupport-2.3 to help with several Rails-related upgrade issues, when using Rails 2.3 (with e.g. redmine from wheezy). See #779882 * Cleanup Uploaders: remove akira yamada and Daigo Moriwaki . We are grateful to their previous maintainance of ruby in Debian, but in practive they haven't done anything in quite a few years. Checksums-Sha1: d34b61ba2c12b5860d363aedc2d3c35e0139ea29 1952 ruby-defaults_2.1.5.0.dsc 7662902442fd42278b09ac89261e3d9da6e48ea0 10144 ruby-defaults_2.1.5.0.tar.xz 106f446405adc273ca62df1bb65eeb18f9fc3b55 9832 ruby_2.1.5.0_all.deb b249b149d6dbf21c2d2da5e03464d84f02237f32 8502 ruby-dev_2.1.5.0_all.deb 8d6cb904faaf727b358a5b3ccef05097a9741adb 9210 ruby-all-dev_2.1.5.0_all.deb 2279ec9bbb027ca682414bfbb1f6f8bbc277b80a 8442 libruby_2.1.5.0_all.deb 16659e51bf57fe5ec7a72f26acd0080ea2c9a1ca 8332 libtcltk-ruby_2.1.5.0_all.deb 17cb2acb282b33bd964d0fc85d8ae4bfb6603486 8484 ri_2.1.5.0_all.deb 8b18e1c8caf0bddb801ac8c98a1fbd367ae0cc93 8440 ruby-full_2.1.5.0_all.deb Checksums-Sha256: d4ae3f1b8996df51e1793d3c9ac19e18d8b999aeae2050fc2dc0a7a88c58440a 1952 ruby-defaults_2.1.5.0.dsc d3a0ce859829a854f832d2229c7eccfb8470002726c7200099c38ee38f25b519 10144 ruby-defaults_2.1.5.0.tar.xz 130f4b9c6f0a1d8b8f055c5c435d30872fc6e39cf21798bd8a0232795a48f952 9832 ruby_2.1.5.0_all.deb 999be80d9313b7991c3d82c49afb13f5111e8ae592be9fc46f1129f415a2d616 8502 ruby-dev_2.1.5.0_all.deb d50e7a44f236fcd5a7ea38d41b9949e7375c7f2394288ae64ce29cfc8ab027ee 9210 ruby-all-dev_2.1.5.0_all.deb 31d4a33044621f694f20ab6fd2129af13b59561022042474267aac4413f3b8f5 8442 libruby_2.1.5.0_all.deb c4fe30213615254b24fd311338deb4237646de1919265d925ea2cc9b0c7bf97e 8332 libtcltk-ruby_2.1.5.0_all.deb 1b0e1d4563527a76abbc1feb71814da544640b21b5c6c25a6b3656126f9e90ae 8484 ri_2.1.5.0_all.deb c3d0e80c8c6894af6ddad958b9695df5ef1a440b40f08328648eedd33497e92d 8440 ruby-full_2.1.5.0_all.deb Files: 602e81d7e320f51490efa6a2acdf8f93 1952 ruby
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
On Friday 29 May 2015 04:10 PM, Pirate Praveen wrote: > So all we need to do is run apt-cdrom add if they choose not to use a > network mirror. Also the installation hangs at "Running exit-installer" step Restarting the system at this stage gives you a working installation, but it is an irritant. signature.asc Description: OpenPGP digital signature
Bug#787133: Acknowledgement (libu2f-server: FTBFS on arm64, ...)
Sorry, I seem to have sent the wrong version of the patch. This one is
better, I think.
diff -ru libu2f-server-0.0.0.orig/u2f-server/cdecode.c libu2f-server-0.0.0/u2f-server/cdecode.c
--- libu2f-server-0.0.0.orig/u2f-server/cdecode.c 2014-11-24 14:29:01.0 +
+++ libu2f-server-0.0.0/u2f-server/cdecode.c 2015-05-28 22:05:25.88000 +
@@ -9,7 +9,7 @@
int base64_decode_value(char value_in)
{
- static const char decoding[] =
+ static const signed char decoding[] =
{ 62, -1, -1, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, -1, -1, -1,
-2, -1,
-1, -1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16,
@@ -35,11 +35,12 @@
int
base64_decode_block(const char *code_in, const int length_in,
-char *plaintext_out, base64_decodestate * state_in)
+char *plaintext_out_, base64_decodestate * state_in)
{
const char *codechar = code_in;
- char *plainchar = plaintext_out;
- char fragment;
+ unsigned char *plaintext_out = (unsigned char *) plaintext_out_;
+ unsigned char *plainchar = plaintext_out;
+ int fragment;
*plainchar = state_in->plainchar;
@@ -52,7 +53,7 @@
state_in->plainchar = *plainchar;
return plainchar - plaintext_out;
}
-fragment = (char) base64_decode_value(*codechar++);
+fragment = base64_decode_value(*codechar++);
}
while (fragment < 0);
*plainchar = (fragment & 0x03f) << 2;
@@ -63,7 +64,7 @@
state_in->plainchar = *plainchar;
return plainchar - plaintext_out;
}
-fragment = (char) base64_decode_value(*codechar++);
+fragment = base64_decode_value(*codechar++);
}
while (fragment < 0);
*plainchar++ |= (fragment & 0x030) >> 4;
@@ -75,7 +76,7 @@
state_in->plainchar = *plainchar;
return plainchar - plaintext_out;
}
-fragment = (char) base64_decode_value(*codechar++);
+fragment = base64_decode_value(*codechar++);
}
while (fragment < 0);
*plainchar++ |= (fragment & 0x03c) >> 2;
@@ -87,7 +88,7 @@
state_in->plainchar = *plainchar;
return plainchar - plaintext_out;
}
-fragment = (char) base64_decode_value(*codechar++);
+fragment = base64_decode_value(*codechar++);
}
while (fragment < 0);
*plainchar++ |= (fragment & 0x03f);
Bug#787168: "filter failed" error when trying to print on HP M1132
Subject: hplip: "filter failed" error when trying to print on HP M1132 Package: hplip Version: 3.14.6-1+b2 Severity: normal 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 *** -- Package-specific info: Saving output in log file: /home/konst/hp-check.log HP Linux Imaging and Printing System (ver. 3.14.6) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" warning: debian-8.0 version is not supported. Using debian-7.5 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) GNU/Linux Host: sysadmin-debian Proc: 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) GNU/Linux Distribution: debian 8.0 Bitness: 32 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.14.6 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for debian distro 8.0 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.14.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip-doc/HTML html=/usr/share/doc/hplip-3.14.6 icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=yes foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.14.6 restricted-build=no ui-toolkit=qt4 qt3=no qt4=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [installation] date_time = 05/29/15 13:55:45 version = 3.14.6 -- | External Dependencies | -- policykitAdmin-Policy-frameworkOPTIONAL- 0.105 OK - gs Ghostscript REQUIRED7.05 9.06OK - network Network-wget OPTIONAL- 1.16OK - scanimageShell-ScanningOPTIONAL1.0 1.0.24 OK - avahi-utils avahi-utils OPTIONAL- 0.6.31 OK - dbus DBus REQUIRED- 1.8.16 OK - cups CUPS REQUIRE
Bug#783890: [Pkg-sugar-devel] Bug#783890: Merged upstream: Add skip-install-mime option to bundlebuilder
Quoting James Cameron (2015-05-29 08:58:46) > An upstream patch to the source package sugar-toolkit-gtk3 is > available to help with this bug: > > https://github.com/sugarlabs/sugar-toolkit-gtk3/commit/e8553c13a11e53ea78928ac4ab547b460eb22de5 Yes, I already noticed. Thanks for mentioning here, anyway! :-) - 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#787093: autopkgtest: dpkg-deb chokes with build profiles in Build-Depends:
Hi, Quoting Antonio Terceiro (2015-05-29 12:42:44) > On Fri, May 29, 2015 at 02:52:10AM +0200, Guillem Jover wrote: > > If this is indeed parsing Build-Depends, you probably also want “build_dep > > => 1” there. > In a part of the time, that code will be parsing Build-Depends that will be > turned into Depends: of a fake package that is installed to pull in test > dependencies. In that case, besides build_dep, is that anything else we need > to pass to be sure that the end result is compatible with Depends: ? you can see how sbuild does it which also parses Build-Depends to then create a dummy binary package to install later from them: http://sources.debian.net/src/sbuild/0.65.2-1/lib/Sbuild/ResolverBase.pm/#L827 Turning build-depends into a binary package seem to be a common pattern not only shared by autopkgtest and sbuild but is also used by pbuilder or mk-build-deps. It would be great if there was a common library doing this but maybe the slightly different requirements of each software taking this approach as well as the different programming languages used make this tricky. On the other hand, I think all this software mainly does it that way because apt in unstable cannot yet be given a .dsc or unpacked debian/control and then satisfy the build dependencies from it. So everybody using apt to satisfy build dependencies of a local package first creates a dummy package from these build dependencies and only then passes it to apt. Maybe all the software using this approach can drop it once apt from experimental moves to unstable because that one can do `apt-get build-dep foo.dsc`. cheers, josch signature.asc Description: signature
Bug#787043: adequate: Adequate needs dependency on pkg-config for new missing-pkgconfig-dependency tag
Control: retitle 787043 adequate: missing autopkgtest dependency on pkg-config Control: clone 787043 -1 Control: retitle 787043 -1 adequate: missing Suggests/Recommends on pkg-config Control: found -1 0.13.2 * Micah Gersten , 2015-05-28, 15:12: adequate doesn't have hard dependency on pkg-config. It silently skips pkg-config checks if the package is not installed. Shouldn't it at least be a recommends since one would probably want to check all the tags in all but unusual cases? Or at least a Suggests? You're right of course. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#625777: French_France.1252
Control: found -1 4.9.1-19+14.3 If I compile `l.cxx` using VS 2010 (Win7/64bits), here is what I get: > cl l.cxx > l.exe French_France.1252 >From wine32 (current jessie): $ wine32 ./l.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 English_United States.1252 Now if I use i686-w64-mingw32-g++: $ i686-w64-mingw32-g++ l.cxx -static-libgcc -static-libstdc++ $ WINEPATH=/usr/lib/gcc/i686-w64-mingw32/4.9-win32 wine32 ./a.exe locale::facet::_S_create_c_locale name not valid Then from my cmd prompt (Win7/64bits): > a.exe C So clearly the behavior is slightly different (C != French locale), but at least "" is valid. 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787170: belle-sip: Vcs-Git and Vcs-Browser wrongly points to upstream git
Source: belle-sip Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vcs-* fields in control file of source package should reference Debian packaging resources, not upstream. If Debian packaging does not use a version control system (VCS) then those fields should simply be dropped. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVaEziAAoJECx8MUbBoAEhwpYP+wazRo5IRJZEg/mv1DoAIhPy S9kMTtyti3scBhJ5NVm7YkDZ3N0lhlGs829W5Z20L6t3ubKq061/viT3c8o89UsJ k8Y7/zu3jiEm+w9C6GwrjKJO3QJ9qHwHCzdG0CMWBTzupt5kEn9Moi/CopNB7IOo D0jpOX8eOU8YPZKOmjEIS1XmvARpFIzZFcbUuNNhCJKBaXw4Io5vBtVIRqWsc48A O5TdWrl3jWn1/HShE15/QMJINFsOgv+FFbLW5B8MoZgRWWJicrWSdoO48fHUZAZD e+QIe0lK5eCUbE0+YrBo7XPn6xFAZ7JGo6cRBcgQTBNWfUpDBihu+KKHPMijZgBk upmcVxVN7NAlQfHVQQFtIQc+oJ3Iv3ejA08gErH07DDDoj9fedwpfaWlE3ihtjf9 wb5asu8jRA7GWt1wl7aBZoAYLscpXtGcZgnGsrJRc3ESfkIVEy1GqV0RM9SHaupZ vZmitQd+QZ0Gc48xpOkrZ6MV1s7DqraobXX6LSq3UA5fTKxupwbh79jLBKzkj2he CZScnAmN4FsUQ0UuDe5V+50TGpDZDe+LS0+GyLOw1Vdql5wW9FoPVHRJ6dOf1YcG 2PEBrNupST92SrX2cRGEptvNxmMZU6T/Lpola+dlAchXnok+Hw6itVG0KZCd1BWW kaWlCriUlMSSI8cTj3lC =q28W -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#783718: linux-image-3.16.0-4-kirkwood: Regression: mv_cesa crypto driver fails a self-test
I have tested linux-image-kirkwood-4.0.0-2 from unstable and I can confirm that this bug has been fixed upstream and mv_cesa passes kernel self-tests.
Bug#786567: python-distlib-whl=0.2.0-2 breaks pip
This seems to be a duplicate of #785787 which was fixed with python-pip 1.5.6-6. -- http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787171: g++-mingw-w64: Document i686-w64-mingw32-g++: -posix vs -win32
Package: g++-mingw-w64 Version: 4.9.1-19+14.3 Severity: minor Dear Maintainer, Please consider adding a README.Debian file to document diffs between -posix and -win32 variant. Thanks -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages g++-mingw-w64 depends on: ii g++-mingw-w64-i6864.9.1-19+14.3 ii g++-mingw-w64-x86-64 4.9.1-19+14.3 ii gcc-mingw-w64-base4.9.1-19+14.3 g++-mingw-w64 recommends no packages. g++-mingw-w64 suggests no packages. -- no debconf information Quick notes about -win32 and -posix differences: The -win32 variant uses native Win32 threads, which results in binaries with no pthreads dependency. The -posix variant uses POSIX threads, which enables C++11 threads (and GOMP), but results in binaries depending on the pthreads DLL. https://bugs.debian.org/748353 gives a bit more context. -- Stephen Kitt Thu, 18 Dec 2014 07:23:13 +0100
Bug#787129: apt-setup-udeb: No contrib and non-free by default
Cyril Brulebois (2015-05-29): > This leaves us with the following question: why does the cdrom: line > contain contrib. To which I don't have an immediate answer. This is likely due to this in debian-cd: | commit 916440cf9a265370facae13776213aefaa8a28d6 | Author: Tollef Fog Heen | Date: Sat Dec 7 10:22:40 2002 + | | add support for excluding contrib. | … | + * Make it possible to exclude contrib from the CDs. Useful if you only | +have a mirror of main. | | - -- Raphael Hertzog Thu, 10 Oct 2002 14:52:15 +0200 | + -- Tollef Fog Heen Sat, 7 Dec 2002 10:58:53 +0100 | … | +# Do I want to have CONTRIB merged in the CD set | +export CONTRIB=1 | … Cc-ing debian-cd@ to get some input. Is having contrib enabled in official images a deliberate choice? And a reasonable one? Mraw, KiBi. signature.asc Description: Digital signature
Bug#787172: python-pylibacl: FTBFS with Sphinx 1.3: warning about theme rename
Source: python-pylibacl Version: 0.5.2-1 User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.3 python-pylibacl FTBFS with Sphinx 1.3 (which is available in experimental): sphinx-build -b html -d doc/doctrees -W doc doc/html Running Sphinx v1.3.1 making output directory... loading pickled environment... not yet created Warning, treated as error: WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default. Makefile:17: recipe for target 'doc/html/index.html' failed Dropping -W from sphinx-build options should fix it. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#787173: virt-manager: Can't access KVM kernel module
Package: virt-manager Version: 1:1.0.1-5 Severity: normal Hi When I try to create a new VM it says that it can't access KVM module. The modules are loaded: lsmod |grep kvm kvm_intel 139116 0 kvm 388635 1 kvm_intel And the permissions seems to be OK crw-rw+ 1 root kvm 10, 232 may 29 06:44 /dev/kvm I attach the virt-manager and VM logs Thanks in advance -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages virt-manager depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gconf2 3.2.6-3 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-gtk-vnc-2.0 0.5.3-1.3 ii gir1.2-libvirt-glib-1.0 0.1.9-4 ii gir1.2-vte-2.90 1:0.36.3-1 ii librsvg2-common 2.40.9-2 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-gi-cairo 3.14.0-1 ii python-ipaddr2.1.11-2 ii python-libvirt 1.2.15-1 ii python-urlgrabber3.9.1-4.1 pn python2.7:any pn python:any ii virtinst 1:1.0.1-5 Versions of packages virt-manager recommends: ii gir1.2-spice-client-gtk-3.0 0.25-1+b1 ii gnome-icon-theme 3.12.0-1 ii libvirt-daemon-system1.2.15-2 Versions of packages virt-manager suggests: pn gnome-keyring pn python-gnomekeyring pn python-guestfs pn ssh-askpass ii virt-viewer 1.0-1 [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (cli:187) Launched with command line: /usr/share/virt-manager/virt-manager --debug --no-fork [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (virt-manager:150) virt-manager version: 1.0.1 [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (virt-manager:151) virtManager import: [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (virt-manager:209) GTK version: 3.14.5 [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (engine:484) libguestfs inspection support: False /usr/share/virt-manager/virtManager/systray.py:124: Warning: The property GtkImageMenuItem:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version. exit_item = Gtk.ImageMenuItem.new_from_stock(Gtk.STOCK_QUIT, None) /usr/share/virt-manager/virtManager/systray.py:124: Warning: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version. exit_item = Gtk.ImageMenuItem.new_from_stock(Gtk.STOCK_QUIT, None) /usr/share/virt-manager/virtManager/systray.py:124: Warning: The property GtkImageMenuItem:accel-group is deprecated and shouldn't be used anymore. It will be removed in a future version. exit_item = Gtk.ImageMenuItem.new_from_stock(Gtk.STOCK_QUIT, None) [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (systray:152) Showing systray: False [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (engine:231) About to connect to uris ['qemu:///system'] /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:462: Warning: The property GtkImage:stock is deprecated and shouldn't be used anymore. It will be removed in a future version. return Gtk.Builder.add_from_string(self, buffer, length) /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:462: Warning: The property GtkImageMenuItem:image is deprecated and shouldn't be used anymore. It will be removed in a future version. return Gtk.Builder.add_from_string(self, buffer, length) /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py:462: Warning: The property GtkToolButton:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version. return Gtk.Builder.add_from_string(self, buffer, length) [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (manager:216) Showing manager [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (engine:385) window counter incremented to 1 [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (connection:995) Scheduling background open thread for qemu:///system [vie, 29 may 2015 13:27:31 virt-manager 29044] DEBUG (connection:1012) Background 'open connection' thread is running [vie, 29 may 2015 13:27:44 virt-manager 29044] DEBUG (connection:1063) Background open thread complete, scheduling notify [vie, 29 may 2015 13:27:44 virt-manager 29044] DEBUG (connection:1068) Notifying open result [vie, 29 may 2015
Bug#785762: gcc-4.9: Segfault on llvm build
Control: tags -1 + moreinfo Control: severity -1 normal On 05/20/2015 12:24 AM, Mike Dupont wrote: > Please submit a full bug report, > with preprocessed source if appropriate. > See for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787175: buildbot: FTBFS with Sphinx 1.3: warning about theme rename
Source: buildbot Version: 0.8.9-2 User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx1.3 buildbot FTBFS with Sphinx 1.3 (which is available in experimental): sphinx-build -b html -d _build/doctrees -q -W . _build/html Warning, treated as error: WARNING: the config value 'latex_show_urls' has type `bool', defaults to `str.' Makefile:60: recipe for target 'html' failed make[2]: *** [html] Error 1 Replacing "latex_show_urls = True" with "latex_show_urls = 'inline'" in docs/conf.py will fix it. See [1] for details. [1]: http://sphinx-doc.org/config.html#confval-latex_show_urls -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#785616: httpie: Please update to version 0.9.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's fine. Thanks again for taking care of that. regards Bartek W dniu 5/28/2015 o 9:35 PM, Vincent Bernat pisze: > ❦ 28 mai 2015 20:09 +0200, Bartosz Fenski : > >> I'd be more than happy if you could take care of it via NMU. I >> have madness in my job and I simply don't have time to work on >> that. >> >> You've got green light from me to prepare new version. > > Thanks! > > I have uploaded a new version. I wanted to upload to a delayed > queue but I did forget. Hope all is OK. > > httpie (0.9.2-0.1) unstable; urgency=low > > * Non-maintainer upload with maintainer's authorization. * New > upstream release. Closes: #785616. + This new release supports SNI. > Closes: #751568. + Remove https symlink. This feature is not > supported anymore. + Add build dependency to dh-python. + Disable > tests for now, they need pytest-httpbin. + Remove build dependency > to tox (unused). + Force "pybuild" build system for debhelper > (instead of makefile). + Update debian/copyright. * Switch httpie > package to "Architecture: all", as it is pure Python. Closes: > #750179. * Update debian/watch. * Bump Standards-Version to 3.9.6. > > For the tests, I have an ITP for both httpbin and pytest-httpbin > that are needed to run the tests. As it will take some time for me > to package them and they have to go through the NEW queue, I > preferred uploading without tests first. I'll do another NMU when > pytest-httpbin will be available (I'll ping you first). > -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJVaFNyAAoJELDZ1Kg807vBbWoQAJtjjOT6fFV17T5PFVnQeKh+ 0hAI/mtkeE6j6Wns86890mEMSuq7XnmiMETrMfnMGWOl5b5Ld0SeVzrCX9znLPxQ li3Ug+/jK+4JZnI8oQB1/yPvgBLy4u8hI/ghhYRm3Pg1N2OhFIxzvhErYDgFLz+c vLGUwcw9emOs6kIk4zCAEsshxoa8DvVq3kDWlv9osk6telmr75CDKijqUWzkzMV3 ce384Upw1+mV0UUq/7i0o3MJ9ROJW+LhLpgpQTZvh3luuiW8ABLsNteZNGdjEWyf JCjgmejUhvoxQwO+J7zHmpo6p+hXK7JyvlVZld8tL03rXakaubZCSDzkHEwbI/iT ZQf7TyAssQSvWp1HzQXsScNBPlbxOiCW6Y1eXUt5KHkC3NiPh1zLVjomLZgoGla0 QMumOLaw++7YHgr7zsGSoD5frpJl34MwdzlBIHFLLktif+p8CHj4Sf0G62tqGk56 VscONUSaYBcQbGLIJJIXbpxnjrhTmdCa2pddSohjB6sxAIpaDXux6UrAR0xWOr8g ODUgeJVJuJf7LDc2Ur1i+FJW2Xvj32o/7ciMNJ4Faayiv7MThhsqSvKsmqjeF8AO hzJFaiNmSxHlPKVONtYKdlunT7Q5nXbVG41YDP8Y9iMpb1Q61cK0Jtj/80yALf+x 9tcjUGqgAKETAtaFY86y =fA7P -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787174: remove unblockable new tab ads
Package: iceweasel Version: 38.0.1-5 Severity: normal The new tab page has been infested with ads provided by Mozilla. For example, I have seen ads for FedEx, and for some web password service. The only way to turn them off is to disable viewing tiles at all in the new tab page. Please disable this adware antifeature in iceweasel. -- see shy jo signature.asc Description: Digital signature
Bug#786850: gcc-4.9: AddressSanitizer fails with pthread_cond_init
Control: tags -1 + wontfix fixed-upstream upstream On 05/27/2015 02:30 PM, Erik de Castro Lopo wrote: >> please recheck with gcc-5 from unstable. > > > Works with gcc-5. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787176: netbeans: Remove w3c-dtd-xhtml reference from d/control
Source: netbeans Severity: serious Justification: rely on obsolete package Control: blocks 711332 with -1 Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332) -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787178: wdg-html-validator: Remove w3c-dtd-xhtml reference from d/control
Source: wdg-html-validator Severity: serious Justification: rely on obsolete package Control: blocks 711332 with -1 Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332), it has been superseded by w3c-sgml-lib. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787177: libnb-platform18-java: Remove w3c-dtd-xhtml reference from d/control
Source: libnb-platform18-java Severity: serious Justification: rely on obsolete package Control: blocks 711332 with -1 Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332), it has been superseded by w3c-sgml-lib. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787179: spip: Remove w3c-dtd-xhtml reference from d/control
Source: spip Severity: serious Justification: rely on obsolete package Control: blocks 711332 with -1 Please remove reference to w3c-dtd-xhtml from debian/control. This package will be removed for stretch (see #711332), it has been superseded by w3c-sgml-lib. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (700, 'stable'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
On Fri, 29 May 2015, Pirate Praveen wrote: > On Friday 29 May 2015 02:46 PM, Cyril Brulebois wrote: > > It might be useful to provide a log so that we understand what's > > happening here. > > Just tested with "Graphical Install" from boot menu and grub install is > working. So we can mention it as a work around. I will now try live > install again and provide logs. What do you mean with "live install"? running the installer from the graphical interface of the live system once started? If the bug is only reproducible there, then it's not necessarily a bug in live-installer but in debian-installer-launcher... and in the way it interacts with the current desktop. Cyril, don't count on me to look into this issue, I won't have the time to handle this, sorry. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#786763: redmine: error messages during update of ruby-rails packages
Antonio Terceiro wrote on 05/29/2015 12:49: > Control: reassign -1 dpkg > > On Mon, May 25, 2015 at 02:07:37PM +0200, Jörg-Volker Peetz wrote: >> Antonio Terceiro wrote on 05/25/2015 13:48: >> >> >>> I'm sorry but I cannot see what is the problem; did you forget to >>> include the actual error messages? >>> >> Hi Antonio, >> >> it's further down: >> >> Setting up ruby-activesupport (2:4.1.10-1) ... >> dpkg: cycle found while processing triggers: >> chain of packages whose triggers are or may be responsible: >> redmine -> redmine >> packages' pending triggers which are or may be unresolvable: >> libc-bin: ldconfig >> redmine: /usr/lib/ruby/vendor_ruby >> dpkg: error processing package libc-bin (--configure): >> triggers looping, abandoned >> dpkg: cycle found while processing triggers: >> chain of packages whose triggers are or may be responsible: >> redmine -> redmine -> redmine >> packages' pending triggers which are or may be unresolvable: >> redmine: /usr/lib/ruby/vendor_ruby >> dpkg: error processing package redmine (--configure): >> triggers looping, abandoned >> >> ... >> >> Errors were encountered while processing: >> libc-bin >> redmine >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> Failed to perform requested operation on package. Trying to recover: >> Setting up libc-bin (2.19-18) ... > > That looks like a problem in dpkg. Did you try upgrading dpkg before > upgrading the rest of the system? Or trying again after the above > happened? > On May 25 I encountered the problem when upgrading ruby-rails. I used and am still using dpkg version 1.18.0. I upgraded to this version from version 1.17.25 on May 19. -- Regards, Jörg. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787129: apt-setup-udeb: No contrib and non-free by default
Op 29-05-15 om 13:42 schreef Cyril Brulebois: > Cyril Brulebois (2015-05-29): >> This leaves us with the following question: why does the cdrom: line >> contain contrib. To which I don't have an immediate answer. It's not only about the "cdrom:" line, but also about the lines with the security and updates repositories: deb http://security.debian.org/ jessie/updates main contrib deb-src http://security.debian.org/ jessie/updates main contrib deb http://ftp.nl.debian.org/debian/ jessie-updates main contrib deb-src http://ftp.nl.debian.org/debian/ jessie-updates main contrib With regards, Paul van der Vlis -- Paul van der Vlis Linux systeembeheer, Groningen https://www.vandervlis.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787129: apt-setup-udeb: No contrib and non-free by default
Paul van der Vlis (2015-05-29): > Op 29-05-15 om 13:42 schreef Cyril Brulebois: > > Cyril Brulebois (2015-05-29): > >> This leaves us with the following question: why does the cdrom: line > >> contain contrib. To which I don't have an immediate answer. > > It's not only about the "cdrom:" line, but also about the lines with the > security and updates repositories: > > deb http://security.debian.org/ jessie/updates main contrib > deb-src http://security.debian.org/ jessie/updates main contrib > deb http://ftp.nl.debian.org/debian/ jessie-updates main contrib > deb-src http://ftp.nl.debian.org/debian/ jessie-updates main contrib I tried to explain that those are a direct consequence of contrib being on the cdrom line in the first place. Mraw, KiBi. signature.asc Description: Digital signature
Bug#787127: openscad segfault
hello lkcl, On Thu, May 28, 2015 at 09:33:15PM +0100, lkcl wrote: > openscad segfaults with the file that may be downloaded from the > following location: http://lkcl.net/openscad_bug.scad thans for reporting this; i can reproduce the problem with the current debian version of openscad. the issue is already fixed in openscad 2015.03, which i'm currently preparing for upload based on hyperair's work. i've had a hard time already trying to fix openscad crashes, and given the new release, i won't look into this much deeper and rather focus on getting the next version into sid, unstable, and backports. (of course i'd welcome patches, and assist them in getting into stable updates, but i doubt it's worth it). best regards chrysn -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom signature.asc Description: Digital signature
Bug#673426: update ?
Some notes: https://github.com/Bumblebee-Project/bumblebee-ppa/issues/30 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#738478: pngcrush maintenance
Hi Zack, According to #738478 [1] the position of "pngcrush" maintainer is vacant. I shall be happy to sponsor your work if you are willing to step in. Nelson, are you still interested/able to work on "pngcrush"? [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738478 -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- Success consists of going from failure to failure without loss of enthusiasm. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#782442: USB3 external HDD not recognized [regression]
Hi again, > Indeed doing "echo 'on' | sudo tee /sys/bus/pci/devices/*/power/control" > fixes the problem: When I subsequently plug in the disk, it is > recognized correctly. I confirmed this with an older kernel (the 3.16 > Debian kernel, to be more precise). That's good to know, now I don't > need to reboot to a different kernel anymore to do fast backups ;-) Is there any news on this? Any further information I can provide to help fix the issue? Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787180: wine-development (arch:all) does not satisfy dependencies of a foreign-architecture package
Source: wine-development Version: 1.7.41-3 Severity: normal Control: found -1 1.7.43-1 The package wine32-development recommends wine-development, but the latter is unavailable. I guess this happens because the package wine-development is Architecture: all since 1.7.41-3, but not marked as Multi-Arch. https://wiki.ubuntu.com/MultiarchSpec: This means that for an Architecture: all package to satisfy the dependencies of a foreign-architecture package, it must be marked Multi-Arch: foreign or Multi-Arch: allowed. So please add "Multi-Arch: foreign" to wineVERSION. btw: the package description of "wineVERSION" notes: "This is a virtual package that depends on the standard Wine components." which is not true, it is not virtual and has some content. Greets jre -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wine-development depends on: ii wine32-development 1.7.43-1 ii wine64-development 1.7.43-1 wine-development recommends no packages. wine-development suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#783721: Info received (Bug#783721: Acknowledgement (dnssec-tools: dnssec-signzone behaviour changed; new signed zonefiles unparseable by rollerd))
I have just had to pull the plug on six DNSSEC domains, as it has been a month without any movement on this bug and all my RRSIGs have now expired. Andrew. signature.asc Description: OpenPGP digital signature
Bug#787181: jessie-pu: 1:2.2.13-11~deb8u1
package: release.debian.org
severity: normal
x-debbugs-cc: jaldhar-dove...@debian.org, sanv...@unex.es
I would like to update dovecot to fix a mbox corruption issue that affects
the version in stable. (see bug #776094) Upstream provided a fix which is
included in the version currently in unstable. A debdiff is attached.
--
Jaldhar H. Vyas diff -Nru dovecot-2.2.13/debian/changelog dovecot-2.2.13/debian/changelog
--- dovecot-2.2.13/debian/changelog 2014-12-14 12:28:42.0 -0500
+++ dovecot-2.2.13/debian/changelog 2015-05-28 19:41:14.0 -0400
@@ -1,3 +1,13 @@
+dovecot (1:2.2.13-11~deb8u1) stable; urgency=high
+
+ * [7ecf912] Fix a mbox corruption problem by applying two patches from
+mercurial upstream.
+- fix-mbox-corruption-18534.patch (changeset 18534:94bd895721d8).
+- fix-mbox-corruption-18679.patch (changeset 18679:b6ea460e7cc4).
+Thanks to Santiago Vila (Closes: #776094)
+
+ -- Jaldhar H. Vyas Thu, 28 May 2015 19:37:40 -0400
+
dovecot (1:2.2.13-11) unstable; urgency=high
* [ebc0377] Don't allow install of dovecot-sieve without a new enough
diff -Nru dovecot-2.2.13/debian/patches/fix-mbox-corruption-18534.patch dovecot-2.2.13/debian/patches/fix-mbox-corruption-18534.patch
--- dovecot-2.2.13/debian/patches/fix-mbox-corruption-18534.patch 1969-12-31 19:00:00.0 -0500
+++ dovecot-2.2.13/debian/patches/fix-mbox-corruption-18534.patch 2015-05-28 19:41:14.0 -0400
@@ -0,0 +1,40 @@
+From: Timo Sirainen
+Subject: mbox: Fixed crash/corruption in some situations when the first mail was expunged.
+
+--- a/src/lib-storage/index/mbox/mbox-sync.c
b/src/lib-storage/index/mbox/mbox-sync.c
+@@ -630,7 +630,7 @@
+ static int mbox_sync_handle_header(struct mbox_sync_mail_context *mail_ctx)
+ {
+ struct mbox_sync_context *sync_ctx = mail_ctx->sync_ctx;
+- uoff_t orig_from_offset;
++ uoff_t orig_from_offset, postlf_from_offset = (uoff_t)-1;
+ off_t move_diff;
+ int ret;
+
+@@ -647,6 +647,7 @@
+ if (sync_ctx->first_mail_crlf_expunged)
+ mail_ctx->mail.from_offset++;
+ }
++ postlf_from_offset = mail_ctx->mail.from_offset;
+
+ /* read the From-line before rewriting overwrites it */
+ if (mbox_read_from_line(mail_ctx) < 0)
+@@ -700,10 +701,16 @@
+ /* create dummy message to describe the expunged data */
+ struct mbox_sync_mail mail;
+
++ /* if this is going to be the first mail, increase the
++ from_offset to point to the beginning of the
++ From-line, because the previous [CR]LF is already
++ covered by expunged_space. */
++ i_assert(postlf_from_offset != (uoff_t)-1);
++ mail_ctx->mail.from_offset = postlf_from_offset;
++
+ memset(&mail, 0, sizeof(mail));
+ mail.expunged = TRUE;
+ mail.offset = mail.from_offset =
+-(sync_ctx->dest_first_mail ? 1 : 0) +
+ mail_ctx->mail.from_offset -
+ sync_ctx->expunged_space;
+ mail.space = sync_ctx->expunged_space;
diff -Nru dovecot-2.2.13/debian/patches/fix-mbox-corruption-18679.patch dovecot-2.2.13/debian/patches/fix-mbox-corruption-18679.patch
--- dovecot-2.2.13/debian/patches/fix-mbox-corruption-18679.patch 1969-12-31 19:00:00.0 -0500
+++ dovecot-2.2.13/debian/patches/fix-mbox-corruption-18679.patch 2015-05-28 19:41:14.0 -0400
@@ -0,0 +1,18 @@
+From: Timo Sirainen
+Subject: mbox: Fixed corruption in some usage patterns.
+
+--- a/src/lib-storage/index/mbox/mbox-sync.c
b/src/lib-storage/index/mbox/mbox-sync.c
+@@ -679,8 +679,10 @@
+ }
+ } else if (mail_ctx->need_rewrite) {
+ mbox_sync_update_header(mail_ctx);
+- if (sync_ctx->delay_writes) {
+- /* mark it dirty and do it later */
++ if (sync_ctx->delay_writes && sync_ctx->need_space_seq == 0) {
++ /* mark it dirty and do it later. we can't do this
++ if we're in the middle of rewriting acquiring more
++ space. */
+ mail_ctx->dirty = TRUE;
+ return 0;
+ }
diff -Nru dovecot-2.2.13/debian/patches/series dovecot-2.2.13/debian/patches/series
--- dovecot-2.2.13/debian/patches/series 2014-12-14 12:28:42.0 -0500
+++ dovecot-2.2.13/debian/patches/series 2015-05-28 19:41:14.0 -0400
@@ -9,3 +9,5 @@
mboxlocking.patch
dovecot_name.patch
bye_logout_not_sent.patch
+fix-mbox-corruption-18534.patch
+fix-mbox-corruption-18679.patch
Bug#787182: ITP: zaqar -- OpenStack Queueing as a Service
Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: zaqar Version : 2015.1.0 Upstream Author : OpenStack Foundation * URL : https://github.com/openstack/zaqar * License : Apache-2.0 Programming Lang: Python Description : OpenStack Queueing as a Service Zaqar is a multi-tenant cloud messaging service for web developers. It combines the ideas pioneered by Amazon's SQS product with additional semantics to support event broadcasting. . The service features a fully RESTful API, which developers can use to send messages between various components of their SaaS and mobile applications, by using a variety of communication patterns. Underlying this API is an efficient messaging engine designed with scalability and security in mind. . Other OpenStack components can integrate with Zaqar to surface events to end users and to communicate with guest agents that run in the "over-cloud" layer. Cloud operators can leverage Zaqar to provide equivalents of SQS and SNS to their customers. . By installing python-zaqarclient you get programmatic access to the Zaqar v1.0 API library. Plus, it installs a plugin to python-openstackclient that allows you to perform simple queue operations. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680109: Advice on bug #680109 (proposal would break translations of the website footer)
2015-05-29 7:49 GMT+02:00 Paul Wise : > debian-www gets a lot of misplaced emails that should go elsewhere, to > debian-user or trademarks@ etc. The time spent responding to these > emails could be spent on fixing the website instead. I think we should > help people find the correct place for their inquiry up front, to > reduce the amount of time wasted by us and to reduce the amount of > time before they get their question answered. We should also help > people provide the needed information up-front so we don't have to > waste time asking for it. I agree with you: it's a waste of time for everyone. And the person who asks has to wait someone explains he sent his question/remark at the wrong list. > About the legalistic part, people often complain to Debian that we > made their emails public, I wonder if hiding the email in the html archives could lower the complain. I think it would be easy to transform the email field like: john-...@provider.tld -> john-doe AT provider DOT tld It will not block everyone to understand the right email address and the archive will not be found when searching the e-mail into a search engine. The RedHat archive does something equivalent. For example: https://www.redhat.com/archives/anaconda-devel-list/2015-May/msg6.html -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782896: wine32 recommends of wine ignores already installed foreign arch version
On 05/21/2015 08:34 PM, jre wrote: > [ wine-development is marked as multi-arch allowed since 1.7.41-2, which > should have fixed this bug. ] Ah, just saw that you changed to arch all instead of multi-arch allowed in 1.7.43-1. I already wondered why aptitude showed wine-development as arch all ;) > But as of now an update to wine-development 1.7.43-1 tries to pull > wine-development:i386 1.7.41-1. So I still end up with broken packages > in aptitude. > > In aptitude wine32-development (1.7.43-1) recommends only the > wine-development:i386 (1.7.41-1) package, but not the wine-development > 1.7.43-1 (all) package. > > I assume this is more a problem of the repository, and will solve itself > once 1.7.41-1 is removed. [1] I don't know if this will happen on its > own or needs manual intervention. Nope, now that 1.7.41-1 is gone, wine-development recommended by wine32-development is "Unavailable". See the new bug #787180 for the solution. Greets jre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#785069: jessie live-installer can't install grub when booted via usb drive without internet
Yes, run the installer after the live system is booted. Raphael Hertzog എഴുതി: > On Fri, 29 May 2015, Pirate Praveen wrote:>> On Friday 29 May 2015 02:46 PM, > Cyril Brulebois wrote:>>> It might be useful to provide a log so that we > understand what's >>> happening here.>> Just tested with "Graphical Install" from boot menu and >>> grub install is >> working. So we can mention it as a work around. I will now try live >> install again and provide logs.> What do you mean with "live install"? >> running the installer from > the graphical interface of the live system once started? > > If the bug is only reproducible there, then it's not necessarily a bug > in live-installer but in debian-installer-launcher... and in the way it > interacts with the current desktop. > > Cyril, don't count on me to look into this issue, I won't have the > time to handle this, sorry. > > Cheers,> -- > Raphaël Hertzog ◈ Debian Developer > > Support Debian LTS: http://www.freexian.com/services/debian-lts.html > Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743474: linphone: New upstream version available
Package: linphone Followup-For: Bug #743474 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Seems packaging of new upstream release has been prepared but is waiting for introduction of new bZRTP library (bug#785461). Please consider release the new upstream version now, with ZRTP support temporarily disabled: Then ftpmaster approval can be done in parallel for libbzrtp and linphone (which also will introduce changed packages), and we can sooner test if the range of bugs unrelated to ZRTP is tested. Regards, - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVaGoTAAoJECx8MUbBoAEhnjEQAJYRKy9vPiVq/cerUop/RIEL tKdi950DzSNPaSVvT4jSoIYqwOZJjjosNGU9mXt+AuET0An+5RcJFthcMqptFcvf DyORXrr1CBHrY/eiu4L3WGnfcID6L1KhkFIQjaAk2SyPKRn07BAfrfkmvQiZtt8r 61dMGXN+mVqwU9ZsltOawZHksl5daGrtvpnuEPv3YkiHYt9Av8x9MNrNnAz6XUhP q8x7y06LVYDK13GlyQphczQKecKgN5ukm4fDZOE3IOCJk3LHtgOoovmw3GEYmGmV 1cFrb0zTdYIoV+Ods6r3rzABUb7owlpwe5UyPsjNyg2Hi1NqLO/IUgnKmMFS4eXx OWl1wWcHuv/1AO+NopRsxRK8L5pLz4xS9ucAbIZGbn+Gv7WoA0Jk22OOCjESiOmM Kdu4sIFT8/s2mPMuMy1GjVuTdt7YLRp6sas+Koa6MzdxiQRhFek7gs9OSH5rkOaX 40g2ql+7h8INcJAXVOByfVzJtsY81FZxG4k4ABgEzX3MHXNcqjMFbztoCCemdlIx AnfZz5inLnmBK0+fED1OF1BQ+Gn4un79uDt0YWGHSwEgdHNhk2+osqb3VbuuXiQh mQBiJ27o0GUnEqIKgT+Re0CKKGCFzUN2GVQQu+M8vDJkzDuAhb+V3B50xayBZSsI q7lmmlVNQa8IBAFu+rCK =puNE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#688182: kFreeBSD support
Package: linphone Followup-For: Bug #688182 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It seems upstream now probes for and gracefully handles lack of V4L support, but the packaging forcefully avoids any video capabilities on non-Linux targets. Please try simply drop that discrimination in debian/rules and see if package still succeeds building on non-Linux targets. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVaG0iAAoJECx8MUbBoAEhgOAP/1O0ZQ4xhunvG3WO/vTBDm3N UXfllvUJlxUC0cvUPdT8u6JPXTcKveqf12SK8eQXweFL3OozAUF7rO9OWjNpQ1Ss AWBO0GRVGm5kFyTUtxTlZR10STqE64fUwzSynT4Ss2z0FifvnHTlF9za8s8Yw4Qc HNNhRSkgWafwTb3qqUhNbCPFE8HxiNr4JNFgX4jODwn1dH9QpBpKH7HdhyZDHE38 dBgxRl4Ooo0eIWuFB8ZB99FOUm9GX59Ze81CTvrRTeaDYtugrIJUPsubi/tijl5h pamFGvLiUVbGueaeO6Ch7MfjrQ93EFIpvU7l5CEYBds2plUByL0h6RZSK0/4lCzW DCfp8L0+BS2pxDIP063aDX2QYejfvofQ+8ncgdOWrJwVPmS9e+EOE/7ZysBGSeNw E5Z32NtHJd/f1on1P031WEso4/H8myFrOZE7Ai7gsvtSW5Us4+VLwUhabRtjH0NF FW2SvgMiPJvJDtBOi1JPewoeIZSmmJ/uxJatzsLiSK7aUxGAwexNXSHhvrsWb2G6 pI89GAOU8OOh+bojvAH1za0xrBS3shkp02/eF7JDg1EJgtPmLgHggbq1y78JdGFD sdiYTmBoEY3PPglCSMtbYCbvJ0pn+iU3+i5h0QzWowBE2Zq3gf8XtmxtqQD7J3/1 bKESpreFa5De9Yi9Emak =qS9y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782782: fix for CVE-2015-1819 in stretch/sid
Control: tags -1 patch
.debdiff for libxml2 2.9.2+dfsg1-3 (currently in unstable) attached...
light+love
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
diff -Nru libxml2-2.9.2+dfsg1/debian/changelog
libxml2-2.9.2+dfsg1/debian/changelog
--- libxml2-2.9.2+dfsg1/debian/changelog2015-02-01 05:37:42.0
+0100
+++ libxml2-2.9.2+dfsg1/debian/changelog2015-05-29 15:41:55.0
+0200
@@ -1,3 +1,13 @@
+libxml2 (2.9.2+dfsg1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches:
++ Add
0004-Enforce-the-reader-to-run-in-constant-memory-CVE-2015-1819.patch.
+ Fix CVE-2015-1819: Enforce the reader to run in constant memory.
+ (Closes: #782782).
+
+ -- Mike Gabriel Fri, 29 May 2015 15:40:53 +0200
+
libxml2 (2.9.2+dfsg1-3) unstable; urgency=medium
* Add icu related deps for -dev and -dbg packages
diff -Nru
libxml2-2.9.2+dfsg1/debian/patches/0004-Enforce-the-reader-to-run-in-constant-memory-CVE-2015-1819.patch
libxml2-2.9.2+dfsg1/debian/patches/0004-Enforce-the-reader-to-run-in-constant-memory-CVE-2015-1819.patch
---
libxml2-2.9.2+dfsg1/debian/patches/0004-Enforce-the-reader-to-run-in-constant-memory-CVE-2015-1819.patch
1970-01-01 01:00:00.0 +0100
+++
libxml2-2.9.2+dfsg1/debian/patches/0004-Enforce-the-reader-to-run-in-constant-memory-CVE-2015-1819.patch
2015-05-29 15:39:08.0 +0200
@@ -0,0 +1,166 @@
+From 213f1fe0d76d30eaed6e5853057defc43e6df2c9 Mon Sep 17 00:00:00 2001
+From: Daniel Veillard
+Date: Tue, 14 Apr 2015 17:41:48 +0800
+Subject: CVE-2015-1819 Enforce the reader to run in constant memory
+
+One of the operation on the reader could resolve entities
+leading to the classic expansion issue. Make sure the
+buffer used for xmlreader operation is bounded.
+Introduce a new allocation type for the buffers for this effect.
+
+v2: rebased against libxml2 2.9.2
+Mike Gabriel
+diff --git a/buf.c b/buf.c
+index 6efc7b6..07922ff 100644
+--- a/buf.c
b/buf.c
+@@ -299,7 +300,8 @@ xmlBufSetAllocationScheme(xmlBufPtr buf,
+ if ((scheme == XML_BUFFER_ALLOC_DOUBLEIT) ||
+ (scheme == XML_BUFFER_ALLOC_EXACT) ||
+ (scheme == XML_BUFFER_ALLOC_HYBRID) ||
+-(scheme == XML_BUFFER_ALLOC_IMMUTABLE)) {
++(scheme == XML_BUFFER_ALLOC_IMMUTABLE) ||
++ (scheme == XML_BUFFER_ALLOC_BOUNDED)) {
+ buf->alloc = scheme;
+ if (buf->buffer)
+ buf->buffer->alloc = scheme;
+@@ -458,6 +460,18 @@ xmlBufGrowInternal(xmlBufPtr buf, size_t len) {
+ size = buf->use + len + 100;
+ #endif
+
++if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++/*
++ * Used to provide parsing limits
++ */
++if ((buf->use + len >= XML_MAX_TEXT_LENGTH) ||
++ (buf->size >= XML_MAX_TEXT_LENGTH)) {
++ xmlBufMemoryError(buf, "buffer error: text too long\n");
++ return(0);
++ }
++ if (size >= XML_MAX_TEXT_LENGTH)
++ size = XML_MAX_TEXT_LENGTH;
++}
+ if ((buf->alloc == XML_BUFFER_ALLOC_IO) && (buf->contentIO != NULL)) {
+ size_t start_buf = buf->content - buf->contentIO;
+
+@@ -739,6 +753,15 @@ xmlBufResize(xmlBufPtr buf, size_t size)
+ CHECK_COMPAT(buf)
+
+ if (buf->alloc == XML_BUFFER_ALLOC_IMMUTABLE) return(0);
++if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++/*
++ * Used to provide parsing limits
++ */
++if (size >= XML_MAX_TEXT_LENGTH) {
++ xmlBufMemoryError(buf, "buffer error: text too long\n");
++ return(0);
++ }
++}
+
+ /* Don't resize if we don't have to */
+ if (size < buf->size)
+@@ -867,6 +890,15 @@ xmlBufAdd(xmlBufPtr buf, const xmlChar *str, int len) {
+
+ needSize = buf->use + len + 2;
+ if (needSize > buf->size){
++ if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++ /*
++ * Used to provide parsing limits
++ */
++ if (needSize >= XML_MAX_TEXT_LENGTH) {
++ xmlBufMemoryError(buf, "buffer error: text too long\n");
++ return(-1);
++ }
++ }
+ if (!xmlBufResize(buf, needSize)){
+ xmlBufMemoryError(buf, "growing buffer");
+ return XML_ERR_NO_MEMORY;
+@@ -938,6 +970,15 @@ xmlBufAddHead(xmlBufPtr buf, const xmlChar *str, int len)
{
+ }
+ needSize = buf->use + len + 2;
+ if (needSize > buf->size){
++ if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++ /*
++ * Used to provide parsing limits
++ */
++ if (needSize >= XML_MAX_TEXT_LENGTH) {
++ xmlBufMemoryError(buf, "buffer error: text too long\n");
++ return(-1);
++ }
++ }
+ if (!xmlBufResize(buf, needSize)){
+ xmlBufMemoryError(buf, "gr
Bug#782782: patch proposal for fixing CVE-2015-1819 in wheezy
Control: tags -1 patch
Hi,
under the umbrella of the LTS team, I worked out a patch for libxml2
in squeeze(-lts).
The patch is very similar to the patch required for wheezy.
Please note: it hasn't been tested much, yet, it is more a request for
feedback.
The patch has been derived from the content of the upstream commit
that fixes CVE-2015-1819.
Please test well before uploading to wheezy-pu.
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
diff -Nru libxml2-2.8.0+dfsg1/debian/changelog
libxml2-2.8.0+dfsg1/debian/changelog
--- libxml2-2.8.0+dfsg1/debian/changelog2015-04-07 16:22:41.0
+0200
+++ libxml2-2.8.0+dfsg1/debian/changelog2015-05-29 15:47:04.0
+0200
@@ -1,3 +1,12 @@
+libxml2 (2.8.0+dfsg1-7+wheezy4.1) wheezy-proposed-updates; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches:
++ Add cve-2015-1819.patch. Fix CVE-2015-1819: Enforce the reader to run in
+ constant memory. (Closes: #782782).
+
+ -- Mike Gabriel Fri, 29 May 2015 15:45:45 +0200
+
libxml2 (2.8.0+dfsg1-7+wheezy4) wheezy-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru libxml2-2.8.0+dfsg1/debian/patches/cve-2015-1819.patch
libxml2-2.8.0+dfsg1/debian/patches/cve-2015-1819.patch
--- libxml2-2.8.0+dfsg1/debian/patches/cve-2015-1819.patch 1970-01-01
01:00:00.0 +0100
+++ libxml2-2.8.0+dfsg1/debian/patches/cve-2015-1819.patch 2015-05-29
15:33:03.0 +0200
@@ -0,0 +1,139 @@
+From 213f1fe0d76d30eaed6e5853057defc43e6df2c9 Mon Sep 17 00:00:00 2001
+From: Daniel Veillard
+Date: Tue, 14 Apr 2015 17:41:48 +0800
+Subject: CVE-2015-1819 Enforce the reader to run in constant memory
+
+One of the operation on the reader could resolve entities
+leading to the classic expansion issue. Make sure the
+buffer used for xmlreader operation is bounded.
+Introduce a new allocation type for the buffers for this effect.
+
+v2: rebased against libxml2 (<< 2.9)
+Mike Gabriel
+--- a/include/libxml/tree.h
b/include/libxml/tree.h
+@@ -75,7 +75,8 @@
+ XML_BUFFER_ALLOC_EXACT, /* grow only to the minimal size */
+ XML_BUFFER_ALLOC_IMMUTABLE, /* immutable buffer */
+ XML_BUFFER_ALLOC_IO, /* special allocation scheme used for I/O */
+-XML_BUFFER_ALLOC_HYBRID /* exact up to a threshold, and doubleit
thereafter */
++XML_BUFFER_ALLOC_HYBRID, /* exact up to a threshold, and doubleit
thereafter */
++XML_BUFFER_ALLOC_BOUNDED /* limit the upper size of the buffer */
+ } xmlBufferAllocationScheme;
+
+ /**
+--- a/tree.c
b/tree.c
+@@ -683,7 +683,8 @@
+ xmlSetBufferAllocationScheme(xmlBufferAllocationScheme scheme) {
+ if ((scheme == XML_BUFFER_ALLOC_EXACT) ||
+ (scheme == XML_BUFFER_ALLOC_DOUBLEIT) ||
+-(scheme == XML_BUFFER_ALLOC_HYBRID))
++(scheme == XML_BUFFER_ALLOC_HYBRID) ||
++(scheme == XML_BUFFER_ALLOC_BOUNDED))
+ xmlBufferAllocScheme = scheme;
+ }
+
+@@ -7148,6 +7149,19 @@
+ size = buf->use + len + 100;
+ #endif
+
++if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++ /*
++ * Used to provide parsing limits
++ */
++ if ((buf->use + len >= XML_MAX_TEXT_LENGTH) ||
++ (buf->size >= XML_MAX_TEXT_LENGTH)) {
++ xmlTreeErrMemory("buffer error: text too long");
++ return(0);
++ }
++ if (size >= XML_MAX_TEXT_LENGTH)
++ size = XML_MAX_TEXT_LENGTH;
++}
++
+ if ((buf->alloc == XML_BUFFER_ALLOC_IO) && (buf->contentIO != NULL)) {
+ size_t start_buf = buf->content - buf->contentIO;
+
+@@ -7258,7 +7272,15 @@
+ return(0);
+
+ if (buf->alloc == XML_BUFFER_ALLOC_IMMUTABLE) return(0);
+-
++if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++ /*
++ * Used to provide parsing limits
++ */
++ if (size >= XML_MAX_TEXT_LENGTH) {
++ xmlTreeErrMemory("buffer error: text too long");
++ return(0);
++ }
++}
+ /* Don't resize if we don't have to */
+ if (size < buf->size)
+ return 1;
+@@ -7452,6 +7474,15 @@
+ }
+ needSize = buf->use + len + 2;
+ if (needSize > buf->size){
++ if (buf->alloc == XML_BUFFER_ALLOC_BOUNDED) {
++ /*
++ * Used to provide parsing limits
++ */
++ if (needSize >= XML_MAX_TEXT_LENGTH) {
++ xmlTreeErrMemory("buffer error: text too long");
++ return(-1);
++ }
++ }
+ if (!xmlBufferResize(buf, needSize)){
+ xmlTreeErrMemory("growing buffer");
+ return XML_ERR_NO_MEMORY;
+--- a/xmlreader.c
b/xmlreader.c
+@@ -2072,6 +2072,8 @@
+ "xmlNewTextReader : malloc failed\n");
+ return(NULL);
+ }
++/* no operation on a re
Bug#787183: linphone: please build-depend on libsrtp-dev
Package: linphone Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Linphone packaging currently (possibly only in unreleased HEAD) has commented out build-dependency on libsrtp-dev with a comment that a newer version is needed. That's true, but upstream autotools probing gracefully skips use of a too old library. Please build-depend on libsrtp-dev - even though currently unused: Then when libsrtp package is (soon, I expect) updated, enabling it in linphone requires only a binNMU. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVaG9LAAoJECx8MUbBoAEhmY4P/2RA2oXl6Ayl40ghNUoQi/Cc CXVjdEtLw9OdLI2n2g8MrK0lGGNloKm49DxIs8NWL+zrHBLoGV0hTQcSXrcxTw51 mtK1k/B+/rznFSAUHrPcmEGX8k6TK/YYmvaIGTGa8Yk2v0o67x1os7tKgS48MwKn /qzrH1U44aJnM94B7DkZNCDIICyV/1sjbnzU7Ls8RC4kpBFWyXze6QEo9PzIbLrJ qhsz3yog2wEENOaqfExRZOUoqjYN81axtFjQNv0CIzXThdYtfH4VlXS+aWpG1Sl1 0H/fy4koDuXEllEmKlXxpKHD5IL3pQSHrmyiL21tBvtSzPdCw3QbaiO5krYLtq3g vsFxJP4tMJugx2wGBTaIlaJjdeuSPla3uKHFRisZriR7GAtqc8Iexlz5KHMwPJd8 UJn/AvE8yzrQgrDi14Xg0V+jnU+my+3vo6Vb9xKn8tSpseUwD40iEalrtefDqMff zClDsaIh5yPYCgkJj3N0SJcFWKrog6wWBji3DMJp6nYOs0VZZtu75YORJ9OUNhZF ChKBGSUNxkprLV9zcroqqgqc/hmJnCOPaDm3Ji/mt+8gTKzJJJuseUOXwL0C9Bj1 CDhgLE1FdVhO0Z5FtDOyFz7vgoZpzyBr7RYKG25Vw3alrgJjh5noOL5H3wZvhHe9 ctVqie24ThbbOcse+9aF =Eg/T -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787184: ITP: haskell-js-jquery -- bundles the minified jQuery code into a Haskell package
Package: wnpp Severity: wishlist Owner: Iustin Pop * Package name: haskell-js-jquery Version : 1.11.3-1 Upstream Author : Neil Mitchell * URL : https://github.com/ndmitchell/js-jquery * License : BSD Programming Lang: Haskell Description : bundles the minified jQuery code into a Haskell package This package bundles the minified jQuery code into a Haskell package, so it can be depended upon by Cabal packages. The first three components of the version number match the upstream jQuery version. The haskell library is designed to meet the redistribution requirements of downstream users, and to reduce duplication of bundled code in Debian. Will be maintained as part of debian-haskell team. signature.asc Description: Digital signature
