Tomas Pospisek dixit:
>in the description s/si- milar/similar/
Are we not allowed to wrap the text then?
I will fix it with the next release which is due soon.
Thanks,
//mirabile
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God i
I have an idea…
Dixi:
>Martin Zobel-Helas dixit:
>
>>> /usr/include/sys/stat.h:217: error: conflicting types for 'stat'
>>> /usr/include/sys/stat.h:365: error: previous definition of 'stat' was here
>[...]
>
>Sounds like a bug in the header file to me:
>
>215 extern int __REDIRECT_NTH (stat,
This version was uploaded to 'experimental' exactly to find out
possibly portability problems, e.g. with kfreebsd and hurd ;)
So I suppose that was a good move.
Martin Zobel-Helas dixit:
>> /usr/include/sys/stat.h:217: error: conflicting types for 'stat'
>> /usr/include/sys/stat.h:365: error: pre
Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Justification: breaks unrelated software
Just dist-upgrading today…
tglase@tglase:~ $ ssh localhost
OpenSSL version mismatch. Built against 1000105f, you have 10001060
255|tglase@tglase:~ $ nc ::1 22
tglase@tglase:~ $ # huh?
Dec 23 10:01:
Hi *,
binNMUing src:openssh locally, against the new OpenSSL, fixes
the problem. The problem with binNMUs is that you cannot guarantee
that the new OpenSSL is already used for the build (nothing in the
buildd network can give that guarantee, not even when OpenSSL has
already been built for that pa
On Mon, 23 Dec 2013, Kurt Roeckx wrote:
> On Mon, Dec 23, 2013 at 10:03:08AM +0100, Thorsten Glaser wrote:
> > tglase@tglase:~ $ ssh localhost
> > OpenSSL version mismatch. Built against 1000105f, you have 10001060
>
> This is already the 4th time this is reported.
Interest
On Mon, 23 Dec 2013, Raphael Hertzog wrote:
> Hello dear maintainers,
(strictly speaking I’m only co-maintainer of mw-extensions,
but have helped out with mw itself too)
> can you share your plans to update the mediawiki package ?
Upstream said 1.19 would be an LTS release, so we chose
it for w
On Mon, 23 Dec 2013, Raphael Hertzog wrote:
> Well, you also ensure that you won't discover issues introduced in new
> versions until well too-late in the developement cycle...
Sure, but that happens always, no matter how you set the
cut-off. Unless we stick with 1.19 for jessie too. I think
you
On Mon, 23 Dec 2013, David Gerard wrote:
> (Particularly given Debian's idiosyncratic
> default to the not-well-supported Postgres rather than the
> highly-supported MySQL/Maria).
Actually, Debian defaults to the not-even-a-real-ACID-database
MySQL instead of a proper database, by ordering of the
+ * Port to newer libewf API to fix FTBFS (Closes: #729651)
+
+ -- Thorsten Glaser Wed, 25 Dec 2013 00:09:42 +
+
guymager (0.6.7-3) unstable; urgency=low
* [136b5d8] Adjust ThreadScanLibPartedSearchDirs of threadscan.cpp
diff -Nru guymager-0.6.7/debian/patches/newer_libewf.diff
guymager
On Wed, 25 Dec 2013, David Gerard wrote:
> But MySQL is also the platform MediaWiki is developed against, and
> Postgres isn't, and this last fact is important. This question was
> originally about moving the package to 1.22.0. You do realise that
> MediaWiki 1.22.0 didn't work in Postgres, and no
Package: sysvinit-core
Version: 2.88dsf-44
Severity: important
Tail of the output of apt-get --purge dist-upgrade, with
adequate installed:
[…]
uno-libs3: library-not-found /usr/lib/libuno_cppuhelpergcc3.so.3 =>
libxmlreaderlo.so
sysvinit-core: program-name-collision /sbin/halt /usr/sbin/halt
sy
Source: pp-popularity-contest
Version: 1.0.6-1
Severity: important
Justification: fails to build from source (but built successfully in the past)
[…]
cd .. && /bin/bash /«PKGBUILDDIR»/missing automake-1.14 --gnu src/Makefile
configure.ac:4: error: version mismatch. This is Automake 1.14.1,
confi
Source: proot
Version: 3.0.2-1
Severity: serious
Justification: fails to build from source
proot does not build on all architectures it declares support for:
• https://buildd.debian.org/status/package.php?p=proot
• http://buildd.debian-ports.org/status/package.php?p=proot&suite=sid
See e.g. here
Package: quilt
Version: 0.60-2
Severity: important
Hi,
this is the companion bug for the same problem in dpkg-source --commit
reported as: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689193
The severity in quilt is higher because this is quilt’s primary
objective (managing diffs) and the im
Package: mc
Version: 3:4.8.11-1
Severity: serious
I cannot move files in mc any more.
For example, I have the cursor on a file called x and want
to move it to my home directory (the other panel does NOT
show my home directory right now (but a second work dir),
so I need to type it).
I type F6 ~
Martin Quinson dixit:
>In lack of this, I blame dpkg for the behavior you saw, not quilt.
No, what I meant is: it got fixed in dpkg, but quilt still writes
diffs with files in arbitrary (as opposed to fixed) order, which
is what I want to fix.
Every program writing a diff that contains changes t
Martin Quinson dixit:
>And I claim that quilt is not doing this. You have to provide some
>sort of evidence of the bug, actually.
$ echo foo >foo; echo fnord >fnord; echo zulu >zulu
$ quilt new bar; quilt add fnord zulu
Patch bar is now on top
File fnord added to patch bar
File zulu added to patc
Hi *,
I’ve had a look at this again. Helmut had suggested that I split
the installed trees between core and extensions into two separate
directories (instead of combining them into one directory with
entries being sometimes symlinks, sometimes directories, under
/var/lib/mediawiki/extensions), but
Sandro Tosi dixit:
>i've just tried replicating this bug but was unable to: now the bug is
>retrieved correctly. Are you still able to replicate it? it might have
Yes, *now* it works for me too (although the bug in question is not
shown in the list any more anyway, maybe it was something with tha
Ivan Jager dixit:
>sizeof(uint64_t) = 4
Ouch. This should be 8 even on sparc32, yes.
Ivan, can you please check with older dietlibc versions from, for
example, snapshot.debian.org? It might be related to #587042 which
“suddenly” appeared, and 0.32-5 does have sparc related changes.
Thanks,
//mi
Andreas Schwab dixit:
>Invalid alignment assumptions:
Thanks! That was fast and confirms my first (without looking at the
code) suspiction. I’ll try that tomorrow.
bye,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God
=low
+
+ * Add padding to avoid bogus alignment assumptions (Closes: #604603)
+
+ -- Thorsten Glaser Wed, 24 Nov 2010 09:46:57 +
+
gobject-introspection (0.6.14-1) unstable; urgency=low
* New upstream release
diff -Nru
gobject-introspection-0.6.14/debian/patches/debian-changes-0.6.14-1+
Laurent Bigonville dixit:
>Does this bug also happen with the version in experimental?
The version from experimental cannot be built:
pbuilder-satisfydepends-dummy: Depends: libglib2.0-dev (>= 2.25.11) but it is
not installable
>Has it been forwarded upstream?
No. (After all, I detected it t
Compose + ( + A + ) always worked for me.
bye,
//mirabilos
--
20:54⎜ dmaphy: remember: "In theory there's no difference
⎜ between theory and practice, but in practice..."
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
Source: gcj-4.4
Version: 4.4.5-2
Severity: important
While compiling gcc-4.4_4.4.5-8 as gcj-4.4_4.4.5-2+m68k.1 I noticed,
and confirmed by looking at buildd logs of gcj-4.4_4.4.5-2 that it’s
not a local problem, that GCC not only contains an embedded code copy
of libz but also compiles it (at leas
cannot reproduce with 4.4.5-8
//mirabilos
--
20:54⎜ dmaphy: remember: "In theory there's no difference
⎜ between theory and practice, but in practice..."
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
I uploaded gcc-4.4 4.4.5-8 to unstable, works fine so far.
I’ve also made a gcj-4.4 package for unreleased out of it,
following the documentation, which also seems to work well
(once build-deps are installed).
So, all that’s left is probably:
• look at the symbols warnings from Message #30
• uploa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi!
Fun to be reading this. Me like ;-)
Anyway. With my Debian hat on, the C/POSIX locales must not use
UTF-8 as encoding, because otherwise, all kind of hell breaks
loose (consider running 'tr u x' on a binary or other legacy
encoded text file, an
Ivan Jager dixit:
> AFAICT, the difference between lenny and squeeze is that squeeze gcc defines
> __sparc_v9__ whereas lenny's does not.
Well, it’s wrong there: v9 is sparc64 not sparc. The Debian/sparc port
uses 32-bit userland, which is either v7/v8/hypersparc/supersparc/…
or v8plus (which wil
Ivan Jager dixit:
> Is there some reason why changing it to __sparcv9 is wrong?
Yes, v9 is 64 bit, sparc is 32 bit (sparc64 is 64 bit).
Out of curiosity, does manually specifying -m32 on the
command line “fix” your problem/testcase?
bye,
//mirabilos
--
20:54⎜ dmaphy: remember: "In theory there
Damyan Ivanov dixit:
>> I request an adopter for the libbsd-arc4random-perl package.
>> I’d like to put it under the Debian Perl umbrella, if possible,
>
>Alright. I intent to adopt it for the Debian Perl group.
Cool, thanks!
Do you want the ,v files from VCS-CVS for import into your version
con
Damyan Ivanov dixit:
>> > This suggested that there's additional history that I'd like to have,
>> > but retrieving it fails:
>> [snip]
>> > Perhaps git-cvsimport is not happy about the module rename or the
>> > history is just not available anymore.
Oops. Sorry.
>I guess that could work, alth
Hello Debian TeX Maintainers,
could you please give advice how to fix this? I know virtually
nothing about Teχ, and the package is “just” trying to build
its documentation into PDF format (standard GNU stuff).
Thanks!
Daniel Schepler dixit:
>From my pbuilder build log:
>
>...
>make[2]: Enterin
Norbert Preining dixit:
>Add
> texlive-fonts-recommended
>to the build-deps.
Thanks for the amazingly fast help! Will do.
bye,
//mirabilos
--
ncal.c: In function 'parsemonth': warning: comparison between pointer
and integer • ↑ hab da „in function parselmouth“ gelesen
ICH AUCH! • Ic
Sylvestre Ledru dixit:
>Did you had the chance to refresh this patch against the current release
>of Iceweasel ?
Sorry, no.
bye,
//mirabilos
--
Ach, mach doch was du willst, du hast doch eh immer Recht!
jupp ~/.etc/sig………
unfaßbar…
Mit Eszett sogar, unfaßbar!
--
To UNSUBSCRIBE, email to d
Matthew Woodcraft dixit:
>If I use jmacs with 'marking' in the configuration, often (but not
>always) ^W (cut) fails.
>
>Also, sometimes the 'region' highlighting fails to appear, and this
>seems to correspond to the times when ^W doesn't fail.
Hrm okay – I don’t normally use jmacs so I didn’t no
Ian Jackson dixit:
>(and to use a helper tool for daemonisation).
mksh -T- -c 'exec daemond arg1 …'
bye,
//mirabilos
--
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz i
Anthony Towns dixit:
> [default-init] Having examined the features and bugs of the various
>init systems packaged for Debian, the default init system for jessie
>for Linux architectures shall be {OpenRC | systemd | upstart |
Please do not forget sysv-rc here.
>determined by a GR}.
> [systemd-
Package: steam
Version: 1.0.0.39-2
Followup-For: Bug #736455
Installing ttf-mscorefonts-installer fixes this problem;
that package therefore must be a Depends.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
For
On Fri, 24 Jan 2014, Fabian Greffrath wrote:
> Am Donnerstag, den 23.01.2014, 20:50 +0100 schrieb Thorsten Glaser:
> > Installing ttf-mscorefonts-installer fixes this problem;
> > that package therefore must be a Depends.
>
> Could you try if installing fonts-liberation or
piruthiviraj natarajan dixit:
>This thing about 'Linux/Debian is all about choice' reminds me of the
>famous post I read in the past about choice.
>
>http://www.redhat.com/archives/fedora-devel-list/2008-January/msg00861.html
That is about Fedora, and about Linux, but *not* about Debian.
Debian
Michael Gilbert dixit:
>Why not avoid impeding progress and just let gnome do what it needs to
>work the way it wants, which would involve depending on the right
Excuse me, why is GNOME, specifically, being allowed to “do what it
wants”, in this case? Imagine other software with a more-or-less
le
Olav Vitters dixit:
>IMO other init systems should provide the interfaces which GNOME
>requires. It is not up to GNOME to provide these. That or takeup
There is a lot wrong with that statement.
Imagine you’re working on/with a software FOO that is not yet
packaged in Debian. Say it comes from th
Matthias Klumpp dixit:
>No, Josselin is right: GNOME *does not* work without services provided
>by systemd. He never said that - given some amount of work - it can't
Hum, we can always add “remove GNOME (3) from Debian” to the
list of GR or TC points to consider (this *has* been suggested
earlier
Matthias Klumpp dixit:
>2014-01-30 ChaosEsque Team :
>> [bullshit]
This was actually *not* bullshit. The delivery of most of the
content could use some polishing, but the content is a(n inconvenient)
truth.
>Wasn't there some kind of a ban applied here?
Apparently not, but it’s better that way
Matthias Klumpp dixit:
>What would happen if we adopted systemd?
The project would lose (a different set of) contributors and users.
The OSS ecosystem would lose, vendor-lock-in would ensue in a way
even worse than the FSF does, and the remnants of Unix/GNU in Debian
would die, to be replaced by
Jason A. Donenfeld dixit:
>Question B. Debian will allow alternative, non-default, init systems on Linux:
No, as Ian already explained this will not permit people
to vote, for example:
A with multiple > B with multiple > B alone > NOTA > A alone
bye,
//mirabilos
--
Beware of ritual lest you f
Package: snapshot.debian.org
Severity: normal
Hi,
in response to the lintian post, please remove the following
versions (all files, source and binary) of src:mediawiki:
* [14]1:1.19.6-1
* [15]1:1.19.5-1+deb7u1
* [16]1:1.19.5-1
* [17]1:1.19.4-1
* [18]1:1.19.3-2
* [19
Colin Watson dixit:
>("Decide any technical matter where Developers' jurisdictions overlap").
I think it is not up to the d-i people to decide on the init system
anyway – especially as not d-i but debootstrap is the canonical way
to install Debian… and debootstrap goes by whatever ftp-masters put
Colin Watson dixit:
>> https://lists.debian.org/debian-devel/2014/02/msg00106.html
>
>Various developers certainly continue to work enthusiastically on their
>preferred approaches, but that's not really the same as "efforts to
>resolve [the issue] via consensus".
But is not diversity some sort of
Didier 'OdyX' Raboud dixit:
>Now, I think there is currently a shared agreement in Debian that
>
>"all Debian packages (unless there's a good reason) should run on
> sysvinit + Linux + amd64 , support outside that is best-effort"
Eh, no! Debian is the universal OS, and it has quite a numb
On Mon, 15 Nov 2010, Jonathan Nieder wrote:
> Patches are attached, since that is what debbugs seems to cope best
> with.
02-guard-against-unset-ifs
• An unset IFS shall behave like an IFS set to ,
see POSIX:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06
Olav Vitters dixit:
>References to religion and second world war? Really? You expect people
>to listen to such bullshit?
Also, as a German, I’m affronted by Craig’s comment. After all,
Hitler was Austrian, not even German.
>Fairly easy to assign everything to conspiracy and say systemd
>advocate
Package: wnpp
Severity: normal
I request an adopter for the libbsd-arc4random-perl package.
I’d like to put it under the Debian Perl umbrella, if possible,
as my Perl is very limited, and this package has been spitting
warnings recently for which more experienced people can write
patches (which I’
Package: apt
Version: 0.9.12.1
Severity: wishlist
Hi,
as user of one of the slower architectures (m68k), I regularily
see things like this in apt-get --purge dist-upgrade:
The following packages will be REMOVED:
git* mc*
The following packages will be upgraded:
[…] git-man […] mc-data […]
T
Package: apt
Version: 0.9.14
Severity: normal
Hi,
I’ve got lengthy local deltas in /etc/lynx-cur/lynx.cfg and was
just prompted by dpkg how to handle it, while the fancy progress
thing was still visible. I told it to show me the diff (in less),
and the progress thing vanished, but after scrolling
Phillip Susi dixit:
>> While chatting with someone who was trying to install Linux onto
>> his ATARI Falcon 060, we stumbled into the task getting the hard
>> disk partitioned for the ATARI Falcon to be used.
>
>I must be missing something... isn't this a 30 year old relic that
>only exists in mus
Package: tendra
Version: 4.1.2-19
Severity: grave
Justification: renders package unusable
A screenshot says more than a thousand words ☺
tglase@tglase:~ $ sudo apt-get install tendra
[sudo] password for tglase:
Reading package lists... Done
Building dependency tree
Reading state information... Do
Michael Vogt dixit:
>could not trigger the issue.
Hmm. I run things in GNU screen (TERM=screen) inside uxterm.
Maybe this is important?
Thanks,
//mirabilos
--
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kap
John Paul Adrian Glaubitz dixit:
>But, of course, you could apply the patch to gparted, rebuild it,
>then create a partition table on a hard disk and hook it up to
>your ATARI and see if it's being recognized.
Before hooking it up, bswap the disc if it’s IDE, though.
bye,
//mirabilos
--
Yay for
Phillip Susi dixit:
>> John Paul Adrian Glaubitz dixit:
>>
>>> But, of course, you could apply the patch to gparted, rebuild
>>> it, then create a partition table on a hard disk and hook it up
>>> to your ATARI and see if it's being recognized.
>>
>> Before hooking it up, bswap the disc if it’s
Vincent Lefevre dixit:
>Well, that's very confusing, because both ksh93 and mksh are
>ksh alternatives. This can break scripts with "#!/bin/ksh".
ksh93 can break scripts with "#!/bin/ksh" because interpreting
leading-digit-zero numbers as octal is a *very* recent change,
and is *known* to break e
Klaus Ethgen dixit:
>> This does not warrant an upload to stable, though.
>> At best, a backport.
>
>Why not? I did file the bug for stable and not for testing.
Because the Stable Release Team only permits uploads for
security fixes and other grave issues in packages. Not
even my decision, see.
Package: qemu-utils
Version: 1.6.0+dfsg-2
Severity: wishlist
Hi,
some other distros have preallocation=full option for qemu-img
qcow2 format, somehow Debian (even sid) doesn’t.
Please add it, because this is needed in order to not overcommit
the available VM backing store space when one is unabl
pload.
+ * Write to both CLIPBOARD and PRIMARY selection, using xsel(1) which,
+unlike xclip, is able to keep the latter in memory (closes: #725653).
+
+ -- Thorsten Glaser Thu, 17 Oct 2013 22:11:40 +0200
+
password-store (1.4.2-1) unstable; urgency=low
* New upstream release (c
Jarkko Palviainen f-secure.com> writes:
> I looked into one of these, libmail-deliverystatus-bounceparser-
> perl_1.531.orig.tar.gz, and found multipart email file containing zip
> attachment. Inside this archive is a .pif file (PE32 executable for MS
Windows)
> which is detected as Win32.Worm.My
On Tue, 15 Oct 2013, Thijs Kinkhorst wrote:
> I'm still not sure why the virus contained in the source could not be
> replaced by the EICAR test signature.
Because it’s not testing a virus scanner, but because the
specific RFC822 message in question exhibited multiple problems
in the code, due to
1,12 @@
+alpine (2.10+dfsg-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix endian detection for UCS-2, UCS-4, UTF-16 encodings
+ * Unbreak building twice by deleting more generated files
+ * Fix display of base64 encoded raw messages
+
+ -- Thorsten Glaser Fri, 18 Oct 2013 17:09
Short survey across what I have:
xpdf (sid): no support
kpdf (hardy): no support
okular (sid): no support
evince: not tested, but the PDF says no support
mupdf 1.2 (Debian sid): no support
mupdf 1.3 (MirBSD): no support
Acrobar Reader 5: no support
Adobe Reader 9: must be explicitly enabled
This
Michael Tokarev dixit:
>> some other distros have preallocation=full option for qemu-img
>
>Which other distros?
lsb_release -a says:
LSB Version:
:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Dist
Michael Tokarev dixit:
> I don't think this makes any sense. If you want fully-pre-allocated
> images, just use raw, there's no need to use qcow at all. You'll get
I'd actually prefer using an LVM LV, but I can’t always do what I want.
(In my case, the other admins argue with “qcow2 can do (mul
Package: edos-distcheck
Version: 1.4.2-13+b1
Severity: normal
tglase@tglase:~ $ = 3.3.2-2~)
1|tglase@tglase:~ $
Architecture: all
Replaces: python3 (<< 3.3.2-4~)
Depends: python3:any (>= 3.3.2-2~)
Breaks: python3 (<< 3.3.2-4~)
Description: Debian helper tools for packaging Python libraries and ap
Hi *,
since the RFH found no answers I will, most likely, upload
something like the following:
The next mediawiki-extensions upload will check whether the
pre-version is older than the current one (in preinst) and,
if so, remove *both* versions of the files (mediawiki and
mediawiki-extensions), *
Package: dose-distcheck
Version: 3.1.3-5
Severity: normal
Hi,
I get the following error with dose-debcheck in both wheezy and sid:
tglase@tglase:~ $ dose-debcheck --deb-native-arch=m68k --failures --explain >> $?"
Fatal error in module deb/debcudf.ml:
Unable to get real vers
Ralf Treinen dixit:
>> I get the following error with dose-debcheck in both wheezy and sid:
>
>Thanks for having produced a minimal input file to reproduce the bug,
>that is much appreciated!
You’re welcome!
>The problem seems to be in the generation of explanations, if you drop
>the --explain f
Paul Tagliamonte dixit:
>please vote on and decide on the default init system for Debian.
It’s not (just) about the _default_ but also on whether we will
force this default init system onto *all* our users, or whether
we commit to support more than one, and if so, how.
This is an *important* dis
Paul Tagliamonte dixit:
>It may be, but it's not for the project. Let's let this bug be, and
>have the tech cttie decide on *the* init system for Debian. If you want
No, this must really really be decided first.
bye,
//mirabilos
--
Beware of ritual lest you forget the meaning behind it.
yeah
Ondřej Surý dixit:
>then please submit your arguments directly there.
Sure.
>> Please stick to your side and make arguments for _your_ case, not
My “case” here is to ask CTTE to not make any decision and defer
to the Developers as whole, by means of a GR. As Guillem wrote:
| stop doing work du
Okay,
and here’s the reasoning for “sticking to an antiquated” init system:
I fully believe that Debian should be as flexible as possible
when meeting users’ needs. There is already a big downstream
running on Upstart, and I believe that, given the assumption
that we need to decide on one/the ini
Package: ftp.debian.org
Severity: normal
Hi,
I’ve begun porting pcc to Debian in the hope of making it useful
as an alternative compiler, especially as it’s very easy to use
it for cross-compiling since it doesn’t distinguish between cross
and native. (That was before M-A, and patching pcc up fo
Andrew Bartlett dixit:
>The issue here is not wrong file lists, but missing dependencies. When
Hm, but that’s still a bug in the package, then. (On the other
hand, you could just use rm -f, which wouldn’t error out, but
there are other failures happening too.)
bye,
//mirabilos
--
Beware of ri
Jelmer Vernooij dixit:
>Does 'xsltproc --nonet
>http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl'
>work properly on the m68k host with xsltproc and docbook-xsl
>installed?
I don’t know what “work properly” means here, but it takes about
20 seconds to not display anything an
Package: ifupdown
Version: 0.7.45
Severity: grave
Tags: security
Justification: user security hole
I’ve got a configuration snippet in /etc/network/interfaces (chmod 0600,
root-owned) on my work laptop like the following one:
iface tarent-lan inet dhcp
wireless-mode Managed
wirele
Package: php5-apcu
Version: 4.0.2-2
Severity: serious
Justification: breaks other software
When running Mediawiki with the APC user cache enabled,
and trying to run the Mediawiki DB upgrade script, which
previously worked, it fails with:
CACHE_ACCEL requested but no suitable object cache is prese
On Mon, 28 Oct 2013, Thorsten Glaser wrote:
> The reason for this appears to be:
>
> php5_invoke apcu: no action - module was disabled by maintainer for cli SAPI
Manually running sudo php5enmod apcu seems to fix this.
I don’t understand.
bye,
//mirabilos
--
tarent solutions GmbH
Roc
Jelmer Vernooij dixit:
>Can you provide the config.log from the Samba4 build? Configure tries
>to run this exact command, and for some reason it failed there.
Not from that exact build (any more), sorry. But I’m re-running it
and will get back to you on this.
bye,
//mirabilos
--
Beware of ritu
Source: console-tools
Version: 2:0.2.3-72
Severity: serious
Justification: fails to build from source (but built successfully in the past)
ksyms.c: In function 'list_charsets':
ksyms.c:1667:5: error: format not a string l
2013-10-30 19:57:38.0
+
@@ -1,3 +1,10 @@
+console-tools (2:0.2.3-72.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix FTBFS due to format string problem.
+
+ -- Thorsten Glaser Wed, 30 Oct 2013 19:57:25 +
+
console-tools (2:0.2.3-72) unstable; urgency=low
*
Package: git
Version: 1:1.7.10.4-1+wheezy1
Severity: normal
Tags: patch
Hi *,
gitweb uses p5-CGI which, according to its perldoc, defaults
to latin1 if no charset is given. This causes mojibake:
$ env GATEWAY_INTERFACE=CGI/1.1 REQUEST_METHOD=GET \
REQUEST_URI=/gitweb/ SERVER_PROTOCOL=HTTP/1.
Source: linux
Severity: wishlist
Tags: patch
Dear Maintainers,
please add the following patch to your next upload of src:linux,
as per discussion with upstream in… I’d include a link, but
article.gmane.org is currently down.
This option used to be always enabled, then the default changed
upstrea
Vincent Lefevre dixit:
>Well, that's very confusing, because both ksh93 and mksh are
>ksh alternatives. This can break scripts with "#!/bin/ksh".
ksh93 can break scripts with "#!/bin/ksh" because interpreting
leading-digit-zero numbers as octal is a *very* recent change,
and is *known* to break e
Source: minetest
Version: 0.4.9+repack-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
minetest FTBFS on release architectures mipsel, s390x and other
architectures ia64 (where it built in stable and testing), hurd-i386,
kfreebsd-amd64 (where
Vincent Lefevre dixit:
>Well, the scripts may be started sequentially, but this doesn't mean
>that the daemons will be and always in the same order. And they don't,
>as shows in the following log:
That’s due to the (now default with sysv-rc) use of parallel boot
in combination with insserv. It us
Steven Chamberlain dixit:
>Actually, even if they forked in the same order every time, they might
>not be *ready* in the same order. That would be the rationale for
>readiness protocols and other features of the more complex init systems.
Strong disagree. This actually is a bug in the initscript
Package: sudo
Version: 1.8.9p3-1
Followup-For: Bug #732008
I’ve just noticed the same problem (mostly because, on my four-core
workstation at $dayjob, a “sudo xz -9” made IceWM’s CPU monitor go
up by half instead of quarter) but cannot say since when it happens.
Both “sudo su -” and “sudo sleep 3
On Wed, 15 Jan 2014, Olivier Berger wrote:
> This seems related to SVN's way to delegate tasks to sqlite, as per
> http://subversion.tigris.org/issues/show_bug.cgi?id=3437
I’ve fixed it like this:
https://evolvis.org/pipermail/evolvis-platfrm-commits/2013-December/002728.html
This commit takes
On Thu, 16 Jan 2014, Olivier Berger wrote:
> Are you suggesting that this wouldn't happen if we configured the SVN
> repos differently, i.e. is only a side effect ?
>
> Can you elaborate on the enable-rep-sharing = false ?
Basically, setting “enable-rep-sharing = false” disables
that SQLite crap
On Thu, 16 Jan 2014, Olivier Berger wrote:
> So... I'm not sure the right fix is to set enable-rep-sharing to false,
> but I'd probably prefer to touch an empty file with proper rights before
> creating the repo, until svn fixes the issue with its sqlite
> sub-component.
You can’t do that nōn-rac
Steven Chamberlain dixit:
>Then he gives a preference for Debian's own insserv and startpar. It
>allows for boot order to be fixed (after running insserv once, the same
>/etc/rc2.d/Sxx numbering may be rsync'd out to many machines). startpar
I would like to express a preference for one init sys
1 - 100 of 4623 matches
Mail list logo
