Control: forward -1 https://bugs.kde.org/show_bug.cgi?id=327377
Control: severity -1 important
On Sat, 9 Nov 2013 15:53:04 Rainer Dorsch wrote:
> Upgrade: digikam-private-libs:i386 (3.4.0-1, 3.5.0-2), digikam:i386
> (3.4.0-1, 3.5.0-2), digikam-data:i386 (3.4.0-1, 3.5.0-2)
Rainer,
I see you have
Processing control commands:
> forward -1 https://bugs.kde.org/show_bug.cgi?id=327377
Unknown command or malformed arguments to command.
> severity -1 important
Bug #729119 [digikam] digikam: Upgrade to Digikam 3.5 makes all albums disappear
Severity set to 'important' from 'grave'
--
729119: h
Hi,
Although fixing this serious bug is not a big deal but another NMU for
very outdated version does not make much sense to me.
I tried newer 0.11.4-0ubuntu5 Ubuntu source package which builds OK.
https://launchpad.net/sbackup
https://launchpad.net/ubuntu/+source/sbackup
(I see some rooms fo
Processing commands for cont...@bugs.debian.org:
> found 726724 0.99.20.1-0+squeeze3
Bug #726724 {Done: Christian Hammers } [quagga] quagga:
CVE-2013-2236
Marked as found in versions quagga/0.99.20.1-0+squeeze3.
> found 726724 0.99.21-3~bpo60+1
Bug #726724 {Done: Christian Hammers } [quagga] quag
Hi Alberto or other maintainers,
Please consider making a small upload/NMU with just Rebecca's patch to
fix the immediate FTBFS. Then perhaps wait for the libav9 transition to
finish before uploading the new upstream version 3.2?
Rebecca's patch (taken verbatim from link below) fixes the build a
On 10/11/2013 00:18, Steven Chamberlain wrote:
>> - elflint doesn't know about the OS ABI "FreeBSD".
>> - Is this correct in the ELF files?
Yes.
>> I don't know whether
>> kfreebsd is supposed to follow the user space ELF OS ABI
>> or the kernel one.
I'm not sure what you
Currently I see some different testsuite failures than before. This was
in a sid chroot on kfreebsd-amd64 (not using bind mounts) :
run-native-test.sh passes for me.
> FAIL: run-disasm-x86.sh
that failure is new.
> ../config/test-driver: line 95: 44771 Segmentation fault "$@" >
> $log_fi
Hi,
debian-bsd@ was not put in Cc: for this bug, so the recent discussion
was probably not seen yet by people who can answer:
On Tue, 22 Oct 2013 16:02:18 +0200, Mark Wielaard wrote:
> Two questions:
>
> - Would it help to just disable the testsuite on the kfreebsd arch?
> Clearly the package
Package: tar
Version: 1.27-1
Severity: serious
Justification: FTBFS
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
tar FTBFS since 1.27-1 due to failure of extrac09.at in the testsuite.
The problem occurred only on kFreeBSD and Hurd but I could
Processing commands for cont...@bugs.debian.org:
> block 720911 with 674930
Bug #720911 [ftp.debian.org] RM: openjdk-6 -- ROM; openjdk-7 replaces it
720911 was blocked by: 720572 720571 717122 720570 717249 720552 720557 727805
720551 720573 720569 727791 727806 720561 683450 727789
720911 was no
On 08.11.2013 22:35, Niels Thykier wrote:
> However, sleuthkit suffers from #713364 which is a FTBFS bug, so I
> have no reason to believe a binNMU will be successful.
[...]
> Comments welcome, a fix for #713364 in sid (or deferred) even more so.
I have taken the 2 patches from upstream that I
Processing commands for cont...@bugs.debian.org:
> tags 729119 + moreinfo
Bug #729119 [digikam] digikam: Upgrade to Digikam 3.5 makes all albums disappear
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
729119: http://bugs.debian.org/cgi-bin
Your message dated Sat, 09 Nov 2013 21:27:44 +
with message-id
and subject line Bug#729172: fixed in spip 3.0.12-1
has caused the Debian Bug report #729172,
regarding Security update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Sat, 09 Nov 2013 21:24:51 +
with message-id
and subject line Bug#729029: fixed in openssh 1:6.4p1-1
has caused the Debian Bug report #729029,
regarding openssh-server: fatal xfree error when RekeyLimit hit with GCM
to be marked as done.
This means that you claim that the pr
Your message dated Sat, 09 Nov 2013 21:27:26 +
with message-id
and subject line Bug#729172: fixed in spip 2.1.24-1
has caused the Debian Bug report #729172,
regarding Security update
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Sat, 09 Nov 2013 21:24:51 +
with message-id
and subject line Bug#729029: fixed in openssh 1:6.4p1-1
has caused the Debian Bug report #729029,
regarding openssh: CVE-2013-4548: Memory corruption in AES-GCM support
to be marked as done.
This means that you claim that the prob
Your message dated Sat, 09 Nov 2013 21:24:51 +
with message-id
and subject line Bug#729029: fixed in openssh 1:6.4p1-1
has caused the Debian Bug report #729029,
regarding Memory corruption vulnerability when using AES-GCM
to be marked as done.
This means that you claim that the problem has be
Processing commands for cont...@bugs.debian.org:
> reassign 726818 openssh
Bug #726818 [openssh-server] openssh-server: fatal xfree error when RekeyLimit
hit with GCM
Bug reassigned from package 'openssh-server' to 'openssh'.
No longer marked as found in versions openssh/1:6.2p2-6.
Ignoring reque
On Sat, Nov 9, 2013 at 3:25 PM, Adrian Bunk wrote:
> Hi Michael,
>
> your #728444 hack is extremely ugly, and it is unclear how bad the
> performance penalty for this hack is.
fontconfig was without pthreads for its lifetime prior to 2.11, so
there won't be any performance regressions. Granted pt
Processing commands for cont...@bugs.debian.org:
> forcemerge 729029 726818
Bug #729029 [openssh] openssh: CVE-2013-4548: Memory corruption in AES-GCM
support
Bug #729148 [openssh] Memory corruption vulnerability when using AES-GCM
Unable to merge bugs because:
package of #726818 is 'openssh-serv
Processing commands for cont...@bugs.debian.org:
> reopen 725516 =
Bug #725516 {Done: Mikolaj Izdebski } [lbzip2] lbzip2:
FTBFS: problems running testsuite
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Hi Michael,
your #728444 hack is extremely ugly, and it is unclear how bad the
performance penalty for this hack is.
I am myself an xpdf user affected by this bug, but it seems clear that
there are libpoppler issues that have to be sorted out in xpdf, instead
of ugly hacks like this (that coul
Processing commands for cont...@bugs.debian.org:
> #spip (3.0.12-1) experimental; urgency=low
> #
> # * Imported Upstream version 3.0.12 (Closes: #729172)
> #
> limit source spip
Limiting to bugs with field 'source' containing at least one of 'spip'
Limit currently set to 'source':'spip'
> tags
Processing commands for cont...@bugs.debian.org:
> notfixed 644203 libwebkitgtk-1.0-0/1.7.91-1
Bug #644203 {Done: Gustavo Noronha Silva }
[libwebkitgtk-1.0-0] recommend gstreamer0.10-plugins-good and
gstreamer0.10-ffmpeg
The source libwebkitgtk-1.0-0 and version 1.7.91-1 do not appear to match a
Processing control commands:
> severity -1 important
Bug #728843 [nvidia-driver] nvidia-driver: Changing sound on keyboard or
launching remmina crashes X
Severity set to 'important' from 'grave'
> tag -1 upstream moreinfo
Bug #728843 [nvidia-driver] nvidia-driver: Changing sound on keyboard or
l
Control: severity -1 important
Control: tag -1 upstream moreinfo
On 2013-11-06 08:53, Crispy wrote:
> Package: nvidia-driver
> Version: 319.60-2
> Versions of packages nvidia-driver depends on:
> ii libc6 2.17-93
> pn libgl1-nvidia-glx
Your message dated Sat, 09 Nov 2013 19:48:45 +
with message-id
and subject line Bug#728044: fixed in cmucl 20c-2.1
has caused the Debian Bug report #728044,
regarding FTBFS: building docs results in endless loop
to be marked as done.
This means that you claim that the problem has been dealt w
Processing control commands:
> found -1 2.1.1-3squeeze6
Bug #729172 [spip] Security update
Marked as found in versions spip/2.1.1-3squeeze6.
> found -1 2.1.17-1+deb7u1
Bug #729172 [spip] Security update
Marked as found in versions spip/2.1.17-1+deb7u1.
> found -1 2.1.23-1
Bug #729172 [spip] Securi
Package: spip
Version: 3.0.11-1
Severity: critical
Tags: security upstream
Control: found -1 2.1.1-3squeeze6
Control: found -1 2.1.17-1+deb7u1
Control: found -1 2.1.23-1
Hi, the latest SPIP upstream update fixes various security issues. The
stable and oldstable security update are currently deal
Processing commands for cont...@bugs.debian.org:
> # Saturday 9 November 19:03:11 UTC 2013
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: href="http://packages.qa.debian.org/freerdp";>freerdp
> tags 729044 +
Package: icedove
Version: 24.0-1
Severity: serious
icedove-dev claims to require linking against libxpcom.so, however it does not
exist:
$ grep Libs /usr/lib/pkgconfig/icedove.pc
Libs: -L${libdir} -lxpcomglue_s -lxul -lxpcom -lmozjs -lmozalloc -lldap60
-lprldap60
$ locate libxpcom.so
/usr/lib/
Your message dated Sat, 09 Nov 2013 18:34:52 +
with message-id
and subject line Bug#712338: fixed in gnugo 3.8-6
has caused the Debian Bug report #712338,
regarding gnugo: FTBFS: manuals build fails against textinfo5 because some
incompatibles changes wrt 4.13 and below (some warnings have tu
control: tag -1 pending
On Sat, Nov 2, 2013 at 4:30 PM, Michael Gilbert wrote:
> control: tag -1 patch
>
> Hi, this results from upstream enabling pthreads in 2.11. I've
> attached a patch to disable pthreads until a more permanent solution
> is found for xpdf.
Hi, I've uploaded an nmu with the
Processing control commands:
> tag -1 pending
Bug #728444 [libfontconfig1] libfontconfig1: xpdf is broken by fontconfig
version 2.11.0-1
Added tag(s) pending.
--
728444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Package: xpdf
Version: 3.03-11
Followup-For: Bug #727202
Additional info:
xpdf run without any file args starts fine, the crash happens only when opening
a file.
Backtrace from the core file:
Core was generated by `xpdf.real'.
Program terminated with signal 6, Aborted.
#0 0x7f8c7a1c61e5 i
package: scilab-scimax
version: 2.1.4-3
severity: serious
Hi,
It seems scilab-scimax FTBFS on i386, armel, armhf:
https://buildd.debian.org/status/package.php?p=scilab-scimax
Cheers,
Ivo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
package: libbuffy-bindings
version: 0.15
severity: serious
Hi,
It seems libbuffy-bindings can't build on kfreebsd anymore, because
libbuffy-dev isn't there anymore. The architecture list for libbuffy-bindings
should probably be updated accordingly.
Please note that there still needs to be a remo
package: mricron
version: 0.20130828.1~dfsg.1-1
severity: serious
Hi,
It seems mricron FTBFS on armhf, powerpc, sparc (but it did so before):
https://buildd.debian.org/status/package.php?p=mricron
Cheers,
Ivo
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
Your message dated Sat, 09 Nov 2013 17:34:16 +
with message-id
and subject line Bug#724865: fixed in gcc-4.6 4.6.4-5
has caused the Debian Bug report #724865,
regarding gcc-4.6: FTBFS: Unsatisfiable Build-Conflicts on binutils-gold
to be marked as done.
This means that you claim that the prob
package: gdb-msp430
version: 7.2a~mspgcc-20111205-2
severity: serious
Hi,
The latest upload of gdb-msp430 cannot build on ia64, as libunwind8-dev is not
co-installable with gcc on ia64:
https://buildd.debian.org/status/package.php?p=gdb-msp430
Given that gdb-msp430 is only available on a limited
Processing control commands:
> reassign -1 openssh 1:6.2p2-6~bpo70+1
Bug #729148 [openssh-server] Memory corruption vulnerability when using AES-GCM
Bug reassigned from package 'openssh-server' to 'openssh'.
No longer marked as found in versions 1:6.2p2-6~bpo7.
Ignoring request to alter fixed vers
Control: reassign -1 openssh 1:6.2p2-6~bpo70+1
Control: forcemerge -1 729029
On Sat, Nov 09, 2013 at 10:54:33AM -0500, GUO Yixuan wrote:
> This seems to be the same as #729029?
Indeed it is, though a useful reminder that I'll need to update the
version in backports as well once this is in unstabl
Hi,
On Sat, Nov 09, 2013 at 04:08:50PM +0100, Patrick Godschalk wrote:
> Package: openssh-server
> Version: 1:6.2p2-6~bpo7
> Severity: grave
> Tags: patch, security, fixed-upstream
>
> The recent security advisory from OpenSSH upstream dated 2013-11-07
> mentions that "a memory corruption vulnera
Your message dated Sat, 09 Nov 2013 15:50:02 +
with message-id
and subject line Bug#724080: fixed in libgraph-perl 1:0.96-1.1
has caused the Debian Bug report #724080,
regarding libgraph-perl: FTBFS: make: *** [clean] Error 1
to be marked as done.
This means that you claim that the problem ha
Control: tag -1 pending
On Fri, Nov 08, 2013 at 06:38:17AM +0100, Moritz Muehlenhoff wrote:
> Please see http://www.openssh.com/txt/gcmrekey.adv
I've merged 6.4p1 into my development branch. I'm hoping for #722970 to
be fixed this weekend so that I can just upload that directly; otherwise
I gues
Processing control commands:
> tag -1 pending
Bug #729029 [openssh] openssh: CVE-2013-4548: Memory corruption in AES-GCM
support
Added tag(s) pending.
--
729029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
T
Package: openssh-server
Version: 1:6.2p2-6~bpo7
Severity: grave
Tags: patch, security, fixed-upstream
The recent security advisory from OpenSSH upstream dated 2013-11-07
mentions that "a memory corruption vulnerability exists in the
post-authentication sshd process when an AES-GCM cipher
(aes128-.
On Sat, 09 Nov 2013 15:40:54 +0100, Steinar H. Gunderson wrote:
> On Sat, Nov 09, 2013 at 03:36:26PM +0100, gregor herrmann wrote:
> > I've prepared an NMU for libgraph-perl (versioned as 1:0.96-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> O
On Sat, Nov 09, 2013 at 03:36:26PM +0100, gregor herrmann wrote:
> I've prepared an NMU for libgraph-perl (versioned as 1:0.96-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Oh wow, did I forget to upload the fix for this? I was positive I had alrea
Processing commands for cont...@bugs.debian.org:
> tags 559356 + pending
Bug #559356 [selinux-policy-default] libvirt-bin: libvirtd fails to start
(SELinux)
Ignoring request to alter tags of bug #559356 to the same tags previously set
> tags 691284 + pending
Bug #691284 [selinux-policy-default] s
Processing commands for cont...@bugs.debian.org:
> tags 559356 + pending
Bug #559356 [selinux-policy-default] libvirt-bin: libvirtd fails to start
(SELinux)
Added tag(s) pending.
> tags 691284 + pending
Bug #691284 [selinux-policy-default] selinux-policy-default: allow_ptrace and
deny_ptrace
Add
Processing commands for cont...@bugs.debian.org:
> tags 724080 + patch
Bug #724080 [src:libgraph-perl] libgraph-perl: FTBFS: make: *** [clean] Error 1
Added tag(s) patch.
> tags 724080 + pending
Bug #724080 [src:libgraph-perl] libgraph-perl: FTBFS: make: *** [clean] Error 1
Added tag(s) pending.
>
tags 724080 + patch
tags 724080 + pending
thanks
Dear maintainer,
I've prepared an NMU for libgraph-perl (versioned as 1:0.96-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB
Hi,
Thanks for your report, I'll fix and upload it after MiniDebConf in
Taiwan. Can you wait a bit for it?
--
Hideki Yamane
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> tags 713672 + patch
Bug #713672 [src:xca] xca: FTBFS: ld: /«PKGBUILDDIR»/lib/db_key.o: undefined
reference to symbol '__cxa_free_exception@@CXXABI_1.3'
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistan
Processing commands for cont...@bugs.debian.org:
> reassign 704713 src:gimp-plugin-registry
Bug #704713 [gimp-plugin-registry] gimp-plugin-registry: fails to build with ld
--no-add-needed
Bug reassigned from package 'gimp-plugin-registry' to
'src:gimp-plugin-registry'.
No longer marked as found
Package: libpam-systemd
Version: 204-5
Severity: important
I was having issues with my computer lately:
- I wasn't able to mount USB keys anymore in thunar ;
- I wasn't able to shutdown/restart/hibernate anymore in xfce ;
- even when logged out, lightdm didn't allow shutdown/restart/hibernate.
I
Processing commands for cont...@bugs.debian.org:
> tags 713841 + patch
Bug #713841 [oss4-dkms] oss4-dkms: oss4-4.2-build2006 cp: stat failed
/source/include/linux/limits.h
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
713841: http://bugs.deb
Processing commands for cont...@bugs.debian.org:
> reassign 727746 src:lxappearance
Bug #727746 [lxappearance] lxappearance: Build-Depends on libmenu-cache1-dev
which is going away
Bug reassigned from package 'lxappearance' to 'src:lxappearance'.
Ignoring request to alter found versions of bug #7
Hi all,
Can somebody from openjdk team apply the patch shared by Hideki Yamane
and see if that fixes the FTBFS issue.
I am looking forward to seeing the current openjdk version move to
testing. Unless this bug is fixed, it's not gonna move to testing.
--
Regards,
Shirish Agarw
Processing control commands:
> forwarded -1 https://github.com/KDAB/GammaRay/issues/63
Bug #728869 [gammaray] gammaray FTBFS: build failed on post-compile-test on
mips/mipsel
Set Bug forwarded-to-address to 'https://github.com/KDAB/GammaRay/issues/63'.
> severity -1 important
Bug #728869 [gammara
Control: forwarded -1 https://github.com/KDAB/GammaRay/issues/63
Control: severity -1 important
I see you've already forwarded it upstream, so hopefully
it will be fixed soon.
I'm downgrading the severity as gammaray never built on mips*.
Cheers,
Felix
--
To UNSUBSCRIBE, email to debian-bugs-r
Processing commands for cont...@bugs.debian.org:
> retitle 728113 _dl_check_map_versions: Assertion `needed != ((void *)0)'
> failed!
Bug #728113 {Done: Laurent Bigonville } [libselinux1]
[smartmontools] Fails to run on a Wheezy/Jessie mixed system
Bug #728507 {Done: Laurent Bigonville } [libsel
retitle 728113 _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
reassign 728113 libc6 2.17-93
reopen 728113
severity 728113 important
thanks
Hi,
I'm reassigning this to the glibc package.
smartmontools is asserting with the following message when libselinux
is removing the expli
Processing commands for cont...@bugs.debian.org:
> # on OP request
> close 729117
Bug #729117 [gmpc] Crash at startup: gmpc-favorites.vala:165: error:
Unrecognized image file format
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
729117: http:/
Your message dated Sat, 09 Nov 2013 13:03:30 +
with message-id
and subject line Bug#726341: fixed in ideviceinstaller 1.0.1-0.1
has caused the Debian Bug report #726341,
regarding ideviceinstaller: FTBFS against libimobildevice 1.1.5
to be marked as done.
This means that you claim that the pr
On Sat, 2013-11-09 at 12:09 +0100, Pascal Dormeau wrote:
>
> My programming knowledge is limited but I understand this as
> consolekit
> being launched only if no logind session is launched.
>
> And if libpam-systemd is installed, only the logind session is
> launched.
>
> I am not sure that xfc
On Sat, 9 Nov 2013 11:18:23 Rainer Dorsch wrote:
> I upgrade to digikam 3.5 to validate if Bug #714561 is still
> present. After the upgrade, all albums of digikam are
> gone.
Rainer,
Could you please provide some more details?
Did you upgrade digikam only, if so from what version to 3.5.0?
Did
Hi,
nevermind. Though I have not understood which package
have created the problem and which one fixed it, after
the installation of new updates today the problem has
gone.
This bug can be closed.
Ciao,
Paolo.
--
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@l
Hi,
> Try these packages http://mb1.pl/~qba/python/ compiled against new
> python-sip libs.
I do not want to partially upgrade my production system to KDE 4.11, so
I cannot test these packages. Instead I tried to re-build python-kde4 in
testing, but that did not work. It failed to build:
In file
Hi,
Thanks for reporting this bug.
In order to help solve this bug, I would like to ask:
1. Which older version of pwman did you use?
2. Do you have tags in the DB stored as plain strings or encrypted string?
3. Can you please test if you can still see this bug in the upstream
version?
Th
Hello,
I could be wrong here, but looking in session-child.c, one can find
(line 470):
if (login1_is_running ())
{
login1_session = login1_get_session_id ();
write_string (login1_session);
}
if (!login1_session)
{
/* Open a Console Kit session */
My p
Processing commands for cont...@bugs.debian.org:
> severity 728435 normal
Bug #728435 [lxc-stuff] lxc-stuff breaks bash completion
Severity set to 'normal' from 'critical'
> notfound 728435 1.0.0~alpha2-6
Bug #728435 [lxc-stuff] lxc-stuff breaks bash completion
No longer marked as found in version
severity 728435 normal
notfound 728435 1.0.0~alpha2-6
thanks
On 11/09/2013 03:54 AM, Servilio Afre Puentes wrote:
> This bug is still present in version 1.0.0~alpha2-6:
no, it's not.
http://packages.debian.org/experimental/i386/lxc-stuff/filelist
however, since you're using experimental, you'll
Processing control commands:
> block 674587 by -1
Bug #674587 [release.debian.org] transition: mapnik 2.0.x
674587 was not blocked by any bugs.
674587 was not blocking any bugs.
Added blocking bug(s) of 674587: 729121
--
674587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674587
729121: htt
Package: mapnik
Version: 2.2.0+ds1-5
Severity: serious
Control: block 674587 by -1
Hi,
Your package FTBFS on mips and mipsel, but built there in the past.
Until this issue has been resolved, we cannot move forward with the
mapnik transition.
~Niels
--
To UNSUBSCRIBE, email to debian-bugs-rc-
Package: digikam
Version: 4:3.5.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgrade to digikam 3.5 to validate if Bug #714561 is still
present. After the upgrade, all albums of digikam are
gone. Fortunately, the picture data on the harddisk is still present,
so
Package: gmpc
Version: 11.8.16-6
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after installation of some system updates (last week) suddenly
gmpc have started to fail to start (crash immediately) with the
following message:
$ gmpc
(gmpc:4432): MMKeysPlugin-WARNING
Package: smartmontools
Version: 6.2+svn3841-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
smartctl is unusable. It fails on every call:
shannara:~# whoami
root
shannara:~# smartctl -a /dev/sda
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions
Processing commands for cont...@bugs.debian.org:
> tags 726341 + sid jessie
Bug #726341 [ideviceinstaller] ideviceinstaller: FTBFS against libimobildevice
1.1.5
Added tag(s) sid and jessie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
726341: http://bugs.debia
80 matches
Mail list logo
