Bug#738610: maven: Can't run mvn due to some bad java library dependency
Package: maven Version: 3.0.5-1 Severity: important Dear Maintainer, After safe-upgrade, running mvn results in the following: lior@meme:/tmp$ mvn --- constituent[0]: file:/usr/share/maven/lib/plexus-cipher.jar constituent[1]: file:/usr/share/maven/lib/maven-artifact-3.x.jar constituent[2]: file:/usr/share/maven/lib/wagon-provider-api.jar constituent[3]: file:/usr/share/maven/lib/plexus-component-annotations.jar constituent[4]: file:/usr/share/maven/lib/maven-settings-3.x.jar constituent[5]: file:/usr/share/maven/lib/maven-settings-builder-3.x.jar constituent[6]: file:/usr/share/maven/lib/plexus-utils.jar constituent[7]: file:/usr/share/maven/lib/commons-logging.jar constituent[8]: file:/usr/share/maven/lib/aether-util.jar constituent[9]: file:/usr/share/maven/lib/plexus-interpolation.jar constituent[10]: file:/usr/share/maven/lib/aether-connector-wagon.jar constituent[11]: file:/usr/share/maven/lib/sisu-inject-plexus.jar constituent[12]: file:/usr/share/maven/lib/wagon-file.jar constituent[13]: file:/usr/share/maven/lib/plexus-sec-dispatcher.jar constituent[14]: file:/usr/share/maven/lib/maven-plugin-api-3.x.jar constituent[15]: file:/usr/share/maven/lib/sisu-guice.jar constituent[16]: file:/usr/share/maven/lib/maven-repository-metadata-3.x.jar constituent[17]: file:/usr/share/maven/lib/maven-model-3.x.jar constituent[18]: file:/usr/share/maven/lib/maven-embedder-3.x.jar constituent[19]: file:/usr/share/maven/lib/maven-model-builder-3.x.jar constituent[20]: file:/usr/share/maven/lib/sisu-inject-bean.jar constituent[21]: file:/usr/share/maven/lib/commons-cli.jar constituent[22]: file:/usr/share/maven/lib/guava.jar constituent[23]: file:/usr/share/maven/lib/commons-codec.jar constituent[24]: file:/usr/share/maven/lib/aether-impl.jar constituent[25]: file:/usr/share/maven/lib/aether-api.jar constituent[26]: file:/usr/share/maven/lib/maven-core-3.x.jar constituent[27]: file:/usr/share/maven/lib/wagon-http-shaded.jar constituent[28]: file:/usr/share/maven/lib/commons-httpclient.jar constituent[29]: file:/usr/share/maven/lib/maven-aether-provider-3.x.jar constituent[30]: file:/usr/share/maven/lib/aether-spi.jar constituent[31]: file:/usr/share/maven/lib/maven-compat-3.x.jar --- Exception in thread main com.google.common.util.concurrent.ExecutionError: java.lang.VerifyError: class com.google.inject.internal.cglib.core.$DebuggingClassWriter overrides final method visit.(IILjava/lang/String;Ljava/lang/String;Ljava/lang/String;[Ljava/lang/String;)V at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2197) at com.google.common.cache.LocalCache.get(LocalCache.java:3932) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3936) at com.google.common.cache.LocalCache$LocalLoadingCache.get(LocalCache.java:4806) at com.google.common.cache.LocalCache$LocalLoadingCache.getUnchecked(LocalCache.java:4812) at com.google.inject.internal.FailableCache.get(FailableCache.java:48) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:50) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:139) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:532) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:180) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at com.google.inject.Guice.createInjector(Guice.java:62) at org.codehaus.plexus.DefaultPlexusContainer.addPlexusInjector(DefaultPlexusContainer.java:470) at org.codehaus.plexus.DefaultPlexusContainer.init(DefaultPlexusContainer.java:196) at org.codehaus.plexus.DefaultPlexusContainer.init(DefaultPlexusContainer.java:160) at org.apache.maven.cli.MavenCli.container(MavenCli.java:375) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:191) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at
Bug#727708: call for votes on default Linux init system for jessie
* Bdale Garbee (bd...@gag.com) [140208 20:50]: I expect that Debian can and should continue to support multiple init systems for the foreseeable future. I also believe that Debian can and should take an active role working with upstream projects on software that is important to us, such as init system projects. [...] - - - start ballot - - - We exercise our power to decide in cases of overlapping jurisdiction (6.1.2) by asserting that the default init system for Linux architectures in jessie should be Dsystemd Uupstart Oopenrc Vsysvinit (no change) Frequires further discussion Should the project pass a General Resolution before the release of jessie asserting a position statement about issues of the day on init systems, that position replaces the outcome of this vote and is adopted by the Technical Committee as its own decision. - - - end ballot - - - I'm unhappy with this resolution; in fact, after the discussions I don't think it would be good to decide on an init system without explicitly stating that users should be able to continue to make different decisions on their own systems (and in hindsight it was an error that I voted FD on the previous call for votes to allow textual optimizations). This is especially true for systemd (I consider the probability of people to depend soley on upstart to be lower) - after some long thinking about this I came to the conclusion that I cannot vote systemd above further discussion in the current scenario. (Also I hope but don't expect that the discussions we had on our list are enough for maintainers to not try to force a specific init system on our users.) Thus voting U, F, D, O, V. Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Init system GR override call for votes
* Ian Jackson (ijack...@chiark.greenend.org.uk) [140209 20:57]: I hereby call for votes on the following resolution If the project passes (before the release of jessie) by a General Resolution, a position statement about issues of the day, on the subject of init systems, the views expressed in that position statement entirely replace the substance of any TC resolution (past or future) on the same topic; the TC hereby adopts any such position statement as its own decision. Such a position statement could, for example, use these words: The Project requests (as a position statement under s4.1.5 of the Constitution) that the TC reconsider, and requests that the TC would instead decide as follows: I think this is already covered by Bdales text, so unless there are reasons I missed I intend to vote no here (i.e. FD first). Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Init system coupling call for votes
* Ian Jackson (ijack...@chiark.greenend.org.uk) [140209 20:51]: I hereby call for votes on the following resolution: The init system decision is limited to selecting a default initsystem for jessie. We expect that Debian will continue to support multiple init systems for the foreseeable future; we continue to welcome contributions of support for all init systems. Therefore, for jessie and later releases, we exercise our power to set technical policy (Constitution 6.1.1): Software outside of an init system's implementation may not require a specific init system to be pid 1, although degraded operation is tolerable. Maintainers are encouraged to accept technically sound patches to enable improved interoperation with various init systems. Voting in favour (i.e. Resolution, FD). Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738571: FTBFS on mips(el)
Hi Jurica, while the bug is against the ray package I realised that the patch is against mpi-defaults. Do you think we should reassign the bug to this package - otherwise the maintainers might not notice the patch. Kind regards Andreas. On Mon, Feb 10, 2014 at 07:29:49PM +, Jurica Stanojkovic wrote: Tags: patch This is an openmpi issue. Currently mpi-defaults for mips and mipsel is built with mpich. Instead of a package mpich, openmpi should be used for building of mpi-defaults. Until recently openmpi for mips and mipsel was not available. I have attached a patch that contains debian changes of mpi-default package. Thanks! Jurica diff -uNr mpi-defaults.orig/debian/control mpi-defaults/debian/control --- mpi-defaults.orig/debian/control 2013-10-26 13:33:29.0 + +++ mpi-defaults/debian/control 2014-02-10 16:44:45.0 + @@ -5,10 +5,10 @@ Uploaders: Adam C. Powell, IV hazel...@debian.org, Manuel Prinz man...@debian.org Standards-Version: 3.9.2 Build-Depends: debhelper, - libopenmpi-dev (= 1.4.3-2.1) [alpha armel armhf i386 amd64 lpia ia64 powerpc sparc kfreebsd-i386 kfreebsd-amd64 hurd-i386], - openmpi-bin (= 1.4.3-2.1) [alpha armel armhf i386 amd64 lpia ia64 powerpc sparc kfreebsd-i386 kfreebsd-amd64 hurd-i386], - libmpich-dev [!alpha !armel !armhf !i386 !amd64 !lpia !ia64 !powerpc !sparc !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], - mpich [!alpha !armel !armhf !i386 !amd64 !lpia !ia64 !powerpc !sparc !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] + libopenmpi-dev (= 1.4.3-2.1) [alpha armel armhf i386 amd64 lpia ia64 powerpc sparc kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips mipsel], + openmpi-bin (= 1.4.3-2.1) [alpha armel armhf i386 amd64 lpia ia64 powerpc sparc kfreebsd-i386 kfreebsd-amd64 hurd-i386 mips mipsel], + libmpich-dev [!alpha !armel !armhf !i386 !amd64 !lpia !ia64 !powerpc !sparc !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips !mipsel], + mpich [!alpha !armel !armhf !i386 !amd64 !lpia !ia64 !powerpc !sparc !kfreebsd-i386 !kfreebsd-amd64 !hurd-i386 !mips !mipsel] Vcs-Browser: http://anonscm.debian.org/git/?p=debian-science/packages/mpi-defaults.git Vcs-Git: git://anonscm.debian.org/debian-science/packages/mpi-defaults.git ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700630: ITP: gitorious -- Git based tool for collaborating on distributed open source projects
Hi Hannes, On Mo 10 Feb 2014 22:20:40 CET, Hannes von Haugwitz wrote: Hi, is there any progress in packaging gitorious? Best regards Hannes unfortunately, there is not much progress, yet. I am currently quite busy with packaging the MATE desktop which has priority to me. If you want to join in the packaging, feel free to meet up with me on IRC (nick: sunweaver on irc.debian.org). Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpVsBp1x0wB_.pgp Description: Digitale PGP-Signatur
Bug#738611: acpid: Mic mute button not recognized on Thinkpad again
Package: acpid Version: 1:2.0.21-1 Severity: normal Dear maintainers, udev remapped KEY_MICMUTE to KEY_F20 because it is out of range for X.org. Now acpi_listen won't return button/micmute event. kacpimon gets 190 (KEY_F20) instead. http://cgit.freedesktop.org/systemd/systemd/commit/keymaps?id=1563c0c35a8005f5b71f04abe32c95d849efb420 Lingzhu Xiang -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738407: ulogd2: FTBFS: dh_install: ulogd2-dbi missing files (debian/tmp/usr/lib/*/ulogd/ulogd_output_DBI.so), aborting
Control: tags -1 +patch +pending Hi, Specifying dbi.so directory fixes this FTBFS bug, see attached diff. I'll upload it to 7-delayed queue, if you don't want it, please tell me. # git repo doesn't have master branch, so I'm not sure how to commit it. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -Nru ulogd2-2.0.3/debian/changelog ulogd2-2.0.3/debian/changelog --- ulogd2-2.0.3/debian/changelog 2013-12-04 07:51:31.0 +0900 +++ ulogd2-2.0.3/debian/changelog 2014-02-11 13:36:16.0 +0900 @@ -1,3 +1,11 @@ +ulogd2 (2.0.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules +- specify dbi.so location with --with-dbi-lib option (Closes: #738407) + + -- Hideki Yamane henr...@debian.org Tue, 11 Feb 2014 13:36:15 +0900 + ulogd2 (2.0.3-1) unstable; urgency=low * New upstream release. diff -Nru ulogd2-2.0.3/debian/rules ulogd2-2.0.3/debian/rules --- ulogd2-2.0.3/debian/rules 2013-12-03 22:41:24.0 +0900 +++ ulogd2-2.0.3/debian/rules 2014-02-11 13:35:38.0 +0900 @@ -10,6 +10,8 @@ # Activate full hardening build flags export DEB_BUILD_MAINT_OPTIONS := hardening=+pie,+bindnow +DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) + PACKAGE = $(firstword $(shell dh_listpackages)) TMP = $(CURDIR)/debian/$(PACKAGE) @@ -17,7 +19,8 @@ dh $@ --with autotools-dev,systemd override_dh_auto_configure: - dh_auto_configure -- --disable-silent-rules --with-pgsql --with-mysql --with-dbi + dh_auto_configure -- --disable-silent-rules --with-pgsql --with-mysql \ + --with-dbi --with-dbi-lib=/usr/lib/$(DEB_HOST_MULTIARCH) override_dh_auto_build: dh_auto_build
Bug#736231: Ping... (NMU in two weeks)
Hi Laurent, as I haven't heard of you about my bug filing of #736231, herewith you revceive a ping about the issue. Please note, that I will NMU the patches attached to my bug report in about two weeks. I'd be happy to get those upstream patches into Debian without NMU'ing the package. light+love, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgp6yHbTdbHXl.pgp Description: Digitale PGP-Signatur
Bug#727708: Init system coupling call for votes
Hi, Andreas Barth a...@ayous.org writes: I hereby call for votes on the following resolution: The init system decision is limited to selecting a default initsystem for jessie. We expect that Debian will continue to support multiple init systems for the foreseeable future; we continue to welcome contributions of support for all init systems. Therefore, for jessie and later releases, we exercise our power to set technical policy (Constitution 6.1.1): Software outside of an init system's implementation may not require a specific init system to be pid 1, although degraded operation is tolerable. Maintainers are encouraged to accept technically sound patches to enable improved interoperation with various init systems. Voting in favour (i.e. Resolution, FD). I think it is a very bad idea to vote on a resolution proposed in anger, pretty much regardless of the contents. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738612: gnome-session: Suspends at login when lid is closed with external monitor
Package: gnome-session Version: 3.8.4-3 Severity: normal Dear Maintainer, I have a newly installed laptop with systemd as pid 1, and a fresh jessie install. Most of the time, the laptop is lid closed, with external keyboard, mouse and monitor plugged in. When booting, gdm shows up for login. After choosing the user, typing the password, and validating, the gnome session opens and... the laptop goes into suspend. I need to open the lid, unsuspend it, and then reclose the lid so that the session can be used with the external monitor as the sole output. Mike -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 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-session depends on: ii gnome-session-bin 3.8.4-3 ii gnome-session-common 3.8.4-3 ii gnome-settings-daemon 3.8.5-2 ii gnome-shell3.8.4-5 gnome-session recommends no packages. Versions of packages gnome-session suggests: ii desktop-base 7.0.3 ii gnome-keyring 3.8.2-2 ii gnome-user-guide 3.8.2-1 -- 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#738613: needs co-ordination with users
Package: libasio-dev Severity: serious Version: 1.10-1 This package is a build dependency for other packages and they are all likely to break with this new version Lets get a list of impacted packages and co-ordinate with maintainers The only package I know of personally is resiprocate -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#601310: gdm3: login manager does not support rotate (pivot)
Package: gdm3 Version: 3.8.4-6 Followup-For: Bug #601310 I don't know if 2.30 actually had something to configure this, but I couldn't find any way to configure screen orientation on the login manager, besides editing configuration files. (Seriously?) Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738578: omake: unbound variable: public.OMakeVersion
Le 2014-02-11 07:43, Stéphane Glondu a écrit : Hello, Thanks for your answer so quick, What was your previously installed version? Can you send a (minimal) testcase? This is the update log : $ grep omake /var/log/aptitude [MIS A JOUR] omake:amd64 0.9.8.5-3-8 - 0.9.8.5-3-9 Here is a way to reproduce the problem : $ mkdir test cd test $ omake --install *** omake: creating OMakeroot *** omake: creating OMakefile *** omake: project files OMakefile and OMakeroot have been installed *** omake: you should edit these files before continuing $ omake *** omake: reading OMakefiles *** omake error: File /usr/lib/omake/build/C.om: line 4, characters 2-32 unbound variable: public.OMakeVersion The file « C.om » starts with : $ head /usr/lib/omake/build/C.om # # Required version of omake # OMakeVersion(0.9.8.5, 0.9.8.5) # Building C files. # # Copyright (C) 2003-2007 Jason Hickey and Mojave Group # Regards, -- Sébastien Dailly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738440: cups: new version contains Ubuntu Bug #1019662
Le lundi, 10 février 2014, 23.34:23 Till Kamppeter a écrit :
I have fixed the problem upstream (BZR rev. 7159) now. I do not use
PATH+MAX any more for strings which are used to hold a command line.
Command lines have 65535 bytes now.
Please test and tell whether it solves the problem. If so, I will
release a new cups-filters version.
At least it doesn't cause obvious regressions for me.
Till: if you release a new version, can you include your fix for the
upstart job?
Randy: can you recompile cups-filters on your platform with the attached
patch and confirm that it works?
Cheers, OdyXDescription: foomatic-rip: Do not use PATH_MAX for the length of static
strings which are supposed to hold a command line. Use our own
CMDLINE_MAX constant to set them to a length of 65535 bytes
Author: Till Kamppeter till.kampet...@gmail.com
Origin: upstream
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1019662
Bug-Debian: https://bugs.debian.org/738440
--- a/filter/foomatic-rip/foomaticrip.h
+++ b/filter/foomatic-rip/foomaticrip.h
@@ -76,8 +76,9 @@
extern int spooler;
#ifndef PATH_MAX
-#define PATH_MAX 65536
+#define PATH_MAX 4096
#endif
+#define CMDLINE_MAX 65536
typedef struct {
char printer[256];
--- a/filter/foomatic-rip/foomaticrip.c
+++ b/filter/foomatic-rip/foomaticrip.c
@@ -571,7 +571,7 @@
if (!ppd_supports_pdf())
{
-char pdf2ps_cmd[PATH_MAX];
+char pdf2ps_cmd[CMDLINE_MAX];
FILE *out, *in;
int renderer_pid;
char tmpfilename[PATH_MAX] = ;
@@ -617,12 +617,12 @@
We give priority to Ghostscript here and use Poppler if
Ghostscript is not available. */
if (spooler == SPOOLER_CUPS)
- snprintf(pdf2ps_cmd, PATH_MAX,
+ snprintf(pdf2ps_cmd, CMDLINE_MAX,
pdftops '%s' '%s' '%s' '%s' '%s' '%s',
job-id, job-user, job-title, 1, job-optstr-data,
filename);
else
- snprintf(pdf2ps_cmd, PATH_MAX,
+ snprintf(pdf2ps_cmd, CMDLINE_MAX,
gs -q -sstdout=%%stderr -sDEVICE=ps2write -sOutputFile=-
-dBATCH -dNOPAUSE -dPARANOIDSAFER -dNOINTERPOLATE %s 2/dev/null ||
pdftops -level2 -origpagesizes %s - 2/dev/null,
--- a/filter/foomatic-rip/pdf.c
+++ b/filter/foomatic-rip/pdf.c
@@ -41,12 +41,12 @@
static int pdf_count_pages(const char *filename)
{
-char gscommand[4095];
+char gscommand[CMDLINE_MAX];
char output[31] = ;
int pagecount;
size_t bytes;
-snprintf(gscommand, 4095, %s -dNODISPLAY -q -c
+snprintf(gscommand, CMDLINE_MAX, %s -dNODISPLAY -q -c
'/pdffile (%s) (r) file def pdfdict begin pdffile pdfopen begin
(PageCount: ) print pdfpagecount == flush currentdict pdfclose
end end quit',
@@ -109,7 +109,7 @@
int first,
int last)
{
-char gscommand[4095];
+char gscommand[CMDLINE_MAX];
char filename_arg[PATH_MAX], first_arg[50], last_arg[50];
int fd;
@@ -127,7 +127,7 @@
else
first_arg[0] = '\0';
-snprintf(gscommand, 4095, %s -q -dNOPAUSE -dBATCH -dPARANOIDSAFER -dNOINTERPOLATE
+snprintf(gscommand, CMDLINE_MAX, %s -q -dNOPAUSE -dBATCH -dPARANOIDSAFER -dNOINTERPOLATE
-sDEVICE=pdfwrite %s %s %s %s,
gspath, filename_arg, first_arg, last_arg, pdffilename);
--- a/filter/foomatic-rip/renderer.c
+++ b/filter/foomatic-rip/renderer.c
@@ -37,11 +37,12 @@
*/
int test_gs_output_redirection()
{
-char gstestcommand[PATH_MAX];
+char gstestcommand[CMDLINE_MAX];
char output[10] = ;
int bytes;
-snprintf(gstestcommand, PATH_MAX, %s -dQUIET -dPARANOIDSAFER -dNOPAUSE
+snprintf(gstestcommand, CMDLINE_MAX,
+ %s -dQUIET -dPARANOIDSAFER -dNOPAUSE
-dBATCH -dNOMEDIAATTRS -sDEVICE=ps2write -sstdout=%%stderr
-sOutputFile=/dev/null -c '(hello\n) print flush' 21, gspath);
Bug#727708: call for votes on default Linux init system for jessie
On Sat, Feb 08, 2014 at 12:56:56PM -0700, Bdale Garbee wrote:
Bdale Garbee bd...@gag.com writes:
- - - start ballot - - -
We exercise our power to decide in cases of overlapping jurisdiction
(6.1.2) by asserting that the default init system for Linux
architectures in jessie should be
Dsystemd
Uupstart
Oopenrc
Vsysvinit (no change)
Frequires further discussion
Should the project pass a General Resolution before the release of
jessie asserting a position statement about issues of the day on
init systems, that position replaces the outcome of this vote and is
adopted by the Technical Committee as its own decision.
- - - end ballot - - -
I vote D U O V F.
On Sat, Feb 08, 2014 at 12:16:51PM -0800, Russ Allbery wrote:
I vote:
D U O V F
On Sat, Feb 08, 2014 at 02:18:39PM -0800, Steve Langasek wrote:
I vote F U D O V
On Sat, Feb 08, 2014 at 02:51:13PM -0800, Don Armstrong wrote:
I vote D U O V F.
On Sat, Feb 08, 2014 at 02:57:52PM -0800, Keith Packard wrote:
I vote:
1. D
2. U
3. O
4. V
5. F
On Sun, Feb 09, 2014 at 01:04:31PM +, Colin Watson wrote:
I vote UDOFV.
On Sun, Feb 09, 2014 at 07:15:58PM +, Ian Jackson wrote:
I vote F, V, O, U, D.
On Tue, Feb 11, 2014 at 09:07:11AM +0100, Andreas Barth wrote:
Thus voting U, F, D, O, V.
So that's all the votes in, by my count. Summary is:
4x D U O V F (bdale, russ, keith, don)
F U D O V (steve)
U D O F V (colin)
F V O U D (ian)
U F D O V (andi)
Pairwise defeats are:
D = U (4:4)
U and D O and V
(7:1) (ian against)
O V (7:1) (ian against)
U F (6:2) (steve, ian against)
D F (5:3) (steve, ian, andi against)
O F (5:3) (steve, ian, andi against)
V = F (4:4)
A.6.2: Quorum is 2 (6.3.1), all options meet quorum.
A.6.3: Option V does not strictly defeat default option F, so is eliminated
A.6.5: Transitive defeats are:
D : O, F (directly)
U : O, F (directly)
O : F (directly)
F :
A.6.6: Schwartz set is {D,U}
A.6.8: There are no defeats in the Schwartz set, so the elector with
the casting vote chooses which of these options wins.
Per 6.3.2, the casting vote is held by the Chairman, who is currently
Bdale.
Per 6.3.1, the voting period expires either Feb 15th, or when the outcome
is no longer in doubt. Not clear to me if that's now, or only after Bdale
specifies a casting vote. Per 7.3, if there's any dispute about that, the
secretary adjudicates that dispute.
Cheers,
aj
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701659: testing again
travis-ci appears to have libasio-dev 1.4.8 now With commit r10959 in reSIProcate, I've enabled clang builds on travis-ci again, it should start building soon and then we can see if this issue is resolved -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738591: lintian: Add checker for timestamped gzip files
On 11/02/14 06:54, Niels Thykier wrote: On 2014-02-11 01:20, Jakub Wilk wrote: * Tomasz Buchert tomasz.buch...@inria.fr, 2014-02-11, 00:56: There is an ongoing project to build reproducible deps (see https://wiki.debian.org/ReproducibleBuilds). One of tasks is to update lintian to emit a tag on gzips that contain timestamps. I've written a simple checker that does exactly that and emits package-contains-timestamped-gzip. The patch is attached. We check for a very similar thing already in files.pm (the gzip-file-is-not-multi-arch-same-safe tag). Perhaps it would be better to reuse that code. Ok, no problem. Should I put the test inside files.pm then? I wanted to dedicate a whole check for prospective reproduciblity checks. Niels, do you remember why we read timestamp with sysread() and unpack() instead of using file_info? I have a vague recollection that we did it on purpose, but can't remember the details. Yes, file(1) cannot reliably detect gzip files[1] and I guess I figured it was easier to do it with sysread than have file-info-helper replace even more of file(1) job. That's funny! Not a problem, my prototype was written that way, but then I found file_info and decided to do it the easy way. +Severity: normal It think it should be at most wishlist, perhaps even pedantic. Let's make it pedantic, but hopefully one day it will be normal. ~Niels [1] Apparently based on the timestamp it randomly decides to misreport it as a different file type. At least that is my conclusion based on the test failures we used to have. Cheers, Tomasz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737634: dpkg-dev: please reject native/non-native version when building native/non-native source packages
Sigh. On Wed, Feb 05, 2014 at 12:59:23PM +, Neil Williams wrote: Using packages to support upstream development is a common problem and this is exactly where things get awkward. No, it is not a *problem*; it is a *method* of doing things. It is not your place (nor mine) to question another person's methods of doing things; especially not if said methods are done outside of Debian, as is here the case. Enforcing Debian Policy in the tools (i.e., not allowing to do things contrary to debian policy, even if that's wanted) is a *bad* idea, in all cases. [...] Also, using git-buildpackage is difficult. The build is done by sbuild, which does not call git-buildpackage. Not true. There are options to use debuild or pdebuild or dpkg-buildpackage in-place. e.g. I use: [DEFAULT] #builder = git-pbuilder builder = debuild cleaner = fakeroot debian/rules clean pristine-tar = True [git-buildpackage] export-dir = ../build-area/ tarball-dir = ../tarballs/ Even if so, this increases the complexity of the system, and requires people to learn yet another tool to Just Do what was previously possible with no extra fluff. It's okay for a tool (like dpkg) to warn if something doesn't look right. It's not okay for a tool (like dpkg) to pretend to be smarter than the person operating said tool. -- This end should point toward the ground if you want to go to space. If it starts pointing toward space you are having a bad problem and you will not go to space today. -- http://xkcd.com/1133/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738613: Fedora / EPEL
reSIProcate is also targetting Fedora and EPEL6. They are both carrying asio 1.4.x now We may need to contact the Fedora maintainer of asio-devel about whether he will include 1.10 in Fedora 21 and EPEL7, they will probably be released about the same time as jessie (or just a little bit before) This would make it much easier for users and upstreams to standardize on asio v1.10 if it is consistent on all Linux platforms -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738614: wine-alsa: wine alsa-preloader amd64 SamBroadcaster michrophone problem
Package: wine-alsa Version: alsa Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737634: dpkg-dev: please reject native/non-native version when building native/non-native source packages
On Mon, 10 Feb 2014 22:13:45 +0100 Wouter Verhelst wou...@debian.org wrote: Sigh. On Wed, Feb 05, 2014 at 12:59:23PM +, Neil Williams wrote: Using packages to support upstream development is a common problem /common problem/common source of problems/ and this is exactly where things get awkward. No, it is not a *problem*; it is a *method* of doing things. ... one which I've used consistently for more years than I've been a DD and had frequent problems with various assumptions in various tools and in more distributions than just Debian and its derivatives. Hopefully the clarification will show that I'm not questioning the methods of anyone (other than possibly my own). It is not your place (nor mine) to question another person's methods of doing things; especially not if said methods are done outside of Debian, as is here the case. ... and in my ongoing work. If using distribution tools for upstream development was easy, we might not have had people developing tools like pypi, ruby gems, CPAN or a whole range of other non-distribution distributive tools. This isn't just a Debian problem. (Indeed fixing it in Debian isn't going to fix the problems because upstreams will rarely fixate on a single distribution across the entire team - for entirely sane reasons.) It is right for upstream to want to deploy to FHS compliant paths and use dependencies from the main distribution system etc. None of the distribution tools for any of the distributions actually make it easy to then develop within those paths without either rebuilding unreleased upstream packages or copying files into privileged paths. Both of these routes need sudo access which just makes things harder again. Why must every developer have sudo access on the development box? That is exactly why pypi and buildout have got so much traction. It annoys me that I have to use such methods for upstream work because dpkg-dev is too constrained by rules which *only* relate to official builds. Doing a quick native build of a non-native package for use and distribution within a known team is a *common requirement* for upstream teams. (e.g. it means that developers can push to a branch, get a quick native package built, uploaded locally, installed via an inotify and available to test without the unnecessary step of building an .orig.tar.gz in the middle.) It's not quite as clean or DRY as restarting a daemon directly from a user-privilege git clone but it is workable. Why should that require two branches of the packaging files? Developing using Debian is not just about development of Debian. Upstream teams use dpkg-dev too. Constraints which are entirely warranted for developing packages destined for ftp-master are directly harmful for developing packages destined for a repository on 192.168. Yes this could work with overrides but those overrides need to be build specific (not package specific or version specific). This is exactly why a ~/.gbp.conf is the right approach. Not true. There are options to use debuild or pdebuild or dpkg-buildpackage in-place. e.g. I use: [DEFAULT] #builder = git-pbuilder builder = debuild cleaner = fakeroot debian/rules clean pristine-tar = True [git-buildpackage] export-dir = ../build-area/ tarball-dir = ../tarballs/ Even if so, this increases the complexity of the system, and requires people to learn yet another tool to Just Do what was previously possible with no extra fluff. It's okay for a tool (like dpkg) to warn if something doesn't look right. It's not okay for a tool (like dpkg) to pretend to be smarter than the person operating said tool. True - however, there will always be a need for tools like git-bp and it is common to use aliases and JDTRT scripts to provide a consistent interface no matter what changes beneath. Thankfully, none of those hacks make it into Debian but that does mean that people within Debian don't get to see how the tools are actually used. Switching a non-native package to native arbitrarily is a necessary use of dpkg and it needs to be supported cleanly and in a way which is easy to override using a per-build configuration option. -- Neil Williams = http://www.linux.codehelp.co.uk/ signature.asc Description: PGP signature
Bug#713193: guile-gnome-platform: FTBFS: /bin/sh: 1: aclocal-1.11: not found
Control: tags -1 +patch +pending Hi, I've fixed this FTBFS bug as attached diff, not use hardcoding value but include macro. And I'll upload it to 7-delayed queue, if you don't want it, please tell me. Thanks. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane diff -Nru guile-gnome-platform-2.16.2/debian/changelog guile-gnome-platform-2.16.2/debian/changelog --- guile-gnome-platform-2.16.2/debian/changelog 2012-06-02 23:32:20.0 +0900 +++ guile-gnome-platform-2.16.2/debian/changelog 2014-02-11 17:59:12.0 +0900 @@ -1,3 +1,12 @@ +guile-gnome-platform (2.16.2-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules +- use /usr/share/cdbs/1/class/autotools-vars.mk, instead of hardcoding + autotools versions (Closes: #713193) + + -- Hideki Yamane henr...@debian.org Tue, 11 Feb 2014 17:59:09 +0900 + guile-gnome-platform (2.16.2-1) unstable; urgency=low * New upstream version: diff -Nru guile-gnome-platform-2.16.2/debian/rules guile-gnome-platform-2.16.2/debian/rules --- guile-gnome-platform-2.16.2/debian/rules 2012-06-02 23:32:20.0 +0900 +++ guile-gnome-platform-2.16.2/debian/rules 2014-02-11 17:58:28.0 +0900 @@ -2,13 +2,9 @@ #export DH_VERBOSE=1 -DEB_AUTO_UPDATE_AUTOCONF = 2.69 -DEB_AUTO_UPDATE_ACLOCAL = 1.11 -DEB_AUTO_UPDATE_AUTOMAKE = 1.11 -DEB_AUTO_UPDATE_LIBTOOL = pre - include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk +include /usr/share/cdbs/1/class/autotools-vars.mk DEB_CONFIGURE_EXTRA_FLAGS := --disable-Werror GUILE=guile-1.8 DEB_DH_INSTALL_ARGS := --sourcedir=$(DEB_DESTDIR)
Bug#738591: lintian: Add checker for timestamped gzip files
Tomasz Buchert: +Severity: normal It think it should be at most wishlist, perhaps even pedantic. Let's make it pedantic, but hopefully one day it will be normal. Could we go for “wishlist” instead? I know that switching to reproducible builds sounds like a major shift in Debian's current practices but we already have way more packages reproducible that one might expect. The following wiki page describe the last large scale experiment that was done: https://wiki.debian.org/ReproducibleBuilds/Rebuild20140126 67% out of the 6887 packages that were tested were reproducible. 103 of them failed due to one or more timestamp in gzip files. I think “wishlist” is more appropriate because we are trying to get the the archive reproducible and asking interested maintainers for help. I don't think this fall under a “particular Debian packaging style” as worded in the man page about `--pedantic`. In any cases, my dear Lintian maintainers, I trust you to sort things out appropriately. :) -- Lunar.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- signature.asc Description: Digital signature
Bug#738615: wrong firmware for intel iwlwifi 7260
Package: firmware-iwlwifi Version: 0.40 Hi I downloaded the unstable firmware as I saw it had the firmware I needed for my new laptop and copied the file into the right place. Not a normal install... I'm running testing. The firmware is too old even for testing. Sadly the firmware doesn't work well at all, regular disconnects and lots of errors in the kernel log. Others have seen exactly this problem: http://ubuntuforums.org/showthread.php?t=2189035page=3 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1221202 I grabbed the new images from: http://wireless.kernel.org/en/users/Drivers/iwlwifi And they work perfectly so far, no errors, no disconnects, much better throughput. Thanks, M -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738610: Maven not working
This is caused by #738579 Downgrading libsisu-guice-java to version 3.1.1+dfsg-1 makes Maven work again. -- Kim Rydhof Thor Hansen Vadgårdsvej 3, 2. tv. 2860 Søborg Phone: +45 3091 2437 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737634: dpkg: is_native version checks in dpkg 3.0 Native
Le Wed, Feb 05, 2014 at 09:08:04PM +0100, Guillem Jover a écrit : Sorry, I should have added here my usual note about being open to reconsideration *if* convincing arguments are put forward. But I was pretty much unimpressed with the way this had been brought up. Way more so now with the threats of TC force, but I guess that's the new Debian-way… Hi Guillem, I would like you to consider that, what you would feel if the TC would push a decision on you, we feel it when you push your decision on us. Clearly, when my work was first interrupted by dpkg-dev after upgrading it, and when I realised through the changelog and the bug log that it was an unconcerted top-down decision, my feeling was that the contribution that I was making was not as welcome as I thought, and that I should find a better way to spend my time. For example, what does ikiwiki (a native package with a native version) has to do with anything? The Ikiwiki package, which uses a native version number for a clearly non-native work in the sense of Policy's section 3.2.1 (packages which have been written especially for Debian), shows how inconsistent is the concept of a native package. It shows that there is no problem with the version number indicating one thing and the source format indicating another one. So please revert your change, which solves no practical problems. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738559: logrotate: Wildcard match first directory only
On Mon, Feb 10, 2014 at 04:12:58PM +, Colin Fowler wrote: Logrotate only rotatated the first directory matched i.e. /var/log/a/*.log was rotated /var/log/b/*.log remained untouched * What outcome did you expect instead? All logs in all directories under /var/log to be rotated Can you send the output of ls -l /var/log/*/*.log please? Bear in mind that other installed programs may have a glob on *.log, and a specific directory (eg. apache), and your pattern might interfere with that. I'd suggest logging into /var/log/a-unique-name/xxx/yyy.log instead. -- Paul Martin p...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735405: ktimer doesn't write ktimerrc
Control: tags -1 + unreproducible In article 20140115075728.32637.95165.reportbug__5024.19059998846$1389772834$gmane$org@localhost you wrote: Package: ktimer Version: 4:4.11.3-1 Severity: normal I am unable to save jobs, ie the jobs list is empty when I start ktimer and changes to ktimerrc can be made only by hand. As I see no save buttons around how job management is supposed to work? I can't reproduce the issue here. After adding a job from the ui and setting the command the configuration file gets written. Maybe there a syntax error in your configuration file and that might be the reason why its not being overwritten. Try to rename your ~/.kde/share/config/ktimerrc Thanks, -- If a million people believe a foolish thing, it is still a foolish thing. -- France's Rule of Folly Saludos /\/\ /\ `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
Package: release.debian.org We would like the version of libasio-dev in unstable to revert to the version currently in testing (1.4.8-2) Can you please remove the v1.10.1-1 libasio-dev from unstable or let me know what action to take, e.g. should I upload a 1.4.8-3 package? Also, could you please comment on whether we should plan a transition for asio 1.10 to enter jessie? Markus is maintaining the package, reSIProcate is the only build dependency we know of and if there are no others then a formal transition probably isn't required. Is there an equivalent of apt-cache rdepends that can help us locate any other packages with a build dependency on libasio-dev? As it is a header library, no packages declare a runtime dependency on it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738526: sort: weird(might wrong) sorting result
On 02/10/2014 08:56 AM, Adam Lee wrote: echo -e c = c\nca = ca\ncm = cm|sort $ echo -e c = c\nca = ca\ncm = cm| LANG=C sort c = c ca = ca cm = cm This is a FAQ, but you need to explicitly set the C locale to avoid your locale collating rules. thanks, Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738591: lintian: Add checker for timestamped gzip files
On 11/02/14 10:09, Jérémy Bobbio wrote:
Tomasz Buchert:
+Severity: normal
It think it should be at most wishlist, perhaps even pedantic.
Let's make it pedantic, but hopefully one day
it will be normal.
Could we go for “wishlist” instead?
Hi,
I reworked the patch so that it reuses the machinery
in files.pm. I also made it wishlist this time. I attach the patch.
Currently, it will emit package-contains-timestamped-gzip
on any file ending with .gz, being a gzip file and containing
a timestamp. It means that currently the tag
gzip-file-is-not-multi-arch-same-safe
will imply package-contains-timestamped-gzip. Moreover, the new tag breaks
multiple
tests (files-gzip, manpages-general, etc.) because they use timestamped gzips.
I will
fix it, but first I'd like to know that implementation of the tag is ok.
Cheers,
Tomasz
I know that switching to reproducible builds sounds like a major
shift in Debian's current practices but we already have way more
packages reproducible that one might expect.
The following wiki page describe the last large scale experiment that
was done: https://wiki.debian.org/ReproducibleBuilds/Rebuild20140126
67% out of the 6887 packages that were tested were reproducible. 103 of
them failed due to one or more timestamp in gzip files.
I think “wishlist” is more appropriate because we are trying to get the
the archive reproducible and asking interested maintainers for help.
I don't think this fall under a “particular Debian packaging style”
as worded in the man page about `--pedantic`.
In any cases, my dear Lintian maintainers, I trust you to sort things
out appropriately. :)
--
Lunar.''`.
lu...@debian.org: :Ⓐ : # apt-get install anarchism
`. `'`
`-
From 4dcc45c75df792820c356beca0fa84b067cf0268 Mon Sep 17 00:00:00 2001
From: Tomasz Buchert tomasz.buch...@inria.fr
Date: Tue, 11 Feb 2014 10:11:20 +0100
Subject: [PATCH] new tag: package-contains-timestamped-gzip (+ test)
---
checks/files.desc | 8
checks/files.pm| 14 +-
t/tests/reproducibility/debian/debian/control.in | 17 +
.../debian/debian/unreproducible-pkg.install | 1 +
t/tests/reproducibility/debian/file| 1 +
t/tests/reproducibility/debian/file-with-timestamp.gz | Bin 0 - 39 bytes
.../reproducibility/debian/file-without-timestamp.gz | Bin 0 - 34 bytes
t/tests/reproducibility/debian/prepare | 4
t/tests/reproducibility/desc | 6 ++
t/tests/reproducibility/tags | 1 +
10 files changed, 47 insertions(+), 5 deletions(-)
create mode 100644 t/tests/reproducibility/debian/debian/control.in
create mode 100644 t/tests/reproducibility/debian/debian/unreproducible-pkg.install
create mode 100644 t/tests/reproducibility/debian/file
create mode 100644 t/tests/reproducibility/debian/file-with-timestamp.gz
create mode 100644 t/tests/reproducibility/debian/file-without-timestamp.gz
create mode 100755 t/tests/reproducibility/debian/prepare
create mode 100644 t/tests/reproducibility/desc
create mode 100644 t/tests/reproducibility/tags
diff --git a/checks/files.desc b/checks/files.desc
index 760f86a..e8237f0 100644
--- a/checks/files.desc
+++ b/checks/files.desc
@@ -1448,3 +1448,11 @@ Info: The given file is in PATH but consists of non-ASCII characters.
.
Note that Lintian may be unable to display the filename accurately.
Unprintable characters may have been replaced.
+
+Tag: package-contains-timestamped-gzip
+Severity: wishlist
+Certainty: certain
+Info: The package contains a gzip'ed file that has timestamps.
+ Such files make the produces packages unreproducible.
+ .
+ Pass -n flag to gzip to avoid it.
diff --git a/checks/files.pm b/checks/files.pm
index 5c5a60d..21a0f0c 100644
--- a/checks/files.pm
+++ b/checks/files.pm
@@ -1400,23 +1400,27 @@ sub run {
my $finfo = $info-file_info($file) || '';
if ($finfo !~ m/gzip compressed/) {
tag 'gz-file-not-gzip', $file;
-} elsif ($isma_same $file !~ m/\Q$arch\E/o) {
+} else {
my $path = $info-unpacked($file);
my $buff;
+my $mtime;
open(my $fd, '', $path);
# We need to read at least 8 bytes
if (sysread($fd, $buff, 1024) = 8) {
# Extract the flags and the mtime.
# NN NN NN NN, NN NN NN NN - bytes read
# __ __ __ __,$mtime- variables
-my (undef, $mtime) = unpack('NN', $buff);
-if ($mtime){
-
Bug#727645: Please see bug #668890
In article 52D546C7.5040005__5034.13459887287$1389709119$gmane$o...@gmail.com you wrote: Package: polkit-kde-1 Version: 0.99.1-1 Please see bug #668890 [1] for a possible solution on the dirmngr side of this issue. I'm still wondering why an user who can well shutdown the entire box should be prevented to hibernate. Furthermore, oddly enough, in my case suspend doesn't need any further authentication, while hibernation does. Sorry, but I fail to see the relation between dirmngr and polkit-kde-1, why does the use of su vs start-stop-daemon affects the hibernation? Thanks, -- The cheapest, fastest and most reliable components of a computer system are those that aren't there. -- Gordon Bell Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Bug#723789: FTBFS: configure.ac:76: error: required file 'config/compile' not found
Control: retitle -1 FTBFS: dpkg-shlibdeps: error: couldn't find library libparsifal-1.0.0.so Hi, Just use autoreconf in debian/rules eliminate this issue. stamp-configure: dh_testdir autoreconf -if JNI_INCLUDES=-I/usr/lib/jvm/java-gcj/include \ PYTHON=python ./configure --prefix=/usr touch $@ However, I cannot upload it since dpkg-shlibdeps gets a lot of errors as below. dpkg-shlibdeps: error: couldn't find library libparsifal-1.0.0.so needed by debian/python-sidl/usr/lib/python2.7/dist-packages/sidl/RuntimeException.so (ELF format: 'elf64-x86-64'; RPATH: '') dpkg-shlibdeps: error: couldn't find library libparsifal-1.0.0.so needed by debian/python-sidl/usr/lib/python2.7/dist-packages/sidl/rmi/NoServerException.so (ELF format: 'elf64-x86-64'; RPATH: '') dpkg-shlibdeps: error: couldn't find library libparsifal-1.0.0.so needed by debian/python-sidl/usr/lib/python2.7/dist-packages/sidl/rmi/Ticket.so (ELF format: 'elf64-x86-64'; RPATH: '') ... -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738617: /usr/lib/x86_64-linux-gnu/qt5/bin/lupdate: lupdate would need qmldevtools to collect translation strings from qml files
Package: qttools5-dev-tools
Version: 5.2.0-9
Severity: minor
File: /usr/lib/x86_64-linux-gnu/qt5/bin/lupdate
Dear Maintainer,
lupdate has conditional support to collect strings from qml files. To
enable qml support qttools build would need access to qmldevtools module.
If I understand qt module system correctly that would mean build
dependency to qtdeclarative5-private-dev.
The optional dependency is in
src/linguist/lupdate/lupdate.pro
test.pro:
TARGET = test
QT += quick
lupdate_only {
SOURCES += test.qml
}
TRANSLATIONS = en.ts
OTHER_FILES = test.qml
test.qml:
import QtQuick 2.0
Rectangle {
width: 400
height: 400
Text {
text: qsTr(Translated text)
}
}
result:
$ lupdate test.pro
lupdate warning: Some files have been ignored due to missing qml/javascript
support
Updating 'en.ts'...
Found 0 source text(s) (0 new and 0 already existing)
Thanks,
Pauli
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages qttools5-dev-tools depends on:
ii libc62.17-97
ii libgcc1 1:4.8.2-15
ii libqt5core5a [qtbase-abi-5-2-0] 5.2.0+dfsg-7
ii libqt5dbus5 5.2.0+dfsg-7
ii libqt5designer5 5.2.0-9
ii libqt5designercomponents55.2.0-9
ii libqt5gui5 5.2.0+dfsg-7
ii libqt5help5 5.2.0-9
ii libqt5network5 5.2.0+dfsg-7
ii libqt5printsupport5 5.2.0+dfsg-7
ii libqt5sql5 5.2.0+dfsg-7
ii libqt5widgets5 5.2.0+dfsg-7
ii libqt5xml5 5.2.0+dfsg-7
ii libstdc++6 4.8.2-15
ii qtchooser39-g4717841-2
ii zlib1g 1:1.2.8.dfsg-1
Versions of packages qttools5-dev-tools recommends:
ii libqt5sql5-sqlite 5.2.0+dfsg-7
qttools5-dev-tools 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#738559: logrotate: Wildcard match first directory only
Can you send the output of ls -l /var/log/*/*.log please? It was thousands of lines long, but comprised mostly of /var/log/servername1/daemon.info.log /var/log/servername2/daemon.info.log Bear in mind that other installed programs may have a glob on *.log, and a specific directory (eg. apache), and your pattern might interfere with that. I'd suggest logging into /var/log/a-unique-name/xxx/yyy.log instead. This works :) Now logging to /var/log/servers/machinename/xxx.log Thanks for the help! Colin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725579: lldpad: FTBFS: automake errors
Control: tags -1 +patch +pending
Hi,
I've fixed this FTBFS (as log suggested ;), attached debdiff.
And also I'll upload it to 7-delayed queue, if you don't want it,
please tell me.
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru lldpad-0.9.46/debian/changelog lldpad-0.9.46/debian/changelog
--- lldpad-0.9.46/debian/changelog 2013-07-16 23:19:39.0 +0900
+++ lldpad-0.9.46/debian/changelog 2014-02-11 19:07:03.0 +0900
@@ -1,3 +1,11 @@
+lldpad (0.9.46-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches
+- add specify_subdir-objects.patch (Closes: #725579)
+
+ -- Hideki Yamane henr...@debian.org Tue, 11 Feb 2014 19:07:02 +0900
+
lldpad (0.9.46-1) unstable; urgency=low
* [8e5431e] Imported Upstream version 0.9.46
diff -Nru lldpad-0.9.46/debian/patches/series lldpad-0.9.46/debian/patches/series
--- lldpad-0.9.46/debian/patches/series 2013-07-16 23:19:39.0 +0900
+++ lldpad-0.9.46/debian/patches/series 2014-02-11 19:05:25.0 +0900
@@ -3,3 +3,4 @@
fix-cannot-adjust-line-in-dcbtool-8.patch
dont-touch-var-lock-subsys-lldpad-when-start.patch
fix-typo-in-lldptool-ets-8.patch
+specify_subdir-objects.patch
diff -Nru lldpad-0.9.46/debian/patches/specify_subdir-objects.patch lldpad-0.9.46/debian/patches/specify_subdir-objects.patch
--- lldpad-0.9.46/debian/patches/specify_subdir-objects.patch 1970-01-01 09:00:00.0 +0900
+++ lldpad-0.9.46/debian/patches/specify_subdir-objects.patch 2014-02-11 19:06:26.0 +0900
@@ -0,0 +1,12 @@
+Description: specify subdir-objects for directories
+Bug-Debian: http://bugs.debian.org/725579
+Last-Update: 2014-02-10
+
+--- lldpad-0.9.46.orig/Makefile.am
lldpad-0.9.46/Makefile.am
+@@ -1,3 +1,5 @@
++AUTOMAKE_OPTIONS = subdir-objects
++
+ # target programs to be installed in ${sbindir}
+ sbin_PROGRAMS = lldpad dcbtool lldptool
+
Bug#737538: org-mode: Beamer latex export (ox-beamer) not available with emacs24
tag 737538 + unreproducible moreinfo thanks Hello Olivier, using 8.4.2-1, here's what I get: # emacs24 -q --batch --eval (progn (org-mode) (princ (describe-variable 'org-export-backends))) 2 /dev/null | grep value is Its value is (ascii html icalendar latex) # emacs23 -q --batch --eval (progn (org-mode) (princ (describe-variable 'org-export-backends))) 2 /dev/null | grep value is Its value is (ascii html icalendar latex) Do you see something else ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731860: libtar: CVE-2013-4420: directory traversal when extracting archives
Hi, On 9 February 2014 22:08, Magnus Holmgren mag...@kibibyte.se wrote: The first if should be a while, shouldn't it? Otherwise we'll only skip over the first ../ if file_name starts with ../../, if I'm not mistaken. That's handled by the while loop right after the if. Attached test case contains an entry called ../../../empty-file tar tf should print a warning message and list the full path, while libtar should simply print it as 'empty-file'. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net triple-double-dot.tar Description: Unix tar archive
Bug#738618: cdimage.debian.org: new install CD unsuable on some hardware
Package: cdimage.debian.org Severity: important Dear Maintainer, I've got a bunch of hardware wich has problems with a kernel driver. I can't say if it the hardware wich is faulty or the driver that has a bug, or even if it tries to load against an unsupported hardware, but the system just hang as soon as it tries to load this driver. /kernel/drivers/gpu/drm/gma500/gma500_gfx.ko This is well tested, reproduced etc... I'm absolutely sure of that. It occurs at least on every Intel Motherboard DN2800MT and maybe on most Atom Based systems used in x64 mode On lhe last installation CD, This driver was not present but installed on the new system. Since this driver is loaded VERY early, I found no way to blacklist it nicely and I finaly solve the problem by just deleting the module from ths disk. Anyway, that's not a big deal since I only use text mode on theses machines and the vesa standard works nicely. The problem is that the new install CD (debian 7.4.0), try to load this driver even in console mode and the system hangs immediately after the bootloader. I'm absolutely sure the problem is related with this video driver. I'm not comfortable with CD images, and bootable CD images and don't want to mess up with this if I can avoid it. So, Is there a way to boot the CD with some parameter that prevent this driver from loading ? Is there an easy way to modify the installation CD (or an usb key) and remove a specific driver. -- System Information: Debian Release: 7.4 Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731821: bluefish: Bluefish segmentfaults when I try to open a file
tags 731821 + unreproducible thanks Hi, Please install bluefish-dbg (the debugging symbols) and run bluefish in the gdb program, create a backtrace and attach it to this report. http://bfwiki.tellefsen.net/index.php/Debugging_Bluefish#Run_Bluefish_in_the_debugger Regards, Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On Tue, Feb 11, 2014 at 10:44:30 +0100, Daniel Pocock wrote: Package: release.debian.org We would like the version of libasio-dev in unstable to revert to the version currently in testing (1.4.8-2) You might want to explain why. Can you please remove the v1.10.1-1 libasio-dev from unstable or let me know what action to take, e.g. should I upload a 1.4.8-3 package? No, we can't do that. And you shouldn't do that. What you can do is use an epoch to make the version number go backwards. Also, could you please comment on whether we should plan a transition for asio 1.10 to enter jessie? Markus is maintaining the package, reSIProcate is the only build dependency we know of and if there are no others then a formal transition probably isn't required. Is there an equivalent of apt-cache rdepends that can help us locate any other packages with a build dependency on libasio-dev? As it is a header library, no packages declare a runtime dependency on it. wget -qO- http://ftp.debian.org/debian/dists/sid/main/source/Sources.gz | zcat | grep-dctrl -FBuild-Depends -sPackage libasio-dev Adjusting for contrib and non-free left as an exercise for the reader. Cheers, Julien signature.asc Description: Digital signature
Bug#738605: bash man page says can't break line
Control: reassign -1 bash On Tue, Feb 11, 2014 at 02:09:21PM +0800, Dan Jacobson wrote: man bash shows: HISTIGNORE A colon-separated list of patterns used to decide which command lines should be saved on the history list. Each pattern is anchored at the beginning of the line and must mastandard input:2282: warning [p 18, 11.0i]: can't break line tch the com- plete line (no implicit `*' is appended). Each pattern is tested against the line after the checks specified by HISTCON- TROL are applied. In addition to the normal shell pattern (Package: bash Version: 4.3~rc2-1) Reassigning to bash, then. Please do not report bugs about manual pages in other packages to man-db; the maintainers of the other packages in question can reassign things to man-db or groff if they think it's the fault of the formatting toolchain rather than their page. (I think I've told you this before.) -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738619: Upper-case Host specification in .ssh/config doesn't work anymore in 6.5p1
Package: openssh-client Version: 1:6.5p1-1 Severity: important Tags: upstream Hi Colin, Since the 6.5p1 update, uppercase Host specifications in .ssh/config don't work anymore: I had the following in my .ssh/config that allowed me to correctly connect with 6.4p1: Host Icterus HostName odyx.homelinux.org With 6.5p1, this fails as follows: $ ssh - Icterus OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/didier/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * ssh: Could not resolve hostname icterus: Name or service not known While it worked with 6.4p1-2: $ ssh - Icterus OpenSSH_6.4, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/didier/.ssh/config debug1: /home/didier/.ssh/config line 1: Applying options for Icterus debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to odyx.homelinux.org That's IMHO a regression, hence the important severity. Cheers, OdyX -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-client depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.6 ii libc6 2.17-97 ii libedit2 3.1-20130712-2 ii libgssapi-krb5-2 1.12+dfsg-2 ii libselinux1 2.2.2-1 ii libssl1.0.0 1.0.1f-1 ii passwd1:4.1.5.1-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages openssh-client recommends: ii xauth 1:1.0.7-1 Versions of packages openssh-client suggests: pn keychain none pn libpam-sshnone pn monkeysphere none ii ssh-askpass 1:1.2.4.1-9 -- 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#735785: ogre-1.8: FTBFS: Could not locate FREETYPE
Control: tags -1 +fixed-upstream Hi, New upstream 1.9.0 release fixes this issue, you can get it from https://bitbucket.org/sinbad/ogre/downloads # However, it's necessary to deal with other issues (not ogre-1.8 but 1.9, etc) -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640150:
This appears to still be an issue: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:20929): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Thanks, Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525175: kdebase-runtime: kdesu not in path
Control: tags -1 + wontfix In article web-131712055__4354.46066917411$1389356483$gmane$o...@sns.it you wrote: Hi, this problem is still present in kdebase-runtime 4:4.8.4-2. Any news? That change was reverted back in 2008, kdesu in /usr/bin conflicted with kde3 packages, and will probably be an issue for kde frameworks 5, so we plan to ship those files in /usr/lib/kf5/libexec (or something similar). Please notice that you can use kdesu directly in a desktop file (in kde) or from krunner. Thanks, -- Porque no respeta el orden natural en el que se leen las cosas ¿Por qué contestar al principio del mensaje es malo? Saludos /\/\ /\ `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733439: pydicom: diff for NMU version 0.9.7-1.1
Control: tags -1 + pending Dear maintainer, I've prepared an NMU for pydicom (versioned as 0.9.7-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- Sebastian Ramacher diff -Nru pydicom-0.9.7/debian/changelog pydicom-0.9.7/debian/changelog --- pydicom-0.9.7/debian/changelog 2012-06-08 20:30:49.0 +0200 +++ pydicom-0.9.7/debian/changelog 2014-02-11 11:50:05.0 +0100 @@ -1,3 +1,11 @@ +pydicom (0.9.7-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/distribute.patch: Disable downloading of distribute from +PyPI. (Closes: #733439) + + -- Sebastian Ramacher sramac...@debian.org Tue, 11 Feb 2014 11:50:03 +0100 + pydicom (0.9.7-1) unstable; urgency=low * New upstream release diff -Nru pydicom-0.9.7/debian/patches/distribute.patch pydicom-0.9.7/debian/patches/distribute.patch --- pydicom-0.9.7/debian/patches/distribute.patch 1970-01-01 01:00:00.0 +0100 +++ pydicom-0.9.7/debian/patches/distribute.patch 2014-02-11 11:46:38.0 +0100 @@ -0,0 +1,14 @@ +Description: Do not download distribute from the internet +Author: Sebastian Ramacher sramac...@debian.org +Bug-Debian: http://bugs.debian.org/733439 +Last-Update: 2014-02-05 + +--- pydicom-0.9.7.orig/setup.py pydicom-0.9.7/setup.py +@@ -1,6 +1,4 @@ + #!/usr/bin/env python +-from distribute_setup import use_setuptools +-use_setuptools() + + from setuptools import setup, find_packages + import os diff -Nru pydicom-0.9.7/debian/patches/series pydicom-0.9.7/debian/patches/series --- pydicom-0.9.7/debian/patches/series 2012-06-08 20:30:49.0 +0200 +++ pydicom-0.9.7/debian/patches/series 2014-02-11 11:47:19.0 +0100 @@ -0,0 +1 @@ +distribute.patch signature.asc Description: Digital signature
Bug#738620: GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
Package: consolekit Version: 0.4.6-3+b1 From my systemd jounral after a SSH session was closed: Feb 11 12:04:30 woodpecker console-kit-daemon[3277]: (process:32483): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Feb 11 12:04:30 woodpecker console-kit-daemon[3277]: missing action For me, it is hard to tell if this is a consolekit bug or a GLib bug. libglib2.0-0 version is 2.36.4-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735825: python-fswrap: diff for NMU version 0.1.1-1.1
Control: tags -1 + pending Dear maintainer, I've prepared an NMU for python-fswrap (versioned as 0.1.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- Sebastian Ramacher diff -Nru python-fswrap-0.1.1/debian/changelog python-fswrap-0.1.1/debian/changelog --- python-fswrap-0.1.1/debian/changelog 2013-08-11 11:18:00.0 +0200 +++ python-fswrap-0.1.1/debian/changelog 2014-02-11 11:45:16.0 +0100 @@ -1,3 +1,11 @@ +python-fswrap (0.1.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/distribute.patch: Disable downloading of distribute from +PyPI. (Closes: #735825) + + -- Sebastian Ramacher sramac...@debian.org Tue, 11 Feb 2014 11:45:13 +0100 + python-fswrap (0.1.1-1) unstable; urgency=low * Initial release diff -Nru python-fswrap-0.1.1/debian/patches/distribute.patch python-fswrap-0.1.1/debian/patches/distribute.patch --- python-fswrap-0.1.1/debian/patches/distribute.patch 1970-01-01 01:00:00.0 +0100 +++ python-fswrap-0.1.1/debian/patches/distribute.patch 2014-02-11 11:44:01.0 +0100 @@ -0,0 +1,13 @@ +Description: Do not download distribute from the internet +Author: Sebastian Ramacher sramac...@debian.org +Bug-Debian: http://bugs.debian.org/735825 +Last-Update: 2014-02-05 + +--- python-fswrap-0.1.1.orig/setup.py python-fswrap-0.1.1/setup.py +@@ -1,5 +1,3 @@ +-from distribute_setup import use_setuptools +-use_setuptools() + from setuptools import setup + + try: diff -Nru python-fswrap-0.1.1/debian/patches/series python-fswrap-0.1.1/debian/patches/series --- python-fswrap-0.1.1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ python-fswrap-0.1.1/debian/patches/series 2014-02-11 11:44:28.0 +0100 @@ -0,0 +1 @@ +distribute.patch signature.asc Description: Digital signature
Bug#735817: python-shelltoolbox: diff for NMU version 0.2.1+bzr17-1.1
Control: tags -1 + pending Dear maintainer, I've prepared an NMU for python-shelltoolbox (versioned as 0.2.1+bzr17-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- Sebastian Ramacher diff -u python-shelltoolbox-0.2.1+bzr17/debian/changelog python-shelltoolbox-0.2.1+bzr17/debian/changelog --- python-shelltoolbox-0.2.1+bzr17/debian/changelog +++ python-shelltoolbox-0.2.1+bzr17/debian/changelog @@ -1,3 +1,10 @@ +python-shelltoolbox (0.2.1+bzr17-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * setup.py: Do not download distribute from PyPI. (Closes: #735817) + + -- Sebastian Ramacher sramac...@debian.org Tue, 11 Feb 2014 11:41:15 +0100 + python-shelltoolbox (0.2.1+bzr17-1) unstable; urgency=low * Initial Release. (Closes: #684202) only in patch2: unchanged: --- python-shelltoolbox-0.2.1+bzr17.orig/setup.py +++ python-shelltoolbox-0.2.1+bzr17/setup.py @@ -3,11 +3,6 @@ # Copyright 2012 Canonical Ltd. This software is licensed under the # GNU General Public License version 3 (see the file LICENSE). -import ez_setup - - -ez_setup.use_setuptools() - __version__ = '0.2.1' signature.asc Description: Digital signature
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 11:49, Julien Cristau wrote: On Tue, Feb 11, 2014 at 10:44:30 +0100, Daniel Pocock wrote: Package: release.debian.org We would like the version of libasio-dev in unstable to revert to the version currently in testing (1.4.8-2) You might want to explain why. API changes make it incompatible Fedora and EPEL still carry 1.4.8 which is widely used by dependencies such as those mentioned below Can you please remove the v1.10.1-1 libasio-dev from unstable or let me know what action to take, e.g. should I upload a 1.4.8-3 package? No, we can't do that. And you shouldn't do that. What you can do is use an epoch to make the version number go backwards. Ok, I will do that and upload later today Also, could you please comment on whether we should plan a transition for asio 1.10 to enter jessie? Markus is maintaining the package, reSIProcate is the only build dependency we know of and if there are no others then a formal transition probably isn't required. Is there an equivalent of apt-cache rdepends that can help us locate any other packages with a build dependency on libasio-dev? As it is a header library, no packages declare a runtime dependency on it. wget -qO- http://ftp.debian.org/debian/dists/sid/main/source/Sources.gz | zcat | grep-dctrl -FBuild-Depends -sPackage libasio-dev Adjusting for contrib and non-free left as an exercise for the reader. Thanks for that feedback Looks like the following three packages are impacted by this build dependency: src:abiword src:ball src:resiprocate All those packages need patching to work with the new version of asio due to API changes Does the release team have any preference for making this a formal transition or we should just work it out informally between the maintainers of these packages? Markus, please have a brief look at https://wiki.debian.org/Teams/ReleaseTeam/Transitions -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738622: fglrx-driver: Request for upgrade to new upstream version 14.1
Package: fglrx-driver Version: 1:13.12-4 Severity: normal New upstream version 14.1 beta is available since 02/02 and downloadable at : http://www2.ati.com/drivers/beta/amd-catalyst-14.1-betav1.3-linux-x86.x86_64.zip This version introduces * support for xserver 1.15 (which is default in unstable now) * support for kernel 3.13 (in experimental) * official support for Kaveri APUs -- Vincent Alquier vincent.alqu...@gmail.com
Bug#738621: wishlist: Display current active screensaver in the password dialog window
Package: xscreensaver Version: 5.23-1 Severity: wishlist Dear Maintainer, I would like to make a suggestion for xscreensaver. It would be very nice, if the password display window could list the currently active screensaver of xscreensaver. Another idea would be an option in the preferences to display it maybe under the FPS text or nearby the FPS text. Thank you for your efforts. Adrian Immanuel KIESS -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-trunk-amd64 (SMP w/4 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 xscreensaver depends on: ii libatk1.0-0 2.10.0-2 ii libc62.17-97 ii libcairo21.12.16-2 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglade2-0 1:2.6.4-2 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-0 2.24.22-1 ii libice6 2:1.0.8-2 ii libpam0g 1.1.3-9 ii libpango-1.0-0 1.36.0-1+b1 ii libpangocairo-1.0-0 1.36.0-1+b1 ii libpangoft2-1.0-01.36.0-1+b1 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxi6 2:1.7.2-1 ii libxinerama1 2:1.1.3-1 ii libxml2 2.9.1+dfsg1-3 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.4-1 ii libxxf86vm1 1:1.1.3-1 ii xscreensaver-data5.23-1 Versions of packages xscreensaver recommends: ii libjpeg-progs8d-2 ii perl [perl5] 5.18.2-2 ii wamerican [wordlist] 7.1-1 ii wamerican-insane [wordlist] 7.1-1 ii wbritish-insane [wordlist] 7.1-1 ii wcanadian-insane [wordlist] 7.1-1 ii wcatalan [wordlist] 0.20111230b-4 ii wfrench [wordlist] 1.2.3-10 ii wgerman-medical [wordlist] 20110608-1 ii wngerman [wordlist] 20120607-1 Versions of packages xscreensaver suggests: ii chromium [www-browser] 31.0.1650.63-1 ii epiphany-browser [www-browser] 3.8.2-5 ii fortune-mod [fortune] 1:1.99.1-7 ii gdm33.8.4-6 ii iceweasel [www-browser] 24.2.0esr-1 ii kdm-gdmcompat 0.13-2 ii konqueror [www-browser] 4:4.11.3-1 ii links2 [www-browser]2.8-1+b1 ii lynx-cur [www-browser] 2.8.8pre4-1 ii opera [www-browser] 12.16.1860 ii streamer3.103-3 ii w3m [www-browser] 0.5.3-15 pn xdaliclock none pn xfishtank none ii xscreensaver-gl 5.23-1 -- 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#738623: gnome-icon-theme: Cannot open pixbuf loader module file
Package: gnome-icon-theme Version: 3.10.0-1 Severity: normal Hi, I saw the following while updating: Processing triggers for gnome-icon-theme (3.10.0-1) ... (gtk-update-icon-cache-3.0:32480): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linu$ This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Is this related to #640150 at all? Thanks, Nick -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-icon-theme depends on: ii hicolor-icon-theme 0.13-1 ii libgtk-3-bin3.8.6-1 ii librsvg2-common 2.40.0-1 gnome-icon-theme recommends no packages. gnome-icon-theme 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#738619: Upper-case Host specification in .ssh/config doesn't work anymore in 6.5p1
On Tue, Feb 11, 2014 at 11:56:08AM +0100, Didier Raboud wrote: Since the 6.5p1 update, uppercase Host specifications in .ssh/config don't work anymore: Yes, I happened to spot a fix for this go by in the Arch packages. In my next upload I'll cherry-pick the same patch from upstream as they did. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727645: Please see bug #668890
Package: polkit-kde-1 Version: 0.99.1-1 Please see bug #668890 [1] for a possible solution on the dirmngr side of this issue. I'm still wondering why an user who can well shutdown the entire box should be prevented to hibernate. Furthermore, oddly enough, in my case suspend doesn't need any further authentication, while hibernation does. Sorry, but I fail to see the relation between dirmngr and polkit-kde-1, why does the use of su vs start-stop-daemon affects the hibernation? Thanks, According to the description in the http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668890 su spawns login shell where the start-stop-daemon doesn't. This login shell that su spawns violates polkit policy org.freedesktop.login1.hibernate-multiple-sessions when trying to hibernate and it can be seen with loginctl. loginctl shows: SESSIONUID USER SEAT c1112 dirmngr c2 1000 durinseat0 I don't know if su works differently when using systemd and not sysvinit and makes this problem appear only when using systemd. Thanks, Sami
Bug#725471: cglib: FTBFS using locally rebuilt packages
Hi Daniel, I haven't been able to reproduce this error. Do you know what Java packages were installed in the local repository? Did you build them on sid or wheezy? Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738593: openssh-server: changelog mis-description, ... upgrades create ed25519 host keys as well
On Tue, Feb 11, 2014 at 01:26:29AM +0100, Christoph Anton Mitterer wrote: As far as I'd understand the changelog entry * Generate ED25519 host keys on fresh installations. Upgraders who wish to add such host keys should manually add 'HostKey /etc/ssh/ssh_host_ed25519_key' to /etc/ssh/sshd_config and run 'ssh-keygen -q -f /etc/ssh/ssh_host_ed25519_key -N -t ed25519'. for 1:6.5p1-1... ED25519 are not created on package upgrades but only fresh installations. Oops, right. I'll retroactively correct the changelog. (You still need to add the HostKey entry manually on upgrades.) This does not seem to be the case (I'm generally unsure whether I like the idea of automatically created keys... since this may also happen in low entropy situations)... Well, that's why I prefer to do this in the postinst rather than at boot time as some other distributions do, as I think it's much more likely that sufficient entropy will be available when installing packages. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618862: [systemd-devel] Debian Bug#618862: systemd: ignores keyscript in crypttab - a possible solution
On Sat, 08.02.14 21:07, David Härdeman (da...@hardeman.nu) wrote: On Wed, Feb 05, 2014 at 12:16:00AM +0100, Lennart Poettering wrote: On Thu, 30.01.14 10:40, David Härdeman (da...@hardeman.nu) wrote: This issue is fixable with minor upstream changes, e.g. by extending the PasswordAgent protocol to add Subsystem=cryptsetup and Target=diskname entries to the ask. file. I'd be fine with adding a field Id= or so, which then is filled by an identifier of some kind be the cryptsetup tool that is useful to identify the device to query things on. for example: Id=cryptsetup:/dev/sda5 or so could be one way how this could be filled in. We wouldn't enfoce any kind of syntax on this, just suggest some common sense so that people choose identifiers that are unlikely to clash with other subsystems, and somewhat reasonable to read... In the patches I sent I split it into Purpose and Target and my thinking was more or less the same as yours...i.e. that there's no particular syntax and that the meaning of the string is subsystem specific. I'd be happy to change the patch to use Id=subsystem:target if you'd prefer. Yes, please! b) the password agent implementation in systemd doesn't seem to handle binary strings (i.e. strings with '\0'), as can be seen by calls to e.g. strlen()... Whether making it binary safe would be a major change or not is something I haven't researched yet but it seems like a change that should be generally useful upstream... I'd be OK with this, as discussed at FOSDEM, and I see you already posted a ptach for this. Yes. I take it you're pretty busy with the kdbus stuff right now but a review of those patches would be nice when you have the time. Lennart -- Lennart Poettering, Red Hat -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716880: apache2 upgrade failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I have the same problem on two different wheezy hosts with aptitude
safe-upgrade (both fresh installed wheezys and no distupgrade from
squeeze) and the package libapache2-svn was, and is, not installed on
both hosts.
But I have other fresh installed Wheezy Hosts without upgrade Problems.
i.e. the mistaken safe-upgrade
(...)
Setting up apache2-utils (2.2.22-13+deb7u1) ...
Setting up apache2.2-bin (2.2.22-13+deb7u1) ...
Setting up apache2.2-common (2.2.22-13+deb7u1) ...
insserv: Service slapd has to be enabled to start service apache2
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing apache2.2-common (--configure):
subprocess installed post-installation script returned error exit
status 1
dpkg: dependency problems prevent configuration of apache2-mpm-itk:
apache2-mpm-itk depends on apache2.2-common (= 2.2.22-13+deb7u1);
however:
Package apache2.2-common is not configured yet.
dpkg: error processing apache2-mpm-itk (--configure):
dependency problems - leaving unconfigured
Setting up openssl (1.0.1e-2+deb7u4) ...
Errors were encountered while processing:
apache2.2-common
apache2-mpm-itk
E: Sub-process /usr/bin/dpkg returned an error code (1)
# aptitude reinstall apache2.2-common
Die folgenden Pakete werden ERNEUT INSTALLIERT:
apache2.2-common
Die folgenden teilweise installierten Pakete werden konfiguriert:
apache2-mpm-itk
0 Pakete aktualisiert, 0 zusätzlich installiert, 1 erneut installiert,
0 werden entfernt und 0 nicht aktualisiert.
0 B an Archiven müssen heruntergeladen werden. Nach dem Entpacken
werden 0 B zusätzlich belegt sein.
E: Internal Error, No file name for apache2.2-common:i386
# apache2ctl fullstatus
(...)
Server Version: Apache/2.2.22 (Debian) mod_ssl/2.2.22 OpenSSL/1.0.1e
Server Built: Jan 31 2014 18:55:42
(...)
- -- System Information:
Debian Release: 7.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apache2.2-common depends on:
ii apache2-utils 2.2.22-13+deb7u1
ii apache2.2-bin 2.2.22-13+deb7u1
ii lsb-base 4.1+Debian8+deb7u1
ii mime-support 3.52-1
ii perl 5.14.2-21+deb7u1
ii procps 1:3.3.3-3
Versions of packages apache2.2-common recommends:
ii ssl-cert 1.0.32
Versions of packages apache2.2-common suggests:
pn apache2-doc none
pn apache2-suexec | apache2-suexec-custom none
ii lynx-cur [www-browser] 2.8.8dev.12-2
ii w3m [www-browser] 0.5.3-8
Versions of packages apache2.2-common is related to:
pn apache2-mpm-eventnone
iu apache2-mpm-itk 2.2.22-13+deb7u1
pn apache2-mpm-prefork none
pn apache2-mpm-worker none
And a system where the upgrade runs fine.
Server Version: Apache/2.2.22 (Debian) DAV/2 mod_ssl/2.2.22
OpenSSL/1.0.1e
Server Built: Jan 31 2014 18:55:42
- -- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apache2.2-common depends on:
ii apache2-utils 2.2.22-13+deb7u1
ii apache2.2-bin 2.2.22-13+deb7u1
ii lsb-base 4.1+Debian8+deb7u1
ii mime-support 3.52-1
ii perl 5.14.2-21+deb7u1
ii procps 1:3.3.3-3
Versions of packages apache2.2-common recommends:
ii ssl-cert 1.0.32
Versions of packages apache2.2-common suggests:
pn apache2-doc none
pn apache2-suexec | apache2-suexec-custom none
ii lynx-cur [www-browser] 2.8.8dev.12-2
ii w3m [www-browser] 0.5.3-8
Versions of packages apache2.2-common is related to:
pn apache2-mpm-eventnone
ii apache2-mpm-itk 2.2.22-13+deb7u1
pn apache2-mpm-prefork none
pn apache2-mpm-worker none
Regards,
Heiko
- --
{
{ Heiko Fiergolla, Systembetrieb
{ E-Mail heiko.fiergo...@xmachina.de
{ Telefon +49-6221-8220-48 Fax +49-8220-40
{ xmachina GmbH advancing e-business
{ Maaßstraße 24 D-69123 Heidelberg
{ http://www.xmachina.de
{ Registergericht Mannheim 335935
{ Geschäftsführer: Klaus Mueller, Michael Grüterich
{
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iEYEARECAAYFAlL6B9gACgkQYX7URpS5/quN7gCfdYHI1T0achr9OqGhUzYyQLYs
rncAoIK1CP3hLxj/pqvaiYV9mTj8owMg
=KKhM
-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#713211: (no subject)
I have uploaded in mentors http://mentors.debian.net/package/sysbench and I am looking for a sponsor ! if someone stumbles over here ... diff -u sysbench-0.4.12/debian/rules sysbench-0.4.12/debian/rules --- sysbench-0.4.12/debian/rules +++ sysbench-0.4.12/debian/rules @@ -6,8 +6,8 @@ # Add here any variable or target overrides you need. DEB_CONFIGURE_SCRIPT_ENV += LDFLAGS= -Wl,-as-needed -DEB_AUTO_UPDATE_AUTOMAKE = 1.11 -DEB_AUTO_UPDATE_ACLOCAL = 1.11 +DEB_AUTO_UPDATE_AUTOMAKE = 1.14 +DEB_AUTO_UPDATE_ACLOCAL = 1.14 DEB_AUTO_UPDATE_LIBTOOL = pre DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl diff -u sysbench-0.4.12/debian/changelog sysbench-0.4.12/debian/changelog --- sysbench-0.4.12/debian/changelog +++ sysbench-0.4.12/debian/changelog @@ -1,3 +1,10 @@ +sysbench (0.4.12-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Bump DEB_AUTO_UPDATE_AUTOMAKE to 1.14 (closes: #713211) + + -- Emmanuel Kasper emman...@libera.cc Tue, 11 Feb 2014 10:57:46 +0100 + sysbench (0.4.12-1) unstable; urgency=low * New upstream version
Bug#738624: RFS: dynamips/0.2.11-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package dynamips * Package name: dynamips Version : 0.2.11-1 Upstream Author : Flávio J. Saraiva flaviojs2...@gmail.com * URL : http://www.gns3.net/dynamips * License : GPLv2 Section : net It builds those binary packages: dynamips - Cisco 7200/3600/3725/3745/2600/1700 Router Emulator To access further information about this package, please visit the following URL: http://mentors.debian.net/package/dynamips Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/non-free/d/dynamips/dynamips_0.2.11-1.dsc More information about dynamips can be obtained from http://www.gns3.net/dynamips https://github.com/GNS3/dynamips Changes since the last upload: dynamips (0.2.11-1) unstable; urgency=low * [ab3a8d82] Bump standards-version to 3.9.5 - no changes * [b792229e] debian/watch - Remove obsolete githubredir * [278818eb] Imported Upstream version 0.2.11 * [f1fec7b5] Drop patches applied upstream + 20-stableMakefileHardening + 30-arm_support.patch * [4a4ab133] Patches to fix architecture detection in Makefile + 10-Makefile-Architecture - removed + MakefileArchitecture.patch - added * [98e2662c] debian/rules + Remove override_dh_install (Makefile fixed for DESTDIR) * [4ec13364] Add patch to fix lintian warning: + manpage-has-errors-from-man hypervisor_mode.7.gz 310: warning: macro `Bvm' not defined -- Daniel Lintott dan...@serverb.co.uk Tue, 11 Feb 2014 11:20:41 + Regards, Daniel Lintott -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJS+gzgAAoJEMw/9yOWzAkJb7UH+wYv3sq2adQhmzoUHxFjtjP4 6Wtt/QpBPf9MpHBu2BmXjaJT9xjBbWSMAM9ve9ex7+UznapA6oaO8VwAWuIu9riK 762T4I4fgJOrz5B28NmctcLNfiSOGj6STRFnac9pnXsALxitWhcWu7f8+55GXZcU mpO9vmRc9EYpSVqlEsC4EkI8/BY/vIM0QJVbW7luFc9c8X6avW9JRDk5gF+ku7J6 UjEK/y8VndVU6Rf+88tOkicj3e9oYC2wnLqPSBNTPfiCW5KF+hCQ0rACt8mXYcMn 5WLnTvCsdWdzjs28srDe0BdW3x88qt2/rVJjMwoJMPmdx7aZwG+4ZsD3TTF7ZLA= =Wnry -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#735785: ogre-1.8: FTBFS: Could not locate FREETYPE
2014-02-11 10:54 GMT+00:00 Hideki Yamane henr...@debian.or.jp: Control: tags -1 +fixed-upstream Hi, New upstream 1.9.0 release fixes this issue, you can get it from https://bitbucket.org/sinbad/ogre/downloads # However, it's necessary to deal with other issues (not ogre-1.8 but 1.9, etc) There already exists src:ogre-1.9, up to date w.r.t. upstream, and present in unstable for a few months. src:ogre-1.8 should be fixed if possible anyway, there are rdepends which didn't move onto 1.9 (and probably not all of their upstreams are ready). Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#737538: org-mode: Beamer latex export (ox-beamer) not available with emacs24
Hello. Sébastien Delafond s...@debian.org writes: tag 737538 + unreproducible moreinfo thanks Hello Olivier, using 8.4.2-1, here's what I get: # emacs24 -q --batch --eval (progn (org-mode) (princ (describe-variable 'org-export-backends))) 2 /dev/null | grep value is Its value is (ascii html icalendar latex) # emacs23 -q --batch --eval (progn (org-mode) (princ (describe-variable 'org-export-backends))) 2 /dev/null | grep value is Its value is (ascii html icalendar latex) Do you see something else ? Nope. Same here. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On Tuesday, 11. February 2014 11:49:22 Julien Cristau wrote: No, we can't do that. And you shouldn't do that. What you can do is use an epoch to make the version number go backwards. Or if you want to avoid using epochs, reupload 1.4.8 using as 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to experimental. Once you upload upstream 1.11 you are back to normal version numbers without having used an epoch inbetween. On Tuesday, 11. February 2014 12:09:46 Daniel Pocock wrote: All those packages need patching to work with the new version of asio due to API changes Does the release team have any preference for making this a formal transition or we should just work it out informally between the maintainers of these packages? You should probably prepare these API adjustments in experimental and request a regular transition once the packages are all fixed. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733439: pydicom: diff for NMU version 0.9.7-1.1
Thank you Sebastian... you could even push without delay Sebastian Ramacher sramac...@debian.org wrote: Control: tags -1 + pending Dear maintainer, I've prepared an NMU for pydicom (versioned as 0.9.7-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. -- Sebastian Ramacher -- Sent from a phone which beats iPhone.
Bug#738625: wget: Unable to establish SSL connection.
Package: wget Version: 1.13.4-3+deb7u1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After the update to 1.13.4-3+deb7u1 I'm unable to Connect to HTTPS-Sites. * What exactly did you do (or not do) that was effective (or ineffective)? wget https://example.com --2014-02-11 12:56:55-- https://example.com/ Resolving example.com (example.com)... xxx.xxx.xxx.xxx Connecting to example.com (example.com)|xxx.xxx.xxx.xxx|:443... connected. GnuTLS: A TLS warning alert has been received. Unable to establish SSL connection. * What was the outcome of this action? see above. * What outcome did you expect instead? Downloading the given URL, which was working fine with 1.13.4-3. As a workaround please backport the option: --sslcheckcert -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wget depends on: ii dpkg 1.16.12 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38+deb7u1 ii libgcrypt111.5.0-5+deb7u1 ii libgnutls262.12.20-7 ii libgpg-error0 1.10-3.1 ii libidn11 1.25-2 ii zlib1g 1:1.2.7.dfsg-13 wget recommends no packages. 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#734750: virtuoso-minimal: segfaults all the time, constant high CPU load
In article 20140109150634.24181.54890.reportbug__40997.8787684397$1389280176$gmane$org@Erwin.babel you wrote: Package: virtuoso-minimal Version: 6.1.6+dfsg-4 Severity: normal From log on to KDE, virtuoso (and akonadi) constantly causes very high CPU load. I notice in syslog that it keeps on segfaulting all the time: Please note that virtuoso is the database backend of nepomuk, and akonadi is a set of agents for the kdepim resources (one of them is a feeder for nepomuk). You could probably disable nepomuk indexing if it takes too much cpu for you or you don't use it. Jan 9 15:57:40 Erwin laptop-mode: enabled, not active Jan 9 15:57:50 Erwin kernel: [10327.063254] virtuoso-t[23809]: segfault at ip 007b2c1e sp 7fa4c0715fc0 error 7 in virtuoso-t[40+974000] Jan 9 15:57:56 Erwin kernel: [10333.170102] virtuoso-t[23853]: segfault at ip 007b2c1e sp 7f5453781fc0 error 7 in virtuoso-t[40+974000] Jan 9 15:58:06 Erwin kernel: [10342.758358] virtuoso-t[23870]: segfault at ip 007b2c1e sp 7f971c81ffc0 error 7 in virtuoso-t[40+974000] Jan 9 15:58:12 Erwin kernel: [10348.894821] virtuoso-t[23886]: segfault at ip 007b2c1e sp 7f6193d2ffc0 error 7 in virtuoso-t[40+974000] Jan 9 15:58:43 Erwin kernel: [10379.637821] virtuoso-t[23955]: segfault at ip 007b2c1e sp 7f5c7bf4efc0 error 7 in virtuoso-t[40+974000] Jan 9 15:58:50 Erwin kernel: [10386.560659] virtuoso-t[24034]: segfault at ip 007b2c1e sp 7fb1c9b08fc0 error 7 in virtuoso-t[40+974000] Jan 9 16:00:05 Erwin kernel: [10462.077828] virtuoso-t[24109]: segfault at ip 007b2c1e sp 7fd979fdefc0 error 7 in virtuoso-t[40+974000] Jan 9 16:00:12 Erwin kernel: [10468.814755] virtuoso-t[24234]: segfault at ip 007b2c1e sp 7f1747d30fc0 error 7 in virtuoso-t[40+974000] Jan 9 16:00:50 Erwin kernel: [10506.472417] virtuoso-t[24270]: segfault at ip 007b2c1e sp 7fc379efdfc0 error 7 in virtuoso-t[40+974000] Jan 9 16:00:56 Erwin kernel: [10513.166859] virtuoso-t[24285]: segfault at ip 007b2c1e sp 7f9fdf8b8fc0 error 7 in virtuoso-t[40+974000] Jan 9 16:03:36 Erwin kernel: [10672.596203] LogServer[3666]: segfault at 20 ip 0020 sp 7f5f4b250738 error 14 in mythlogserver[40+3000] Eventhough I would not call virtuoso rock solid your mythlogserver seems to be also segfaulting, maybe you have an issue with the memory hardware and revealing in intensive applications. Anyway, nepomuk includes a nepomukcleaner that you can run and check if that improves things for you. Thanks, -- If you have too many special cases, you are doing it wrong. -- Craig Zarouni Saludos /\/\ /\ `/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738623:
I've done some further testing - hopefully this information is useful. I can only reproduce this when installing XFCE via the Debian Installer (Alternative Desktop Environment), and then updating to testing. A minimal install, updating to testing and *then* installing XFCE doesn't reproduce this problem. Thanks, Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640150:
I've done some further testing - hopefully this information is useful. I can only reproduce this when installing XFCE via the Debian Installer (Alternative Desktop Environment), and then updating to testing. A minimal install, updating to testing and *then* installing XFCE doesn't reproduce this problem. Thanks, Nick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 02/11/2014 01:01 PM, Andreas Beckmann wrote: Or if you want to avoid using epochs, reupload 1.4.8 using as 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to experimental. Once you upload upstream 1.11 you are back to normal version numbers without having used an epoch inbetween. Given that we are likely to switch to separate libasio1.4-dev and libasio1.10-dev packages, I think the epoch approach is less confusing, overall. You should probably prepare these API adjustments in experimental and request a regular transition once the packages are all fixed. Agreed. Let's do a regular transition. Regards Markus signature.asc Description: OpenPGP digital signature
Bug#737538: org-mode: Beamer latex export (ox-beamer) not available with emacs24
On Feb/11, Olivier Berger wrote: Nope. Same here. so, how do you see the beamer exporter available by default with emacs23 ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733439: pydicom: diff for NMU version 0.9.7-1.1
On 2014-02-11 07:10:53, Yaroslav Halchenko wrote: Thank you Sebastian... you could even push without delay Thanks. Just uploaded it without delay. Cheers -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#639984: lightdm: restart/reload fails if DISPLAY is set
Package: lightdm Version: 1.2.2-4 Followup-For: Bug #639984 Dear Maintainer, we were bitten by that in a real environment, too. And, Yves-Alexis, you were wrong when saying other login managers act equally. I agree that when the lightdm binary is started directly it should somehow be able to auto-detect if it runs in a nested environment or not. Nonetheless we were using the runlevel startup scripts to restart lightdm over a ssh connection which failed while other login managers (namely kdm) did not. That way you can restart remotely any display manager I know of without fiddling with the DISPLAY variable. Thats why I ask you to accept this bug and maybe change the init script accordingly in order to ignore the DISPLAY variable. If wanted, I can write up a small patch which makes the behaviour configurable via /etc/defaults/lightdm. With kind regards, Jens -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
Hi Daniel, On Tue, Feb 11, 2014 at 12:09:46PM +0100, Daniel Pocock wrote: Looks like the following three packages are impacted by this build dependency: src:abiword src:ball src:resiprocate All those packages need patching to work with the new version of asio due to API changes I admit we have serious trouble wis ball. Despite we worked heavily on the build system to get it at least 99% build and sended patches upstream we did not got any response so far. While a patch is welcome thought we have no idea whether we can keep ball inside Debian. Does the release team have any preference for making this a formal transition or we should just work it out informally between the maintainers of these packages? Markus, please have a brief look at https://wiki.debian.org/Teams/ReleaseTeam/Transitions Since ball never hit testing it is probably not relevant for this problem. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738626: Depending on locale, xmlto creates wrong epub encoding
Package: xmlto Version: 0.0.25.2 Severity: normal When I run xmlto without a certain (UTF) charmap set, an encoding is set into the output epub encoding. As an example, take the developers reference and issue $ LC_ALL=C xmlto epub index.dbk $ unzip -p index.epub OEBPS/index.html|head -1 shows then ?xml version=1.0 encoding=ANSI_X3.4-1968 standalone=no? (LC_ALL=C locale charmap shows ANSI_X3.4-1968 as charmap) However, the encoding of an epub file must be UTF-8 or UTF-16, as one can check by epubcheck: $ epubcheck index.dbk shows errors like Only UTF-8 and UTF-16 encodings are allowed, detected ANSI_X3.4-1968 This problem appears in the generation of the developers-reference package; see also http://bugs.debian.org/738566 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738583: libcglib-java - Uses jarjar without proper copyright or Built-Using
I prepared an update of the cglib package on alioth: - The Built-Using field has been added - debian/copyright now mentions the inclusion of the asm classes - the asm license file is now included in cglib-nodep.jar like the jar distributed by upstream Tony, could you please upload this update if you think it addresses this issue properly? Thank you. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738627: missing copyright in debian/copyright
Package: docker.io Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Hi Paul, the files pkg/mflag/* are under BSD-3 license and contrib/completion/zsh/_docker is BSD (I assume BSD-4, but as the license text is missing, I don't know). So please add those to debian/copyright Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738629: Wrong mimetype file in epub
Package: xmlto
Version: 0.0.25.2
Severity: normal
Tags: patch upstream
xmlto epub generates a mimetype file that contains a newline at the
end. The requirement, however, is a mimetype file just with the string
application/epub+zip, as one can test with the epubcheck program:
(on the developers-reference package)
$ xmlto epub index.dbk
$ epubcheck index.epub
produces an error
Validating against EPUB version 2.0
ERROR: index.epub/mimetype:
Mimetype file should contain only the string application/epub+zip.
The applied patch fixes this; the problem is however in upstream.
Best
Ole
--- xmlto-0.0.25/debian/patches/fix_epub_mimetype.patch
+++ xmlto-0.0.25/debian/patches/fix_epub_mimetype.patch
@@ -0,0 +1,14 @@
+Author: Ole Streicher deb...@liska.ath.cx
+Description: Fix mimetype file in epub.
+ The file must not have a newline at the end.
+--- a/format/docbook/epub
b/format/docbook/epub
+@@ -18,7 +18,7 @@
+ then
+ echo 2 Creating epub file
+ fi
+- echo application/epub+zip mimetype
++ echo -n application/epub+zip mimetype
+ EPUB_NAME=$(basename ${XSLT_PROCESSED%.*}).epub
+ [ -e $XSLT_PROCESSED ] rm $XSLT_PROCESSED
+ ${ZIP_PATH} -0Xq $EPUB_NAME mimetype
--- xmlto-0.0.25/debian/patches/series
+++ xmlto-0.0.25/debian/patches/series
@@ -1,3 +1,4 @@
getopt_noextensions_fix.patch
652974_local_only_in_function.patch
format_fo_passivetex_check.patch
+fix_epub_mimetype.patch
Bug#738628: openrc: initscripts copies break service management
Package: openrc Version: 0.12.4+20131230-8 Severity: normal If there are initscript copies under /etc/init.d, initscript won't be considered at all. root@sid-hurd-i386-0 ~# cp /etc/init.d/exim4 /etc/init.d/exim4.orig root@sid-hurd-i386-0 ~# rc-status * Caching service dependencies ... * Found a solvable dependency loop: checkfs.sh p checkfs n mountall.sh p mountall u hwclock.sh a checkroot n checkfs.sh. * Solving the loop by breaking mountall u hwclock.sh. * Found a solvable dependency loop: checkfs.sh p checkfs n mountall.sh p mountall n mountall-bootclean.sh p mountall-bootclean u hwclock.sh a checkroot n checkfs.sh. * Solving the loop by breaking mountall-bootclean u hwclock.sh. [ ok ] Runlevel: default bootlogs [ started ] buildslave [ started ] motd [ started ] rsyslog [ started ] sudo [ started ] atd [ started ] cron [ started ] dbus [ started ] puppet [ started ] rsync [ started ] ssh [ started ] hurd-console [ started ] rc.local [ started ] rmnologin [ started ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed umountroot [ started ] umountfs [ started ] umountnfs.sh [ started ] Dynamic Runlevel: manual root@sid-hurd-i386-0 ~# rm /etc/init.d/exim4.orig root@sid-hurd-i386-0 ~# rc-status * Caching service dependencies ... * Found a solvable dependency loop: checkfs.sh p checkfs n mountall.sh p mountall u hwclock.sh a checkroot n checkfs.sh. * Solving the loop by breaking mountall u hwclock.sh. * Found a solvable dependency loop: checkfs.sh p checkfs n mountall.sh p mountall n mountall-bootclean.sh p mountall-bootclean u hwclock.sh a checkroot n checkfs.sh. * Solving the loop by breaking mountall-bootclean u hwclock.sh. [ ok ] Runlevel: default bootlogs [ started ] buildslave [ started ] motd [ started ] rsyslog [ started ] sudo [ started ] atd [ started ] cron [ started ] dbus
Bug#738630: missing license in debian/copyright
Package: kid3 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, according to the file header src/plugins/oggflacmetadata/vcedit.h of your pakage is under LGPL. Please add this to debian/copyright. Further it references a file LICENSE.LGPL which is not available in the source tarball. Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On Tue, Feb 11, 2014 at 13:10:55 +0100, Markus Wanner wrote: On 02/11/2014 01:01 PM, Andreas Beckmann wrote: Or if you want to avoid using epochs, reupload 1.4.8 using as 1.10.really.1.4.8 as the upstream version, and upload 1.10 as 1.10.release to experimental. Once you upload upstream 1.11 you are back to normal version numbers without having used an epoch inbetween. Given that we are likely to switch to separate libasio1.4-dev and libasio1.10-dev packages, I think the epoch approach is less confusing, overall. Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Cheers, Julien signature.asc Description: Digital signature
Bug#738556: libaqbanking: Please package and backport 5.3.6beta
Hi Sascha, On 10.02.2014 17:11, Sascha Silbe wrote: please package 5.3.6beta and provide a backport of it for wheezy. I've just uploaded libaqbanking 5.3.6beta-1 to unstable. Once it migrated to testing, I will upload a backport to wheezy-backports. Regards, Micha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728984: base: HDMI audio not working
Hello, Hello, I can't get HDMI sound to work for my ATI card, I believe that this is either a bug with alsa's drivers or with the kernel, as you can see I have set the radeon.audio=1 which should have enabled sound, I am using the proprietary driver. I think the radeon.audio kernel option is for open source driver only. Have you tried with more recent fglrx version ? Catalyst 13.9 is supposed to add some improvements for hdmi audio. Are you using a non-AMD DVI-to-HDMI adapter ? I think I read something on phoronix about HDMI audio troubles when not using the provided DVI-to-HDMI adapter. -- Vincent Alquier vincent.alqu...@gmail.com
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Why is that? Keep in mind this is a headers-only library, i.e. it only ever ships with a -dev (and a -doc) package. There's no other way multiple versions of this library can be installed on a system. Regards Markus Wanner signature.asc Description: OpenPGP digital signature
Bug#735785: ogre-1.8: FTBFS: Could not locate FREETYPE
Control: tags -1 -fixed-upstream +patch
Hi,
On Tue, 11 Feb 2014 11:49:45 +
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote:
There already exists src:ogre-1.9, up to date w.r.t. upstream, and
present in unstable for a few months.
Oops, it's my mistake, investigation is not enough.
src:ogre-1.8 should be fixed if possible anyway, there are rdepends
which didn't move onto 1.9 (and probably not all of their upstreams
are ready).
Okay, then I've created patch for it, please review and consider to
apply it :)
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
diff -Nru ogre-1.8-1.8.0+dfsg1/debian/changelog ogre-1.8-1.8.0+dfsg1/debian/changelog
--- ogre-1.8-1.8.0+dfsg1/debian/changelog 2013-09-08 03:24:10.0 +0900
+++ ogre-1.8-1.8.0+dfsg1/debian/changelog 2014-02-11 21:22:38.0 +0900
@@ -1,3 +1,12 @@
+ogre-1.8 (1.8.0+dfsg1-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches
+- add search_freetype2.5.0_or_above.patch to avoid FTBFS with newer
+ freetype (Closes: #735785)
+
+ -- Hideki Yamane henr...@debian.org Tue, 11 Feb 2014 21:22:37 +0900
+
ogre-1.8 (1.8.0+dfsg1-6) unstable; urgency=low
* Document some files missing in debian/copyright
diff -Nru ogre-1.8-1.8.0+dfsg1/debian/patches/search_freetype2.5.0_or_above.patch ogre-1.8-1.8.0+dfsg1/debian/patches/search_freetype2.5.0_or_above.patch
--- ogre-1.8-1.8.0+dfsg1/debian/patches/search_freetype2.5.0_or_above.patch 1970-01-01 09:00:00.0 +0900
+++ ogre-1.8-1.8.0+dfsg1/debian/patches/search_freetype2.5.0_or_above.patch 2014-02-11 21:26:16.0 +0900
@@ -0,0 +1,26 @@
+Description: also checks newer freetype version
+Bug-Debian: http://bugs.debian.org/735785
+Last-Update: 2014-02-10
+
+Index: ogre-1.8-1.8.0+dfsg1/CMake/Packages/FindFreetype.cmake
+===
+--- ogre-1.8-1.8.0+dfsg1.orig/CMake/Packages/FindFreetype.cmake 2014-02-11 21:21:00.0 +0900
ogre-1.8-1.8.0+dfsg1/CMake/Packages/FindFreetype.cmake 2014-02-11 21:26:14.998906335 +0900
+@@ -31,7 +31,7 @@
+ FREETYPE_INCLUDE_DIR
+ )
+
+-set(FREETYPE_LIBRARY_NAMES freetype249 freetype248 freetype246 freetype2311 freetype239 freetype238 freetype235 freetype219 freetype)
++set(FREETYPE_LIBRARY_NAMES freetype251 freetype2501 freetype250 freetype249 freetype248 freetype246 freetype2311 freetype239 freetype238 freetype235 freetype219 freetype)
+ get_debug_names(FREETYPE_LIBRARY_NAMES)
+
+ use_pkgconfig(FREETYPE_PKGC freetype2)
+@@ -43,7 +43,7 @@
+ findpkg_framework(FREETYPE)
+ message(STATUS CMAKE_PREFIX_PATH: ${CMAKE_PREFIX_PATH})
+
+-find_path(FREETYPE_INCLUDE_DIR NAMES freetype/freetype.h HINTS ${FREETYPE_INC_SEARCH_PATH} ${FREETYPE_PKGC_INCLUDE_DIRS} PATH_SUFFIXES freetype2)
++find_path(FREETYPE_INCLUDE_DIR NAMES freetype2/freetype.h HINTS ${FREETYPE_INC_SEARCH_PATH} ${FREETYPE_PKGC_INCLUDE_DIRS} PATH_SUFFIXES freetype2)
+ find_path(FREETYPE_FT2BUILD_INCLUDE_DIR NAMES ft2build.h HINTS ${FREETYPE_INC_SEARCH_PATH} ${FREETYPE_PKGC_INCLUDE_DIRS})
+
+ if (SYMBIAN)
diff -Nru ogre-1.8-1.8.0+dfsg1/debian/patches/series ogre-1.8-1.8.0+dfsg1/debian/patches/series
--- ogre-1.8-1.8.0+dfsg1/debian/patches/series 2013-09-04 05:42:45.0 +0900
+++ ogre-1.8-1.8.0+dfsg1/debian/patches/series 2014-02-11 21:21:00.0 +0900
@@ -1,2 +1,3 @@
boost.patch
remove-alignment-hack.patch
+search_freetype2.5.0_or_above.patch
Bug#738593: openssh-server: changelog mis-description, ... upgrades create ed25519 host keys as well
On Tue, 2014-02-11 at 11:19 +, Colin Watson wrote: Oops, right. No real problem... I'm just a perfectionist... even regarding typos in changelogs ;) I'll retroactively correct the changelog. (You still need to add the HostKey entry manually on upgrades.) Actually I didn't understand that at all.. why do you need that? It seems to be that ssh looks per default at /etc/ssh/ssh_host_ed25519_key AFAIU the 6.5 release notes, ED25519, should be used per default (when client/server both support it)... but it seems the case,... the default for HostKeyAlgorithms seems to still have ECDSA first, while KexAlgorithms prefers Curve25519 now... Any idea about that? Well, that's why I prefer to do this in the postinst rather than at boot time as some other distributions do, as I think it's much more likely that sufficient entropy will be available when installing packages. Sure... that's already much much better than what other distros do... but it might be still not enough in some corner cases... anyway as I said... I'm not really sure whether I'd prefer to not have that initialised at all. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#738631: gnome-screensaver: Please re-enable the lock-screen feature for Jessie/testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: gnome-screensaver Version: 3.6.1-1 Severity: minor Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** - -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.9caec (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-screensaver depends on: ii dbus-x11 1.8.0-1 ii gnome-icon-theme 3.10.0-1 ii gnome-session-bin 3.8.4-3 ii gsettings-desktop-schemas 3.8.2-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libdbus-1-31.8.0-1 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-0 2.36.4-1 ii libgnome-desktop-3-7 3.8.4-2 ii libgnomekbd8 3.6.0-1 ii libgtk-3-0 3.8.6-1 ii libpam0g 1.1.3-10 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxklavier16 5.2.1-1 ii libxxf86vm11:1.1.3-1 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.8.2-1 ii libpam-gnome-keyring 3.8.2-2+b1 gnome-screensaver suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL6G3IACgkQ5+rBHyUt5wvR7gCeKn4TXvzD8pkZlQFKbatQlHjc pu4An09WBwtPqOgfnj9g1N+4uiSx74gu =NYDW -END PGP SIGNATURE-
Bug#738632: icedtea-netx: split javaws 6 7 to different packages
Package: icedtea-netx Version: 1.4.2-1 Severity: wishlist Tags: upstream Dear Maintainer, I suggest to split package to icedtea-6-netx and icedtea-7-netx (or similar) to avoid have 2 different versions of javaws on the user's machines. I use now openjdk-7, but until I run update-alternatives (yes, I don't use default-jre), javaws by default sets to version 6. On top of everything, why I must have unused version on my desktop? Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (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 Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.4.2-1 ii openjdk-7-jre7u51-2.4.5-2 icedtea-netx recommends no packages. icedtea-netx 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#738633: pandoc: Newer version available and query about excluded files
Package: pandoc Version: 1.12.2.1-1+b2 Severity: wishlist Version 1.12.3.3 is now available, which will hopefully fix some bugs I'm experiencing. Also, I don't understand why LaTeXMathML.js is excluded: it is just a compressed version of the GPL'd original available from http://math.etsu.edu/LaTeXMathML/LaTeXMathML.js with description available from http://math.etsu.edu/LaTeXMathML/ (in raw LaTeX?!). So it does appear to be DFSG-free, AFAICT. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738575: pthread: segfault in libpthread on Intel Galileo board
The default toolchain (and thus libc) in Debian has been targetting i586 for quite a while now. If this CPU doesn't provide *all* the i586 instructions, I'd be pretty surprised if anything worked. I was first trending in the same direction, but this is a different issue. I compiled code with instructions that aren't working on Quark. The issue you get then is an 'invalid instruction exception', not a segfault. If you use gcc and the '-march=i586' option, the code that is generated is fine for Quark. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On 11/02/14 13:44, Markus Wanner wrote: On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Why is that? Keep in mind this is a headers-only library, i.e. it only ever ships with a -dev (and a -doc) package. There's no other way multiple versions of this library can be installed on a system. Julien, Fedora and EPEL6 still have 1.4.8 as well. We don't know how widely it is used in things that are not packaged (e.g. in private code that people run on Debian) If we release a versions libasio1.4-dev package and libasio1.10-dev concurrently in jessie it will mean people can transition more slowly but nothing will really break -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738634: qemuctl: Frontend is not workable for ARM, forgets saved settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: qemuctl Version: 0.3.1-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** I tried the qemu-launcher for both ARM-architectures, because I was not sure, which of the two is the right one. Qemu should be able to boot from the armel-netinstall-CD-ISO, but this was not workable at all. When I restarted the software now, I saw, that my settings are gone. If the software is not workable, then I would recommend to completely leave it away, because it frustrates people only, who try to use it. - -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.9caec (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qemuctl depends on: ii libc6 2.17-97 ii libgcc1 1:4.8.2-14 ii libqt4-network 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtcore4 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1 ii libstdc++6 4.8.2-14 ii libx11-62:1.6.2-1 ii libxext62:1.3.2-1 ii qemu1.7.0+dfsg-3 Versions of packages qemuctl recommends: ii qemu-launcher 1.7.4-1 qemuctl suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL6H0kACgkQ5+rBHyUt5wsYFwCeN1rFyjWQu0HhokA0aFFWXgiK 3boAn2JPyUSwVV1Qz1jmpt96qL3yZIBg =UN8Y -END PGP SIGNATURE-
Bug#731300: Patch link
This link was provided also in a control message, but I'll report here for convenience. https://raw2.github.com/linuxmint/systemd/master/debian/patches/pam-check-runtime-dir-user.patch -- ESC:wq
Bug#738616: removing newer libasio-dev (v1.10) from unstable
On Tue, Feb 11, 2014 at 13:58:17 +0100, Daniel Pocock wrote: On 11/02/14 13:44, Markus Wanner wrote: On 02/11/2014 01:40 PM, Julien Cristau wrote: Please try to avoid versioned -dev packages. Unless you really really have to keep both versions around for years. Why is that? Keep in mind this is a headers-only library, i.e. it only ever ships with a -dev (and a -doc) package. There's no other way multiple versions of this library can be installed on a system. Julien, Fedora and EPEL6 still have 1.4.8 as well. We don't know how widely it is used in things that are not packaged (e.g. in private code that people run on Debian) That's irrelevant, as far as I'm concerned. If we release a versions libasio1.4-dev package and libasio1.10-dev concurrently in jessie it will mean people can transition more slowly but nothing will really break And if you don't they can still use the old version, either through the old package or through an unpackaged local version. Shipping libraries in Debian only makes sense if Debian packages use them, IMO. Cheers, Julien signature.asc Description: Digital signature
Bug#499498: asciidoc: [manual] page is missig section EXAMPLES
forwarded 499498 https://github.com/asciidoc/asciidoc/pull/8 tags 499498 + upstream thanks Dear Jari, I added an example section to the asciidoc manpage and sent a pull request to upstream. You can find the content and follow the evolution of it at: https://github.com/asciidoc/asciidoc/pull/8 Tell me if you have remarks. Best regards, Joseph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725703: Please enable zswap in wheezy-backports
Compiling zswap support would be much appreciated, especially on low memory systems. Thanks.
Bug#738593: openssh-server: changelog mis-description, ... upgrades create ed25519 host keys as well
On Tue, Feb 11, 2014 at 01:30:35PM +0100, Christoph Anton Mitterer wrote: On Tue, 2014-02-11 at 11:19 +, Colin Watson wrote: I'll retroactively correct the changelog. (You still need to add the HostKey entry manually on upgrades.) Actually I didn't understand that at all.. why do you need that? It seems to be that ssh looks per default at /etc/ssh/ssh_host_ed25519_key Only if HostKey isn't specified at all, and we have long included explicit HostKey directives in our stock sshd_config. AFAIU the 6.5 release notes, ED25519, should be used per default (when client/server both support it)... but it seems the case,... the default for HostKeyAlgorithms seems to still have ECDSA first, while KexAlgorithms prefers Curve25519 now... That'd be something to bring up with upstream, I think. I'm not an expert on the serious crypto involved in OpenSSH. Cheers, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738634: Settings were not forgotten
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When trying this again now, I found, that my settings were not forgotten, they were only saved under a different name than 'Default', they were selectable. I also fail to display the qemu-command-line that was produced, maybe this is the problem. All qemu-system-man-pages display qemu-system-i386 only, seem to be symlinks. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL6Ip4ACgkQ5+rBHyUt5wu61gCfYH3EbLQoXwIenmcWwxlukr5C xKsAnRtMYm1I+cMubOkdD2k2s5mPR3b3 =p+qL -END PGP SIGNATURE-
