Bug#685074: fusionforge: Provide plugin apache 2 conf snippets in the plugin's package

On Thu, 16 Aug 2012, Olivier Berger wrote: > It would be much clearer if every package managed its own installation > of the web server configuration IMHO. I guess the design decision behind that is that there’s more than one webserver potentially supported. Or, at least, used to. Though I think

Bug#684994: ifup: fails to open statefile, does not bring up the network

e this (didn’t try rebooting it yet, LUCKILY as it’s a hosted domU), and it was an old(er) sid box upgraded to newer sid. See below, too. Piotr Borkowski dixit: >On Thu, Aug 16, 2012 at 12:02:56PM +0200, Thorsten Glaser wrote: >> The current sysvinit configuration (with file-rc) is a

Bug#684994: [File-rc-users] Bug#684994: ifup: fails to open statefile, does not bring up the network

Alexander Wirt dixit: >> So this looks like a missing Depends (insserv is Prio: optional) and >> thus is a grave bug. After manually installing it (of *course* it was >> not installed previously, because file-rc allowed getting rid of it): >Ah, this is some kind of an upgrade bug and won't happen

Bug#684994: [File-rc-users] Bug#684994: ifup: fails to open statefile, does not bring up the network

Alexander Wirt dixit: >> Is there some magic to do that for _all_ init scripts, or will >> the file-rc postinst of the version you’re going to upload later >> take care of that? >In fact this should change all initscript. As this is dependency based >booting the whole table should get rebuild whe

Bug#685324: [Pkg-mediawiki-devel] Bug#685324: Local File Inclusion Vulnerability in contrib script

On Sun, 19 Aug 2012, Benny Baumann wrote: > Please upgrade the php-geshi package to latest upstream. With the freeze this is no longer possible. If this is indeed a security issue, we can either apply a backported fix or have the package removed from the release, at this point in time. bye, //mi

Bug#685323: [Pkg-mediawiki-devel] Bug#685323: Re: Bug#685324: Local File Inclusion Vulnerability in contrib script

On Tue, 21 Aug 2012, Benny Baumann wrote: > Given exactly the > 2-3 years this package will be in stable/oldstable is the reason why > there should be an update to something reasonably recent before the > package is put into a distribution. Sorry, it’s now too late for that. In May, something cou

Bug#685786: lynx-cur: debconf question for homepage does not accept https

Package: lynx-cur Version: 2.8.8dev.5-1 Severity: minor Upon dist-upgrading a lenny system, I got a debconf question, after answering it over and over again: ┌─┤ Lynx-cur Configuration ├─┐ │ Please enter the defaul

Bug#655388: python-numpy: FTBFS: [m68k] unrecognised long double format

Source: python-numpy Version: 1.5.1-3 Tags: upstream Hi, the m68k “long double” format isn’t recognised: […] compile options: '-Inumpy/core/src/private -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/include -I/usr/include/

Bug#655388: [Python-modules-team] Bug#655388: python-numpy: FTBFS: [m68k] unrecognised long double format

Sandro Tosi dixit: >I'll forward this upstream, but first I'd like to ask you a favour: is >there a chance you can test numpy from experimental (v.1.6.1)? This >way I can provide additional information to developers. I can try that, sure. >Also, in case they provide a patch, is there already a p

Bug#655388: [Python-modules-team] Bug#655388: python-numpy: FTBFS: [m68k] unrecognised long double format

Sandro Tosi dixit: >there a chance you can test numpy from experimental (v.1.6.1)? This >way I can provide additional information to developers. ValueError: Unrecognized format (['000', '000', '000', '000', '001', '043', '105', '147', '211', '253', '315', '357', '300', '031', '000', '000', '353'

Bug#652948: mediawiki: Incorrect sidebar rendering with Monobook skin and Firef*x 9

Hi all, I’ve just engineered a better fix for this and applied it to the MW 1.15 branch in the pkg-mediawiki SVN, so it will be included with the next regular upload. Index: mediawiki-1.15.5/skins/common/wikibits.js === --- mediawiki

Bug#655014: python-numpy: FTBFS: [m68k] unrecognised long double format

1,3 +1,19 @@ +python-numpy (1:1.5.1-3+m68k.2) unreleased; urgency=low + + [ Andreas Schwab ] + * debian/patches/20_m68k_long_double_format.diff +- add support for the Motorola 68k big endian long double + floating point representation format + Closes: #655388 + + [ Thorsten Gla

Bug#633038: NMU for sysklogd: 1.5-6.2

Dear Joey, I’ve uploaded Roger’s patch as NMU, versioned as 1.5-6.2, to the archive, since it’s a release critical bug, there has been no maintainer activity for way more than a week, etc. per the new 0-day rules. I’ve tested sysklogd before and after the /run transition. Thanks Roger for the pa

Bug#656227: Jenkins (Winstone) AJP doesn’t work with Apache

Source: jenkins-winstone Version: 0.9.10-jenkins-31+dfsg-1 ii apache2-mpm-prefork 2.2.21-5 Apache HTTP Server - traditional non-threaded model ii jenkins 1.409.3+dfsg-2 Continuous Integration and Job Scheduling Ser

Bug#678468: took care of RC bug, for now

Hi Boris, I’ve taken care of the RC bug for now, so the freeze won’t be a problem. I’ve not got the time to look at your suggested package, and I personally do not like dh > 5 plus Helmut raised a few points. (Note that an arch:all package can’t be binNMU’d, and an orphaned package should not be N

Bug#678468: took care of RC bug, for now

Boris Pek dixit: >> I’ve taken care of the RC bug for now, so the freeze won’t be a >> problem. > >Yes, I've got the messages from BTS. You forgot to close bug #606038. Sorry, didn't see that one (I had a look at the BTS, but didn’t audit the complete package as I just needed to fix the issue a

Bug#678984: gvfs: do not build-depend on src:libbluray

Source: gvfs Version: 1.12.3-1 Severity: serious Hi, src:gvfs currently build-depends on packages built from src:libbluray which needs OpenJDK to build, which, in turn, is not available everywhere. Please add support for building src:gvfs without it, at least on selected architectures (right now,

Bug#679190: override: pdksh:oldlibs/extra

-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Package: ftp.debian.org Hi, with the takeover of the pdksh binary package by src:mksh as transitional package (by request of the pdksh maintainer), the section and priority must be adjusted so our beloved tools know how to deal with the package (if

Bug#200750: pdksh ulimit file size problem, file can not be over 2GB

Jonathan Nieder dixit: >Maybe rgselk is on i386. I'm guessing it also works there, though. Hrm, then he wouldn’t have written about 64 bit? Anyway: r($n=0;$n<2097160;$n++){ < > print FH $x;} close(FH);' ll x tglas

Bug#679322: pdksh: add NEWS file for mksh transition

Package: pdksh Severity: serious Tags: pending As discussed in IRC today, pdksh symlinked to lksh should not transition to testing without a NEWS file detailing the transition and that users shall switch to mksh as login shell since lksh is not intended for interactive use. Will tackle this ASAP

Bug#569697: Please allow an intermediate upload with minimal change

Hi, just confirming that the attached patch works for me. (Now, if TenDRA were multiarch-safe…) So please, go forward. bye, //mirabilos -- “Having a smoking section in a restaurant is like having a peeing section in a swimming pool.” -

Bug#658914: imvirt: does not know about ARAnyM (m68k Atari emulator)

Michael Schmitz dixit: >The amount of TT RAM might be an additional clue. No, that’s configurable and arbitrary. >If that's not enough we could conceivably detect usage of natfeat drivers in >the >running kernel There unfortunately are kernels out there without those. Especially old ones. >

Bug#659583: pbuilderrc manpage doesn't mention that quotes are needed around multiple components

Maarten Bezemer dixit: >However, using the line: > > COMPONENTS=main universe Uhm. It’s a shell script. What do you expect? bye, //mirabilos -- Yay for having to rewrite other people's Bash scripts because bash suddenly stopped supporting the bash extensions they make use of -- To

Bug#658914: imvirt: does not know about ARAnyM (m68k Atari emulator)

Andreas Schwab dixit: >Finn Thain writes: > >> I don't know what those differences might be but the aranym developers may >> have some ideas. They may even know how to get the CPU to identify itself. Good plan. >You could probe for the natfeat instruction. That could work, especially if the p

Bug#658914: imvirt: does not know about ARAnyM (m68k Atari emulator)

Petr Stehlik dixit: ># cat /proc/hardware >Model: ARAnyM <--- output of That, again, would require a kernel that supports this. Oh, by the way, Linux 3.2.4 says: root@aranym:~ # cat /proc/hardware Model: Atari Falcon (with Afterburner040) System Memory: 800768K

Bug#658914: several messages

Michael Schmitz dixit: >cat /proc/scsi/scsi /proc/scsi ENOENT. >But then, the SCSI driver does not need to be compiled in or loaded either. True. Finn Thain dixit: >ColdFire with 680x0 emulation libraries (though that may not matter since >/proc/cpuinfo is only available on Linux). There

Bug#659861: cvs contains /usr/share/info/dir.gz

tags 659861 squeeze thanks Only in squeeze (lenny is EOL). Richard Kettlewell dixit: > Perhaps there should be some systematic approach to preventing packages > shipping such toxic files? IIRC there’s a lintian warning against it. OTOH, the pre-wheezy packaging of cvs is not mine and extremely

Bug#660030: texlive-base: fails to install (on m68k) any more

Source: texlive-base Version: 2009-15 Severity: important Hi, something changed, and I don't know what. This package probably is not the correct one, but it's the one that fails to configure, and you are probably the maintainer in the best situation to ana- lyse the problem, spot the correct pack

Bug#660030: texlive-base: fails to install (on m68k) any more

Hilmar Preusse dixit: >Running this command on the command line works fine for me. Could you >tell us, which version of luatex and which version of zlib1g is >installed? Ah. Sure. zlib got updated recently. root@aranym:~ # apt-cache policy luatex zlib1g zlib1g: Installed: 1:1.2.6.dfsg-1 Cand

Bug#660030: texlive-base: fails to install (on m68k) any more

Hilmar Preusse dixit: >I'm afraid you need a more recent luatex on m68k. Maybe recompiling >the source package of 0.50.0 would solve your problem. Ah ok, probably. Thanks. I will try that and close this not-bug then. >On the other hand: I wouldn't expect the problem at all if there is >no luatex

Bug#660149: atari-bootstrap: fails to boot kernel

Package: atari-bootstrap Version: 3.3-6.1 Severity: important X-Debbugs-CC: debian-...@lists.debian.org X-Debbugs-CC: rag...@chaosdorf.de ataboot.ttp failed to load the kernel (Linux 3.2.4 from stock linux-image-3.2.0-1-amiga_3.2.4-1_m68k.deb in sid) for ragnar76; he said he had to use ataboot.prg

Bug#658050: FTBFS: miniperl Out of memory during list extend at make_patchnum.pl line 126.

reassign 658050 gcc-4.6 thanks Dixi quod… >OK. Depending on when -6 was uploaded, it may very well be >a gcc-4.6 regression (m68k was switched from 4.4 to 4.6 only >recently). Will do. With gcc-4.4, the uploaded perl indeed builds. Reassigning to gcc-4.6 then. bye, //mirabilos -- Support mksh

Bug#660200: gforge-mta-postfix: postfix-to-mailman.py on Debian deb-specific/install-postfix.sh missing parameter

On Fri, 17 Feb 2012, Mathias Gebbe wrote: > Dear Maintainer, > > as said Yes, you put that into the upstream bugtracker. That should have been enough. Strictly spoken, the Debian BTS is for packaging issues, not upstream bugs. Duplicating by filing both is just making more work for developers.

Bug#550611: closed by Aron Xu (Bug#550611: fixed in netcat-openbsd 1.105-1)

Debian Bug Tracking System dixit: >#550611: please use libbsd instead of glib for strlcpy > >It has been closed by Aron Xu . This FTBFS (no pkg-config? did you forget to build in a clean chroot, e.g. with cowbuilder?). bye, //mirabilos -- “Having a smoking section in a restaurant is like havi

Bug#658050: FTBFS: miniperl Out of memory during list extend at make_patchnum.pl line 126.

Hi, just found http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47612 by almost-accident (in the MiNT patch for gcc). It does not seem to have been applied to the 4.6 branch yet; the MiNT patch is against 4.6 and contains this. I will test the patch from that PR in a local build and see whether it fix

Bug#550611: closed by Aron Xu (Bug#550611: fixed in netcat-openbsd 1.105-1)

Dixi quod… >This FTBFS (no pkg-config? did you forget to build in Now builds but throws errors when installing: Setting up netcat-openbsd (1.105-2) ... update-alternatives: warning: forcing reinstallation of alternative /bin/nc.openbsd because link group nc is broken. update-alternatives: warni

Bug#550611: closed by Aron Xu (Bug#550611: fixed in netcat-openbsd 1.105-1)

Aron Xu dixit: >Thanks for spotting this. I was a bit messy in the packaging of this >(actually patching on patched files had made me crazy). Will fix this You’re welcome, and I know the feeling for packages I took over (cvs in squeeze uses dbs for crying out loud, and there was a security fix re

Bug#660525: libffi on m68k failures

hangelog +++ libffi-3.0.10/debian/changelog @@ -1,3 +1,15 @@ +libffi (3.0.10-3+m68k.2) unreleased; urgency=low + + * Apply patch from Alan Hourihane to fix err_bad_abi testcase on m68k. + + -- Thorsten Glaser Mon, 16 Jan 2012 17:23:35 + + +libffi (3.0.10-3+m68k.1) unreleased; urgency=low + +

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

maximilian attems dixit: >so could it be out of blindness that we didn't properly build with >thumb instruction in Debian? I’ve tried enabling thumb, but the bugs didn’t go away with that either. bye, //mirabilos -- 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good guy. Bu

Bug#592959: Dovecot in backports

On Fri, 29 Jun 2012, micah anderson wrote: > is pending in BPO's NEW right now. However, what ended up happening is > that the BPO autobuilders picked it up and built it against stable > dovecot1. Backports generally do that; to build against another package from backports you need to have a ver

Bug#679932: fusionforge-plugin-mediawiki: Call to undefined method SkinFusionForge::tooltipAndAccesskey

On Mon, 2 Jul 2012, Olivier Berger wrote: > I've just upgraded mediawiki to 1.19 and now have the following > exceptions reported in the mediawiki pages : > Original exception: exception 'MWException' with message 'Call to > undefined method SkinFusionForge::tooltipAndAccesskey' in > /usr/share/m

Bug#680066: libatomic-ops: FTBFS on m68k: 1 of 4 tests failed

Source: libatomic-ops Version: 7.3~alpha1+git20120701-1 Severity: normal Justification: fails to build from source (but built successfully in the past) Hi, on m68k, libatomic-ops also fails in one test. I’m Cc’ing the porters in the hope that they help if they can, possibly at DebConf? If this pr

Bug#680081: slang2: FTBFS: ar: src/elfobjs/*.o: ENOENT (probably named src/m68kelfobjs/ but why?)

Alastair McKinstry dixit: >I can't reach crest.debian.net to test on m68k. Right, the porterbox has hardware issues TTBOMK, but you can try this on a VM youself: https://wiki.debian.org/Aranym/Quick >The following changes were made to CFLAGS Hm, this did not look like a CFLAGS issue to me. I th

Bug#680165: fusionforge-plugin-mediawiki: $MWCRON/dump-wikis.php Notice : Constant MEDIAWIKI already defined

severity 680165 wishlist # probably tags 680165 + wontfix thanks On Wed, 4 Jul 2012, Olivier Berger wrote: > I noticed the following problem, reported by the dump cron : > PHP Notice: Constant MEDIAWIKI already defined in > /usr/share/mediawiki/maintenance/Maintenance.php on line 530 This is

Bug#680225: libjack-jackd2-0 conflicts with libjack0

Package: libjack-jackd2-0 Severity: important Justification: release goal Multi-Arch Hi, libjack-jackd2-0 conflicts with libjack0, which is a bit unfortunate, as some things depend on either; waldi suggested to either take over the binary package if it’s the same lib, or use a different library n

Bug#680226: lib{nss,pam}-ldapd: apt wants to remove them on dist-upgrade in favour of lib{nss,pam}-ldap:i386

Package: libnss-ldapd Severity: important Hi, this situation is a bit weird, on an M-A enabled system (debugging hindered a bit due to #680225), after upgrading libnss-ldapd and libpam-ldapd to the latest version (or even before doing that), a further dist-upgrade wants to kill them and install l

Bug#680225: libjack-jackd2-0 conflicts with libjack0

Jonas Smedegaard dixit: >gstreamer0.10-plugins-good favors libjack-jackd2-0 but is also satisfied >with libjack0. Hrm. Then, libjack0 is not M-A yet, I guess, from the symptoms. bye, //mirabilos -- 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good guy. But he's always rig

Bug#680226: lib{nss,pam}-ldapd: apt wants to remove them on dist-upgrade in favour of lib{nss,pam}-ldap:i386

[… “interesting” M-A consequences …] Oh, sorry for disturbing an anthill then. This sounds entirely nōn-trivial to solve… Could this work: libnss-ldap and libnss-ldapd both provide the same virtual package and conflict with it? Same for the pam ones but a different virtual package. Just a wild-g

Bug#680672: kpartx: does not handle Atari partition map

Package: kpartx Version: 0.4.9-3 Hi, when creating a hdd image, losetup'ing it to /dev/loop0 and then creating partitions on it with atari-fdisk, kpartx -l -v /dev/loop0 doesn't show any partitions recognised. On i386, with MBR partition tables, this works. Cc'ing the porter list where I just h

Bug#658050: FTBFS: miniperl Out of memory during list extend at make_patchnum.pl line 126.

I’d try to help to debug this, but gdb behaves weird: erl-5.14.2${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH gdb --args ./miniperl -Ilib make_patchnum.pl < GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Bug#658050: FTBFS: miniperl Out of memory during list extend at make_patchnum.pl line 126.

Niko Tyni dixit: >Have you tried to rebuild 5.14.2-6? The only functionality change in >-7 is a Pod::Man one line fix, the rest are documentation and test >suite changes. It seems very improbable that any of these would >cause the error. OK. Depending on when -6 was uploaded, it may very well be

Bug#658914: imvirt: does not know about ARAnyM (m68k Atari emulator)

Package: imvirt Version: 0.9.2-1 Severity: wishlist Tags: upstream imvirt doesn’t know about ARAnyM (Atari Running on Any Machine): root@ara2:~ # imvirt pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. Use of uninitialized value $avail in concatenation (.) or string

Bug#658914: imvirt: does not know about ARAnyM (m68k Atari emulator)

Thomas Liske dixit: > Are there additional characteristics while running inside ARAnyM (i.e. cat > /proc/modules)? The dmesg logfile might not be available for (unprivileged) > users and the dmesg kernel buffer might be scrolled off. Hrm, good question. root@ara3:~ # cat /proc/modules ipv6 23794

Bug#658947: cvs: Uses perl4 corelibs without Depends

tags 658947 = pending thanks Dominic Hargreaves dixit: >This package currently uses one or more deprecated perl 4 era packages, >as shown on the lintian report[1]: This is sort of a false positive – cvs has a number of scripts in contrib/ which often don’t even work as-is but are provided as an

Bug#658955: Call-time pass-by-reference has been removed from php5 (>= 5.4)

On Mon, 6 Feb 2012, Ondřej Surý wrote: > PHP 5.4 is planned to be included in wheezy, as such, this bug might > become RC if not fixed before 5.4 is uploaded to sid. This bug will not become RC because the file is not used if not enabled manually – in fact, we are still waiting for a response fro

Bug#659108: lintian: suggestion: warn when short description starts with article

Source: lintian Severity: wishlist Hi, just saw it again, so here I suggest a lintian warning when a package’s short description starts with an article or so, that is, a/an/the and possibly others. For that matter, I’d like to see short descriptions that actually explain what packages do… bad ex

Bug#680080: Invalidated by dependency: Excuse for mediawiki-extensions

Hi, can *please* be something done about this, so we can ship a version of mediawiki-extensions that actually matches the version on mediawiki shipped in wheezy? What, exactly, needs to be done in/for json-js? Can I help? I’ve got Super Co^W^WDebian Developer Upload Powers. AFAICS, uglifyjs shou

Bug#679665: [Pkg-javascript-devel] Bug#680080: Invalidated by dependency: Excuse for mediawiki-extensions

On Tue, 10 Jul 2012, Jonas Smedegaard wrote: > Right now I am waiting for the judgement of the tech-ctte regarding > nodejs. See bug#614907. Ah. Luckily, that’s almost resolved. > I am concerned about switching compressor - see the discussion at > bug#679665. I see. (But yui was used before,

Bug#614907: [Pkg-javascript-devel] Bug#680080: Invalidated by dependency: Excuse for mediawiki-extensions

On Tue, 10 Jul 2012, Jonas Smedegaard wrote: > Because it performs worse, which makes it less used in general, which > makes it less tested, which makes it less trustworthy. I thought that > was already clarified at bug#679665. Does it make sense now? Thanks, yes. > It is helpful that you in

Bug#681184: mediawiki: includes courtesy copies of ECMAscript libs

Source: mediawiki Version: 1:1.18.1-1 Severity: serious Justification: Policy v3.9.3.1 §4.13 src:mediawiki contains embedded code copies of jQuery as well as its extensions Effects, Tipsy and UI. These are shipped in the mediawiki binary package, and at least three of those four are otherwise avai

Bug#680080: [Pkg-mediawiki-devel] Invalidated by dependency: Excuse for mediawiki-extensions

On Tue, 10 Jul 2012, Platonides wrote: > How does json-js block mediawiki-extensions? One of the extensions depends on that package. > a) MediaWiki ships with a copy of jQuery since 1.17 Ah, good to know, we’ll need to remove that. > b) MediaWiki resourceloader will automatically minify the ja

Bug#681773: mc: segfaults when /tmp/mc-root is not owned by root

Package: mc Version: 3:4.8.3-3 Severity: minor # mc Directory /tmp/mc-root is not owned by you Segmentation fault OK, admittedly (no idea why, though): drwx-- 2 tomcat55 adm 40 Jul 10 11:01 mc-root/ Still should not segfault, IMO. Minor inconvenience, at best. After rm -rf /tmp/mc-roo

Bug#603904: [Pkg-mailman-hackers] Bug#603904: Fresh installation of mailman has wrong permissions, causes archiving to fail

On Tue, 17 Jul 2012, NERvOus wrote: > This way mailman (running as "list") can write to > /var/lib/mailman/archive which is owned by group "www-data". Hrm, how about /usr/lib/mailman/bin/check_perms instead? bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.t

Bug#603904: [Pkg-mailman-hackers] Bug#603904: Fresh installation of mailman has wrong permissions, causes archiving to fail

On Wed, 18 Jul 2012, Luca Gibelli wrote: > but if you chgrp the dir to "list", then the webserver cannot access it > any longer, because its permissions are drwxrws---. Yes, that’s correct. If you want that, sudo adduser www-data list not the other way round though. bye, //mirabilos --

Bug#603904: [Pkg-mailman-hackers] Bug#603904: Fresh installation of mailman has wrong permissions, causes archiving to fail

On Wed, 18 Jul 2012, Luca Gibelli wrote: > If you run fix_perms -f as you suggested, the dir is chgrp'ed to "list" > and then indeed you need to add the user "www-data" to the group "list" > to make the private archive work. Hum yes, but that’s how upstream does it. > This means that any (php

Bug#614907: [Pkg-mediawiki-devel] [Pkg-javascript-devel] Bug#680080: Invalidated by dependency: Excuse for mediawiki-extensions

On Tue, 10 Jul 2012, Thorsten Glaser wrote: > > Right now I am waiting for the judgement of the tech-ctte regarding > > nodejs. See bug#614907. > > Ah. Luckily, that’s almost resolved. It has been resolved for days now, would please someone implement the solution? I can, as

Bug#677335: Fwd: Bug#677335: gforge-web-apache2: PHP Warning: ob_start(): output handler 'ob_gzhandler' conflicts with 'zlib output compression'

On Wed, 18 Jul 2012, Olivier Berger wrote: > Do you have any idea on how to try and investigate that ? Yes I did so (told people in IRC, IIRC). $ sudo a2dismod deflate This seems to be a new Debian standard setting for new installations. We can add a workaround to not use our own gzip compressi

Bug#680225: closed by Adrian Knoth (Re: Bug#680225: libjack-jackd2-0 conflicts with libjack0)

Debian Bug Tracking System dixit: >Their explanation is attached below along with your original report. >This is a known problem with ia32-libs. Don't use it, use multiarch Hm, this doesn’t work for stuff that directly depends on ia32-libs. But I guess it would be best for ia32-libs to use an al

Bug#686190: [Pkg-mediawiki-devel] Bug#686190: mediawiki-extensions-base: Fatal error: Call to undefined method Xml::hidden()

On Wed, 29 Aug 2012, Anye Li wrote: > When I migrated from squeeze to wheezy, my mediawiki wiki stopped Can you please upgrade to mediawiki-extensions-base from experimental? If that works for you, I’ll upload it to sid. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn •

Bug#686330: mediawiki: Multiple security issues

On Fri, 31 Aug 2012, Moritz Muehlenhoff wrote: > Please see here for more info: > http://www.gossamer-threads.com/lists/wiki/mediawiki/295767 Thanks. The Release Notes say that 1.19.2 is a security-fix release, and does not list any unrelated changes. Question is, (to the more seasoned MW packag

Bug#603904: [Pkg-mailman-hackers] Bug#603904: Bug#603904: Bug#603904: Fresh installation of mailman has wrong permissions, causes archiving to fail

On Sun, 22 Jul 2012, Thijs Kinkhorst wrote: > Indeed this entire bug stems from the conflict that there is between the > need of Mailman to write to that directory (as list), and for Mailman (as > www-data) to be able to read it. How about we add a second group and patch upstream sources to use t

Bug#681184: [Pkg-mediawiki-devel] Bug#681184: mediawiki: includes courtesy copies of ECMAscript libs

Platonides dixit: >Thorsten, how do you expect to handle it? Have not investigated it yet. Same as with the other occurrences, I guess – cut off the convenience copies of third-party code, patch the code to use the system-wide copy, and kick it until it ble^Wworks. >There's of course the risk of

Bug#681184: [Pkg-mediawiki-devel] Bug#681184: mediawiki: includes courtesy copies of ECMAscript libs

Platonides dixit: >Beware that jquery.tipsy has been modified at mediawiki repo (I just >opened bug 38733 to try merge them upstream). I think many people (need to) do that. It's short enough to not worry about it if it's in fact modified (I had to do so for Evolvis as well). Thanks for the head

Bug#682945: sks: recon does not start

Package: sks Version: 1.1.3-1 Severity: normal Hi, just noticed an error during logrotate’s cronjob, where it tried to restart sks but the recon part was not running. I have no idea what that is and how severe this is, if it is a problem at all. This server is a private installation that, by des

Bug#682992: unblock: mksh/40.9.20120630-2

ting (LP#1025843) and fix + bugs in the same code wrt. completion display and other expansions + * Document use of CONSERVATIVE_FDS in lksh manpage + + -- Thorsten Glaser Fri, 20 Jul 2012 23:32:37 + + mksh (40.9.20120630-1) unstable; urgency=low * The “GC2TDN7” upload --- mksh-40.9

Bug#660963: qt4-x11: m68k third attempt

tomic +builtins (from debian-ports GCC) like avr32 (Closes: #660963) + + -- Thorsten Glaser Sun, 29 Jul 2012 21:33:38 +0200 + qt4-x11 (4:4.8.2-1) unstable; urgency=low * New upstream release. diff -Nru qt4-x11-4.8.2/debian/patches/m68k.diff qt4-x11-4.8.2/debian/patches/m68k.diff --- qt

Bug#683188: API change in python-subversion breaks ViewVC, too

affects 683188 viewvc affects 683188 fusionforge-plugin-scmsvn thanks Mathias Gebbe noticed on IRC that this also affects ViewVC as used by FusionForge. Just FYI, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 548

Bug#683464: iceweasel: FTBFS on m68k due to invalid alignment assumptions

Source: iceweasel Version: 10.0.6esr-1 Tags: patch Hi, while building src:iceweasel (don't laugh please, libmozjs-dev is needed as build dependency by a *lot* of packages) on Debian/m68k, the first FTBFS (of how many to come, I don't know) occurs due to non-portable alignment assumptions. On m68

Bug#637232: Multiarch breaks support for non-multiarch toolchain

Jonathan Nieder dixit: > pcc (Portable C compiler): unfixed - http://bugs.debian.org/638309 Yes, but that was not the main showstopper for pcc. Besides upstream bugs on some architectures (recently, even Linux/amd64 broke again – I’m following pcc dev), the main problem was how to get pcc-l

Bug#683838: release-notes: transition: pdksh → mksh

Package: release-notes Severity: normal Hi, Robert asked me to replace pdksh with its successor mksh in time for the wheezy release, and we’d like it to be gone in jessie. Right now, pdksh is a transitional package, and the upgrade might need some sysadmin and/or user effort: ① The sysadmin need

Bug#684324: please consider merging patch tweaks needed for raspbian.

tags 684324 + pending thanks peter green dixit: > I'm currently working on an armv6 hardfloat derivitive of debian called > raspbian. \o/ Applied, will be in the next upload. Do you require one before the freeze? > When trying to build the latest version of dietlibc I ran into the > following

Bug#684431: python3-defaults: policy violation: dash in version number of native package

Source: python3-defaults Version: 3.2.3-5 Severity: important Justification: Policy §5.6.12 Hi, just skimming recent changelogs I came across this gem: python3-defaults (3.2.3-5) unstable; urgency=low […] * Change source format from native to 3.0 (native) […] Now, obviously, this package has

Bug#638309: pcc: does not find crt1.o

Mathieu Malaterre dixit: >any update on this ? None right now. It’s frozen anyway. I guess I can have a look at pcc once I get a bit of hacking time this week or the next. bye, //mirabilos -- Dann mach ich git annex copy --to shore und fertig ist das das ist ja viel cooler als ownCloud ... s

Bug#687305: RFP: mwlib -- MediaWiki render server for use with the Collection extension

Package: wnpp Severity: wishlist * Package name: mwlib Version : 0.14.0 Upstream Author : PediaPress GmbH * URL : http://www.mediawiki.org/wiki/Extension:Collection http://www.mediawiki.org/wiki/Extension:PDF_Writer * License : looks like 3-c

Bug#687450: checkbashisms: please add bounds check for "exit"

Package: devscripts Version: 2.12.2 Severity: wishlist Hi, please add a check to checkbashisms that "exit" has exactly 0 or 1 argument and, if it has one, it's a number between 0 and 255 inclusive. Note that "exit" doesn't support "--" as argument separator portably either, and "exit -1" has neve

Bug#687519: [Pkg-mediawiki-devel] Bug#687519: mediawiki: Sortable tables are not sortable at all

On Thu, 13 Sep 2012, Flavio Bello Fialho wrote: > I imagine that mediawiki 1:1.19.1-1 is > incompatible with libjs-jquery-tablesorter 6-1, although one depends on the > other. I suggest removing the dependency and using the upstream mediawiki file > instead of the symlink. That would violate Poli

Bug#687519: [Pkg-mediawiki-devel] Bug#687519: mediawiki: Sortable tables are not sortable at all

On Thu, 13 Sep 2012, Flavio Bello Fialho wrote: > Based on the file header, it seems mediawiki uses a fork of tablesorter or is > a modified version of it, specifically for use with mediawiki. I see. In this case, the Policy part I had in mind does not apply, and it’s correct to use the version s

Bug#686330: mediawiki: Multiple security issues

On Thu, 13 Sep 2012, Moritz Muehlenhoff wrote: > On Fri, Aug 31, 2012 at 06:34:38PM +0200, Julien Cristau wrote: > > Can't answer without a diff. > > Mediawiki maintainers, what's the status? Oh, sorry. Other stuff made me forget this for too long. The diff between the two tarballs is over 10

Bug#687641: mediawiki-extensions-base: Fatal error: Call to a member function isContentPage() on a non-object

On Fri, 14 Sep 2012, Anye Li wrote: > Package: mediawiki-extensions-base > Version: 2.6+wheezy1 > When I went from stable (squeeze) to testing (wheezy) my mediawiki Yes, the reason is that mediawiki-extensions 2.6 does not work with mediawiki 1.19, not even the +wheezy1 which was, as I predicted

Bug#659861: Processed: your mail

Adam D. Barratt dixit: >>> tags 659861 + squeeze-ignore > Apologies if I missed the discussion, but was that agreed with anyone on the > release team? It’s just not a bug in the package but a bug in the build environment of the person who did the last upload (which was subsequently fixed by a bi

Bug#659861: Processed: your mail

Adam D. Barratt dixit: > In which case it should probably be closed, as it doesn't apply to any current > package in the archive and no changes in the package are required to resolve > it. OK. Hrm. How do I tell the BTS’ version tracking that it’s fixed in 1:1.12.13-12+squeeze1+b1 on amd64 and n

Bug#659861: Processed: your mail

Adam D. Barratt dixit: > I don't think you can (in either case). You can mark a bug as found / fixed in > a binary version, but the BTS will translate that to the corresponding source > version. Similarly bug versions apply to the package, not to particular > architectures. Hrm. > I think the cl

Bug#702965: feedback: works

Hi, after upgrading libprocps0 the problem went away. Just so you know. Thanks, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser,

Bug#703852: [Pkg-mediawiki-devel] Bug#703852: Bug#703852: [mediawiki] mw{en, dis}ext ineffective for new installs

On Thu, 28 Mar 2013, Filipus Klutiero wrote: > There's a very simple solution to that which would solve even more > problems. Unfortunately, it requires a larger change. Well, let’s just not do that right now. The upgrade to 1.19 was on very short notice already, and, IIRC, Jonathan wanted to m

Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system

Package: pbuilder Version: 0.215 Severity: critical Justification: breaks unrelated software I’ve just did the following: ① get https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/pbuilderrc?rev=1.34 and install that file as /etc/pbuilderrc ② edit the MIRROR_wheezy line to use a local mirror ③

Bug#683838: release-notes: transition: pdksh → mksh

Julien Cristau dixit: >That sounds appropriate for a pdksh NEWS.Debian file, not the release >notes? I don’t think so – the change should really be done before the new pdksh package is installed, since it’ll immediately begin affecting users. >We can add pdksh to the list of packages that are go

Bug#683838: release-notes: transition: pdksh → mksh

Julien Cristau dixit: >If mksh is not a drop-in replacement then I'm not sure it's a good idea >to have it provide a transitional package. Might as well leave the old >pdksh alone so there's no functionality loss... mksh contains an lksh binary which is a drop-in for scripts. The only thing it’s

Bug#683838: release-notes: transition: pdksh → mksh

Joost van Baal-Ilić dixit: >I propose this text instead: > >--- > > > Pdksh to mksh transition ^ I’d not capitalise here, as it’s a name/“trade”mark. If you really must, I guess PDksh would make more sense. > >The Public Domain Korn Shell ( role="package">pdksh) >pac

Bug#704744: pbuilder: umounts /{dev,run}/shm of the *host* system

Junichi Uekawa dixit: >0.215 should have already fixed it, are you sure? Sorry, yes, I’m sure. My desktop at work now runs sid. bye, //mirabilos -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a cle

Bug#699397: sh4 also affected

Hi, sh4 is also affected from this; nacl looks like unported software that requires a positive-list of architectures supported in the Architecture field in debian/control, instead of “any”, so it will get marked as auto-not-for-us on all other arches. bye, //mirabilos -- Sorry, I’m annoyed toda

<    1   2   3   4   5   6   7   8   9   10   >