Hi -
Please beware a possible naming confusion: "valgrind-gdb" vs
"valgrind-dbg". The former is a relatively recently added subpackage
for gdb interfacing support, and has nothing to do with valgrind's
own debuginfo.
- FChE
o?
Maybe it would even be possible to provide this for stable-backports? :)
thanks, Frank
signature.asc
Description: PGP signature
update bobcat will also be updated.
--
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
signature.asc
Description: PGP signature
is needed/used?
In any case: the dependence on icmake when constructing the full bobcat
library could be avoided, but I'd rather not do that once icmake *is*
available. So please advise.
--
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
signature.asc
Description: PGP signature
Hi -
> Version: 4.9-1
> https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/39374282/log.gz
>
> 223s /usr/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct
> module’ has no member named ‘core_text_size’; did you mean
> ‘kprobes_text_size’?
> 223s 367 |(un
Package: xserver-xspice
Version: 0.1.6-1
Severity: grave
Justification: renders package unusable
See #1038648.
As I wrote there, 0.1.6-1 doesn't fix the problem, but this was
ignored, so I'm sending a new bug report.
The buggy patch is now upstream, but that doesn't make it correct.
I've already
Doesn't fix the problem.
Control: tags patch
I think I found the problem. It seems to be
Fix-a-build-error-with-Xorg-master.patch
To be honest, I don't really understand the patch. According to the
comment, instead of just changing one renamed parameter, it changes
the calling conventions at the cost of an unnecessary "s
Package: xserver-xspice
Version: 0.1.5+git20200331-3
Severity: grave
Justification: renders package unusable
Since upgrading to bookworm, Xspice always crashes when I try to
start it:
Xspice --config xspice.1.conf :25
(EE) Caught signal 6 (Aborted). Server aborting
Full log: xspice.1.log
https
Siep Kroonenberg wrote:
> The problem was that the test was specifically for a file rather
> than for any filesystem item.
>
> In the updated TL package, the test has been removed altogether
> since there was already a later test for successful generation of a
> temp subdirectory.
>
> The update
Package: texlive-pictures
Version: 2020.20210202-3
Severity: grave
File: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu
Classic /tmp write vulnerability: function dir_writable writes to
"/tmp/1" (and if this fails, "/tmp/2" etc.) without sufficient
checks.
Harmless demonstration:
% mkfi
Package: pulseaudio-dlna
Version: 0.5.3+git20200329-0.1
Followup-For: Bug #1016288
Dear Maintainer,
A similar situation occurs on stable:
Exception in thread zeroconf-ServiceBrowser__googlecast._tcp.local.:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in
Package: sshfs
Version: 3.7.1+repack-2
Severity: grave
Justification: renders package unusable
Given the following setup:
- remote directory mounted to /mnt/incoming on server using the
following options:
sshfs -d --debug librarian@archive:/mnt/incoming /mnt/incoming -o
rw,delay_connect,t
Debian 11.3 was released over the weekend, and the ifenslave fix in this
bug report is still not included.
Hi,
I see Bullseye 11.3 is planned to release in two weeks:
https://lists.debian.org/debian-project/2022/03/msg00015.html
Is there a chance the fixed ifenslave version 2.13 be added?
Upstream did this; bash-5.1.16 includes this patch and other recent
patches.
> Matthias, would you prepare such an update? TTBOMK the next bullseye
> release will be around february 2022, according to the planning of the
> release team.
OK, that's too late for me, so I'm patching it myself. Thanks for
the info.
Frank
rt it myself, and I'd like to avoid having to do
both (and thus rebooting my systems twice).
Frank
Package: bash
Version: 5.1-2+b3
Severity: critical
Justification: breaks unrelated software
Tags: patch upstream l10n
I've reported this bug on bug-bash:
https://lists.gnu.org/archive/html/bug-bash/2022-01/msg0.html
only to learn that it's known and not fixed for months (it was known
before b
Package: command-not-found
Version: 20.10.1-1
Severity: grave
Justification: renders package unusable
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917455
Bug #917455 was closed with:
Marked as fixed in versions 20.10.1-1
This is *NOT* the case!
After upgrading to bullseye, which inc
This will fix the problem tgemporarily. Discovered by some folks over at
the Mozilla-Thunderbird forum.
Type into the search bar: network.http.spdy.enabled.http2 Double-click
the entry to toggle from true to false
I have no idea whether this has any side effects, but it will
allow a connectio
Package: command-not-found
Version: 18.04.5-1
Severity: critical
Justification: breaks unrelated software
% apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Traceback (most recent call last):
File "/usr/li
> On Fri, 29 May 2020 at 09:21, Frank Heckenbach
> wrote:
> > killall fails to kill processes with names longer than 15
> > characters.
> Actually it does. But the comm length has increased for some kernels.
>
> If you're asking it to kill something with an
Package: psmisc
Version: 23.2-1
Severity: serious
killall fails to kill processes with names longer than 15
characters.
According to the manpage:
-e, --exact
Require an exact match for very long names. If a command
name is longer than 15 characters, the full name may be
for HepMC 3.2.1, but given the error looks the same it
probably also applies to 3.1.2 which you have in Debian.)
Best,
Frank
PS: This is also being used in the Archlinux package now and fixes the
same compilation issue there
(https://aur.archlinux.org/packages/hepmc3/ -> View PKGBUILD).
Package: initramfs-tools
Version: 0.136
Severity: grave
File: /usr/sbin/update-initramfs
Justification: renders package unusable
Dear Maintainer,
Not much to report. Update-initramfs hangs forever when trying to create a new
file or update a current one.
This happened after this afternoons update
Package: grdesktop
Version: 0.23+d040330-3.1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
using grdesktop to connect to another host on Debian Buster
* What exactly did you do (or not do) that was effective (or
ineffective)?
g
as been dropped from
> texlive-base in sid. Please update your build-dependency to
> texlive-plain-generic instead.
Thanks for the bug report: I'll handle that either today or tomorrow.
--
Frank B. Brokken
(+31) 6 5353 2509
PGP Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
Package: gimp
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Q) What led up to the situation?
A) open any image file
Q) What exactly did you do (or not do) that was effective (or ineffective)?
A) choose restart
Q) What was the outcome of this actio
Il will upgrade that package.
Thank you Moritz
Franklin
--
Envoyé de mon téléphone. Excusez la brièveté.
rd from the user list).
Many, many thanks to all involved people for your immediate help. I'm looking
very forward to one of the next of Buster's weekly-builds :) .
> Cheers,
Have a nice day,
Frank.
eXirius IT Dienstleistungen GmbH
Juchem-Straße 24 | 66571 Eppelborn
T +49 6881 999
Please let me know if it works for you.
Kind Regards,
Frank
Am 31.03.19 um 16:32 schrieb Peter Wienemann:
> Package: libifd-cyberjack6
> Version: 3.99.5final.sp09-1.1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> trying to chang
fails due to more strict tools that are
> > not going to be changed -- not sure.
To narrow it down, does it work if you build it manually (see
above)?
> BTW I included a patch that I noticed, fixing a duplicated entry in
> projects_using_ftgl.txt, please try to apply it.
Done.
Cheers,
Frank
that work
for you? If so, it must be something in the Debian rules; otherwise
it seems to be difference between stable and testing which may be
worth investigating as it may affect others too. What errors do you
get?
Cheers,
Frank
epend on ftgl>=2.4.0 in all packages that use FTGL.
Cheers,
Frank
can require setting this flag,
first with a warning, later with an error if it's not set before
the first rendering. Provided you've added the call to all
packages by then, nothing will break.
Cheers,
Frank
> Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach
> escreveu:
> >
> > According to https://release.debian.org/buster/freeze_policy.html:
> >
> > 2019-01-12 - Transition freeze
> >
> > Is there still time yet to get a fix in, or is it FUBAR already?
&
According to https://release.debian.org/buster/freeze_policy.html:
2019-01-12 - Transition freeze
Is there still time yet to get a fix in, or is it FUBAR already?
Frank
fgtl, the only practical
> solutions are either to revert the change making some applications
> unuseable via extra patch from Debian; or have this transition and
> deprecation messages etc. in a way that existing packages don't need
> changes at all.
>
> Sorry, but I don't think that anything else works for Buster.
As I said, in the first step (2.4.0), they should not (assuming some
new warnings while recompiling are no problems).
Some changes will be necessary for 3.0.0, after Buster.
Cheers,
Frank
ons using it will break, but fixing them will only
require changing "Render" to "RenderDefault" in some places
(which are found by compiler errors). This can also be done before
you upload 3.0.0 (as "RenderDefault" will be available in 2.4.0
already), so the transition can be smoohter.
Does this sound like a viable plan?
Cheers,
Frank
Hi,
> Em qua, 21 de nov de 2018 às 15:15, Frank Heckenbach
> escreveu:
> >
> > > I think that we should revert this change for the time being, though,
> > > because if it was working in this way for about a decade and the
> > > programs using FTGL work
elect the
behaviour. Of course, it would need to be a runtime flag. It may
default to the old behaviour, but that should be deprecated (and
print a strong depreciation message -- unfortunately that would
have to be at runtime too AFAICS, or is there a way to warn at
compile time when a program, say, does *not* reference a
particular function?).
Cheers,
Frank
e of bugs to propagate to testing by uploading
> in source-only form (dpkg-buildpackage -S). That way we would get
> official build logs here for the arch:all autobuilder:
>
> https://buildd.debian.org/status/package.php?p=yodl
Thx for the advice!
--
Frank B. Brokken
Center for
'll have a look at it asap. As a side note: As
`stretch' is the current stable distribution I'm slightly curious as to what
may be have caused this error. Maybe -A has never been used? Anyway, I'll
check things out. Maybe it's only required to define the missing target in
debi
Hi -
> Package: systemtap
> Version: 3.1-3
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
> [...]
Due to the absence of a fixed kernel API, newer systemtap versions are
required to deal with newer kernels. The particular errors lis
an/bisonc++.1 bisonc++.yo
> Yodl2man 4.02.00
> Yodl: including file ../../release.yo
> bisonc++.yo:30: DEFINEMACRO: `tr' multiply defined
Thanks! This is comparable to what you noticed yesterday with the C++
Annotations. I'll probably have it fixed by tomorrow.
--
Fr
> Yodl2html 4.02.00
> Yodl: including file preamble
> preamble.yo:208: DEFINEMACRO: `nbsp' multiply defined
Oops... Thanks: I'll fix that later today.
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP
I received this message saying thank you for your recent purchase. I having
bought anything recently and don't have any idea what the message means.
kages in sid, your package failed to build on
> amd64.
Hi Lucas,
Thanks for your bug report. I'll check it out asap.
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerpri
Hi -
On Thu, Mar 02, 2017 at 01:25:03PM -0800, Gerald Turner wrote:
> FWIW, I attempted to kludge around the mangled include argument by
> running stap with "-B 'EXTRA_CFLAGS += -I/usr/share/systemtap/runtime'".
> This seems to work around the compilation failure of missing
> runtime_defines.h in
I filed basically this same bug at the GIT site for mate.
This was their reply:
This is with Caja 1.14 as shipped b Debian? That version is not
compatable with GTK 3.21.5. Debian updated GNOME to version
3.21.91, which pulls in GTK 3.21.5 but did not update MATE, in
which Caja and mate-setting
I filed basiclally this same bug at the GIT site for mate.
This was their reply:
This is with Caja 1.14 as shipped b Debian? That version is not
compatable with GTK 3.21.5. Debian updated GNOME to version
3.21.91, which pulls in GTK 3.21.5 but did not update MATE, in
which Caja and mate-settin
Package: caja
Version: 1.14.2-1
Followup-For: Bug #836669
Caja just stated doing this: click on home icon on
desktop...all desktop icons disappear for a moment,
then return but caja never opens directory. Syslog and kernel log
show segfault. .xsessions-error file is full of gtk errors.
Change them
Dear Axel Beckert, you wrote:
> Hi Frank,
Hi Axel,
You wrote:
> I'm not 100% sure what's going on, but it seems to me that while
> c++-annotations indeed FTBFS with 3.07.00-1 and builds fine again with
> 3.08.00-1 (verified it :-), it's the opposite way round with zs
ony, or George, who receive CCs) reassign this
bug to yodl, since that's where the fix is required.
Thanks again,
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF3
Dear Martin Michlmayr, you wrote:
>
> Package: bobcat
> Version: 4.01.04-1
> Severity: serious
>
> Hi Frank, here's a build failure of bobcat. I don't know if it's a
> regression in yodl or if something has to change in bobcat, but in any
> case, bobcat
er tools).
Agree 100%. And the fix is on its way :-)
Thanks again!
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
e quick reply, guys: I'll do my best to come up with the fix
equallly quick :-)
Cheers,
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E
directory (where you also find
a file named CLASSES) and send me the output? That might provide a little
more info about what went wrong.
For now, lacking access to a Helion machine, I'm afraid I have to ask you for
some help
Cheers,
[Cc: Tony/George]
--
Frank B. Brokken
Center f
debian.org/cgit/pkg-xiph/vorbis-tools.git/tree/debian/patches/Fix-segfault-in-vcut.patch
Seems to work for me. Thanks.
Frank
building it
myself, same bug), but anyway.
> The patch is in the git repository.
Where can I get it (just the patch, so I can try it against the
jessie version)?
https://git.xiph.org/ says:
vorbis-tools.git ... Last change 5 months ago
Regards,
Frank
Package: vorbis-tools
Version: 1.4.0-6
Severity: grave
File: /usr/bin/vcut
Justification: renders package unusable
Sorry for the brief description, but for what I can tell, that's
really it. I tried various cases, and vcut always seems to just
segfault. Here's one example:
% head -c 50 /dev/z
o the flash package is
simply not available anymore.
This is the result of running it
root@frank-debian:/home/frank# update-pepperflashplugin-nonfree --install
--verbose
options : --install --verbose --
temporary directory: /tmp/pepperflashplugin-nonfree.lOWqvvqSXk
doing apt-get update on g
had any problems of that kind.
Regards, Frank
i-(6007)-~% apt-get install susv4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
susv4
0 upgraded, 1 newly installed, 0 to remove and 56 not upgraded.
Need to get
lve upstream at some point.
OK, thanks for the help and (for me at least) final conclusion. For me
personally the problem has been solved: for the time being I'm happy with 227,
and I'm sure that the problem will soon be fixed.
Thanks again for helping along!
Cheers,
--
Frank B. Bro
.deb
Thereafter I rebooted several times without encountering any problems. Also
with reduced output (grub's option 'quiet') no problems were encountered.
Cheers,
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
in sh[487]: before rootfs remount
Dec 19 16:45:21 localhost.localdomain sh[516]: before rootfs remount
Dec 19 16:45:24 localhost.localdomain sh[620]: before rootfs remount
$ grep 'after rootfs' *1650
$
Next thing I'll try is to downgrade to 227-2.
--
Frank B. Brokken
Cent
d attach the journal log again.
Instead of running the systemctl command I edited the file
/lib/systemd/system/local-fs.target.wants/systemd-remount-fs.service and added
the lines you suggested. My next e-mail is about the contents of journal log.
Thereafter I'll try to downgrade to the previ
e useful to note: it took like four or five reboot attempts before the
booting process eventually failed. This time even more output than with using
'verbose' flashes by during the booting process, which somewhat slows down the
booting procedure. You're sure it can't be some ti
Dear Michael Biebl, you wrote:
> Am 18.12.2015 um 15:59 schrieb Frank B. Brokken:
> > Is there a way to determine that? What I do to upgrade the system is run
> > 'aptitude update' and then 'aptitude upgrade'. Is there a log somewhere that
> > tells me w
tells me what packages and versions were updated at what moments in time?
> If you downgrade systemd/udev, does the problem go away?
I thought about doing that, but was afraid for an avalanche of forced
downgrades of packages that might now depend on the most recent udev and
systemd ver
Dec 6 2014 70-persistent-cd.rules
-rw-r--r-- 1 root root 895 Feb 26 2013 70-persistent-net.rules
And I definitely didn't recently change there any files, so again: the problem
appeared out of the blue since last weeks upgrade.
I hope the above gives you at least some additional info. As
Dear Michael Biebl, you wrote:
> Am 17.12.2015 um 13:46 schrieb Frank B. Brokken:
> > halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue
> > shell>
> What exactly do you mean with halt? The systems completely locks up so
> you can't use th
ot. Not completely, but
greatly. Still, when rebooting fails there's just the plain halt, w/o a debug
shell. Since removing the quiet also produces a lot more output on the screen,
might my problem not simply be some timing problem?
--
Frank B. Brokken
Center for Information Technology
Use `listlen'
> ...
> 2 error(s) detected
> debian/rules:52: recipe for target 'clean' failed
> make: *** [clean] Error 1
>
> [..]
Cheers,
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
make: *** [clean] Error 1
Thanks! The update adapting the icmake 8.00.04 will arrive shortly
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
x27;clean' failed
Thanks! That's a plain old typo. But an update also including the required
changes for the icmake 8.00.04 upgrade is being prepared right now.
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP
uired:
int idx;// definition moved out of the next for-statement
for (idx = listlen(haystack); idx--; )
But I'll handle this bug ASAP.
Cheers,
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP key: http://pgp.surfnet.nl
Key Fingerprint: DF32 13DE B156 7732 E65E 3B4D 7DB2 A8BE EAE4 D8AA
6000, 4096, PROT_READ) = 0
mprotect(0x7f5a3f459000, 16384, PROT_READ) = 0
mprotect(0x7f5a3f679000, 4096, PROT_READ) = 0
mprotect(0x7f5a3f8ae000, 4096, PROT_READ) = 0
mprotect(0x7f5a407d5000, 4096, PROT_READ) = 0
munmap(0x7f5a407b1000, 136096) = 0
set_tid_address(0x7f5a4079ca30)
severity 798821 normal
tags 798821 unreproducible
--
Am Sonntag, 13. September 2015, 09:38:04 schrieb Jaldhar H. Vyas:
> On Sun, 13 Sep 2015, Frank Engler wrote:
> > Package: dovecot-core
> > Version: 1:2.2.13-12~deb8u1
> > Severity: serious
> >
> > Dear
Package: dovecot-core
Version: 1:2.2.13-12~deb8u1
Severity: serious
Dear Maintainer,
last update introduced /lib/systemd/system/dovecot.socket
and /lib/systemd/system/dovecot.service to handle startup.
Despite the fact customized configuration - especially
/etc/init.d/dovecot - might get ignored
Dear tony mancill, you wrote:
> Frank, George,
>
> I've pushed a new branch to alioth for this upload. The branch name is
> bobcat-gcc5abi.
>
> Please let know if you have any concerns, otherwise, I'll plan to upload
> the evening of August 11th (here in GMT-0
Dear Julien Cristau, you wrote:
> Control: severity -1 serious
> Control: tag -1 confirmed
>
> On Tue, Jul 7, 2015 at 20:47:28 +0200, Frank B. Brokken wrote:
>
> > > - Rebuild the library using g++/g++-5 from experimental. Note that
> > >most likely a
Hi Gianfranco,
ticket https://www.virtualbox.org/ticket/14128 is only about VBox version
4.3.18. No other version is affected by this bug. Note that this has nothing
to do with CVE-2015-3456.
Kind regards,
Frank
On Tuesday 19 May 2015 08:20:07 Gianfranco Costamagna wrote:
> Hi Frank, is 4.1
Hi Gianfranco,
On Tuesday 19 May 2015 09:17:13 Gianfranco Costamagna wrote:
> Hi Frank, are you sure the bug is really fixed?
>
> the qemu patch seems to be different from the virtualbox one, and seems that
> the affected code is not fixed
> http://git.qemu.org/?p=qemu.git;a=blob
Hi Gianfranco,
could you also have a look here?
https://www.virtualbox.org/ticket/14128#comment:1
This is regarding the 4.3.18 Jessie package.
Thanks,
Frank
On Monday 18 May 2015 16:48:13 Gianfranco Costamagna wrote:
> Hi
>
> sid/testing:
>
> - 4.3.28 is not affected
is not affected (only 4.2.x and older)
CVE-2014-0224: this is related to OpenSSL and therefore not a problem for
Linux distributions as you compile your code against the
distro-specific OpenSSL implementation.
Frank
--
Dr.-Ing. Frank Mehnert | Software Development Direc
o these old versions. Sorry but it's not possible to
support such old versions, we only support the latest versions of a
specific branch.
> 4.3.20 (not affected at all I presume)
Correct, already contains fixes for all these problems.
Frank
--
Dr.-Ing. Frank Mehnert | Software
Package: pacemaker
Version: 1.1.10+git20130802-4.1
Severity: grave
Justification: renders package unusable
Hello,
After upgrading pacemaker to 1.1.10+git20130802-4.1, the cluster doesn't work
any more. All resources are unavailable. Command line tools report an undefined
symbol in libcrmcommon.
admin (which
I did, and then I had to debug what killed my changes).
An alternative that would also work for me (not sure about
combination with other tools) would be if merge-hook used some
template to produce its output (which should then include a comment
pointing to the template for manual changes), so
...
> It seems -lpthread is missing from the build command line.
Hm, maybe (some) architecture dependency. Anyway, I'll fix this tomorrow.
Thanks for the report!
--
Frank B. Brokken
Center for Information Technology, University of Groningen
(+31) 50 363 9281
Public PGP
description which just says:
top_branch:lower_branch:...:lowest_branch
I suggest writing something like this to prevent such
misunderstandings:
top_branch[=ro|rw]:lower_branch[=ro|rw]:...:lowest_branch[=ro|rw]
Frank
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: unionfs-fuse
Version: 0.24-2.2
Justification: renders package unusable
Severity: grave
# mkdir 1 2 3
# unionfs-fuse 1:2 3
fuse: warning: library too old, some operations may not not work
According to the dependencies it requires libfuse2 >= 2.8.1.
I have 2.9.0-2 installed, so how can it
Package: fgo
Version: 1.3.1-2
Justification: breaks unrelated software
Severity: critical
The version in wheezy contains:
Recommends: flightgear (>= 2.0.0)
But flightgear does not exist in wheezy.
I tried to get its sources from testing to build it myself, but it
didn't work:
% apt-get source
Encfs still has its uses despite the security problems.
With this bug filed as serious it has now disappeared from jessie.
--
Frank Kingswood fr...@kingswood-consulting.co.uk
Cambridge, United
Hi,
> Frank, are you still active or should someone take over ? I'm asking
> because "gitpkg" is much less used than "git-buildpackage" and
> it might be easier to use Bastien's solution if we switch to
> git-buildpackage.
>From my side any help is we
Hi,
sorry for late reply. Lot of private stuff
Feel free to upload an NMU package.
I will try to fix the other bugs as soon as possible.
regards,
Frank
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
to you if you'd like, but there's nothing
> very complicated going on. My apologies if this disrupts any packaging
> work that was already in progress.
No problem, I just pushed your changes to the Git repo.
Thanks again for your help!
Frank
signature.asc
Description: This is a digitally signed message part.
Package: mate-polkit-common
Version: 1.6.0-1
Severity: critical
Tags: upstream
Justification: aborts update
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Updating via apt-get
* What was the outcome of this
Locks up whenever anything is tried. ctrl-alt-backsp will kill the x-server
so I can get out and into something that works :)
--
Frank in Montreal
from within the framebuffer
and/or
a method to navigate web browsers/burning software to actually aquire and
create
useful, NON-INFECTED programs and disc images. Any info or help would be
greatly
appreciated. Thank you for your time.
-Frank Black [author of the programs found at
www (dot)
1 - 100 of 2106 matches
Mail list logo
