Bug#765749:
I finally managed to get my folders back, restarted icedove, and they vanished again. This time a simpler fix did the trick. I changed the view | folders to unread then restarted icedove. When a new e-mail came in, the folder showed up. Then I reset it to all and they are visible again. I'm not sure if this is the same bug or just a related one. However, it's definitely a royal pain to have to keep playing around trying to restore the folders pane. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#765781: man-db: failed upgrade: trigger loop with install-info
Processing control commands: > reassign -1 dpkg Bug #765781 [man-db] man-db: failed upgrade: trigger loop with install-info Bug reassigned from package 'man-db' to 'dpkg'. No longer marked as found in versions man-db/2.7.0.2-2. Ignoring request to alter fixed versions of bug #765781 to the same values previously set > forcemerge 765434 -1 Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with install-info Severity set to 'serious' from 'normal' Added indication that 765781 affects cups Marked as found in versions dpkg/1.17.18. Added tag(s) sid and jessie. Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Merged 765434 765668 765734 765781 > affects 765434 + man-db install-info mime-support Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with install-info Added indication that 765434 affects man-db, install-info, and mime-support Added indication that 765668 affects man-db, install-info, and mime-support Added indication that 765734 affects man-db, install-info, and mime-support Added indication that 765781 affects man-db, install-info, and mime-support -- 765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434 765668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765668 765734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765734 765781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765785: openrc: can't cope with dangling rc.d links
Package: openrc Version: 0.13.1-1 Severity: grave Hi! I'm afraid that the new version of openrc fails to install if any purged package on the system left over its rc.d links. That's a bug in the package in question too, but an init system must not fail because of that. On my box, openrc first failed with: Setting up openrc (0.13.1-1) ... Add existing services ... * rc-update: killprocs already installed in runlevel `recovery'; skipping * rc-update: motd already installed in runlevel `recovery'; skipping * rc-update: bootlogs already installed in runlevel `recovery'; skipping * rc-update: single already installed in runlevel `recovery'; skipping * rc-update: binfmt-support already installed in runlevel `default'; skipping * rc-update: service `ceph' does not exist update-rc.d: error: rc-update rejected the script header dpkg: error processing package openrc (--configure): The package 'ceph' was purged a long time ago, yet the following danling links remained: /etc/rc1.d/K01ceph /etc/rc0.d/K01ceph /etc/rc3.d/S01ceph /etc/rc6.d/K01ceph /etc/rc5.d/S01ceph /etc/rc4.d/S01ceph /etc/rc2.d/S01ceph Removing these allowed openrc to process a bunch of other daemons, until it found the next package with this problem (in my case libvirt-bin). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.1-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openrc depends on: ii insserv1.14.0-5 ii libc6 2.19-11 ii libeinfo1 0.13.1-1 ii librc1 0.13.1-1 openrc recommends no packages. openrc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763681: not a regression
Control: severity -1 important As openrc has never been built on these architectures, technically the proper severity here is wishlist rather than serious, as the package "needs porting". For example, systemd does FTBFS on kfreebsd-* too. In this case, though, this rule feels more like a technicality rather than intention, I'm setting the severity to "important" instead. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: not a regression
Processing control commands: > severity -1 important Bug #763681 [openrc] openrc: FTBFS[armel,armhf,ppc64el] Severity set to 'important' from 'serious' -- 763681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#765734: dpkg: packages are shown to be partially installed, even though nothing seemed to got wrong
Processing control commands: > forcemerge 765434 -1 Bug #765434 [dpkg] man-db install-triggers broken Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Bug #765434 [dpkg] man-db install-triggers broken Marked as found in versions dpkg/1.17.18. Marked as found in versions dpkg/1.17.18. Bug #765734 [dpkg] dpkg: packages are shown to be partially installed, even though nothing seemed to got wrong Severity set to 'serious' from 'important' Added indication that 765734 affects cups Added tag(s) sid and jessie. Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Merged 765434 765668 765734 > retitle 765434 dpkg: bogus triggers cycle detection Bug #765434 [dpkg] man-db install-triggers broken Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Bug #765734 [dpkg] dpkg: packages are shown to be partially installed, even though nothing seemed to got wrong Changed Bug title to 'dpkg: bogus triggers cycle detection' from 'man-db install-triggers broken' Changed Bug title to 'dpkg: bogus triggers cycle detection' from 'cups: dpkg: cycle found while processing triggers:' Changed Bug title to 'dpkg: bogus triggers cycle detection' from 'dpkg: packages are shown to be partially installed, even though nothing seemed to got wrong' -- 765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434 765668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765668 765734: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 760804 in 2.3.1-1, notfixed 760804 in 2.3.3-1
Processing commands for cont...@bugs.debian.org: > found 760804 2.3.1-1 Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Bug #765671 [scons] serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected. Marked as found in versions scons/2.3.1-1. Marked as found in versions scons/2.3.1-1. Marked as found in versions scons/2.3.1-1. > notfixed 760804 2.3.3-1 Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Bug #765671 [scons] serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected. There is no source info for the package 'scons' at version '2.3.3-1' with architecture '' Unable to make a source version for version '2.3.3-1' No longer marked as fixed in versions scons/2.3.3-1. No longer marked as fixed in versions scons/2.3.3-1. No longer marked as fixed in versions scons/2.3.3-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804 761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565 765671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764885: php-htmlpurifier ready for tests (Security flaws in the current Debian version)
Hi Roland, [ Switching back in English for the benefit of other recipients, who are also welcome to provide feedback. ] On Thu, Oct 16, 2014 at 06:48:31PM -0400, David Prévot wrote: > As agreed with Roland, I’m taking the lead on this proposal. The updated > package should be ready by tomorrow, and I will coordinate with the > fusionforge maintainers (since gforge-common depends on > php-htmlpurifier) to get some testing before the actual upload. The package ready for test and upload is online: https://people.debian.org/~taffit/php-htmlpurifier_4.6.0-1_all.deb If you’d like to inspect the source and rebuild it, feel free to fetch it from its (new) VCS. I’ll replace the (old) one on collab-maint by a symlink after the upload: http://anonscm.debian.org/cgit/pkg-php/php-htmlpurifier.git/ The previous version of this package used to be installed outside of the PHP path, with symlinks to restore the usual expectations. This version does it the other way around (to keep backward compatibility, since e.g., moodle uses the files from /usr/share/php-htmlpurifier). I intend to drop those symlinks after Jessie gets released, so please, do update your package if you use /usr/share/php-htmlpurifier too. The directory to symlink and vice versa dance uses some recent features of dpkg-maintscript-helper(1), thus the Pre-Depends on dpkg (>= 1.17.5). If you expect to use this latest php-htmlpurifier on Wheezy or any other old system without such a recent dpkg version, I can implement the dance the old way (but since it’s a bit more error prone, I will only do so on request). I’ve also ditched the patch to disable the caching implementation, and instead provided a writable (to www-data) directory inside /var/lib by default. If you believe it’s a bad idea to introduce such change less than three weeks before the freeze, I can be more conservative and stage that change for Jessie+1. Thanks in advance for your feedback. If I don’t get negative feedback by Monday, I intend to upload the package as is (it will already be late: two weeks before the freeze). I would much prefer get feedback sooner, and upload this package as soon as you believe it’s OK. Regards David signature.asc Description: Digital signature
Processed: Re: Bug#765671: serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.
Processing control commands: > reassign -1 scons Bug #765671 [serf] serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected. Bug reassigned from package 'serf' to 'scons'. No longer marked as found in versions 1.3.7-1. Ignoring request to alter fixed versions of bug #765671 to the same values previously set > forcemerge 760804 -1 Bug #760804 [scons] serf: FTBFS: Directory /usr/include/mit-krb5 found where file expected. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Bug #765671 [scons] serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected. Set Bug forwarded-to-address to 'https://bitbucket.org/scons/scons/pull-request/184/support-isystem-in-parseflags/diff'. Owner recorded as Jörg Frings-Fürst . Added indication that 765671 affects serf,src:serf The source scons and version 2.3.3-1 do not appear to match any binary packages Marked as fixed in versions scons/2.3.3-1. Added tag(s) sid, jessie, and patch. Bug #761565 [scons] serf: FTBFS: TypeError: Directory /usr/include/mit-krb5 found where file expected Merged 760804 761565 765671 -- 760804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760804 761565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761565 765671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756777: Dirac FTBFS on armhf and blocks migration of arm64 fix.
Quoting peter green (2014-10-17 23:25:14) > peter green wrote: >> I've just tested and found that building with gcc/g++ 4.8 fixes the >> build. Gcc maintainer is pushing to drop gcc-4.8 for Jessie - see bug#765380. - 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#765671: serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.
Control: reassign -1 scons Control: forcemerge 760804 -1 On Fri, Oct 17, 2014 at 11:15:12AM +0200, Michael Tautschnig wrote: > During a rebuild of all Debian packages in a clean sid chroot (using > cowbuilder > and pbuilder) the build failed with the following error. > > [...] > dh_testdir > scons GSSAPI=/usr CFLAGS="-g -O2 -fstack-protector-strong -Wformat > -Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2" > LINKFLAGS="-Wl,-z,relro -Wl,-z,defs -Wl,--as-needed" > scons: Reading SConscript files ... > TypeError: Directory /usr/include/mit-krb5 found where file expected.: Known issue with scons not understanding gcc's -isystem flag. Jörg, have you heard from your sponsor on getting scons uploaded? You may also want to look at the feedback I left on mentors.debian.net. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765764: marked as done (Ganeti 2.12 does not create a required group gnt-wconfd)
Your message dated Fri, 17 Oct 2014 23:04:07 +
with message-id
and subject line Bug#765764: fixed in ganeti 2.12.0-3
has caused the Debian Bug report #765764,
regarding Ganeti 2.12 does not create a required group gnt-wconfd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
765764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Severity: grave
Package: ganeti-2.12
(Until I applied the workarounds Im documenting in both bug reports Ganeti
was unusable (jobs would not process/etc) which appears to qualify as
grave severity. However the workarounds are trivial to apply.)
If I am reading the error message correctly, Ganeti 2.12 does not create a
required group gnt-wconfd. This appears to be an upstream bug. I have
submitted it as https://code.google.com/p/ganeti/issues/detail?id=976
https://code.google.com/p/ganeti/issues/detail?id=952
https://code.google.com/p/ganeti/issues/detail?id=953
# On /all/ nodes
#
# NOTE: Upstream does not yet have changes in the makefile.am
# to create the users-setup with any gnt-wconfd / gnt-metad u/g
# I have /guessed/ at some values that seem to make sense and work for me.
#
addgroup --system gnt-wconfd
addgroup --system gnt-metad
adduser --system --no-create-home --ingroup gnt-wconfd --ingroup gnt-masterd
--ingroup gnt-metad gnt-wconfd
adduser --system --no-create-home --ingroup gnt-metad gnt-metad
# Then on the master node:
gnt-cluster upgrade --to 2.12
# You may also need to restart the ganeti daemons on all nodes one
additional time.
--
gnt-cluster upgrade --to 2.12
_TestLoadingConfigFile()
File "/usr/lib/ganeti/tools/cfgupgrade", line 678, in
_TestLoadingConfigFile
vrfy = cfg.VerifyConfig()
File "/usr/share/ganeti/2.12/ganeti/config.py", line 115, in sync_function
with args[0].GetConfigManager(shared):
File "/usr/share/ganeti/2.12/ganeti/config.py", line 243, in __enter__
self._config_writer._OpenConfig(self._shared) # pylint: disable=W0212
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2797, in _OpenConfig
self._UpgradeConfig(saveafter=True)
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2878, in
_UpgradeConfig
self._WriteConfig()
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2900, in _WriteConfig
getents = self._getents()
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 221, in GetEnts
_priv = resolver() # pylint: disable=W0621
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 114, in __init__
self.wconfd_gid = GetGid(constants.WCONFD_GROUP, _getgrnam)
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 81, in GetGid
raise errors.ConfigurationError("Group '%s' not found (%s)" % (group,
err))
ganeti.errors.ConfigurationError: Group 'gnt-wconfd' not found ('getgrnam():
name not found: gnt-wconfd')
root@h-2:~# /usr/lib/ganeti/tools/users-setup
This will do the following changes
+ Will add group gnt-admin
+ Will add group gnt-confd
+ Will add group gnt-daemons
+ Will add group gnt-luxid
+ Will add group gnt-masterd
+ Will add group gnt-rapi
+ Will add user gnt-confd with primary group gnt-confd
+ Will add user gnt-masterd with primary group gnt-confd
+ Will add user gnt-masterd with primary group gnt-luxid
+ Will add user gnt-masterd with primary group gnt-masterd
+ Will add user gnt-rapi with primary group gnt-rapi
+ Will add user gnt-confd to group gnt-daemons
+ Will add user gnt-masterd to group gnt-admin
+ Will add user gnt-masterd to group gnt-confd
+ Will add user gnt-masterd to group gnt-daemons
+ Will add user gnt-masterd to group gnt-masterd
+ Will add user gnt-rapi to group gnt-admin
+ Will add user gnt-rapi to group gnt-daemons
OK? (y/n)
y
addgroup: The group `gnt-admin' already exists as a system group. Exiting.
addgroup: The group `gnt-confd' already exists as a system group. Exiting.
addgroup: The group `gnt-daemons' already exists as a system group. Exiting.
addgroup: The group `gnt-luxid' already exists as a system group. Exiting.
addgroup: The group `gnt-masterd' already exists as a system group. Exiting.
addgroup: The group `gnt-rapi' already exists as a system group. Exiting.
The system user `gnt-confd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-rapi' already exists. Exiting.
The user `gnt-confd' is already a member of `gnt-daemons'.
The user `gnt-masterd' is already a member of `gnt-admin'.
The user `
Bug#759932: marked as done (bitlbee: FTBFS: /bin/sh: 1: cannot create init/bitlbee.service: Directory nonexistent)
Your message dated Fri, 17 Oct 2014 23:28:20 +0100 with message-id <54419804.9010...@gaast.net> and subject line Fixed has caused the Debian Bug report #759932, regarding bitlbee: FTBFS: /bin/sh: 1: cannot create init/bitlbee.service: Directory nonexistent to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bitlbee Version: 3.2.1+otr4-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/«BUILDDIR»/bitlbee-3.2.1+otr4/debian/build-native/doc' > # Only build the docs if this is a bzr checkout > test ! -d ../.bzr || /usr/bin/make -C user-guide > make[2]: Leaving directory > '/«BUILDDIR»/bitlbee-3.2.1+otr4/debian/build-native/doc' > sed 's|@sbindir@|/usr/sbin/|' init/bitlbee.service.in > init/bitlbee.service > /bin/sh: 1: cannot create init/bitlbee.service: Directory nonexistent > make[1]: *** [systemd] Error 2 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/bitlbee_3.2.1+otr4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. The build was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. --- End Message --- --- Begin Message --- Closing two bugs that have been fixed in recent releases. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+--- End Message ---
Bug#760053: marked as done (bitlbee: FTBFS - cannot create init/bitlbee.service: Directory nonexistent)
Your message dated Fri, 17 Oct 2014 23:28:20 +0100 with message-id <54419804.9010...@gaast.net> and subject line Fixed has caused the Debian Bug report #759932, regarding bitlbee: FTBFS - cannot create init/bitlbee.service: Directory nonexistent to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 759932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bitlbee Version: 3.2.1+otr4-1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] /usr/bin/make -C doc make[2]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-bitlbee/bitlbee-3.2.1+otr4/debian/build-native/doc' # Only build the docs if this is a bzr checkout test ! -d ../.bzr || /usr/bin/make -C user-guide make[2]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-bitlbee/bitlbee-3.2.1+otr4/debian/build-native/doc' sed 's|@sbindir@|/usr/sbin/|' init/bitlbee.service.in > init/bitlbee.service /bin/sh: 1: cannot create init/bitlbee.service: Directory nonexistent Makefile:141: recipe for target 'systemd' failed make[1]: *** [systemd] Error 2 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael bitlbee-build-log.txt.gz Description: application/gunzip pgpUeCuru3ZU6.pgp Description: PGP signature --- End Message --- --- Begin Message --- Closing two bugs that have been fixed in recent releases. -- + .''`. - -- ---+ +- -- --- - --+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---+ +-- - --- -- -+--- End Message ---
Bug#765771: gdm3: Xorg.N.log is gone
Package: gdm3 Version: 3.13.92-1 Severity: serious Justification: makes X maintainer's life miserable X-Debbugs-Cc: debia...@lists.debian.org Hi, it looks like gdm nowadays starts Xorg with -logfile /dev/null, and the log can only be found in the journal, which is root only. As the X packages' bug script heavily relies on getting the user's X log, that is not going to work out for us. Please bring the X log back for jessie and work with us during the next cycle to find an acceptable non-root-only way to get at the X log. Thanks, Julien signature.asc Description: Digital signature
Bug#764176: [Pkg-osm-maint] Bug#764176: josm-plugins update to fix RC bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/09/2014 08:25 PM, Ross Gammon wrote: > I have managed to successfully download and import the latest > josm-plugin tarball (svn30708). > > After adjusting all the dependencies to suit the latest version of > josm, I failed to get it building. > > One of the patches did not apply cleanly. It turns out that the > part of build-common.xml which was being > removed in the previous patch, has now been split into 3 > (revision-svn, revision-svn2git & revision-git). I hoped that > deleting all 3 in the same way would do the job - but no. > > My knowledge of ant and it's build system is zero, so it will take > me some time to investigate further. Maybe someone else would see > the answer faster! I'm also not an ant expert, but I managed to update josm-plugins to the latest SVN snapshot (30728) and have it build with the current josm version in testing & unstable. > I would like to be able to "git push" what I have done so far, but > I do not have permissions for pkg-osm. My plan (if I succeeded) was > to ask if anyone had any objections switching this package to > pkg-grass. Because I'm also not a member of pkg-osm my changes are available in my person git repo: http://git.linuxminded.nl/?p=pkg-osm/josm-plugins > Should I create a new respository and stick it there anyway so > anyone able to help can jump in? I'm in favor of moving josm & josm-plugins to pkg-grass where it will benefit from more team maintenance. I think we should move josm & josm-plugins to pkg-grass if the other JOSM uploaders don't object. Kind Regards, Bas - -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUQZaQAAoJEGdQ8QrojUrx1twP/RNlz7c8AS3MoCPLellaz8Q9 h38I3u0p+KQ9P51Ve2npnTsscOED4UH3gIJyXpbVnFmFg+Qw61MODP8O3XemSjGQ QarLMsslKfEwwDK6XKo6Msf5rdjltWtt/ArBAuuDtSns/AyZ2PX6xRiX7Ugur4Vd 8MyoGdPrmaDifHuPwUjf3ZfqHnT0wuQ9xqU6cOKTNlsmcDtNKe8pnH7E3sKukCTz d8c+TLFJV6Pk4EoYy5DKWha6AumQRm69o8Z6eyfEcy7j/kcifxH9glRInaXDVUT2 BPy4f1N959/D0p5Hld13sB/3d82+Oc09qzi/ESDI1EF3E1HNSM1cKWSwjfeaQOVa xbiL2nl9ug4aq6UUqDEZzfO0ohCe0m14/K7I8Me3SGwjETwiymuI4kA7EQOx6AwY CXSJL75d8Cah4COr6o7BZmCH7DEm8vz+QFkht81E4HTKxoirfh4H/tENflStdOi+ S0Dzl437+ZLR6NFE9DhZV+b+fa2dJrFQRkxIgM675pX1/8tbr1Qbd9jVJUDwjrjO +T39iypfInulsGrghOJ/CLv+7aIajY3VpakmP8cUK0urpLPNCUGAYlVpJcEd5x5L hpNB51zDsRwHwJEfEzEnETrjEPqY7A94bnIREnR4Q9J1T5zdgzkzz5J4hi5cmxQ0 5qc52fUSV6teB8wHPJZO =IPJy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761538: marked as done (camping: FTBFS: rm: cannot remove 'debian/camping/usr/share/doc/camping/rdoc/js/jquery.js': No such file or directory)
Your message dated Fri, 17 Oct 2014 22:03:44 + with message-id and subject line Bug#761538: fixed in camping 2.1.580-1 has caused the Debian Bug report #761538, regarding camping: FTBFS: rm: cannot remove 'debian/camping/usr/share/doc/camping/rdoc/js/jquery.js': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: camping Version: 2.1.532-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140913 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/«PKGBUILDDIR»' > dh_installdocs -O--buildsystem=ruby > rm debian/camping/usr/share/doc/camping/rdoc/js/jquery.js > rm: cannot remove 'debian/camping/usr/share/doc/camping/rdoc/js/jquery.js': > No such file or directory > make[1]: *** [override_dh_installdocs] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/09/13/camping_2.1.532-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: camping Source-Version: 2.1.580-1 We believe that the bug you reported is fixed in the latest version of camping, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul van Tilburg (supplier of updated camping package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Oct 2014 23:06:17 +0200 Source: camping Binary: camping Architecture: source all Version: 2.1.580-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Paul van Tilburg Description: camping- small Ruby web framework for Model-View-Controller type applicati Closes: 761538 Changes: camping (2.1.580-1) unstable; urgency=medium . [ Tim Potter ] * d/rules: fix jquery.js link for clean and repeated builds (Closes: #761538) . [ Paul van Tilburg ] * New upstream (snapshot) release (with git HEAD 0904ad4) * d/docs, d/rules: although doc/ contains RDoc file, still generate our own docs following the Rakefile options * d/rules: reuse Late fonts from the fonts-lato package * d/control: - replace depend on ruby-activerecord-3.2 by ruby-activerecord; this snapshot release works with AR 2.3.x up until AR 4.1.6 - bump standards version to 3.9.6; no changes required - add depend on fonts-lato for the documentation Checksums-Sha1: 54309b7d80c3d2f9ca562a2ec30cea55f9cc1a06 1399 camping_2.1.580-1.dsc 2217a45c2deb0f45ea190acdac2ab02408ac9721 419476 camping_2.1.580.orig.tar.gz 596550e6b24a1ebc4b9c1065f16197fcc8a7168a 33668 camping_2.1.580-1.debian.tar.xz 09fccb23484549c387f8e6e9fb5d7a4d8ac3e1e7 152318 camping_2.1.580-1_all.deb Checksums-Sha256: 8fe690323aea48b488720b2bd5e26bc27634ee26111eed817c68b3f6f5d3966f 1399 camping_2.1.580-1.dsc 5b9453b61faaea3a9024ac793f8fbaa41986f796e1bf110401cf03108be90bab 419476 camping_2.1.580.orig.tar.gz 56a9a603d5512621c07e248579a84429c256d45c5b138d223e4d9b16cc4343c5 33668 camping_2.1.580-1.debian.tar.xz 484e47295b05917109f037e63bf308d024720e4b74c63432c94cbf72290fe161 152318 camping_2.1.580-1_all.deb Files: 910b14d33a36800b46478e327c701bf4 1399 web optional camping_2.1.580-1.dsc 06db026d24acb6f634671cc19d1f743f 419476 web optional camping_2.1.580.orig.tar.gz 5e05790b39a067087ad7e9a7098ed13b 33668 web optional camping_2.1.580-1.debian.tar.xz efe7d48aa00ee8463027a6dede8065ca 152318 web optional camping_2.1.580-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlRBj8IACgkQJBBhylAGQYHcsQCfcSLWSHzPxR
Processed: Modify #765764:
Processing commands for cont...@bugs.debian.org: > reassign 765764 ganeti 2.12.0-2 Bug #765764 [ganeti-2.12] Ganeti 2.12 does not create a required group gnt-wconfd Bug reassigned from package 'ganeti-2.12' to 'ganeti'. Ignoring request to alter found versions of bug #765764 to the same values previously set Ignoring request to alter fixed versions of bug #765764 to the same values previously set Bug #765764 [ganeti] Ganeti 2.12 does not create a required group gnt-wconfd Marked as found in versions ganeti/2.12.0-2. > tags 765764 pending Bug #765764 [ganeti] Ganeti 2.12 does not create a required group gnt-wconfd Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 765764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756777: marked as done (dirac: FTBFS on armhf)
Your message dated Fri, 17 Oct 2014 21:51:50 + with message-id and subject line Bug#756777: fixed in dirac 1.0.2-7.1 has caused the Debian Bug report #756777, regarding dirac: FTBFS on armhf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 756777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dirac Version: 1.0.2-7 Severity: serious Justification: fails to build from source (but built successfully in the past) dirac failed to build on armhf with | ## --- ## | ## test suite: dirac. ## | ## --- ## | | Running unit tests | | 1: unittests skipped (unittests.at:5) | | Checking encode and decode of colourbars | | 2: colourbars FAILED (colourbars.at:7) | | Checking encode and decode of sample data | | 3: samples skipped (samples.at:5) | | ## - ## | ## Test results. ## | ## - ## | | ERROR: 1 test was run, | 1 failed unexpectedly. | 2 tests were skipped. | ## -- ## | ## testsuite.log was created. ## | ## -- ## | | Please send `tests/testsuite.log' and all information you think might help: | |To: <> |Subject: [] testsuite: 2 failed | | You may investigate any problem if you feel able to do so, in which | case the test suite provides a good starting point. Its output may | be found below `tests/testsuite.dir'. | | make[3]: *** [check-local] Error 1 Full build log is available at https://buildd.debian.org/status/fetch.php?pkg=dirac&arch=armhf&ver=1.0.2-7&stamp=1406621057. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: dirac Source-Version: 1.0.2-7.1 We believe that the bug you reported is fixed in the latest version of dirac, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 756...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated dirac package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Oct 2014 20:04:24 + Source: dirac Binary: dirac libdirac-decoder0 libdirac-encoder0 libdirac-dev libdirac-doc Architecture: source amd64 all Version: 1.0.2-7.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Peter Michael Green Description: dirac - open and royalty free high quality video codec - commandline util libdirac-decoder0 - open and royalty free high quality video codec - decoder library libdirac-dev - open and royalty free high quality video codec - development file libdirac-doc - open and royalty free high quality video codec - library document libdirac-encoder0 - open and royalty free high quality video codec - encoder library Closes: 756777 Changes: dirac (1.0.2-7.1) unstable; urgency=medium . * Non-maintainer upload. * Use gcc/g++ 4.8 on armhf to avoid segfault in test. (Closes: 756777) * Use -fstack-protector instead of -fstack-protector-strong on armhf as gcc-4.8 doesn't support the later. (note: due to the aforementioned segfault dirac was never built with the strong stack protector on armhf so this is not a regression) Checksums-Sha1: 705a6be9d66a77dbdf61a262ae4fee2d6edf1c84 2253 dirac_1.0.2-7.1.dsc da77c6565f91668b8ce97049eca48247611441c5 155508 dirac_1.0.2-7.1.debian.tar.xz 44001335b517faab9ec2c026f222ee5052bd1536 404606 dirac_1.0.2-7.1_amd64.deb dbd4e4ffc14894e513fc37b990d5e79f778f5723 275850 libdirac-decoder0_1.0.2-7.1_amd64.deb 62c86aa30cb50e49fddcec2d7d9a2dac8853fa8f 335848 libdirac-encoder0_1.0.2-7.1_amd64.deb 0c60edc57213c382e20885749ea83d75d3afc04e 146824 libdirac-dev_1.0.2-7.1_amd64.deb e8739aab535987d478aa2b937eef0a52f132ab17 13034664 libdirac-doc_1.0.2-7.1_all.deb Checksums-Sha256: 25c07fb5309509184fba1e2b1c6893a9891a29f377263fe89b29ebd3687aceeb 2253 dirac_1.0.2-7.1.dsc 307d0bcf19fe7248f0fcda1cc14176e8a0a6c588bac0bfff8860b06646dcb63b 155508 dir
Bug#756777: Dirac FTBFS on armhf and blocks migration of arm64 fix.
peter green wrote: Found 756777 1.0.2-6 Thanks I've just tested and found that building with gcc/g++ 4.8 fixes the build. Using 4.8 also requires switching from strong to regular stack protector. This can be done with the following export CC=gcc-4.8 export CXX=g++-4.8 export DEB_CFLAGS_MAINT_STRIP=-fstack-protector-strong export DEB_CFLAGS_MAINT_APPEND=-fstack-protector export DEB_CXXFLAGS_MAINT_STRIP=-fstack-protector-strong export DEB_CXXFLAGS_MAINT_APPEND=-fstack-protector If noone proposes a better soloution in the next couple of days I'll wrap this in appropriate conditional logic and upload it as a NMU. I have just uploaded a NMU with the attatched debdiff. diff -Nru dirac-1.0.2/debian/changelog dirac-1.0.2/debian/changelog --- dirac-1.0.2/debian/changelog2014-07-29 07:14:50.0 + +++ dirac-1.0.2/debian/changelog2014-10-17 20:49:36.0 + @@ -1,3 +1,14 @@ +dirac (1.0.2-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * Use gcc/g++ 4.8 on armhf to avoid segfault in test. (Closes: 756777) + * Use -fstack-protector instead of -fstack-protector-strong on armhf as +gcc-4.8 doesn't support the later. (note: due to the aforementioned +segfault dirac was never built with the strong stack protector on armhf +so this is not a regression) + + -- Peter Michael Green Fri, 17 Oct 2014 20:04:24 + + dirac (1.0.2-7) unstable; urgency=medium * Team upload. diff -Nru dirac-1.0.2/debian/control dirac-1.0.2/debian/control --- dirac-1.0.2/debian/control 2014-07-29 07:14:13.0 + +++ dirac-1.0.2/debian/control 2014-10-17 20:08:20.0 + @@ -7,7 +7,8 @@ Build-Depends: autoconf, debhelper (>= 9~), - dh-autoreconf + dh-autoreconf, + gcc-4.8 [armhf], g++-4.8 [armhf] Build-Depends-Indep: doxygen-latex, graphviz diff -Nru dirac-1.0.2/debian/rules dirac-1.0.2/debian/rules --- dirac-1.0.2/debian/rules2014-07-29 07:11:08.0 + +++ dirac-1.0.2/debian/rules2014-10-17 20:02:19.0 + @@ -1,5 +1,16 @@ #!/usr/bin/make -f +DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) +ifeq ($(DEB_HOST_ARCH),armhf) +export CC=gcc-4.8 +export CXX=g++-4.8 +export DEB_CFLAGS_MAINT_STRIP=-fstack-protector-strong +export DEB_CFLAGS_MAINT_APPEND=-fstack-protector +export DEB_CXXFLAGS_MAINT_STRIP=-fstack-protector-strong +export DEB_CXXFLAGS_MAINT_APPEND=-fstack-protector +endif + + %: dh $@ --parallel --with autoreconf
Bug#765004: marked as done (libmojolicious-plugin-mailexception-perl: FTBFS with Mojolicous 5)
Your message dated Fri, 17 Oct 2014 21:22:26 + with message-id and subject line Bug#765004: fixed in libmojolicious-plugin-mailexception-perl 0.19-1 has caused the Debian Bug report #765004, regarding libmojolicious-plugin-mailexception-perl: FTBFS with Mojolicous 5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmojolicious-plugin-mailexception-perl Version: 0.18-1 Severity: serious Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libmojolicious-plugin-mailexception-perl doesn't build anymore: dh_auto_test make[1]: Entering directory '/tmp/buildd/libmojolicious-plugin-mailexception-perl-0.18' PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t Can't locate object method "secret" via package "MpemTest" at /usr/share/perl5/Mojo/Server.pm line 17. # Looks like you planned 33 tests but ran 5. # Looks like your test exited with 255 just after 5. t/010-tplugun.t .. 1..33 ok 1 - use Test::Mojo; ok 2 - require Mojolicious; ok 3 - require MIME::Lite; ok 4 - require MIME::Words; ok 5 - require Mojolicious::Plugin::MailException; Dubious, test returned 255 (wstat 65280, 0xff00) Failed 28/33 subtests Test Summary Report - --- t/010-tplugun.t (Wstat: 65280 Tests: 5 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 33 tests but ran 5. Files=1, Tests=5, 0 wallclock secs ( 0.04 usr 0.00 sys + 0.26 cusr 0.01 csys = 0.31 CPU) Result: FAIL Failed 1/1 test programs. 0/5 subtests failed. Makefile:828: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory '/tmp/buildd/libmojolicious-plugin-mailexception-perl-0.18' dh_auto_test: make -j1 test returned exit code 2 debian/rules:23: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Upstream activity: https://github.com/dr-co/libmojolicious-plugin-mail_exception/pull/9 Cheers, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUOvK4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGV48P/Ra92NP4rdVXPKqHVC/xGUee I1ty2IHwarEc7SXfNzyWe4asf+q1DWiruJEkWQgDppjuDZWi0XQjBwo2epwPAPsL nHKnIThBQx5OZwcf1J4SRKEgNKVlughc/gENeUQLxNt5Smpb7bhX6tugIghmyQ6v VtHVDacc/p0anSo+Aq8zAmZd/yBb5JeoqOiWU57wxuC0hA6kqWgePiZ1ZBAD5J3l buyNVKIVeCUGKdD4TAe8MLvJslxisFH3C7oDPWEAsFNH7lj0COfXAGc7WVp0mLWF fyR4pRbiSZ8Di3ejGOrksyj5X/kZBeOX7WTE8ZDmWhAc8N6zPKZNE9xlH5EUocVR iFC/09X5C0lVTTUgvnQymcbutWnIiDIRCaauc4tNKiit6fTQUeEfsyyPoGxbIgKs rnQHRE6XeZSZa0P8GzGrENsl296WDqjVK//e5hhgnZaEn7Wqum4x2VStgwKEGADG UvLsBpZ3DItHXe1pYwZ440mB0f2quXu6q2y95hykefZ5w5HbFt/rcg1k3obVSnS1 YlRm79QsnLogfBQiDC/RhMbKo3V3YWZq/lPr1+dvKSLmgNWJ/My4rmvCwBzOmxOy Vrm5gHX/ifQpLs1/xdLA/owcZyz9WFppH+jMvb9T71kL9Q9wR+vpTZLSzcXG+T+M Kg68sq0swE+mi4FrXOf6 =tZ1d -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libmojolicious-plugin-mailexception-perl Source-Version: 0.19-1 We believe that the bug you reported is fixed in the latest version of libmojolicious-plugin-mailexception-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry E. Oboukhov (supplier of updated libmojolicious-plugin-mailexception-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Oct 2014 23:44:06 +0400 Source: libmojolicious-plugin-mailexception-perl Binary: libmojolicious-plugin-mailexception-perl Architecture: source all Version: 0.19-1 Distribution: unstable Urgency: medium Maintainer: Dmitry E. Oboukhov Changed-By: Dmitry E. Oboukhov Description: libmojolicious-plugin-mailexception-perl - Mojolicious plugin to send crash information by email Closes: 76500
Bug#765050: marked as done (libmojolicious-plugin-mailexception-perl: FTBFS - Can't locate object method "secret" via package "MpemTest")
Your message dated Fri, 17 Oct 2014 21:22:26 + with message-id and subject line Bug#765004: fixed in libmojolicious-plugin-mailexception-perl 0.19-1 has caused the Debian Bug report #765004, regarding libmojolicious-plugin-mailexception-perl: FTBFS - Can't locate object method "secret" via package "MpemTest" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmojolicious-plugin-mailexception-perl Version: 0.18-1 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] dh_auto_test make[1]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-libmojolicious-plugin-mailexception-perl/libmojolicious-plugin-mailexception-perl-0.18' PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t Can't locate object method "secret" via package "MpemTest" at /usr/share/perl5/Mojo/Server.pm line 17. # Looks like you planned 33 tests but ran 5. # Looks like your test exited with 255 just after 5. t/010-tplugun.t .. 1..33 ok 1 - use Test::Mojo; ok 2 - require Mojolicious; ok 3 - require MIME::Lite; ok 4 - require MIME::Words; ok 5 - require Mojolicious::Plugin::MailException; Dubious, test returned 255 (wstat 65280, 0xff00) Failed 28/33 subtests Test Summary Report --- t/010-tplugun.t (Wstat: 65280 Tests: 5 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 33 tests but ran 5. Files=1, Tests=5, 0 wallclock secs ( 0.02 usr 0.01 sys + 0.33 cusr 0.02 csys = 0.38 CPU) Result: FAIL Failed 1/1 test programs. 0/5 subtests failed. Makefile:828: recipe for target 'test_dynamic' failed make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-libmojolicious-plugin-mailexception-perl/libmojolicious-plugin-mailexception-perl-0.18' dh_auto_test: make -j1 test returned exit code 2 debian/rules:23: recipe for target 'build' failed make: *** [build] Error 2 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael libmojolicious-plugin-mailexception-perl-build-log.txt.gz Description: application/gunzip pgpiwRPC1sQeA.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: libmojolicious-plugin-mailexception-perl Source-Version: 0.19-1 We believe that the bug you reported is fixed in the latest version of libmojolicious-plugin-mailexception-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry E. Oboukhov (supplier of updated libmojolicious-plugin-mailexception-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Oct 2014 23:44:06 +0400 Source: libmojolicious-plugin-mailexception-perl Binary: libmojolicious-plugin-mailexception-perl Architecture: source all Version: 0.19-1 Distribution: unstable Urgency: medium Maintainer: Dmitry E. Oboukhov Changed-By: Dmitry E. Oboukhov Description: libmojolicious-plugin-mailexception-perl - Mojolicious plugin to send crash information by email Closes: 765004 Changes: libmojolicious-plugin-mailexception-perl (0.19-1) unstable; urgency=medium . * Some fixes for Mojo v.5, closes: #765004 thanks to Stephan Jauernick . Checksums-Sha1: 3c3617131e596338be25ba4921bd3d0d055bfc12 2134 libmojolicious-plugin-mailexception-perl_0.19-1.dsc aba6e122355c7bb1eea2fe571a0ccf75f431033f 4977 libmojolicious-plugin-mailexception-perl_0.19.orig.tar.gz a9efc6a77edc03a05d0f28a5079378680b4011d6 2556 libmojolicious-plugin-mailexception-perl_0.19-1.debian.tar.xz 1a91548bb32b7aeaa28dea7f6dd965d39c3d0820 8528 libmojolicious-plugin-mailexception-perl_0.19-1_all.deb Checksums-Sha256: 1d4c9d0294222ca3f62832d20c76bf859945bb1e2ad78c3b857ec3d7b60
Bug#765765: deluge: Deluge clients cannot connect to deluged because of SSL error
Package: deluge
Version: 1.3.10-1
Severity: grave
Justification: renders package unusable
In the deluge 1.3.10-1 package, deluged will start without problems. However,
the GTK+ client and the console client cannot connect (the GTK+ client cannot
even see that a daemon is running).
Running deluged with arguments to provide verbose output (deluged -d -L info)
reveals an SSL handshake error every time a client tries to connect to it:
[INFO] 00:00:51 rpcserver:203 Deluge Client connection made from:
127.0.0.1:39105
[INFO] 00:00:51 rpcserver:223 Deluge client disconnected: [('SSL routines',
'SSL3_READ_BYTES', 'ssl handshake failure')]
[INFO] 00:00:53 rpcserver:203 Deluge Client connection made from:
127.0.0.1:39106
[INFO] 00:00:53 rpcserver:223 Deluge client disconnected: [('SSL routines',
'SSL3_READ_BYTES', 'ssl handshake failure')]
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756104: binary removal mrpt
Hi Jose, In order to get them removed you have to open a bug against ftp.debian.org Feel free to copy the significant bit from this bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764859 cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756784: marked as done (visp: FTBFS on powerpc)
Your message dated Fri, 17 Oct 2014 22:02:42 +0100 with message-id <1413579762.32507.yahoomail...@web171804.mail.ir2.yahoo.com> and subject line has caused the Debian Bug report #756784, regarding visp: FTBFS on powerpc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 756784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: visp Version: 2.9.0-3 Severity: serious Justification: fails to build from source viisp failed to build on powerpc with: | Start 90: videoReader | 90/135 Test #90: videoReader ...***Exception: SegFault 0.34 sec ... | 99% tests passed, 1 tests failed out of 135 | | Total Test time (real) = 137.03 sec | | The following tests FAILED: |90 - videoReader (SEGFAULT) | Errors while running CTest | make[2]: *** [test] Error 8 | Makefile:116: recipe for target 'test' failed The full log is available at https://buildd.debian.org/status/fetch.php?pkg=visp&arch=powerpc&ver=2.9.0-3&stamp=1405961889. Please take a look. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Hi, Both -3 and -3+b1 (against new libjpeg62) have succeeded for powerpc. I'm closing then this one. Feel free to reopen if you find again the same failure. Cheers, G. --- End Message ---
Bug#765764: Ganeti 2.12 does not create a required group gnt-wconfd
Severity: grave
Package: ganeti-2.12
(Until I applied the workarounds Im documenting in both bug reports Ganeti
was unusable (jobs would not process/etc) which appears to qualify as
grave severity. However the workarounds are trivial to apply.)
If I am reading the error message correctly, Ganeti 2.12 does not create a
required group gnt-wconfd. This appears to be an upstream bug. I have
submitted it as https://code.google.com/p/ganeti/issues/detail?id=976
https://code.google.com/p/ganeti/issues/detail?id=952
https://code.google.com/p/ganeti/issues/detail?id=953
# On /all/ nodes
#
# NOTE: Upstream does not yet have changes in the makefile.am
# to create the users-setup with any gnt-wconfd / gnt-metad u/g
# I have /guessed/ at some values that seem to make sense and work for me.
#
addgroup --system gnt-wconfd
addgroup --system gnt-metad
adduser --system --no-create-home --ingroup gnt-wconfd --ingroup gnt-masterd
--ingroup gnt-metad gnt-wconfd
adduser --system --no-create-home --ingroup gnt-metad gnt-metad
# Then on the master node:
gnt-cluster upgrade --to 2.12
# You may also need to restart the ganeti daemons on all nodes one
additional time.
--
gnt-cluster upgrade --to 2.12
_TestLoadingConfigFile()
File "/usr/lib/ganeti/tools/cfgupgrade", line 678, in
_TestLoadingConfigFile
vrfy = cfg.VerifyConfig()
File "/usr/share/ganeti/2.12/ganeti/config.py", line 115, in sync_function
with args[0].GetConfigManager(shared):
File "/usr/share/ganeti/2.12/ganeti/config.py", line 243, in __enter__
self._config_writer._OpenConfig(self._shared) # pylint: disable=W0212
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2797, in _OpenConfig
self._UpgradeConfig(saveafter=True)
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2878, in
_UpgradeConfig
self._WriteConfig()
File "/usr/share/ganeti/2.12/ganeti/config.py", line 2900, in _WriteConfig
getents = self._getents()
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 221, in GetEnts
_priv = resolver() # pylint: disable=W0621
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 114, in __init__
self.wconfd_gid = GetGid(constants.WCONFD_GROUP, _getgrnam)
File "/usr/share/ganeti/2.12/ganeti/runtime.py", line 81, in GetGid
raise errors.ConfigurationError("Group '%s' not found (%s)" % (group,
err))
ganeti.errors.ConfigurationError: Group 'gnt-wconfd' not found ('getgrnam():
name not found: gnt-wconfd')
root@h-2:~# /usr/lib/ganeti/tools/users-setup
This will do the following changes
+ Will add group gnt-admin
+ Will add group gnt-confd
+ Will add group gnt-daemons
+ Will add group gnt-luxid
+ Will add group gnt-masterd
+ Will add group gnt-rapi
+ Will add user gnt-confd with primary group gnt-confd
+ Will add user gnt-masterd with primary group gnt-confd
+ Will add user gnt-masterd with primary group gnt-luxid
+ Will add user gnt-masterd with primary group gnt-masterd
+ Will add user gnt-rapi with primary group gnt-rapi
+ Will add user gnt-confd to group gnt-daemons
+ Will add user gnt-masterd to group gnt-admin
+ Will add user gnt-masterd to group gnt-confd
+ Will add user gnt-masterd to group gnt-daemons
+ Will add user gnt-masterd to group gnt-masterd
+ Will add user gnt-rapi to group gnt-admin
+ Will add user gnt-rapi to group gnt-daemons
OK? (y/n)
y
addgroup: The group `gnt-admin' already exists as a system group. Exiting.
addgroup: The group `gnt-confd' already exists as a system group. Exiting.
addgroup: The group `gnt-daemons' already exists as a system group. Exiting.
addgroup: The group `gnt-luxid' already exists as a system group. Exiting.
addgroup: The group `gnt-masterd' already exists as a system group. Exiting.
addgroup: The group `gnt-rapi' already exists as a system group. Exiting.
The system user `gnt-confd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-masterd' already exists. Exiting.
The system user `gnt-rapi' already exists. Exiting.
The user `gnt-confd' is already a member of `gnt-daemons'.
The user `gnt-masterd' is already a member of `gnt-admin'.
The user `gnt-masterd' is already a member of `gnt-confd'.
The user `gnt-masterd' is already a member of `gnt-daemons'.
The user `gnt-masterd' is already a member of `gnt-masterd'.
The user `gnt-rapi' is already a member of `gnt-admin'.
The user `gnt-rapi' is already a member of `gnt-daemons'.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: limit source to php-htmlpurifier, tagging 764885
Processing commands for cont...@bugs.debian.org: > limit source php-htmlpurifier Limiting to bugs with field 'source' containing at least one of 'php-htmlpurifier' Limit currently set to 'source':'php-htmlpurifier' > tags 764885 + pending Bug #764885 [php-htmlpurifier] Security flaws in the current Debian version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 764885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765749: icedove: empty folder pane
Package: icedove Version: 31.1.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I restarted my computer and launched icedove. The folder pane was present but empty while the messages pane just showed one e-mail with a non-working read e-mail button. * What exactly did you do (or not do) that was effective (or ineffective)? Searched the Internet for similar problems. Tried removing session.json and folders.json. Tried a few add-ons that were supposed to be able to help. Purged Icedove and reinstalled. Installed the version from Sid. Tried starting from Konsole. Got this message: (process:23945): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Tried starting from Konsole using icedove -jsconsole and got this message in the error console: Timestamp: 17/10/14 03:02:07 PM Warning: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create Source File: resource://gre/components/steelApplication.js Line: 783 Searched for Application.js. Closest I could find was in /usr/local/sushi. Tried reinstalling sushi and found that it wasn't installed. Installed it. After that had no impact, I purged sushi. * What was the outcome of this action? The problem still exists. * What outcome did you expect instead? I want a way to be able to access my e-mail. Right now Icedove is useless. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/6 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.4 ii fontconfig2.11.0-6.1 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii libdbus-1-3 1.8.8-2 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-1.1 ii libffi6 3.1-2 ii libfontconfig12.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-16 ii libgdk-pixbuf2.0-02.30.8-1+b1 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.24-1 ii libhunspell-1.3-0 1.3.3-2 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.1-1 ii libpango-1.0-01.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-0 1.36.8-2 ii libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.6-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.1-16 ii libvpx1 1.3.0-2.1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxrender1 1:0.9.8-1 ii libxt61:1.1.4-1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2 Versions of packages icedove recommends: ii myspell-en-us [myspell-dictionary] 1:3.3.0-4 Versions of packages icedove suggests: ii fonts-lyx 2.1.2-2 ii libgssapi-krb5-2 1.12.1+dfsg-10 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765380: don't ship gcc-4.8 with jessie
Am 17.10.2014 um 19:44 schrieb Steve Cotton: > On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: >> Package: src:gcc-4.8 >> Version: 4.8.3-11 >> Severity: serious >> Tags: sid jessie >> >> The current default for GCC (4.9) is good enough for jessie. Don't ship >> legacy >> compilers with jessie. > > Hi Matthias, > > Removing GCC 4.8 will need Linux kernel ABI transitions. > > I haven't seen any discussion on the debian-kernel list, and the > latest of the Linux package (uploaded to sid this week) still has > it generating linux-compiler-* packages depending on gcc-4.8, so > I think the Linux maintainers are expecting GCC 4.8 to be in > Jessie. This was communicated to Ben Hutching at DebConf, so plenty of time to prepare the change. Are there known showstoppers? Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765380: don't ship gcc-4.8 with jessie
On Tue, Oct 14, 2014 at 05:25:13PM +0200, Matthias Klose wrote: > Package: src:gcc-4.8 > Version: 4.8.3-11 > Severity: serious > Tags: sid jessie > > The current default for GCC (4.9) is good enough for jessie. Don't ship legacy > compilers with jessie. Hi Matthias, Removing GCC 4.8 will need Linux kernel ABI transitions. I haven't seen any discussion on the debian-kernel list, and the latest of the Linux package (uploaded to sid this week) still has it generating linux-compiler-* packages depending on gcc-4.8, so I think the Linux maintainers are expecting GCC 4.8 to be in Jessie. (CC'ing the debian-kernel list for comments) Regards, Steve -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764814: freecad downloads and executes code
Okay, I'll try to do that this weekend
Bug#765668: cups: dpkg: cycle found while processing triggers:
Didier 'OdyX' Raboud dixit: >Yet nothing has changed in the CUPS triggers handling in a long time; I Oh. In that case, me ending up with only cups in the cycle is probably only a consequence of the actual error. (Unless the error is caused by #DEBHELPER# inclusions, but I doubt.) >think this is #765434 , hereby force-merging. Thanks! Sounds indeed reasonable. bye, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764814: freecad downloads and executes code
Hi Yorik, 2014-10-15 19:36 GMT+02:00 Yorik van Havre : > I wonder if it's not easier to simply disable the > whole DXF import/export, and indicate to users how to add > it themselves. We have not so much time till Debian`s freeze. If you think, there is no "proper" solution let`s disable this feature. I would be thankful if upstream people propose a nice patch for that. Thanks Anton -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#763617: marked as done (socket-wrapper: FTBFS: tests fail)
Your message dated Fri, 17 Oct 2014 18:58:39 +0200 with message-id <20141017165839.ga1...@jwilk.net> and subject line Re: Bug#763617: socket-wrapper: FTBFS: tests fail has caused the Debian Bug report #763617, regarding socket-wrapper: FTBFS: tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 763617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: socket-wrapper Version: 1.1.1-1 Severity: serious Justification: fails to build from source socket-wrapper FTBFS: | /usr/bin/make -C obj/ test | make[1]: Entering directory '/build/socket-wrapper-EntZBP/socket-wrapper-1.1.1/obj' | Running tests... | /usr/bin/ctest --force-new-ctest-process | Test project /build/socket-wrapper-EntZBP/socket-wrapper-1.1.1/obj | Start 1: test_ioctl | 1/12 Test #1: test_ioctl . Passed0.01 sec | Start 2: test_echo_tcp_socket | 2/12 Test #2: test_echo_tcp_socket ... Passed0.00 sec | Start 3: test_echo_tcp_connect | 3/12 Test #3: test_echo_tcp_connect ..***Failed0.10 sec | Start 4: test_echo_tcp_bind | 4/12 Test #4: test_echo_tcp_bind . Passed0.22 sec | Start 5: test_echo_tcp_socket_options | 5/12 Test #5: test_echo_tcp_socket_options ...***Failed0.19 sec | Start 6: test_echo_tcp_write_read | 6/12 Test #6: test_echo_tcp_write_read ... Passed0.08 sec | Start 7: test_echo_tcp_writev_readv | 7/12 Test #7: test_echo_tcp_writev_readv . Passed0.02 sec | Start 8: test_echo_tcp_get_peer_sock_name | 8/12 Test #8: test_echo_tcp_get_peer_sock_name ...***Failed0.29 sec | Start 9: test_echo_udp_sendto_recvfrom | 9/12 Test #9: test_echo_udp_sendto_recvfrom ..***Failed0.19 sec | Start 10: test_echo_udp_send_recv | 10/12 Test #10: test_echo_udp_send_recv Passed0.17 sec | Start 11: test_echo_udp_sendmsg_recvmsg | 11/12 Test #11: test_echo_udp_sendmsg_recvmsg .. Passed0.03 sec | Start 12: test_sendmsg_recvmsg_fd | 12/12 Test #12: test_sendmsg_recvmsg_fd Passed0.00 sec | | 67% tests passed, 4 tests failed out of 12 | | Total Test time (real) = 1.30 sec | | The following tests FAILED: | 3 - test_echo_tcp_connect (Failed) | 5 - test_echo_tcp_socket_options (Failed) | 8 - test_echo_tcp_get_peer_sock_name (Failed) | 9 - test_echo_udp_sendto_recvfrom (Failed) | Errors while running CTest | make[1]: *** [test] Error 8 -- Jakub Wilk --- End Message --- --- Begin Message --- * Jakub Wilk , 2014-10-01, 14:30: socket-wrapper FTBFS: I can no longer reproduce it. -- Jakub Wilk--- End Message ---
Processed: fixed 765507 in 7.14-2+deb7u7~bpo60+1
Processing commands for cont...@bugs.debian.org:
> fixed 765507 7.14-2+deb7u7~bpo60+1
Bug #765507 {Done: Salvatore Bonaccorso } [drupal7]
[drupal7] CVE-2014-3704 - Drupal - pre Auth SQL Injection Vulnerability
Marked as fixed in versions drupal7/7.14-2+deb7u7~bpo60+1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
765507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 754354 to src:linux, found 754354 in 3.2.60-1+deb7u3, severity of 754354 is important
Processing commands for cont...@bugs.debian.org: > reassign 754354 src:linux 3.2.60-1+deb7u1 Bug #754354 [nfs-kernel-server] nfs-kernel-server: hangs after hours or days, no login to server possible Bug reassigned from package 'nfs-kernel-server' to 'src:linux'. No longer marked as found in versions nfs-utils/1:1.2.6-4. Ignoring request to alter fixed versions of bug #754354 to the same values previously set Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Marked as found in versions linux/3.2.60-1+deb7u1. > found 754354 3.2.60-1+deb7u3 Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Marked as found in versions linux/3.2.60-1+deb7u3. > severity 754354 important Bug #754354 [src:linux] nfs-kernel-server: hangs after hours or days, no login to server possible Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 754354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764696: marked as done (psensor: unsatisfiable build-dependencies on kfreebsd-*)
Your message dated Fri, 17 Oct 2014 16:25:10 + with message-id and subject line Bug#764696: fixed in psensor 1.1.3-2 has caused the Debian Bug report #764696, regarding psensor: unsatisfiable build-dependencies on kfreebsd-* to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 764696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:psensor Version: 1.1.3-1 Severity: serious Hi, psensor fails to build from source on kFreeBSD because libudisks2-dev is not built there. The arch list for psensors should be adjusted to suit. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 i have six years of solaris sysadmin experience, from 8->10. i am well qualified to say it is made from bonghits layered on top of bonghits --- End Message --- --- Begin Message --- Source: psensor Source-Version: 1.1.3-2 We believe that the bug you reported is fixed in the latest version of psensor, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean-Philippe Orsini (supplier of updated psensor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Oct 2014 03:02:39 -0400 Source: psensor Binary: psensor psensor-server psensor-common Architecture: source amd64 all Version: 1.1.3-2 Distribution: unstable Urgency: medium Maintainer: Jean-Philippe Orsini Changed-By: Jean-Philippe Orsini Description: psensor- display graphs for monitoring hardware temperature psensor-common - common files for Psensor and Psensor server psensor-server - Psensor server for monitoring hardware sensors remotely Closes: 764696 Changes: psensor (1.1.3-2) unstable; urgency=medium . * debian/control + switched to standard 3.9.6. + no build dep to libudisks2-dev for kfreebsd. (Closes: #764696) Checksums-Sha1: f9c6c5ccb946b3817fb62b5c9d18ad92d134cd89 2297 psensor_1.1.3-2.dsc cce7a4d9101950b95d42dd5c40f66d3a78ab0d2e 686881 psensor_1.1.3.orig.tar.gz be005172c71796c3ef918cdf80ee2f3e8b6ae979 7368 psensor_1.1.3-2.debian.tar.xz 6485c434402b45478b1ed37336b7191be9e1c25a 61242 psensor_1.1.3-2_amd64.deb 7e0b183a92274ca5cc0659ab14ffa65bd5ac71b0 107706 psensor-server_1.1.3-2_amd64.deb 978a9d8bf7d04457bbc20daf681dda3faec24c89 53084 psensor-common_1.1.3-2_all.deb Checksums-Sha256: 03e76df55bc75e08723bafccfcc72885ecad2d5b53b77cf83a763c5ded43f22e 2297 psensor_1.1.3-2.dsc 340239451bf2d6fe7f725c80e7f177220fb59e1ec8dc081d4e84599792f94d0a 686881 psensor_1.1.3.orig.tar.gz 78fb02b483c26ac9a8c417de956db59fa588fbb78c1ab039378fc30eaed0d2ca 7368 psensor_1.1.3-2.debian.tar.xz ec8d49d44b58404356c1255b2f74175c5c14c6d62185eda34d25742f21ddc842 61242 psensor_1.1.3-2_amd64.deb 0b8de8921d294f15da089c790b963a075053c438ec9f48adaeab8969a1647ed5 107706 psensor-server_1.1.3-2_amd64.deb 35da9fc248567752df4e9e9ee6b9c334d2199055e8617cf3add7d87889c1e4f3 53084 psensor-common_1.1.3-2_all.deb Files: f6c5fa5b1362dbd4967c1587f5678763 2297 utils optional psensor_1.1.3-2.dsc c3a3c1dea4dbfe12bbfb8088b86c3d4f 686881 utils optional psensor_1.1.3.orig.tar.gz a9d90ebbc9fc72ce521f897e722a1f90 7368 utils optional psensor_1.1.3-2.debian.tar.xz 928271713aeeaa51e8d5a7cefbd4344f 61242 utils optional psensor_1.1.3-2_amd64.deb b5fc7dc7f50d837ddc78e6973eca959d 107706 utils optional psensor-server_1.1.3-2_amd64.deb d73d26c0b49ebb35f0d574dcc83860ae 53084 utils optional psensor-common_1.1.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUQTt1AAoJEHQmOzf1tfkT3TMP/iQ8d3eGWXS5gy5XjXRDvdyY 5K4Jr/ItSf17V38kehLWzOxbXjhv5CkiyjiY+xnAdtMmiZFHCjpu3kXANUV0n3eV E8cEODsSrdzRxy663UZIgJzwesqPTxGFOxQeD4alWFNT4h1IHfG2M3Q9uXQ1KIqm pnPSOKho1l3Ui5dhGzxg2GTYAVroDNkSNxkeF0VELgdYk+P0pmh5tss3+geeMnCH aAcXk6RTj/QSlKUoJ7HNOLT2KPKg1x/PrgTImb9noM6DyWP7w/j85MROi31LO7BI nXttLyVFmNZ4rm646BAngBV9B38jWj/jIR+5zdU3yBD97AJtadla1b0ENdui7+Lh 4f
Bug#765566: marked as done (FTBFS: Test failures on multiple environments)
Your message dated Fri, 17 Oct 2014 16:23:40 + with message-id and subject line Bug#765566: fixed in libvirt-glib 0.1.9-4 has caused the Debian Bug report #765566, regarding FTBFS: Test failures on multiple environments to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libvirt-glib Version: 0.1.9-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Hello, Apparentlu 0.1.9 is currently FTBFS on multiple environments due to test failures: make check-TESTS make[4]: Entering directory '/«PKGBUILDDIR»/tests' make[5]: Entering directory '/«PKGBUILDDIR»/tests' PASS: test-events 1 /libvirt-glib/remove-disabled-watch ERROR: test-events - missing test plan ERROR: test-events - exited with status 139 (terminated by signal 11?) PASS: test-gconfig 1 /libvirt-gconfig/domain PASS: test-gconfig 2 /libvirt-gconfig/domain-clock PASS: test-gconfig 3 /libvirt-gconfig/domain-os PASS: test-gconfig 4 /libvirt-gconfig/domain-cpu PASS: test-gconfig 5 /libvirt-gconfig/domain-device-disk PASS: test-gconfig 6 /libvirt-gconfig/domain-device-network PASS: test-gconfig 7 /libvirt-gconfig/domain-device-input PASS: test-gconfig 8 /libvirt-gconfig/domain-device-graphics PASS: test-gconfig 9 /libvirt-gconfig/domain-device-video PASS: test-gconfig 10 /libvirt-gconfig/domain-device-sound PASS: test-gconfig 11 /libvirt-gconfig/domain-device-console PASS: test-gconfig 12 /libvirt-gconfig/domain-device-channel PASS: test-gconfig 13 /libvirt-gconfig/domain-device-usb-redir make[6]: Entering directory '/«PKGBUILDDIR»/tests' make all-am make[7]: Entering directory '/«PKGBUILDDIR»/tests' make[7]: Nothing to be done for 'all-am'. make[7]: Leaving directory '/«PKGBUILDDIR»/tests' make[6]: Leaving directory '/«PKGBUILDDIR»/tests' Testsuite summary for libvirt-glib 0.1.9 # TOTAL: 16 # PASS: 14 make[5]: *** [test-suite.log] Error 1 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 2 See tests/test-suite.log Makefile:1054: recipe for target 'test-suite.log' failed Cheers, Laurent Bigonville -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: libvirt-glib Source-Version: 0.1.9-4 We believe that the bug you reported is fixed in the latest version of libvirt-glib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guido Günther (supplier of updated libvirt-glib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Oct 2014 17:32:20 +0200 Source: libvirt-glib Binary: libvirt-glib-1.0-0 libvirt-glib-1.0-0-dbg libvirt-glib-1.0-dev gir1.2-libvirt-glib-1.0 Architecture: source amd64 Version: 0.1.9-4 Distribution: unstable Urgency: medium Maintainer: Guido Günther Changed-By: Guido Günther Description: gir1.2-libvirt-glib-1.0 - libvirt glib mainloop integration libvirt-glib-1.0-0 - libvirt glib mainloop integration libvirt-glib-1.0-0-dbg - libvirt glib mainloop integration libvirt-glib-1.0-dev - libvirt glib mainloop integration Closes: 765566 Changes: libvirt-glib (0.1.9-4) unstable; urgency=medium . * [7e61158] Fix test by not running main loop twice (Closes: #765566) Checksums-Sha1: deb343426b7760bcc83efebb1b4d4d86079ae972 2269 libvirt-glib_0.1.9-4.dsc 9b2d1d599cad2c123d84ebc41079ccac484e9e16 7540 libvirt-glib_0.1.9-4.debian.tar.xz 6ca7334bd42d380a9cdfc4e1102abc5372a5532d 146398
Bug#765670: marked as done (boinc: not binNMU safe)
Your message dated Fri, 17 Oct 2014 16:21:34 + with message-id and subject line Bug#765670: fixed in boinc 7.4.23+dfsg-1 has caused the Debian Bug report #765670, regarding boinc: not binNMU safe to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boinc Version: 7.4.22+dfsg-3 Severity: serious Your package is not binNMU safe: boinc-app-seti build-depends on: - boinc-dev (>= 7.1.21+dfsg) | libboinc-app-dev (>= 7.1.21+dfsg) boinc-dev depends on: - libboinc-app-dev (= 7.4.22+dfsg-3) boinc-app-seti build-depends on: - boinc-dev (>= 7.1.21+dfsg) | libboinc-app-dev (>= 7.1.21+dfsg) libboinc-app-dev depends on missing: - libboinc-app7 (< 7.4.22+dfsg-3+1~) This is preventing some packages from being built. Emilio --- End Message --- --- Begin Message --- Source: boinc Source-Version: 7.4.23+dfsg-1 We believe that the bug you reported is fixed in the latest version of boinc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated boinc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Oct 2014 14:49:21 +0200 Source: boinc Binary: boinc boinc-nvidia-cuda boinc-amd-opencl boinc-client boinc-manager boinc-dev libboinc-app-dev libboinc-app7 libboinc7 boinc-dbg Architecture: source all Version: 7.4.23+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian BOINC Maintainers Changed-By: Gianfranco Costamagna Description: boinc - metapackage for the BOINC client and the manager boinc-amd-opencl - metapackage for AMD/ATI OpenCL-savvy BOINC client and manager boinc-client - core client for the BOINC distributed computing infrastructure boinc-dbg - debugging symbols for BOINC binaries boinc-dev - development files to build applications for BOINC projects (trans boinc-manager - GUI to control and monitor the BOINC core client boinc-nvidia-cuda - metapackage for CUDA-savvy BOINC client and manager libboinc-app-dev - development files to build applications for BOINC projects libboinc-app7 - libraries for BOINC's scientific applications libboinc7 - libraries of BOINC the client depends on Closes: 765670 Changes: boinc (7.4.23+dfsg-1) unstable; urgency=medium . * New upstream release candidate. * Relaxing dependencies between packages, to allow binNMUs (Closes: #765670). * Remove useless -dbg packages dependencies. * Make boinc multiarch compatible: - switch dev packages to arch:any - remove disabled multiarch tweaks in rules file. - tweak .install files to point to the triplet lib directory Checksums-Sha1: 91cd5a8884f8e5aae7391b518b11f24284d96739 2680 boinc_7.4.23+dfsg-1.dsc 7da65b01b011c7b9c99deca46750567860f14427 34629749 boinc_7.4.23+dfsg.orig.tar.gz 43a69480eccdd0876b424dfe6f35683e17eaf1d3 447916 boinc_7.4.23+dfsg-1.debian.tar.xz b25b6bba50a57ea61627665f34602a7b573a08f9 45360 boinc_7.4.23+dfsg-1_all.deb Checksums-Sha256: d4fb1f6267c4901882f65c800a49b20898ba613fa437de3eaf7a1fba483794b5 2680 boinc_7.4.23+dfsg-1.dsc 7d378288757cabd1984c5509dbe502421ca74d713739d702f808eb045b1bfacf 34629749 boinc_7.4.23+dfsg.orig.tar.gz 83e6a5c09ece50bd9883fe54b64f573b6e859d5cab34a4101781ceab2897483e 447916 boinc_7.4.23+dfsg-1.debian.tar.xz 3bc3f86da9aa7a7c1872c9d7191f0fef25a8d9898327d4a90bb92eacd949ae43 45360 boinc_7.4.23+dfsg-1_all.deb Files: fdf74fdaff52e0b18a9a5bc70258d378 2680 net optional boinc_7.4.23+dfsg-1.dsc b1b2633306d2077db73c4150c17780e5 34629749 net optional boinc_7.4.23+dfsg.orig.tar.gz c45e7dc1fa2a9d80d9a28c88ab674bfe 447916 net optional boinc_7.4.23+dfsg-1.debian.tar.xz 305d55454750c9d75326bae1be121bb0 45360 net optional boinc_7.4.23+dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUQUB0AAoJEItu8lKPB14dU70IAJen4+ZD0b7b4R1jFGk5Ii2z fiRopI02Qt9HDW5Y+l5LzIvGgl6ouJrk+6kY3n4UxU8prPpvXlbmXlCAbUK7v/f1 EE1JMbh/h8UhxCNLFpqtnnFTly5wn7OaJwbxbXjiUmOKEBceZoPMqf
Processed: tagging 765507
Processing commands for cont...@bugs.debian.org:
> tags 765507 + upstream fixed-upstream
Bug #765507 {Done: Salvatore Bonaccorso } [drupal7]
[drupal7] CVE-2014-3704 - Drupal - pre Auth SQL Injection Vulnerability
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
765507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765507: closing 765507
close 765507 7.32-1 thanks Sorry for the reopen, tried to mark it with the fixed control command (vs. notfound) to get the version tracking information right. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 765507 is grave
Processing commands for cont...@bugs.debian.org:
> severity 765507 grave
Bug #765507 {Done: Salvatore Bonaccorso } [drupal7]
[drupal7] CVE-2014-3704 - Drupal - pre Auth SQL Injection Vulnerability
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
765507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707402: marked as done (umview: FTBFS: um_select.c:177: undefined reference to `__FDELT')
Your message dated Fri, 17 Oct 2014 16:02:25 + with message-id and subject line Bug#707402: fixed in umview 0.8.2-1.1 has caused the Debian Bug report #707402, regarding umview: FTBFS: um_select.c:177: undefined reference to `__FDELT' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: umview Version: 0.8.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -DHAVE_CONFIG_H -I. -I.. -Wall -I../include -D_GNU_SOURCE > -DLIBEXECDIR=\"/usr/lib/umview\" -DMODULES_DIR=\"/usr/lib/umview/modules\" > -D_UM_MMAP -D_UM_EPOLL -D_VIEWOS_KM -D_FORTIFY_SOURCE=2 -DNDEBUG -g -O2 > -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security > -Wall -c -o kmview-kmview.o `test -f 'kmview.c' || echo './'`kmview.c > kmview.c: In function 'main': > kmview.c:441:11: warning: ignoring return value of 'asprintf', declared with > attribute warn_unused_result [-Wunused-result] > kmview.c: In function 'kmview_recursive': > kmview.c:304:11: warning: ignoring return value of 'asprintf', declared with > attribute warn_unused_result [-Wunused-result] > kmview.c: In function 'load_it_again': > kmview.c:246:12: warning: ignoring return value of 'asprintf', declared with > attribute warn_unused_result [-Wunused-result] > /bin/bash ../libtool --tag=CC --mode=link gcc -DNDEBUG -g -O2 > -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security > -Wall -rdynamic -Wl,-z,relro -o kmview kmview-canonicalize.o > kmview-capture_nested.o kmview-gdebug.o kmview-mainpoll.o kmview-modutils.o > kmview-pcb.o kmview-scmap.o kmview-sctab.o kmview-services.o > kmview-treepoch.o kmview-um_basicio.o kmview-um_exec.o kmview-um_ioctl.o > kmview-um_misc.o kmview-um_mmap.o kmview-um_plusio.o kmview-um_select.o > kmview-um_services.o kmview-um_signal.o kmview-um_socket.o kmview-um_time.o > kmview-um_uname.o kmview-um_wdm.o kmview-umproc.o kmview-loginshell.o > kmview-hashtab.o kmview-capture_km.o kmview-kmview.o -ldl -lpthread > -lpthread -ldl > libtool: link: gcc -DNDEBUG -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -rdynamic > -Wl,-z -Wl,relro -o kmview kmview-canonicalize.o kmview-capture_nested.o > kmview-gdebug.o kmview-mainpoll.o kmview-modutils.o kmview-pcb.o > kmview-scmap.o kmview-sctab.o kmview-services.o kmview-treepoch.o > kmview-um_basicio.o kmview-um_exec.o kmview-um_ioctl.o kmview-um_misc.o > kmview-um_mmap.o kmview-um_plusio.o kmview-um_select.o kmview-um_services.o > kmview-um_signal.o kmview-um_socket.o kmview-um_time.o kmview-um_uname.o > kmview-um_wdm.o kmview-umproc.o kmview-loginshell.o kmview-hashtab.o > kmview-capture_km.o kmview-kmview.o -lpthread -ldl > kmview-um_select.o: In function `putfdset': > /«PKGBUILDDIR»/xmview/um_select.c:177: undefined reference to `__FDELT' > kmview-um_select.o: In function `getfdset': > /«PKGBUILDDIR»/xmview/um_select.c:171: undefined reference to `__FDELT' > collect2: error: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/umview_0.8.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: umview Source-Version: 0.8.2-1.1 We believe that the bug you reported is fixed in the latest version of umview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated umview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED
Bug#752964: marked as done (libshib-common-java: FTBFS - 5 required artifacts are missing)
Your message dated Fri, 17 Oct 2014 15:55:30 + with message-id and subject line Bug#752964: fixed in libshib-common-java 1.4.0-3 has caused the Debian Bug report #752964, regarding libshib-common-java: FTBFS - 5 required artifacts are missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libshib-common-java Version: 1.4.0-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] 5 required artifacts are missing. for artifact: edu.internet2.middleware:shibboleth-common:jar:1.4.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), shib-snapshot (https://build.shibboleth.net/nexus/content/repositories/snapshots), shib-release (https://build.shibboleth.net/nexus/content/groups/public) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Fri Jun 27 23:36:20 UTC 2014 [INFO] Final Memory: 20M/1963M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael libshib-common-java-build-log.txt.gz Description: application/gunzip pgp4TPDFrysaF.pgp Description: PGP signature --- End Message --- --- Begin Message --- Source: libshib-common-java Source-Version: 1.4.0-3 We believe that the bug you reported is fixed in the latest version of libshib-common-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 752...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated libshib-common-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Oct 2014 15:12:50 +0200 Source: libshib-common-java Binary: libshib-common-java libshib-common-java-doc Architecture: source all Version: 1.4.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libshib-common-java - Shibboleth Common Library libshib-common-java-doc - Documentation for the Shibboleth Common Library Closes: 752964 Changes: libshib-common-java (1.4.0-3) unstable; urgency=medium . * Team upload. * Fixed the build dependencies issues (Closes: #752964): - Added the missing build dependencies on libjcip-annotations-java and libmaven-javadoc-plugin-java - Removed the unused build dependency on ant-contrib - Build depend on libsvnkit-java >= 1.8.6-1~ * Build depend on libmail-java instead of libgnumail-java * Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: ee8f7ac8123500ab62372db2c69d0c3e5d036da9 2800 libshib-common-java_1.4.0-3.dsc 374845e547880584947dcf7337f33517991761d4 4088 libshib-common-java_1.4.0-3.debian.tar.xz e5e488c5a50c4f7fdfd6b2997586aecb518eecbd 583870 libshib-common-java_1.4.0-3_all.deb 3a962c71bc72b874a6fb23716f903a6231081df7 2841128 libshib-common-java-doc_1.4.0-3_all.deb Checksums-Sha256: 83e6b8900781d6ca2d7511973593cc7d4ed7909d6018330e1484dd1574547806 2800 libshib-common-java_1.4.0-3.dsc 1a7560f9caa2b6a4805a8ec84fff495774beab2acdccf65c1fc2cca8bb139b54 4088 libshib-common-java_1.4.0-3.debian.tar.xz 0d06bfdd04d4e9f4cdcc6d9462b39e7981cef5a799b733bc48e26330090b4fdd 583870 libshib-common-java_1.4.0-3_all.deb 27ac3ae2576fe21db0a57d307383459e4915df407365340bab4e992b794f197b 2841128 libshib-common-java-doc_1.4.0-3_all.deb Files: 420c137a64f5c3974f09f1c3bc583d2f 2800 java optional l
Processed: Re: Bug#765726: nvidia-driver 340.46-1 Unusable with GF108 and GT610
Processing control commands: > severity -1 normal Bug #765726 [nvidia-driver] nvidia-driver 340.46-1 Unusable with GF108 and GT610 Severity set to 'normal' from 'critical' > tag -1 moreinfo Bug #765726 [nvidia-driver] nvidia-driver 340.46-1 Unusable with GF108 and GT610 Added tag(s) moreinfo. -- 765726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765726: nvidia-driver 340.46-1 Unusable with GF108 and GT610
Control: severity -1 normal Control: tag -1 moreinfo Hi Martin, On 2014-10-17 17:26, Martin Gallant wrote: > nvidia-driver upgrade this morning on my Jessie systems broke both my > NVIDIA boxes > One is a amd64 latop with Quadro 1000M (GF108M) > The other is a i386 with a generic GT610 card > Everything was peachy on 340.32.-1 before this upgrade your bug report unfortunately contains no information that could help us analyze the problem. Running reportbug -N 765726 on a "broken" system would collect system state and logfiles that might show some issues. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765726: nvidia-driver 340.46-1 Unusable with GF108 and GT610
Package: nvidia-driver Version: 340.46-1 Severity: Critical nvidia-driver upgrade this morning on my Jessie systems broke both my NVIDIA boxes One is a amd64 latop with Quadro 1000M (GF108M) The other is a i386 with a generic GT610 card Everything was peachy on 340.32.-1 before this upgrade Downgrading to the following packages from snapshot.debian.org got me back online libgl1-nvidia-glx_340.32-1_amd64.deb libnvidia-ml1_340.32-1_amd64.deb nvidia-alternative_340.32-1_amd64.deb nvidia-driver_340.32-1_amd64.deb nvidia-kernel-dkms_340.32-1_amd64.deb nvidia-modprobe_340.32-1_amd64.deb nvidia-vdpau-driver_340.32-1_amd64.deb xserver-xorg-video-nvidia_340.32-1_amd64.deb [ 5.086] X.Org X Server 1.16.0 Release Date: 2014-07-16 [ 5.086] X Protocol Version 11, Revision 0 [ 5.086] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian [ 5.086] Current Operating System: Linux hp8560w 3.14-1-amd64 #1 SMP Debian 3.14.12-1 (2014-07-11) x86_64 [ 5.086] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-amd64 root=/dev/mapper/ss-xfce ro quiet [ 5.086] Build Date: 17 July 2014 10:22:36PM [ 5.086] xorg-server 2:1.16.0-1 (http://www.debian.org/support) [ 5.086] Current version of pixman: 0.32.6 [ 5.086] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 5.086] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 5.086] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 26 15:09:23 2014 [ 5.087] (==) Using config file: "/etc/X11/xorg.conf" [ 5.087] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 5.089] (==) No Layout section. Using the first Screen section. [ 5.089] (==) No screen section available. Using defaults. [ 5.089] (**) |-->Screen "Default Screen Section" (0) [ 5.089] (**) | |-->Monitor "" [ 5.089] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 5.089] (**) | |-->Device "NVIDIA Quadro 1000M" [ 5.089] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 5.089] (==) Automatically adding devices [ 5.089] (==) Automatically enabling devices [ 5.089] (==) Automatically adding GPU devices [ 5.092] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 5.092] Entry deleted from font path. [ 5.096] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 5.096] (==) ModulePath set to "/usr/lib/xorg/modules" [ 5.096] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 5.096] (II) Loader magic: 0x7f95b75dcd80 [ 5.096] (II) Module ABI versions: [ 5.096] X.Org ANSI C Emulation: 0.4 [ 5.096] X.Org Video Driver: 18.0 [ 5.096] X.Org XInput driver : 21.0 [ 5.096] X.Org Server Extension : 8.0 [ 5.097] (--) PCI:*(0:1:0:0) 10de:0dfa:103c:1631 rev 161, Mem @ 0xd000/16777216, 0xc000/134217728, 0xc800/33554432, I/O @ 0x4000/128, BIOS @ 0x/524288 [ 5.097] (II) LoadModule: "glx" [ 5.099] (II) Loading /usr/lib/xorg/modules/linux/libglx.so [ 5.216] (II) Module glx: vendor="NVIDIA Corporation" [ 5.216] compiled for 4.0.2, module version = 1.0.0 [ 5.217] Module class: X.Org Server Extension [ 5.217] (II) NVIDIA GLX Module 340.24 Wed Jul 2 15:04:31 PDT 2014 [ 5.218] (II) LoadModule: "nvidia" [ 5.219] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [ 5.228] (II) Module nvidia: vendor="NVIDIA Corporation" [ 5.228] compiled for 4.0.2, module version = 1.0.0 [ 5.228] Module class: X.Org Video Driver [ 5.230] (II) NVIDIA dlloader X Driver 340.24 Wed Jul 2 14:42:23 PDT 2014 [ 5.230] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 5.230] (++) using VT number 7 [ 5.234] (II) Loading sub module "fb" [ 5.234] (II) LoadModule: "fb" [ 5.234] (II) Loading /usr/lib/xorg/modules/libfb.so [ 5.237] (II) Module fb: vendor="X.Org Foundation" [ 5.237] compiled for 1.16.0, module version = 1.0.0 [ 5.237] ABI class: X.Org ANSI C Emulation, version 0.4 [ 5.237] (WW) Unresolved symbol: fbGetGCPrivateKey [ 5.237] (II) Loading sub module "wfb" [ 5.237] (II) LoadModule: "wfb" [ 5.237] (II) Loading /usr/lib/xorg/modules/libwfb.so [ 5.240] (II) Module wfb: vendor="X.Org Foundation" [ 5.240] compiled for 1.16.0, module version = 1.0.0 [ 5.240] ABI class: X.Org ANSI C Emulation, version 0.4 [ 5.240] (II) Loading sub module "ramdac" [ 5.240] (II) LoadModule: "ramda
Bug#764318: Could be that the correct way to solve the problem?
Doing an apt-cache show libjpeg-progs and an apt-cache show libjpeg-turbo-progs, i saw that libjpeg-progs depends on libjpeg-turbo-progs, but that libjpeg-turbo-progs breaks libjpeg-progs. I think that in Debian administrators handbook is said that when a package breaks another is because the breaker package does the same jobs than the breaked one, so i decided to directly remove libjpeg-progs. Have I done some crazy thing or it is a way to solve the problem? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765725: Crash with "terminate called after throwing an instance of 'Gio::Error'"
Package: pavucontrol
Version: 2.0-2
Severity: grave
File: /usr/bin/pavucontrol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
When running pavucontrol, it just crashes. Here is a backtrace:
Program received signal SIGABRT, Aborted.
0x72a41077 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0 0x72a41077 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 9505
selftid = 9505
#1 0x72a42458 in __GI_abort () at abort.c:89
save_stage = 2
act = {
__sigaction_handler = {
sa_handler = 0x96a3a0,
sa_sigaction = 0x96a3a0
},
sa_mask = {
__val = {12925824, 6595224, 140737351949831, 1, 0, 12886432,
140737264037160, 140737337045957, 6595224, 12824896, 140737351975717,
140737353759264, 12886352, 1, 140737353761616, 12886352}
},
sa_flags = -8952,
sa_restorer = 0x7fffd810
}
sigs = {
__val = {32, 0 }
}
#2 0x73548b2d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#3 0x73546ba6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#4 0x73546bf1 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#5 0x73546e09 in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#6 0x76f68ff7 in Gio::Error::throw_func (gobject=0x9d7470) at
error.cc:58
No locals.
#7 0x76a26977 in Glib::Error::throw_exception (gobject=0x9d7470) at
error.cc:167
throw_func =
__PRETTY_FUNCTION__ = "static void
Glib::Error::throw_exception(GError*)"
#8 0x779c6ced in Gtk::IconTheme::load_icon (this=0xa6a7c0,
icon_name=..., size=16, flags=Gtk::ICON_LOOKUP_GENERIC_FALLBACK) at
icontheme.cc:347
gerror = 0x9d7470
retvalue = {
pCppObject_ = 0x0
}
#9 0x0041f3b2 in ?? ()
No symbol table info available.
#10 0x0041f7c8 in ?? ()
No symbol table info available.
#11 0x004271c8 in ?? ()
No symbol table info available.
#12 0x7380ccf5 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#13 0x7fffedbbab61 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so
No symbol table info available.
#14 0x7fffedbbaef3 in pa_pdispatch_run () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so
No symbol table info available.
#15 0x738026ae in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#16 0x7fffedbbf160 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-5.0.so
No symbol table info available.
#17 0x73a45bba in ?? () from
/usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0
No symbol table info available.
#18 0x73c92c5d in g_main_dispatch (context=0x6d8100) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3111
dispatch = 0x73a45a60
prev_source = 0x0
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs =
cb_data =
need_destroy =
source = 0x96b1b0
current = 0x979460
i = 1
#19 g_main_context_dispatch (context=context@entry=0x6d8100) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3710
No locals.
#20 0x73c92f48 in g_main_context_iterate (context=0x6d8100,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3781
max_priority = 0
timeout = 0
some_ready = 1
nfds =
allocated_nfds = 4
fds = 0x9e34e0
#21 0x73c93272 in g_main_loop_run (loop=0x9bd1b0) at
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3975
__FUNCTION__ = "g_main_loop_run"
#22 0x7578ba85 in gtk_main () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
No symbol table info available.
#23 0x779d612f in run_impl (this=) at main.cc:439
No locals.
#24 Gtk::Main::run (window=...) at main.cc:398
No locals.
#25 0x0040ed3e in ?? ()
No symbol table info available.
#26 0x72a2db45 in __libc_start_main (main=0x40ea30, argc=1,
argv=0x7fffe688, init=, fini=,
rtld_fini=, stack_end=0x7fffe678) at libc-start.c:287
result =
unwind_buf = {
cancel_jmp_buf = {{
jmp_buf = {0, -6509670257359671333, 4255741, 140737488348800, 0,
0, 6509670256477646811, 6509641144830046171},
mask_was_saved = 0
}},
priv = {
pad = {0x0, 0x0, 0x42b160, 0x7fffe688},
data = {
prev = 0x0,
cleanup
Bug#764901: linux-image-3.16-2-amd64: Suspend results in shutdown
Control: severity -1 important Control: tag -1 moreinfo On Sat, 11 Oct 2014 21:44:53 -0600 David Zundel wrote: > Package: src:linux > Version: 3.16.3-2 > Severity: critical > Justification: causes serious data loss Not unless this causes disk corruption. > Dear Maintainer, > > Following installation of linux-image-3.16-2-amd64 and related, attempts > at suspend most often (but not always) result in an unwanted shutdown. > > Reverting to linux-image-3.14-2-amd64 resolves the problem. > > Attempted re-installation of linux-image-3.16-2-amd64 generates an error > report: > Error! Bad return status for module build on kernel: 3.16-2-amd64 > (x86_64) > Consult /var/lib/dkms/open-vm-tools/2012.05.21/build/make.log for more > information. That is a bug in open-vm-tools, not the kernel. > > -- Package-specific info: > ** Version: > Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version > 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) > > ** Command line: > BOOT_IMAGE=/vmlinuz-3.16-2-amd64 > root=UUID=5051f67f-ea68-41c3-ba22-bb2c1210b21b ro initrd=/install/initrd.gz > quiet > > ** Tainted: PO (4097) > * Proprietary module has been loaded. > * Out-of-tree module has been loaded. [...] Please test whether suspend works properly without the Broadcom wireless driver (wl) installed. Ben. -- Ben Hutchings Life is what happens to you while you're busy making other plans. - John Lennon signature.asc Description: This is a digitally signed message part
Processed: Re: linux-image-3.16-2-amd64: Suspend results in shutdown
Processing control commands: > severity -1 important Bug #764901 [src:linux] linux-image-3.16-2-amd64: Suspend results in shutdown Severity set to 'important' from 'critical' > tag -1 moreinfo Bug #764901 [src:linux] linux-image-3.16-2-amd64: Suspend results in shutdown Added tag(s) moreinfo. -- 764901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 764814
Processing commands for cont...@bugs.debian.org: > tags 764814 + upstream Bug #764814 [freecad] freecad downloads and executes code Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 764814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765722: CVE-2014-3660 libxml2 billion laugh variant
Package: libxml2 Severity: serious Tags: security patch Hi, The Netherlands Cyber Security Center announced an issue in libxml2. https://www.ncsc.nl/actueel/nieuwsberichten/kwetsbaarheid-ontdekt-in-libxml2.html It seems to be a variant of the classic 'billion laughs' vulnerability. Upstream has fixed this in 2.9.2: https://git.gnome.org/browse/libxml2/commit/?id=be2a7edaf289c5da74a4f9ed3a0b6c733e775230 Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765665: marked as done (missing license in debian/copyright)
Your message dated Fri, 17 Oct 2014 13:51:20 + with message-id and subject line Bug#765665: fixed in owfs 2.9p7-2 has caused the Debian Bug report #765665, regarding missing license in debian/copyright to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: owfs Version: 2.9p7-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of: module/swig/perl5/OW/* to debian/copyright. Thanks! Thorsten --- End Message --- --- Begin Message --- Source: owfs Source-Version: 2.9p7-2 We believe that the bug you reported is fixed in the latest version of owfs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Danjean (supplier of updated owfs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Oct 2014 15:08:15 +0200 Source: owfs Binary: owfs-common owfs libow-2.9-7 libowcapi-2.9-7 libow-dev libownet-2.9-7 libownet-dev owserver ow-shell ow-tools owfs-fuse owhttpd owftpd libow-php5 libownet-php libow-perl libownet-perl python-ow python-ownet libow-tcl owfs-doc owfs-dbg Architecture: all amd64 source Version: 2.9p7-2 Distribution: unstable Urgency: medium Maintainer: Vincent Danjean Changed-By: Vincent Danjean Closes: 765665 Description: libow-2.9-7 - 1-Wire File System full library libowcapi-2.9-7 - 1-Wire File System C library libow-dev - 1-Wire File System (development files) libownet-2.9-7 - owserver protocol library libownet-dev - owserver protocol library (development files) libownet-perl - Perl module for accessing 1-wire networks libownet-php - Dallas 1-wire support: PHP OWNet library libow-perl - Dallas 1-wire support: Perl5 bindings libow-php5 - Dallas 1-wire support: PHP5 bindings libow-tcl - Dallas 1-wire support: Tcl bindings owfs-common - common files used by any of the OWFS programs owfs - Dallas 1-wire support owfs-dbg - Debugging symbols for the OWFS packages owfs-doc - Dallas 1-wire support: Documentation for owfs owfs-fuse - 1-Wire filesystem owftpd - FTP daemon providing access to 1-Wire networks owhttpd- HTTP daemon providing access to 1-Wire networks owserver - Backend server for 1-Wire control ow-shell - shell utilities to talk to an 1-Wire owserver ow-tools - tools to monitor or inspect a ow-server link python-ow - Dallas 1-wire support: Python bindings python-ownet - Python module for accessing 1-wire networks Changes: owfs (2.9p7-2) unstable; urgency=medium . * remove README.source template * fix perl source file licenses in copyright and reorganize it (Closes: #765665) Checksums-Sha1: 568e23e3d221f5cc24aaf7336d32a0b8664102e2 2977 owfs_2.9p7-2.dsc 0aaafe2a109fba0ca0079af608e5b9db3087df13 52036 owfs_2.9p7-2.debian.tar.xz a07b491c6797340f5c5162a8eb42d14d6a5be4b0 15456 owfs-common_2.9p7-2_all.deb db88e85b4f97de960fde0542e2665fead766d352 7390 owfs_2.9p7-2_all.deb c5c1210a1bedf118728aecedb0d3ddbb07ae21bc 216800 libow-2.9-7_2.9p7-2_amd64.deb c7865963ef2de2ac96e0adea815516367c203937 10942 libowcapi-2.9-7_2.9p7-2_amd64.deb 360a91db1f85766d3c486744498068183c20b899 15154 libow-dev_2.9p7-2_amd64.deb a39d3f0f7a8a7e91a6e2e118292b9d734bd620c1 20520 libownet-2.9-7_2.9p7-2_amd64.deb 1f5efa76f0da891f6a0f9a580a22ae41406194ad 14192 libownet-dev_2.9p7-2_amd64.deb 37989c081376d19d4d5b455a1e31e1d7dc46f41c 23840 owserver_2.9p7-2_amd64.deb b3649ff447f5deda43d70319e31fca549a7e1843 25894 ow-shell_2.9p7-2_amd64.deb 4fa2a45fa4f21fc06c28d3d33797248e57f18bbb 26740 ow-tools_2.9p7-2_all.deb efa53430bc673096e2f531bfe7d66ee22f48336a 18922 owfs-fuse_2.9p7-2_amd64.deb 23e9c833995b3d410860b249942b38675a032897 26036 owhttpd_2.9p7-2_amd64.deb c138ac1adcc00ce167db8a0ade0f43aaec17ab1e 36362 owftpd_2.9p7-2_amd64.deb 909821580682a8639ecd18e0bf43d39f05d1da0a 12812 libow-php5_2.9p7-2_amd64.deb fca0259a77fa8ae1dc5e577f0cbbbeeb87df83bf 16030 libowne
Processed: user debian-secur...@lists.debian.org, usertagging 764814, tagging 764814
Processing commands for cont...@bugs.debian.org: > user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). > usertags 764814 + tracked There were no usertags set. Usertags are now: tracked. > tags 764814 + security Bug #764814 [freecad] freecad downloads and executes code Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 764814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765706: Please give back webkit2gtk on kfreebsd-i386
Dear debian-wb-team, Please give back webkit2gtk for build on kfreebsd-i386. There is a bug report open already (#765706) for what looks like a race during build (on multiple arches), but it already built everywhere else. On 17/10/14 14:07, Alberto Garcia wrote: > Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=137686 > > On Fri, Oct 17, 2014 at 01:51:50PM +0100, Steven Chamberlain wrote: >> webkit2gtk FTBFS on its first build attempt on linux-i386 and >> kfreebsd-i386 due to: > > Thanks for the report. > > I'm afraid that it's not specific to x86, I also saw it the other day > with ppc64el (see the upstream bug report). > >> Is this a race condition or perhaps something to do with a build >> dependency? > > A race condition would be my guess, but I haven't had the time to > investigate it yet. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765706: webkit2gtk: sometimes FTBFS[any-i386]: undefined method `[]' for nil:NilClass
Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=137686 On Fri, Oct 17, 2014 at 01:51:50PM +0100, Steven Chamberlain wrote: > webkit2gtk FTBFS on its first build attempt on linux-i386 and > kfreebsd-i386 due to: Thanks for the report. I'm afraid that it's not specific to x86, I also saw it the other day with ppc64el (see the upstream bug report). > Is this a race condition or perhaps something to do with a build > dependency? A race condition would be my guess, but I haven't had the time to investigate it yet. Berto -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#765706: webkit2gtk: sometimes FTBFS[any-i386]: undefined method `[]' for nil:NilClass
Processing control commands: > forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=137686 Bug #765706 [webkit2gtk] webkit2gtk: sometimes FTBFS[any-i386]: undefined method `[]' for nil:NilClass Set Bug forwarded-to-address to 'https://bugs.webkit.org/show_bug.cgi?id=137686'. -- 765706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765678: ruby-rack: FTBFS - rake aborted!
Control: tag -1 unreproducible Control: severity -1 normal On Fri, Oct 17, 2014 at 11:55:00AM +0200, Michael Tautschnig wrote: > Package: ruby-rack > Version: 1.5.2-2 > Severity: serious > Usertags: goto-cc > > During a rebuild of all Debian packages in a clean sid chroot (using > cowbuilder > and pbuilder) the build failed with the following error. > > [...] > Entering dh_ruby --install > Rewriting shebang line of > /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack/usr/bin/rackup > Running tests for ruby2.1 using debian/ruby-tests.rake ... > /usr/bin/ruby2.1 /usr/bin/bacon -I./lib:./test -w -a -q -t > '^(?!Rack::Adapter|Rack::Session::Memcache|Rack::Server|Rack::Handler)' > /usr/lib/ruby/vendor_ruby/bacon.rb:221: warning: shadowing outer local > variable - args > /usr/lib/ruby/vendor_ruby/memcache.rb:303: warning: assigned but unused > variable - key_count > /usr/lib/ruby/vendor_ruby/memcache.rb:812: warning: assigned but unused > variable - key > /usr/lib/ruby/vendor_ruby/memcache.rb:24: warning: assigned but unused > variable - e > /usr/lib/ruby/vendor_ruby/continuum_native.rb:38: warning: assigned but > unused variable - e > /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in > `': uninitialized constant Rack::Handler::WEBrick (NameError) > from /usr/bin/bacon:116:in `load' > from /usr/bin/bacon:116:in `block in ' > from /usr/bin/bacon:115:in `each' > from /usr/bin/bacon:115:in `' > /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in > `': uninitialized constant Rack::Handler::WEBrick (NameError) > from /usr/bin/bacon:116:in `load' > from /usr/bin/bacon:116:in `block in ' > from /usr/bin/bacon:115:in `each' > from /usr/bin/bacon:115:in `' > . > Finished in 0.339649703 seconds. > > 217 tests, 722 assertions, 0 failures, 0 errors > rake aborted! > Command failed with status (1): [/usr/bin/ruby2.1 /usr/bin/bacon > -I./lib:./...] > /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-tests.rake:6:in > `block in ' > -e:1:in `' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby2.1" failed. Exiting. > dh_auto_install: dh_ruby --install > /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack > returned exit code 1 > debian/rules:15: recipe for target 'binary' failed > make: *** [binary] Error 1 > > The full build log is attached; please do let me know if the problem is > unreproducible, in which case I shall try to investigate further. It does work under sbuild. looking at the source, I understand why it would fail, but I don't understand why it doesn't under sbuild. I have just uploaded a new version that runs the test suite in verbose mode, maybe you can retry on your infrastructure and compare the output, maybe it has something to do with the order in which the tests are run, or something like that. I'm attaching the build log on my end. -- Antonio Terceiro sbuild (Debian sbuild) 0.64.3 (30 Sep 2014) on homer ╔══╗ ║ ruby-rack 1.5.2-3 (amd64) 17 Out 2014 09:49 ║ ╚══╝ Package: ruby-rack Version: 1.5.2-3 Source Version: 1.5.2-3 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 I: NOTICE: Log filtering will replace 'build/ruby-rack-teZpse/ruby-rack-1.5.2' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/ruby-rack-teZpse' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-691f63bc-c545-423f-9f52-cfefdcd84d61' with '«CHROOT»' ┌──┐ │ Update chroot│ └──┘ Get:1 http://http.debian.net unstable InRelease [242 kB] Get:2 http://http.debian.net unstable/main amd64 Packages/DiffIndex [7876 B] Get:3 http://http.debian.net unstable/main amd64 2014-10-16-2042.39.pdiff [26.7 kB] Get:4 http://http.debian.net unstable/main amd64 2014-10-17-0239.33.pdiff [50.7 kB] Get:5 http://http.debian.net unstable/main amd64 2014-10-17-0842.51.pdiff [52.6 kB] Get:6 http://http.debian.net unstable/main amd64 2014-10-17-0842.51.pdiff [52.6 kB] Fetched 380 kB in 1s (206 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ┌
Bug#765706: webkit2gtk: sometimes FTBFS[any-i386]: undefined method `[]' for nil:NilClass
Package: webkit2gtk Version: 2.6.1+dfsg1-2 Severity: serious Hi, webkit2gtk FTBFS on its first build attempt on linux-i386 and kfreebsd-i386 due to: https://buildd.debian.org/status/fetch.php?pkg=webkit2gtk&arch=i386&ver=2.6.1%2Bdfsg1-2&stamp=1413468679 | cd /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-i586-linux-gnu/Source/JavaScriptCore && /usr/bin/ruby /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/offlineasm/generate_offset_extractor.rb -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-i586-linux-gnu/DerivedSources/JavaScriptCore/ /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/JavaScriptCore/llint/LowLevelInterpreter.asm /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-i586-linux-gnu/DerivedSources/JavaScriptCore/LLIntDesiredOffsets.h | Building CXX object Source/WebCore/CMakeFiles/ANGLESupport.dir/__/ThirdParty/ANGLE/src/compiler/translator/glslang_tab.cpp.o | cd /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/obj-i586-linux-gnu/Source/WebCore && /usr/bin/c++ -DBUILDING_GTK__=1 -DBUILDING_WEBKIT -DBUILDING_WITH_CMAKE=1 -DDATA_DIR=\"share\" -DENABLE_3D_RENDERING=1 -DENABLE_PLUGIN_PROCESS_GTK2=1 -DGETTEXT_PACKAGE=\"WebKit2GTK-4.0\" -DHAVE_CONFIG_H=1 -DMOZ_X11=1 -DUSER_AGENT_GTK_MAJOR_VERSION=601 -DUSER_AGENT_GTK_MINOR_VERSION=1 -DWEBKITGTK_API_VERSION_STRING=\"4.0\" -DWEBKIT_DOM_USE_UNSTABLE_API -DWTF_PLATFORM_X11=1 -DWTF_USE_3D_GRAPHICS=1 -DWTF_USE_GLX=1 -DWTF_USE_GSTREAMER -DWTF_USE_OPENGL=1 -DWTF_USE_TEXTURE_MAPPER=1 -DWTF_USE_TEXTURE_MAPPER_GL=1 -DWTF_USE_WEBAUDIO_GSTREAMER -DXP_UNIX -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wall -DNDEBUG -std=c++11 -fno-exceptions -fno-strict-aliasing -fno-rtti -fno-omit-frame-pointer -fno-tree-dce -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/airplay -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source /WebCore/Modules/battery -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/encryptedmedia -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/gamepad -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/gamepad/deprecated -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/geolocation -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/indexeddb -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/indieui -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/mediacontrols -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/mediasource -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/mediastream -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/navigatorcontentutils -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/notifications -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/plugins -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/proximity -I /«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/quota -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/speech -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/vibration -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/webaudio -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/webdatabase -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/Modules/websockets -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/accessibility -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bindings -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bindings/generic -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bindings/js -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bridge -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bridge/c -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/bridge/jsc -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/crypto -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/ crypto/algorithms -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/crypto/keys -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/crypto/parameters -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/css -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/cssjit -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/dom -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/dom/default -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/editing -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/fileapi -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/history -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html/canvas -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html/forms -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html/parser -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html/shadow -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/html/track -I/«BUILDDIR»/webkit2gt k-2.6.1+dfsg1/Source/WebCore/inspector -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/loader -I/«BUILDDIR»/webkit2gtk-2.6.1+dfsg1/Source/WebCore/loader/appcache -I/
Processed: Re: Bug#765678: ruby-rack: FTBFS - rake aborted!
Processing control commands: > tag -1 unreproducible Bug #765678 [ruby-rack] ruby-rack: FTBFS - rake aborted! Added tag(s) unreproducible. > severity -1 normal Bug #765678 [ruby-rack] ruby-rack: FTBFS - rake aborted! Severity set to 'normal' from 'serious' -- 765678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 765667 to libjpeg-progs,libjpeg-turbo-progs ...
Processing commands for cont...@bugs.debian.org: > reassign 765667 libjpeg-progs,libjpeg-turbo-progs Bug #765667 [libjpeg-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #764318 [libjpeg-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs Bug reassigned from package 'libjpeg-progs' to 'libjpeg-progs,libjpeg-turbo-progs'. Bug reassigned from package 'libjpeg-progs' to 'libjpeg-progs,libjpeg-turbo-progs'. No longer marked as found in versions libjpeg9/1:9a-2 and libjpeg-turbo/1:1.3.1-3. No longer marked as found in versions libjpeg9/1:9a-2 and libjpeg-turbo/1:1.3.1-3. Ignoring request to alter fixed versions of bug #765667 to the same values previously set Ignoring request to alter fixed versions of bug #764318 to the same values previously set > found 765667 libjpeg-progs/1:9a-2,libjpeg-turbo-progs/1:1.3.1-3 Bug #765667 [libjpeg-progs,libjpeg-turbo-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #764318 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs The source libjpeg-progs and version 1:9a-2 do not appear to match any binary packages The source libjpeg-turbo-progs and version 1:1.3.1-3 do not appear to match any binary packages Marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. Marked as found in versions libjpeg-turbo-progs/1:1.3.1-3 and libjpeg-progs/1:9a-2. > fixed 765667 libjpeg-turbo-progs/1:1.3.1-6 Bug #765667 [libjpeg-progs,libjpeg-turbo-progs] [libjpeg-progs] Conflicts with libjpeg-turbo-progs Bug #764318 [libjpeg-progs,libjpeg-turbo-progs] libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in libjpeg-turbo-progs The source libjpeg-turbo-progs and version 1:1.3.1-6 do not appear to match any binary packages Marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. Marked as fixed in versions libjpeg-turbo-progs/1:1.3.1-6. > thanks Stopping processing here. Please contact me if you need assistance. -- 764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318 765667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765540: [SOLVED] Re:
On Fri, 17 Oct 2014 01:21:57 +0200 =?UTF-8?Q?Jos=C3=A9_A=2E_Barrera?= wrote: Hi. I have the same issue after upgrade. I access to my system with a rescue. Try dpkg-reconfigure grub-pc and found all my images. After that, i try to install grub with: # grub-install /dev/sda And I get this error: Grub-install: error: cannot copy `/usr/share/locale/sv.gmo' to `/boot/grub/locale/sv.mo': is a directory. And finish without install. Hi. I found three directories .gmo in mi locale directory (sv.gmo one of them). I checked that they were equals to the locale and move them to a temp. After that, I purged grub-pc and installed it and it installed fine in my boot. That temp directories were the problem for me. I really don't know what program create them (they have date of 2007 :)) So, that fixed the problem for me. Thanks and sorry for the noise. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764897: kfreebsd-kernel-headers: net/route.h fails to compile in userland, squid3 FTBFS
affects 764897 + squid3 thanks On 12/10/14 02:00, Steven Chamberlain wrote: > kfreebsd-kernel-headers >= 10.1~ adds a sys/counter.h, used in various > places including net/route.h. It requires a kernel type uint64_t > (from sys/kglue/sys/types.h) without which any userland code using > net/route.h could break This also caused squid3 to FTBFS; it should be fixed by a new upload of kfreebsd-kernel-headers today. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Bug#764897: kfreebsd-kernel-headers: net/route.h fails to compile in userland, squid3 FTBFS
Processing commands for cont...@bugs.debian.org: > affects 764897 + squid3 Bug #764897 [kfreebsd-kernel-headers] kfreebsd-kernel-headers: net/route.h fails to compile in userland, nmap FTBFS Added indication that 764897 affects squid3 > thanks Stopping processing here. Please contact me if you need assistance. -- 764897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747465: marked as done (notification-daemon crashes)
Your message dated Fri, 17 Oct 2014 11:19:14 + with message-id and subject line Bug#747465: fixed in notification-daemon 0.7.6-2 has caused the Debian Bug report #747465, regarding notification-daemon crashes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 747465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: notification-daemon Version: 0.7.6-1 Severity: normal --- Please enter the report below this line. --- When I start notification-daemon in an LXDE environment and try to send a notification via notifiy-send, the expected notification popup appears but notification-daemon crashes now with the following message in terminal: (notification-daemon:2280): GLib-CRITICAL **: Source ID 17 was not found when attempting to remove it Another execution of notify-send does nothing anymore. I found out that notifications work correct if I provide the following file /usr/share/dbus-1/services/org.gnome.Notifications.service with content: [D-BUS Service] Name=org.freedesktop.Notifications Exec=/usr/lib/notification-daemon/notification-daemon In Squeeze notification-daemon package this file was present and removed in Wheezy. Specific notification-daemon packages for a certain desktop, e.g. Mate in Jessie provide the file /usr/share/dbus-1/services/org.freedesktop.mate.Notifications.service. --- System information. --- Architecture: i386 Kernel: Linux 3.14.0-1-generic Debian Release: jessie/sid 500 testing security.debian.org 500 testing ftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Maximilian Gerhard --- End Message --- --- Begin Message --- Source: notification-daemon Source-Version: 0.7.6-2 We believe that the bug you reported is fixed in the latest version of notification-daemon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 747...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Henriksson (supplier of updated notification-daemon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 17 Oct 2014 13:00:53 +0200 Source: notification-daemon Binary: notification-daemon Architecture: source amd64 Version: 0.7.6-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Andreas Henriksson Description: notification-daemon - daemon for displaying passive pop-up notifications Closes: 693837 747465 Changes: notification-daemon (0.7.6-2) unstable; urgency=medium . * Team upload. . [ Jeremy Bicha ] * Use canonical Vcs-* fields. . [ intrigeri ] * Fix_GSource_usage_with_recent_GLib.patch: new patch, from upstream Bugzilla (Closes: #747465). * Fix_positioning_notifications_with_long_text.patch: new patch, from upstream Bugzilla (Closes: #693837). Checksums-Sha1: d0173d76df7a1ab13950a5cea7754f8ff427829d 2284 notification-daemon_0.7.6-2.dsc f5dc6be9f71e9c31a9e08bd8a7b39d99161c6224 8664 notification-daemon_0.7.6-2.debian.tar.xz 8d95db8f70c907f97959422709a30cb99faab5a1 51406 notification-daemon_0.7.6-2_amd64.deb Checksums-Sha256: 301e79a9ae6f25c4809fcbf23879c343fde292945a18add125b954b48bcf510c 2284 notification-daemon_0.7.6-2.dsc 8de41bb62a4e92fefb5a61ff386315190c4786e9e248c35d076527faaff8e14d 8664 notification-daemon_0.7.6-2.debian.tar.xz 0533a7a509381774b6926b93f8d40739cc3011801c8c1ee37726d2303ceba5f8 51406 notification-daemon_0.7.6-2_amd64.deb Files: 6cf3520d3248111b2e0b2d92cd2b8abe 2284 x11 optional notification-daemon_0.7.6-2.dsc 09a7804788720dbcd4216d666e89d2c1 8664 x11 optional notification-daemon_0.7.6-2.debian.tar.xz d14845e8c8e0dba5f69ed13d9df9c40d 51406 x11 optional notification-daemon_0.7.6-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUQPnQAAoJEAvEfcZNE1MGFZsQAJ9X0EsTCAp+I4UlrVyfC7xa QzZ4gSU78QTC0/7dd7pZLzG+/sCZfKW2jEGPKUYduMzvS6WLjmdufLGAGvQIMgfq HMwx27p4xxhmPpzXjhyHalBtv6/0BDlXiSefi07+mjAJz0BykQL7oTXiq9GxSpS+ Xdd7tD45ww7BLKbLgwnkAlyYimgiMaSuNHie9m/T6wyR3
Bug#765160: marked as done (python-jingo: FTBFS: Tests failures)
Your message dated Fri, 17 Oct 2014 11:04:49 +
with message-id
and subject line Bug#765160: fixed in python-jingo 0.7-2
has caused the Debian Bug report #765160,
regarding python-jingo: FTBFS: Tests failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
765160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jingo
Version: 0.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> mod = load_module(part_fqname, fh, filename, desc)
> File "/«PKGBUILDDIR»/jingo/tests/test_monkey.py", line 9, in
> import jingo.monkey
> File "/«PKGBUILDDIR»/jingo/monkey.py", line 60, in
> class SafeStrAndUnicode(django.utils.encoding.StrAndUnicode):
> AttributeError: 'module' object has no attribute 'StrAndUnicode'
>
> ==
> ERROR: jingo.tests.test_views.test_template_substitution_crash
> --
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> File "/«PKGBUILDDIR»/jingo/tests/test_views.py", line 15, in
> test_template_substitution_crash
> translation.activate('xx')
> File
> "/usr/lib/python2.7/dist-packages/django/utils/translation/__init__.py", line
> 145, in activate
> return _trans.activate(language)
> File
> "/usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py",
> line 225, in activate
> _active.value = translation(language)
> File
> "/usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py",
> line 209, in translation
> default_translation = _fetch(settings.LANGUAGE_CODE)
> File
> "/usr/lib/python2.7/dist-packages/django/utils/translation/trans_real.py",
> line 189, in _fetch
> "The translation infrastructure cannot be initialized before the "
> AppRegistryNotReady: The translation infrastructure cannot be initialized
> before the apps registry is ready. Check that you don't make non-lazy gettext
> calls at import time.
>
> --
> Ran 24 tests in 0.275s
>
> FAILED (errors=9)
> make[1]: *** [override_dh_auto_test] Error 1
> debian/rules:24: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/10/12/python-jingo_0.7-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-jingo
Source-Version: 0.7-2
We believe that the bug you reported is fixed in the latest version of
python-jingo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand (supplier of updated python-jingo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 17 Oct 2014 08:08:54 +
Source: python-jingo
Binary: python-jingo python3-jingo python-jingo-doc
Architecture: source all
Version: 0.7-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack
Changed-By: Thomas Goirand
Description:
python-jingo - adapter for using Jinja2 templates with Django - Python 2.x
python-jingo-doc - adapter for using Jinja2 templates with Django - doc
python3-jingo - adapter for using Jinja2 templates with Django - Python 3.x
Closes: 765160
Changes:
python-jingo (0.7-2) unstable; urgency=medium
.
* Added fix-run_tests.py-with-django-1.7.patch (Closes: #765160).
* Added defines-own
Processed: severity of 765685 is important
Processing commands for cont...@bugs.debian.org: > severity 765685 important Bug #765685 [src:linux] linux-image-3.16-2-amd64: Kernel lockups with r8723au Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 765685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747465: NMU for #747465 and #693837?
intrigeri wrote (17 Oct 2014 10:34:42 GMT) :
> Control: tag -1 + patch
This time with the patch...
Index: debian/changelog
===
--- debian/changelog (revision 43628)
+++ debian/changelog (working copy)
@@ -1,3 +1,18 @@
+notification-daemon (0.7.6-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ intrigeri ]
+ * Fix_GSource_usage_with_recent_GLib.patch: new patch, from upstream
+Bugzilla (Closes: #747465).
+ * Fix_positioning_notifications_with_long_text.patch: new patch,
+from upstream Bugzilla (Closes: #693837).
+
+ [ Jeremy Bicha ]
+ * Use canonical Vcs-* fields.
+
+ -- intrigeri Thu, 09 Oct 2014 12:54:55 +0200
+
notification-daemon (0.7.6-1) unstable; urgency=low
* New upstream bugfix and translation release.
Index: debian/patches/Fix_GSource_usage_with_recent_GLib.patch
===
--- debian/patches/Fix_GSource_usage_with_recent_GLib.patch (revision 0)
+++ debian/patches/Fix_GSource_usage_with_recent_GLib.patch (working copy)
@@ -0,0 +1,51 @@
+From 7e458afddc7c57eba5c392a7a89990600a070ae5 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Ball=C3=B3=20Gy=C3=B6rgy?=
+Date: Wed, 8 Oct 2014 23:35:37 +0200
+Subject: [PATCH] Fix GSource usage with recent GLib
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=728157
+Bug-Debian: https://bugs.debian.org/747465
+Origin: https://bugzilla.gnome.org/attachment.cgi?id=288082
+
+---
+ src/nd-bubble.c | 1 +
+ src/nd-queue.c | 5 +
+ 2 files changed, 6 insertions(+)
+
+diff --git a/src/nd-bubble.c b/src/nd-bubble.c
+index 0587478..6de7f8f 100644
+--- a/src/nd-bubble.c
b/src/nd-bubble.c
+@@ -420,6 +420,7 @@ nd_bubble_enter_notify_event (GtkWidget*widget,
+ NdBubble *bubble = ND_BUBBLE (widget);
+ if (bubble->priv->timeout_id != 0) {
+ g_source_remove (bubble->priv->timeout_id);
++bubble->priv->timeout_id = 0;
+ }
+
+ return FALSE;
+diff --git a/src/nd-queue.c b/src/nd-queue.c
+index de73940..b744b88 100644
+--- a/src/nd-queue.c
b/src/nd-queue.c
+@@ -532,6 +532,10 @@ nd_queue_finalize (GObject *object)
+
+ g_return_if_fail (queue->priv != NULL);
+
++if (queue->priv->update_id != 0) {
++g_source_remove (queue->priv->update_id);
++}
++
+ g_hash_table_destroy (queue->priv->notifications);
+ g_queue_free (queue->priv->queue);
+
+@@ -919,6 +923,7 @@ update_idle (NdQueue *queue)
+ }
+ }
+
++queue->priv->update_id = 0;
+ return FALSE;
+ }
+
+--
+2.1.2
+
Index: debian/patches/Fix_positioning_notifications_with_long_text.patch
===
--- debian/patches/Fix_positioning_notifications_with_long_text.patch (revision 0)
+++ debian/patches/Fix_positioning_notifications_with_long_text.patch (working copy)
@@ -0,0 +1,130 @@
+From cef286903c24795e72cae8795c7b433b6baf9f57 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Ball=C3=B3=20Gy=C3=B6rgy?=
+Date: Wed, 8 Oct 2014 23:57:34 +0200
+Subject: [PATCH] Fix positioning notifications with long text
+Bug: https://bugzilla.gnome.org/show_bug.cgi?id=687724
+Bug-Debian: https://bugs.debian.org/693837
+Origin: https://bugzilla.gnome.org/attachment.cgi?id=288083
+
+---
+ src/nd-bubble.c | 13 +
+ src/nd-notification-box.c | 2 ++
+ src/nd-stack.c| 16
+ 3 files changed, 23 insertions(+), 8 deletions(-)
+
+diff --git a/src/nd-bubble.c b/src/nd-bubble.c
+index 0587478..2d36003 100644
+--- a/src/nd-bubble.c
b/src/nd-bubble.c
+@@ -413,6 +413,16 @@ nd_bubble_realize (GtkWidget *widget)
+ GTK_WIDGET_CLASS (nd_bubble_parent_class)->realize (widget);
+ }
+
++static void
++nd_bubble_get_preferred_width (GtkWidget *widget,
++ gint *min_width,
++ gint *nat_width)
++{
++if (nat_width != NULL) {
++ *nat_width = WIDTH;
++}
++}
++
+ static gboolean
+ nd_bubble_enter_notify_event (GtkWidget*widget,
+ GdkEventCrossing *event)
+@@ -450,6 +460,7 @@ nd_bubble_class_init (NdBubbleClass *klass)
+ widget_class->enter_notify_event = nd_bubble_enter_notify_event;
+ widget_class->leave_notify_event = nd_bubble_leave_notify_event;
+ widget_class->realize = nd_bubble_realize;
++widget_class->get_preferred_width = nd_bubble_get_preferred_width;
+
+ g_type_class_add_private (klass, sizeof (NdBubblePrivate));
+ }
+@@ -622,6 +633,7 @@ nd_bubble_init (NdBubble *bubble)
+ gtk_box_pack_start (GTK_BOX (vbox), bubble->priv->summary_label, TRUE, TRUE, 0);
+ gtk_misc_set_alignment (GTK_MISC (bubble->priv->summary_label), 0, 0);
+ gtk_label_set_line_wrap (GTK_LABEL (bubble->priv->summary_label), TRUE);
++gtk_label_set_line_wrap_mode
Bug#765685: linux-image-3.16-2-amd64: Kernel lockups with r8723au
Package: src:linux Version: 3.16.3-2 Severity: serious The staging driver r8723au is enabled in the kernel but there appear to be very good reasons why it's in staging - when it loads it routinely locks up my system (hard with no output unfortunately). It seems to make sense to disable the driver. -- Package-specific info: ** Version: Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64 root=UUID=1c8b372e-5478-46fe-84d9-efc496b4a0ce ro init=/bin/systemd quiet ** Tainted: WC (1536) * Taint on warning. * Module from drivers/staging has been loaded. ** Kernel log: [ 557.489458] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 557.489463] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 557.494527] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 557.494530] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 558.501325] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 558.501338] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 558.506380] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 558.506383] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 559.515171] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 559.515183] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 559.520204] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 559.520206] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 560.527936] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 560.527939] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 560.532991] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 560.532994] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 561.543521] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 561.543525] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 561.548556] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 561.548560] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 562.557183] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 562.557188] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 562.562215] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 562.562220] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 563.571309] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 563.571314] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 563.576374] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 563.576377] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 564.585412] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 564.585424] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 564.590447] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 564.590450] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 565.599700] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 565.599703] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 565.604736] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 565.604740] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 566.613028] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 566.613033] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 566.618109] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 566.618116] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 567.627585] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 567.627588] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 567.632636] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 567.632640] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 568.640977] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 568.640981] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 568.646030] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). [ 568.646034] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 569.656338] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). [ 569.656348] atkbd serio0: Use 'setkeycodes e03e ' to make it known. [ 569.661391] atkbd s
Bug#763169: marked as done (apt upgrade fails in postinst with "adduser: not found")
Your message dated Fri, 17 Oct 2014 12:35:35 +0200 with message-id <20141017103535.GB3846@crossbow> and subject line Re: Bug#763169: apt upgrade fails in postinst with "adduser: not found" has caused the Debian Bug report #763169, regarding apt upgrade fails in postinst with "adduser: not found" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 763169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.1~exp3 During upgrade: Setting up apt (1.1~exp3) ... /var/lib/dpkg/info/apt.postinst: 30: /var/lib/dpkg/info/apt.postinst: adduser: not found chown: invalid user: '_apt:root' dpkg: error processing package apt (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: apt E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up apt (1.1~exp3) ... /var/lib/dpkg/info/apt.postinst: 30: /var/lib/dpkg/info/apt.postinst: adduser: not found chown: invalid user: '_apt:root' dpkg: error processing package apt (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: apt --- End Message --- --- Begin Message --- Version: 1.1~exp4 Hi, On Sun, Sep 28, 2014 at 01:42:15PM +0200, Max Kellermann wrote: > During upgrade: > > Setting up apt (1.1~exp3) ... > /var/lib/dpkg/info/apt.postinst: 30: /var/lib/dpkg/info/apt.postinst: > adduser: not found > chown: invalid user: '_apt:root' > dpkg: error processing package apt (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > apt > E: Sub-process /usr/bin/dpkg returned an error code (1) > Failed to perform requested operation on package. Trying to recover: > Setting up apt (1.1~exp3) ... > /var/lib/dpkg/info/apt.postinst: 30: /var/lib/dpkg/info/apt.postinst: > adduser: not found > chown: invalid user: '_apt:root' > dpkg: error processing package apt (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > apt Thanks for the report (and thanks for testing experimental apt versions)! Around the same time we got another report about this, so this one was supposed to be merged, but ultimatively forgotten… I am therefore closing it now appropriately at least. The relevant changelog being: apt (1.1~exp4) experimental; urgency=medium […] * Add missing "adduser" dependency (for the new _apt user) Thanks to Russ Allbery (Closes: #763004) […] -- Michael Vogt Wed, 08 Oct 2014 09:37:35 +0200 Thanks again & best regards David Kalnischkies signature.asc Description: Digital signature --- End Message ---
Bug#747465: NMU for #747465 and #693837?
Control: tag -1 + patch Control: severity 747465 grave Hi, intrigeri wrote (10 Oct 2014 08:56:49 GMT) : > A patch was proposed upstream [1] and I've confirmed it fixes the > problem for me. I'm tempted to raise the severity to grave, and to > upload with that patch applied. Thoughts? Please find attached a diff against current Vcs-Svn, that imports the patches proposed on the upstream Bugzilla to fix #747465 and #693837. I've built the resulting source tree with svn-buildpackage, and successfully tested on current sid. Should I go ahead and NMU? (I realize that no upstream developer has ACK'd these patches yet, so it would be great if someone who's C-literate could take a look first.) Also raising severity of #747465, as proposed in June and a week ago. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: NMU for #747465 and #693837?
Processing control commands: > tag -1 + patch Bug #693837 [notification-daemon] notification-daemon: Bad position for the warning, fallback mode notification, and others Bug #684474 [notification-daemon] notification-daemon: Bad position for the warning, fallback mode notification, and others Added tag(s) patch. Added tag(s) patch. > severity 747465 grave Bug #747465 [notification-daemon] notification-daemon crashes Severity set to 'grave' from 'important' -- 684474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684474 693837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693837 747465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: NMU for #747465 and #693837?
Processing control commands: > tag -1 + patch Bug #747465 [notification-daemon] notification-daemon crashes Added tag(s) patch. > severity 747465 grave Bug #747465 [notification-daemon] notification-daemon crashes Ignoring request to change severity of Bug 747465 to the same value. -- 747465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765458: apt: broken cdrom support, breaking installation from weekly ISO images
On Fri, Oct 17, 2014 at 11:28:12AM +0200, Cyril Brulebois wrote: > Cyril Brulebois (2014-10-16): > > I'm tempted to make apt migrate to testing soon, possibly today, because > > bug reports are piling up. From your maintainer point of view, is there > > anything speaking against such a move? > > Having received no negative feedback, I did that yesterday and fixed apt > is now in testing. I've also started a rebuild of the weekly images[1], > and images dated 2014-10-17 should have a fixed apt. I was about to answer that from our side of the fence we see no problem with quick-aging (okay, its a bit misfortune that now buildprofiles in apt are changed before dpkg, but the drivers response to an earlier inquiry on compatibility requirements was: no need, so I am sure they will manage just fine as this was bound to happen one way or another anyway). Thanks for testing & hinting and until next time in apt-cdrom bugland ;) Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#765681: libqtgui4-perl: QtGui4 module cannot be imported
Package: libqtgui4-perl Version: 4.8.4-1.1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, The QtGui4 Perl module cannot be used since merely loading it raises an error: Code: use QtCore4; use QtGui4; Result: defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1420. (Maybe you should just omit the defined()?) defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1421. (Maybe you should just omit the defined()?) defined(@array) is deprecated at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtCore4.pm line 1422. (Maybe you should just omit the defined()?) "SvREFCNT_inc" is not exported by the Devel::Peek module Can't continue after import errors at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtGui4.pm line 25. BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/perl5/5.20/QtGui4.pm line 25. Compilation failed in require at /tmp/qt.pl line 2. BEGIN failed--compilation aborted at /tmp/qt.pl line 2. Thanks, Alberto -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libqtgui4-perl depends on: ii libc6 2.19-11 ii libgcc1 1:4.9.1-16 ii libperl5.20 5.20.1-1 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4-perl 4.8.4-1.1+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libsmokebase3 4:4.14.0-2 ii libsmokeqtcore4-3 4:4.12.2-2 ii libsmokeqtgui4-34:4.12.2-2 ii libsmokeqtnetwork4-34:4.12.2-2 ii libstdc++6 4.9.1-16 ii perl5.20.1-1 ii perl-base [perlapi-5.20.0] 5.20.1-1 libqtgui4-perl recommends no packages. libqtgui4-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765371: marked as done (Import fails - error parsing version (fixed upstream))
Your message dated Fri, 17 Oct 2014 10:00:32 +
with message-id
and subject line Bug#765371: fixed in owfs 2.9p7-1
has caused the Debian Bug report #765371,
regarding Import fails - error parsing version (fixed upstream)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
765371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-ow
Version: 2.9p5-1
Severity: grave
Trying to import ow results in
pietro@debiousci:~$ python -c "import ow"
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/ow/__init__.py", line 37, in
__version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ]
IndexError: list index out of range
The line which gives an error... couldn't really do otherwise. The problem
comes from the fact that while in previous upstream versions that line looked
like
__version__ = _OW.version( ) + '-%s' % '$Id: __init__.py,v 1.19 2013/03/24
01:23:30 alfille Exp $'.split( )[ 2 ]
, this was changed probably through an automatic replacement which broke
owpython in version 2.9p5.
The same applies to ownet. Attached is a patch which fixes both.
Notice that both are also fixed upstream in version 2.9p7 (exactly in the same
way as my patch). So the optimal fix would be to simply package it. But if
this can't be done in reasonable time, I could (push 2.9p5-1.1 to
collab-maint, and) try to get a new NMU sponsored with my simple patch applied.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (600, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages python-ow depends on:
ii libc62.19-11
ii libow-2.9-5 2.9p5-1.1
ii python 2.7.8-1
python-ow recommends no packages.
python-ow suggests no packages.
-- no debconf information
commit 64222f5788c664c15bb0f980ed170be1405c308c
Author: Pietro Battiston
Date: Tue Oct 14 14:32:29 2014 +0200
Only return the OW version
diff --git a/debian/patches/only-return-the-OW-version.patch b/debian/patches/only-return-the-OW-version.patch
new file mode 100644
index 000..3c040be
--- /dev/null
+++ b/debian/patches/only-return-the-OW-version.patch
@@ -0,0 +1,25 @@
+From: Pietro Battiston
+Date: Tue, 14 Oct 2014 14:29:13 +0200
+Subject: Only return the OW version.
+
+The python files are currently installed without replacing some
+placeholders such as "$Id$". As a consequence, the parsing ("split()")
+of the version number fails. This horrible hack simply disables it,
+until the real fix is implemented.
+---
+ module/swig/python/ow/__init__.py | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/module/swig/python/ow/__init__.py b/module/swig/python/ow/__init__.py
+index 0ed9dfd..84bc115 100644
+--- a/module/swig/python/ow/__init__.py
b/module/swig/python/ow/__init__.py
+@@ -34,7 +34,7 @@ from ow import _OW
+
+ __author__ = 'Peter Kropf'
+ __email__ = 'pkr...@gmail.com'
+-__version__ = _OW.version( ) + '-%s' % '$Id$'.split( )[ 2 ]
++__version__ = _OW.version( )
+
+
+ #
diff --git a/debian/patches/series b/debian/patches/series
index 494f101..f0fe969 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -7,3 +7,4 @@ deb-specific_python-install.patch
deb_specific__owfs-use-config.patch
for-upstream_fix-ABI.patch
for-upstream_owexist-manpage.patch
+only-return-the-OW-version.patch
--- End Message ---
--- Begin Message ---
Source: owfs
Source-Version: 2.9p7-1
We believe that the bug you reported is fixed in the latest version of
owfs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 765...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Danjean (supplier of updated owfs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 14 Oct 2014 18:57:13 +0200
Source: owfs
Binary: owfs-common owfs libow-2.9-7 libowcapi-2.9-7 libow-dev l
Bug#765678: ruby-rack: FTBFS - rake aborted!
Package: ruby-rack Version: 1.5.2-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] Entering dh_ruby --install Rewriting shebang line of /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack/usr/bin/rackup Running tests for ruby2.1 using debian/ruby-tests.rake ... /usr/bin/ruby2.1 /usr/bin/bacon -I./lib:./test -w -a -q -t '^(?!Rack::Adapter|Rack::Session::Memcache|Rack::Server|Rack::Handler)' /usr/lib/ruby/vendor_ruby/bacon.rb:221: warning: shadowing outer local variable - args /usr/lib/ruby/vendor_ruby/memcache.rb:303: warning: assigned but unused variable - key_count /usr/lib/ruby/vendor_ruby/memcache.rb:812: warning: assigned but unused variable - key /usr/lib/ruby/vendor_ruby/memcache.rb:24: warning: assigned but unused variable - e /usr/lib/ruby/vendor_ruby/continuum_native.rb:38: warning: assigned but unused variable - e /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in `': uninitialized constant Rack::Handler::WEBrick (NameError) from /usr/bin/bacon:116:in `load' from /usr/bin/bacon:116:in `block in ' from /usr/bin/bacon:115:in `each' from /usr/bin/bacon:115:in `' /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/test/spec_webrick.rb:6:in `': uninitialized constant Rack::Handler::WEBrick (NameError) from /usr/bin/bacon:116:in `load' from /usr/bin/bacon:116:in `block in ' from /usr/bin/bacon:115:in `each' from /usr/bin/bacon:115:in `' . Finished in 0.339649703 seconds. 217 tests, 722 assertions, 0 failures, 0 errors rake aborted! Command failed with status (1): [/usr/bin/ruby2.1 /usr/bin/bacon -I./lib:./...] /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-tests.rake:6:in `block in ' -e:1:in `' Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby2.1" failed. Exiting. dh_auto_install: dh_ruby --install /srv/jenkins-slave/workspace/sid-goto-cc-ruby-rack/ruby-rack-1.5.2/debian/ruby-rack returned exit code 1 debian/rules:15: recipe for target 'binary' failed make: *** [binary] Error 1 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael ruby-rack-build-log.txt.gz Description: application/gunzip pgphIUGXnft6K.pgp Description: PGP signature
Bug#765460: gnome-shell-extensions: apps-menu extension not working after upgrade to 3.14
Control: tag -1 + patch
Hi,
ricky wrote (15 Oct 2014 10:13:17 GMT) :
> I understood that the extension did not work because the GMenu package was
> missing.
> As soon as I installed the following package:
> # apt-get install gir1.2-gmenu-3.0
> The shell loaded the extension correctly. I suppose that some dependency is
> broken (I
> do not know what was the status of this package before the upgrade).
Confirmed the bug and the proposed fix on current sid.
The attached patch fixes this bug for me.
Should I NMU?
Cheers!
Index: debian/changelog
===
--- debian/changelog (revision 43628)
+++ debian/changelog (working copy)
@@ -1,3 +1,11 @@
+gnome-shell-extensions (3.14.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add dependency on gir1.2-gmenu-3.0, so that the apps-menu extension
+can work (Closes: #765460).
+
+ -- intrigeri Fri, 17 Oct 2014 11:45:18 +0200
+
gnome-shell-extensions (3.14.0-2) unstable; urgency=medium
* Drop xrandr from EXTENSIONS_DISABLED, this extension was removed
Index: debian/control
===
--- debian/control (revision 43628)
+++ debian/control (working copy)
@@ -25,6 +25,7 @@
Depends: ${misc:Depends},
gnome-shell (>= ${gnome:Version}),
gnome-shell (<< ${gnome:NextVersion}),
+ gir1.2-gmenu-3.0,
gir1.2-gtop-2.0,
gvfs (>= 1.16.0),
gnome-session (>= 3.8)
Index: debian/control.in
===
--- debian/control.in (revision 43628)
+++ debian/control.in (working copy)
@@ -21,6 +21,7 @@
Depends: ${misc:Depends},
gnome-shell (>= ${gnome:Version}),
gnome-shell (<< ${gnome:NextVersion}),
+ gir1.2-gmenu-3.0,
gir1.2-gtop-2.0,
gvfs (>= 1.16.0),
gnome-session (>= 3.8)
Processed: Re: Bug#765460: gnome-shell-extensions: apps-menu extension not working after upgrade to 3.14
Processing control commands: > tag -1 + patch Bug #765460 [gnome-shell-extensions] gnome-shell-extensions: apps-menu extension not working after upgrade to 3.14 Added tag(s) patch. -- 765460: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765677: taskcoach: FTBFS - missing build dependency on cpio
Package: taskcoach Version: 1.4.1-3 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] debian/rules override_dh_auto_build make[2]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-taskcoach/taskcoach-1.4.1' python changes.in/make.py text > CHANGES.txt gm convert -resize 32x32 icons.in/taskcoach.png icons.in/taskcoach.xpm dh_auto_build --buildsystem=makefile -- prepare make[3]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-taskcoach/taskcoach-1.4.1' cd thirdparty; tar xzf desktop-0.4.2.tar.gz --strip-components=1 -C ../taskcoachlib/thirdparty desktop-0.4.2/desktop cp /usr/share/pyshared/lockfile.py taskcoachlib/thirdparty cd /usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/lib/pubsub taskcoachlib/thirdparty; \ find . \! -name "*.pyc" -print0 \ | cpio -pmd0 /srv/jenkins-slave/workspace/sid-goto-cc-taskcoach/taskcoach-1.4.1/taskcoachlib/thirdparty/pubsub /bin/sh: 3: cpio: not found Makefile:181: recipe for target 'thirdpartymodules' failed make[3]: *** [thirdpartymodules] Error 127 The full build log is attached; please do let me know if the problem is unreproducible, in which case I shall try to investigate further. Best, Michael taskcoach-build-log.txt.gz Description: application/gunzip pgpOBBzboM7oJ.pgp Description: PGP signature
debian-bugs-rc@lists.debian.org
Your message dated Fri, 17 Oct 2014 09:41:45 + with message-id and subject line Bug#762796: fixed in munin 2.0.23-1 has caused the Debian Bug report #762796, regarding munin: Undefined subroutine &main::header to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762796 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: munin Version: 2.0.21-2 Severity: important Dear Maintainer, Since the last upgrade, the web interface of Munin does not work any more. The following error message appears on the homepage: Undefined subroutine &main::header called at /usr/lib/munin/cgi/munin-cgi-html line 54. Kind regards, Sébastien -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (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 Versions of packages munin depends on: ii cron 3.0pl1-124.2 ii fonts-dejavu 2.34-1 ii libdate-manip-perl 6.47-1 pn libdigest-md5-perl ii libfile-copy-recursive-perl 0.38-1 ii libhtml-template-perl2.95-1 ii libio-socket-inet6-perl 2.72-1 ii liblog-log4perl-perl 1.44-1 ii librrds-perl 1.4.8-1.1+b1 pn libstorable-perl ii liburi-perl 1.64-1 ii munin-common 2.0.21-2 ii perl [libtime-hires-perl]5.20.0-6 ii perl-modules 5.20.0-6 ii rrdtool 1.4.8-1.1+b1 Versions of packages munin recommends: ii libcgi-fast-perl 1:2.02-1 ii munin-doc 2.0.21-2 ii munin-node2.0.21-2 Versions of packages munin suggests: ii apache2-bin [httpd] 2.4.10-1+b1 ii elinks [www-browser]0.12~pre6-5+b1 ii libapache2-mod-fcgid1:2.3.9-1 ii libnet-ssleay-perl 1.65-1+b1 ii lynx-cur [www-browser] 2.8.9dev1-2 ii w3m [www-browser] 0.5.3-17 -- Configuration Files: /etc/munin/apache.conf [not included] /etc/munin/apache24.conf [not included] /etc/munin/munin.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: munin Source-Version: 2.0.23-1 We believe that the bug you reported is fixed in the latest version of munin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Levsen (supplier of updated munin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Oct 2014 11:09:40 +0200 Source: munin Binary: munin-node munin-plugins-core munin-plugins-extra munin-plugins-java munin munin-common munin-async munin-doc Architecture: source all Version: 2.0.23-1 Distribution: unstable Urgency: medium Maintainer: Munin Debian Maintainers Changed-By: Holger Levsen Description: munin - network-wide graphing framework (grapher/gatherer) munin-async - network-wide graphing framework (async master/client) munin-common - network-wide graphing framework (common) munin-doc - network-wide graphing framework (documentation) munin-node - network-wide graphing framework (node) munin-plugins-core - network-wide graphing framework (plugins for node) munin-plugins-extra - network-wide graphing framework (user contributed plugins for nod munin-plugins-java - network-wide graphing framework (java plugins for node) Closes: 762796 Changes: munin (2.0.23-1) unstable; urgency=medium . * New upstream release. This time including commit 9fabbe7 which is the bugfix for Perl 5.20 and CGI. (Closes: #762796) Checksums-Sha1: 240c96b63a11f12aef8e9e4e80eccbfda4654404 2425 munin_2.0.23-1.dsc d6f8aceedb6ba27c94517c456190c9ccf72f5292 1337241 munin_2.0.23.orig.tar.gz 52d776720047c94358db32a6e13853820f142e97 60816 munin_2.0.23-1.debian.tar.xz 36d412cc3641a71e19eaad7ae163a3ad4ea1842b 130624 munin-node_2.0.23-1_all.deb 16975151afac2320d8edc38095f4bfe05a68627b 241292 munin-plugins-core_2.0.23-1_all.deb 7713c469d65ce9319d04ab75fade3f9bc8b17a7c 14
Processed: Bugs #764318 and #765667 are not fixed yet.
Processing commands for cont...@bugs.debian.org:
> forcemerge 764318 765667
Bug #764318 {Done: Bill Allombert } [libjpeg-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #765667 {Done: Bill Allombert } [libjpeg-progs]
[libjpeg-progs] Conflicts with libjpeg-turbo-progs
Marked as found in versions libjpeg9/1:9a-2.
Bug #764318 {Done: Bill Allombert } [libjpeg-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Marked as found in versions libjpeg-turbo/1:1.3.1-3.
Merged 764318 765667
> reopen 764318
Bug #764318 {Done: Bill Allombert } [libjpeg-progs]
libjpeg-progs: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', also in
libjpeg-turbo-progs
Bug #765667 {Done: Bill Allombert } [libjpeg-progs]
[libjpeg-progs] Conflicts with libjpeg-turbo-progs
Bug reopened
Ignoring request to alter fixed versions of bug #764318 to the same values
previously set
Ignoring request to alter fixed versions of bug #765667 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
764318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764318
765667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: affects 765668
Processing commands for cont...@bugs.debian.org: > affects 765668 cups Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Bug #765434 [dpkg] man-db install-triggers broken Added indication that 765668 affects cups Added indication that 765434 affects cups > thanks Stopping processing here. Please contact me if you need assistance. -- 765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434 765668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764318: Bugs #764318 and #765667 are not fixed yet.
forcemerge 764318 765667 reopen 764318 thanks Hello Bill. I'm running jessie on a computer lab, and I found this today in the logs for unattended-upgrades: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg.1.gz', que está también en el paquete [ Translation: Trying to overwrite [...] which is also in package [...]] libjpeg-turbo-progs 1:1.3.1-3 Processing triggers for man-db (2.7.0.2-1) ... Se encontraron errores al procesar: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb I admit that I had one of those packages in hold until the issue with the different implementations was sorted out, but in either case we should not only support upgrades from wheezy to jessie but also upgrades from the jessie of last week to the jessie of today, whenever such thing is feasible, which of course it is in this case. Please use versioned Conflicts/Replaces or whatever is appropriate so that apt-get never tries to unpack a package over another one if there is a conflict. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765458: apt: broken cdrom support, breaking installation from weekly ISO images
Cyril Brulebois (2014-10-16): > I've tweaked bits and pieces locally to use apt 1.0.9.3 at the > appropriate time and I can confirm that the easy/usual one-CD case is > fixed, thanks! It'd be nice to see what happens with several CDs but > that's not going to be me today. > > > Some notes: > - apt.git is missing at least one commit and the tag. > - I think you wanted to close #764442, rather than #76442. > > I'm tempted to make apt migrate to testing soon, possibly today, because > bug reports are piling up. From your maintainer point of view, is there > anything speaking against such a move? Having received no negative feedback, I did that yesterday and fixed apt is now in testing. I've also started a rebuild of the weekly images[1], and images dated 2014-10-17 should have a fixed apt. 1. http://cdimage.debian.org/cdimage/weekly-builds/ Right now I've confirmed this with the i386 netinst CD. All of amd64, i386, and multi-arch have been rebuilt already. I'm therefore adding all blocked bug reports and their submitters to the loop to let them know. Users: please send follow-ups to your individual report (nnn...@bugs.debian.org). If I get no negative feedback in the upcoming days I'll probably mass-close those reports. Mraw, KiBi. signature.asc Description: Digital signature
Processed: reassign 765668 to dpkg, forcibly merging 765434 765668, severity of 765668 is serious
Processing commands for cont...@bugs.debian.org: > reassign 765668 dpkg Bug #765668 [cups] cups: dpkg: cycle found while processing triggers: Bug reassigned from package 'cups' to 'dpkg'. No longer marked as found in versions cups/1.7.5-4. Ignoring request to alter fixed versions of bug #765668 to the same values previously set > forcemerge 765434 765668 Bug #765434 [dpkg] man-db install-triggers broken Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Added tag(s) sid and jessie. Merged 765434 765668 > severity 765668 serious Bug #765668 [dpkg] cups: dpkg: cycle found while processing triggers: Bug #765434 [dpkg] man-db install-triggers broken Ignoring request to change severity of Bug 765668 to the same value. Ignoring request to change severity of Bug 765434 to the same value. > thanks Stopping processing here. Please contact me if you need assistance. -- 765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434 765668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765668: cups: dpkg: cycle found while processing triggers:
Control: forcemerge 765434 -1 Hi Thorsten, Le vendredi, 17 octobre 2014 10.14:52, vous avez écrit : > I’ve been having dpkg messages about cycles in triggers for a while > recently, but they all involved multiple packages (mostly cups, > postgresql, man-db) and were resolved just configuring the packages > again. > > Today is different: > (…) Yet nothing has changed in the CUPS triggers handling in a long time; I think this is #765434 , hereby force-merging. dpkg maintainers: if there's something fishy in CUPS, please un-merge an reassign, but this has worked for a long time without changes. Cheers OdyX -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#765668: cups: dpkg: cycle found while processing triggers:
Processing control commands: > forcemerge 765434 -1 Bug #765434 [dpkg] man-db install-triggers broken Unable to merge bugs because: package of #765668 is 'cups' not 'dpkg' Failed to forcibly merge 765434: Did not alter merged bugs -- 765434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765434 765668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765671: serf: FTBFS - TypeError: Directory /usr/include/mit-krb5 found where file expected.
Package: serf
Version: 1.3.7-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
dh_testdir
scons GSSAPI=/usr CFLAGS="-g -O2 -fstack-protector-strong -Wformat
-Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2" LINKFLAGS="-Wl,-z,relro
-Wl,-z,defs -Wl,--as-needed"
scons: Reading SConscript files ...
TypeError: Directory /usr/include/mit-krb5 found where file expected.:
File "/srv/jenkins-slave/workspace/sid-goto-cc-serf/serf-1.3.7/SConstruct",
line 360:
env.ParseConfig('$GSSAPI --cflags gssapi')
File "/usr/lib/scons/SCons/Environment.py", line 1555:
return function(self, self.backtick(command))
File "/usr/lib/scons/SCons/Environment.py", line 1550:
return env.MergeFlags(cmd, unique)
File "/usr/lib/scons/SCons/Environment.py", line 814:
args = self.ParseFlags(args)
File "/usr/lib/scons/SCons/Environment.py", line 800:
do_parse(arg)
File "/usr/lib/scons/SCons/Environment.py", line 730:
dict['LIBS'].append(self.fs.File(arg))
File "/usr/lib/scons/SCons/Node/FS.py", line 1340:
return self._lookup(name, directory, File, create)
File "/usr/lib/scons/SCons/Node/FS.py", line 1319:
return root._lookup_abs(p, fsclass, create)
File "/usr/lib/scons/SCons/Node/FS.py", line 2216:
result.diskcheck_match()
File "/usr/lib/scons/SCons/Node/FS.py", line 2362:
"Directory %s found where file expected.")
File "/usr/lib/scons/SCons/Node/FS.py", line 385:
return self.func(*args, **kw)
File "/usr/lib/scons/SCons/Node/FS.py", line 406:
raise TypeError(errorfmt % node.abspath)
debian/rules:26: recipe for target 'debian/stamp-build' failed
make: *** [debian/stamp-build] Error 2
The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further. It seems,
however, that the s390 build fails with exactly the same error.
Best,
Michael
serf-build-log.txt.gz
Description: application/gunzip
pgpnm0ahZAH9C.pgp
Description: PGP signature
Processed: forcibly merging 764180 765659
Processing commands for cont...@bugs.debian.org:
> forcemerge 764180 765659
Bug #764180 {Done: Michael Gilbert } [chromium]
/etc/default/chromium removed in postinst
Bug #764270 {Done: Michael Gilbert } [chromium] dpkg:
warning: unable to delete old directory '/etc/chromium': Directory
Bug #765659 [chromium] /etc/default/chromium removed in postinst
Marked Bug as done
Marked as fixed in versions chromium-browser/38.0.2125.101-1.
Marked as found in versions chromium-browser/37.0.2062.120-4.
Bug #764270 {Done: Michael Gilbert } [chromium] dpkg:
warning: unable to delete old directory '/etc/chromium': Directory
Merged 764180 764270 765659
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
764180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764180
764270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764270
765659: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765667: marked as done ([libjpeg-progs] Conflicts with libjpeg-turbo-progs)
Your message dated Fri, 17 Oct 2014 10:23:59 +0200 with message-id <20141017082359.GA663@yellowpig> and subject line Re: Bug#765667: [libjpeg-progs] Conflicts with libjpeg-turbo-progs has caused the Debian Bug report #765667, regarding [libjpeg-progs] Conflicts with libjpeg-turbo-progs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjpeg-progs Version: 1:1.3.1-3 Severity: grave Dear maintainer, This packages conflicts with libjpeg-turbo-progs: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3 Processing triggers for debian-security-support (2014.09.07) ... Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- System information. --- Architecture: amd64 Kernel: Linux 3.17.0 Debian Release: jessie/sid 500 testing ftp.debian.org 500 stable security.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== libc6 (>= 2.7) | 2.19-11 libjpeg8(>= 8c) | 8d1-1 Package's Recommends field is empty. Package's Suggests field is empty. -- Manolo Díaz --- End Message --- --- Begin Message --- On Fri, Oct 17, 2014 at 10:09:26AM +0200, Manolo Díaz wrote: > Package: libjpeg-progs > Version: 1:1.3.1-3 > Severity: grave > > Dear maintainer, > > This packages conflicts with libjpeg-turbo-progs: > > Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... > dpkg: error processing archive > /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): > trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in > package libjpeg-turbo-progs 1:1.3.1-3 > Processing triggers for debian-security-support (2014.09.07) ... > Processing triggers for man-db (2.7.0.2-1) ... > Errors were encountered while processing: > /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Hello Manolo, This problem is fixed in libjpeg-turbo-progs 1:1.3.1-6, see bug #764318 Cheers -- Bill. Imagine a large red swirl here. --- End Message ---
Processed: tagging 765085, tagging 726500, severity of 765109 is important
Processing commands for cont...@bugs.debian.org: > tags 765085 + pending Bug #765085 [nvidia-support] nvidia-support: [INTL:nl] Dutch translation of debconf messages Added tag(s) pending. > tags 726500 + wontfix Bug #726500 [fglrx-legacy-driver] fglrx-legacy-driver: does not support Xorg Xserver 1.13 or later Added tag(s) wontfix. > severity 765109 important Bug #765109 [fglrx-driver] fglrx-driver: Black screen after xorg startup Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 726500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726500 765085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765085 765109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765670: boinc: not binNMU safe
Source: boinc Version: 7.4.22+dfsg-3 Severity: serious Your package is not binNMU safe: boinc-app-seti build-depends on: - boinc-dev (>= 7.1.21+dfsg) | libboinc-app-dev (>= 7.1.21+dfsg) boinc-dev depends on: - libboinc-app-dev (= 7.4.22+dfsg-3) boinc-app-seti build-depends on: - boinc-dev (>= 7.1.21+dfsg) | libboinc-app-dev (>= 7.1.21+dfsg) libboinc-app-dev depends on missing: - libboinc-app7 (< 7.4.22+dfsg-3+1~) This is preventing some packages from being built. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765669: avifile: not binNMU safe
Source: avifile Version: 1:0.7.48~20090503.ds-16 Severity: serious Your package is still not binNMU safe: onscripter build-depends on: - libavifile-0.7-dev libavifile-0.7-dev depends on: - libavifile-0.7c2 (= 1:0.7.48~20090503.ds-16+b2) libavifile-0.7c2 depends on missing: - libavifile-0.7-common (= 1:0.7.48~20090503.ds-16+b2) This is making various packages unbuildable (e.g. onscripter or vxl). Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750719: Processed: severity of 750719 is serious
Hi Tonnerre, Quoting Tonnerre LOMBARD (2014-10-17 02:19:03) > On Thu, Oct 16, 2014 at 04:54:19PM +, Debian Bug Tracking System wrote: > > Bug #750719 [src:sockjs-client] sockjs-client: FTBFS against uglify > > 2.x series - Cannot call method 'parse' of undefined Severity set to > > 'serious' from 'important' > > FYI, the patch has been waiting for someone to upload it for a while: > https://qa.debian.org/cgi-bin/vcswatch?package=sockjs-client Great! I recommend that you add a tag to signal that more clearly (e.g. to attract fly-by bug-squashers seeking easy tasks for NMUs): https://www.debian.org/Bugs/Developer#tags > I would appreciate if this could be taken care of. I notice that you are maintaining this package on your own. That's perfectly ok if that is what you prefer, but you might consider moving it to team-maintenance at the Javascript team (where you are already a member). It seems from above you do not have upload rights yourself, and I believe it is easier to finalize packaging work in teams than as "lonely rider" relying on sponsors. I also notice that you use short-form dh sequencer in the packaging. Again, it is perfectly ok - but I solely use CDBS for the 400+ packages I am involved in, and am not confident enough in that to help you out (and also as a principle - nothing personal! - I don't do sponsoring for lonely riders, I only help do teamwork). Hope that helps, - 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#765668: cups: dpkg: cycle found while processing triggers:
Package: cups Version: 1.7.5-4 Severity: serious Justification: fails to install Hi, I’ve been having dpkg messages about cycles in triggers for a while recently, but they all involved multiple packages (mostly cups, postgresql, man-db) and were resolved just configuring the packages again. Today is different: 1|root@tglase:~ # dpkg -a --configure Setting up libc-bin (2.19-11) ... dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: cups -> cups packages' pending triggers which are or may be unresolvable: cups: /usr/share/cups/ppd-updaters dpkg: error processing package cups (--configure): triggers looping, abandoned Errors were encountered while processing: cups This repeated for several times, only the fourth repeated call to “dpkg -a --configure” gave: 1|root@tglase:~ # dpkg -a --configure Setting up cups (1.7.5-4) ... Updating PPD files for cups ... Updating PPD files for openprinting-ppds ... So I guess there may be something wrong with the cups package. Feel free to reassign to some other package if the bug is not with cups, or something. -- System Information: Debian Release: jessie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: x32 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Versions of packages cups depends on: ii cups-client1.7.5-4 ii cups-common1.7.5-4 ii cups-core-drivers 1.7.5-4 ii cups-daemon1.7.5-4 ii cups-filters 1.0.61-2 ii cups-ppdc 1.7.5-4 ii cups-server-common 1.7.5-4 ii debconf [debconf-2.0] 1.5.53 ii ghostscript9.06~dfsg-1 ii libavahi-client3 0.6.31-4 ii libavahi-common3 0.6.31-4 ii libc-bin 2.19-11 ii libc6 2.19-11 ii libcups2 1.7.5-4 ii libcupscgi11.7.5-4 ii libcupsimage2 1.7.5-4 ii libcupsmime1 1.7.5-4 ii libcupsppdc1 1.7.5-4 ii libgcc11:4.9.1-17 ii libstdc++6 4.9.1-17 ii libusb-1.0-0 2:1.0.19-1 ii lsb-base 4.1+Debian13 ii poppler-utils 0.26.5-1 ii procps 2:3.3.9-8 Versions of packages cups recommends: ii avahi-daemon 0.6.31-4 pn colord ii cups-filters [ghostscript-cups] 1.0.61-2 pn printer-driver-gutenprint Versions of packages cups suggests: ii cups-bsd 1.7.5-4 pn cups-pdf pn foomatic-db-compressed-ppds | foomatic-db pn hplip pn printer-driver-hpcups pn smbclient ii udev 215-5+b1 -- debconf information: * cupsys/raw-print: true * cupsys/backend: lpd, socket -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765667: [libjpeg-progs] Conflicts with libjpeg-turbo-progs
Package: libjpeg-progs Version: 1:1.3.1-3 Severity: grave Dear maintainer, This packages conflicts with libjpeg-turbo-progs: Unpacking libjpeg-progs (1:9a-2) over (1:1.3.1-3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1:1.3.1-3 Processing triggers for debian-security-support (2014.09.07) ... Processing triggers for man-db (2.7.0.2-1) ... Errors were encountered while processing: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- System information. --- Architecture: amd64 Kernel: Linux 3.17.0 Debian Release: jessie/sid 500 testing ftp.debian.org 500 stable security.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== libc6 (>= 2.7) | 2.19-11 libjpeg8(>= 8c) | 8d1-1 Package's Recommends field is empty. Package's Suggests field is empty. -- Manolo Díaz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#765665: missing license in debian/copyright
Package: owfs Version: 2.9p7-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of: module/swig/perl5/OW/* to debian/copyright. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736066: multiple security issues discovered in encfs
Package: encfs Version: 1.7.4-4.1 Followup-For: Bug #736066 While the security message itself is mostly-OK, could you please make sure it's displayed _once_? As it is, it's shown once before installing/updating the package, and another time during the actual installation. That's annoying; besides, I'd like to come back after triggering a dist-upgrade and _not_ see the process stuck 10% through, waiting for an OK I already gave. :-/ -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
