Bug#591577: Problem fixed in Smb4K 1.0.x
Hello again! Smb4K 1.0.x fixes this problem. It comes with the translations of the KDE project and the build system correctly installs all translations. A fix to the 0.10.x branch is not planned. However, either renaming smb4k/po/pt/pt.po to smb4k/po/pt/smb4k.po in the source package or renaming the pt.mo file to smb4k.mo during installation (as the reporter already stated) will provide the portuguese users with the translation. Since we moved to Sourceforge due to the unclear future of BerliOS some months ago, the source code of the newest stable versions can be found at http://sourceforge.net/projects/smb4k/files/Smb4K%20%28stable%20releases%29/ Best regards Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668580: procps: vmstat performs faulty averaging of interrupt/ctxt switch counters
Package: procps Version: 1:3.3.2-3 Severity: normal Dear Maintainer, If you just run vmstat or vmstat 1 the first line shows an average of certain counters since machine boot. However, I believe that at least the average interrupt and context switch counts are broken. Observer the following output: edb@lapedb:~/today$ grep -E -e "ctxt|intr" /proc/stat | cut -d \ -f 1-2 ; cat /proc/uptime ; vmstat intr 1051786 ctxt 1184893 1188.50 9001.64 procs ---memory-- ---swap-- -io -system-- cpu r b swpd free buff cache si sobibo in cs us sy id wa 1 0 0 6979028 77512 642036007318 111 125 3 1 95 2 So we have 1051786 interrupts during 1188 seconds which gives an average of: >>> 1051786/1188 885 Same for context switches: >>> 1184893/1188 997 One thing however which should be noted is that if I multiply vmstats output by 8, I get very close to the real results. (Why the magical 8 ? Believe it or not but my laptop has a quad core cpu with ht: edb@lapedb:~/today$ cat /proc/cpuinfo | grep processor | wc -l 8 ) I took a look at the code, and si/so bi/bo are also calculated the same way, so these might also be broken. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages procps depends on: ii initscripts 2.88dsf-22.1 ii libc6 2.13-27 ii libncurses5 5.9-4 ii libncursesw5 5.9-4 ii libprocps01:3.3.2-3 ii libtinfo5 5.9-4 ii lsb-base 4.1+Debian0 Versions of packages procps recommends: ii psmisc 22.16-1 procps suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667106: auralquiz: ftbfs with GCC-4.7
tags 667106 fixed-upstream thanks Thank you Cyril for the patch. Upstream has released a new version including this fix plus some new translations. I will package it up and seek sponsorship for it this weekend. Thanks, Dean -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667058: RFS: libupnp/1:1.6.16~git.20120316.d3d17da6-1 (updated package, transition upload)
On Tue, Apr 03, 2012 at 08:01:40PM +0100, Nick Leverton wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "libupnp" because my normal > sponsor seems to be away or busy at the moment. I would normally wait > patiently, but this release is the subject of a transition for which > others are waiting. The upload has been OK'd by ftpmasters, please > see transition bug #655912. Just updating the bug to note that this package is being reviewed off-list by a sponsor at present. Thanks Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666894: patch fixes 667827
Just want to add that the patch from Rafael Laboissiere also fixes the FTBFS on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667827 when libgdf was binNMUed for the boost 1.49 transition. May be worth a quick upload? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668579: febootstrap: Can I pack febootstrap 2.x that is goot for chroot environment?
Package: febootstrap Severity: normal Dear Maintainer, febootstrap 3.x cann't download and setup fedora chroot environment on Debian. See below. http://people.redhat.com/~rjones/febootstrap/ Can I pack febootstrap 2.x (it is old version) ? What package name should I choose for it, "febootstrap2" or "febootstrap-chroot"? Regards, Kiwamu. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667835: Working JBIG-KIT uploaded
Could you please test it with the version of jbigkit in the repository now? Please let me know if there are any issues outstanding. Warmest regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668578: icedove: Please update icedove version in backports
Package: icedove Version: 10.0.3-3 Severity: wishlist Dear Maintainer, icedove in squeeze-backports is currently at version 3.1 which is unmaintained. It would be great if you could update it to the version currently in testing, (including the calendar extension and the localisation packages) Thanks! Johannes -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3 ii fontconfig2.8.0-3.1 ii libasound21.0.25-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-27 ii libcairo2 1.12.0-2 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libevent-2.0-52.0.18-stable-1 ii libffi5 3.0.10-3 ii libfontconfig12.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-3 ii libgdk-pixbuf2.0-02.26.0-2 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-0 2.24.10-1 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libnspr4-0d 4.9-1 ii libnss3-1d3.13.3-1 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.24.4-1 ii libsqlite3-0 3.7.11-2 ii libstartup-notification0 0.12-1 ii libstdc++64.7.0-3 ii libvpx1 1.0.0-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxrender1 1:0.9.6-2 ii libxt61:1.1.1-2 ii psmisc22.16-1 ii zlib1g1:1.2.6.dfsg-2 Versions of packages icedove recommends: ii hunspell-da [hunspell-dictionary] 1:3.3.0-3 ii hunspell-de-at [hunspell-dictionary] 20110609-1 ii hunspell-de-ch [hunspell-dictionary] 20110609-1 ii hunspell-en-us [hunspell-dictionary] 20070829-5 ii myspell-de-de [myspell-dictionary]20110609-1 ii myspell-en-gb [myspell-dictionary]1:3.3.0-3 ii myspell-ru [myspell-dictionary] 0.99g5-18 Versions of packages icedove suggests: ii gconf-service 3.2.3-4 ii libgconf-2-4 3.2.3-4 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libnotify40.7.5-1 ii ttf-lyx 2.0.3-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668577: Debian maintainer annual ping for Russell Stuart
Package: debian-maintainers Severity: normal My annual ping as per: http://wiki.debian.org/DebianMaintainer/Tutorial#Annual_ping (If the policy is now that we stay current by uploading packages, it would be nice if that page was updated accordingly.) signature.asc Description: This is a digitally signed message part
Bug#663897: icedove: Please package icedove 11
Package: icedove Version: 10.0.3-3 Followup-For: Bug #663897 Hi, it would really be great if you could update icedove to the latest version, as I have some extensions, which no longer work with Thunderbird 10 but require 11... Thanks, Johannes -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (250, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.3 ii fontconfig2.8.0-3.1 ii libasound21.0.25-2 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-27 ii libcairo2 1.12.0-2 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libevent-2.0-52.0.18-stable-1 ii libffi5 3.0.10-3 ii libfontconfig12.8.0-3.1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-3 ii libgdk-pixbuf2.0-02.26.0-2 ii libglib2.0-0 2.32.0-4 ii libgtk2.0-0 2.24.10-1 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libnspr4-0d 4.9-1 ii libnss3-1d3.13.3-1 ii libpango1.0-0 1.30.0-1 ii libpixman-1-0 0.24.4-1 ii libsqlite3-0 3.7.11-2 ii libstartup-notification0 0.12-1 ii libstdc++64.7.0-3 ii libvpx1 1.0.0-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxrender1 1:0.9.6-2 ii libxt61:1.1.1-2 ii psmisc22.16-1 ii zlib1g1:1.2.6.dfsg-2 Versions of packages icedove recommends: ii hunspell-da [hunspell-dictionary] 1:3.3.0-3 ii hunspell-de-at [hunspell-dictionary] 20110609-1 ii hunspell-de-ch [hunspell-dictionary] 20110609-1 ii hunspell-en-us [hunspell-dictionary] 20070829-5 ii myspell-de-de [myspell-dictionary]20110609-1 ii myspell-en-gb [myspell-dictionary]1:3.3.0-3 ii myspell-ru [myspell-dictionary] 0.99g5-18 Versions of packages icedove suggests: ii gconf-service 3.2.3-4 ii libgconf-2-4 3.2.3-4 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libnotify40.7.5-1 ii ttf-lyx 2.0.3-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668247: [Pkg-utopia-maintainers] Bug#668247: power control on command line
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/11/12 00:39, Michael Biebl wrote: > > There is pm-suspend and pm-hibernate (from pm-utils) and and the upower > command line utility to query power related information. > > What exactly are you missing? > The man page to pm-utils says "These commands will usually be called by UPower or ..." I would like to trigger this on the command line. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk+HttQACgkQUTlbRTxpHjd40wCfXzylW00FcztbPkxFkNYcUGX7 BXcAnAnH4W1dTs19u6mejyP/ZpatuLx4 =K+ic -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#343575: patch breaks build checks
Thanks for the patch you provided in early Feb. Unfortunately, applying
this patch causes 'make check' to fail like so:
make[4]: Leaving directory `/tmp/buildd/gzip-1.4/build'
GENgzip.doc.gz
{ test '..' != . || ./zdiff --__bindir . -c gzip.doc.gz; }
./zdiff --__bindir . -c ../gzip.doc ../gzip.doc
./zdiff --__bindir . ../gzip.doc gzip.doc.gz
./zdiff --__bindir . -c - ../gzip.doc
pgpsYGFkqyAQM.pgp
Description: PGP signature
Bug#665073: Version 0.4.2.3-4 unusable
Hi, I just updated 0.4.2.3-3 to 0.4.2.3-4 in Wheezy and FontyPython doesn't install or uninstall pogs anymore. I tried starting from scratch with a clean .fonts folder and removing .fontypython to make sure it wasn't some old configuration or broken font symlink causing this, but I get the same result: new pogs can't be installed either. When I try to install a pog I receive the following error message: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/fontypythonmodules/gui_Right.py", line 236, in multiClick fpsys.state.targetobject.install() File "/usr/lib/python2.7/dist-packages/fontypythonmodules/fontcontrol.py", line 775, in install linkDestination = os.path.join(self.__pc.userFontPath(), dirname ) File "/usr/lib/python2.7/dist-packages/fontypythonmodules/pathcontrol.py", line 61, in userFontPath return self.__userfontpath AttributeError: PathControl instance has no attribute '_PathControl__userfontpath' In my systems fontypython was working great until this update and I'm pretty sure that it isn't caused by anything else because I one of my computers I updated everything except fontypython (left version 0.4.2.3-3 installed) and it still works as usual. Everything points to this new version, and I haven't been able to find a workaround to make it work. Kind regards, Guillermo Espertino.
Bug#668576: ldb: Please update version of tdb in Build-Depends.
Source: ldb
Version: 1:1.1.5-1
Severity: important
Justification: fails to build from source
Tags: patch
Hi,
ldb is wrong in version specification of tdb, it may be unable to build.
Because ldb require 1.00 or above versions of tdb.
Please see build log of alpha and sh4.
http://buildd.debian-ports.org/status/fetch.php?pkg=ldb&arch=alpha&ver=1%3A1.1.5-1&stamp=1334212987
http://buildd.debian-ports.org/status/fetch.php?pkg=ldb&arch=sh4&ver=1%3A1.1.5-1&stamp=1334217066
-
Checking for getpwnam_r
: ok
Checking for getpwuid_r
: ok
Checking for getpwent_r
: ok
Checking for declaration of getpwent_r
: ok
Checking C prototype for getpwent_r
: not found
Checking for declaration of getgrent_r
: ok
Checking C prototype for getgrent_r
: not found
Checking C prototype for getpwent_r
: not found
Checking C prototype for getgrent_r
: not found
Checking for getgrouplist
: ok
Checking for system tdb >= 1.2.10
: not found
ERROR: System library tdb of version 1.2.10 not found, and bundling disabled
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory `/build/buildd-ldb_1.1.5-1-alpha-4JFVqG/ldb-1.1.5'
make: *** [build-arch] Error 2
-
Please update version of tdb in Build-Depends.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
ldb-1.1.5.debdiff
Description: Binary data
Bug#620543: upgrade from lenny to squeeze: mailbox_command changed
On Sat, Apr 02, 2011 at 04:29:52PM +0200, Daniel Pocock wrote: > On my lenny system, I had this setting in main.cf: > mailbox_command = procmail -a "$EXTENSION" DEFAULT=$HOME/Maildir/ > MAILDIR=$HOME/Maildir > > After doing `apt-get dist-upgrade' to squeeze, I found it had changed to > this: > > mailbox_command = procmail -a "$EXTENSION" > > which would send incoming mail to /var/spool/mail mboxes instead of > $HOME/Maildir I believe that you at one time told debconf that the mailbox command should be: mailbox_command = procmail -a "$EXTENSION" and it was simply enforcing what you told it. Maintaining a file with both debconf and vi is extremely problematic, and prone to the admin discovering that he changed something in the wrong place. lamont -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668316: [Team-xbmc] Bug#668316: xbmc: Please enable builds for arches other than amd64 and i386
Hi, Andres.
On Apr 12, 2012, at 10:09 PM, Andres Mejia wrote:
2012/4/10 Rogério Brito :
I saw that the latest revision of xbmc (BTW, thanks for uploading
it to
Debian---one fewer package from dmo) disabled builds for
architectures other
than amd64 and i386. Would it be possible to have it enabled for
other
architectures? The changelog didn't mention the reason for the
restriction.
At least for PowerPC there are people that may (and are willing to)
test the
packages.
Yes, builds for the other archs will be reactivated soon. We're
currently working on getting the ARM builds working.
Great, thanks for considering this. I figured out that since dmo
offers the packages for arches other than amd64 and i386, then Debian
can too. :)
For now, I at least want the amd64 and i386 packages to enter testing.
OK, that's a sensible thing. What about uploading new test packaging
to experimental, to not disrupt the transition to testing? That way,
we could achieve the best of both worlds.
BTW, thanks a lot for packaging xmbc. This package in particular makes
Debian increase so much in value on its own.
One next step would be to sanitize the build system of handbrake to
make another "high profile" package come from Debian proper...
Thanks again,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668575: encfs: don't mount again anymore
Package: encfs Version: 1.7.4-2.4+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, * What led up to the situation? I transferred 2 directories encrypted by default in aes to new ones encrypted in BF (both use a 511 characters password). After creation, my new directories were mounted, so I transferred 2x256GB files. * What exactly did you do (or not do) that was effective (or ineffective)? When I want to mount my new directories it utterly fail: /OTHER$ encfs -v /OTHER/.AZ /OTHER/AZ 04:45:48 (main.cpp:523) Root directory: /OTHER/.AZ/ 04:45:48 (main.cpp:524) Fuse arguments: (daemon) (threaded) (keyCheck) encfs /OTHER/AZ -s -o use_ino -o default_permissions 04:45:49 (FileUtils.cpp:177) version = 20 04:45:49 (FileUtils.cpp:181) found new serialization format 04:45:49 (FileUtils.cpp:199) subVersion = 20100713 04:45:49 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(3:0:0) 04:45:49 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16 04:45:49 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(3:0:0) 04:45:49 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16 04:45:49 (FileUtils.cpp:1620) useStdin: 0 EncFS Password: 04:46:26 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(3:0:0) 04:46:26 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16 04:46:29 (FileUtils.cpp:1628) cipher key size = 52 04:46:29 (SSL_Cipher.cpp:604) checksum mismatch: expected 1644232459, got 2316882196 04:46:29 (SSL_Cipher.cpp:605) on decode of 48 bytes Error decoding volume key, password incorrect 04:46:29 (openssl.cpp:48) Allocating 41 locks for OpenSSL So I made a test: encfs /OTHER/.TST /OTHER/TST (choosed "p" and used the same password) at the end of the creation, directory was correctly mounted, but ASA I fusermount -u /OTHER/TST I wasn't able to remount it anymore (same error message as above). * What was the outcome of this action? I left my new encrypted directories mounted from creation, afraid I couldn't retrieve my files. * What outcome did you expect instead? encfs to work correctly and don't refuse to re-mount. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages encfs depends on: ii fuse 2.8.7-1 ii libboost-filesystem1.49.0 1.49.0-2 ii libboost-serialization1.49.0 1.49.0-2 ii libboost-system1.49.0 1.49.0-2 ii libc6 2.13-27 ii libfuse2 2.8.7-1 ii libgcc1 1:4.7.0-3 ii librlog5 1.4-2 ii libssl1.0.0 1.0.1-4 ii libstdc++64.7.0-3 encfs recommends no packages. encfs suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#626648: installation lacks RELEASE_NOTES-2.7 documentation file
tags 626648 + wontfix -- It also lacks RELEASE_NOTES-1.0 RELEASE_NOTES-1.1 RELEASE_NOTES-2.0 RELEASE_NOTES-2.1 RELEASE_NOTES-2.2 RELEASE_NOTES-2.3 RELEASE_NOTES-2.4 RELEASE_NOTES-2.5 RELEASE_NOTES-2.6 (which are found in the source, and not delivered by Debian, nor the upstream install process.) I'm not planning to deliver useless old files. lamont -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#652511: postfix: Postfix fails to start after upgrade due failed `Running newaliases postalias …'
On Sun, Dec 18, 2011 at 12:48:44AM +0100, Pascal Volk wrote:
> No idea why the Postfix package creates /etc/aliases if the file doesn't
> exist. The postinst script probably should check `postconf -h alias_database`
> output. And it will hopefully do nothing if the output looks like
> `${indexed}aliases'.
Debian policy, see section 11.6 Mail transport, delivery and user agents:
...
/etc/aliases is the source file for the system mail aliases (e.g., postmaster,
usenet, etc.), it is the one which the sysadmin and postinst scripts may edit.
After /etc/aliases is edited the program or human editing it must call
newaliases. All MTA packages must come with a newaliases program, even if it
does nothing, but older MTA packages did not do this so programs should not
fail if newaliases cannot be found. Note that because of this, all MTA packages
must have Provides, Conflicts and Replaces: mail-transport-agent control
fields.
...
lamont
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668574: tcsh: "echo ``" causes segfault
Package: tcsh Version: 6.17.02-4 Severity: minor Looks like this: > echo $version tcsh 6.17.02 (Astron) 2010-05-12 (x86_64-unknown-linux) options wide,nls,dl,al,kan,rh,nd,color,filec > echo `` Segmentation fault Exit 139 > (I use "set printexitvalue") This was not the behavior as of tcsh 6.17.00: > echo $version tcsh 6.14.00 (Astron) 2005-03-25 (x86_64-unknown-linux) options wide,nls,dl,al,kan,rh,nd,color,filec prototype:~> echo `` > Thanks. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tcsh depends on: ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-5 shared libraries for terminal hand tcsh recommends no packages. tcsh suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583476: openscad ITP
On Thu, Apr 12, 2012 at 8:03 PM, Christian M. Amsüss wrote: >> I can sponsor it [...] > > thank you. i'll prepare an updated package (to section main, with > changelog collapsed, standards version updated, and possible new lintian > warnings fixed), and notify you when it's ready. Great. It doesn't matter too much to me if you make them UNRELEASED or just a single entry. If I was doing it, I probably would just put it as a single entry "Initial release (Closes: #583476)", but you're maintainer so you're free to do it how you see fit for the package. Yes, let me know when it's ready and I'll check over it once again and upload. I know you've been working on this for some time, and it can feel "lonely" when you're not getting feedback, but lots of people will appreciate your work (licensing, packaging, fixing upstream problems). ~Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649146:
forcemerge 650234 649146 reassign 650234 eglibc retitle 650234 eglibc: libc-2.11.x.so segfaults when used with ld-2.13.so thanks Hi, this seems more of an eglibc issue, so I am reassigning. Daniel Kahn Gillmor did a lot of useful tinkering in http://bugs.debian.org/650234. Thanks, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#634902: (no subject)
In #626680 (console-data: setting overwritten by reboot) Christian says: "console-data should be replaced by console-setup". Also: c-s provides the "keyboard-configuration" package. "dpkg-reconfigure keyboard-configuration" apparently offers the option to use a keymap. Additinally there are several debconf preseeding items for keyboard-configuration. IMO we should use this. It seems that setting the keyboard is not that easy as before (by just using the variable KEYMAP). -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667442: r-base-core: Help docs unavailable with libpcre3 8.30
On 4 April 2012 at 20:08, Shyamal Prasad wrote: | | > "Dirk" == Dirk Eddelbuettel writes: | | Dirk> | It might be worth updating the dependency to libpcre >= 8.30 | | Dirk> That may in fact be thw minimum requirement now. | | I tried building R 2.15 against PCRE 8.12 since I my curiosity got the | better of me (and I'm using R more than usual this month). It works | fine, even when dynamically linked against libpcre3 8.30. | | In fact, I found that src/main/util.c has been cleaned up to not include | pcre.h and access the previously private _pcre_valid_utf8 function. So I | can confirm 8.30 is *not* the new minimum (in fact, I suspect the R source | is now more portable for PCRE versions than before). | | Dirk> I guess putting libpcre3 'on hold' to keep the old version | Dirk> would work too. | | It sure does! | | Dirk> But hopefully by April 9 we should have R 2.15.0 in testing... | | Yep, please go ahead and close this when you want to. It might be worth | leaving it open until April 9 on the off chance that this report helps | some one else who runs into the same issue (who will probably need to | browse http://snapshot.debian.org/package/pcre3/8.12-3/#libpcre3_8.12-3 | and install that version :-) Closing this now as R 2.15.0 did in fact make it to testing. Thanks again for eagle-eyed work on this. Dirk | | Cheers! | Shyamal -- R/Finance 2012 Conference on May 11 and 12, 2012 at UIC in Chicago, IL See agenda, registration details and more at http://www.RinFinance.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668573: coreutils: coreutils-dbg
package: coreutils severity: wishlist Some issues require debugging of certain coreutils tools (e.g. chroot in bug #649146). For those cases, it would be very useful to have a coreutils-dbg package. As an aside, redhat does provide this as a convenience to their developers. Thanks, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668316: [Team-xbmc] Bug#668316: xbmc: Please enable builds for arches other than amd64 and i386
tags 668316 upstream pending
stop
2012/4/10 Rogério Brito :
> Package: xbmc
> Severity: wishlist
> Version: 2:11.0~git20120403.ec33f1f+repack1-5
>
> Hi.
>
> I saw that the latest revision of xbmc (BTW, thanks for uploading it to
> Debian---one fewer package from dmo) disabled builds for architectures other
> than amd64 and i386. Would it be possible to have it enabled for other
> architectures? The changelog didn't mention the reason for the restriction.
>
> At least for PowerPC there are people that may (and are willing to) test the
> packages.
>
>
> Regards,
>
> --
> Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
> http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~team-xbmc
> Post to : team-x...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~team-xbmc
> More help : https://help.launchpad.net/ListHelp
Yes, builds for the other archs will be reactivated soon. We're
currently working on getting the ARM builds working. For now, I at
least want the amd64 and i386 packages to enter testing.
--
~ Andres
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654819: Please enabled hardened build flags
* Moritz Mühlenhoff wrote: > On Thu, Jan 05, 2012 at 11:18:09PM +0100, Moritz Muehlenhoff wrote: > > Source: libcgroup > > Severity: important > > Tags: patch > > > > Please enable hardened build flags for your package. Since your > > package has already been converted to dh, setting debian/compat > > to 9 is all you need to do. > > > > I've tested in a local build that this is sufficient to enable > > hardened build flags. > > What's the status? Do you plan an upload in the next weeks or > shall I upload a NMU? I'm working a new upstream release, but I think you should NMU if you have it ready. I have no objection. -- Jon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668404: xbmc-live: dependency on upstart prevents using xbmc with sysvinit
severity 668404 important stop Thanks for your report. xbmc-live requires upstart to be installed. Note that xbmc-live is not necessary to install and use the xbmc package. I did not find anything in policy that says packages cannot require the use of another init system. The only language I found pertaining to this is Debian policy 9.3, which pertains to how maintainer scripts should be provided for the init system, and has language like "should" or "may" and not "must" or "require." I'm downgrading this bug to important. -- ~ Andres -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666569: maint-guide: FTBFS: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty:852: I can't find file `t3enc.def'.
Hi Osamu,
On Fr, 13 Apr 2012, Osamu Aoki wrote:
> > > I'd vote for contacting (d)ctt to ask for a comment.
>
> What is (d)ctt ???
(de.)comp.text.tex, the probably most active and most responsive place
to contact with any TeX related problem.
The TeX Live mailing list is also here, but it only for the development
of TeX Live, not for package support.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
POPCASTLE (n.)
Something drawn or modelled by a small child which you are supposed to
know what it is.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654708: backupninja: rsync handler only respects the first rsync option
Em Mon, Apr 09, 2012 at 02:13:01PM +0200, Paul van Tilburg escreveu:
> This partly fixes it. Indeed, the --delete gets passed on now, but
> still expansion happens.
> But the expansion still happens (irregularly), so '/*bin' is expanded to
> '/bin' and '/sbin', but '/home/*/.cache' isn't, and '/home/*/Music' is!?
Hi Paul, thanks again for the reportback. I opened a new upstream bug as
this looks like another issue, but still related with your rsync handler
experience: https://labs.riseup.net/code/issues/3882
Could you try the patch below?
---
From aa8d0f864830036e12e52696243c05df76d678e2 Mon Sep 17 00:00:00 2001
From: Silvio Rhatto
Date: Thu, 12 Apr 2012 21:29:57 -0300
Subject: [PATCH 1/1] Quoting $exclude and $excludes and avoiding a for loop on
$exclude to not expand wildcards in beforehand (upstream #3882)
---
handlers/rsync.in |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
diff --git a/handlers/rsync.in b/handlers/rsync.in
index e253c5c..a77da2a 100644
--- a/handlers/rsync.in
+++ b/handlers/rsync.in
@@ -277,9 +277,7 @@ function eval_config {
mv=move_files
fi
- for path in $exclude; do
-excludes="$excludes --exclude=$path"
- done
+ excludes=`echo "$exclude" | sed -e 's/^/--exclude=/g' -e 's/ / --exclude=/g'`
}
@@ -1113,8 +,8 @@ for SECTION in $include; do
set_dest
info "Syncing $SECTION on $dest_path..."
- debug $nice $rsync "${rsync_options[@]}" $filelist_flag $excludes
$batch_option $orig $dest_path
- $nice $rsync "${rsync_options[@]}" $filelist_flag $excludes $batch_option
$orig $dest_path | tee -a $log
+ debug $nice $rsync "${rsync_options[@]}" $filelist_flag "$excludes"
$batch_option $orig $dest_path
+ $nice $rsync "${rsync_options[@]}" $filelist_flag "$excludes" $batch_option
$orig $dest_path | tee -a $log
if [ "$?" != "0" ]; then
fatal "Rsync error when trying to transfer $SECTION"
--
1.7.2.5
--
rhatto at riseup.net
pubkey 64E39FCA / keys.indymedia.org
signature.asc
Description: Digital signature
Bug#614233: Is the debian-doc kfreeBSD-ready?
Hi On Wed, Apr 11, 2012 at 08:34:52AM +0200, Robert Millan wrote: > El 11 d’abril de 2012 5:24, David Prévot ha escrit: > > Hi kFreeBSD folks, Hurd folks CC. > > > > After taking care of the website (mostly changing “Debian GNU/Linux” to > > a simple “Debian” where it's accurate), we are wondering if our Debian > > documentation is kFreeBSD-ready, i.e. can we safely drop “GNU/Linux”, or > > do we need to tweak the documentation first? maybe ... > I can't answer your question, however I wanted to comment something > about one of the proposed texts: > > | Debian is a free operating system (OS) for your computer. An operating > | system is the set of basic programs and utilities that make your > | computer run. Debian uses the Linux or FreeBSD kernel (the core of an > | operating system), but most of the basic OS tools come from the GNU > | project; hence the name Debian GNU/Linux or Debian GNU/kFreeBSD. > > This is saying that FreeBSD is a kernel, and that Debian uses it. But > that's not true. Debian doesn't use FreeBSD, only a small part of it > (its kernel, plus some bits of kernel-related code). The phrase > "kernel of FreeBSD" (or its abbreviation, "kFreeBSD") is often used to > refer to the situation unambigously. Very good point. I also think placing equivalent weight for GNU/Linux and GNU/kFreeBSD might skew the reality. Just because we released GNU/kFreeBSD does not make it to gain the completely equivalent status as GNU/Linux. When we look at the recent sysyemd/upstart/sysvint discussion, this is obvious. Now we have: | Debian systems currently use the Linux kernel or the FreeBSD kernel. | Linux is a piece of software started by Linus Torvalds and supported by | thousands of programmers worldwide. FreeBSD is an operating system | including a kernel and other software. | | However, work is in progress to provide Debian for other kernels, | primarily for the Hurd. The Hurd is a collection of servers that run on | top of a microkernel (such as Mach) to implement different features. The | Hurd is free software produced by the GNU project. | | A large part of the basic tools that fill out the operating system come | from the GNU project; hence the names: GNU/Linux, GNU/kFreeBSD and | GNU/Hurd. These tools are also free. I think adding some historical context should make this balanced. I propose the following to keep this part not too long: | Debian system was created as the Free operating system initially on the | i386 PC platform using the Linux kernel started by Linus Torvalds with | many system tools from the GNU project. Thus Debian was initially called | as "Debian GNU/Linux". | | Since then, Debian has been ported to various hardware platforms and | Free kernel platforms. | | Debian has released its ports using the kernel from FreeBSD project with | the same set of GNU tools as "Debian GNU/kFreeBSD". | | There are activities in progress to port Debian system to the Hurd from | GNU project as "Debian GNU/Hurd". Hurd is a collection of servers that | run on top of a microkernel (such as Mach). This way, a change in future for "Debian GNU/kFreeBSD" or "Debian GNU/Hurd" only requires to change one paragraph. (My initial proposal we a bit too much to put all Debian GNU/* together.) Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666569: maint-guide: FTBFS: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty:852: I can't find file `t3enc.def'.
Hi,
I am short on time now ...
On Fri, Apr 13, 2012 at 07:40:18AM +0900, Norbert Preining wrote:
> Hi Hilmar,
>
> thanks for the example, yes, that is true.
>
> On Do, 12 Apr 2012, Hilmar PreuÃe wrote:
> > ifxetex.sty is in texlive-base. The problem goes away if
> > \usepackage{xeCJK} or \usepackage[french]{babel} is commented. The
>
> Well, honestly this is a common problem, you ar enot expected to
> mix everything with everything.
I see .. So this problem can be avoided for DDP pages building by
changing build script/xslt a bit... I will think about it.
> > I'd vote for contacting (d)ctt to ask for a comment.
What is (d)ctt ???
> I guess yes, that is the best solution, or ask the xeCJK maintainers.
>
> In any case, this is not a packaging issue, so if it is solved, fine,
> if not, I can live with it, the failing document has to be
> adapted.
Sure.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#600286: atl1c driver hangs after "NETDEV WATCHDOG: eth0 (atl1c): transmit queue 0 timed out"
Greetings, I found this thread https://lkml.org/lkml/2012/2/24/365 with a patch of https://lkml.org/lkml/diff/2012/2/24/365/1 perhaps it assists some how on this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655503: marked as done (Please enabled hardened build flags)
Debian Bug Tracking System (13/04/2012): > Package: x11-xserver-utils > Version: 7.6+3 > Severity: important > Tags: patch […] > Source: grep > Source-Version: 2.11-1 > Format: 1.8 > Date: Fri, 13 Apr 2012 09:20:46 +1000 > Source: grep > Binary: grep > Architecture: source mipsel > Version: 2.11-1 > Distribution: unstable > Urgency: low > Maintainer: Anibal Monsalve Salazar > Changed-By: Anibal Monsalve Salazar > Description: > grep - GNU grep, egrep and fgrep > Closes: 651617 655503 668534 > Changes: > grep (2.11-1) unstable; urgency=low > . >* New upstream version 2.11 > Closes: 668534 > Fix "input file == output file detection and -q" > Closes: 651617 >* Enable hardened build flags > Patch by Moritz Muehlenhoff > Closes: 655503 This isn't the bug number you're looking for. >* Drop 55-185208-bigfile.patch as it doesn't work >* Standards Version is 3.9.3 Mraw, KiBi. signature.asc Description: Digital signature
Bug#668572: installation-guide: [patch] mention DEBCONF_DEBUG
Package: installation-guide Severity: normal Tags: patch Hi please consider this patch explaining the use of DEBCONF_DEBUG when debugging a preseeded installation. I found it a helpful tool. Cheers Vince Index: manual/en/appendix/preseed.xml === --- manual/en/appendix/preseed.xml (revision 67384) +++ manual/en/appendix/preseed.xml (working copy) @@ -1578,6 +1578,14 @@ questions that are actually displayed during an installation and not for internal parameters. + + +For more debugging information, use the boot parameter +DEBCONF_DEBUG=5. +This will cause debconf to print much more detail +about the current settings of each variable and about its progress through +each package's installation scripts. + -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583476: openscad ITP
On Thu, Apr 12, 2012 at 06:30:33PM -0400, Scott Howard wrote: > CGAL is in main now, does that mean your package can be also? it can be. by the time i last updated the package, cgal wasn't updated yet. i'll prepere a new debian version going to the proper repository. > tests 168-379 fail - is that something to be concerned about? no. the tests are mixed -- some check the functionality of the openscad language interpretation, serving as regression tests for the basic functionality of openscad itself. others target the visual representation -- that's why some elaborate image comparison is done. these tests require presence of an opengl rendering engine. such could be provided in the build environment by running a virtual x server. most imporantly, though, these tests are there to test whether openscad works on a particular graphics card. on the long term, i'd like to have the tests split on those that require graphics output and those that are just basic tests of the openscad language, as to run only the latter and require all of them to pass -- but for the moment, the current setup provides an easy way to see when things went wrong if they go wrong, and otoh doesn't spend too much time as the test requiring grahics fail quickly. > The changelog has lots of entries in it that says it has been released > to unstable and experimental already, but I can't find it in the > repos. Is this a new package or reviving of an old one? If it is a new > one that has never been in unstable, you should get rid of the > changelog entries saying that it was. You also should close this ITP > bug in the changelog. the packages were previously uploaded only to my own private server archive.amsuess.com's unstable and experimental areas and to an ubuntu ppa, from where they are already used. i remember a recent discussion on mentors@l.d.o, which concluded that some sponsors would like all the old changelog entries marked as UNRELEASED if that version didn't make it, and yet others like it collapsed. if the latter is your preferred way, i'll collapse them to a single short message. > I can sponsor it [...] thank you. i'll prepare an updated package (to section main, with changelog collapsed, standards version updated, and possible new lintian warnings fixed), and notify you when it's ready. signature.asc Description: Digital signature
Bug#668571: arp manpage typo and bad author email
Package: net-tools Version: 1.60-24.1 Forwarded from Launchpad: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/945337 The examples header in the manpage for the arp command is spelled "Exsamples", where it should be "Examples". Also, the first author's e-mail address (Fred N. van Kempen, no longer exists; mail returned, domain name not found). The error for the manpage seems to be in a patch. It changes "EXAMPLES" to "EXSAMPLES", creating the typo. -- Sincerely, kroq-gar78
Bug#654192: Fwd: Bug#654192: [pkg-backupninja] Bug#654192: backupninja rsync handler bugs
Em Mon, Apr 09, 2012 at 02:01:45PM +0200, Paul van Tilburg escreveu: > What it IMO doesn't solve, is the fact that the handler gave a syntax > error and probably returned and error code, but backupninja intepreted > this as "backup succesful". This worries me a bit. I think that the only way to avoid that is to validate the metadata. The following commit tries to do it: https://git.sarava.org/?p=backupninja.git;a=commitdiff;h=e22107cf0954f29215052becf848bc28b47ffbe0 Could you test to see if it works? Thanks again :) -- rhatto at riseup.net pubkey 64E39FCA / keys.indymedia.org signature.asc Description: Digital signature
Bug#668570: override: php-rrd:php/source
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Team, Please, relocate php-rrd package into the 'php' section. Thanks in advance. Regards, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPh2uIAAoJEKgvu4Pz1XAz7L4P/2pNU3xw2mesk5hEEZMvOIPj GpW/KM1YefRfVK+BZVQfwCgG/mYhfvDGN+v3A35Gy/Bpr0Jd6qxKxzvasrF1b6JS biofPLJh/HOE3LEtwBi6ukAeTzNT5xMfMt6g4MYQjZXdJrbmXhCHJQ+ICPZ8IsSm 9pwsMLbxDdeuPxz0AfICtgfXZHvwo1a5Ok3lUKjQMnR7L2nwjuB82K+xsx23c1HF B++OmM45wGrdHI/+3Ul86ni9WMTzahpjfRgVacpd2lG8kUAUCNNuTJhK8ovbh7RD qqNOSAks/kwRMdG/v8P26LPe7Q5cCYKa7IO+OjOI/+HyzmJbvtSQj1O7hsHjUke4 PsuyEBTKuVBHLIvVqYwHlZQrQVJdMiCTevrES0DJvkaluqMihJxeuL+itexf7Pab JkuwXT4gsLm0TgrN+RR18KAgBeLTOWLuIO0OMLHMprTLyDvKkj+bqSzLJAXyerqT rRxRst/t/alHs2Ogx62ciZ3or8Cj5uQzCiyuFOFDFViNN0fIFwgt68d7+t2ovvOe pl9Pq6ri4wj4fp1iIg4VK7pO7mSXSxo6ZkM+6I7k3EiWTE1/bIVHbbg+jvrR8e9Y sSlqG7hnVeymSt7GMK2bRaf8kJ9sI0pxkbHnKZwwWB0Q04TxIChf65CXmr7Vs+4u E09T/DfqCm/0pzPo3Gw8 =mh4b -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#596284: sysvinit: Doesn't install with debootstrap --variant=fakechroot
severity 596284 important tag 596284 patch thanks i took a look at this. the issue is that even though initctl is now in /run, the postinst continues to try to create a symlink for the old initctl in /dev. attached is a patch that detects the situation when there isn't an old initcl and avoids the symlink attempt. see attached. best wishes, mike sysvinit.patch Description: Binary data
Bug#668569: /usr/bin/apt-get: apt-get/aptitude reinstall option is broken
Package: apt Version: 0.8.15.10 Severity: important File: /usr/bin/apt-get Both apt-get --reinstall install ... and aptitutde reinstall ... does NOT reinstall a package, but only configure a package if it is in broken state. That is *REALLY* bad, since if there is a conffile missing and you reinstall with apt-get -o DPkg::Options::="--force-confmiss" --reinstall install ... then I expect apt-get (and aptitude) to: - unpack the actual .deb package, with dpkg --force-confmiss ... - *then* try to configure it If this is not the case, there is NO way one can tell a user easily how to reinstall missing conffiles. An incantation of dpkg always needs the actual path of the .deb file. Furthermore, this is NOT what is documented in apt-get, where it clearly states that the package is *reinstalled* which IMHO does NOT mean that it is first configured. Thanks Norbert -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "true"; APT::Install-Suggests "0"; APT::Cache-Limit "4000"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image.*"; APT::NeverAutoRemove:: "^kfreebsd-image.*"; APT::NeverAutoRemove:: "^linux-restricted-modules.*"; APT::NeverAutoRemove:: "^linux-ubuntu-modules-.*"; APT::NeverAutoRemove:: "^gnumach$"; APT::NeverAutoRemove:: "^gnumach-image.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Periodic ""; APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Update ""; APT::Update::Post-Invoke ""; APT::Update::Post-Invoke:: "touch /var/lib/apt/periodic/update-success-stamp 2>/dev/null || true"; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 1 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Archives ""; APT::Archives::MaxAge "30"; APT::Archives::MinAge "2"; APT::Archives::MaxSize "500"; APT::Architectures ""; APT::Architectures:: "amd64"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::mirrors "mirrors/"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::dpkg "/usr/bin/dpkg"; Dir::Media ""; Dir::Media::MountPath "/media/apt"; Dir::Log "var/log/apt"; Dir::Log::Terminal "term.log"; Dir::Log::History "history.log"; Dir::Ignore-Files-Silently ""; Dir::Ignore-Files-Silently:: "~$"; Dir::Ignore-Files-Silently:: "\.disabled$"; Dir::Ignore-Files-Silently:: "\.bak$"; Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.save$"; Dir::Ignore-Files-Silently:: "\.orig$"; Acquire ""; Acquire::cdrom ""; Acquire::cdrom::mount "/media/cdrom/"; Acquire::Languages ""; Acquire::Languages:: "en"; Acquire::Languages:: "none"; DPkg ""; DPkg::Post-Invoke ""; DPkg::Post-Invoke:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 1 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; DPkg::Post-Invoke:: "if [ -x /usr/bin/debsums ]; then /usr/bin/debsums --generate=nocheck -sp /var/cache/apt/archives; fi"; DPkg::Post-Invoke:: "if [ -d /var/lib/update-notifier ]; then touch /var/lib/update-no
Bug#668568: initramfs-tools: could not open /var/tmp/mkinitramfs_gi1ZmH/lib/modules/3.2.0-rc7-amd64/modules.builtin
Package: initramfs-tools Version: 0.101 Severity: minor After some upgrades (when update-initramfs is run), I get the following warning: Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-rc7-amd64 WARNING: could not open /var/tmp/mkinitramfs_gi1ZmH/lib/modules/3.2.0-rc7-amd64/modules.builtin: No such file or directory It is similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662612 but may be another bug. I wonder which script outputs this warning (IMHO, processes that output a message should include their name in the message). FYI: xvii% locate modules.builtin /lib/modules/3.2.0-1-amd64/modules.builtin /lib/modules/3.2.0-1-amd64/modules.builtin.bin /lib/modules/3.2.0-2-amd64/modules.builtin /lib/modules/3.2.0-2-amd64/modules.builtin.bin xvii% ls /lib/modules 2.6.37-2-amd64 2.6.39-1-amd64 3.0.0-2-amd64 3.2.0-2-amd64 2.6.38-1-amd64 2.6.39-2-amd64 3.1.0-1-amd64 3.2.0-rc7-amd64 2.6.38-2-amd64 3.0.0-1-amd64 3.2.0-1-amd64 -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 11M 2011-03-09 01:21:24 /boot/initrd.img-2.6.37-2-amd64 -rw-r--r-- 1 root root 11M 2011-03-30 02:03:00 /boot/initrd.img-2.6.38-1-amd64 -rw-r--r-- 1 root root 11M 2011-05-20 02:00:15 /boot/initrd.img-2.6.38-2-amd64 -rw-r--r-- 1 root root 11M 2011-05-28 11:36:14 /boot/initrd.img-2.6.39-1-amd64 -rw-r--r-- 1 root root 11M 2011-07-14 00:21:57 /boot/initrd.img-2.6.39-2-amd64 -- /proc/cmdline root=/dev/mapper/xvii-root ro quiet -- resume RESUME=/dev/mapper/xvii-swap_1 -- /proc/filesystems ext3 ext2 fuseblk -- lsmod Module Size Used by usb_storage43870 0 uas13296 0 acpi_cpufreq 12935 1 mperf 12453 1 acpi_cpufreq cpufreq_powersave 12454 0 cpufreq_stats 12866 0 cpufreq_userspace 12576 0 cpufreq_conservative13147 0 xt_multiport 12548 2 iptable_filter 12536 1 ip_tables 22042 1 iptable_filter x_tables 19073 3 ip_tables,iptable_filter,xt_multiport parport_pc 22364 0 ppdev 12763 0 lp 17149 0 parport31858 3 lp,ppdev,parport_pc bnep 17567 2 rfcomm 33656 0 bluetooth 119406 10 rfcomm,bnep crc16 12343 1 bluetooth binfmt_misc12957 1 uinput 17440 1 fuse 61981 1 nfsd 211858 2 nfs 312191 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67328 2 nfs,nfsd sunrpc173671 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd ext2 59231 1 coretemp 12898 0 firewire_sbp2 17993 0 loop 22641 0 snd_hda_codec_idt 53792 1 snd_hda_intel 26345 2 snd_hda_codec 78031 2 snd_hda_intel,snd_hda_codec_idt snd_hwdep 13186 1 snd_hda_codec snd_pcm_oss41081 0 snd_mixer_oss 17916 1 snd_pcm_oss snd_pcm63900 3 snd_pcm_oss,snd_hda_codec,snd_hda_intel snd_page_alloc 13003 2 snd_pcm,snd_hda_intel snd_seq_midi 12848 0 uvcvideo 57744 0 videodev 70889 1 uvcvideo v4l2_compat_ioctl3216655 1 videodev media 18148 2 videodev,uvcvideo snd_seq_midi_event 13316 1 snd_seq_midi snd_rawmidi23060 1 snd_seq_midi snd_seq45093 2 snd_seq_midi_event,snd_seq_midi joydev 17266 0 arc4 12458 2 pcmcia 32691 0 nouveau 545197 2 snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi mxm_wmi12473 1 nouveau ttm48725 1 nouveau yenta_socket 22899 0 dell_wmi 12477 0 sparse_keymap 12760 1 dell_wmi iwlwifi 166657 0 pcmcia_rsrc17533 1 yenta_socket drm_kms_helper 27227 1 nouveau drm 167670 4 drm_kms_helper,ttm,nouveau mac80211 192768 1 iwlwifi snd_timer 22917 2 snd_seq,snd_pcm i2c_algo_bit 12841 1 nouveau snd52850 15 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_idt cfg80211 137140 2 mac80211,iwlwifi iTCO_wdt 17081 0 iTCO_vendor_support12704 1 iTCO_wdt psmouse64455 0 serio_raw 12931 0 pcmcia_core18294 3 pcmcia_rsrc,yenta_socket,pcmcia i2c_i801 16870 0 i2c_core 23876 6 i2c_i801,i2c_algo_bit,drm,drm_kms_helper,nouveau,videodev processor 28059 3 acpi_cpufreq soundcore 13065 1 snd video
Bug#666569: maint-guide: FTBFS: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty:852: I can't find file `t3enc.def'.
Hi Hilmar,
thanks for the example, yes, that is true.
On Do, 12 Apr 2012, Hilmar PreuÃe wrote:
> ifxetex.sty is in texlive-base. The problem goes away if
> \usepackage{xeCJK} or \usepackage[french]{babel} is commented. The
Well, honestly this is a common problem, you ar enot expected to
mix everything with everything. Especially, looking at xeCJK, I see
a lot of things that might create problems, like
\AtBeginDocument{%
\xeCJK@patch\textellipsis {\begingroup\makexeCJKinactive}{\endgroup}
\xeCJK@patch\textemdash {\begingroup\makexeCJKinactive}{\endgroup}
or
\xeCJK@postPunct{25}{00}
\xeCJK@prePunct{30}{08,0A,0C,0E,10,12,14,16,18,1A,1D,1F,36}
that smells like playing around with with these things. Babel also
is known for doing many tricks, so honestly, I am not convinced
that there is a good solution.
> - LaTeX from stable and unstable
> - XeLaTeX from stable
> *not* using XeLaTeX from unstable.
Yes, because in this case xeCJK is not loaded (in the latex case).
SO I assume the change comes from xeCJK.sty.
> I'd vote for contacting (d)ctt to ask for a comment.
I guess yes, that is the best solution, or ask the xeCJK maintainers.
In any case, this is not a packaging issue, so if it is solved, fine,
if not, I can live with it, the failing document has to be
adapted.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
PEVENSEY (n. archaic)
The right to collect shingle from the king's foreshore.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668567: package includes conflicting config.h in /usr/include/srtp
Package: libsrtp0-dev Version: 1.4.4~dfsg-6 The package installs a copy of config.h to /usr/include/srtp This config.h redefines a number of things that are standard across any autotools project, e.g. PACKAGE_NAME If someone is building another package (e.g. resiprocate) that depends on srtp, then the defines in config.h from srtp may clash with those from resiprocate/config.h Sample error: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -DUSE_CARES -Wall -Wno-deprecated -DRESIP_OSTYPE_LINUX -DRESIP_ARCH_X86_64 -DRESIP_LARCH_IA64 -D_REENTRANT -DRESIP_TOOLCHAIN_GNU -MT Flow.lo -MD -MP -MF .deps/Flow.Tpo -c Flow.cxx -fPIC -DPIC -o .libs/Flow.o In file included from ../reTurn/client/TurnAsyncTlsSocket.hxx:3, from Flow.hxx:13, from Flow.cxx:10: ../config.h:69:1: warning: "PACKAGE_NAME" redefined -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668510: tex-common: Installation of tex-common failed. "update-language-dat: cannot read /etc/texmf/hyphen.d/00tex.cnf"
Hi Ronen,
severity 668510 normal
tags 668510 + unreproducible moreinfo
thanks
On Do, 12 Apr 2012, Ronen Abravanel wrote:
>* What led up to the situation?
> Installation,
> "apt-get install tex-common "
What was the state of tex-common *before* installation?
removed or purged?
> AFTER I failed over and over again with normal installation, I tried to
> extract
> the missing file (00tex.cnf) from the .deb file, and copy it to
> /etc/texmf/hyphen.d/00tex.cnf
etc etc.
My wild guess, coming also from what you wrote here:
> Also, I tried to remove any tex-related package, delete /etc/texmf and
> install
> again, and the problam is the same.
Did you *PURGE* the package?
Because if you *purge* the package and then remove the remaining files
manually in /etc/texmf, then a reinstallation will NOT reinstatiate
these files, because it was *your* wish to remove these files.
That is Debian policy.
So my theory is that you just simply shot your system by removing
conffiles that are still maintained by dpkg, instead of purging
the packages.
In case you don't udnerstand the difference between remove and purge,
I recommend one of the many Debian handbooks or quick starters.
Now,how to *SOLVE* your problem:
First I would say:
dpkg -force-confmiss /var/cache/apt/archives/tex-common_3.7_all.deb
after that
apt-get install texlive
that should work.
If that does NOT work, then you have delete MORE conffiles then only
tex-common. In this case the following procedure might show useful:
Search for all package in removed but NOT purged state:
COLUMNS=200 dpkg -l | grep ^rc
then search for packages like tex-common etc
COLUMNS=200 dpkg -l | grep ^rc | grep tex
select the packages that are TeX related (tex-common, any texlive-* etc)
and call
aptitude purge
after that apt-get install texlive
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
SLUGGAN (n.)
A lurid facial bruise which everyone politely omits to mention because
it's obvious that you had a punch-up with your spouse last night - but
which into a door. It is useless to volunteer the true explanation
because nobody will believe it.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635382: [tex-live] new release of latex-unicode
Hi Wolfgang,
thanks for your answer.
On Do, 12 Apr 2012, Wolfgang Jeltsch wrote:
> Norbertâs e-mail made me start with the polishing of the Unicode package
> I had planned to do some time ago. So please donât upload yet. I plan to
Ok, no problem.
> have a version ready for release within the next few days. Iâll also
> have a look at the âhorn issueâ.
Thanks, that is great. If you need any help please let us know!
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
ADRIGOLE (n.)
The centrepiece of a merry-go-round on which the man with the tickets
stands unnervingly still.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#583476: openscad ITP
Thanks for your work, Chrysn - you'd done a lot with this package. I can sponsor it but have some questions: CGAL is in main now, does that mean your package can be also? tests 168-379 fail - is that something to be concerned about? The changelog has lots of entries in it that says it has been released to unstable and experimental already, but I can't find it in the repos. Is this a new package or reviving of an old one? If it is a new one that has never been in unstable, you should get rid of the changelog entries saying that it was. You also should close this ITP bug in the changelog. Thanks again for your work. ~Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668308: xbmc: VDPAU with NVidia card stopped working
Package: xbmc Version: 2:11.0~git20120403.ec33f1f+repack1-5 Followup-For: Bug #668308 notfixed 668308 3:11.0-0.1 thanks On 12/04/12 19:16, Markus Koller wrote: > Looks like this was fixed in the latest update 3:11.0-0.1, thanks! That is not an official Debian package. That package comes from dmo [1] which is known to cause problems with official Debian packages [2]. Thanks, Jon [1] http://debian-multimedia.org/ [2] http://wiki.debian.org/DebianMultimedia/FAQ#There_is_.27Debian_Multimedia_Maintainers.27_and_.27debian-multimedia.org.27._So_what.27s_the_difference.3F -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xbmc depends on: ii fonts-liberation [ttf-liberation] 1.07.2-2 ii mesa-utils 8.0.1-2+b3 ii python 2.7.2-10 ii python-imaging 1.1.7-4 ii python-support 1.0.14 ii ttf-dejavu-core2.33-2 ii ttf-liberation 1.07.2-2 ii x11-utils 7.6+4 ii xbmc-bin 2:11.0~git20120403.ec33f1f+repack1-5 Versions of packages xbmc recommends: ii python-qt3 3.18.1-5 xbmc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664214: Pending fixes for bugs in the libparse-recdescent-perl package
tag 664214 + pending thanks Some bugs in the libparse-recdescent-perl package are closed in revision 51c62fb68064226dc5eab78788043bbd6d155ebd in branch 'master' by Florian Schlichting The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libparse-recdescent-perl.git;a=commitdiff;h=51c62fb Commit message: Added Breaks: on versions of libmail-imapclient-perl and libcss-perl compiled with a backwards-incompatible version of this package (closes: #664214) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668566: ITA: tinyirc -- a tiny IRC client
Package: wnpp Severity: normal Hi, I intend to adopt this package, if that's okay. signature.asc Description: This is a digitally signed message part
Bug#668565: ITP: libgedcom-perl -- interface to genealogy GEDCOM files
Package: wnpp Owner: Nicholas Bamber Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libgedcom-perl Version : 1.16 Upstream Author : Paul Johnson * URL : http://search.cpan.org/dist/Gedcom/ * License : Perl Programming Lang: Perl Description : interface to genealogy GEDCOM files The Gedcom modules provide an interface to read, verify and manipulate Gedcom files. The Gedcom format is the standard format for storing genealogical data such a family trees, a person's birth, marriage, children and death and background research. Package: wnpp Owner: Nicholas Bamber Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libgedcom-perl Version : 1.16 Upstream Author : FIXME * URL : http://search.cpan.org/dist/Gedcom/ * License : FIXME Programming Lang: Perl Description : interface to genealogy GEDCOM files The Gedcom modules provide an interface to read, verify and manipulate Gedcom files. The Gedcom format is the standard format for storing genealogical data such a family trees, a person's birth, marriage, children and death and background research.
Bug#668564: courier-authdaemon: init script needs to set SELinux context for /run/courier
Package: courier-authdaemon Version: 0.63.0-5 Severity: normal Tags: patch On a system using SELinux, /etc/init.d/courier-authdaemon needs to set the file context for the /run/courier directory after creating itl otherwise it ends up with context var_run_t instead of courier_var_run_t. --- debian/courier-authdaemon.init.orig 2012-04-09 00:01:44.074736575 +0100 +++ debian/courier-authdaemon.init 2012-04-09 00:02:23.330738689 +0100 @@ -32,10 +32,12 @@ if [ ! -d "$rundir_courier" ]; then mkdir -m 0775 $rundir_courier chown daemon:daemon $rundir_courier + [ -x /sbin/restorecon ] && /sbin/restorecon $rundir_courier fi if [ ! -d "$rundir" ]; then mkdir -m 0750 $rundir chown daemon:daemon $rundir + [ -x /sbin/restorecon ] && /sbin/restorecon $rundir fi $daemonscript start log_end_msg 0 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.1 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages courier-authdaemon depends on: ii courier-authlib 0.63.0-5 ii lsb-base 4.1+Debian0+fancy0 courier-authdaemon recommends no packages. courier-authdaemon suggests no packages. -- Configuration Files: /etc/courier/authdaemonrc [Errno 13] Permission denied: u'/etc/courier/authdaemonrc' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668554: [git-buildpackage/master] Make the upstream version check match policy
tag 668554 pending thanks Date: Thu Apr 12 23:03:21 2012 +0200 Author: Guido Günther Commit ID: 407dfa157d8fabca4dac89e207b713503d594c1d Commit URL: http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h=407dfa157d8fabca4dac89e207b713503d594c1d Patch URL: http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff_plain;h=407dfa157d8fabca4dac89e207b713503d594c1d Make the upstream version check match policy Closes: #668554 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657027: krb5: FTBFS on hurd-i386
On Mon, 2012-01-23 at 16:00 +0100, Svante Signell wrote: > Package: krb5 > Version: 1.10+dfsg~beta1-2 > Severity: important > Tags: patch > User: debian-h...@lists.debian.org > Usertags: hurd > > Hello, > > The tiny patch inlined below fixes the build of krb5 for GNU/Hurd, by > defining MAXHOSTNAMELEN also in function spnego_mech.c. Hi, this patch has been lingering for some while now, almost three months to be exact. And it is a minor one. It hinders a lot of other packages to build. Is there any problem with the DM status or something else? Thank you for your attention. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668563: ITP: iqr -- large-scale neuronal systems simulator
Package: wnpp Severity: wishlist Owner: Ulysses Bernardet * Package name: iqr Version : 2.4.2 Upstream Author : Ulysses Bernardet * URL : http://iqr.sourceforge.net * License : GPL Programming Lang: C++ Description : large-scale neuronal systems simulator iqr is a simulation software to graphically design and control large-scale neuronal models. Simulations in iqr can control real-world devices in real-time. iqr can be extended by new neuron, and synapse types, and custom interfaces to hardware. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On Thu, 12 Apr 2012 21:53:48 +0200 Olaf van der Spek wrote: > On 12-4-2012 21:40, Michael Tokarev wrote: > > On 12.04.2012 23:33, Olaf van der Spek wrote: > >> On 12-4-2012 21:29, Michael Tokarev wrote: > >>> On 12.04.2012 23:20, Olaf van der Spek wrote: > >>> > > Anyway, I think the current behavour is right. > > Why? > Can't you default to mailing root or just using syslog? > >>> > >>> It _is_ the current situation already - to mail to root. > >> > >> Then it shouldn't be complaining about a missing MAILADDR line, should it? > > > > I don't see why not. If you modified debian-generated > > config file and removed the setting, it will complain, > > exactly as in this bugreport. My point is that when > > the package gets installed, it creates the right config > > file with proper email address, and I said exactly this > > several times already. > > > > I don't really want to change default in the source, this > > adds unnecessary changes from upstream which trivially can > > be, and _are_ already handled in the config file. > > That's understandable, upstream should make that change. ;) Upstream disagrees. If you want mail, put an email address in mdadm.conf. If you don't have an email address there, you don't want email. The simplest way to get rid of the message might be to add --syslog or maybe $DEAMON_OPTIONS to the exec $MDADM --monitor --scan --oneshot line in /etc/cron.daily/mdadm I would accept a patch to the documentation to suggest including --syslog in that example. NeilBrown signature.asc Description: PGP signature
Bug#666569: maint-guide: FTBFS: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty:852: I can't find file `t3enc.def'.
clone 666578 -1 retitle -1 XeLaTeX fails to process some files reassign -1 texlive-xetex stop On 11.04.12 David Prévot (da...@tilapin.org) wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi TeX maintainers, > > Le 03/04/2012 09:29, Osamu Aoki a écrit : > > > This […] still fails to build. If I can > > not fix this soonish, I will build without PDF for problematic locales. > > > > Now EN and ES build OK but not FR. > > We have a similar “Improper discretionary list” issue with the French > Developers Reference, #666578 (once added tipa), and I'm a bit clueless > here, hopefully TeX maintainers may have a hint about this one. > I'm pretty sure this is a regression introduced in TL 2012. Cloning this bug. H. -- Machines that have broken down will work perfectly when the repairman arrives. http://www.hilmar-preusse.de.vu/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664997: Issues with your #664997 bug report
On 12.04.2012 23:38, Olaf van der Spek wrote: > Upstream Apache or upstream PHP? PHP, at Apache the majority probably considers mod_php5 because of its dependency against a forking MPMs some backward oriented technology. > BTW, you skipped my other question. ;) Which one? Note, I do not think Adrian likes us to hijack a bug in his package for a problem which should be addressed at a higher level. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#666569: maint-guide: FTBFS: /usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty:852: I can't find file `t3enc.def'.
On 12.04.12 Norbert Preining (prein...@logic.at) wrote:
> On Mi, 11 Apr 2012, David Prévot wrote:
Hi,
> > We have a similar “Improper discretionary list” issue with the French
> > Developers Reference, #666578 (once added tipa), and I'm a bit clueless
> > here, hopefully TeX maintainers may have a hint about this one.
>
> > > stdin.tex:5739: leading text: .../Bugs/}{http://www.debian.org/\-Bugs/\-}
> > > stdin.tex:5739: Improper discretionary list.
> > > stdin.tex:5739: leading text: .../Bugs/}{http://www.debian.org/\-Bugs/\-}
>
> It would be nice if you could provide a somehow minimal TeX file
> as example. Just drop all the main text and only include
> the discretionary calls. Then remove one usepackage after the other
> and see if the error goes away. If you arrived at something halfway
> decent minimal please send it.
>
I'm pretty sure it is not minimal:
\documentclass{article}
\usepackage{ifthen}
\IfFileExists{ifxetex.sty}{%
\usepackage{ifxetex}%
}{%
\newif\ifxetex
\xetexfalse
}
\ifxetex
\usepackage{xeCJK}
\else
\usepackage[T2A,T2D,T1]{fontenc}
\fi
\usepackage[french]{babel}
\begin{document}
http://www.debian.org/\-doc/\-manuals/\-debian-{}reference/\-
\end{document}
The first condition of that \IfFileExists is always true, as
ifxetex.sty is in texlive-base. The problem goes away if
\usepackage{xeCJK} or \usepackage[french]{babel} is commented. The
file can processed as it is using
- LaTeX from stable and unstable
- XeLaTeX from stable
*not* using XeLaTeX from unstable.
I'd vote for contacting (d)ctt to ask for a comment.
H.
--
Void where prohibited by law.
http://www.hilmar-preusse.de.vu/
signature.asc
Description: Digital signature
Bug#664997: Issues with your #664997 bug report
On Thu, Apr 12, 2012 at 11:36 PM, Arno Töll wrote: > On 12.04.2012 21:06, Olaf van der Spek wrote: >>> It's basically code duplication. What if php6 comes along? >>> What if another php provider is added? >>> >>> With Apache 2.4, isn't FastCGI the recommended way to run PHP? >> >> Arno? > > If you ask me, mod_php5 should burn with fire. Having that said, it is > still the easiest (and as far as I know recommended) way to execute PHP > scripts by upstream. Upstream Apache or upstream PHP? BTW, you skipped my other question. ;) -- Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664997: Issues with your #664997 bug report
On 12.04.2012 21:06, Olaf van der Spek wrote: >> It's basically code duplication. What if php6 comes along? >> What if another php provider is added? >> >> With Apache 2.4, isn't FastCGI the recommended way to run PHP? > > Arno? If you ask me, mod_php5 should burn with fire. Having that said, it is still the easiest (and as far as I know recommended) way to execute PHP scripts by upstream. With PHP FPM rising there is some hope more people are going to use a FCGI driven approach. I do not see this happen anytime soon for the vast majority of users though. As far as Debian is involved, that's something which PHP maintainers might address. As usual: I think we web server maintainer can offer assistance, but in the end, it's up to maintainers to decide what to support. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#615846: snmpd: init script using wrong return code on option "status"
* Ignace Mouzannar [Thu Apr 12, 2012 at 12:11:57PM -0400]: > On Mon, 2011-02-28 at 13:30 +0100, Michael Prokop wrote: > > snmpd's init script uses status_of_proc in the status option code > > but due to lack of pid files (see #611668) this seems to go wrong: > > # /etc/init.d/snmpd status > > snmpd is not running ... failed! > > snmptrapd is not running ... failed! > > # echo $? > > 1 > I am unable to reproduce this on a freshly installed Squeeze, using the > same package version. > > ~# /etc/init.d/snmpd status > snmpd is not running ... failed! > snmptrapd is not running ... failed! > ~# echo $? > 3 > > Using: > > ii snmpd5.4.3~dfsg-2 SNMP > (Simple Network Management Protocol) agents > > Are you still experiencing the same issue? No, I sadly (well, luckily on the other hand) can no longer reproduce this issue on current squeeze installations. Feel free to close the bugreport. regards, -mika- signature.asc Description: Digital signature
Bug#621464: sweethome3d: bug still alive
Package: sweethome3d Version: 2.5+dfsg-1 Severity: normal the gui is drawn on the screen for a second, then sweethome3d crashes with "Segmentation fault" -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sweethome3d depends on: ii java-wrappers 0.1.16 wrappers for java executables ii java3ds-fileloade 1.2+dfsg-1 Java3D 3DS File Loader ii libfreehep-graphi 2.1.1-3FreeHEP Scalable Vector Graphics D ii libitext-java 2.1.7-2Java Library to create and manipul ii libjava3d-java1.5.2+dfsg-5 Java 3D API (java library) ii libsunflow-java 0.07.2.svn396+dfsg-6 rendering system for photo-realist ii openjdk-6-jre 6b18-1.8.13-0+squeeze1 OpenJDK Java runtime, using Hotspo sweethome3d recommends no packages. sweethome3d suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668561: [korganizer] korganizer freezes when activating akonadi-ressource
Package: korganizer Version: 4:4.4.11.1+l10n-1 Severity: normal --- Please enter the report below this line. --- Hello folks, I have multiple calenders as akonadi-ressources. They can be (de-)activated one by one using check boxes. When I activate them, korganizer uses almost all my cpu and is unusable for several minutes. Regards Lorenz --- System information. --- Architecture: i386 Kernel: Linux 3.2.0-2-486 Debian Release: wheezy/sid 800 testing www.debian-multimedia.org 800 testing security.debian.org 800 testing ftp.de.debian.org 750 unstableftp.de.debian.org 250 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+- = kdebase-runtime | 4:4.7.4-2 kdepim-runtime| 4:4.4.11.1-3 libakonadi-contact4(>= 4:4.6) | 4:4.7.4-2+b1 libc6 (>= 2.1.3) | 2.13-27 libkabc4 (>= 4:4.6) | 4:4.7.4-2+b1 libkcal4 (>= 4:4.6) | 4:4.7.4-2+b1 libkcmutils4 (>= 4:4.6) | 4:4.7.4-4 libkde3support4(>= 4:4.6) | 4:4.7.4-4 libkdecore5(>= 4:4.6) | 4:4.7.4-4 libkdepim4 (= 4:4.4.11.1+l10n-1) | 4:4.4.11.1+l10n-1 libkdeui5 (>= 4:4.6) | 4:4.7.4-4 libkholidays4 (>= 4:4.6) | 4:4.7.4-2+b1 libkio5(>= 4:4.6) | 4:4.7.4-4 libkmime4 (>= 4:4.6) | 4:4.7.4-2+b1 libknewstuff2-4(>= 4:4.6) | 4:4.7.4-4 libkontactinterface4 (>= 4:4.6) | 4:4.7.4-2+b1 libkparts4 (>= 4:4.6) | 4:4.7.4-4 libkpimidentities4 (>= 4:4.6) | 4:4.7.4-2+b1 libkpimutils4 (>= 4:4.6) | 4:4.7.4-2+b1 libkprintutils4(>= 4:4.6) | 4:4.7.4-4 libkresources4 (>= 4:4.6) | 4:4.7.4-2+b1 libphonon4 (>= 4:4.6.0really4.3.80) | 4:4.6.0.0-1 libqt4-dbus (>= 4:4.5.3) | 4:4.7.4-2 libqt4-qt3support(>= 4:4.5.3) | 4:4.7.4-2 libqt4-xml (>= 4:4.5.3) | 4:4.7.4-2 libqtcore4 (>= 4:4.7.0~beta2) | 4:4.7.4-2 libqtgui4(>= 4:4.5.3) | 4:4.7.4-2 libstdc++6 (>= 4.1.1) | 4.7.0-1 phonon| 4:4.6.0.0-1 zlib1g (>= 1:1.1.4) | 1:1.2.6.dfsg-2 perl | 5.14.2-9 Package's Recommends field is empty. Suggests (Version) | Installed -+-=== kdepim-kresources| 4:4.4.11.1+l10n-1 kdepim-groupware | 4:4.4.11.1+l10n-1 signature.asc Description: This is a digitally signed message part.
Bug#668560: exuberant-ctags 'etags' should have lower priority than Emacs 'etags'
Package: exuberant-ctags Version: 1:5.9~svn20110310-2 Severity: normal Currently, exuberant-ctags has higher priority than emacs for the 'etags' executable. Since etags stands for 'emacs tags', it seems that it would make more sense for the emacs executable to take priority; if a user desires to use exuberant-ctags they can always use ctags -e. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric') Architecture: i386 (i686) Kernel: Linux 3.0.0-17-generic (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages exuberant-ctags depends on: ii libc6 2.13-20ubuntu5.1 Embedded GNU C Library: Shared lib exuberant-ctags recommends no packages. Versions of packages exuberant-ctags suggests: ii emacs 23.3+1-1ubuntu4The GNU Emacs editor (metapackage) ii emacs 22.2-0ubuntu9 The GNU Emacs editor (with GTK+ 2. ii emacs 23.3+1-1ubuntu4The GNU Emacs editor (with GTK+ us ii vim 2:7.3.154+hg~74503f6ee649-2ubuntu3 Vi IMproved - enhanced vi editor ii vim-g 2:7.3.154+hg~74503f6ee649-2ubuntu3 Vi IMproved - enhanced vi editor - -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512309: debian-sys-maint has insufficient permissions on MySQL 5.0
Well... that's amazing. The "this-is-not-a-bug"-answer for this bug request has been posted within less than a day. After explaining WHY this is should be considered an issue and some confirmations from other people affected by this behaviour it took less than four years to finally get the liberating "is-this-still-an-issue" reply. Thank you, Nicholas. And no, it isn't an issue anymore - it has been fixed in the meantime. Please note that this bug has been reported for Debian Sarge, that's the one we have had once upon a time, long before Lenny and even longer before Squeeze... Regards, Thomas Gelf -- Thomas Gelf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668559: overwrites -> overrides
Package: insserv Version: 1.14.0-3 Severity: minor Hi, I cringe every time insserv gives a report such as this: insserv: warning: current stop runlevel(s) (0 6) of script `alsa-utils' overwrites defaults (0 1 6). Shouldn't the word be "overrides"? Even the Debian patch that tweaks these messages uses "overrides" in the patch description. "overwrites" just seems plain wrong, and it's in a fairly visible place here, output very often when upgrading packages... Sami -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.3.1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages insserv depends on: ii libc6 2.13-27 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 -- debconf information: insserv/enable: true signature.asc Description: Digital signature
Bug#667545: [Pkg-iscsi-maintainers] Bug#667545: Bug#667545: iscsi_trgt: Kernel
Hello, > Am I interpreting correctly that, "On system start-up, since the > encrypted volume wasn't opened, iscsitarget failed to access the files. > Thus failed. Later, after opening the encrypted volume, iscsitarget was > restarted, successfully" ??? At first, iscsitarget starts, but complains that it can't find the files mentioned in /etc/iet/ietd.conf. Thus I gave the following commands: /etc/init.d/iscsitarget stop crsetup mount /dev/mapper/something /mnt/storage3 /etc/init.d/iscsitarget start Further experimentation has shown me the following: - Creating a new empty image (dd if=/dev/zero of=wherever bs=1G count=40), making it available as a iscsitarget never fails to get hooked/booted from (apart from the fact that it is empty). This does not cause the kernel bug. - Booting my (apparently) broken win7 installation image (which broke halfway during installation) causes win7 to bsod and reboot immediately (I haven't been able to tell windows not to do that, since it's not completely installed yet). This somehow leaves the iscsitarget-system in a state where the next attempt to do anything with an exported volume (for example a sanhook-command from ipxe) causes the kernel bug to happen. It doesn't matter if the imagefile itself is stored on an encrypted volume or not. Is there any way I can let the iscsitarget-system log everything it does to file and reproduce the above scenario (tried 4 times, always has the same outcome)? -- Best regards, H. Buurman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667429: zsnes: ftbfs with GCC-4.7
tag 667429 + patch thanks Hello, This patch fixes the problem and will be included in the next upload. Thanks for this bug report. -- Etienne Millon From: Etienne Millon Date: Thu, 12 Apr 2012 18:01:45 +0200 Subject: Fix build with gcc 4.7 Headers in the new C++ library do not implicitly import unistd.h, so it is necessary to do it in the source. Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667429 --- src/tools/depbuild.cpp |1 + 1 file changed, 1 insertion(+) diff --git a/src/tools/depbuild.cpp b/src/tools/depbuild.cpp index 1e4bbc5..ea0854c 100644 --- a/src/tools/depbuild.cpp +++ b/src/tools/depbuild.cpp @@ -25,6 +25,7 @@ This program generates dependencies for all C/C++/Assembly files #include #include #include +#include using namespace std; #include "fileutil.h"
Bug#668558: netcat-openbsd: Segfaults when using -Ulv
Subject: netcat-openbsd: Segfaults when using -Ulv Package: netcat-openbsd Version: 1.105-5 Severity: normal *** Please type your report below this line *** Hi, thanks for taking over maintenance of this package; it was much in need of attention. I think a bug was introduced in 1.105-1 because of this line: fprintf(stderr, "Listening on [%s] (family %d, port %s)\n", host ?: local, family, *uport); which was added to 0008-verbose-numeric-port.patch. The problem is that uport is normally NULL when using Unix domain sockets, so for example: nc -Ulv /tmp/unix.skt segfaults. I suggest not printing any port in the Unix domain socket case. Thanks. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-0.bpo.2-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages netcat-openbsd depends on: ii libbsd0 0.2.0-1utility functions from BSD systems ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib netcat-openbsd recommends no packages. netcat-openbsd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668550: libxs-dev conflicting with libxen-dev
Thomas Goirand wrote: > Since Xen has been around for a long long time, and that libxs is pretty > new in Debian (only few days), I'd say that libxs-dev should be fixed. > Do you agree? yes, i've already brought it up to upstream. hopefully it will be fixed there rather than needing to be patched in individual distributions. http://groups.crossroads.io/groups/crossroads-dev/messages/topic/2PAVRyQVwFozRDYmypdpUN -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667161: FASTX-Toolkit faisl to build with GCC-4.7.
Hello Charles, Charles Plessy wrote, On 04/04/2012 12:17 AM: > > Debian distributes FASTX-Toolkit, and after a mass-rebuild against GCC 4.7, we > noticed the following error: > > ../libfastx/sequence_alignment.h:146:32: error: 'ssize_t' does not name a > type > I can't reproduce it locally (don't have Ubuntu with GCC-4.7 yet), but after reading the porting guide, I'm guessing this error stems from re-organization done in GCC-4.7 which removed "unistd.h" from some header files. I've created a new tarball which explicitly includes "unistd.h" in the relevant CPP files - may I ask you to test it ? http://cancan.cshl.edu/labmembers/gordon/files/fastx_toolkit-0.0.13.2--20120412-1613.tar.bz2 Thanks, -gordon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512309: moreinfo
tag 512309 +moreinfo +unreproducible thanks Is this still an issue in 5.5? I am inclined to close it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664088: mdadm fails to initialize components for bitmap
On 13.04.2012 00:22, Markus Hochholdinger wrote: > Hello Michael, > > Am 12.04.2012 um 21:38 Uhr schrieb Michael Tokarev : >> On 31.03.2012 01:28, Markus Hochholdinger wrote: >>> Package: mdadm >>> Version: 3.2.3-2 >>> Followup-For: Bug #664088 >>> Dear Maintainer, >>> seems I've been stumbled over this bug. I'm running wheezy and can >>> reproduce a crash: mdadm --grow /dev/md0 --bitmap=none >>> mdadm --grow /dev/md0 --bitmap=internal >>> A few seconds after this, the system is still alive, I see the newly >>> created bitmap in /proc/mdstat, and then the system crashes: [ >>> 342.437949] md0: bitmap file is out of date (0 < 322) -- forcing full >>> recovery [ 342.437967] created bitmap (1 pages) for device md0 >>> [ 347.949946] BUG: unable to handle kernel NULL pointer dereference at >>> 0008 [ 347.949969] IP: [] bitmap_endwrite+0x138/0x199 >>> [md_mod] [ 347.949991] *pdpt = 02660007 *pde = >>> [ 347.950010] Oops: [#1] SMP >> Oh. This is a kernel bug, kernel should not crash like this even if >> incorrect bitmap is created. >> Marcus, what's your kernel version? > > Linux 3.2.0-2-686-pae from wheezy. This was obvious from your initial message, but I wasn't clear. I meant to ask what kernel PACKAGE version is that. Sigh, how many times I suggested kernel folks to include debian package version in the kernel OOPs test, but has been ignored every time... :( > Hm, perhaps I could use mdadm from squeeze to check weather the kernel also > crashes. I doubt it is easily reproducible. The original bug in mdadm (which is fixed upstream btw, in git, not any released version) does not initialize bitmap, leaving some garbage in it. Obviously not every garbage triggers the bug in kernel. So if another attempt will not crash your kernel it does not tell anything. I asked for the kernel package version in order to clone and reassign this bugreport to kernel properly. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664088: mdadm fails to initialize components for bitmap
Hello Michael, Am 12.04.2012 um 21:38 Uhr schrieb Michael Tokarev : > On 31.03.2012 01:28, Markus Hochholdinger wrote: > > Package: mdadm > > Version: 3.2.3-2 > > Followup-For: Bug #664088 > > Dear Maintainer, > > seems I've been stumbled over this bug. I'm running wheezy and can > > reproduce a crash: mdadm --grow /dev/md0 --bitmap=none > > mdadm --grow /dev/md0 --bitmap=internal > > A few seconds after this, the system is still alive, I see the newly > > created bitmap in /proc/mdstat, and then the system crashes: [ > > 342.437949] md0: bitmap file is out of date (0 < 322) -- forcing full > > recovery [ 342.437967] created bitmap (1 pages) for device md0 > > [ 347.949946] BUG: unable to handle kernel NULL pointer dereference at > > 0008 [ 347.949969] IP: [] bitmap_endwrite+0x138/0x199 > > [md_mod] [ 347.949991] *pdpt = 02660007 *pde = > > [ 347.950010] Oops: [#1] SMP > Oh. This is a kernel bug, kernel should not crash like this even if > incorrect bitmap is created. > Marcus, what's your kernel version? Linux 3.2.0-2-686-pae from wheezy. Hm, perhaps I could use mdadm from squeeze to check weather the kernel also crashes. -- greetings eMHa signature.asc Description: This is a digitally signed message part.
Bug#668550: libxs-dev conflicting with libxen-dev
Hi, Since Xen has been around for a long long time, and that libxs is pretty new in Debian (only few days), I'd say that libxs-dev should be fixed. Do you agree? Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668557: [PATCH] xfig: Helping to update to packaging format 3.0
Package: xfig
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From a65de0d90e8d6e7244ae212e11404a823d603512 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Thu, 12 Apr 2012 22:42:53 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/README.source | 31
debian/changelog |9 ++
debian/compat |2 +-
debian/control |4 +--
debian/patches/00list | 14 -
...ile_Debian.dpatch => 02-Imakefile-Debian.patch} |8 ++---
.../{03_usr_share.dpatch => 03-usr-share.patch}|9 ++
...4_app-defaults.dpatch => 04-app-defaults.patch} |8 ++---
.../{05_xfig-libs.dpatch => 05-xfig-libs.patch}|8 ++---
...twork_images.dpatch => 12-network-images.patch} |8 ++---
...xtra_libs.dpatch => 13-remove-extra-libs.patch} |8 ++---
...gparserstack.dpatch => 30-figparserstack.patch} | 12 +++-
.../{31_spelling.dpatch => 31-spelling.patch} |8 ++---
...2_papersize_b1.dpatch => 32-papersize-b1.patch} |9 ++
...mediabox.dpatch => 33-pdfimport-mediabox.patch} |8 ++---
...{34_old_shadows.dpatch => 34-old-shadows.patch} | 10 ++-
...CVE-2010-4262.dpatch => 35-CVE-2010-4262.patch} | 12 +++-
.../{36_libpng15.dpatch => 36-libpng15.patch} |8 ++---
...eps-reading.dpatch => 37-fix-eps-reading.patch} |8 ++---
debian/patches/series | 14 +
debian/rules | 27 +
debian/source/format |2 +-
22 files changed, 68 insertions(+), 159 deletions(-)
delete mode 100644 debian/README.source
delete mode 100644 debian/patches/00list
rename debian/patches/{02_Imakefile_Debian.dpatch => 02-Imakefile-Debian.patch} (86%)
rename debian/patches/{03_usr_share.dpatch => 03-usr-share.patch} (77%)
rename debian/patches/{04_app-defaults.dpatch => 04-app-defaults.patch} (82%)
rename debian/patches/{05_xfig-libs.dpatch => 05-xfig-libs.patch} (65%)
rename debian/patches/{12_network_images.dpatch => 12-network-images.patch} (97%)
rename debian/patches/{13_remove_extra_libs.dpatch => 13-remove-extra-libs.patch} (76%)
rename debian/patches/{30_figparserstack.dpatch => 30-figparserstack.patch} (80%)
rename debian/patches/{31_spelling.dpatch => 31-spelling.patch} (75%)
rename debian/patches/{32_papersize_b1.dpatch => 32-papersize-b1.patch} (76%)
rename debian/patches/{33_pdfimport_mediabox.dpatch => 33-pdfimport-mediabox.patch} (80%)
rename debian/patches/{34_old_shadows.dpatch => 34-old-shadows.patch} (69%)
rename debian/patches/{35_CVE-2010-4262.dpatch => 35-CVE-2010-4262.patch} (67%)
rename debian/patches/{36_libpng15.dpatch => 36-libpng15.patch} (91%)
rename debian/patches/{37_fix-eps-reading.dpatch => 37-fix-eps-reading.patch} (87%)
create mode 100644 debian/patches/series
diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 264b9b9..000
--- a/debian/README.source
+++ /dev/null
@@ -1,31 +0,0 @@
-This package uses dpatch to manage all modifications to the upstream
-source. Changes are stored in the source package as diffs in
-debian/patches and applied during the build.
-
-To get the fully patched source after unpacking the source package, cd
-to the root level of the source package and run:
-
-debian/rules patch
-
-Removing a patch is as simple as removing its entry from the
-debian/patches/00list file, and please also remove the patch file
-itself.
-
-Creating a new patch is done with "dpatch-edit-patch patch XX_patchname"
-where you should replace XX with a new number and patchname with a
-descriptive shortname of the patch. You can then simply edit all the
-files your patch wants to edit, and then simply "exit 0" from the shell
-to actually create the patch file.
-
-To tweak an already existing patch, call "dpatch-edit-patch XX_patchname"
-and replace XX_patchname with the actual filename from debian/patches
-you want to use.
-
-To clean up afterwards again, "debian/rules unpatch" will do the
-work for you - or you can of course choose to call
-"fakeroot
Bug#668556: ITP: dparser -- a scannerless GLR parser generator
Package: wnpp Severity: wishlist Owner: Markus Wanner * Package name: dparser Version : 1.26 Upstream Author : John Bradley Plevyak * URL : http://dparser.sourceforge.net/ * License : BSD Programming Lang: C and Python Description : a scannerless GLR parser generator DParser is a scannerless GLR parser generator based on the Tomita algorithm. It is self-hosted and very easy to use. Grammars are written in a natural style of EBNF and regular expressions and support both speculative and final actions. There's an archived RPF for dparser: #248589 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12-4-2012 21:40, Michael Tokarev wrote: On 12.04.2012 23:33, Olaf van der Spek wrote: On 12-4-2012 21:29, Michael Tokarev wrote: On 12.04.2012 23:20, Olaf van der Spek wrote: Anyway, I think the current behavour is right. Why? Can't you default to mailing root or just using syslog? It _is_ the current situation already - to mail to root. Then it shouldn't be complaining about a missing MAILADDR line, should it? I don't see why not. If you modified debian-generated config file and removed the setting, it will complain, exactly as in this bugreport. My point is that when the package gets installed, it creates the right config file with proper email address, and I said exactly this several times already. I don't really want to change default in the source, this adds unnecessary changes from upstream which trivially can be, and _are_ already handled in the config file. That's understandable, upstream should make that change. ;) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#568176: Info received (memtest86+: multiboot image is broken)
tag 568176 patch
thanks
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
diff -ur memtest86+-4.20/head.S memtest86+-4.20-mod/head.S
--- memtest86+-4.20/head.S 2012-04-12 21:42:42.0 +0200
+++ memtest86+-4.20-mod/head.S 2012-04-12 21:45:24.639055516 +0200
@@ -17,7 +17,7 @@
#include "defs.h"
#include "config.h"
#include "test.h"
-#include "multiboot.h"
+#include "multiboot_impl.h"
/*
* References to members of the boot_cpu_data structure.
@@ -78,7 +78,33 @@
/* Move MBI pointer to a safe place */
testl %ecx, %ecx
je 0f
- movl %ecx, mbiptr@GOTOFF(%ebx)
+ movl$1, have_mbi@GOTOFF(%ebx)
+ lealmbi@GOTOFF(%ebx), %edi
+ movl%ecx, %esi
+ mov %ecx, %edx
+ movl0(%esi), %eax
+ movl$(MAX_MBI_SIZE / 4), %ecx
+ rep movsl
+ test$MULTIBOOT_INFO_CMDLINE, %eax
+ jz 1f
+ movl%edx, %esi
+ movl0x10(%esi), %eax
+ movl%eax, %esi
+ lealmbi_cmdline@GOTOFF(%ebx), %edi
+ movl$(MAX_MBI_CMDLINE_SIZE / 4), %ecx
+ rep movsl
+1:
+ movl%edx, %esi
+ movl0(%esi), %eax
+ test$MULTIBOOT_INFO_MEM_MAP, %eax
+ jz 1f
+ movl0x30(%esi), %eax
+ movl%eax, %esi
+ lealmbi_mem@GOTOFF(%ebx), %edi
+ movl$(MAX_MBI_MEMINFO_SIZE / 4), %ecx
+ rep movsl
+1:
+
0:
jmp 0f
@@ -1026,9 +1052,6 @@
movl $1, %eax
ret
-.globl mbiptr
-mbiptr:
- .long 0
realptr:
.word real - RSTART
.word 0x
@@ -1041,6 +1064,19 @@
.word 0, 0# idt base = 0L
.data
+.globl have_mbi
+have_mbi:
+ .long 0
+.globl mbi
+mbi:
+ . = . + MAX_MBI_SIZE
+.globl mbi_mem
+mbi_mem:
+ . = . + MAX_MBI_MEMINFO_SIZE
+.globl mbi_cmdline
+mbi_cmdline:
+ . = . + MAX_MBI_CMDLINE_SIZE
+ .long 0
zerobss: .long 1
clear_display: .long 1
.previous
diff -ur memtest86+-4.20/main.c memtest86+-4.20-mod/main.c
--- memtest86+-4.20/main.c 2012-04-12 21:42:42.0 +0200
+++ memtest86+-4.20-mod/main.c 2012-04-12 21:45:03.863056181 +0200
@@ -11,12 +11,10 @@
#include "test.h"
#include "defs.h"
#include "config.h"
-#include "multiboot.h"
+#include "multiboot_impl.h"
#undef TEST_TIMES
#define DEFTESTS 9
-extern struct multiboot_info *mbiptr;
-
extern void bzero();
const struct tseq tseq[] = {
@@ -154,8 +152,8 @@
if (cmdline_parsed)
return;
- if (mbiptr && (mbiptr->flags & MULTIBOOT_INFO_CMDLINE)) {
- cmdline = (void *) mbiptr->cmdline;
+ if (have_mbi && (mbi.flags & MULTIBOOT_INFO_CMDLINE)) {
+ cmdline = mbi_cmdline;
} else {
if (*OLD_CL_MAGIC_ADDR != OLD_CL_MAGIC)
return;
diff -ur memtest86+-4.20/memtest.lds memtest86+-4.20-mod/memtest.lds
--- memtest86+-4.20/memtest.lds 2011-01-23 19:11:04.0 +0100
+++ memtest86+-4.20-mod/memtest.lds 2012-04-12 21:42:14.887061839 +0200
@@ -3,7 +3,7 @@
ENTRY(_start);
SECTIONS {
- . = 0x5000;
+ . = 0x2000;
_start = . ;
.data : {
*(.data)
diff -ur memtest86+-4.20/multiboot.c memtest86+-4.20-mod/multiboot.c
--- memtest86+-4.20/multiboot.c 2012-04-12 21:42:42.0 +0200
+++ memtest86+-4.20-mod/multiboot.c 2012-04-12 21:42:14.887061839 +0200
@@ -8,31 +8,33 @@
* By Eric Biederman
*/
-#include "multiboot.h"
+#include "multiboot_impl.h"
#include "test.h"
-extern struct multiboot_info *mbiptr;
-
int query_multiboot(void)
{
struct multiboot_mmap_entry *mem;
int i;
- if (!mbiptr) {
+ if (!have_mbi) {
return 0;
}
- if (!mbiptr->mmap_addr) {
+ if (!mbi.mmap_addr) {
return 1;
}
- if ((mbiptr->flags & MULTIBOOT_INFO_MEM_MAP) == 0) {
+ if ((mbi.flags & MULTIBOOT_INFO_MEM_MAP) == 0) {
return 1;
}
- mem = (struct multiboot_mmap_entry *) mbiptr->mmap_addr;
+ mem = mbi_mem;
mem_info.e820_nr = 0;
for (i = 0; i < E820MAX; i++) {
- if ((multiboot_uint32_t) mem >= (mbiptr->mmap_addr + mbiptr->mmap_length)) {
+ if ((char *) mem >= ((char *) mbi_mem + mbi.mmap_length)
+ || (char *) mem + sizeof (mem->size)
+ > ((char *) mbi_mem + MAX_MBI_MEMINFO_SIZE)
+ || (char *) mem + mem->size + sizeof (mem->size)
+ > ((char *) mbi_mem + MAX_MBI_MEMINFO_SIZE)) {
break;
}
--- memtest86+-4.20/multiboot_impl.h 1970-01-01 01:00:00.0 +0100
+++ memtest86+-4.20-mod/multiboot_impl.h 2012-04-12 21:42:14.887061839 +0200
@@ -0,0 +1,15 @@
+#include "multiboot.h"
+
+#define MAX_MBI_SIZE 256
+#define MAX_MBI_MEMINFO_SIZE 1024
+#define MAX_MBI_CMDLINE_SIZE 256
+
+#ifndef ASM_FILE
+
+extern int have_mbi;
+
+extern struct multiboot_info mbi;
+extern char mbi_cmdline[MAX_MBI_SIZE + 1];
+extern struct multiboot_mmap_entry mbi_mem[];
+
+#endif
signature.asc
Description: OpenPGP digital signature
Bug#567441: pidgin does not log on to accounts automatically when starting
Hello, when I installed pidgin 2.7.3, it was working. I was using NetworkManager to manage my wlan0. now I have switched to static address within my home network, I am no more using Network manager. and pidgin has the same behaviour as described in message #5. Unfortunately I cannot go back to test with NetworkManager, I have it still installed, but my nm-applet is not finding any connections at the moment. This is to say, maybe is this bug linked to NetworkManager or its absence. Johnny B. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12.04.2012 23:33, Olaf van der Spek wrote: > On 12-4-2012 21:29, Michael Tokarev wrote: >> On 12.04.2012 23:20, Olaf van der Spek wrote: >> Anyway, I think the current behavour is right. >>> >>> Why? >>> Can't you default to mailing root or just using syslog? >> >> It _is_ the current situation already - to mail to root. > > Then it shouldn't be complaining about a missing MAILADDR line, should it? I don't see why not. If you modified debian-generated config file and removed the setting, it will complain, exactly as in this bugreport. My point is that when the package gets installed, it creates the right config file with proper email address, and I said exactly this several times already. I don't really want to change default in the source, this adds unnecessary changes from upstream which trivially can be, and _are_ already handled in the config file. What I don't understand? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12-4-2012 20:59, Michael Tokarev wrote: Can't you default to mailing root or just using syslog? How did you generate /etc/mdadm/mdadm.conf ? The mdadm postinst script creates this file which includes MAILADDR statement, and the question about mail address is asked using debconf. I don't know, it's a dedicated server from http://www.hetzner.de/en/ Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668555: [PATCH] igerman98: Helping to update to packaging format 3.0
Package: igerman98
Severity: wishlist
Tags: patch
Hi,
The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:
http://wiki.debian.org/Projects/DebSrc3.0
I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.
Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.
Thanks,
Jari
>From 9958a125162f5e93187a2d44f0f10aa064e0c5c6 Mon Sep 17 00:00:00 2001
From: Jari Aalto
Date: Thu, 12 Apr 2012 22:06:17 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Signed-off-by: Jari Aalto
---
debian/README.source | 31
debian/changelog |9 ++
debian/compat |2 +-
debian/control |4 +--
debian/patches/00list |4 ---
.../{01_compeng.dpatch => 01-compeng.patch}| 10 ++-
...HTML-entities.dpatch => 03-HTML-entities.patch} |8 ++---
.../{12_fix_clean.dpatch => 12-fix-clean.patch}| 10 ++-
.../patches/{18_aspell.dpatch => 18-aspell.patch} |8 ++---
debian/patches/series |4 +++
debian/rules | 24 ---
debian/source/format |2 +-
12 files changed, 33 insertions(+), 83 deletions(-)
delete mode 100644 debian/README.source
delete mode 100644 debian/patches/00list
rename debian/patches/{01_compeng.dpatch => 01-compeng.patch} (94%)
rename debian/patches/{03_HTML-entities.dpatch => 03-HTML-entities.patch} (80%)
rename debian/patches/{12_fix_clean.dpatch => 12-fix-clean.patch} (58%)
rename debian/patches/{18_aspell.dpatch => 18-aspell.patch} (90%)
create mode 100644 debian/patches/series
diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 264b9b9..000
--- a/debian/README.source
+++ /dev/null
@@ -1,31 +0,0 @@
-This package uses dpatch to manage all modifications to the upstream
-source. Changes are stored in the source package as diffs in
-debian/patches and applied during the build.
-
-To get the fully patched source after unpacking the source package, cd
-to the root level of the source package and run:
-
-debian/rules patch
-
-Removing a patch is as simple as removing its entry from the
-debian/patches/00list file, and please also remove the patch file
-itself.
-
-Creating a new patch is done with "dpatch-edit-patch patch XX_patchname"
-where you should replace XX with a new number and patchname with a
-descriptive shortname of the patch. You can then simply edit all the
-files your patch wants to edit, and then simply "exit 0" from the shell
-to actually create the patch file.
-
-To tweak an already existing patch, call "dpatch-edit-patch XX_patchname"
-and replace XX_patchname with the actual filename from debian/patches
-you want to use.
-
-To clean up afterwards again, "debian/rules unpatch" will do the
-work for you - or you can of course choose to call
-"fakeroot debian/rules clean" all together.
-
-
-original text by Gerfried Fuchs, edited by Junichi Uekawa
-10 Aug 2008.
diff --git a/debian/changelog b/debian/changelog
index a3681d9..d7b126f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+igerman98 (20110609-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+ * Update to Standards-Version to 3.9.3 and debhelper to 9.
+ * Add build-arch and build-indep targets to rules file.
+
+ -- Jari Aalto Thu, 12 Apr 2012 22:06:07 +0300
+
igerman98 (20110609-1) unstable; urgency=low
* New upstream version 20110609.
diff --git a/debian/compat b/debian/compat
index 7ed6ff8..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-5
+9
diff --git a/debian/control b/debian/control
index aa23cb3..ed3d1bf 100644
--- a/debian/control
+++ b/debian/control
@@ -3,10 +3,10 @@ Section: text
Priority: optional
Maintainer: Roland Rosenfeld
Uploaders: Rene Engelhard
-Standards-Version: 3.9.2
+Standards-Version: 3.9.3
Build-Depends-Indep: ispell (>= 3.1.20-12.1), hunspell, aspell (>= 0.60.5-2),
dictionaries-common-dev (>= 1.10.5)
-Build-Depends: debhelper (>= 5.0.0), dpatch
+Build-Depends: debhelper (>= 9)
Homepage: http://j3e.de/ispell/igerman98/
Package: ingerman
diff --git a/debian/patches/00list b/debian/patches/00list
deleted file mode 100644
index 05908e6..000
--- a/debian/patches/00list
+++ /dev/null
@@ -1,4
Bug#664088: mdadm fails to initialize components for bitmap
On 31.03.2012 01:28, Markus Hochholdinger wrote: > Package: mdadm > Version: 3.2.3-2 > Followup-For: Bug #664088 > > Dear Maintainer, > > seems I've been stumbled over this bug. I'm running wheezy and can reproduce > a crash: > mdadm --grow /dev/md0 --bitmap=none > mdadm --grow /dev/md0 --bitmap=internal > > A few seconds after this, the system is still alive, I see the newly created > bitmap in /proc/mdstat, and then the system crashes: > [ 342.437949] md0: bitmap file is out of date (0 < 322) -- forcing full > recovery > [ 342.437967] created bitmap (1 pages) for device md0 > [ 347.949946] BUG: unable to handle kernel NULL pointer dereference at > 0008 > [ 347.949969] IP: [] bitmap_endwrite+0x138/0x199 [md_mod] > [ 347.949991] *pdpt = 02660007 *pde = > [ 347.950010] Oops: [#1] SMP Oh. This is a kernel bug, kernel should not crash like this even if incorrect bitmap is created. Marcus, what's your kernel version? Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12-4-2012 21:29, Michael Tokarev wrote: On 12.04.2012 23:20, Olaf van der Spek wrote: Anyway, I think the current behavour is right. Why? Can't you default to mailing root or just using syslog? It _is_ the current situation already - to mail to root. Then it shouldn't be complaining about a missing MAILADDR line, should it? Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658701: mdadm: should send email if mismatches are reported by a check
Neil, re http://bugs.debian.org/658701 , how do you think, is it okay if mdadm --monitor will send email in case check found mismatches, the same way it sends email about other more critical errors? I think Russell has a good point here, but there's one more source of mismatches we have in kernel - some "sporadic" mismatches in raid1 and raid10, especially when these are used as swap space... In Debian we've several bugreports already requesting more attention to mismatch_cnt, see: http://bugs.debian.org/658701 (this one) http://bugs.debian.org/599821 http://bugs.debian.org/588516 Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12.04.2012 23:20, Olaf van der Spek wrote: >> Anyway, I think the current behavour is right. > > Why? > Can't you default to mailing root or just using syslog? It _is_ the current situation already - to mail to root. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12-4-2012 21:19, Michael Tokarev wrote: On 12.04.2012 23:02, Olaf van der Spek wrote: On 12-4-2012 20:59, Michael Tokarev wrote: Can't you default to mailing root or just using syslog? How did you generate /etc/mdadm/mdadm.conf ? The mdadm postinst script creates this file which includes MAILADDR statement, and the question about mail address is asked using debconf. I don't know, it's a dedicated server from http://www.hetzner.de/en/ Well, this does not help much. Anyway, I think the current behavour is right. Why? Can't you default to mailing root or just using syslog? Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
On 12.04.2012 23:02, Olaf van der Spek wrote: > On 12-4-2012 20:59, Michael Tokarev wrote: >>> Can't you default to mailing root or just using syslog? >> >> How did you generate /etc/mdadm/mdadm.conf ? The mdadm >> postinst script creates this file which includes MAILADDR >> statement, and the question about mail address is asked >> using debconf. > > I don't know, it's a dedicated server from http://www.hetzner.de/en/ Well, this does not help much. Anyway, I think the current behavour is right. Mdadm package installation procedure ensures that some email address gets configured in mdadm.conf (there's a debconf question about it and the address defaults to root). It is possible to remove the configuration item, but that's entirely up to the user ofcourse. Do you agree it's okay to close this bug? Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667635: Correctly marking bad versions
found 667635 8:6.7.4.0-3 found 667635 8:6.6.9.7-7 thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668480: [PATCH] yamdi: Helping to update to packaging format 3.0
Feel free to NMU Jari- thanks very much!
-Todd
On Thu, Apr 12, 2012 at 10:08:50AM +0300, jari.aa...@cante.net wrote:
> Package: yamdi
> Severity: wishlist
> Tags: patch
>
> Hi,
>
> The dpatch patch management system has been deprecated for some time. The
> Lintian currently flags use of dpatch packages as an error. The new 3.0
> packaging format is an improved version which, among other things, contains
> patch management built-in. For more information, see:
>
> http://wiki.debian.org/Projects/DebSrc3.0
>
> I had some free time; see attached patch to migrate to new package
> format. Note that all files in debian/patches/* are canocalized to
> *.patch.
>
> Notes:
>
> In-line changes to original sources were moved to debian/patches
> due to new package format requirements.
>
> Let me know if there is anything that needs adjusting or if it is ok
> to upload this version in a NMU in case you are working on other
> issues needing attention.
>
> Thanks,
> Jari
>
> From e53d552f0fb54f5ea07c15a6dc17a93374f3f4a7 Mon Sep 17 00:00:00 2001
> From: Jari Aalto
> Date: Thu, 12 Apr 2012 10:05:18 +0300
> Subject: [PATCH] format-3.0
> Organization: Private
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: 8bit
>
> Signed-off-by: Jari Aalto
> ---
> Makefile |2 +-
> debian/changelog | 15 +++
> debian/compat |2 +-
> debian/control |8 +++---
> debian/copyright |7 ++---
> debian/patches/00list |1 -
> ..._height_fix.dpatch => 20-zero-height-fix.patch} |7 ++---
> debian/patches/series |2 ++
> debian/rules | 28
> +++-
> debian/source/format |1 +
> 10 files changed, 39 insertions(+), 34 deletions(-)
> delete mode 100644 debian/patches/00list
> rename debian/patches/{01_zero_height_fix.dpatch =>
> 20-zero-height-fix.patch} (78%)
> create mode 100644 debian/patches/series
> create mode 100644 debian/source/format
>
> diff --git a/Makefile b/Makefile
> index ccf7080..cad74ea 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,7 +1,7 @@
> # Makefile for yamdi
>
> CC=gcc
> -CFLAGS=-O2 -Wall -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat
> -Wformat-security -Wl,-z,relro
> +CFLAGS=-O2 -Wall
>
> yamdi: yamdi.c
> $(CC) $(CFLAGS) yamdi.c -o yamdi
> diff --git a/debian/changelog b/debian/changelog
> index d9538b9..00a5f0b 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,18 @@
> +yamdi (1.4-2.1) unstable; urgency=low
> +
> + * Non-maintainer upload.
> + * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
> + * Update to Standards-Version to 3.9.3, debhelper to 9, ${misc:Depends}.
> + * Delete header XS-Vcs-Hg from control; domain and URL no longer exists.
> + * Add build-arch and build-indep targets; use dh_prep in rules file.
> + * Convert in-line patches to individual debian/patches (patch 10).
> + * Fix copyright-with-old-dh-make-debian-copyright (Lintian).
> + * Fix description-synopsis-starts-with-article (Lintian).
> + * Fix no-homepage-field (Lintian).
> + * Fix description-synopsis-starts-with-article (Lintian).
> +
> + -- Jari Aalto Thu, 12 Apr 2012 10:02:09 +0300
> +
> yamdi (1.4-2) unstable; urgency=low
>
>* Add dpatch to Build-Depends
> diff --git a/debian/compat b/debian/compat
> index 7ed6ff8..ec63514 100644
> --- a/debian/compat
> +++ b/debian/compat
> @@ -1 +1 @@
> -5
> +9
> diff --git a/debian/control b/debian/control
> index c05bf0d..6d65928 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -2,14 +2,14 @@ Source: yamdi
> Section: utils
> Priority: extra
> Maintainer: Todd Troxell
> -Build-Depends: debhelper (>= 5), dpatch
> -Standards-Version: 3.7.2
> -XS-Vcs-Hg: http://code.rapidpacket.com/yamdi/
> +Build-Depends: debhelper (>= 9)
> +Standards-Version: 3.9.3
> +Homepage: http://freecode.com/projects/yamdi
>
> Package: yamdi
> Architecture: any
> Depends: ${shlibs:Depends}, ${misc:Depends}
> -Description: a utility for adding metadata to flash video files
> +Description: utility for adding metadata to flash video files
> yamdi is a fast console application for adding various metadata to flv
> files.
> The program buffers its input file, rather than loading into memory in its
> entirety.
> diff --git a/debian/copyright b/debian/copyright
> index c1b6d5e..d5eede2 100644
> --- a/debian/copyright
> +++ b/debian/copyright
> @@ -9,7 +9,7 @@ Upstream Author:
>
> Copyright:
>
> -Copyright (c) 2007, Ingo Oppermann
> +Copyright (C) 2007 Ingo Oppermann
>
> License:
>
> @@ -39,5 +39,6 @@ License:
> * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
> * POSSIBILITY OF S
Bug#668554: git-import-orig: please allow upper case letters in upstream version strings
Package: git-buildpackage Version: 0.5.32 Severity: normal File: /usr/bin/git-import-orig Hi, I've been trying to import a new upstream tarball of pcsc-cyberjack, which carries the version number 3.99.5final.SP03'. Unfortunately, git-import-orig refuses this version string with this error message: gbp:warn: Not a valid upstream version: '3.99.5final.SP03'. Upstream version numbers must start with a digit and can only containg lower case letters (a-z), digits (0-9), full stops (.), plus signs (+), minus signs (-), colons (:) and tildes (~) I worked around it by avoid upper-case letters for now. However, this is suboptimal, since a) upstream does use upper-case letters here and b) Policy §5.6.12 [1] does explicitly allow upper case letters in the upstream version, see footnote 36: http://www.debian.org/doc/debian-policy/footnotes.html#f36 [1 ]http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version Please relax this upstream version check. Cheers, Reinhard -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise-proposed'), (500, 'precise') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-23-generic (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-buildpackage depends on: ii devscripts 2.11.6ubuntu1 ii git [git-core] 1:1.7.9.5-1 ii python 2.7.2-9ubuntu6 ii python-dateutil 1.5-1 ii python2.72.7.3-0ubuntu1 Versions of packages git-buildpackage recommends: ii cowbuilder0.67 ii pristine-tar 1.20 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-3 ii unzip 6.0-4ubuntu1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664997: Issues with your #664997 bug report
On Mon, Mar 26, 2012 at 7:54 PM, Olaf van der Spek wrote: > On Mon, Mar 26, 2012 at 1:54 AM, Arno Töll wrote: >> So, as a start, web applications should recommend a web server like >> this if they ship both, an Apache2 configuration file and a Lighttpd >> configuration file: >> >> Recommends: apache2 | lighttpd | httpd > > What's the advantage over apache2 | httpd or just httpd? > >> Of course, that's not enough to run for a PHP application. I was >> outlining lots of ways to execute PHP scripts on a web server. I do >> not see what's so bad to depend on libapache2-mod-php5 or whatever PHP >> maintainers provide these days. > > It's basically code duplication. What if php6 comes along? > What if another php provider is added? > > With Apache 2.4, isn't FastCGI the recommended way to run PHP? Arno? -- Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#568176: memtest86+: multiboot image is broken
Package: memtest86+ Version: 4.20-1.1 Followup-For: Bug #568176 The problem comes from memtest not declaring its BSS in multiboot image. So the booloader supposes that these area can be used to pass parameters and then memtest overwrites this info. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.42 memtest86+ recommends no packages. Versions of packages memtest86+ suggests: ii grub-pc 1.99-21 ii hwtools ii kernel-patch-badram ii memtest864.0a-0.1 ii memtester ii mtools 4.0.12-1 -- debconf information: shared/memtest86-run-lilo: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668035: mdadm: Default to mailing root
tags 668035 + moreinfo thanks On 08.04.2012 16:54, Olaf van der Spek wrote: > Package: mdadm > Version: 3.1.4-1+8efb9d1+squeeze1 > Severity: wishlist > > Hi, > > Just got this mail: > /etc/cron.daily/mdadm: > mdadm: No mail address or alert command - not monitoring. > run-parts: /etc/cron.daily/mdadm exited with return code 1 > > Can't you default to mailing root or just using syslog? How did you generate /etc/mdadm/mdadm.conf ? The mdadm postinst script creates this file which includes MAILADDR statement, and the question about mail address is asked using debconf. Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668548: git-buildpackage: patch
tags 668548 +patch thanks Attached is a patch that fixes the manpage. Regards, Jö. -- Jorrit (Jö) Fahlke, Interdisciplinary Center for Scientific Computing, Heidelberg University, Im Neuenheimer Feld 368, D-69120 Heidelberg Tel: +49 6221 54 8890 Fax: +49 6221 54 8884 Der Horizont vieler Menschen ist ein Kreis mit Radius Null - und das nennen sie ihren Standpunkt. -- A. Einstein From 26a937d6d27edce0b753c8bd6bd3555129882031 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6=20Fahlke?= Date: Thu, 12 Apr 2012 19:19:33 +0200 Subject: [PATCH] Cite the default value for the --git-builder command line option correctly in the manpage. This should fix Bug#668548. --- docs/manpages/git-buildpackage.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manpages/git-buildpackage.sgml b/docs/manpages/git-buildpackage.sgml index e884d81..7b06b85 100644 --- a/docs/manpages/git-buildpackage.sgml +++ b/docs/manpages/git-buildpackage.sgml @@ -122,7 +122,7 @@ --git-builder=BUILD_CMD - Use BUILD_CMD instead of debuild -i\.git -I.git + Use BUILD_CMD instead of debuild -i -I -- 1.7.9.5 signature.asc Description: Digital signature
Bug#668034: mdadm: Typo in 4b. Can a 4-disk RAID10 survive two disk failures?
tags 668034 + squeeze thanks On 08.04.2012 16:42, Olaf van der Spek wrote: > Package: mdadm > Version: 3.1.4-1+8efb9d1+squeeze1 > Severity: wishlist > > Hi, > > FAQ.gz: > In two thirds of the cases, yes[0], and it does not matter which layout you > use. When you assemble 4 disks into a RAID10, you essentially stripe a RAID0 > across two RAID1, so the four disks A,B,C,D become two pairs: A,B and C,D. > If A fails, the RAID6 can only survive if the second failing disk is either > C or D; If B fails, your array is dead. > > RAID6 should be RAID10 in the second to last line. This has been fixed for wheezy, see #637068. /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661538: support for Build-Depends-Stage1 in order to allow breaking of cyclic Build-depends loops
tags 661538 - patch quit Gustavo Prado Alkmim wrote: > Patch updated to work on dpkg-1.16.2. Same comments as before apply. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649518: haskell-dpkg: FTBFS against latest libdpkg-dev
Source: haskell-dpkg Version: 0.0.1-2 Followup-For: Bug #649518 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Clint, this bug by now affects also Debian (and was confusing because https://buildd.debian.org/status/package.php?p=haskell-dpkg only lists s390 as failing, probably because multi-arch dpkg was installed there first) and holds up the transition. Can you release a fixed version of haskell-dpkg, with a correctly versioned build-depends on dpkg? Thanks, Joachim - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk+HIuEACgkQ9ijrk0dDIGzdIACeJacYLeOvU77BzY9Tn2VqEFmU Tk0AnR4lToPevbbP8j3hC2WOA83s+taj =d75F -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
