Bug#735254: flash-kernel: QNAP TS-212 doesn't boot with 3.12-1-kirkwood and flash-kernel 3.12
Control: reassign -1 src:linux Control: forcemerge 735172 -1 On Tue, 2014-01-14 at 05:50 +, Ruben Silveira wrote: Description and steps to reproduce: - QNAP TS-212 (cpuinfo = 'QNAP TS-119/TS-219') with 3.11-2-kirkwood and flash-kernel 3.12; - Installed 3.12-1-kirkwood (update-initramfs and flash-kernel executed automatically and normally); - Rebooted; - System not up; - Connected serial console; - Rebooted; - System hangs just after kernel being (successfully) loaded by U-Boot, with no output whatsoever. You see Uncompressing Linux... done, booting the kernel. as the last thing, right? I was able to restore an old backup (flash and rootfs), repeat the whole process and get to the same exact result. I suppose this has to do with DT - Device Tree and could be (loosely) related to bugs #731345 and #734769. Actually AFAICT this is #735172 which is a kernel bug unrelated to the recent flash-kernel changes, reassigning and merging. The solution appears to be the appendage of DTB to the kernel, but I have little to no knowledge in patching flash-kernel to get to a working solution. This issue is being observed even on platforms which have no DTB support yet (e.g. TS-419). Have you actually tried with an appended DTB and seen it work or are you speculating? Thanks, Ian. signature.asc Description: This is a digitally signed message part
Processed (with 1 errors): Re: Bug#735254: flash-kernel: QNAP TS-212 doesn't boot with 3.12-1-kirkwood and flash-kernel 3.12
Processing control commands:
reassign -1 src:linux
Bug #735254 [flash-kernel] flash-kernel: QNAP TS-212 doesn't boot with
3.12-1-kirkwood and flash-kernel 3.12
Bug reassigned from package 'flash-kernel' to 'src:linux'.
No longer marked as found in versions flash-kernel/3.12.
Ignoring request to alter fixed versions of bug #735254 to the same values
previously set
forcemerge 735172 -1
Bug #735172 [linux] linux: Upgrade to linux-image-3.12-1-kirkwood prevents QNAP
TS-119 from booting
Unable to merge bugs because:
package of #735254 is 'src:linux' not 'linux'
Failed to forcibly merge 735172: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2ccd508)',
'requester', 'Ian Campbell i...@hellion.org.uk', 'request_addr',
'735254-sub...@bugs.debian.org', 'request_msgid',
'1389688601.10695.21.ca...@dagon.hellion.org.uk', 'request_subject', ...)
called at /usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', 'forcemerge 735172 -1',
'clonebugs', 'HASH(0x2ce4af8)', 'limit', 'HASH(0x2ce4d20)',
'common_control_options', 'ARRAY(0x2ce4df8)', 'errors', ...) called at
/usr/lib/debbugs/process line 1039
--
735172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735172
735254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735254
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#735261: kmail2 randomly marks read messages as unread
Package: kmail Version: 4:4.11.3-1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, KMail randomly marks single messages as unread. This makes my normal workflow, where I leave messages unread for later, deeper consideration, tedious and bordering on impossible. KMail also randomly creates new duplicates of old messages, which are (of course) also marked unread. After an safe-update which included Akonadi, I found duplicates for 400 such messages. Losing read status is data loss. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kmail depends on: ii kde-runtime 4:4.11.3-1 ii kdepim-runtime4:4.11.3-1 ii kdepimlibs-kio-plugins4:4.11.3-2 ii libakonadi-calendar4 4:4.11.3-2 ii libakonadi-contact4 4:4.11.3-2 ii libakonadi-kde4 4:4.11.3-2 ii libakonadi-kmime4 4:4.11.3-2 ii libakonadiprotocolinternals1 1.11.0-1 ii libc6 2.17-97 ii libcalendarsupport4 4:4.11.3-1 ii libgcc1 1:4.8.2-13 ii libgpgme++2 4:4.11.3-2 ii libgrantlee-core0 0.3.0-5 ii libincidenceeditorsng44:4.11.3-1 ii libkabc4 4:4.11.3-2 ii libkalarmcal2 4:4.11.3-2 ii libkcalcore4 4:4.11.3-2 ii libkcalutils4 4:4.11.3-2 ii libkcmutils4 4:4.11.3-2 ii libkdecore5 4:4.11.3-2 ii libkdepim44:4.11.3-1 ii libkdeui5 4:4.11.3-2 ii libkio5 4:4.11.3-2 ii libkleo4 4:4.11.3-1 ii libkmime4 4:4.11.3-2 ii libknewstuff3-4 4:4.11.3-2 ii libknotifyconfig4 4:4.11.3-2 ii libkontactinterface4 4:4.11.3-2 ii libkparts44:4.11.3-2 ii libkpgp4 4:4.11.3-1 ii libkpimidentities44:4.11.3-2 ii libkpimtextedit4 4:4.11.3-2 ii libkpimutils4 4:4.11.3-2 ii libkprintutils4 4:4.11.3-2 ii libksieveui4 4:4.11.3-1 ii libktnef4 4:4.11.3-2 ii libmailcommon44:4.11.3-1 ii libmailimporter4 4:4.11.3-1 ii libmailtransport4 4:4.11.3-2 ii libmessagecomposer4 4:4.11.3-1 ii libmessagecore4 4:4.11.3-1 ii libmessagelist4 4:4.11.3-1 ii libmessageviewer4 4:4.11.3-1 ii libnepomukcore4 4:4.11.3-2 ii libpimcommon4 4:4.11.3-1 ii libqt4-dbus 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-network4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-xml4:4.8.5+git209-g718fae5+dfsg-1 ii libqtcore44:4.8.5+git209-g718fae5+dfsg-1 ii libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtwebkit4 2.2.1-7 ii libsendlater4 4:4.11.3-1 ii libsolid4 4:4.11.3-2 ii libsoprano4 2.9.4+dfsg-1 ii libstdc++64.8.2-13 ii libtemplateparser44:4.11.3-1 ii perl 5.14.2-21 Versions of packages kmail recommends: ii gnupg-agent 2.0.22-3 ii gnupg22.0.22-3 ii pinentry-gtk2 [pinentry-x11] 0.8.3-1 Versions of packages kmail suggests: ii bogofilter 1.2.4+dfsg1-2 pn clamav | f-prot-installer none ii kaddressbook 4:4.11.3-1 pn kleopatra none ii procmail 3.22-21 ii spambayes 1.1a6-1 -- 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#734857: marked as done (bundler: cannot load, /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle)
Your message dated Tue, 14 Jan 2014 09:41:43 +0100 with message-id 20140114084143.ga21...@nq.home.zeha.at and subject line User says it's working has caused the Debian Bug report #734857, regarding bundler: cannot load, /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle 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.) -- 734857: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bundler Version: 1.5.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, After updating/upgrading a machine running Debian Testing, gitlab doesn't start any more: $ sudo service gitlab start Starting GitLab SidekiqThe Sidekiq job dispatcher is already running with pid 26122, not restarting /usr/local/bin/bundle:23:in `load': cannot load such file -- /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle (LoadError) from /usr/local/bin/bundle:23:in `main' ..Waited 30s for the processes to write their pids, something probably went wrong. On December 2nd, with the then current software packages from Debian Testing everything still worked as expected. To reproduce it suffices to call bundle: $ bundle /usr/local/bin/bundle:23:in `load': cannot load such file -- /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle (LoadError) from /usr/local/bin/bundle:23:in `main' Best regards, Chris -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bundler depends on: ii ruby 1:1.9.3 ii ruby-net-http-persistent 2.9-1 ii ruby-thor 0.18.1-1 ii ruby1.9.1 [ruby-interpreter] 1.9.3.484-1 Versions of packages bundler recommends: ii build-essential 11.6 ii less 458-2 ii ruby-dev 1:1.9.3 ii rubygems-integration 1.2 ii sudo 1.8.8-2 bundler suggests no packages. -- no debconf information If you want to provide additional information, please wait to receive the bug tracking number via email; you may then send any extra information to n...@bugs.debian.org (e.g. 999...@bugs.debian.org), where n is the bug number. Normally you will receive an acknowledgement via email including the bug report number within an hour; if you haven't received a confirmation, then the bug reporting process failed at some point (reportbug or MTA failure, BTS maintenance, etc.). ---End Message--- ---BeginMessage--- X-CrossAssassin-Score: 33688---End Message---
Bug#734857: bundler: cannot load, /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle
On 01/10/2014 05:45 PM, Christian Hofstaedtler wrote: * Chris c20...@gmail.com [140110 13:03]: To reproduce it suffices to call bundle: $ bundle /usr/local/bin/bundle:23:in `load': cannot load such file -- /usr/share/rubygems-integration/1.9.1/gems/bundler-1.5.0/bin/bundle (LoadError) from /usr/local/bin/bundle:23:in `main' ^ Debian does not ship /usr/local/bin/bundle. I suspect that you somehow installed bundler from RubyGems. Okay. So we reinstalled bundler and did then a `bundle install` for the gitlab stuff. Now gitlab worked again. The latest update of bundler from debian testing (1.5.1+dfsg-1) pulled in afterwords didn't break anything, either, i.e. now everything works as expected. Thanks, Chris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735183: FTBFS on all architectures: test-suite failures
On Tue, Jan 14, 2014 at 12:22 PM, Theppitak Karoonboonyanan t...@linux.thai.net wrote: That's weird. I cannot reproduce it with my i386 cowbuilder. See the attached build log. (My host system is amd64, but the base.cow being used is debootstrapped as i386.) OK. I managed to setup sbuild and have found the cause of the problem. It's about the difference between normal build and arch-only build. Fix will be uploaded soon. -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735048: mediathekview: doesn't start at all
On 12.01.2014 11:20, Gerfried Fuchs wrote: Package: mediathekview Version: 4-1 Severity: grave Justification: renders package unusable Hi! *ping* Did you try to run MediathekView with OpenJDK 7? What was the outcome? Thanks Markus signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#735048: mediathekview: doesn't start at all
Processing commands for cont...@bugs.debian.org: tags 735048 - moreinfo Bug #735048 [mediathekview] mediathekview: doesn't start at all Removed tag(s) moreinfo. severity 735048 normal Bug #735048 [mediathekview] mediathekview: doesn't start at all Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 735048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735048 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#735048: mediathekview: doesn't start at all
tags 735048 - moreinfo severity 735048 normal thanks Dear Markus! * Markus Koschany a...@gambaru.de [2014-01-12 12:10:41 CET]: On 12.01.2014 11:20, Gerfried Fuchs wrote: I didn't want to wait the few days for the testing transition, so I installed mediathekview from unstable into my testing system. But it doesn't start at all, this is the output I receive: Did you try to run MediathekView with OpenJDK 6 or OpenJDK 7? As far as I can see you seem to have installed OpenJDK 7 but perhaps your defaults (update-alternatives) still point to version 6? MV 4 will only work with OpenJDK 7 or later and since default-jre points to OpenJDK-7 on your system, the dependency should be satisfied. You are right, after I removed openjdk-6 packages from my system mediathekview started properly. I am uncertain how this problem could get resolved. Having a wrapper script that would set JAVA_HOME, or anything along that lines. Or at least give useful error message when started from the commandline - which wouldn't help people calling it from the menu. Maybe a zenity dialogue then or such. Do you have an idea how other packages with similar requirements do mitigate the issue? At least thanks for your information on how to get it working! Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tags
Processing commands for cont...@bugs.debian.org: tag 735138 + pending Bug #735138 [aspcud] autopkg test always failing Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 735138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735138 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#730737: marked as done (dizzy: exits immediately with strict refs error in Perl2GLSL.pm, line 160)
Your message dated Tue, 14 Jan 2014 09:19:38 +
with message-id e1w309q-0002hn...@franck.debian.org
and subject line Bug#730737: fixed in dizzy 0.3-2
has caused the Debian Bug report #730737,
regarding dizzy: exits immediately with strict refs error in Perl2GLSL.pm,
line 160
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.)
--
730737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: dizzy
Version: 0.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When I launch dizzy, it briefly displays a black window, then exits. The
following is printed to the console:
Smartmatch is experimental at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 17.
Smartmatch is experimental at /usr/share/perl5/Dizzy/Perl2GLSL.pm line 183.
GPU features: [x] GLSL [x] FBOs
Can't use string (# op description list of private...) as an ARRAY ref
while strict refs in use at /usr/share/perl5/Dizzy/Perl2GLSL.pm line
160.
I have a local modification to /usr/games/dizzy, to make the '-f'
(fullscreen) option work; this was reported as bug 697423, and appears
to be fixed under that bug, but the fixed version has not yet been
released AFAICT. I have tested without this modification, by way of
'apt-get install --reinstall dizzy', and the present problem still
occurs.
I am reporting this as grave because it renders the package completely
unusable for me, and I have no reason to expect the behavior to be
different for anyone else. If it still works on a fully upgraded system
tracking testing for anyone else, please feel free to downgrade this to
normal.
Note that this is the same version of dizzy as was working at the time
of bug 697423. In the interim I have dist-upgraded multiple times to
track testing, and I am at present up-to-date with testing as of early
this afternoon. I do not know specifically when it stopped working.
Although I do not use dizzy often, I still like having it available. If
there is anything I can do to help track this down, please do not
hesitate to let me know.
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.10-3-amd64 (SMP w/12 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 dizzy depends on:
ii libconvert-color-perl 0.09-1
ii libopengl-perl 0.6702+dfsg-2
ii libsdl-perl2.540-3
ii perl 5.18.1-4
dizzy recommends no packages.
dizzy suggests no packages.
-- debconf-show failed
-- debsums errors found:
debsums: changed file /usr/games/dizzy (from dizzy package)
---End Message---
---BeginMessage---
Source: dizzy
Source-Version: 0.3-2
We believe that the bug you reported is fixed in the latest version of
dizzy, 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 730...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Damyan Ivanov d...@debian.org (supplier of updated dizzy 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 Jan 2014 10:26:47 +0200
Source: dizzy
Binary: dizzy xscreensaver-screensaver-dizzy
Architecture: source all
Version: 0.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: Damyan Ivanov d...@debian.org
Description:
dizzy - Graphics demo that makes you dizzy using rotating textures
xscreensaver-screensaver-dizzy - Graphics demo that makes you dizzy
(XScreenSaver hack)
Closes: 697423 730737 734160
Changes:
dizzy (0.3-2) unstable; urgency=low
.
* Team upload
.
[ gregor herrmann ]
* debian/control: update {versioned,alternative} (build) dependencies.
.
[ Salvatore Bonaccorso ]
* Add Add-missing-use-SDL-Mouse.patch patch.
Add 'use SDL::Mouse' in dizzy. Fix fullscreen display with '-f' fails
on undefined subroutine, 'SDL::Mouse::show_cursor' at line 61.
Thanks to The
Bug#731743: marked as done (dff: FTBFS (broken swig detection))
Your message dated Tue, 14 Jan 2014 09:19:30 + with message-id e1w309i-0002dk...@franck.debian.org and subject line Bug#731743: fixed in dff 1.3.0+dfsg.1-4 has caused the Debian Bug report #731743, regarding dff: FTBFS (broken swig detection) 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.) -- 731743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: dff Version: 1.3.0+dfsg.1-3 Severity: serious Justification: fails to build from source (but built successfully in the past) Your package fails to build in sid with: CMake Error at CMakeLists.txt:29 (MESSAGE): Need SWIG version = 2.0.7 (current version is 2.0.11) -- Configuring incomplete, errors occurred! Cheers, Julien signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: dff Source-Version: 1.3.0+dfsg.1-4 We believe that the bug you reported is fixed in the latest version of dff, 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 731...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Chifflier pol...@debian.org (supplier of updated dff 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: Tue, 14 Jan 2014 09:51:19 +0100 Source: dff Binary: dff Architecture: source amd64 Version: 1.3.0+dfsg.1-4 Distribution: unstable Urgency: high Maintainer: Pierre Chifflier pol...@debian.org Changed-By: Pierre Chifflier pol...@debian.org Description: dff- Powerful, efficient and modular digital forensic framework Closes: 731743 Changes: dff (1.3.0+dfsg.1-4) unstable; urgency=high . * Fix broken swig detection (Closes: #731743) Urgency high, fix an RC bug * Bump Standards Version to 3.9.5 Checksums-Sha1: 59f4ac2a5d78856072a9d7d068ca602db63faf1a 1680 dff_1.3.0+dfsg.1-4.dsc 676a393036f103d9fd66849f6963ae2b6d0fdcf3 5604 dff_1.3.0+dfsg.1-4.debian.tar.gz 7a554d9c0f8580e963d1b880a7f5a1aaf8dd144b 4360852 dff_1.3.0+dfsg.1-4_amd64.deb Checksums-Sha256: 286d1dd09dd446201790086105fd13ca3f3d60ebbdf2dd0f0839a9976db7a2f8 1680 dff_1.3.0+dfsg.1-4.dsc 2417b2d735ca6f3f74906b101fe2b9c963c128ef8d54e5c63dc31696057a445a 5604 dff_1.3.0+dfsg.1-4.debian.tar.gz b8486305e9b3a76a1f28448507d726e69a19b9a996c2d8585e4dd0929c4166b3 4360852 dff_1.3.0+dfsg.1-4_amd64.deb Files: 5d04eac42405935a0b51c858d7c40d22 1680 admin optional dff_1.3.0+dfsg.1-4.dsc c6c71d24407034e006458274301e6210 5604 admin optional dff_1.3.0+dfsg.1-4.debian.tar.gz 27906491d989a678c03e2c0cc4efce58 4360852 admin optional dff_1.3.0+dfsg.1-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) iQEcBAEBAgAGBQJS1PwAAAoJEFqCeQfe0MQYDYkH/jAg+3pHa9rUAnqj9hMT9G0k 0fe8DJ3bN5AS8ySqQXa8nl95z1fEA99KRBdHNIFMDnLbkTqJAgw+TMqKa5Wa7lw1 n9+TUKxDdU8b5HTVApw5ia+y226NCoUxxbEeyW8eUiQqBkAZuDZnnJXkskUrq7Vn QnHkXxJrysnuGvCxAs3xIY14BxZt+4XBW1Vbdt7u+YkqNkggHjfecWGl9QWnYmXD 8hN06X08a5/Gg+CezNBD0jmdWSLnMILyFYq/Hfkzr2YSv57ZkLpn2faJFMKEzYeR rFyczIyjn26HHMoCPiLz2CxI9H4EWCx9akorhdFm4dOPqFUQOyHj+WPceJ5Ey9k= =4pp2 -END PGP SIGNATUREEnd Message---
Bug#735183: marked as done (FTBFS on all architectures: test-suite failures)
Your message dated Tue, 14 Jan 2014 09:21:27 + with message-id e1w30bb-0004bd...@franck.debian.org and subject line Bug#735183: fixed in libthai 0.1.20-3 has caused the Debian Bug report #735183, regarding FTBFS on all architectures: test-suite 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.) -- 735183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libthai Version: 0.1.20-2 Severity: serious libthai FTBFS on all architectures. See https://buildd.debian.org/status/package.php?p=libthai -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: libthai Source-Version: 0.1.20-3 We believe that the bug you reported is fixed in the latest version of libthai, 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 735...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Theppitak Karoonboonyanan t...@debian.org (supplier of updated libthai 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: Tue, 14 Jan 2014 15:55:01 +0700 Source: libthai Binary: libthai-dev libthai0 libthai-data libthai-doc Architecture: source all amd64 Version: 0.1.20-3 Distribution: unstable Urgency: medium Maintainer: Theppitak Karoonboonyanan t...@debian.org Changed-By: Theppitak Karoonboonyanan t...@debian.org Description: libthai-data - Data files for Thai language support library libthai-dev - Development files for Thai language support library libthai-doc - Documentation files for Thai language support library libthai0 - Thai language support library Closes: 735183 Changes: libthai (0.1.20-3) unstable; urgency=medium . * Fix arch-only FTBFS due to failure in test suite. In build-arch target, dictionary should be built before test suite is run. - debian/control: Move libdatrie1-bin from B-Dep-Indep to B-Dep. - debian/rules: Configure with --enable-dict and also build data/ before running checks. (Closes: #735183) Checksums-Sha1: 322aad923d7552ee5376a013342606e57e1dba8a 2129 libthai_0.1.20-3.dsc 8310664da79384572c3d78120c77252b1c9df4fd 11341 libthai_0.1.20-3.debian.tar.gz 3a559e28672b519900a4faf7be6bc227be54e1ea 157478 libthai-data_0.1.20-3_all.deb abc8323dca00539c6e2a51c18c4bdcbf8b7881b5 74498 libthai-doc_0.1.20-3_all.deb bcb4c639ce8774430a2b0dce521bd4d7858b2efc 55116 libthai-dev_0.1.20-3_amd64.deb 8bd4d7eb0485d1539c4afc4c42d95e66b7fa132d 44242 libthai0_0.1.20-3_amd64.deb Checksums-Sha256: 2bc1de71b4c1fdcaec8d346c26a2dfee5acb981834831bbfb7a06e3e286c4b5c 2129 libthai_0.1.20-3.dsc 054b70c706a078ba2038836d130a057326ff402df2b4da6c6acaff3390f9b70b 11341 libthai_0.1.20-3.debian.tar.gz 17aa9479b70c030e623e064aed838963e8ea6e1d8e8f33629f95273809baf396 157478 libthai-data_0.1.20-3_all.deb 8ca8011c27fcfc1b7f1582c3167e796ce4a9924b6e741ce48865c06e7fad8de9 74498 libthai-doc_0.1.20-3_all.deb c00dd17345dbfb817e6ceaa67ddef2934ad3ae2c0e0aeea52d384bf3ae7a0e42 55116 libthai-dev_0.1.20-3_amd64.deb aa7707deb0e79edb12fcee98f5c97d063bdaf0379008daef9405915b6c67e213 44242 libthai0_0.1.20-3_amd64.deb Files: 819e1cb05848f72df10566fa3c067d0d 2129 libs optional libthai_0.1.20-3.dsc a3f207036c9f6899363748d26e1a151c 11341 libs optional libthai_0.1.20-3.debian.tar.gz 69f6f1a7feb5c14dfc95810d4a1053da 157478 libs optional libthai-data_0.1.20-3_all.deb 880a061b99ea8d86127a2f1cf225ac73 74498 doc optional libthai-doc_0.1.20-3_all.deb 0b05299c644d7f3d4efb5352c86d566f 55116 libdevel optional libthai-dev_0.1.20-3_amd64.deb feab14582d91b12f201cb8140a375b8d 44242 libs optional libthai0_0.1.20-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJS1PzWAAoJEKLrrtG2+QJBkEoQAK3EOlfXn1HyCC8nIq6OY3nX PkBBGbs5dTQURmuxuSAuoD5v8+miqFWenQnSwvY31KGLeK6qFX1i5xMKkyp+wT9J
Bug#735138: autopkg test always failing
Hi Martin, On Mon, Jan 13, 2014 at 05:26:42PM +0100, Martin Pitt wrote: Hello Ralf, Ralf Treinen [2014-01-13 16:53 +0100]: thanks for your patch. However, I cannot reproduce that Bad Input Stream error on my machine. What are the versions of the dependencies of aspcud that you had installed when running this test ? Indeed I re-tried in sid, and that particular Bad Input Stream error doesn't happen there: /tmp/aspcud-1.8.0 $ adt-run -B .// --- adt-virt-schroot sid [...] adt-run: ubtree0t-upstream: - - - - - - - - - - results - - - - - - - - - - ubtree0t-upstreamFAIL non-zero exit status 126 adt-run: ubtree0t-upstream: - - - - - - - - - - stderr - - - - - - - - - - /usr/bin/aspcud: /tmp/adt-run.rFHKC6/ubtree0t-upstream-testtmp/tmpdir/outNJPr7x/parse.py: /usr/bin/python: bad interpreter: No such file or directory So apparently something in these tests uses python, but python isn't a dependency of the package or the tests. Once I add that, the test [...] It may very well be that python actually needs to be a binary dependency of aspcud or cudf-tools, I didn't check that closely. Indeed, aspcud needs to depend on python. The aspcud.sh shell script contains an embedded python script, as I just discovered. Thanks for your help ! -Ralf. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Packaging] Bug#735236: [munin] Non sourced min.js files
Processing commands for cont...@bugs.debian.org: Package: munin Limiting to bugs with field 'package' containing at least one of 'munin' Limit currently set to 'package':'munin' tag 735236 +experimental Bug #735236 [munin] [munin] Non sourced min.js files Added tag(s) experimental. found 735236 2.1.1-1 Bug #735236 [munin] [munin] Non sourced min.js files Marked as found in versions munin/2.1.1-1. thanks Stopping processing here. Please contact me if you need assistance. -- 735236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735236 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#735254: flash-kernel: QNAP TS-212 doesn't boot with 3.12-1-kirkwood and flash-kernel 3.12
On 14 January 2014 08:36, Ian Campbell i...@hellion.org.uk wrote: Control: reassign -1 src:linux Control: forcemerge 735172 -1 On Tue, 2014-01-14 at 05:50 +, Ruben Silveira wrote: Description and steps to reproduce: - QNAP TS-212 (cpuinfo = 'QNAP TS-119/TS-219') with 3.11-2-kirkwood and flash-kernel 3.12; - Installed 3.12-1-kirkwood (update-initramfs and flash-kernel executed automatically and normally); - Rebooted; - System not up; - Connected serial console; - Rebooted; - System hangs just after kernel being (successfully) loaded by U-Boot, with no output whatsoever. You see Uncompressing Linux... done, booting the kernel. as the last thing, right? You're right, that is the last message. I was able to restore an old backup (flash and rootfs), repeat the whole process and get to the same exact result. I suppose this has to do with DT - Device Tree and could be (loosely) related to bugs #731345 and #734769. Actually AFAICT this is #735172 which is a kernel bug unrelated to the recent flash-kernel changes, reassigning and merging. The solution appears to be the appendage of DTB to the kernel, but I have little to no knowledge in patching flash-kernel to get to a working solution. This issue is being observed even on platforms which have no DTB support yet (e.g. TS-419). Have you actually tried with an appended DTB and seen it work or are you speculating? I'm speculating, as I haven't tried that. I don't know what or how to append to a kernel. If you can point me to some kind a reference, I can test that out in my current setup. Thank you, Ruben -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735270: package build with SSE2 defaults on i386
Package: glm Version: 0.9.5.0-1 Severity: serious Tags: sid jessie when building on i386: cd /build/buildd/glm-0.9.5.0/obj-i686-linux-gnu/test/gtx /usr/bin/c++ -D_CRT_SECURE_NO_WARNINGS -O2 -g -DNDEBUG -I/build/buildd/glm-0.9.5.0/. -I/build/buildd/glm-0.9.5.0/./test/external-pedantic -o CMakeFiles/test-gtx_associated_min_max.dir/gtx_associated_min_max.cpp.o -c /build/buildd/glm-0.9.5.0/test/gtx/gtx_associated_min_max.cpp In file included from /build/buildd/glm-0.9.5.0/test/gtx/gtx_associated_min_max.cpp:10:0: /usr/lib/gcc/i686-linux-gnu/4.8/include/emmintrin.h:31:3: error: #error SSE2 instruction set not enabled # error SSE2 instruction set not enabled ^ This is not just for the glm build, but every package build-depending on this will ftbfs on i386. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: nvidia-graphics-drivers: CVE-2013-5987 - Unprivileged GPU access vulnerability
Processing control commands: fixed -1 319.72-1,331.20-1 Bug #735271 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2013-5987 - Unprivileged GPU access vulnerability Marked as fixed in versions nvidia-graphics-drivers/331.20-1 and nvidia-graphics-drivers/319.72-1. -- 735271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735271 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#735270: package build with SSE2 defaults on i386
On Tue, Jan 14, 2014 at 11:09:09AM +0100, Matthias Klose wrote: when building on i386: cd /build/buildd/glm-0.9.5.0/obj-i686-linux-gnu/test/gtx /usr/bin/c++ -D_CRT_SECURE_NO_WARNINGS -O2 -g -DNDEBUG -I/build/buildd/glm-0.9.5.0/. -I/build/buildd/glm-0.9.5.0/./test/external-pedantic -o CMakeFiles/test-gtx_associated_min_max.dir/gtx_associated_min_max.cpp.o -c /build/buildd/glm-0.9.5.0/test/gtx/gtx_associated_min_max.cpp In file included from /build/buildd/glm-0.9.5.0/test/gtx/gtx_associated_min_max.cpp:10:0: /usr/lib/gcc/i686-linux-gnu/4.8/include/emmintrin.h:31:3: error: #error SSE2 instruction set not enabled # error SSE2 instruction set not enabled ^ This is not just for the glm build, but every package build-depending on this will ftbfs on i386. I don't think reverse depends will FTBFS. The problem is that the tests (which are only run at build time and are not in any way included in the binary packages) unconditionally #include emmintr.h. Could you try removing those #includes from glm-0.9.5.0/test/gtx/*.cpp, and try building again? -- Met vriendelijke groet / with kind regards, Guus Sliepen g...@debian.org signature.asc Description: Digital signature
Bug#735271: nvidia-graphics-drivers: CVE-2013-5987 - Unprivileged GPU access vulnerability
Source: nvidia-graphics-drivers Severity: serious Tags: security Control: fixed -1 319.72-1,331.20-1 Quoting from http://nvidia.custhelp.com/app/answers/detail/a_id/3377 Vulnerability Description: An NVIDIA graphics driver bug allows unprivileged user-mode software to access the GPU inappropriately. An attacker who successfully exploited this vulnerability could take control of an affected system. Exploit Scope and Risk: To take advantage of this vulnerability, an attacker would need to run specially crafted software locally on the target computer. Expert knowledge of system and NVIDIA GPU programming would be required to create such an exploit. NVIDIA is not aware of the existence of any actual exploits that leverage this vulnerability. This issue could potentially affect all supported PC OS platforms and form factors. NVIDIA Tegra GPUs are not vulnerable. The following table shows the first NVIDIA UNIX GPU Drivers that contain the security fix. Driver BranchVersion Release 331 331.20 Release 319 319.72 Release 304 304.116 nvidia-graphics-drivers-legacy-304xx is affected as well, but is already at the fixed version. It is unknown whether the older legacy branches are affected. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735270: package build with SSE2 defaults on i386
Am 14.01.2014 11:23, schrieb Guus Sliepen: I don't think reverse depends will FTBFS. The problem is that the tests (which are only run at build time and are not in any way included in the binary packages) unconditionally #include emmintr.h. Could you try removing those #includes from glm-0.9.5.0/test/gtx/*.cpp, and try building again? I don't think this would be the correct fix, because the include machinery provides several FORCE macros to support those targets as well. Please check with a i386 chroot. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730428: marked as done (nss: copyright file refers to wrong license)
Your message dated Tue, 14 Jan 2014 11:00:07 + with message-id e1w31j5-0005da...@franck.debian.org and subject line Bug#730428: fixed in nss 2:3.15.4-1 has caused the Debian Bug report #730428, regarding nss: copyright file refers to wrong license 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.) -- 730428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:nss Version: 2:3.15.3-1 Severity: serious The copyright file refers to the MPL 1.1, but the COPYING file in the tarball refers to MPL 2.0. The copyright file should probably be updated to refer to the newer version. -- 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.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: nss Source-Version: 2:3.15.4-1 We believe that the bug you reported is fixed in the latest version of nss, 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 730...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Hommey gland...@debian.org (supplier of updated nss 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 Jan 2014 10:46:04 +0900 Source: nss Binary: libnss3 libnss3-1d libnss3-nssdb libnss3-tools libnss3-dev libnss3-dbg Architecture: source amd64 all Version: 2:3.15.4-1 Distribution: unstable Urgency: low Maintainer: Maintainers of Mozilla-related packages pkg-mozilla-maintain...@lists.alioth.debian.org Changed-By: Mike Hommey gland...@debian.org Description: libnss3- Network Security Service libraries libnss3-1d - Network Security Service libraries - transitional package libnss3-dbg - Debugging symbols for the Network Security Service libraries libnss3-dev - Development files for the Network Security Service libraries libnss3-nssdb - Network Security Security libraries - shared databases libnss3-tools - Network Security Service tools Closes: 537866 682925 730428 Changes: nss (2:3.15.4-1) unstable; urgency=low . * New upstream release. * Acknowledge NMU. * debian/rules: Avoid long one-liner with semi-colons. * debian/patches/*: Refresh patches. * debian/copyright: Update. Closes: #730428. * debian/control, debian/libnss3-nssdb.*, debian/pkcs11.txt, debian/rules: Add shared cert and key databases. Thanks Timo Aaltonen. Closes: #537866. * debian/rules: Use DEB_HOST_ARCH instead of DEB_BUILD_ARCH. * debian/control: Mark libnss3-dev as Multi-Arch: same. Thanks Shawn Landden. Closes: #682925. * debian/libnss3.symbols: Add NSS_3.15.4 symbol versions. Checksums-Sha1: fb226da0f98283974a3ae9bd561424212ca4517d 2229 nss_3.15.4-1.dsc c164fac83fcbaff010786767e2a858ca23a89a5b 6366271 nss_3.15.4.orig.tar.gz 2fffb0fc1bd374fb884b1ae10c8360f2f6ea8496 34635 nss_3.15.4-1.debian.tar.gz fad01f5dd4c0583a6c30e0ad8e02f50972e3e9ec 1093506 libnss3_3.15.4-1_amd64.deb 8d00425977641c16dd6547415725538e409f9c72 17300 libnss3-1d_3.15.4-1_amd64.deb 2d5da1ffaea99ba58c4e0860e7bf736978857984 18548 libnss3-nssdb_3.15.4-1_all.deb 656dac488cec51161200f53cee80b6a8ff1e5a35 749918 libnss3-tools_3.15.4-1_amd64.deb 23cb9ca3455c87a916b4ff36507bc027cf77676b 217790 libnss3-dev_3.15.4-1_amd64.deb 3f4d6ea7e4102ac3e7ae42d2b1f23acb74631552 8134642 libnss3-dbg_3.15.4-1_amd64.deb Checksums-Sha256: 841263f162fe6a653aa9565f14dbb95ec7b361612129e8020f12816e6075401a 2229 nss_3.15.4-1.dsc 14d69a0735c5af6b3cc12591f7ebf272203e889f09104182148091d0af682d7c 6366271 nss_3.15.4.orig.tar.gz bdebdc561b5a1102ff65964c459df7914f815f0d6c60800841baef159dcfcb6d 34635 nss_3.15.4-1.debian.tar.gz
Bug#726578: Ping: pwgen: Multiple vulnerabilities in passwords generation
Thank you for reacting quickly!
begin quotation from Theodore Ts'o (in 20140112234500.ga15...@thunk.org):
On Sun, Jan 12, 2014 at 09:27:14PM +0100, Arne Wichmann wrote:
This grave problem is now open for more than two months. Is there any plan
to resolve this?
First, the CVE about having the unavailability of /dev/random fail
hard -- sure, that should be a separate bug since that's a fix that I
think is reasonable at this point. We can now guarantee that
/dev/random exists everywhere. (And by that same token, if an
attacker can cause /dev/random not to be present, they probably have
root, so you're probably toast anyway. So I don't think it's going to
really improve things to remove the drand() fallback, but I don't have
strong feelings about that.)
So you might clone a new bug for this...
Secondly, I'll note that one of the CVE's were rejected as not a
vulnerability. (In general it would have been better to have opened
seperate bugs for each CVE.)
Different maintainers have different preferences here - I will note that
you want seperate bugs (as we do for a number of other packages).
Finally, whether you think the other two CVE's justify this to be
serious, let alone grave bug really depends on what you think the
goals of pwgen are. To quote from the manual page:
This is your decision - we try to use a fitting severity for every problem,
but sometimes the cases are not so clear.
The pwgen program generates passwords which are designed to be easily
memorized by humans, while being as secure as possible. Human-memo???
rable passwords are never going to be as secure as completely com???
pletely random passwords. In particular, passwords generated by pwgen
without the -s option should not be used in places where the password
could be attacked via an off-line brute-force attack.On the other
hand, completely randomly generated passwords have a tendency to be
written down, and are subject to being compromised in that fashion.
So we could change the defaults to be pwgen -csy 20, in which case
you would get passwords like tihs:
L}U@lc_~i^n|ro!4uI- 1`;yXlYVMW%?E9)3A7G **}6BoBu=!~3)y?3v]Or
=:PC;H?E7*+6$c-QH URGgjUNG[\dSw\p7F-] _AXZ~(HYd8Q#%b!]'u:
~)0I-{)}_Ya*Q2nlWN; ^#t~1/'sf@*xz9GOhBuv e_[-_Fe{CD#]DY8@M^a
I'm not sure that would be an improvement, as simply no one would use
them.
OK, how about this? (Generated using pwgen -s).
vQ6uwkMk lSswO2MB tA8dYPpl KU1pQ2Xh 2XfxRyrC Za2xKx7h psPwHZ0c dOsC0JBX
JY3udA9c t6LzoiUq M0jR3AoS GOHkNE7G TeThsZz1 6cVi4ayY Poe4hPj7 o2a7OpPC
Xh24cRLO 1chQyseV 6c2k0O3B OkdgRxy4 K6Vc4JY2 ylO3IE9B gVvNxw6B 7wjcOXwF
Again, this will make the professional paranoids happy (although
perhaps not as happy as =:PC;H?E7*+6$c-QH), but its not clear that
real users would be any less likely to write ylO3IE9B on a sticky
note which is pasted to their monitor, or just in a passwords file
in their home directory.
I do not have a really good idea on how to handle this. Some ideas come to
mind, mostly inspired by [1]:
- Improve the algorithm to be less biased. Though I see that would not be
easy.
- Warn about the bias
- Use -s as default
[2] suggests, that there is a patch out there, but I have not yet looked at
it.
So ultimately, a lot of this is about an argument over defaults, and I
think the higher level problem is that no matter what password policy
you use, passwords are doomed as a technology. Anything which is
secure against a brute force attack is impossible for a user to use,
unless they share passwords across multiple sites so they only have to
remember one password such as ylO3IE9B --- at which point they get
toast once some web site screws up in some way and gets penetrated by
bad guys.
I see the point, but that does not make the problem go away, and in many
cases you do not have so much of a choice, so the program does still have
its points.
CVE-2013-4440 has an easy fix, isn't it?
[1] http://www.openwall.com/lists/oss-security/2012/01/19/24
[2] http://marc.info/?l=oss-securitym=138015793928431w=2
cu
AW
--
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to protect yourself, just don't support
it. Noone can free you but yourself. (crag, on Debian Planet)
Arne Wichmann (a...@linux.de)
signature.asc
Description: Digital signature
Bug#735270: package build with SSE2 defaults on i386
On Tue, Jan 14, 2014 at 11:36:08AM +0100, Matthias Klose wrote: I don't think reverse depends will FTBFS. The problem is that the tests (which are only run at build time and are not in any way included in the binary packages) unconditionally #include emmintr.h. Could you try removing those #includes from glm-0.9.5.0/test/gtx/*.cpp, and try building again? I don't think this would be the correct fix, because the include machinery provides several FORCE macros to support those targets as well. The #include emmintrin.h does not #define any macro that changes the behaviour in GLM. In fact, GLM itself checks for the presence of __SSE2__ and automatically #includes emmintrin.h if possible. Also, GLM version 0.9.4.6 did not #include emmintrin.h in its tests, and only a few tests have the #include, I think it is just an oversight from the upstream maintainer. Please check with a i386 chroot. An i386 chroot won't do me any good as I only have processors that support SSE2. It would be helpful if you could test the patch which I attached to this email on your i386 system. -- Met vriendelijke groet / with kind regards, Guus Sliepen g...@debian.org --- a/test/gtx/gtx_associated_min_max.cpp +++ b/test/gtx/gtx_associated_min_max.cpp @@ -7,8 +7,6 @@ // File: test/gtx/associated_min_max.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/associated_min_max.hpp --- a/test/gtx/gtx_bit.cpp +++ b/test/gtx/gtx_bit.cpp @@ -7,8 +7,6 @@ // File: test/gtx/bit.cpp /// -#include emmintrin.h - #include glm/gtx/bit.hpp #include glm/gtc/type_precision.hpp --- a/test/gtx/gtx_closest_point.cpp +++ b/test/gtx/gtx_closest_point.cpp @@ -7,8 +7,6 @@ // File: test/gtx/associated_min_max.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/associated_min_max.hpp --- a/test/gtx/gtx_color_space.cpp +++ b/test/gtx/gtx_color_space.cpp @@ -7,8 +7,6 @@ // File: test/gtx/color_space.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/color_space.hpp --- a/test/gtx/gtx_color_space_YCoCg.cpp +++ b/test/gtx/gtx_color_space_YCoCg.cpp @@ -7,8 +7,6 @@ // File: test/gtx/color_space_YCoCg.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/color_space_YCoCg.hpp --- a/test/gtx/gtx_component_wise.cpp +++ b/test/gtx/gtx_component_wise.cpp @@ -7,8 +7,6 @@ // File: test/gtx/component_wise.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/component_wise.hpp --- a/test/gtx/gtx_extented_min_max.cpp +++ b/test/gtx/gtx_extented_min_max.cpp @@ -7,8 +7,6 @@ // File: test/gtx/associated_min_max.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/associated_min_max.hpp --- a/test/gtx/gtx_int_10_10_10_2.cpp +++ b/test/gtx/gtx_int_10_10_10_2.cpp @@ -7,8 +7,6 @@ // File: test/gtx/associated_min_max.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/associated_min_max.hpp --- a/test/gtx/gtx_mixed_product.cpp +++ b/test/gtx/gtx_mixed_product.cpp @@ -7,8 +7,6 @@ // File: test/gtx/associated_min_max.cpp /// -#include emmintrin.h - #include glm/glm.hpp #include glm/gtc/type_precision.hpp #include glm/gtx/associated_min_max.hpp signature.asc Description: Digital signature
Bug#735281: missing license in debian/coypright
Package: geoclue-2.0 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, some documentation, for example geoclue-2.0.0\docs\geoclue-docs.xml is licensed under GFDLv1.1+. Please add this 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#735270: package build with SSE2 defaults on i386
Am 14.01.2014 12:41, schrieb Guus Sliepen: Please check with a i386 chroot. An i386 chroot won't do me any good as I only have processors that support SSE2. It would be helpful if you could test the patch which I attached to this email on your i386 system. this is a misunderstanding. The compiler doesn't define these on macros by itself. it defaults to i586. So yes, a test in an i386 chroot does help. Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735270: marked as forwarded (package build with SSE2 defaults on i386)
Your message dated Tue, 14 Jan 2014 13:01:44 +0100 with message-id 20140114120144.gs1...@sliepen.org has caused the report #735270, regarding package build with SSE2 defaults on i386 to be marked as having been forwarded to the upstream software author(s) Christophe Riccio g...@g-truc.net (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.) -- 735270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Hello Christophe, Since GLM version 0.9.5.0, some tests in test/gtx/ appear to unconditionally #include emmintrin.h. This causes a compiler error on machines that do not support SSE2 instructions. I think these #includes should be removed. -- Met vriendelijke groet / with kind regards, Guus Sliepen g...@debian.org signature.asc Description: Digital signature ---End Message---
Bug#735270: package build with SSE2 defaults on i386
On Tue, Jan 14, 2014 at 01:01:25PM +0100, Matthias Klose wrote: An i386 chroot won't do me any good as I only have processors that support SSE2. It would be helpful if you could test the patch which I attached to this email on your i386 system. this is a misunderstanding. The compiler doesn't define these on macros by itself. it defaults to i586. So yes, a test in an i386 chroot does help. Ugh, I should have known that. I'll test it. -- Met vriendelijke groet / with kind regards, Guus Sliepen g...@debian.org signature.asc Description: Digital signature
Bug#668890: This bug should be solved the most correct way IMO
Package: dirmngr Version: 1.1.1-1.1 Tags: patch Hi, thanks for the NMU; nonetheless, I believe the root cause of the issue shouldn't be worked around. The use of su in dirmngr init script is causing further troubles [1] and I believe that the cleanest solution, which I found to fix the mentioned issues, would be using start-stop-daemon directly, as Thorsten recommended in message #33: --- dirmngr.old 2014-01-14 13:01:12.235277583 +0100 +++ dirmngr.new 2014-01-14 13:01:24.791269629 +0100 @@ -32,7 +32,7 @@ mkdir -p /var/run/dirmngr || return 1 chown dirmngr:dirmngr /var/run/dirmngr || return 1 - output=$(su -c . /lib/lsb/init-functions umask 027 start_daemon -p $PIDFILE $DAEMON --daemon --sh dirmngr) || return 1 + output=$(start-stop-daemon --start --quiet --exec $DAEMON --oknodo --pidfile $PIDFILE --umask 027 --chuid dirmngr -- --daemon --sh) || return 1 eval $output || return 1 pid=$(echo $DIRMNGR_INFO | cut -d : -f 2) || return 1 echo $pid $PIDFILE || return 1 Please consider applying this patch. Thanks, Maurizio [1]: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727645 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717554 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717731 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725876: marked as done (hplip: CVE-2013-6402: insecure temporary files handling in pkit.py)
Your message dated Tue, 14 Jan 2014 12:19:09 + with message-id e1w32xz-0004vm...@franck.debian.org and subject line Bug#725876: fixed in hplip 3.13.11-2.1 has caused the Debian Bug report #725876, regarding hplip: CVE-2013-6402: insecure temporary files handling in pkit.py 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.) -- 725876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hplip Version: 3.12.6-3 Tags: security (Please adjust severity as necessary) Hi, pkit.py seems to create a log file at /tmp/hp-pkservice.log and I believe it is done as root, making it a nice vector for a symlink attack. I only took a quick look at it, so I might be missing something. Could you please confirm the report? Thanks, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net ---End Message--- ---BeginMessage--- Source: hplip Source-Version: 3.13.11-2.1 We believe that the bug you reported is fixed in the latest version of hplip, 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 725...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso car...@debian.org (supplier of updated hplip 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: Sun, 12 Jan 2014 10:59:12 +0100 Source: hplip Binary: hplip hplip-data printer-driver-postscript-hp hplip-gui hplip-dbg hplip-doc hpijs-ppds printer-driver-hpijs printer-driver-hpcups libhpmud0 libhpmud-dev libsane-hpaio Architecture: source all amd64 Version: 3.13.11-2.1 Distribution: unstable Urgency: medium Maintainer: Debian HPIJS and HPLIP maintainers pkg-hpijs-de...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: hpijs-ppds - HP Linux Printing and Imaging - HPIJS PPD files hplip - HP Linux Printing and Imaging System (HPLIP) hplip-data - HP Linux Printing and Imaging - data files hplip-dbg - HP Linux Printing and Imaging - debugging information hplip-doc - HP Linux Printing and Imaging - documentation hplip-gui - HP Linux Printing and Imaging - GUI utilities (Qt-based) libhpmud-dev - HP Multi-Point Transport Driver (hpmud) development libraries libhpmud0 - HP Multi-Point Transport Driver (hpmud) run-time libraries libsane-hpaio - HP SANE backend for multi-function peripherals printer-driver-hpcups - HP Linux Printing and Imaging - CUPS Raster driver (hpcups) printer-driver-hpijs - HP Linux Printing and Imaging - printer driver (hpijs) printer-driver-postscript-hp - HP Printers PostScript Descriptions Closes: 725876 Changes: hplip (3.13.11-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add CVE-2013-6402.patch patch. CVE-2013-6402: Fix insecure temporary files handling in pkit.py. (Closes: #725876) * Add missing dh_bugfiles invocation in binary-indep target Checksums-Sha1: 865de0288b21c0eaf248e51aa05e0eb6cefa8b89 2948 hplip_3.13.11-2.1.dsc 862ac81873114900db35656c4b7d253b1dec75df 108898 hplip_3.13.11-2.1.debian.tar.gz 9a7907a034b74689274b64d4422e924a5094cc5a 6567468 hplip-data_3.13.11-2.1_all.deb 22ddd65df4c0b5adcb4763219cc17245ff57e7a6 813822 printer-driver-postscript-hp_3.13.11-2.1_all.deb 8cdee642fc45cc1a6a1a183a98cf40d3851e0c99 90732 hplip-gui_3.13.11-2.1_all.deb 52a38be5e017ba70a9654e6e27385ab34d53b945 661698 hplip-doc_3.13.11-2.1_all.deb 9fd2d7606b30779f5b7573f148c1cf4ede211fa7 165004 hpijs-ppds_3.13.11-2.1_all.deb 4f31bff1ca134d58f44339340608d4bbabee0ba9 138532 hplip_3.13.11-2.1_amd64.deb 239f5f2bfe27576b70d22a45af52d886c3cd80e9 1412632 hplip-dbg_3.13.11-2.1_amd64.deb 2e4f6573184f8c3d0cfae12d2d1134144fac45b6 330940 printer-driver-hpijs_3.13.11-2.1_amd64.deb c115bba4ab0884b2e7db2d74a061663db67b0891 310344 printer-driver-hpcups_3.13.11-2.1_amd64.deb b81eb7e8b3cf327cc2ea3c0ecafd2650ec73afd3 166760 libhpmud0_3.13.11-2.1_amd64.deb 5584a1e6c39fe608fa9d37e9c46c82f6741559a1 80200 libhpmud-dev_3.13.11-2.1_amd64.deb a9d34c7b6c543e3adf894da6bc501a34d25ab07a 178290 libsane-hpaio_3.13.11-2.1_amd64.deb Checksums-Sha256:
Bug#733218: already fixed
this issue was fixed in an upload that was done before your report came in. (but: thanks for the report correct diagnosis appropriate fix!) --Barak. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 733218
Processing commands for cont...@bugs.debian.org: close 733218 1.6.2-3 Bug #733218 [src:liboping] liboping: FTBFS: cp: cannot stat 'debian/tmp/usr/bin/noping': No such file or directory Marked as fixed in versions liboping/1.6.2-3. Bug #733218 [src:liboping] liboping: FTBFS: cp: cannot stat 'debian/tmp/usr/bin/noping': No such file or directory Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 733218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733218 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#732342: Samba Stack Trace due to hdb interface change in Heimdal
On Thu, 2014-01-09 at 18:04 -0600, Jeff Clark wrote: No problem. Will send it over in a few hours. With all the false starts on this, I've sat on the patches until I can test it with the developer at Catalyst IT who also reproduced it. Once that comes out OK, I'll get the fix for this pushed, and get the matching Heimdal patch in. Brian, This bug needs a patch to Heimdal as well as to Samba. I'll post you the patch once I've tested it, and then I guess we need to work on a stricter version dep here to make sure this all keeps in sync. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735270: Tests fail to build on machines without SSE2 instructions
tags 735270 + fixed-upstream tags 735270 + pending thanks The problem has been fixed by upstream, it will be part of the upcoming release of 0.9.5.2. I already tested it in an i386 chroot :) -- Met vriendelijke groet / with kind regards, Guus Sliepen g...@debian.org signature.asc Description: Digital signature
Processed: Re: Tests fail to build on machines without SSE2 instructions
Processing commands for cont...@bugs.debian.org: tags 735270 + fixed-upstream Bug #735270 [glm] package build with SSE2 defaults on i386 Added tag(s) fixed-upstream. tags 735270 + pending Bug #735270 [glm] package build with SSE2 defaults on i386 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 735270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735270 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#735297: iceweasel: Update the license to MPL 2.0
Package: iceweasel Version: 24.2.0esr-1 Severity: serious Justification: policy 4.5 The debian/copyright file still refers MPL1.1/GPL2/LGPL2.1 tri-license only. But the license of most Mozilla source code has been updated to MPL 2.0 from the tri-license. Please update the licenses. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Pending fixes for bugs in the libdbix-class-perl package
Processing commands for cont...@bugs.debian.org: tag 735024 + pending Bug #735024 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: test failures Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 735024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735024 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#735024: Pending fixes for bugs in the libdbix-class-perl package
tag 735024 + pending thanks Some bugs in the libdbix-class-perl package are closed in revision 4d0859cdc355fe57e3800e3a67c1d76ea102c502 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libdbix-class-perl.git;a=commitdiff;h=4d0859c Commit message: add patch adapting tests to DBD::SQLite 1.40 Closes: #735024 -- FTBFS: test failures -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 735024 is forwarded to http://rt.cpan.org/Public/Bug/Display.html?id=92138
Processing commands for cont...@bugs.debian.org: forwarded 735024 http://rt.cpan.org/Public/Bug/Display.html?id=92138 Bug #735024 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: test failures Set Bug forwarded-to-address to 'http://rt.cpan.org/Public/Bug/Display.html?id=92138'. thanks Stopping processing here. Please contact me if you need assistance. -- 735024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735024 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: bug 735024 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=92138
Processing commands for cont...@bugs.debian.org: forwarded 735024 https://rt.cpan.org/Ticket/Display.html?id=92138 Bug #735024 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: test failures Changed Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=92138' from 'http://rt.cpan.org/Public/Bug/Display.html?id=92138' thanks Stopping processing here. Please contact me if you need assistance. -- 735024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735024 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#733875: dnmalloc broken
Hi This problem also exists in the version in sid. Some debugging shows that dnmalloc is broken. It is already disabled for ia64 and s390, so the maintainer obviously knows. Please disable for _all_ architectures until this code is known to work. Bastian -- Bastian BlankDurchwahl: +49 21 61 / 46 43 -194 credativ GmbH, HRB Mönchengladbach 12080 Zentrale: +49 21 61 / 46 43 0 Hohenzollernstr. 133 Fax: +49 21 61 / 46 43 -100 D-41061 Mönchengladbach www: http://www.credativ.de Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- 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#711436: Hash randomization test failures
Processing control commands: severity -1 important Bug #711436 [src:libdbix-abstract-perl] libdbix-abstract-perl: FTBFS with perl 5.18: test failures Severity set to 'important' from 'serious' -- 711436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711436 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#711436: Hash randomization test failures
Control: severity -1 important
-=| Dominic Hargreaves, 05.01.2014 18:15:20 + |=-
So this package needs to be checked to see whether the test failures
are definitely random, and that the random breakage is purely in the test
suite. If so, the severity of this bug can be downgraded to
important.
I think the problem is indeed with hash randomization, and it is not
a real problem.
The text found is
DATE 1 INSERT INTO foo ( id, name, value) VALUE S ('1', 'test1',
'value1')
while the expected text is
DATE 1 INSERT INTO foo ( value, name, id) VALUE S ('value1', 'test1',
'1')
Both SQL statements are equivalent and differ only in the order of the
fields/values.
Cheers,
dam
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728743: Fixed upstream
This bug is apparently fixed in NVIDIA 331.38 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735024: marked as done (libdbix-class-perl: FTBFS: test failures)
Your message dated Tue, 14 Jan 2014 15:19:58 + with message-id e1w35my-0005sx...@franck.debian.org and subject line Bug#735024: fixed in libdbix-class-perl 0.08250-2 has caused the Debian Bug report #735024, regarding libdbix-class-perl: FTBFS: test 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.) -- 735024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libdbix-class-perl Version: 0.08250-1 Severity: serious Justification: FTBFS This package FTBFS in a clean sid chroot: # Failed test 'Exception propogated properly' # at t/multi_create/standard.t line 447. # expecting: Regexp ((?^:cd.artist may not be NULL)) # found: DBIx::Class::Exception (DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st execute failed: NOT NULL constraint failed: cd.artist [for Statement INSERT INTO cd ( artist) VALUES ( ? )] at t/multi_create/standard.t line 446 # ) # Looks like you failed 1 test of 91. t/multi_create/standard.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/91 subtests ... # Failed test 'ambiguous find + create failed' # at t/relationship/update_or_create_multi.t line 72. # expecting: Regexp ((?^:cd\.artist\ may\ not\ be\ NULL)) # found: DBIx::Class::Exception (DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st execute failed: NOT NULL constraint failed: cd.artist [for Statement INSERT INTO cd ( genreid, title, year) VALUES ( ?, ?, ? )] at t/relationship/update_or_create_multi.t line 68 # ) # Looks like you failed 1 test of 7. t/relationship/update_or_create_multi.t . Dubious, test returned 1 (wstat 256, 0x100) Failed 1/7 subtests ... # Failed test 'threw Regexp ((?^s:DBI Exception.+cd\.artist.+NULL))' # at t/storage/error.t line 18. # expecting: Regexp ((?^s:DBI Exception.+cd\.artist.+NULL)) # found: DBIx::Class::Exception (DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st execute failed: NOT NULL constraint failed: cd.artist [for Statement INSERT INTO cd ( title) VALUES ( ? )] at t/storage/error.t line 16 # ) # Looks like you failed 1 test of 4. t/storage/error.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests ... Test Summary Report --- t/52leaks.t (Wstat: 0 Tests: 196 Failed: 0) TODO passed: 8 t/multi_create/standard.t (Wstat: 256 Tests: 91 Failed: 1) Failed test: 87 Non-zero exit status: 1 t/relationship/update_or_create_multi.t (Wstat: 256 Tests: 7 Failed: 1) Failed test: 6 Non-zero exit status: 1 t/storage/error.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=288, Tests=22165, 205 wallclock secs ( 3.49 usr 1.60 sys + 180.62 cusr 18.20 csys = 203.91 CPU) Result: FAIL ---End Message--- ---BeginMessage--- Source: libdbix-class-perl Source-Version: 0.08250-2 We believe that the bug you reported is fixed in the latest version of libdbix-class-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 735...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov d...@debian.org (supplier of updated libdbix-class-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: SHA256 Format: 1.8 Date: Tue, 14 Jan 2014 16:25:33 +0200 Source: libdbix-class-perl Binary: libdbix-class-perl Architecture: source all Version: 0.08250-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: libdbix-class-perl - extensible and flexible object - relational mapper Closes: 735024 Changes: libdbix-class-perl (0.08250-2) unstable; urgency=medium . * Team upload . * add patch adapting tests to DBD::SQLite 1.40 Closes: #735024 -- FTBFS: test failures * add patch fixing POD error about trailing whitespace in a link * Declare conformance with Policy 3.9.5 Checksums-Sha1:
Bug#735312: moodle: deletes files from packages libjs-yui-*
Package: moodle Version: 2.5.3-3 Severity: serious Having libjs-yui-common and libjs-yui-common installed, an upgrade of moodle from 2.5.3-2 to -3 results in loss of a large number of files from these two packages. What I think happens here is that dpkg first sets the symlink of /usr/share/moodle/lib/yuilib/3.9.1/build to /usr/share/javascript/yui3, and then goes on to remove all the files from /u/s/m/lib/yuilib/3.9.1/build/ that are no longer contained in the new version of moodle. It *will* follow the symlink and this results in removal of these files from /usr/share/javascript/yui3 instead. This is perfectly reproducable for me: install -2, then upgrade to -3. dpkg -L libjs-yui3-common | while read f; do [ -e $f ] || echo $f; done will list a lot of missing files afterwards. Apart from being a policy violation this bug also cripples the functionality of moodle itself. My suggestion would be: 1. elide the dir removal from preinst 2. don't include the symlink in the package contents 3. remove the dir and create the symlink in the postinst When transplanting the dir removal code, remember that [ -d ... ] will return true for a symlink to a directory. br, -- Robert Bihlmeyer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734392: Error: Can't connect to unix socket
Paul, I think it's not the server mode. Maybe due to me running everything as root. jcdeb:~# service speech-dispatcher start speech-dispatcher disabled; edit /etc/default/speech-dispatcher jcdeb:~# grep -E (yes)|(no) /etc/init.d/speech-dispatcher | head -1 RUN=no When I log in as a user, the logs appears at /run/user/1000/speech-d... No matter whether I create ~/.speech-dispatcher directory or not. If you think something needs attention, please tell me what new bug report you would like to have. I don't think this one should be extended. Best Jarek -- 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#708123: [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken)
Processing control commands: retitle -1 [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken) Bug #708123 [grub-pc] add news item about end-of-life for old RAID format Changed Bug title to '[grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken)' from 'add news item about end-of-life for old RAID format' severity -1 important Bug #708123 [grub-pc] [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken) Severity set to 'important' from 'critical' tag -1 unreproducible Bug #708123 [grub-pc] [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken) Added tag(s) unreproducible. -- 708123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708123 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#708123: [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken)
Control: retitle -1 [grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken) Control: severity -1 important Control: tag -1 unreproducible On Sat, Dec 21, 2013 at 01:00:10PM -0500, Michael Gilbert wrote: control: retitle -1 add news item about end-of-life for old RAID format On Wed, Dec 18, 2013 at 1:27 PM, Gleb Golubitsky wrote: On Friday, December 06, 2013 12:28:40 PM Colin Watson wrote: Gleb, if you can still reproduce this, could you please run this command I recently reinstalled my Debian (moved i386 - amd64) and the bug is not reproduced any more. Right before that i found out that 'delay' parameter helped me so i suppose the key of problem here is a long time needed by kernel (or somewhat else?) to detect my RAID. Dunno, maybe the bug should be closed as unreproducible. This is an issue only with RAID arrays using a very old format, which it looks like grub now no longer supports. This, I think, can be corrected by writing a news entry about that so users will see the info during an upgrade. No, I do not believe it is intentional that GRUB no longer supports this old format; furthermore, as I said in message #20 on this bug, a simple test with the 0.90 format works fine for me. Thus, not only do we not know exactly what we would write in such a NEWS entry, but it would probably be an inappropriate fix anyway. While I agree that this is a pretty nasty bug if you encounter it, I really need a way to reproduce this in order to fix it; ideally I'd be able to reproduce it in an emulated system so that I can iterate fixes quickly. Perhaps somebody who hasn't made the bug go away on their system could help with this? In the meantime, I don't think it's any more release-critical than any other isolated problem with the boot loader, so I'm downgrading for now to allow 2.00 into testing as on the whole it should be a very significant improvement over 1.99. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718148:
tags 718148 + patch thanks arpon_2.0-2.1ubuntu1.debdiff Description: Binary data
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 718148 + patch Bug #718148 [src:arpon] arpon: FTBFS: Could not find libnet-1.1 Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 718148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718148 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#735329: nss: FTBFS on all arches: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded
Source: nss Version: 2:3.15.4-1 Severity: serious Hi, nss fails to build on all architectures like this: ... # these utilities are too generically-named, so we prefix them with nss- (see http://bugs.debian.org/701141) install -m 755 -T /«PKGBUILDDIR»/dist/bin/addbuiltin debian/libnss3-tools/usr/bin/nss-addbuiltin install -m 755 -T /«PKGBUILDDIR»/dist/bin/dbtest debian/libnss3-tools/usr/bin/nss-dbtest install -m 755 -T /«PKGBUILDDIR»/dist/bin/pp debian/libnss3-tools/usr/bin/nss-pp # Create the empty certificate databases, with empty passphrase mkdir -p debian/tmp echo \n debian/tmp/password LD_LIBRARY_PATH=/«PKGBUILDDIR»/dist/lib /«PKGBUILDDIR»/dist/bin/certutil -N -d debian/libnss3-nssdb/var/lib/nssdb \ -f debian/tmp/password ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored. certutil: function failed: SEC_ERROR_LEGACY_DATABASE: The certificate/key database is in an old, unsupported format. make[1]: *** [override_dh_auto_install] Error 255 make[1]: Leaving directory `/«PKGBUILDDIR»' make: *** [binary-arch] Error 2 ... Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735331: minia: FTBFS on all arches: missing build-dep on bc and zlib1g-dev
Package: minia Version: 1.6067+dfsg-1 Severity: serious Tags: patch Hi, minia fails to build on all architectures like this: ... dh_auto_build -a /bin/sh: 1: bc: not found /bin/sh: 1: bc: not found make[1]: Entering directory `/«BUILDDIR»/minia-1.6067+dfsg' rm -rf *.o g++ -o Pool.o -c Pool.cpp -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O4 -D_FILE_OFFSET_BITS=64 g++ -o Bank.o -c Bank.cpp -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -O4 -D_FILE_OFFSET_BITS=64 In file included from Bank.cpp:21:0: Bank.h:13:63: fatal error: zlib.h: No such file or directory compilation terminated. make[1]: *** [Bank.o] Error 1 make[1]: Leaving directory `/«BUILDDIR»/minia-1.6067+dfsg' ... Adding bc and zlib1g-dev to build-deps helps. Roland -- System Information: Debian Release: 7.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: powerpcspe (ppc) Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735339: Non free w3m valid icons
Package: src:boost1.54 Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free doc/images/valid-html401.png usual name is valid-html401.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735340: Non free w3m valid icons
Package: src:calibre Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free manual/images/valid.png usual name is valid-xhtml10-blue.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons. Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734184: pmv is to blame for this
reassign 734184 mgltools-pmv thanks I think that wrong parameters within a pmv module are the cause of this bug, so I reassign it ... Thorsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735337: Non free w3m valid icons
Package: src:boost1.49 Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free doc/images/valid-html401.png usual name is valid-html401.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735338: Non free w3m valid icons
Package: src:boost1.53 Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free doc/images/valid-html401.png usual name is valid-html401.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735341: Non free w3m valid icons
Package: src:camlp5 Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free: doc/html/images/valid-xhtml11.png usual name is valid-xhtml11.png. The valid w3c icons could not be modified. See also http://www.w3.org/QA/Tools/Icons. Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735342: Non free donate project button
Package: src:cimg Severity: serious User: debian...@debian.org Usertags: license-problem-md5sum-non-free-file X-Debbugs-CC: ftpmas...@debian.org This file is not free, it a donation button from sourceforge without copyright html/img/project-support.jpg usual name is project-support.jpg. Non free logo. Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735119: [icedove] usertag
User debian...@debian.org Usertags 735119 license-problem-md5sum-non-free-file thanks Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735121: [tulip] usertags
User debian...@debian.org Usertags 735121 license-problem-md5sum-non-free-file thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735120: [postfix-cluebringer] usertags
User debian...@debian.org Usertags 735120 license-problem-md5sum-non-free-file thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735345: Sourceless file
Package: src:ckeditor Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-flash-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: samples/plugins/htmlwriter/assets/outputforflash/outputforflash.* Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735344: [chromium-browser] Sourceless file
Package: chromium-browser Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-flash-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: src/third_party/WebKit/ManualTests/plugins/test.swf src/third_party/WebKit/ManualTests/plugins/timeout-dialog-displayed-over-navigation.swf src/third_party/WebKit/ManualTests/resources/spinbox.swf Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735346: Sourceless file
Package: src:glpi Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-flash-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: lib/extjs/resources/charts.swf lib/extjs/resources/expressinstall.swf Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735347: Sourceless file
Package: src:bacula-doc Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-flash-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: home-page/conferences/T5RrEVAzdM4 Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735227: [activemq] usertags
User debian...@debian.org Usertags 735227 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735349: Sourceless file
Package: src:0ad Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: source/tools/jsdebugger/js/lib/jquery-1.8.3.min.js source/tools/jsdebugger/js/lib/jquery.easyui/jquery-1.8.0.min.js I have some doubt about this one (seems to be build from source directory) source/tools/jsdebugger/js/lib/jquery.easyui/jquery.easyui.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735353: Sourceless file
Package: src:boost1.54 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: libs/numeric/ublas/doc/js/jquery-1.3.2.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735354: Sourceless file
Package: src:calibre Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of resources/content_server/jquery.multiselect.min.js resources/content_server/jquery_ui/js/jquery-ui-1.8.5.custom.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735352: Sourceless file
Package: src:boost1.53 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: libs/numeric/ublas/doc/js/jquery-1.3.2.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735350: Sourceless file
Package: src:boost1.49 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: libs/numeric/ublas/doc/js/jquery-1.3.2.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735234: [icedove] usertags
User debian...@debian.org Usertags 735234 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735355: Sourceless file
Package: src:chromium-browser Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org I could not find the source of: src/third_party/flot/excanvas.min.js src/third_party/flot/jquery.colorhelpers.min.js src/third_party/flot/jquery.flot.canvas.min.js src/third_party/flot/jquery.flot.categories.min.js src/third_party/flot/jquery.flot.crosshair.min.js src/third_party/flot/jquery.flot.errorbars.min.js src/third_party/flot/jquery.flot.fillbetween.min.js src/third_party/flot/jquery.flot.image.min.js src/third_party/flot/jquery.flot.min.js src/third_party/flot/jquery.flot.navigate.min.js src/third_party/flot/jquery.flot.pie.min.js src/third_party/flot/jquery.flot.resize.min.js src/third_party/flot/jquery.flot.selection.min.js src/third_party/flot/jquery.flot.stack.min.js src/third_party/flot/jquery.flot.symbol.min.js src/third_party/flot/jquery.flot.threshold.min.js src/third_party/flot/jquery.flot.time.min.js src/third_party/flot/jquery.min.js src/third_party/polymer/polymer.min.js and duplicate here: src/ui/keyboard/resources/polymer.min.js src/depot_tools/third_party/coverage/htmlfiles/jquery-1.4.3.min.js src/depot_tools/third_party/coverage/htmlfiles/jquery.min.js src/depot_tools/third_party/coverage/htmlfiles/jquery.tablesorter.min.js And duplicated: src/third_party/WebKit/PerformanceTests/resources/jquery.flot.min.js src/third_party/WebKit/PerformanceTests/resources/jquery.tablesorter.min.js And: src/third_party/webdriver/test_data/js/jquery-1.4.4.min.js src/third_party/webdriver/test_data/js/jquery-ui-1.8.10.custom.min.js And: src/third_party/trace-viewer/third_party/Promises/polyfill/bin/Promise.min.js And: src/chrome/common/extensions/docs/examples/extensions/benchmark/jquery/jquery-1.8.2.min.js src/chrome/common/extensions/docs/examples/extensions/benchmark/jquery/jquery.flot.min.js src/chrome/common/extensions/docs/examples/extensions/gdocs/js/jquery-1.4.1.min.js src/third_party/WebKit/Tools/Scripts/webkitpy/thirdparty/coverage/htmlfiles/jquery-1.4.3.min.js src/third_party/WebKit/Tools/Scripts/webkitpy/thirdparty/coverage/htmlfiles/jquery.tablesorter.min.js Bastien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735234: [icedove] usertags
User debian...@lists.debian.org Usertags 735234 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735238: ] usertags
User debian...@lists.debian.org Usertags 735238 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735236: [munin] usertags
Package: munin User debian...@lists.debian.org Usertags 735236 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735237: [icedove] usertags
User debian...@lists.debian.org Usertags 735237 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735236: [munin] usertags
Package: munin User debian...@debian.org Usertags 735236 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735238: ] usertags
User debian...@debian.org Usertags 735238 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735237: [icedove] usertags
User debian...@debian.org Usertags 735237 source-contains-prebuilt-javascript-object thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
On Mon, 13 Jan 2014 00:46:55 +0100 Ricardo Mones wrote: [...] On Sun, Jan 12, 2014 at 10:13:43PM +0100, Francesco Poli wrote: [...] You are still using ruby1.8 as system-wide default Ruby interpreter. You should switch to ruby1.9.1 as default interpreter. Well, I have what it's pulled by apt-listbugs dependencies, which IMO should be able to pull the version of the interpreter necessary to run it, even if that includes switching default ruby. Please let me clarify: apt-listbugs depends on ruby | ruby-interpreter and that's correct. It works fine with both ruby1.8 and ruby1.9.1, as long as the required libraries support the chosen Ruby interpreter. The fact is that ruby1.8 is deprecated and no longer supported upstream: there's an ongoing transition to remove it from Debian. Architecture-dependent Ruby libraries (such as ruby-debian) are being recompiled without support for ruby1.8: that's the reason why apt-listbugs stopped working with ruby1.8. In order to fix this situation, ruby1.8 no longer provides ruby-interpreter, so that packages like apt-listbugs will pull in some other Ruby interpreter (such as ruby1.9.1). This has already been implemented in ruby1.8/1.8.7.358-10 As I have already said, I think there's one last aspect to fix: ruby1.8 should remove itself from the list of possible alternatives for /usr/bin/ruby. Dear ruby1.8 maintainers, do you agree? The following steps should hopefully fix the issue for you: […] At this point you should be again able to upgrade or install packages while using apt-listbugs. Please let me know, if something went wrong. Workaround worked fine, many thanks for the quick response. You're welcome, I am glad that the issue is fixed for you. Bye. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpPPs58yP__k.pgp Description: PGP signature
Processed: Re: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.
Processing commands for cont...@bugs.debian.org: clone 735336 -1 Bug #735336 [git-svn] git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042. Bug 735336 cloned as bug 735358 reassign 735336 git 1:1.8.5.2-1 Bug #735336 [git-svn] git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042. Bug reassigned from package 'git-svn' to 'git'. No longer marked as found in versions git/1:1.7.10.4-1+wheezy1. Ignoring request to alter fixed versions of bug #735336 to the same values previously set Bug #735336 [git] git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042. Marked as found in versions git/1:1.8.5.2-1. retitle 735336 [1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit Bug #735336 [git] git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042. Changed Bug title to '[1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit' from 'git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.' severity 735336 serious Bug #735336 [git] [1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit Severity set to 'serious' from 'important' tags 735336 + upstream Bug #735336 [git] [1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit Added tag(s) upstream. quit Stopping processing here. Please contact me if you need assistance. -- 735336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735336 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: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.
Processing commands for cont...@bugs.debian.org: retitle 735336 [1.8.4.1-1.8.4.2 regression] git: 'error Missing tree' when pushing to gerrit Bug #735336 [git] [1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit Changed Bug title to '[1.8.4.1-1.8.4.2 regression] git: 'error Missing tree' when pushing to gerrit' from '[1.8.5.1-1.8.5.2 regression] git: 'error Missing tree' when pushing to gerrit' End of message, stopping processing here. Please contact me if you need assistance. -- 735336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735336 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#735336: git-svn fails 'tempfile' can't be called as a method at /usr/share/perl5/Git.pm line 1042.
Jonathan Nieder wrote: James Michael DuPont wrote: I am forced to use an older version of git because of the problems with gerrit. http://stackoverflow.com/questions/16586642/git-unpack-error-on-push-to-gerrit That is why I instlled the older version of git. Let's start with that. Can you provide a simple recipe to reproduce the problem? Also, when did you start experiencing the problem? Did it coincide with a git upgrade? Curious, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726838: mplayer depends upon old libavutil under unstable
Removing mplayer in favour of mplayer2 seems to be quite a bad idea,... as the later seems to be more or less dead upstream, while the former is actively developed. So this is probably a no-go. It should be mentioned btw, that the mplayer and mplayer2 packages from DMO just work fine (and can even be installed concurrently),... so I wonder a bit why the ones from Debian can't. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735361: request-tracker4: FTBFS: GPG test failures
Source: request-tracker4 Version: 4.0.18-1 Severity: serious Justification: FTBFS During the Debian packaging of RT 4.0.19 I discovered some unrelated breakage. The behaviour of GnuPG 1.4.16 has changed with respect to trustdb creation. From the changelog: Noteworthy changes in version 1.4.16 (2013-12-18) - ... * Do not create a trustdb file if --trust-model=always is used. This appears to break the RT tests, which use this parameter: $ prove -l t/mail/gnupg-outgoing-plain.t t/mail/gnupg-outgoing-plain.t .. secmem usage: 1440/1440 bytes in 3/3 blocks of pool 1440/32768 gpg: keyring `/tmp/F0SIjsbMXb/secring.gpg' created gpg: keyring `/tmp/F0SIjsbMXb/pubring.gpg' created gpg: key C2274A26: secret key imported gpg: fatal: can't open `/tmp/F0SIjsbMXb/trustdb.gpg': No such file or directory secmem usage: 1440/1440 bytes in 3/3 blocks of pool 1440/32768 gpg: fatal: can't open `/tmp/F0SIjsbMXb/trustdb.gpg': No such file or directory t/mail/gnupg-outgoing-plain.t .. 40/104 secmem usage: 1440/1440 bytes in 3/3 blocks of pool 1440/32768 gpg: keyring `/tmp/F0SIjsbMXb/secring.gpg' created gpg: keyring `/tmp/F0SIjsbMXb/pubring.gpg' created gpg: fatal: can't open `/tmp/F0SIjsbMXb/trustdb.gpg': No such file or directory secmem usage: 1440/1440 bytes in 3/3 blocks of pool 1440/32768 gpg: key 84881F1B: secret key imported gpg: fatal: can't open `/tmp/F0SIjsbMXb/trustdb.gpg': No such file or directory t/mail/gnupg-outgoing-plain.t .. 95/104 # Failed test 'no warnings' # at /home/dom/working/pkg-request-tracker-git/request-tracker4/lib/RT/Test.pm line 1610. # There were 8 warning(s) I think this is related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725889 but I'm not sure of the details, so I will file a bug against gnupg next. Dominic. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 735361 with 735363
Processing commands for cont...@bugs.debian.org: block 735361 with 735363 Bug #735361 [src:request-tracker4] request-tracker4: FTBFS: GPG test failures 735361 was not blocked by any bugs. 735361 was not blocking any bugs. Added blocking bug(s) of 735361: 735363 thanks Stopping processing here. Please contact me if you need assistance. -- 735361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735361 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#735361: [request-tracker-maintainers] Bug#735361: request-tracker4: FTBFS: GPG test failures
On Wed, Jan 15, 2014 at 12:25:23AM +, Dominic Hargreaves wrote: This appears to break the RT tests, which use this parameter: Just to be clear: since trust-model=always is only used in the test suite, I don't believe this issue affects running installations. Dominic. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735364: libosl uses inappropriate compiler flags.
Package: libosl Severity: serious libosl builds on i386 seem to use a mixture of -march=native and -march=pentium4, neither is appropriate for debian since i386 is supposed to support much lower processors (not sure offhand what exactly the minimum is supposed to be but I knot it's well below pentium 4). In general -march=native should never be used in debian because it causes the produced binaries to depend on the CPU in the build machine. Other -march values should generally only be used in combination with some mechanism for runtime hardware detection. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735254: flash-kernel: QNAP TS-212 doesn't boot with 3.12-1-kirkwood and flash-kernel 3.12
Package: src:linux Followup-For: Bug #735254 I can confirm this issue on a TS-219. Adding DTB-Append-From: 3.12 and DTB-Id: kirkwood-ts219-6281.dtb in the apropriate place in all.db solves the issue parially and maybe only for a TS-219 (with Soc: 88F6281) reflashing with kernel 3.12 fails because machine name has changed in device-tree. GRTNX, RobJE -- Package-specific info: ** Version: Linux version 3.12-0.bpo.1-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.12.6-2~bpo70+1 (2014-01-07) ** Command line: console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=32768 ** Not tainted ** Kernel log: [3.900913] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [3.909162] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [3.918222] sd 1:0:0:0: [sdb] Write Protect is off [3.923062] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [3.923080] sd 0:0:0:0: [sda] Write Protect is off [3.927907] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.928101] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.937219] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.979606] sdb: sdb1 sdb2 [3.983167] sda: sda1 sda2 [3.988464] sd 1:0:0:0: [sdb] Attached SCSI disk [3.993485] sd 0:0:0:0: [sda] Attached SCSI disk [4.376216] md: md0 stopped. [4.389290] md: bindsdb1 [4.400689] md: bindsda1 [4.424002] md: raid1 personality registered for level 1 [4.430355] md/raid1:md0: active with 2 out of 2 mirrors [4.435839] md0: detected capacity change from 0 to 999692173312 [4.442193] RAID1 conf printout: [4.442204] --- wd:2 rd:2 [4.442213] disk 0, wo:0, o:1, dev:sda1 [4.442221] disk 1, wo:0, o:1, dev:sdb1 [4.455950] md0: unknown partition table [4.479595] device-mapper: uevent: version 1.0.3 [4.487015] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-de...@redhat.com [4.591082] bio: create slab bio-1 at 1 [4.769140] EXT4-fs (dm-0): mounting ext3 file system using the ext4 subsystem [4.790586] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) [6.614941] udevd[308]: starting version 175 [6.788375] input: gpio_keys.3 as /devices/gpio_keys.3/input/input0 [7.048864] orion_wdt: Initial timeout 21 sec [7.145097] usbcore: registered new interface driver usbfs [7.201410] usbcore: registered new interface driver hub [7.238630] usbcore: registered new device driver usb [7.296547] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [7.368172] ehci-orion: EHCI orion driver [7.488089] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [7.525959] libphy: orion_mdio_bus: probed [7.531214] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral [8.113648] orion-ehci f105.ehci: EHCI Host Controller [8.640122] orion-ehci f105.ehci: new USB bus registered, assigned bus number 1 [8.675746] orion-ehci f105.ehci: irq 24, io mem 0xf105 [8.714355] orion-ehci f105.ehci: USB 2.0 started, EHCI 1.00 [8.724536] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [8.731476] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [8.738764] usb usb1: Product: EHCI Host Controller [8.743676] usb usb1: Manufacturer: Linux 3.12-0.bpo.1-kirkwood ehci_hcd [8.750423] usb usb1: SerialNumber: f105.ehci [8.765609] hub 1-0:1.0: USB hub found [8.781263] hub 1-0:1.0: 1 port detected [8.881220] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:08:9b:8c:76:74 [9.113277] usb 1-1: new high-speed USB device number 2 using orion-ehci [9.262757] usb 1-1: New USB device found, idVendor=058f, idProduct=6254 [9.269532] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [9.294392] hub 1-1:1.0: USB hub found [9.306943] hub 1-1:1.0: 4 ports detected [ 10.155923] Adding 498008k swap on /dev/sda2. Priority:-1 extents:1 across:498008k [ 10.201882] Adding 498008k swap on /dev/sdb2. Priority:-2 extents:1 across:498008k [ 10.237460] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 10.575063] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro [ 10.925312] loop: module loaded [ 18.978766] EXT4-fs (dm-1): mounting ext3 file system using the ext4 subsystem [ 19.033688] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 19.059890] EXT4-fs (dm-2): mounting ext3 file system using the ext4 subsystem [ 19.117530] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 19.145071] EXT4-fs (dm-7): mounting ext3 file system using the ext4 subsystem [ 19.175291] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: (null) [ 19.199526] EXT4-fs (dm-6): mounting ext3 file
Bug#735366: libnet-twitter-perl: 403 Forbidden or certificate error due to SSL/TLS traffic restriction
Package: libnet-twitter-perl Version: 4.01000-1 Severity: grave Justification: renders package unusable The Net::Twitter module suddenly stopped working on 2014-01-14 at about 19:30 UTC. I now also get 403 Forbidden errors. The cause is a change in the Twitter API: https://dev.twitter.com/discussions/24239 In the discussion: @newsytweets News As It Happens I am positive that I am using the https endpoint, but still getting 403 error code. Anyone else seeing the same problem? I am using Net::Twitter perl module. I checked the source code and it is indeed using https. @Cornel74 Cornel van Mastrigt I had a similar problem you could try the apiurl parameter to supply an alternative API url. It seems to be defaulting to http://api.twitter.com/1 I fixed my 403 errors by adding: apiurl = 'https://api.twitter.com/1.1' @newsytweets News As It Happens @cornel74 you are a lifesaver! Thanks. I've tried the apiurl = 'https://api.twitter.com/1.1' solution (I'm wondering why it wasn't done by default before!) but I still get an error: 500 Can't connect to api.twitter.com:443 (certificate verify failed) So, there are 2 problems: 1. The default apiurl that is now broken (it was insecure before). 2. The certificate error (for this one, I don't know which package is in fault). This bug report might be cloned after identifying the exact problem for (2), if not in libnet-twitter-perl. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnet-twitter-perl depends on: ii libcarp-clan-perl 6.04-1 ii libclass-load-perl 0.20-1 ii libcrypt-ssleay-perl 0.58-1+b1 ii libdata-visitor-perl 0.30-1 ii libdatetime-format-strptime-perl 1.5400-1 ii libdatetime-perl 2:1.06-1 ii libdevel-stacktrace-perl 1.3000-1 ii libdigest-hmac-perl1.03+dfsg-1 ii libhtml-parser-perl3.71-1+b1 ii libjson-perl 2.61-1 ii liblwp-protocol-https-perl 6.04-2 ii libmoose-perl 2.1005-1+b1 ii libmoosex-role-parameterized-perl 1.02-1 ii libnamespace-autoclean-perl0.15-1 ii libnet-http-perl 6.06-1 ii libnet-oauth-perl 0.28-1 ii libtry-tiny-perl 0.18-1 ii liburi-perl1.60-1 ii libwww-perl6.05-2 ii perl 5.18.1-5 libnet-twitter-perl recommends no packages. libnet-twitter-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#735366: libnet-twitter-perl: 403 Forbidden or certificate error due to SSL/TLS traffic restriction
On 2014-01-15 01:58:16 +0100, Vincent Lefevre wrote: 2. The certificate error (for this one, I don't know which package is in fault). Concerning this error, there's information on: https://dev.twitter.com/docs/security/using-ssl -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735367: bti: stopped working after SSL/TLS traffic restriction, due to obsolete URL
Package: bti Version: 033-2 Severity: grave Justification: renders package unusable $ bti --config .bti-twitter --action friends Error retrieving from URL (http://api.twitter.com/1.1/statuses/home_timeline.json?page=1) operation failed This URL is no longer valid: it has been forbidden for a few hours. See https://dev.twitter.com/discussions/24239 This is an important notice for developers still using HTTP plaintext connections. On January 14th, 2014, connections to api.twitter.com will be restricted to TLS/SSL connections only. If your application still uses HTTP plaintext connections you will need to update it to use HTTPS connections, otherwise your app will stop functioning. You don't need to wait until deadline to implement this change, given that api.twitter.com already supports the recommended environment. This SSL requirement will be enforced on all api.twitter.com URLs, including all steps of OAuth and all REST API resources. [...] In case there are certificate problems like with libnet-twitter-perl, please see: https://dev.twitter.com/docs/security/using-ssl -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bti depends on: ii libc62.17-97 ii libcurl3-gnutls 7.34.0-1 ii libjson-c2 0.11-3 ii liboauth01.0.1-1 ii libpcre3 1:8.31-2 ii libxml2 2.9.1+dfsg1-3 bti recommends no packages. Versions of packages bti suggests: ii bash-completion 1:2.1-2 -- 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#735368: meep appears to use -march=native
Package: meep Severity: serious From the i386 build log for meep: checking whether C++ compiler accepts -march=native... yes checking for gcc architecture flag... -march=native checking whether C++ compiler accepts -O3 -malign-double -fstrict-aliasing -march=native... yes Unfortunately the flags actually passed to the compiler are hidden in the build log so I can't be absoloutely certain this is not a false positive but a quick grep of the source tree makes me think it is more likely than not that -march=native is actually being used. -march=native is not appropriate for distro packaging as it makes the results of the build dependent on what CPU happens to be in the build machine and means that the resulting binaries are unlikely to work on the minimum CPU supported for the port. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735369: meep appears to use -march=native
Package: meep-openmpi Severity: serious From the kfreebsd-i386 build log for meep-openmpi: checking whether C++ compiler accepts -march=native... yes checking for gcc architecture flag... -march=native checking whether C++ compiler accepts -O3 -malign-double -fstrict-aliasing -march=native... yes Unfortunately the flags actually passed to the compiler are hidden in the build log so I can't be absoloutely certain this is not a false positive but a quick grep of the source tree makes me think it is more likely than not that -march=native is actually being used. -march=native is not appropriate for distro packaging as it makes the results of the build dependent on what CPU happens to be in the build machine and means that the resulting binaries are unlikely to work on the minimum CPU supported for the port. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729827: marked as done (django-oauth-plus: FTBFS with django 1.6)
Your message dated Wed, 15 Jan 2014 01:48:21 +
with message-id e1w3faf-0007cd...@franck.debian.org
and subject line Bug#729827: fixed in django-oauth-plus 2.2.3-1
has caused the Debian Bug report #729827,
regarding django-oauth-plus: FTBFS with django 1.6
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.)
--
729827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: django-oauth-plus
Version: 2.1.5-1
Severity: serious
Justification: fails to build from source
Tags: sid jessie
django-oauth-plus fails to build with django 1.6:
|debian/rules override_dh_auto_test
| make[1]: Entering directory `/«PKGBUILDDIR»'
| set -e ; \
| python /«PKGBUILDDIR»/oauth_provider/runtests/runtests.py
| Traceback (most recent call last):
| File /«PKGBUILDDIR»/oauth_provider/runtests/runtests.py, line 44, in
module
| main()
| File /«PKGBUILDDIR»/oauth_provider/runtests/runtests.py, line 39, in main
| failures = test_runner.run_tests(['tests' + test_case])
| File /usr/lib/python2.7/dist-packages/django/test/runner.py, line 144, in
run_tests
| suite = self.build_suite(test_labels, extra_tests)
| File /usr/lib/python2.7/dist-packages/django/test/runner.py, line 63, in
build_suite
| tests = self.test_loader.loadTestsFromName(label)
| File /usr/lib/python2.7/unittest/loader.py, line 91, in loadTestsFromName
| module = __import__('.'.join(parts_copy))
| ImportError: No module named tests
| make[1]: *** [override_dh_auto_test] Error 1
Full build is available at
http://people.debian.org/~sramacher/logs/django-1.6/django-oauth-plus_2.1.5-1_amd64.log
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: django-oauth-plus
Source-Version: 2.2.3-1
We believe that the bug you reported is fixed in the latest version of
django-oauth-plus, 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 729...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Kouhei Maeda mkou...@palmtb.net (supplier of updated django-oauth-plus
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 15 Jan 2014 06:54:21 +0900
Source: django-oauth-plus
Binary: python-django-oauth-plus
Architecture: source all
Version: 2.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda mkou...@palmtb.net
Changed-By: Kouhei Maeda mkou...@palmtb.net
Description:
python-django-oauth-plus - Support of OAuth 1.0a in Django using python-oauth2
Closes: 729827
Changes:
django-oauth-plus (2.2.3-1) unstable; urgency=medium
.
* New upstream release
* Fixed FTBFS with django 1.6 (Closes: #729827)
- debian/rules:
* Append PYTHONPATH=$(CURDIR)/oauth_provider at
override_dh_auto_test section.
* debian/control:
- Standards-Version: Update 3.9.4 to 3.9.5.
- Build-Depends: Append quilt.
* debian/copyright: Add Alex Irpan, Changhwan Song.
* debian/rules:
- Append quilt option to dh command at % section.
* debian/patches:
- append_egg-info:
* Append DEP3 headers
* Update timestamp, and update PKG-INFO and SOURCES.txt.
- add_setuptools_hg: Append DEP3 headers, and update timestamp.
Checksums-Sha1:
95c589d734893682cb5c2cb90618795b9840e654 1939 django-oauth-plus_2.2.3-1.dsc
63859f37c1d69f5cf7ef597a92eb6d0e5008394d 25684
django-oauth-plus_2.2.3.orig.tar.gz
7ff505daeb9bd88f7e1f5761b0f654d9ddd6e928 6359
django-oauth-plus_2.2.3-1.debian.tar.gz
359a2c91385ed6a4717e1584859da588dbc20bf0 25726
python-django-oauth-plus_2.2.3-1_all.deb
Checksums-Sha256:
73aede7dd6bd7a9b238b29267820a0593c50eeb080298b2ea26a314b4fc4089c 1939
django-oauth-plus_2.2.3-1.dsc
645ddca43dd19cfdd530710cba7916969d3b42f18ad62aa697fec9670d112e94 25684
django-oauth-plus_2.2.3.orig.tar.gz
9f5e7e6f45494e463e4be4740ee83537baa7d971e19e216f70954504c3ea20a8 6359
django-oauth-plus_2.2.3-1.debian.tar.gz
be9e41e681f57c973f9a0ec90b0db3b58a833d1e234e435d3ef49e697ab45eea 25726
python-django-oauth-plus_2.2.3-1_all.deb
Files:
386c73bc907a7511d3cf95931f11f8d7 1939 python optional
Bug#735151: marked as done (wine: fails to upgrade from 'testing' - trying to overwrite '/usr/share/man/de.UTF-8/man1/wineserver.1.gz', which is also in package libwine 1.4.1-4)
Your message dated Wed, 15 Jan 2014 03:20:39 + with message-id e1w3h1z-yf...@franck.debian.org and subject line Bug#735151: fixed in wine 1.6.2-2 has caused the Debian Bug report #735151, regarding wine: fails to upgrade from 'testing' - trying to overwrite '/usr/share/man/de.UTF-8/man1/wineserver.1.gz', which is also in package libwine 1.4.1-4 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.) -- 735151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: wine Version: 1.6.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Preparing to unpack .../wine_1.6.2-1_amd64.deb ... Unpacking wine (1.6.2-1) over (1.4.1-4) ... Replacing files in old package libwine-bin:i386 (1.4.1-4) ... dpkg: error processing archive /var/cache/apt/archives/wine_1.6.2-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/de.UTF-8/man1/wineserver.1.gz', which is also in package libwine 1.4.1-4 cheers, Andreas wine_1.6.2-1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: wine Source-Version: 1.6.2-2 We believe that the bug you reported is fixed in the latest version of wine, 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 735...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated wine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Jan 2014 02:13:44 + Source: wine Binary: wine wine32 wine64 wine32-dev-tools wine64-dev-tools libwine-dev libwine-dbg libwine wine-bin wine64-bin libwine-alsa libwine-bin libwine-capi libwine-cms libwine-gl libwine-gphoto2 libwine-ldap libwine-openal libwine-oss libwine-print libwine-sane Architecture: source amd64 Version: 1.6.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Wine Party pkg-wine-pa...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: libwine- Windows API implementation - library libwine-alsa - Windows API implementation - ALSA sound module libwine-bin - Windows API implementation - system services libwine-capi - Windows API implementation - ISDN module libwine-cms - Windows API implementation - color management module libwine-dbg - Windows API implementation - debugging symbols libwine-dev - Windows API implementation - development files libwine-gl - Windows API implementation - OpenGL module libwine-gphoto2 - Windows API implementation - camera module libwine-ldap - Windows API implementation - LDAP module libwine-openal - Windows API implementation - OpenAL module libwine-oss - Windows API implementation - OSS sound module libwine-print - Windows API implementation - printing module libwine-sane - Windows API implementation - scanner module wine - Windows API implementation - standard suite wine-bin - Windows API implementation - binaries wine32 - Windows API implementation - 32-bit binary loader wine32-dev-tools - Windows API implementation - 32-bit developer tools wine64 - Windows API implementation - 64-bit binary loader wine64-bin - Windows API implementation - 64-bit helper wine64-dev-tools - Windows API implementation - 64-bit developer tools Closes: 735151 Changes: wine (1.6.2-2) unstable; urgency=medium . * Indicate that wine replaces files in libwine and wine-bin (closes: #735151). Checksums-Sha1: cb8d7ad815319d8243bf5b0ce38ecd31167b3063 4300 wine_1.6.2-2.dsc 46bbee908e18da1493a19a7d65d19d40c9ed2e9b 64063 wine_1.6.2-2.debian.tar.gz 3b85d7252a7ae5b65068468ea3a6ba0798ec1837 101216 wine_1.6.2-2_amd64.deb 6b1c5e506d9021e7e52cfa24846e17fc54f44bf7 68186
Processed: Re: Bug#735366: libnet-twitter-perl: 403 Forbidden or certificate error due to SSL/TLS traffic restriction
Processing control commands: forwarded -1 https://github.com/semifor/Net-Twitter/issues/37 Bug #735366 [libnet-twitter-perl] libnet-twitter-perl: 403 Forbidden or certificate error due to SSL/TLS traffic restriction Set Bug forwarded-to-address to 'https://github.com/semifor/Net-Twitter/issues/37'. tag -1 + upstream Bug #735366 [libnet-twitter-perl] libnet-twitter-perl: 403 Forbidden or certificate error due to SSL/TLS traffic restriction Added tag(s) upstream. -- 735366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735366 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
