Bug#778422: [moodle-packaging] Bug#778422: moodle: PHP fatal error while using forum activity
Hi Oscar, Thanks for reporting and investigating. This bug is fixed in yesterdays' upload. Bye, Joost Op Sat, Feb 14, 2015 at 03:04:59PM -0500 schreef Oscar Diaz: Package: moodle Version: 2.7.5+dfsg-2 Severity: important Tags: newcomer Dear Maintainer, When you add a forum activity and try to see a forum post, a HTTP 500 error is returned. PHP log reports: PHP Fatal error: Class 'core_availability\info_module' not found in /usr/share/moodle/mod/forum/lib.php on line 5571 I found the fix from the original sources: the directory /availability is missing from the installed deb package. Once you put this directory under /usr/share/moodle, go to Administration Site administration Notifications to configure the missing directory, and then the forums start working. I guess this is a packaging issue: I checked the downloaded deb package, and also tried to build from source. Both times the same directory is missing. I hope this helps you to fix this bug. Best regards. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages moodle depends on: pn apache2 | httpdnone pn dbconfig-commonnone ii debconf [debconf-2.0] 1.5.55 pn libapache2-mod-php5 | php5-cgi none pn libphp-adodb none pn libphp-pclzip none pn libphp-phpmailer none pn php-htmlpurifier none pn php5-cli none pn php5-curl none pn php5-gdnone pn php5-mysql | php5-pgsqlnone ii postgresql-client 9.4+165 ii postgresql-client-9.4 [postgresql-client] 9.4.0-1 ii ucf3.0030 Versions of packages moodle recommends: ii aspell0.60.7~20110707-1.3 pn mimetex none pn php5-ldap none pn php5-xmlrpc none pn postgresql | mysql-server | virtual-mysql-server none Versions of packages moodle suggests: pn clamav none ___ Pkg-moodle-maintainers mailing list pkg-moodle-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-moodle-maintainers -- Joost van Baal-Ilić joos...@uvt.nl irc://irc.uvt.nl/joostvb http://abramowitz.uvt.nl/(013-466-)3519 do afwezig kamer G 236 LIS Unix https://doc.uvt.nl/its-id/its-unix-sm/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780716: flightgear-data: nasal scripts can ready any file
Package: flightgear-data Version: 3.0.0-1 Severity: grave Tags: security Upstream has reported two related security issues in how FlightGear restricts what files Nasal (its built-in scripting language for aircraft) can access. This bug is tracking the portion related to the flightgear-data package. -The allowed directories for reading include FG_SCENERY, which can be changed from Nasal via /sim/terrasync/scenery-dir. Effect: Can read any file as the user. Fix: fgdata 60da2094252cee1a5cdfe737f29becd5c6800549 Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Bug#780714: [PATCH] Atomix game is 9 years old in Debian and depends on deprecated bonobo and libgnome2 technologies - please upload new upstream GTK3 version
On 18.03.2015 10:29, UAB „Bonamens“ wrote: [...] Please upload latest upstream Atomix GTK3 version - 3.15.92, which works fine with GTK+ 3.14 from Debian testing/unstable Hello, I am aware of the new release and will take care of uploading it as soon as Debian is no longer frozen. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#780714: [PATCH] Atomix game is 9 years old in Debian and depends on deprecated bonobo and libgnome2 technologies - please upload new upstream GTK3 version
On 18.03.2015 11:16, UAB „Bonamens“ wrote: Hi Markus, Could you upload new Atomix GTK3 (ver. 3.15.92) packages into Debian experimental? Then Debian users can test new Atomix and don't be forced to install lots of bonobo 2.x and gnome 2.x packages. Hi, honestly I think it is not that urgent. Atomix is only a small game and there are other applications that still use GTK-2 libraries too. There is nothing ground-breaking going on with the GTK-3 port which would require extensive testing. By the way 3.15.92 is only a pre-release and new stable releases will most likely coincide with major GNOME 3 updates. So I expect the next version will be 3.16.0. Expect an upload of Atomix after the freeze. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#780521: nautilus: Impossible to rename files and directories
On 18/03/15 11:05, Eerste Laatste wrote: Thanks for the key-combination tips, as i did not know them. But i assume you realize that the majority of users don't know them and/or won't be able to remember them either. Yes, and that's why I didn't close the bug, only retitled it. Impossible to rename files would be a very serious bug for a file manager; renaming files is harder than it ought to be is less serious, but still a bug. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780711: nspawn: getty restart loop
Package: systemd Version: 215-12 Severity: normal Tags: patch Dear Maintainer, When launching a container using systemd-nspawn, getty restarts every 10 seconds[1] after first login and when nobody is logged in. The following patch fixes the problem. It has been integrated upstream[2]. [1] http://lists.freedesktop.org/archives/systemd-devel/2014-December/026075.html [2] http://cgit.freedesktop.org/systemd/systemd/commit/?id=68ac53e62fadb87f1b33ccd9bff9c3f7f699c937 Thanks, Alex diff -Nru systemd-215.old/units/container-ge...@.service.m4.in systemd-215/units/container-ge...@.service.m4.in --- systemd-215.old/units/container-ge...@.service.m4.in2013-12-18 18:21:28.159729831 +0100 +++ systemd-215/units/container-ge...@.service.m4.in2015-03-18 09:20:45.017971507 +0100 @@ -14,6 +14,7 @@ )m4_dnl Before=getty.target IgnoreOnIsolate=yes +ConditionPathExists=/dev/pts/%I [Service] ExecStart=-/sbin/agetty --noclear --keep-baud pts/%I 115200,38400,9600 $TERM -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-7 ii libcap2-bin 1:2.24-7 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.2-4+b1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-12 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev215-12 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 215-12 Versions of packages systemd suggests: pn systemd-ui none -- 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#726530: Bug#780401: (gimp: crashes window manager (fvwm) on closing)
Thank you for your reply! Vincent W. Chen (2015-03-18T02:02:44+0100): On Mon, Mar 16, 2015 at 2:03 AM, Olaf Dietrich olaf.dietr...@med.uni-muenchen.de wrote: I think I can trigger the crash reproducibly in my setup: [] I am unable to reproduce this on my end, following the instructions you've given. It seems to be 100% reproducible here; so, if you have any suggestions, I should be able to do some more testing to find out what's going wrong. Probably not related are some persistent fvwm charset problems: [fvwm][convert_charsets]: WARNING - Invalid byte sequence during conversion from UTF-8 to ISO-8859-1 What language are you running Fvwm under (check by running 'locale')? $ locale LANG= LANGUAGE=en_US:en LC_CTYPE=POSIX LC_NUMERIC=POSIX LC_TIME=POSIX LC_COLLATE=POSIX LC_MONETARY=POSIX LC_MESSAGES=POSIX LC_PAPER=POSIX LC_NAME=POSIX LC_ADDRESS=POSIX LC_TELEPHONE=POSIX LC_MEASUREMENT=POSIX LC_IDENTIFICATION=POSIX LC_ALL= Some programs are started with modified environment variables (and I haven't tested recently which of these are really still necessary to get the desired behavior): LC_CTYPE=en_US.utf8 uxterm LANG=en_US.utf8 exec uxterm -e mutt LANG=en_US LC_PAPER=de_DE iceweasel LANG=en_US exec xterm -e octave LANG=de_DE.utf8 soffice LANG=en_US LC_PAPER=de_DE xpdf Do you have any UTF-8 locales on your system (check by running 'locale -a')? $ locale -a C C.UTF-8 POSIX de_DE de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 de_DE@euro deutsch en_US en_US.iso88591 en_US.iso885915 en_US.utf8 german As mentioned before (but not necessarily related), fvwm does not display handles for several dialog windows, e.g., in gimp (File Open) or xpdf. [...] Therefore try putting the following in your config file: Style * DecorateTransient Thanks - that's solving this issue! Olaf Some more config data Package: fvwm Version: 1:2.6.5.ds-3 .fvwm/config: EdgeResistance 400 Style * EdgeMoveDelay 400 Style * EdgeResizeDelay 400 Style * EdgeMoveResistance 200 100 Style * DecorateTransient OpaqueMoveSize 60 WindowFont Xft:Arial:style=Regular:size=10:encoding=utf8 DefaultFont Xft:Arial:style=Semibold:size=9:encoding=utf8 DeskTopSize 8x2 *FvwmPagerGeometry 1200x92+0-0@0 *FvwmPagerFont none *FvwmPagerSmallFont -*-*-*-r-*-*-8-*-*-*-*-*-iso10646-* *RightFvwmPagerGeometry 1200x92+0-0@1 *RightFvwmPagerFont none *RightFvwmPagerSmallFont -*-*-*-r-*-*-8-*-*-*-*-*-iso10646-* Style FvwmPager StaysPut, Sticky, NoTitle, WindowListSkip, Handles Module FvwmPager 0 0 Module FvwmPager RightFvwmPager 0 0 *FvwmBacker: Command (Desk *, Page 0 *) -solid #303030 Module FvwmBacker Style * SloppyFocus Style * MWMBorder, HandleWidth 5 Style xclock NoTitle, Sticky, WindowListSkip Style xloadNoTitle, Sticky, WindowListSkip -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780718: return in ?:-operator with function calls is incorrectly optimized
Package: g++
Version: 4:4.7.2-1
Severity: normal
Hi,
while testing apt with gcc-5 suite I noticed that while it compiles just
fine, the resulting binaries produce incorrect results failing our
integration tests (which aren't run at package buildtime, so this wasn't
detected in the gcc-5 mass-rebuild).
While trying to come up with a smaller testcase I noticed¹ that with
a slight variation even the g++-4.x series² emits the same strange
results… clang on the other hand produces the expected results, neither
of them generates any warnings about the code.
Attached is as far as I got in terms of a testcase. Still depends on
libapt as if I make the method directly available everything is fine…
The results I get are:
$ g++ -Wall -Wextra -O0 -lapt-pkg /tmp/test.cc -o /tmp/test /tmp/test
amd64
i386
armel
$ g++ -Wall -Wextra -O2 -lapt-pkg /tmp/test.cc -o /tmp/test /tmp/test
amd64,i386,armel
Obviously, I would expect the same result with/without optimization.
Doing the suggested modification in getDefaultVector() gets the g++-4.x
series to produce the expected results. g++-5 still emits the results
from above (this is a closer representation of the code in apt, which
is why this hasn't happend before in apt).
Note that getDefaultVector() is called in the false branch of the ?:
operator, but that should never happen as the expression evaluates to
true. This seems to nugde the return type optimization in the wrong
direction through…
Note also that the value of the vector isn't the value of either of the
branches of the ?: operator, but is equal to the first argument of the
method called in the true branch.
If the ?: is replaced with an if-else block everything is fine.
(which is what I am gonna do – way too complicated for an ?: …)
Note Note: I am really bad at guessing and I tend to dislike
bugreporters who do it myself, but I couldn't help it…
The subject being the biggest offender really…
So take everything I just noted with at least a bit of salt.
Best regards
David Kalnischkies
¹ with the help of Julien Cristau and Helmut Grohne
² 4.x series tested in a wheezy chroot, hence the 4:4.7.2-1 version tag
// g++ -Wall -Wextra -O0 -lapt-pkg /tmp/test.cc -o /tmp/test /tmp/test
// g++ -Wall -Wextra -O2 -lapt-pkg /tmp/test.cc -o /tmp/test /tmp/test
#include string
#include map
#include vector
#include iostream
#include apt-pkg/strutl.h
/* method code for reference
vectorstring VectorizeString(string const haystack, char const split)
{
vectorstring exploded;
if (haystack.empty() == true)
return exploded;
string::const_iterator start = haystack.begin();
string::const_iterator end = start;
do {
for (; end != haystack.end() *end != split; ++end);
exploded.push_back(string(start, end));
start = end + 1;
} while (end != haystack.end() (++end) != haystack.end());
return exploded;
}
//*/
std::vectorstd::string getDefaultVector() {
std::vectorstd::string r; // broken g++-4.x g++-5
//static std::vectorstd::string r; // just g++-5
return r;
}
void parseOptions(std::mapstd::string, std::string const Options, std::string const field) {
std::mapstd::string, std::string::const_iterator arch = Options.find(field);
std::vectorstd::string Archs =
(arch != Options.end()) ? VectorizeString(arch-second, ',') :
getDefaultVector(); // - never called, but method content effects result
for (std::vectorstd::string::const_iterator a = Archs.begin(); a != Archs.end(); ++a)
std::cout *a std::endl;
}
int main() {
std::mapstd::string, std::string Options;
Options[a] = amd64,i386,armel;
parseOptions(Options, a);
return 0;
}
signature.asc
Description: Digital signature
Bug#780712: flightgear: permissive file access allowed from nasal
Package: flightgear Version: 3.0.0-1 Severity: grave Tags: security Upstream has reported two related security issues in how FlightGear restricts what files Nasal (its built-in scripting language for aircraft) can access. This bug is tracking the portion related to the flightgear source package: -fgValidatePath uses a property listener to do the checking, and while io.nas blocks direct removal of that listener, this can be bypassed by deleting the entire property node. Effect: Can read or write any file as the user (= arbitrary code execution). Fix: flightgear 6a30e7086ea2f1a060dd77dab6e7e8a15b43e82d Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Bug#780713: CVE-2015-2331
Source: php5 Severity: grave Tags: security This has been assigned CVE-2015-2331: https://bugs.php.net/bug.php?id=69253 https://github.com/php/php-src/commit/ef8fc4b53d92fbfcd8ef1abbd6f2f5fe2c4a11e5 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780714: [PATCH] Atomix game is 9 years old in Debian and depends on deprecated bonobo and libgnome2 technologies - please upload new upstream GTK3 version
Package: atomix Version: 2.14.0-5 Atomix game is 9 years old in Debian (ver. 2.14.0 released 2006-03) and depends on deprecated bonobo and libgnome2 technologies: libbonobo2-0 (= 2.32.1-3~), libbonoboui2-0 (= 2.15.1), libgdk-pixbuf2.0-0 (= 2.22.0), libgnome2-0 (= 2.17.3), libgnomecanvas2-0 (= 2.11.1), libgnomeui-0 (= 2.22.0) Please upload latest upstream Atomix GTK3 version - 3.15.92, which works fine with GTK+ 3.14 from Debian testing/unstable Porting to GTK3 was done January 2015, see https://git.gnome.org/browse/atomix/tree/NEWS * Fixed build problem (bug #711056) * Ported to GTK3 (bug #742827) * Added appstream XML (bug #742886) * Updated desktop file (bug #711056) * Miscapitalized menu items (bug #711056) * About dialog does not close (bug #336524) * Updated website (bug #381360) * Level completion detection fixed (bug #544762) * Removed heavy overlinking (bug #596094) I've updated debian packaging for Atomix 3.15.92 GTK3 release, see attached atomix_3.15.92-0.debian.tar.xz file - I've tested binary packages produced from this debian packaging on Debian unstable and Ubuntu 15.04 and didn't noticed any issues in the game. Thanks, Mantas Kriaučiūnas paslau...@bonamens.lt P.S. Compiled Atomix deb packages for Ubuntu 15.04 available at http://download.vikis.lt/baltix/devel/beta-bandomoji/ATOMIX-GAME-3.15/ -- Good luck, Mantas Kriaučiūnas Jabber ID: man...@akl.ltGPG ID: 43535BD5 Public organization Open Source for Lithuania - www.akl.lt Geriausios biuro programos verslui ir namams - http://openoffice.lt Prekyba naujais ir atnaujintais kompiuteriais su Linux OS - http://tinklas.eu Naudok Baltix GNU/Linux sistemą savo kompiuteryje - http://baltix.lt atomix_3.15.92-0.debian.tar.xz Description: application/xz atomix_3.15.92-0.dsc Description: Binary data
Bug#780710: Additional information
Hey! It seems that the wget does not take the last /n off the file name. Parsing it should help with the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780681: tengwar (tengwarscript) doesn't work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Seems, you're out of luck.
Tell me what finding a bug has to do with luck.
Am Di den 17. Mär 2015 um 23:01 schrieb Hilmar Preuße:
~ pdflatex tengtest.tex
The error message above is helpful perhaps Parmaite_alt is missing from the
map file., which is correct.
Well, that is not true. In my
/usr/share/texlive/texmf-dist/fonts/map/dvips/tengwarscript/tengwarscript.map
from texlive-fonts-extra version 2014.20141024-1 there is the font in
the 4. line.
However, that map seems to get ignored. So, wrongly installed.
There is a way around that: \pdfmapfile{=tengwarscript.map}, but as
the fonts are globally installed this map should be globally available
without using such a hack.
(see the transcript file for additional
information){/usr/share/texlive/texmf-dist/fonts/enc/dvips/base/8r.enc}{/usr/share/texlive/texmf-dist/fonts/enc/dvips/tengwarscript/tengwaralt.enc}
!pdfTeX error: pdflatex (file Parmaite_alt.ttf): cannot open TrueType font
file for reading
== Fatal error occurred, no output PDF file produced!
The reason is: the file Parmaite_alt.ttf is not part of the Debian
distribution; it has to be downloaded manually:
So the fonts are not correctly installed as I state in the bug report.
http://at.mansbjorkman.net/parmaite.htm . About the reason not to include it
I can only guess, but the copyright notice, is rather a cry for do not
include me! [1].
Well, for me that license looks free and compatible with debian.
However, there is only two solutions for that.
1. Include the full fonts and register the map properly (Not only the
.tfm and .vf files that are already included)
2. Or do not deliver any part of that fonts and state in README.Debian
that and why that fonts are not available.
Currently we have a mix where .tfm and .vf files are installed but not
the .ttf file. Moreover, there is a map file but it seems at a wrong
location so updmap-sys does not find it.
Sorry, no bug! One could think about removing the tengwar stub from TeX
Live/Debian to avoid further confusion.
Sorry, a bug. (And please stay objective in bugs and don't be venomous.)
Regards
Klaus
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen kl...@ethgen.de
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQGcBAEBCgAGBQJVCTaKAAoJEKZ8CrGAGfasQQIL/2ViUSHGxY5q5wjeApPE4GJK
gtl0GGBFJQ48oROLy/7KtLWwMlaap/LLl4xFc1dIobwmjn4ggimRImgkUtuaega/
5XZuXaqjiF0wSULITsWXQY0cDsMn4NTAjqLT6kM1Ei0rR2Xf2+/+EN3NlNPV5Lkk
Va7BZm+krgzp3M2gK0CwD56Oy4IWXlO7vla0G0fL4hbF1idphC6DBX4jP28WS5WT
GGldxn2OUGALaYWfq4rbEFCmBOJSIXWJ1E43xKKGnPqh7d02AQjr39Z7Lk9qFoBJ
AGZWjQQntKUdjpLwUFRwPGJxqwljuF0rX5XeJw9g/9Q8ecHqKCsiHYBAg0u1ZMrA
rMh9d8i5vBUY9tYRjEGdR/TidL/dYjDBojPLWPE1b2S+61d07DWhVnEZN7aLLX1o
uI513J8gsHekRm/tDv25Yhyw1zbvkaBXi7pTuqUk/RFO/5hrQqA5yNars9sH7b5c
ZPoPNZJqEw/rRqSq/wCuh2e4dHNK+aISjTJehw4u0A==
=kdSK
-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#709925: FreedomSponsors Entry
I made a proposal for this issue on FreedomSponsors [1] in case anyone is interested in putting a bounty on it. I'd like to package this, but I doubt it will be anytime soon. Maybe this will become more interesting for someone else to take on and it will get done faster. Regards, Afif 1. https://freedomsponsors.org/issue/661/rfp-zotero-dataserver-dataserver-for-the-zotero-client signature.asc Description: OpenPGP digital signature
Bug#780373: Add the ability to set preferred auto IM by locale
On Tue, Mar 17, 2015 at 11:18 PM, Osamu Aoki os...@debian.org wrote: Hi Aron, Can you tell me what exactly you wish to do. Was my previous mail properly depict it/ Let me know. Regards, Osamu About https://bugs.debian.org/780373 We are trying to make Fcitx default for Chinese locales in Ubuntu 15.04, as a transition of making it default for everyone in the next. im-config needs the ability of setting a default in a per-locale case, and fallback to existing mechanism when needed. I think the proposed way in your last email can fulfill my need, I didn't follow up quickly just because I haven't yet gotten a proper updated patch that align to the described behavior, :) Thanks, Aron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780717: sloccount: Change the default annual salary
Package: sloccount Version: 2.26-5.1 Severity: wishlist As per http://www.dwheeler.com/sloccount/sloccount.html: The default annual salary is $56,286 per year; this value was from the ComputerWorld, September 4, 2000's Salary Survey of an average U.S. programmer/analyst salary in the year 2000. You might consider using other numbers (ComputerWorld's September 3, 2001 Salary Survey found an average U.S. programmer/analyst salary making $55,100, senior systems programmers averaging $68,900, and senior systems analysts averaging $72,300). Those are numbers from 15 years ago. Taking the same source, but from last year, gives a programmer/analyst base salary of $73463. http://www.computerworld.com/salarysurvey/breakdown/2014/joblevel/3 Mike -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sloccount depends on: ii libc6 2.19-16 ii perl 5.20.2-2 sloccount recommends no packages. Versions of packages sloccount suggests: pn doc-base none -- 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#780722: unblock: flightgear-data/3.0.0-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, please unblock the package flightgear-data-3.0.0-3 as recently uploaded to unstable. It fixes a minor security issue by disallowing nasal scripts read access to the entire filesystem, see #780716. I kept the packaging changes as minimal as possible. A debdiff and the patch are both attached for review. unblock flightgear-data/3.0.0-3 Regards Markus Wanner diff -Nru flightgear-data-3.0.0/debian/changelog flightgear-data-3.0.0/debian/changelog --- flightgear-data-3.0.0/debian/changelog 2014-11-07 17:28:14.0 +0100 +++ flightgear-data-3.0.0/debian/changelog 2015-03-18 11:24:45.0 +0100 @@ -1,3 +1,11 @@ +flightgear-data (3.0.0-3) unstable; urgency=high + + * Add patch 60da20.patch removing FG_SCENERY from the list of +allowed directories to disallow nasal scripts from reading any +file as the user. Closes: #780716. + + -- Markus Wanner mar...@bluegap.ch Wed, 18 Mar 2015 10:43:34 +0100 + flightgear-data (3.0.0-2) unstable; urgency=medium [ Rebecca N. Palmer ] diff -Nru flightgear-data-3.0.0/debian/patches/60da20.patch flightgear-data-3.0.0/debian/patches/60da20.patch --- flightgear-data-3.0.0/debian/patches/60da20.patch 1970-01-01 01:00:00.0 +0100 +++ flightgear-data-3.0.0/debian/patches/60da20.patch 2015-03-18 11:08:01.0 +0100 @@ -0,0 +1,21 @@ +Description: Drop FG_SCENERY from the accepted file access list + The allowed directories for reading include FG_SCENERY, which can + be changed from Nasal via /sim/terrasync/scenery-dir. Effectively + allowing a nasal script to access any file with the user's + permission. +Author: Rebecca N. Palmer rebecca_pal...@zoho.com +Last-Update: 13-03-2015 +Origin: http://sourceforge.net/p/flightgear/fgdata/ci/60da2094252cee1a5cdfe737f29becd5c6800549 + +diff --git a/Nasal/IOrules b/Nasal/IOrules +index 71d2f67..ddb0189 100644 +--- a/Nasal/IOrules b/Nasal/IOrules +@@ -28,7 +28,6 @@ + READ ALLOW $FG_ROOT/* + READ ALLOW $FG_HOME/* + READ ALLOW $FG_AIRCRAFT/* +-READ ALLOW $FG_SCENERY/* + + WRITE ALLOW /tmp/*.xml + WRITE ALLOW $FG_HOME/*.sav diff -Nru flightgear-data-3.0.0/debian/patches/series flightgear-data-3.0.0/debian/patches/series --- flightgear-data-3.0.0/debian/patches/series 2014-11-06 20:12:35.0 +0100 +++ flightgear-data-3.0.0/debian/patches/series 2015-03-18 10:44:02.0 +0100 @@ -1,2 +1,3 @@ 766251.patch translation-update-pt.diff +60da20.patch signature.asc Description: OpenPGP digital signature
Bug#780705: udev: floating net device number on devices with ro rootfs
On Wed, 18 Mar 2015 14:57:33 +0800 You-Sheng Yang vic...@gmail.com wrote: Typo in the proposed patch. Re-attach the correct one. Oops. It seems udevd doesn't reload rule files. So since /lib/udev/rules.d/70-persistent-net.rules is always a dangling link, it will always be skipped during udevd startup. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780710: wget: while downloading, when ETA comes fills screen
Package: wget Version: 1.16-3 Severity: minor Dear Maintainer, When downloading with wget and using the new style (not the dot style) downloading, wget scrolls the name if it is longer than the space reserved for the system. That is ok. But when the system starts to show estimated time, the screen fills with extra lines instead of staying on one line. Example when does not work: snip --- ptakala@athlon:~/testi$ wget http://ftp.fi.debian.org/debian-cd/7.8.0/i386/jigdo-cd/debian-7.8.0-i386-CD-1.template --2015-03-18 09:44:00-- --http://ftp.fi.debian.org/debian-cd/7.8.0/i386/jigdo-cd/debian-7.8.0-i386-CD-1.template Selvitetään osoitetta ftp.fi.debian.org (ftp.fi.debian.org)... 130.230.54.99, 2001:708:310:54::99 Yhdistetään palvelimeen ftp.fi.debian.org (ftp.fi.debian.org)|130.230.54.99|:80... yhdistetty. HTTP-pyyntö lähetetty, odotetaan vastausta... 200 OK Pituus: 19743005 (19M) [application/x-troff-man] Tallennetaan kohteeseen ”debian-7.8.0-i386-CD-1.template” ian-7.8.0-i386-CD-1 5%[ ] 983,93K 271KB/s eta 86s an-7.8.0-i386-CD-1. 5%[ ] 1,07M 286KB/s eta 86s n-7.8.0-i386-CD-1.t 6%[ ] 1,16M 294KB/s eta 61s -7.8.0-i386-CD-1.te 6%[ ] 1,23M 313KB/s eta 61s -7.8.0-i386-CD-1.tem 6%[ ] 1,31M 338KB/s eta -61s.8.0-i386-CD-1.temp 7%[ ] 1,37M 362KB/s -eta 61s8.0-i386-CD-1.templ 7%[ ] 1,43M -407KB/s eta 61s.0-i386-CD-1.templa 7%[ ] -1,50M 394KB/s eta 59s0-i386-CD-1.templat 8%[ -] 1,57M 408KB/s eta 59sdebian-7.8.0-i386-C 8%[ -] 1,63M 388KB/s eta 59sebian-7.8.0-i386-CD 9%[ -] 1,70M 374KB/s eta 59sbian-7.8.0-i386-CD- 9%[= -] 1,77M 391KB/s eta 59sian-7.8.0-i386-CD-1 9%[= -] 1,84M 399KB/s eta 56san-7.8.0-i386-CD-1. 10%[= -] 1,91M 387KB/s eta 56sn-7.8.0-i386-CD-1.t 10%[= -] 1,99M 388KB/s eta 56s-7.8.0-i386-CD-1.te 10%[= -] 2,05M 360KB/s eta 56s7.8.0-i386-CD-1.tem 11%[= -] 2,14M 357KB/s eta 56s.8.0-i386-CD-1.temp 11%[= -] 2,21M 353KB/s eta 54s8.0-i386-CD-1.templ 12%[= -] 2,29M 355KB/s eta 54s ^C ptakala@athlon:~/testi$ snip As you can see, it makes excess lines to screen. It is not steady. This is how it should work: snip ptakala@athlon:~/testi$ wget http://ftp.fi.debian.org/debian-cd/7.8.0/i386/jigdo-cd/debian-7.8.0-i386-CD-1.jigdo --2015-03-18 09:47:16-- --http://ftp.fi.debian.org/debian-cd/7.8.0/i386/jigdo-cd/debian-7.8.0-i386-CD-1.jigdo Selvitetään osoitetta ftp.fi.debian.org (ftp.fi.debian.org)... 130.230.54.99, 2001:708:310:54::99 Yhdistetään palvelimeen ftp.fi.debian.org (ftp.fi.debian.org)|130.230.54.99|:80... yhdistetty. HTTP-pyyntö lähetetty, odotetaan vastausta... 200 OK Pituus: 39580 (39K) [application/x-troff-man] Tallennetaan kohteeseen ”debian-7.8.0-i386-CD-1.jigdo” debian-7.8.0-i386-CD-1.j 100%[==] 38,65K --.-KB/s kohteessa 0,07s 2015-03-18 09:47:17 (534 KB/s) - ”debian-7.8.0-i386-CD-1.jigdo” tallennettu [39580/39580] ptakala@athlon:~/testi$ - snip This bug is not severe, and does not affect the download, but it just shows out ugly... -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (1001, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.1psft (SMP w/4 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wget depends on: ii libc6 2.19-15 ii libgnutls-deb0-28 3.3.8-6 ii libidn11 1.29-1+b2 ii libnettle4 2.7.1-5 ii libpsl00.5.1-1 ii libuuid1 2.25.2-5 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages wget recommends: ii ca-certificates 20141019 wget 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#780679: git-buildpackage: support %(hversion)s, converting . to -
Hi Daniel,
On Tue, Mar 17, 2015 at 03:03:08PM -0400, Daniel Kahn Gillmor wrote:
Package: git-buildpackage
Version: 0.6.22
Tags: patch
Hi git-buildpackage people--
enigmail upstream uses tags named enigmail-1-8 for 1.8. Other upstreams
have used similar conventions, likely as holdovers from CVS (e.g. gnupg
1.4.2 was tagged with V1-4-2).
I'm proposing adding %(hversion)s as the hyphenated version, which
replaces . with -, to facilitate working with such upstreams.
Thanks for the patch. This matches a particular pattern, I wonder if
it wouldn't be better to introduce a configurable transformation
function to mangle the version like:
-
cat EOF ~/.gbp.conf
version_mangle = lambda x: x.replace('.', '-')
EOF
...
DebianGitRepository.version_to_tag(libfoo-%(mangled_version)s, 1.8.1)
...
return format_msg(format,
dict(version=DebianGitRepository._sanitize_version(version),
mangled_version=version_mangle(DebianGitRepository._sanitize_version(version)))
This would allow for arbitrary replacements/transformations. There
have been several requests for version mangling over time so this
might solve all at once.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780681: tengwar (tengwarscript) doesn't work
On 18.03.2015 09:25, Klaus Ethgen wrote: Am Di den 17. Mär 2015 um 23:01 schrieb Hilmar Preuße: Hi, ~ pdflatex tengtest.tex The error message above is helpful perhaps Parmaite_alt is missing from the map file., which is correct. Well, that is not true. In my /usr/share/texlive/texmf-dist/fonts/map/dvips/tengwarscript/tengwarscript.map from texlive-fonts-extra version 2014.20141024-1 there is the font in the 4. line. Yes, the map file is present, but not included in the map file, which is read my pdftex during run time. They are located below /var/lib and are updated/recreated by the steps I told you. However, that map seems to get ignored. So, wrongly installed. No, not registered. The reason is: the file Parmaite_alt.ttf is not part of the Debian distribution; it has to be downloaded manually: So the fonts are not correctly installed as I state in the bug report. Correct. http://at.mansbjorkman.net/parmaite.htm . About the reason not to include it I can only guess, but the copyright notice, is rather a cry for do not include me! [1]. Well, for me that license looks free and compatible with debian. I'd leave to decision about this to other people. However, there is only two solutions for that. 1. Include the full fonts and register the map properly (Not only the .tfm and .vf files that are already included) 2. Or do not deliver any part of that fonts and state in README.Debian that and why that fonts are not available. You're right that installing some piece of software only partially is not a good idea. We'll discuss the legal part, else we'll completely remove the tengwar stuff from Debian. H. -- sigfault -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780715: Please relax build-depends on libssl-dev to = 1.0.1k so that backporting to Jessie is possible
Source: python-cryptography Version: 0.8-1 Severity: wishlist Hi, As OpenStack Kilo (the next version of OpenStack, to be released within a few weeks now...) needs python-cryptography = 0.7.1. It is needed for Keystone (the auth system of OpenStack). So I tried to backport version 0.8 of python-cryptography from Experimental to Jessie. Unfortunately, this version has a build-depends on libssl-dev = 1.0.2, which means that it declares the need for OpenSSL from Experimental. However, since that version is currently broken, it doesn't work at all. I tried to relax the build-depends to libssl-dev = 1.0.1k (the version which is in Jessie), and all unit tests are passing correctly. So, please lower the version of libssl-dev in the build-depends of python-cryptography so that backports to Jessie are possible. Eventually, if you have time, I'd appreciate an upload of python-cryptography 0.8 to the official Debian backports. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780719: unblock: flightgear/3.0.0-5
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear release team,
please unblock the package flightgear-3.0.0-5 as recently uploaded to
unstable. It fixes a security issue by disallowing nasal scripts to
access or modify files, see #780712. I kept the packaging changes as
minimal as possible. A debdiff and the patch are attached for review.
unblock flightgear/3.0.0-5
Regards
Markus Wanner
diff -Nru flightgear-3.0.0/debian/changelog flightgear-3.0.0/debian/changelog
--- flightgear-3.0.0/debian/changelog 2014-11-07 17:27:50.0 +0100
+++ flightgear-3.0.0/debian/changelog 2015-03-18 11:19:39.0 +0100
@@ -1,3 +1,10 @@
+flightgear (3.0.0-5) unstable; urgency=high
+
+ * Add patch 6a30e70.patch to better restrict file access from
+nasal scripts. Closes: #780712.
+
+ -- Markus Wanner mar...@bluegap.ch Wed, 18 Mar 2015 08:45:21 +0100
+
flightgear (3.0.0-4) unstable; urgency=medium
* Add patch 750939.patch. Closes: #750939.
diff -Nru flightgear-3.0.0/debian/patches/6a30e7.patch flightgear-3.0.0/debian/patches/6a30e7.patch
# patch attached directly for better readability
diff -Nru flightgear-3.0.0/debian/patches/series flightgear-3.0.0/debian/patches/series
--- flightgear-3.0.0/debian/patches/series 2014-10-27 11:33:44.0 +0100
+++ flightgear-3.0.0/debian/patches/series 2015-03-18 08:48:58.0 +0100
@@ -2,3 +2,4 @@
nasal-fix.patch
fix-mobile-tacan.patch
750939.patch
+6a30e7.patch
Description: Restrict file access for Nasal scripts.
Stop using property listener for fgValidatePath
.
This was insecure: while removelistener() won't remove it, there are
other ways to remove a listener from Nasal
Author: Rebecca N. Palmer rebecca_pal...@zoho.com
Last-Update: 13-03-2015
Origin: http://sourceforge.net/p/flightgear/flightgear/ci/6a30e7086ea2f1a060dd77dab6e7e8a15b43e82d
--- a/src/Main/util.cxx
+++ b/src/Main/util.cxx
@@ -33,6 +33,7 @@
#include simgear/math/SGLimits.hxx
#include simgear/math/SGMisc.hxx
+#include GUI/MessageBox.hxx
#include fg_io.hxx
#include fg_props.hxx
#include globals.hxx
@@ -71,32 +72,142 @@
return current;
}
-// Write out path to validation node and read it back in. A Nasal
-// listener is supposed to replace the path with a validated version
-// or an empty string otherwise.
-const char *fgValidatePath (const char *str, bool write)
+static string_list read_allowed_paths;
+static string_list write_allowed_paths;
+
+// Allowed paths here are absolute, and may contain _one_ *,
+// which matches any string
+// FG_SCENERY is deliberately not allowed, as it would make
+// /sim/terrasync/scenery-dir a security hole
+void fgInitAllowedPaths()
{
-SGPropertyNode_ptr r, w;
-r = fgGetNode(/sim/paths/validate/read, true);
-r-setAttribute(SGPropertyNode::READ, true);
-r-setAttribute(SGPropertyNode::WRITE, true);
-
-w = fgGetNode(/sim/paths/validate/write, true);
-w-setAttribute(SGPropertyNode::READ, true);
-w-setAttribute(SGPropertyNode::WRITE, true);
-
-SGPropertyNode *prop = write ? w : r;
-prop-setStringValue(str);
-const char *result = prop-getStringValue();
-return result[0] ? result : 0;
+read_allowed_paths.clear();
+write_allowed_paths.clear();
+read_allowed_paths.push_back(globals-get_fg_root() + /*);
+read_allowed_paths.push_back(globals-get_fg_home() + /*);
+string_list const aircraft_paths = globals-get_aircraft_paths();
+for( string_list::const_iterator it = aircraft_paths.begin();
+ it != aircraft_paths.end();
+ ++it )
+{
+read_allowed_paths.push_back(*it + /*);
+}
+
+for( string_list::const_iterator it = read_allowed_paths.begin();
+ it != read_allowed_paths.end();
+ ++it )
+{ // if we get the initialization order wrong, better to have an
+ // obvious error than a can-read-everything security hole...
+if (!(it-compare(/*))){
+flightgear::fatalMessageBox(Nasal initialization error,
+Empty string in FG_ROOT, FG_HOME or FG_AIRCRAFT,
+or fgInitAllowedPaths() called too early);
+exit(-1);
+}
+}
+write_allowed_paths.push_back(/tmp/*.xml);
+write_allowed_paths.push_back(globals-get_fg_home() + /*.sav);
+write_allowed_paths.push_back(globals-get_fg_home() + /*.log);
+write_allowed_paths.push_back(globals-get_fg_home() + /cache/*);
+write_allowed_paths.push_back(globals-get_fg_home() + /Export/*);
+write_allowed_paths.push_back(globals-get_fg_home() + /state/*.xml);
+write_allowed_paths.push_back(globals-get_fg_home() + /aircraft-data/*.xml);
+write_allowed_paths.push_back(globals-get_fg_home() + /Wildfire/*.xml);
+write_allowed_paths.push_back(globals-get_fg_home() + /runtime-jetways/*.xml);
+
Bug#780677: How to proceed
Hi, I generated the symbol files for libc++1 and libc++abi1 packages. How shall I proceed with this bug? I think just dumping the symbol files to this bug seems insufficient. Best Regards, Jan signature.asc Description: OpenPGP digital signature
Bug#733044:
retitle 733044 RFP: apache-directory-studio -- The Eclipse-based LDAP browser and directory client noowner 733044 thanks I give up with this maven packaging hell. I have no time ATM. -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780162: default timeouts causing data loss
Am Sun, 15 Mar 2015 23:57:44 +0100 schrieb Tobias Frost t...@debian.org: Thanks for responding. Control: Severity 780207 important Control: Severity 780162 wishlist Hi Chris, can you please let us know the link to the upstream discussion? There are frequent reports and responds (like look at recent threadsfor timeout mismatch) comming up. Here is the thread where I got the hint, and then gathered some more info from looking up more precise responds: http://thread.gmane.org/gmane.linux.raid/48071/focus=48086 (The README in the .zip contains the last version.) From your description, I don't see a imminent risk of data loss which warrants a RC bug level. Therefore downgrading to important. AFAIK the all drives that have no data recovery timeout and try to recover a read error longer than the 30s controller timeout (most regular non-raid drives) get completely reset upon a simple block error, risking not only the block but any open/unwritten data. A raid may be able to recover everything from a redundand disk, only if there is no second read error while rebuilding the entire disk. The risk of a error while reading large disks is high (significant amount of such rebuild failure reports) where the second controller reset leads to the raid failing to rebuild leaving behind the array in a corrupt state. Without raid, there is no chance to recover, not only the defect block but also not any other open/unwritten data. That was why I set the bug level to RC, and it does somehow still look quite RC to me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780714: [PATCH] Atomix game is 9 years old in Debian and depends on deprecated bonobo and libgnome2 technologies - please upload new upstream GTK3 version
Hi Markus, Could you upload new Atomix GTK3 (ver. 3.15.92) packages into Debian experimental? Then Debian users can test new Atomix and don't be forced to install lots of bonobo 2.x and gnome 2.x packages. 2015-03-18 12:42, Markus Koschany wrote: On 18.03.2015 10:29, UAB „Bonamens“ wrote: [...] Please upload latest upstream Atomix GTK3 version - 3.15.92, which works fine with GTK+ 3.14 from Debian testing/unstable I am aware of the new release and will take care of uploading it as soon as Debian is no longer frozen. Regards, Markus Thanks, Mantas -- Good luck, Mantas Kriaučiūnas Jabber ID: man...@akl.ltGPG ID: 43535BD5 Public organization Open Source for Lithuania - www.akl.lt Geriausios biuro programos verslui ir namams - http://openoffice.lt Prekyba naujais ir atnaujintais kompiuteriais su Linux OS - http://tinklas.eu Naudok Baltix GNU/Linux sistemą savo kompiuteryje - http://baltix.lt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780509: closed by Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch (Closing bug)
Hi, confirm this Bug when upgrading from 40 to 41. Issues: - Text Selections not possible, partially marking text in link line not possible - Mouse Hover actions do not work entirely. - Applies only to virtualized environments (e.g. Virtualbox clients with integrated mouse) Solution: - downgrade to 40 (hmmm. didnt figure out where to get older jessie packages.) - disable mouse integration (not possible in seamless mode). Regards - Clemens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780584: RFS: s3cmd/1.5.2-1 ITA
Hi Harlan! (ccing Mikhail so he can ack/nack the GPL-2 to GPL-2+ change) The most concerning issue to me is the change in d/copyright from GPL-2 to GPL-2+ for the files under debian/. Matching them to upstream is best practice, to be sure, but to do so needs the permission of the authors of all the files underneath there - especially, it looks like, Mikhail Gusarov. It's not clear to me whether Matt Domsch's permission might also be needed; it certainly couldn't hurt, though. I didn't hide this from changelog, because I know this needs permission, and this is why I'm ccing him (sorry, I was sure I mentioned it in the ITA bug, bad me) Having it as GPL-2 makes it hard to forward patches to upstream (of course I can release *my* patches under GPL-2+, but seems better to relicense the debian packaging in my opinion) this is also why I didn't fix the nitpicks, as soon as I get confidence with the licensing I'll fix them directly upstream, they aren't on top of the issues in my opinion The man page has a couple of errors as well - groff is picking up some text and trying to apply it as a macro. There are also unescaped -'s that need to be escaped so they are not mistaken as hyphens instead of minuses. There's also a spelling error in the man file. All of these are upstream problems - probably with the tool they are using to create the manpage itself - but should be fixed if possible. Other than that, the remaining tweaks are minor. You should install the upstream changelog since it's provided. Upstream does provide GPG signatures of the downloads, so you should verify them if possible - the uscan(1) manpage has details about how to do so. That will require changing the watch file from github to sourceforge. nope, the asc file is also there on github, but for some reasons uscan is picking it and failing for another reason. (it is my first time I add an upstream signing key, help is appreciated) Thanks again for your work on s3cmd, and on Debian! If you have questions, please reach out to me. thanks for the review Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780584: RFS: s3cmd/1.5.2-1 ITA
Ack. On Wed, 18 Mar 2015, at 11:29, Gianfranco Costamagna wrote: Hi Harlan! (ccing Mikhail so he can ack/nack the GPL-2 to GPL-2+ change) The most concerning issue to me is the change in d/copyright from GPL-2 to GPL-2+ for the files under debian/. Matching them to upstream is best practice, to be sure, but to do so needs the permission of the authors of all the files underneath there - especially, it looks like, Mikhail Gusarov. It's not clear to me whether Matt Domsch's permission might also be needed; it certainly couldn't hurt, though. I didn't hide this from changelog, because I know this needs permission, and this is why I'm ccing him (sorry, I was sure I mentioned it in the ITA bug, bad me) Having it as GPL-2 makes it hard to forward patches to upstream (of course I can release *my* patches under GPL-2+, but seems better to relicense the debian packaging in my opinion) this is also why I didn't fix the nitpicks, as soon as I get confidence with the licensing I'll fix them directly upstream, they aren't on top of the issues in my opinion The man page has a couple of errors as well - groff is picking up some text and trying to apply it as a macro. There are also unescaped -'s that need to be escaped so they are not mistaken as hyphens instead of minuses. There's also a spelling error in the man file. All of these are upstream problems - probably with the tool they are using to create the manpage itself - but should be fixed if possible. Other than that, the remaining tweaks are minor. You should install the upstream changelog since it's provided. Upstream does provide GPG signatures of the downloads, so you should verify them if possible - the uscan(1) manpage has details about how to do so. That will require changing the watch file from github to sourceforge. nope, the asc file is also there on github, but for some reasons uscan is picking it and failing for another reason. (it is my first time I add an upstream signing key, help is appreciated) Thanks again for your work on s3cmd, and on Debian! If you have questions, please reach out to me. thanks for the review Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776279: please add support for the Doom 2 Master Levels
Hi, I would like to close this bug; I don't want to wait that some omnipotent Doom launcher eventually comes up. (https://github.com/chocolate-doom/chocolate-doom/issues/434) Here is a patch for adding doom2-masterlevels runtime binary package to g-d-p; this can run by itself without game-data-packager installed. Ok to push also on Alioth ? https://github.com/a-detiste/game-data-packager/commit/2432cbfc286ba7856eed9992d519f907a8aa8acd Alexandre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780703: closed by Markus Koschany a...@gambaru.de (eclipse-pydev fails to build from source)
reopen -1 thanks On 03/18/2015 09:33 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:eclipse-pydev package: #780703: eclipse-pydev fails to build from source It has been closed by Markus Koschany a...@gambaru.de. this fixes the architecture specific build, but not the build of the binary-indep target. Some dependencies missing here? BUILD FAILED /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:35: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/build.xml:91: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/templates/package-build/customTargets.xml:19: The following error occurred while executing this line: /usr/lib/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.8.1.dist/scripts/genericTargets.xml:111: Processing inclusion from feature org.python.pydev.feature: Bundle org.python.pydev.jython_3.9.2.dist failed to resolve.: Missing required plug-in org.python_0.0.0. Total time: 2 seconds An error has occurred. See the log file -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780709: vpnc: fails with Inappropriate ioctl for device
Hi, I'm having the exact same issue on my machines, it began with recent updates. I guess it's related to the updates of libgnutls and libgcrypt. Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` `- signature.asc Description: OpenPGP digital signature
Bug#780721: iputils: Please raise libcap2-bin from Recommends to Depends
Source: iputils Version: 3:20121221-5 Severity: normal Hello! The new version of iputils in Jessie uses capabilities instead of set-uid to gain the necessary priviliges to send ICMP requests. While this is a great improvement with regards to security, it currently may lead to rendering the ping and arping commands unusable for non-root users. This happens because the necessary package, libcap2-bin, which is required to properly configure the iputils package to use capabilities is currently set as Recommends in debian/control rather than a Depends. However, in many cases such as when using debootstrap (which is also used by FAI, for example), 'apt-get install' is run using the --no-install-recommends option which means the 'ping' command is installed such that it can be used by root only. In order to fix this, one has to manually install the libcap2-bin package and re-run 'dpkg-reconfigure iputils-ping' command, for example. Just adding the libcap2-bin package to the list of packages for debootstrap does not fix the problem. Thus, in order to avoid problems in environments where 'apt-get install' is run with the '--no-install-recommends' option, I would like you to ask to add libcap2-bin to Depends rather than Recommends in debian/control. Thanks, Adrian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780723: unblock: forked-daapd/22.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock latest forked-daapd in unstable. It fixes several RC bugs: Changes: forked-daapd (22.0-2) unstable; urgency=medium . * Fix compatibility with iTunes 12.1 (Closes: #778995) * Fix two segfaults with upstream patches (Closes: #778996) * Fix playing audio locally (Closes: #779011) Please see the debdiff is attached. Cheers, Balint forked-daapd-22.0-2.debdiff Description: Binary data
Bug#780713: [php-maint] Bug#780713: CVE-2015-2331
There are couple more heading our way: https://bugs.php.net/bug.php?id=68976 Sec Bug #68976 Use After Free Vulnerability in unserialize() and https://bugs.php.net/bug.php?id=69133 Sec Bug #69133 Use after free vulnerability in unserialize() with DateInterval also https://bugs.php.net/bug.php?id=68486 that can crash apache with apache2handler SAPI I suggest we wait couple of days for a new upstream release and in case it doesn't happen till end of week, I will go and cherry-pick. ok? Cheers, Ondrej On Wed, Mar 18, 2015, at 10:21, Moritz Muehlenhoff wrote: Source: php5 Severity: grave Tags: security This has been assigned CVE-2015-2331: https://bugs.php.net/bug.php?id=69253 https://github.com/php/php-src/commit/ef8fc4b53d92fbfcd8ef1abbd6f2f5fe2c4a11e5 Cheers, Moritz ___ pkg-php-maint mailing list pkg-php-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780720: unblock: gnome-boxes/3.14.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package gnome-boxes As discussed privately, jmm wanted to see fuseiso gone and gnome-boxes had an unneccesary/useless dependency on it. The new version simply drops the fuseiso dependency. unblock gnome-boxes/3.14.2-2 -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780521: nautilus: Impossible to rename files and directories
Thanks for the key-combination tips, as i did not know them. But i assume you realize that the majority of users don't know them and/or won't be able to remember them either. And you probably also realize that more many modern keyboards do not even have direct function keys anymore and require some key combination already to which your key combination tips then have to combined on top of those. Even worse to impossible with virtual/onscreen keyboards and modern applications not making use of any i imagine there will soon(/already?) be keyboards not having function keys at all. Date: Sun, 15 Mar 2015 17:57:06 + From: s...@debian.org To: hoekb...@hotmail.com; 780...@bugs.debian.org Subject: Re: Bug#780521: nautilus: Impossible to rename files and directories Control: retitle 780521 nautilus: not easy to rename files without a right mouse button On 15/03/15 14:12, Eerste Laatste wrote: Imagine you use a pen, finger or single button mouse, so in short do not have a right mouse button. Then in Nautilus select any file or directory and try to rename it. [...] It only seems possible using: - the right-windows-key or whatever the official key is which Windows keyboard have that pop-up the same menu you get when right-clicking a file or directory in Nautilus It's non-obvious, but Shift+F10 also does this (the same as in e.g. Windows), so you don't strictly need the menu key to use this method. - the key-board shortcut of Nautilus to rename a file or directory, but i am not aware such a key combination exists. This is also non-obvious, but the keyboard shortcut to rename is F2. Solution for me would be to bring back the rename option that was dropped from the menu That's a reasonable feature request, and would make this more discoverable. And i would find it logical that other than rename that should be brought back again, also copy and such should be in there even though those can be done with CTRL+C/X/V, because with drag and drop you can not enforce a copy instead of a move. FYI, you can: Ctrl+drag. Regards, S
Bug#780726: unblock: xbmc-pvr-addons/13.0+git20140512+g91cc731+dfsg1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release Team, Please unblock latest xbmc-pvr-addons in unstable. It fixes FTBFS on mips and drops an obsolete dependency: xbmc-pvr-addons (13.0+git20140512+g91cc731+dfsg1-2) unstable; urgency=low . [ Balint Reczey ] * Stop build-depending on libavcodec-dev (Closes: #755818) . [ James Cowgill ] * Fix build on MIPS by using generic atomics (Closes: #778830) Please see the debdiff is attached. Cheers, Balint xbmc-pvr-addons_13.0+git20140512+g91cc731+dfsg1-2.debdiff Description: Binary data
Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
Hi, On Tue, Mar 17, 2015 at 04:55:46PM +0200, Apollon Oikonomopoulos wrote: Hi, On 15:31 Tue 17 Mar , bertagaz wrote: Hi, When enabling storeconfig in puppetmaster, the database connection pool gets filled up by inactive connections opened by previous puppet agents runs. It's normal to see inactive connections from previous runs, but these should be marked as free in the pool and reusable. I can't reproduce this in our Jessie setup with Passenger, MariaDB 10.0.16 and ActiveRecord 4.1.8; I see 2 constantly open connections but I can clearly see they are being reused and recycled. What version of ActiveRecord do you have installed? Did it work in wheezy? I got confirmation it used to work in Wheezy. Are you using the stomserver queue handling feature? We're not, and I'm tempted to give it a try. I'll try to test in another environment, to be sure this bug is not related to any specifics bits of the current system. bert. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780725: PATH used for building is not specified
package: debian-policy affects: simutrans-pak128.britain x-debbugs-cc: ans...@debian.org, reproducible-bui...@lists.alioth.debian.org Hi, I've just noticed and filed #780724: simutrans-pak128.britain ftbfs if PATH does not contain /usr/games which made me notice that PATH is not specified in debian-policy. buildd.debian.org uses PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games while pbuilder uses PATH=/usr/sbin:/usr/bin:/sbin:/bin So this brings up three questions: a.) should /usr/games be in PATH when building packages? b.) should /usr/local/* be part of PATH? and finally, c.) what should PATH be, what must PATH include, what must not be included in PATH? Thanks for maintaining debian-policy! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation
We got hit by this bug too and reported it to upstream. See https://bz.apache.org/bugzilla/show_bug.cgi?id=57268 , applying the patch suggested in there to Debian source solved the issue for us. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769145: atheme-services: fails to upgrade from 'sid' - trying to overwrite /usr/sbin/dbverify
It looks to me like the problem here is simply that dbverify is a very
generic name being used for a very specific utility.
As far as I can tell, the 'dbverify' utility in Atheme is completely
unrelated to that in 389-ds. Neither works as a replacement for the
other. It is just a namespace clash. Therefore, I think a Replaces
relation would be inappropriate here. Perhaps it would be possible to
use Breaks on its own to make the situation be reflected properly in
dependency handling?
The proper solution is for the utility to be either renamed or removed
from the package. It is an administrative utility not called by anything
else in Atheme, therefore this should not break anything except possibly
administrators' local scripts - but Atheme's 'dbverify' does not exist
prior to version 7.0.0 so this does not affect anything using a version
from Debian stable/testing/unstable.
The attached patch renames the utility to atheme-dbverify.
389-ds may also be at fault in this - I am not sure to what extent
dbverify exists as a traditional name for a particular utility.
- Christopher Elsby
On Tue, 11 Nov 2014 20:16:25 +0100 Andreas Beckmann a...@debian.org wrote:
Package: atheme-services
Version: 7.0.7-1~exp0
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
From the attached log (scroll to the bottom...):
Selecting previously unselected package atheme-services.
Preparing to unpack .../atheme-services_7.0.7-1~exp0_amd64.deb ...
Unpacking atheme-services (7.0.7-1~exp0) ...
dpkg: error processing archive
/var/cache/apt/archives/atheme-services_7.0.7-1~exp0_amd64.deb (--unpack):
trying to overwrite '/usr/sbin/dbverify', which is also in package
389-ds-base 1.3.3.5-2
Errors were encountered while processing:
/var/cache/apt/archives/atheme-services_7.0.7-1~exp0_amd64.deb
cheers,
Andreas
Description: Rename dbverify utility to atheme-dbverify
The name dbverify is overly generic and clashes with 389-ds.
This is an administrative tool and not called by other parts of atheme.
Bug-Debian: https://bugs.debian.org/769145
Forwarded: no
Author: Christopher Elsby chr...@chrise.me.uk
Last-Update: 2015-03-18
Index: atheme-services-7.0.7/src/dbverify/Makefile
===
--- atheme-services-7.0.7.orig/src/dbverify/Makefile 2014-02-10 22:38:10.0 +
+++ atheme-services-7.0.7/src/dbverify/Makefile 2015-03-18 11:50:41.296103200 +
@@ -1,4 +1,4 @@
-PROG = dbverify${PROG_SUFFIX}
+PROG = atheme-dbverify${PROG_SUFFIX}
HELP_LINGUAS = es ru
SRCS = main.c
Bug#780724: Bug#780725: PATH used for building is not specified
On Wed, Mar 18, 2015 at 12:48:13PM +0100, Holger Levsen wrote: package: debian-policy affects: simutrans-pak128.britain x-debbugs-cc: ans...@debian.org, reproducible-bui...@lists.alioth.debian.org Hi, I've just noticed and filed #780724: simutrans-pak128.britain ftbfs if PATH does not contain /usr/games which made me notice that PATH is not specified in debian-policy. buildd.debian.org uses PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games while pbuilder uses PATH=/usr/sbin:/usr/bin:/sbin:/bin So this brings up three questions: a.) should /usr/games be in PATH when building packages? b.) should /usr/local/* be part of PATH? and finally, c.) what should PATH be, what must PATH include, what must not be included in PATH? I think this already come up, but I cannot find it. This raise the question, though: why binaries needed to build packages are in /usr/games in the first place ? In the simutrans instance, the culprit is the file /usr/games/makeobj which is not a game and has a very generic name, Also kdesdk-scripts provides /usr/bin/makeobj, so there is a filename conflict already. Maybe it would be better to move it to /usr/lib/simutrans/ and use an absolute path. In any case, policy currently has: 10.10. File names - The name of the files installed by binary packages in the system PATH (namely `/bin', `/sbin', `/usr/bin', `/usr/sbin' and `/usr/games') must be encoded in ASCII. though it is a strange place to define the system path. Cheers, -- Bill. ballo...@debian.org Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
Control: severity -1 normal Debian Bug Tracking System ow...@bugs.debian.org (2015-03-18): Processing commands for cont...@bugs.debian.org: severity 542899 serious Bug #542899 [os-prober] os-prober: please add a man page Severity set to 'serious' from 'normal' Pretty sure that's in no way a serious bug. If you want it to happen, submit one. Artificially bumping the severity won't help. Mraw, KiBi. signature.asc Description: Digital signature
Bug#780584: RFS: s3cmd/1.5.2-1 ITA
Hi Paul, All good points Harlan. I also won't be sponsoring this. thanks to you too! (now we have the ack) That tool doesn't appear to be run at build time to generate themanual page, which means that if downstream folks patch the command they won't get an updated manual page. I'd strongly suggest that the manual page be removed from the upstream git repos and tarballs and that the manual page be created at package build time. The script used to create the manual page would have to be added to the tarballs, currently it is only available in git. I opened upstream issue 505 https://github.com/s3tools/s3cmd/issues/505 That will require changing the watch file from github to sourceforge. An alternative would be to ask upstream to upload all of their tarballs and detached OpenPGP signatures to GitHub in addition to SourceForge. I'd recommend that they do that anyway so people who prefer GitHub can get them from there. I see them here https://github.com/s3tools/s3cmd/releases is that enough? uscan seems to be missing some bits, because it doesn't pick up the key python-magic is dropped from the recommends and isn't in depends, was that intended? I'd suggest using debdiff or debbindiff to compare binary packages before future uploads. yes, seems picked up by install_requires install_requires = [python-dateutil, python-magic] I checked the debian file and seems correct Depends: python-dateutil, python:any (= 2.7.5-5~), python:any ( 2.8), python, python-magic debian/docs has an unnecessary blank line. fixed Usually there are blank lines between the different contributors in debian/changelog, did you use dch to prepare the changelog? yes, but sometimes I use vim too :) fixed The homepage change isn't mentioned in debian/changelog. fixed I'd suggest replacing /tmp/ with ~/ in the README.md examples and the manual page. fixed and opened a pull request upstream As this tool is for interacting with a remote network service, I'd recommend implementing some post-install tests using the mechanisms described in DEP-8. http://dep.debian.net/deps/dep8/ mmm I don't have an amazon service free to test... seems difficult to achieve (we use a private key) It would be good to get one or two screenshots illustrating how to use this tool. https://screenshots.debian.net/upload it is a command line tool, are them really necessary? A build-time warning: I: dh_python2 pydist:184: Cannot find package that provides python_magic. Please add package that provides it to Build-Depends or add python_magic python-magic-fixme line to debian/pydist-overrides or add proper dependency to Depends by hand and ignore this info. I spotted it, but I don't know how to fix it, the python-magic seems correctly added by pydist. lintian: I restored the patches, they disappeared. $ pep8 --ignore W191 . lots of warnings $ pyflakes . lots of warnings can I just report them upstream? https://github.com/s3tools/s3cmd/issues/506 I can fix them, but rewriting downstream is really bad in my opinion, I would like to help upstream fixing them and then wait for the next release. I opened upstream pull requests/issues 504-505-506-507 with all the fixes. (I'm currently uploading again on mentors) thanks Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780724: simutrans-pak128.britain ftbfs if PATH does not contain /usr/games
package: simutrans-pak128.britain x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org Hi Ansgar, as discussed on IRC, simutrans-pak128.britain fails to build if PATH does not contain /usr/games, as this is the case when building with pbuilder. https://reproducible.debian.net/rbuild/testing/amd64/simutrans- pak128.britain_1.09-1.rbuild.log (also attached) exposed the issue, from the log: ... I: Building the package I: Running cd tmp/buildd/*/ env PATH=/usr/sbin:/usr/bin:/sbin:/bin dpkg- buildpackage -us -uc -b -rfakeroot ... /bin/bash: makeobj: command not found Makefile:102: recipe for target 'grounds' failed make[2]: *** [grounds] Error 127 ... Interestingly debian-policy does not specifiy what PATH should be for building packages, I will file a seperate bug about this now. I'm excited about the strange things which can be found on the journey to reproducible builds! :-) cheers, Holger Starting to build simutrans-pak128.britain/testing on 2015-03-17 10:46 The jenkins build log is/was available at https://jenkins.debian.net/job/reproducible_builder_beta/34492//console Reading package lists... Building dependency tree... NOTICE: 'simutrans-pak128.britain' packaging is maintained in the 'Svn' version control system at: svn://svn.debian.org/svn/pkg-games/packages/trunk/simutrans-pak128.britain/ Need to get 67.5 MB of source archives. Get:1 http://ftp.de.debian.org/debian/ testing/main simutrans-pak128.britain 1.09-1 (dsc) [2145 B] Get:2 http://ftp.de.debian.org/debian/ testing/main simutrans-pak128.britain 1.09-1 (tar) [67.5 MB] Get:3 http://ftp.de.debian.org/debian/ testing/main simutrans-pak128.britain 1.09-1 (diff) [4576 B] Fetched 67.5 MB in 2s (24.8 MB/s) Download complete and in download only mode -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 3.0 (quilt) Source: simutrans-pak128.britain Binary: simutrans-pak128.britain Architecture: all Version: 1.09-1 Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Uploaders: Ansgar Burchardt ans...@debian.org Homepage: http://www.simutrans.com/ Standards-Version: 3.9.2 Vcs-Browser: http://svn.debian.org/viewsvn/pkg-games/packages/trunk/simutrans-pak128.britain/ Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/simutrans-pak128.britain/ Build-Depends: debhelper (= 7.0.50~) Build-Depends-Indep: simutrans-makeobj (= 102.2) Package-List: simutrans-pak128.britain deb games extra Checksums-Sha1: 1fe8d0391450dfad398760765221d9a554221755 67523556 simutrans-pak128.britain_1.09.orig.tar.xz 1162cfd2e1e303b592084f5cfd91fa25cf77c8cb 4576 simutrans-pak128.britain_1.09-1.debian.tar.xz Checksums-Sha256: d579520f767727fd449e62940a3b17bcd00aa7e949584b9bb9af45057685ca95 67523556 simutrans-pak128.britain_1.09.orig.tar.xz 4d5f1a20580169b2e2adec6ff53e2b4ff57c1d571764b778e81c1fa2861cfca0 4576 simutrans-pak128.britain_1.09-1.debian.tar.xz Files: 3bb370f4f381e4785cc469559fc9f460 67523556 simutrans-pak128.britain_1.09.orig.tar.xz b8fa7d1f9841427832dd205f510cd8dd 4576 simutrans-pak128.britain_1.09-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJOvk3CAAoJEIATJTTdNH3IufAP/16jIY7zrcSNpkY4qj5KulKf LGsO4ac7pyf2tKrrpKcepg9KYoEdUvn1RtbOvQLnJ+Hv2Ul/mvxh0DIkCBHW4iil PkhMTtRhrfg2jZl2F3ejgA4h9b70YDNeKwELIkBcRZgR0yMvgHgmLB1AHBWNrClN JRYtzPcZKpZU2VOQqZhNfxEV1+IcU6pNstP+J20dsCTfuXCYvBqsdgFRQSUH6RBt vcHs/ym8QwSd/4elNIuMN0WTnF67pdppGZiZm0xej5hZX1W1KASVtgJc1uFM/+wM 34n0soh4QUFnrwkCTysGJHRkUhI+kdugpkInAIMPkASw5vjS+K9bw9hZgtY98GP+ IJ2fRIaRS5FSij876DjqMgHwTwNykaM+xL9L1NcPym3W4fN+yj5PYh57YCs9jgGC sHEmMtuXOOknE7ICLro1VoaRt4aYCMNGO7Det6Ay49civCgARFUxCEEiHUdnMXPn be9DA0RSNjjwMa3IXVmm3W4BROK4eGCImLrljc9xCqwhZfFVHw924v1Qot9k1fwl 0/1suTPJFgnZp6nc7jOOSgDZZc2CCMRSITOTQK9DVB8UtbISb31zEK0M/NxGVJn6 gd1YIeq3kZ9Xtjh3S0QvoSyfymW4md82KJr+CB/74vJFgnIT3kbMuCg5vRMfPZwH xzp2bpaDO6dxKShgXIQR =7BVG -END PGP SIGNATURE- + timeout 12h nice ionice -c 3 sudo DEB_BUILD_OPTIONS=parallel=23 TZ=/usr/share/zoneinfo/Etc/GMT+12 pbuilder --build --configfile /tmp/pbuilderrc_4zNd --debbuildopts -b --basetgz /var/cache/pbuilder/testing-reproducible-base.tgz --distribution testing simutrans-pak128.britain_1.09-1.dsc W: /root/.pbuilderrc does not exist I: using fakeroot in build. I: Current time: Mon Mar 16 22:47:01 GMT+12 2015 I: pbuilder-time-stamp: 1426589221 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/testing-reproducible-base.tgz] I: creating local configuration I: copying local configuration W: --override-config is not set; not updating apt.conf Read the manpage for details. I: mounting /proc filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /run/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps - Attempting to satisfy build-dependencies - Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy Version: 0.invalid.0 Architecture: amd64 Maintainer: Debian Pbuilder Team
Bug#542899: Processed: your mail
Hi Chris, On Mittwoch, 18. März 2015, Chris Bainbridge wrote: On 18 March 2015 at 11:35, Cyril Brulebois k...@debian.org wrote: Pretty sure that's in no way a serious bug. If you want it to happen, submit one. Artificially bumping the severity won't help. Isn't a missing man page a violation of the requirement stated in Debian Policy Manual 12.1? Hence violation of policy = severity serious? not every policy violation is a serious violation, which deserves a serious bug. there are ten thousands of policy violations if you count really nit picky... And really, the best way to get this fixed is to write the missing manpage. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#780679: git-buildpackage: support %(hversion)s, converting . to -
On Wed 2015-03-18 04:04:49 -0400, Guido Günther wrote:
Thanks for the patch. This matches a particular pattern, I wonder if
it wouldn't be better to introduce a configurable transformation
function to mangle the version like:
-
cat EOF ~/.gbp.conf
version_mangle = lambda x: x.replace('.', '-')
EOF
...
DebianGitRepository.version_to_tag(libfoo-%(mangled_version)s, 1.8.1)
...
return format_msg(format,
dict(version=DebianGitRepository._sanitize_version(version),
mangled_version=version_mangle(DebianGitRepository._sanitize_version(version)))
This last line is missing a close-paren, but i get the idea :)
This would allow for arbitrary replacements/transformations. There
have been several requests for version mangling over time so this
might solve all at once.
I can understand the appeal of your proposal, it does seem more
flexible, though a bit more cognitively costly for the user, who now has
to know what kind of code to write for version_mangle.
my only concern is that this change appears to make gbp.conf
turing-complete, which is maybe a risk we don't want to take? or maybe
gbp.conf is already capable of running arbitrary code, and i just don't
know how to do it.
Anyway, either mechanism would work for my purposes (and indeed, for
enigmail specifically, i might not have to worry about it in the future,
because i think upstream has just agreed to use simpler tagging
conventions).
Regards,
--dkg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot
Package: systemd Version: 215-12 Severity: normal Dear Maintainer, for some time now I noticed that fsck checks the root partition on every boot on both my jessie systems, desktop and notebook. As root file system I use ext4 for both of them. Relevant part from /etc/fstab: # / was on /dev/sda3 during installation LABEL=Root/ext4errors=remount-ro 0 1 LABEL=Home/homeext4errors=remount-ro,noatime 01 For some reason systemd rewrites the superblock of my root partition on every boot: Mär 18 11:35:51 laptop systemd-fsck[149]: Root: Superblock last write time is in the future. Mär 18 11:35:51 laptop systemd-fsck[149]: (by less than a day, probably due to the hardware clock being incorrectly set). FIXED. I have no clue, why systemd assumes the last write time is in the future. My hardware clock is kept in localtime (timezone Europe/Berlin) and I manually checked the bios time before boot. The number of mounts is also resetted when the superblock is rewritten. /etc/adjtime 6053.836117 1406826774 0.00 1406826774 LOCAL Extract from tune2fs -l /dev/sda3 (root partition): Filesystem created: Fri Oct 28 16:24:01 2011 Last mount time: Wed Mar 18 11:36:16 2015 Last write time: Wed Mar 18 11:35:51 2015 Mount count: 1 Maximum mount count: -1 Last checked: Wed Mar 18 11:35:51 2015 In contrast, my home partition has a mount count of 764 and the last mount time matches the last write time: Filesystem created: Sat Nov 10 18:09:07 2012 Last mount time: Wed Mar 18 11:36:16 2015 Last write time: Wed Mar 18 11:36:16 2015 Mount count: 764 Maximum mount count: -1 Last checked: Sat Nov 10 18:09:07 2012 Another user on the debian-user-german list also reported that fsck runs on every boot (don't know if the superblock is also rewritten). I'm not sure when this error appeared first, but I'm quite sure it wasn't introduced before February this year. -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (1001, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-5 ii libc6 2.19-15 ii libcap2 1:2.24-7 ii libcap2-bin 1:2.24-7 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.2-4+b1 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-12 ii mount 2.25.2-5 ii sysv-rc 2.88dsf-58 ii udev215-12 ii util-linux 2.25.2-5 Versions of packages systemd recommends: ii dbus1.8.16-1 ii libpam-systemd 215-12 Versions of packages systemd suggests: pn systemd-ui none -- 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#780584: RFS: s3cmd/1.5.2-1 ITA
On Wed, Mar 18, 2015 at 7:34 PM, Gianfranco Costamagna wrote: I opened upstream issue 505 https://github.com/s3tools/s3cmd/issues/505 Could you also suggest removing the manual page from git and tarballs so it is always built from source? I see them here https://github.com/s3tools/s3cmd/releases is that enough? uscan seems to be missing some bits, because it doesn't pick up the key Personally I'd suggest upstream upload tarballs for all the releases to GitHub as well as SF. That should be enough for uscan, the issue appears to be that you are matching against the GitHub-auto-generated tarballs and not the ones that upstream has created and uploaded next to them. Here is a fixed watch file: version=3 opts=pgpsigurlmangle=s/$/.asc/ \ https://github.com/s3tools/s3cmd/releases \ .*/s3cmd-(\d\S*)\.tar\.gz I checked the debian file and seems correct Depends: python-dateutil, python:any (= 2.7.5-5~), python:any ( 2.8), python, python-magic Hmm, I didn't get python-magic in the Depends when I built it. Both with the previous version and the one you just uploaded. The previous version I built with debuild and the current one inside pbuilder. I have python-magic installed in both. mmm I don't have an amazon service free to test... seems difficult to achieve (we use a private key) Ok, I guess it would be hard. it is a command line tool, are them really necessary? Not necessary, but useful for showing potential users what using it looks like lintian: I restored the patches, they disappeared. Please do use DEP-3 for patch headers and get patches upstreamed. http://dep.debian.net/deps/dep3/ can I just report them upstream? https://github.com/s3tools/s3cmd/issues/506 I can fix them, but rewriting downstream is really bad in my opinion, I would like to help upstream fixing them and then wait for the next release. Agreed, getting upstream to fix them and start using these tools is the best option. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
Chris Bainbridge chris.bainbri...@gmail.com (2015-03-18): On 18 March 2015 at 11:35, Cyril Brulebois k...@debian.org wrote: Pretty sure that's in no way a serious bug. If you want it to happen, submit one. Artificially bumping the severity won't help. Isn't a missing man page a violation of the requirement stated in Debian Policy Manual 12.1? Hence violation of policy = severity serious? Severe violations of policy would be serious. That's only a should, not a must/required, so no. Mraw, KiBi. signature.asc Description: Digital signature
Bug#780724: references
Hi, #780724 is the bug about simutrans-pak128.britain failing to build if PATH does not contain /usr/games, #780725 is the bug about debian-policy not defining PATH. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#780724: Bug#780725: PATH used for building is not specified
clone 780724 -1 reassign -1 pbuilder severity -1 serious retitle -1 pbuilder must defines PATH as in debian-policy (and as on buildds) # justification: breaks package builds, see 780724 Hi Bill, hi pbuilder maintainers, (leaving full quote to give context to the pbuilder maintainers) On Mittwoch, 18. März 2015, Bill Allombert wrote: On Wed, Mar 18, 2015 at 12:48:13PM +0100, Holger Levsen wrote: package: debian-policy affects: simutrans-pak128.britain x-debbugs-cc: ans...@debian.org, reproducible-bui...@lists.alioth.debian.org Hi, I've just noticed and filed #780724: simutrans-pak128.britain ftbfs if PATH does not contain /usr/games which made me notice that PATH is not specified in debian-policy. buildd.debian.org uses PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/ga mes while pbuilder uses PATH=/usr/sbin:/usr/bin:/sbin:/bin So this brings up three questions: a.) should /usr/games be in PATH when building packages? b.) should /usr/local/* be part of PATH? and finally, c.) what should PATH be, what must PATH include, what must not be included in PATH? I think this already come up, but I cannot find it. This raise the question, though: why binaries needed to build packages are in /usr/games in the first place ? In the simutrans instance, the culprit is the file /usr/games/makeobj which is not a game and has a very generic name, Also kdesdk-scripts provides /usr/bin/makeobj, so there is a filename conflict already. yes, that's why I left 780724 assigned to simutrans-pak128.britain... Maybe it would be better to move it to /usr/lib/simutrans/ and use an absolute path. probably, yeah. In any case, policy currently has: 10.10. File names - The name of the files installed by binary packages in the system PATH (namely `/bin', `/sbin', `/usr/bin', `/usr/sbin' and `/usr/games') must be encoded in ASCII. though it is a strange place to define the system path. Thanks. Thus I'ved cloned 780724 and assigned the clone to pbuilder, so that pbuilder gets fixed. Feel free to close 780725 or keep it open to move the PATH definition to a better place. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#756467: Supermin: test-build-bash.sh failed on mips64el: failed to find a suitable kernel
Control: tags -1 - moreinfo + patch Hi, On Wed, 30 Jul 2014 21:18:17 +0200 Hilko Bengen ben...@debian.org wrote: for the test to succeed, supermin must be able to find the kernel and the modules. This only works if a kernel image is installed, of course: The source package needs to build-depend on a suitable kernel package. Please add linux-image-arm64 [arm64] to the build-dependencies and try to rebuild the package. Does everything work now? If not, please post the error message you get now. I added a mips64el kernel to the build-dependencies and supermin builds and passes all the tests now. Thanks, James diff -u -r a/debian/control b/debian/control --- a/debian/control 2015-03-08 09:46:44.0 + +++ b/debian/control 2015-03-17 17:17:57.773497094 + @@ -17,6 +17,7 @@ linux-image-armmp [armhf], linux-image-arm64 [arm64], linux-image-4kc-malta [mips mipsel] | linux-image-5kc-malta [mips mipsel], + linux-image-5kc-malta [mips64 mips64el], linux-image-s390x [s390x], linux-image-powerpc [powerpc], linux-image-powerpc64le [ppc64el], signature.asc Description: This is a digitally signed message part
Bug#780703: closed by Markus Koschany a...@gambaru.de (eclipse-pydev fails to build from source)
Control: tags -1 unreproducible On 18.03.2015 11:32, Matthias Klose wrote: reopen -1 thanks On 03/18/2015 09:33 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:eclipse-pydev package: #780703: eclipse-pydev fails to build from source It has been closed by Markus Koschany a...@gambaru.de. this fixes the architecture specific build, but not the build of the binary-indep target. Some dependencies missing here? Hello, I have just rebuilt eclipse-pydev with git-buildpackage in a clean sid cowbuilder chroot and I cannot reproduce this build failure. The binary-indep target works as expected. GIT_PBUILDER_OPTIONS=--debbuildopts=-A DIST=sid ARCH=amd64 git-buildpackage Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#298917: Show NetworkStatusDevice only for up and running Devices
Version: 1.3.8+githubmod+20150310+31bfd46-2 Control: tags 20150310 +unreproducible +moreinfo On Thu, 10 Mar 2005 18:31:46 +0100 Klaus Fuerstberger linux...@arcor.de wrote: Package: icewm Version: 1.2.17-1 Severity: minor Hi all, one of the last updates changed the behavior of the Network Status in the Taskbar. I liked it, when I start a specific Openvpn Connection and when the connection was up, the Network Device Symbol comes up. After the update to my local mirror, all Symbols for all defined Devices are shown in the Taskbar whether the Device ist up or not. This is not very useful I think. Is there a changed settig, or is this a minor bug? Cannot reproduce this with the current version (in Sid) anymore. The tray area is resized as needed when the device come up or disappear again. Could you test again? Regards, Eduard. -- Begangene Fehler können nicht besser entschuldigt werden als mit dem Geständnis, daß man sie als solche erkennt. -- Pedro Calderon de la Barca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780584: RFS: s3cmd/1.5.2-1 ITA
Hi Paul I opened upstream issue 505 https://github.com/s3tools/s3cmd/issues/505 Could you also suggest removing the manual page from git and tarballs so it is always built from source? I just noticed Matt here is also upstream, bad me I didn't check :) Personally I'd suggest upstream upload tarballs for all the releases to GitHub as well as SF. it is already this way, I uploaded a fix for the watch file right now That should be enough for uscan, the issue appears to be that you are matching against the GitHub-auto-generated tarballs and not the ones that upstream has created and uploaded next to them. Here is a fixed watch file: version=3 opts=pgpsigurlmangle=s/$/.asc/ \ https://github.com/s3tools/s3cmd/releases \ .*/s3cmd-(\d\S*)\.tar\.gz hehe, I uploaded almost exactly this patch prior to your mail, just a difference: .*/s3cmd\-?(\d\S*)\.tar\.gz instead of .*/s3cmd-(\d\S*)\.tar\.gz (reuploading right now on mentors) the problem was just an outdated uscan version :) Hmm, I didn't get python-magic in the Depends when I built it. Bothwith the previous version and the one you just uploaded. The previous version I built with debuild and the current one inside pbuilder. I have python-magic installed in both. you are right the problem is the newer dh-python that stopped guessing b-d http://anonscm.debian.org/cgit/dh-python/dh-python.git/commit/?id=de7db9bd0021cee65e477f11cd69cfd93350bd2e well, I added an override for this, the problem seems to be in python-magic (I don't know hot to best report this though) Please do use DEP-3 for patch headers and get patches upstreamed. http://dep.debian.net/deps/dep3/ done Agreed, getting upstream to fix them and start using these tools isthe best option. cheers, Gianfranco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780731: caja crashes after usb drive eject if any bookmarks are present
Source: caja Version: 1.8.2-2 Severity: important Tags: jessie sid Steps to reproduce (from LP bug [1]): --- To reproduce the bug you need : A usb stick connected and recognized in caja and at least one bookmark appearing in the left side of caja, normally the bookmark will appear under the usb stick 1) in the caja window appearing when the usb stick in inserted, click on the eject button to unmount the usb stick = a bug makes the bookmark sticking to the pointer (to see it move the pointer a little bit 2) place the sticky bookmark in front of its real place (the sticky bookmark is supposed to be right in front of the real bookmark) 3) click = caja crashes --- The upstream pull request [2] should fix it. [1] https://bugs.launchpad.net/bugs/1377967 [2] https://github.com/mate-desktop/caja/pull/396
Bug#597897: Current status of alsa-firmware?
Unfortunately, some of the blobs in alsa-firmware are purportedly licensed under the GPLv2, but without source code available. The same problem exists for some blobs that were moved out of the linux tree, but since they were included in Linux tarballs for many years without objection from the copyright holders it is probably safe for kernel.org and other distributors to continue distributing them. However I am not prepared to put anyone at legal risk by adding more of these. Clear. I think we need someone to review the licence status of blobs in alsa-firmware and determine which of them are clearly redistributable. Then these can be added to linux-firmware.git and to Debian's firmware-nonfree. Who should be a person which can help with this? debian-legal? Should we rise the severity to serious? best regards Jaromir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
On 18 March 2015 at 11:35, Cyril Brulebois k...@debian.org wrote: Pretty sure that's in no way a serious bug. If you want it to happen, submit one. Artificially bumping the severity won't help. Isn't a missing man page a violation of the requirement stated in Debian Policy Manual 12.1? Hence violation of policy = severity serious? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775016: ITP: hovercraft -- impress.js presentations by reStructuredText
Hovercraft packaging [1] status report update: solved issues: 1) python3-watchdog is in NEW 2) modules are private now deps remaining RFS: 3) svg.path [2] 4) manuel [3] (could be spared when the tests are disabled) open issues: 5) python-logo-master-v3-TM.png might be non DFSG-compliant [4], could be spared in the examples but it's also used for the tests: ./hovercraft/tests/test_data/maximal/images/python-logo-master-v3-TM.png ./hovercraft/tests/test_data/images/python-logo-master-v3-TM.png ./docs/examples/images/python-logo-master-v3-TM.png That could be difficult to patch out ... Take out, leave tests disabled? Suggestions welcome. Thank you, DS [1] http://anonscm.debian.org/cgit/collab-maint/hovercraft.git [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776571 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776571 [4] https://lists.debian.org/debian-mentors/2015/02/msg00202.html -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB1CA89EA3B74376761DB915E09AF4DF5182C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780727: UDD: rcblog is broken - undefined method `[]' for nil:NilClass (NoMethodError)
Package: qa.debian.org Severity: normal User: qa.debian@packages.debian.org Usertags: udd Hi, The rc bugs blog at this page is blank: https://udd.debian.org/cgi-bin/rcblog.cgi The response headers contain this (some newlines added for clarity): HTTP/1.1 200 OK Date: Wed, 18 Mar 2015 12:09:56 GMT Server: Apache /srv/udd.debian.org/udd/web/cgi-bin/rcblog.cgi: 83:in `getcount': undefined method `[]' for nil:NilClass (NoMethodError) from /srv/udd.debian.org/udd/web/cgi-bin/rcblog.cgi: 93:in `block in main', 92:in `each', 92:in `main' Strict-Transport-Security: max-age=15552000 X-Clacks-Overhead: GNU Terry Pratchett Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 20 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: text/html Thanks, James signature.asc Description: This is a digitally signed message part
Bug#780730: mutt: Does not work correctly with newer gpg-agent
Package: mutt
Version: 1.5.23-3
Severity: wishlist
Tags: patch
Hi!
With recent GnuPG versions, the gpg-agent is always used, and is
started on demand if not already running. It also now uses a stable
socket pathname and as such does not need (and actually ignores) the
GPG_AGENT_INFO environment variable.
I had prepared a patch that uses that socket address also to determine
if the agent is running, but that's actually wrong, because not having
the agent running is a valid configuration and gpg2 will take care of
starting it if needed. So the only sane option with newer gpg2 is to
ignore the environment varialbe altogether. This can cause issues for
people using older gpg, but I'd say that if they are setting
pgp_use_gpg_agent=yes then they should know what they are doing?
In any case I'm attaching both patches, but the correct one to use
is the one that removes the check for the environment variable
(gpg2-agent-always.patch).
Thanks,
Guillem
---
crypt-gpgme.c | 12
pgp.c |2 +-
2 files changed, 1 insertion(+), 13 deletions(-)
--- a/crypt-gpgme.c
+++ b/crypt-gpgme.c
@@ -4407,21 +4407,9 @@ static void init_common(void)
}
/* Initialization. */
-static void init_gpgme (void)
-{
- /* Make sure that gpg-agent is running. */
- if (! getenv (GPG_AGENT_INFO))
-{
- mutt_error (_(\nUsing GPGME backend, although no gpg-agent is running));
- if (mutt_any_key_to_continue (NULL) == -1)
- mutt_exit(1);
-}
-}
-
void pgp_gpgme_init (void)
{
init_common();
- init_gpgme ();
}
void smime_gpgme_init (void)
--- a/pgp.c
+++ b/pgp.c
@@ -108,7 +108,7 @@ int pgp_use_gpg_agent (void)
{
char *tty;
- if (!option (OPTUSEGPGAGENT) || !getenv (GPG_AGENT_INFO))
+ if (!option (OPTUSEGPGAGENT))
return 0;
if ((tty = ttyname(0)))
---
crypt-gpgme.c |6 +-
pgp.c |8 +++-
2 files changed, 12 insertions(+), 2 deletions(-)
--- a/crypt-gpgme.c
+++ b/crypt-gpgme.c
@@ -4409,8 +4409,12 @@ static void init_common(void)
/* Initialization. */
static void init_gpgme (void)
{
+ char gpg_agent_socket[STRING];
+
/* Make sure that gpg-agent is running. */
- if (! getenv (GPG_AGENT_INFO))
+ snprintf (gpg_agent_socket, sizeof(gpg_agent_socket),
+%s/.gnupg/S.gpg-agent, NONULL(Homedir));
+ if (! getenv (GPG_AGENT_INFO) access (gpg_agent_socket, F_OK) == -1)
{
mutt_error (_(\nUsing GPGME backend, although no gpg-agent is running));
if (mutt_any_key_to_continue (NULL) == -1)
--- a/pgp.c
+++ b/pgp.c
@@ -106,9 +106,15 @@ void pgp_forget_passphrase (void)
int pgp_use_gpg_agent (void)
{
+ char gpg_agent_socket[STRING];
char *tty;
- if (!option (OPTUSEGPGAGENT) || !getenv (GPG_AGENT_INFO))
+ if (!option (OPTUSEGPGAGENT))
+return 0;
+
+ snprintf (gpg_agent_socket, sizeof(gpg_agent_socket),
+%s/.gnupg/S.gpg-agent, NONULL(Homedir));
+ if (!getenv (GPG_AGENT_INFO) access (gpg_agent_socket, F_OK) == -1)
return 0;
if ((tty = ttyname(0)))
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
Source: fai Version: 4.3.2 Severity: important Hello! While preparing to migrate our installed FAI systems to Jessie, we stumbled into the problem that it was no longer possible to log on to systems being installed via SSH: === glaubitz@jessie64:~ ssh root@vs76 X11 forwarding request failed on channel 0 PTY allocation request failed on channel 0 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. -bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) stdin: is not a tty === This is a result of devpts not being mounted to /dev/pts in the NFSROOT (while it is actually mounted under /target/dev/pts). Manually mounting devpts on the client with a local console fixes the issue temporarily. Looking at the main fai script, fai_init() actually tries to mount devpts which will, however, only succeed if devpts is already mounted as it checks for the devpts string in /proc/mounts which shows all currently mounted filesystems: if grep -wq devpts /proc/mounts; then mount -t devpts devpts /dev/pts fi On Wheezy this works as the client has already mounted devpts at boot time and the attempted mount just results in an error message which is ignored: mount: devpts already mounted or /dev/pts busy mount: according to mtab, /dev/pts is already mounted on /dev/pts On Jessie, devpts is *not* mounted at boot time (probably due to a change in Debian Live, but I haven't found the reason yet) and consequently, the mount call is never executed as devpts is not present in /proc/mounts. I am also not sure why the mount condition for devpts is actually that devpts is already mounted somewhere. Maybe this was rather intended to check for devpts in /proc/filesystems, the list of filesystems the currently loaded kernel understands? In any case, devpts has to be mounted by the init scripts (systemd does this automatically) or, in this case, by the fai main script as Debian's kernel are usually compiled without CONFIG_DEVTMPFS_MOUNT. Cheers, Adrian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: Processed: your mail
On 18 March 2015 at 11:59, Holger Levsen hol...@layer-acht.org wrote: And really, the best way to get this fixed is to write the missing manpage. Attached. Please add to the Debian package. linux-boot-prober.8 Description: Binary data os-prober.8 Description: Binary data
Bug#780734: anki: segmentation fault
Package: anki Version: 2.0.31+dfsg-1 Severity: normal I can't reproduce it, but it happens quite regularly (meaning I can make it crash again to get more data if necesary) here is a backtrace FIXME: handle dialog start. FIXME: handle dialog end. FIXME: handle dialog start. FIXME: handle dialog end. Program received signal SIGSEGV, Segmentation fault. 0x736f63ae in QMetaObject::cast(QObject*) const () from /usr/lib/x86_64 -linux-gnu/libQtCore.so.4 (gdb) bt #0 0x736f63ae in QMetaObject::cast(QObject*) const () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #1 0x71f2756f in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #2 0x71f2794b in QAccessibleWidget::text(QAccessible::Text, int) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #3 0x71f27c99 in QAccessibleWidgetEx::text(QAccessible::Text, int) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #4 0x7fff99f75e4f in ?? () from /usr/lib/kde4/plugins/accessiblebridge/kaccessiblebridge.so #5 0x71f2a2f4 in QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x71edbc6f in QDialog::setVisible(bool) () from /usr/lib/x86_64 -linux-gnu/libQtGui.so.4 #7 0x7289649c in ?? () from /usr/lib/python2.7/dist- packages/PyQt4/QtGui.so #8 0x71efed2c in QProgressDialog::reset() () from /usr/lib/x86_64 -linux-gnu/libQtGui.so.4 #9 0x71efed51 in QProgressDialog::cancel() () from /usr/lib/x86_64 -linux-gnu/libQtGui.so.4 #10 0x728526e4 in ?? () from /usr/lib/python2.7/dist- packages/PyQt4/QtGui.so #11 0x004c9e05 in call_function (oparg=optimized out, pp_stack=optimized out) at ../Python/ceval.c:4033 #12 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #13 0x004ca592 in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4119 #14 call_function (oparg=optimized out, pp_stack=optimized out) at .../Python/ceval.c:4054 #15 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #16 0x004ca592 in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4119 #17 call_function (oparg=optimized out, pp_stack=optimized out) at .../Python/ceval.c:4054 #18 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #19 0x004c87a1 in PyEval_EvalCodeEx () at ../Python/ceval.c:3265 #20 0x004ca31a in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4129 #21 call_function (oparg=optimized out, pp_stack=optimized out) at .../Python/ceval.c:4054 #22 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #23 0x004ca592 in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4119 #24 call_function (oparg=optimized out, pp_stack=optimized out) at .../Python/ceval.c:4054 #25 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #26 0x004ca592 in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4119 #27 call_function (oparg=optimized out, pp_stack=optimized out) at .../Python/ceval.c:4054 #28 PyEval_EvalFrameEx () at ../Python/ceval.c:2679 #29 0x004e5fe8 in PyEval_EvalCodeEx (closure=optimized out, defcount=optimized out, defs=optimized out, kwcount=optimized out, kws=optimized out, argcount=optimized out, args=optimized out, locals=optimized out, globals=optimized out, co=optimized out) at ../Python/ceval.c:3265 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages anki depends on: ii libjs-jquery 1.7.2+dfsg-3.2 ii libjs-jquery-flot 0.8.2+dfsg-1 ii libjs-jquery-ui 1.10.1+dfsg-1 ii python-beautifulsoup 3.2.1-1 ii python-httplib2 0.9+dfsg-2 ii python-pyaudio0.2.8-1+b1 ii python-qt44.11.2+dfsg-1 ii python-simplejson 3.6.5-1 ii python-sqlalchemy 0.9.8+dfsg-0.1 pn python:anynone Versions of packages anki recommends: ii python-matplotlib 1.4.2-3.1 Versions of packages anki suggests: pn dvipngnone pn lame none ii mplayer2 2.0-728-g2c378c7-4+b1 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690521: xxxterm: X Window System errror, dies with 'BadAlloc (insufficient resources for operation)'
reassign 690521 xombrero 2:1.6.4-1 tag 690521 + upstream thanks On Mon, 15 Oct 2012 09:33:57 +0200 Julius Seemayer deb...@yeeer.net wrote: Package: xxxterm Version: 1:1.11.3-1 Severity: important Steps to reproduce: 1) start xxxterm 2) do anything, e.g. click right on the empty main tab and select 'Inspect Element' 3) xxxterm dies with code 1, leaving the message: xxxterm: config_parse: cannot open /home/myuser/.xxxterm.conf: No such file or directory The program 'xxxterm' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1328 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (note I'm replacing my login name with myuser) Running with --sync prevents from crashing there. I'm a little confused, xxxterm runs on another Wheezy box, amd64, without abnormality. I'm not sure what additional Information I could provide. Using the source package gives the same behavior, running in gdb without anything, with break on gdk_x_error() and finally with --sync gives: $ gdb linux/xxxterm GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /home/myuser/tmp/xxxterm-1.11.3/linux/xxxterm...done. (gdb) r Starting program: /home/myuser/tmp/xxxterm-1.11.3/linux/xxxterm [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. xxxterm: config_parse: cannot open /home/myuser/.xxxterm.conf: No such file or directory [New Thread 0xb341ab70 (LWP 11833)] [New Thread 0xb2af2b70 (LWP 11834)] [New Thread 0xb22ddb70 (LWP 11835)] [New Thread 0xb1addb70 (LWP 11836)] [New Thread 0xad309b70 (LWP 11837)] [New Thread 0xac60db70 (LWP 11839)] [New Thread 0xabe05b70 (LWP 11840)] [New Thread 0xab605b70 (LWP 11841)] [New Thread 0xaae05b70 (LWP 11842)] [New Thread 0xaa605b70 (LWP 11843)] [New Thread 0xa9e05b70 (LWP 11844)] [New Thread 0xa94e4b70 (LWP 11845)] [New Thread 0xa8ce4b70 (LWP 11846)] -- Herbert Parentes Fortes Neto (hpfn) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
Hi, On Wed, Mar 18, 2015 at 02:26:59PM +0100, bertagaz wrote: Are you using the stomserver queue handling feature? We're not, and I'm tempted to give it a try. It does not fix this issue. I'll try to test in another environment, to be sure this bug is not related to any specifics bits of the current system. Just tried in another Jessie environment, which is an almost fresh one, installed not so long ago and that didn't had a lot of changes. Sadly, I hit the same bug. :/ bert. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780736: help button does not provide help
Subject: gnome-menus: activating help button does not provide help Package: gnome-menus Version: 3.4.2-5 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Panel: Applications Accessories Main Menu * What exactly did you do (or not do) that was effective (or ineffective)? Click on Button Help. * What was the outcome of this action? A window pops up saying: Document Not Found The URI ‘ghelp:user-guide?menu-editor#menu-editor’ does not point to a valid page. Search for packages containing this document. Clicking onto the link Search for packages containing this document, a new window shows up, saying: Failed to find package. The file could not be found in any packages. Clicking on button More Information, a web page shows up saying: Missing Package Unfortunately, the package you were searching for is not available in the repositories. * What outcome did you expect instead? A help information or product documentation should show up. *** End of the template - remove these lines *** -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-menus depends on: ii dpkg1.16.15 ii python 2.7.3-4+deb7u1 gnome-menus recommends no packages. gnome-menus suggests no packages. -- no debconf information
Bug#780737: php5-fpm: Call to undefined function apache_request_headers()
Package: php5-fpm Version: 5.4.36-0+deb7u3 Severity: important Tags: patch Dear Maintainer, Please see php bug https://bugs.php.net/bug.php?id=67337thanks=6 There is a patch that should be pushed to the debian package to address this bug. The link to the patch is on that page. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 php5-fpm depends on: ii dpkg 1.16.15 ii libbz2-1.01.0.6-4 ii libc6 2.13-38+deb7u8 ii libcomerr21.42.5-1.1+deb7u1 ii libdb5.1 5.1.29-5 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 ii libk5crypto3 1.10.1+dfsg-5+deb7u3 ii libkrb5-3 1.10.1+dfsg-5+deb7u3 ii libmagic1 5.11-2+deb7u7 ii libonig2 5.9.1-1 ii libpcre3 1:8.30-5 ii libqdbm14 1.8.78-2 ii libssl1.0.0 1.0.1e-2+deb7u14 ii libxml2 2.8.0+dfsg1-7+wheezy3 ii mime-support 3.52-1+deb7u1 ii php5-common 5.4.36-0+deb7u3 ii tzdata2015a-0wheezy1 ii ucf 3.0025+nmu3 ii zlib1g1:1.2.7.dfsg-13 php5-fpm recommends no packages. Versions of packages php5-fpm suggests: pn php-pear none -- Configuration Files: /etc/php5/fpm/php-fpm.conf changed [not included] /etc/php5/fpm/pool.d/www.conf [Errno 2] No such file or directory: u'/etc/php5/fpm/pool.d/www.conf' -- 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#714118: php-composer -- Dependency Manager for PHP
There is a working package over on https://github.com/RobLoach/composer.deb As per the pending status of this report, and the related [NEW] page, there is one already on [ALIOTH] waiting for inclusion in Debian. [NEW] https://ftp-master.debian.org/new/composer_1.0.0~alpha9+dfsg-1.html [ALIOTH] https://anonscm.debian.org/gitweb/?p=pkg-php/composer.git Regards David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714118: php-composer -- Dependency Manager for PHP
There is a working package over on https://github.com/RobLoach/composer.deb And for reference, a relevant issue in the composer project: https://github.com/composer/composer/issues/1811 -- Met vriendelijke groet / Regards, Herman van Rink Initfour websolutions -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
On Wed, Mar 18, 2015 at 04:46:46PM +0200, Apollon Oikonomopoulos wrote: On 15:42 Wed 18 Mar , bertagaz wrote: Hi, Just tried in another Jessie environment, which is an almost fresh one, installed not so long ago and that didn't had a lot of changes. Sadly, I hit the same bug. :/ Then our only difference is Passenger. Can you give it a try? Just did, and you're right, the bug doesn't appear when running with passenger. Now that explains why. So anyone willing to use storeconfigs in Jessie will have to use puppetmaster-passenger. That's an acceptable workaround probably. bert. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot
On 18.03.2015 15:31, Michael Biebl wrote: Which version of initramfs-tools is installed? Version: 0.119 On 18.03.2015 15:33, Michael Biebl wrote: Does it help, if you create a file $ cat /etc/e2fsck.conf [options] broken_system_clock=1 Seems to fix the problem - after removing the option it's back again. But it doesn't explain why only the root partition (and not home) is affected. Besides, it is quite unlikely that the system clock of my notebook and desktop stop working properly around the same time. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780732: RM: gitolite -- ROM; superseded by gitolite3
Package: ftp.debian.org Severity: normal Hi! Please get gitolite removed from unstable (and thus in turn from jessie) because it is obsoleted by gitolite3 and not supported anymore by upstream. Thanks, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780715: Please relax build-depends on libssl-dev to = 1.0.1k so that backporting to Jessie is possible
On 18 March 2015 at 11:32, Thomas Goirand z...@debian.org wrote: I tried to relax the build-depends to libssl-dev = 1.0.1k (the version which is in Jessie), and all unit tests are passing correctly. I think the dependency is there because earlier versions of openssl in experimental were not compatible with the package as is; so the elevated dependency should no longer be required, I will look at relaxing it in a future upload. So, please lower the version of libssl-dev in the build-depends of python-cryptography so that backports to Jessie are possible. Eventually, if you have time, I'd appreciate an upload of python-cryptography 0.8 to the official Debian backports. As far as I understand, jessie-backports is not yet open (the suite exists on ftp-master but w-b etc. is not yet set up); I definitely intend to upload an official backport as soon as it is. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
On 15:42 Wed 18 Mar , bertagaz wrote: Hi, On Wed, Mar 18, 2015 at 02:26:59PM +0100, bertagaz wrote: Are you using the stomserver queue handling feature? We're not, and I'm tempted to give it a try. It does not fix this issue. I'll try to test in another environment, to be sure this bug is not related to any specifics bits of the current system. Just tried in another Jessie environment, which is an almost fresh one, installed not so long ago and that didn't had a lot of changes. Sadly, I hit the same bug. :/ Then our only difference is Passenger. Can you give it a try? Thanks, Apollon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780681: tengwar (tengwarscript) doesn't work
retitle 780681 please package tengwar fonts severity 780681 wishlist tag 780681 + wontfix thanks Hi everyone, first of all, Klaus, don't be picky and venomous yourself. Yes, the map file is present, but not included in the map file, which is read my pdftex during run time. They are located below /var/lib and are updated/recreated by the steps I told you. Because the fonts are not shipped. Thus, the map file should *NOT* be activated. No bug, perfectly correct. So the fonts are not correctly installed as I state in the bug report. Correct. Incorrect. For usage with latex you only need vf/tfm, no actual fonts are needed. Only when you want to convert to pdf from dvi or directly the fonts are needed. THere is no guarantee that all fonts are shipped, this is as *SUPPORT* package. http://at.mansbjorkman.net/parmaite.htm . About the reason not to include it I can only guess, but the copyright notice, is rather a cry for do not include me! [1]. Well, for me that license looks free and compatible with debian. I'd leave to decision about this to other people. Simple answer: Nobody has done it ... Nobody has repackaged them and uploaded to CTAN, that is all ... instead of moaning go forth, contact the authors, and upload to CTAN with their agreement. Nothing hinders you. After that the fonts will be also in TL. However, there is only two solutions for that. 1. Include the full fonts and register the map properly (Not only the .tfm and .vf files that are already included) 2. Or do not deliver any part of that fonts and state in README.Debian that and why that fonts are not available. Wrong again. tex is *NOT* about getting a pdf. TeX is producing dvi. There are convenience options to go directly to pdf, but this is not necessary. You could even tell pdftex to treat the fonts as *not*to*be*embedded. So, whatever you think: * this is *at*most* a wishlist bug: please package Tengwar fonts * it is a upupstream bug, that means, we as Debian have nothing to do with it, nor does TeX Live it self have anything to do with it. As long as the fonts are not uplaoded to CTAN, they will not end up in TeX Live. But the package can still be used ... You're right that installing some piece of software only partially is not a good idea. We'll discuss the legal part, else we'll completely remove the tengwar stuff from Debian. Hilmar, no need to be so cautious. You were right from the beginning. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot
Am 18.03.2015 um 13:31 schrieb Janis Hamme: Package: systemd Version: 215-12 Severity: normal Dear Maintainer, for some time now I noticed that fsck checks the root partition on every boot on both my jessie systems, desktop and notebook. As root file system I use ext4 for both of them. Does it help, if you create a file $ cat /etc/e2fsck.conf [options] broken_system_clock=1 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780728: systemd: fsck checks root partition and superblock is rewritten on every boot
Am 18.03.2015 um 13:31 schrieb Janis Hamme: Package: systemd Version: 215-12 Severity: normal Dear Maintainer, for some time now I noticed that fsck checks the root partition on every boot on both my jessie systems, desktop and notebook. As root file system I use ext4 for both of them. Which version of initramfs-tools is installed? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#780735: icedove: Segfault at startup, even in safe mode
Package: icedove Version: 36.0~b1-1 Severity: serious Justification: Segfault at startup After installing the last experimental version (36.0~b1-1), icedove segfault at startup, even in safe mode. Previous installed version (34.0~b1-2) worked correctly. Here is bellow a gdb backtrace of icedove in safe mode : vdanjean@eyak:~/.icedove/5idnx5md.default$ gdb /usr/lib/icedove/icedove-bin core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from /usr/lib/debug//usr/lib/icedove/icedove-bin...done. done. warning: core file may not match specified executable file. [New LWP 31559] [New LWP 31562] [New LWP 31563] [New LWP 31564] [New LWP 31565] [New LWP 31568] [New LWP 31561] [New LWP 31586] [New LWP 31590] [New LWP 31570] [New LWP 31566] [New LWP 31577] [New LWP 31573] [New LWP 31581] [New LWP 31571] [New LWP 31618] [New LWP 31587] [New LWP 31572] [New LWP 31567] [New LWP 31580] [New LWP 31576] [New LWP 31614] [New LWP 31574] [New LWP 31619] [New LWP 31569] [New LWP 31607] [New LWP 31600] [New LWP 31609] [New LWP 31582] [New LWP 31575] [New LWP 31585] [New LWP 31623] [New LWP 31616] [New LWP 31584] [New LWP 31588] [New LWP 31589] [New LWP 31608] [New LWP 31595] [New LWP 31591] [New LWP 31615] [New LWP 31578] [New LWP 31617] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. bt Core was generated by `icedove -safe-mode'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x77bce79b in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 37 ../nptl/sysdeps/unix/sysv/linux/pt-raise.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 0x77bce79b in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 #1 0x73205f19 in nsProfileLock::FatalSignalHandler (signo=11, info=0x7fffa430, context=0x7fffa300) at /build/icedove-T8nlns/icedove-36.0~b1/mozilla/profile/dirserviceprovider/nsProfileLock.cpp:180 #2 signal handler called #3 0x71dd69fe in memcpy (__len=1624, __src=0x0, __dest=0x7fffba5a6808) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 #4 implementationnsISupports*, nsISupports*, unsigned long, unsigned long (aValues=0x0, aCount=203, aStart=0, aElements=0x7fffba5a6808) at /build/icedove-T8nlns/icedove-36.0~b1/mozilla/xpcom/glue/nsTArray.h:525 #5 AssignRangensISupports* (aValues=0x0, aCount=203, aStart=0, this=0x7fffa960) at /build/icedove-T8nlns/icedove-36.0~b1/mozilla/xpcom/glue/nsTArray.h:1712 #6 nsTArray_ImplnsISupports*, nsTArrayInfallibleAllocator::AppendElementsnsISupports* (this=this@entry=0x7fffa960, aArray=aArray@entry=0x0, aArrayLen=aArrayLen@entry=203) at /build/icedove-T8nlns/icedove-36.0~b1/mozilla/xpcom/glue/nsTArray.h:1314 #7 0x71dd7026 in nsCOMArray_base::Adopt (this=0x7fffa960, aElements=0x0, aSize=203) at /build/icedove-T8nlns/icedove-36.0~b1/mozilla/xpcom/glue/nsCOMArray.cpp:316 #8 0x71d2ca61 in Adopt (aSize=optimized out, aElements=optimized out, this=0x7fffa960) at ../../../dist/include/nsCOMArray.h:434 #9 mozilla::mailnews::EncodedHeader (aHeader=..., aCharset=0x7fffca7319c8 ISO-8859-1) at /build/icedove-T8nlns/icedove-36.0~b1/mailnews/mime/src/MimeHeaderParser.cpp:95 #10 0x71bb4565 in nsMsgDBView::FetchAuthor (this=this@entry=0x7fffbd2ab000, aHdr=0x7fffbcf0d040, aSenderString=...) at /build/icedove-T8nlns/icedove-36.0~b1/mailnews/base/src/nsMsgDBView.cpp:406 #11 0x71bbebdf in nsMsgDBView::CellTextForColumn (this=this@entry=0x7fffbd2ab000, aRow=aRow@entry=573, aColumnName=aColumnName@entry=0x7fffd3404748 usenderCol, aValue=...) at /build/icedove-T8nlns/icedove-36.0~b1/mailnews/base/src/nsMsgDBView.cpp:1948 #12 0x71bd0041 in nsMsgGroupView::CellTextForColumn (this=0x7fffbd2ab000, aRow=573, aColumnName=0x7fffd3404748 usenderCol, aValue=...) at /build/icedove-T8nlns/icedove-36.0~b1/mailnews/base/src/nsMsgGroupView.cpp:882 #13 0x71bb3cbb in nsMsgDBView::GetCellText (this=0x7fffbd2ab000, aRow=573, aCol=0x7fffbab473c0, aValue=...) at /build/icedove-T8nlns/icedove-36.0~b1/mailnews/base/src/nsMsgDBView.cpp:1924 #14 0x72f7146a in nsTreeBodyFrame::PaintText
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
On 03/18/2015 05:04 PM, Thomas Lange wrote: Just for clarification. Do you mean log into the system during or after the installed does not work? Logging into the system while it is being installed. It worked with Wheezy, it stopped working with Jessie. On Wheezy, however, there is an error message shown which pops up just before logging is started to /tmp/fai/fai.log (which is why you will not find it in the log files but only if you look at the actual text console; it appears directly above the FAI logo with .nocolorlogo present in the NFS root). Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730438: UDD: bugs.cgi confused: lists bugs as affecting sid even if the package has been removed
On 25/11/13 at 12:36 -0500, James McCoy wrote: On Mon, Nov 25, 2013 at 03:13:51AM +0100, Andreas Beckmann wrote: UDD seems be be a bit confused about some bugs, too: query for closed bugs affecting sid (all bugs), and you will find several kfreebsd-8 bugs there, e.g. #725575 but kfreebsd-8 has been removed from jessie and sid ... Maybe the sid and jessie tags add to the confusion, but they are needed. Isn't this due to debian-installer-7.0-netboot-kfreebsd-* referencing kfreebsd-8 from their Built-Using field? This means the source for kfreebsd-8 is still part of sid: $ rmadison kfreebsd-8 kfreebsd-8 | 8.1+dfsg-8+squeeze3 | squeeze-security | source kfreebsd-8 | 8.1+dfsg-8+squeeze4 | squeeze | source kfreebsd-8 | 8.2-15~bpo60+1 | squeeze-backports | source kfreebsd-8 | 8.3-6 | wheezy| source Right. Most likely caused by bugs.cgi ignoring Extra-Source-Only: yes. The info is available in UDD though, so it could be exposed somehow. But I have no good idea about how to expose it. - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload
On 17/03/15 22:13, Michael Biebl wrote:
Am 17.03.2015 um 23:02 schrieb Robert Pumphrey:
I have identified a duff init.d script (one of our own that previously
worked in wheezy) that is at the root of this problem. I have removed
the script, rebooted and the I can now run systemctl daemon-reload
withough a seg fault.
This bug may just indicate that systemd poorly handles a bad init
script. Please let me know if you would like details of our broken
script, otherwise, I am happy for this to be closed.
If you can share this init script, this would be appreciated.
systemd certainly shouldn't die because of such a faulty init script and
I'm actually surprised it does, since the SysV support is basically done
in an external generator. So there must be something very fishy with the
generated unit.
As said, if you can attach the faulty init script, that would be great.
Michael
I have reproduced this on a clean install of Jessie running on a virtual
machine using 32bit i686 arch.
1. Install Debian from netinst
2. put the following into /etc/init.d/firewall
#!/bin/bash
### BEGIN INIT INFO
# Provides: iptables
# Required-Start:$network $remote_fs $syslog
# Required-Stop: $network $remote_fs $syslog
# Should-Start: iptables
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
### END INIT INFO
#
###
### Firewall rules
###
#
case $1 in
start)
echo start
;;
stop)
echo stop
;;
restart)
echo restart
;;
*)
echo Usage: /etc/init.d/firewall {start|stop|restart}
exit 1
;;
esac
3. chmod u+x /etc/init.d/firewall
4. update-rc.d firewall defaults
5. reboot
6. login as root
7. systemctl --system daemon-reload
then we see:
Message from syslogd@joule at Mar 18 14:10:40 ...
kernel:[ 27.526029] systemd[1]: segfault at b739cdac ip b739cdac sp
bf9af36c error 15
Failed to execute operation: Connection reset by peer
Also of note are the following entries in dmesg:
[1.075782] systemd[1]: Found ordering cycle on firewall.service/start
[1.075788] systemd[1]: Found dependency on firewall.service/start
[1.075793] systemd[1]: Breaking ordering cycle by deleting job
firewall.service/start
[1.075799] systemd[1]: Job firewall.service/start deleted to break
ordering cycle starting with firewall.service/start
Also note that the problem is not reproducible if the Provides: and
Should-Start: name match the init script name, so I guess mismatch in
the script name and header is at the root of the problem.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780738: save action from init script fails when ipv6 disabled
Package: iptables-persistent
Version: 1.0.3
Despite configuring a system not to use ipv6, the script
from iptables-persistent fails to complete properly and
save just the ipv4 rules. There are a couple problems:
(1) Tries to load ipv6 module load in ../plugins.d/25-ip6tables
while the script runs under set -e but some systems will
have e.g. install ip6table_filter /bin/true in modprobe.conf
and the modprobe will fail. save_rules() correctly tests for
/proc/net/ip6_tables_names to skip but won't even get that
far due to set -e as in:
$ sudo bash -x 25-ip6tables save || echo failed
+ set -e
+ rc=0
+ case $1 in
+ save_rules
+ /sbin/modprobe -q ip6table_filter
failed
(2) Even if we allow the modules to install, we still have issue
because of ipv6.disable=1 on /proc/cmdline, e.g.:
$ sudo bash -x 25-ip6tables save || echo failed
+ set -e
+ rc=0
+ case $1 in
+ save_rules
+ /sbin/modprobe -q ip6table_filter
+ '[' '!' -f /proc/net/ip6_tables_names ']'
+ '[' -x /sbin/ip6tables-save ']'
+ ip6tables-save
ip6tables-save v1.4.21: Cannot initialize: Address family not
supported by protocol
failed
(and for completeness, in case it's relevant:)
$ sudo debconf-show iptables-persistent
* iptables-persistent/autosave_v6: false
* iptables-persistent/autosave_v4: true
Since the running kernel lacking v6 means save/load failure is
not an error that iptables-persist needs to notify the user about
(he likely knows already that ipv6 is disabled completely in kernel),
I would suggest not even warning about this, and just skip, e.g.:
test -e /proc/sys/net/ipv6 || { true; exit; }
as first line of 25-ip6tables script (prior to set -e).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780664: [Pkg-puppet-devel] Bug#780664: puppetmaster fills up the database connection pool.
On 16:24 Wed 18 Mar , bertagaz wrote: Just did, and you're right, the bug doesn't appear when running with passenger. Now that explains why. Glad to hear that! So anyone willing to use storeconfigs in Jessie will have to use puppetmaster-passenger. That's an acceptable workaround probably. I agree. At this point, where upstream has deprecated the feature, I too think this is a reasonable (and now documented) workaround. Thanks, Apollon signature.asc Description: Digital signature
Bug#321168: lynx-cur: P within ULLI lacks blank lines upon rendering
tags 321168 + confirmed tags 321168 - moreinfo thanks Thank you Dan, I can confirm it now. I forward it. regards Denis Briand signature.asc Description: Digital signature
Bug#780550: apt-cacher-ng: Does not start when SPfilePatternEx specified in configuration
Control: 780550 +pending Hallo, * Carlos Maddela [Mon, Mar 16 2015, 11:37:03AM]: Package: apt-cacher-ng Version: 0.8.0-3 Severity: normal Tags: patch Dear Maintainer, While experimenting with this option, I found that specifying it results in the daemon's failure to start. Right... that was not properly tested. :-( Applied, see http://anonscm.debian.org/cgit/apt-cacher-ng/apt-cacher-ng.git/log/?h=upstream/sid Regards, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709335: Another workaround
It seems that using virt-manager client 1.0.0 causes the libvirtd process to behave normally (no high cpu and no more memory leak). You'll get this with Debian testing (Jessie) or Ubuntu 14. It is possible to download from here https://fedorahosted.org/released/virt-manager/virt-manager-1.0.1.tar.gz and get it going on wheezy, although it's a bit of a PITA. Forget about 1.1.0 as it requires newer gtk. As for this bug, I believe there is still something that needs addressing on the libvirtd server side, that allows the virt-manager client 1.0.0 to upset it . -- Chris Lewis Systems Administrator Inview Technology Ltd. T: +44 (0) 1606 812500 M: +44 (0) 7980 446907 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780739: debian-edu-config: debian-edu-pxeinstall fails to preseed ltsp-build-client
Package: debian-edu-config Version: 1.817 Severity: important Tags: patch During test to pxeinstall a thin-client-server I noticed, that ltsp-client-builder preseeding had not taken effect. This is due to a wrong type. This patch fixed it: diff --git a/sbin/debian-edu-pxeinstall b/sbin/debian-edu-pxeinstall index 02b440a..9dc358a 100755 --- a/sbin/debian-edu-pxeinstall +++ b/sbin/debian-edu-pxeinstall @@ -199,7 +199,7 @@ d-i mirror/ftp/proxystring $ftp_proxy #d-i passwd/root-password-crypted password passwordhash # Tell LTSP to not use the CDROM, but a HTTP mirror -d-i ltsp-client-builder/use_cdrom boolean false +d-i ltsp-client-builder/use_cdrom string false d-i ltsp-client-builder/build-client-opts string --mirror $mirrorurl --dist $dist # Tell PXE clients to fetch the correct time from the central NTP server Wolfgang signature.asc Description: Digital signature
Bug#780465: jessie-pu: package glibc/2.19-17
Hi, Niels Thykier ni...@thykier.net (2015-03-14): Thanks for fixing one of the remaining Jessie blockers. :) I have unblocked it from the RT side and am CC'ing KiBi for a d-i ack. Including the debdiff below for his convenience too. I'll get to it before the week end. Thanks for bearing with me. Mraw, KiBi. signature.asc Description: Digital signature
Bug#745446: openvpn-auth-radius: Add IPv6 support
Hello! Here are patches to add IPv6 support to openvpn-auth-radius: - support for Framed-IPv6-Route - support optional gateway parameter - support for announcing routes to bird - support for Framed-IPv6-Address These patches cannot be applied to the current unstable version. Can you please provide updated patches, that can be applied cleanly to the current unstable version and test them before? In addition the optional gateway parameter patch seems to contain functions, which are also within the patch for Bug#773280. Can you please validate, if your code is now obsolete? (File dev.txt) Greetings Torge signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#780737: [php-maint] Bug#780737: php5-fpm: Call to undefined function apache_request_headers()
forwarded 780373 https://bugs.php.net/bug.php?id=62596 thanks The right upstream bug is https://bugs.php.net/bug.php?id=62596 ( I closed the duplicate one to avoid confusion). Notice the PR wasn't accepted... So I don't see us taking this any time soon. Kaplan On Wed, Mar 18, 2015 at 5:11 PM, Emmanuel Schmidbauer eschmidba...@voipxswitch.com wrote: Package: php5-fpm Version: 5.4.36-0+deb7u3 Severity: important Tags: patch Dear Maintainer, Please see php bug https://bugs.php.net/bug.php?id=67337thanks=6 There is a patch that should be pushed to the debian package to address this bug. The link to the patch is on that page. -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 php5-fpm depends on: ii dpkg 1.16.15 ii libbz2-1.01.0.6-4 ii libc6 2.13-38+deb7u8 ii libcomerr21.42.5-1.1+deb7u1 ii libdb5.1 5.1.29-5 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 ii libk5crypto3 1.10.1+dfsg-5+deb7u3 ii libkrb5-3 1.10.1+dfsg-5+deb7u3 ii libmagic1 5.11-2+deb7u7 ii libonig2 5.9.1-1 ii libpcre3 1:8.30-5 ii libqdbm14 1.8.78-2 ii libssl1.0.0 1.0.1e-2+deb7u14 ii libxml2 2.8.0+dfsg1-7+wheezy3 ii mime-support 3.52-1+deb7u1 ii php5-common 5.4.36-0+deb7u3 ii tzdata2015a-0wheezy1 ii ucf 3.0025+nmu3 ii zlib1g1:1.2.7.dfsg-13 php5-fpm recommends no packages. Versions of packages php5-fpm suggests: pn php-pear none -- Configuration Files: /etc/php5/fpm/php-fpm.conf changed [not included] /etc/php5/fpm/pool.d/www.conf [Errno 2] No such file or directory: u'/etc/php5/fpm/pool.d/www.conf' -- no debconf information ___ pkg-php-maint mailing list pkg-php-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint
Bug#766043: Bug#766043: A patch from Red Hat needed for FreeIPA
Tags: wontfix No feedback. Seems patch is not needed anymore signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#173851: lynx: asks me about cookie again when wanting to see source
Yes I have tried with google. I hit \ to see source and I hit \ again to come back to the google main page. It works fine here, he doesn't ask me again about cookie. Is it the good way to reproduce it? regards Denis Briand signature.asc Description: Digital signature
Bug#772598: steam: install fails if debconf selections are already set
Package: steam Followup-For: Bug #772598 hi, today i try to re-install steam but i have the same error. I try install with dpkg with the package from debian website, apt and synaptic. Always the same thing even i try to use the patch. # synaptic download steam:i386 # mkdir steam_1.0.0.49-1_i386.patch/ # dpkg-deb --extract steam_1.0.0.49-1_i386.deb steam_1.0.0.49-1_i386.patch/ # dpkg-deb --control steam_1.0.0.49-1_i386.deb steam_1.0.0.49-1_i386.patch/DEBIAN (patch files) # nano steam_1.0.0.49-1_i386.patch/DEBIAN/preinst # nano steam_1.0.0.49-1_i386.patch/DEBIAN/postrm # dpkg-deb --build steam_1.0.0.49-1_i386.patch/ # dpkg -i steam_1.0.0.49-1_i386.patch.deb Any ideas, i did something wrong ? ( it's my first re-packaging ) -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages steam depends on: ii debconf [debconf-2.0] 1.5.55 ii gnome-terminal 3.14.1-1 ii libc6 2.19-15 ii libgl1-mesa-dri10.3.2-1 ii libgl1-mesa-glx10.3.2-1 ii libstdc++6 4.9.2-10 ii libx11-6 2:1.6.2-3 ii libxau61:1.0.8-1 ii libxcb11.10-3+b1 ii libxdmcp6 1:1.1.1-1+b1 ii multiarch-support 2.19-15 ii xterm 312-2 Versions of packages steam recommends: ii zenity 3.14.0-1 steam suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#654924: Darlehen und Investitionen
Wir bieten sowohl kurz-und langfristige Darlehen. Wir bieten persönliche Darlehen, Schuldenkonsolidierung Darlehen, Risikokapital, Business-Darlehen, Studenten Darlehen, Darlehen, Immobilien-Darlehen, etc. Für weitere Anfragen und Informationen zur Bewerbung und für ein Darlehen zu qualifizieren, mailen Sie an: af@rogers.com Grüße, Garrett McCoy Kreditsachbearbeiter
Bug#595817: pam-ssh-agen-auth deb package
Hi Chrysn, On Thu, 24 Apr 2014 16:04:52 +0200 chrysn chr...@fsfe.org wrote: hello peter, I am planning to try to build a deb file using your git repo, reading through your post I have cloned the repository. the information there is indeed slightly outdated; the new status is: * all my patches were applied, the chrysn/patches branch went away * upstream has released a version with that, there is an appropriate pristine-tar branch * the current debian branch works, and i'd take this bug as rfp and package as maintainer (which i'd be then try to have sponsored as is) if i can get third party comments on the security side of the implementation. in the meantime, to try it out, you can do $ git clone git://prometheus.amsuess.com/pam-ssh-agent-auth -b debian $ cd pam-ssh-agent-auth $ git branch --track pristine-tar origin/pristine-tar $ git-buildpackage to build your packages out of it and test it. I would happily sponsor your package. The packaging part looks good, while I will review it once again before actually uploading it. :-) I CC-d pam maintainers if they would like to comment on this package. Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted
On Wed, 18 Mar 2015 15:20:05 +0100, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de said: While preparing to migrate our installed FAI systems to Jessie, we stumbled into the problem that it was no longer possible to log on to systems being installed via SSH: Just for clarification. Do you mean log into the system during or after the installed does not work? -- regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
