Bug#768598: NMUdiff for patch to fix this bug
Control: tag -1 patch pending
Below please find the NMU diff which fixes #768599 (from fontconfig's
end). This will still need Breaks in dpkg. I have uploaded this to
delayed/2. Please override with a maintainer upload if necessary.
diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog 2014-08-20 06:36:05.0 -0700
+++ fontconfig-2.11.0/debian/changelog 2014-11-10 11:30:45.0 -0800
@@ -1,3 +1,13 @@
+fontconfig (2.11.0-6.2) unstable; urgency=medium
+
+ * Non-maintainer upload to delayed
+ * Switch to noawait triggers to allow self-triggering; will still need
+Breaks from dpkg to resolve this (closes: #768599)
+ * Add Pre-Depends on dpkg to allow for noawait just in case this gets
+backported to squeeze.
+
+ -- Don Armstrong d...@debian.org Mon, 10 Nov 2014 11:26:37 -0800
+
fontconfig (2.11.0-6.1) unstable; urgency=low
* Non-maintainer upload to delayed.
diff -Nru fontconfig-2.11.0/debian/control fontconfig-2.11.0/debian/control
--- fontconfig-2.11.0/debian/control2014-08-20 06:32:13.0 -0700
+++ fontconfig-2.11.0/debian/control2014-11-10 11:28:42.0 -0800
@@ -18,6 +18,7 @@
Section: fonts
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, fontconfig-config
+Pre-Depends: dpkg (= 1.16.1)
Replaces: fontconfig-config ( 2.5.93-1)
Multi-Arch: foreign
Description: generic font configuration library - support binaries
diff -Nru fontconfig-2.11.0/debian/fontconfig.triggers
fontconfig-2.11.0/debian/fontconfig.triggers
--- fontconfig-2.11.0/debian/fontconfig.triggers2013-06-25
11:12:30.0 -0700
+++ fontconfig-2.11.0/debian/fontconfig.triggers2014-11-10
11:28:03.0 -0800
@@ -1,3 +1,3 @@
-interest /usr/share/fonts
-interest /usr/share/ghostscript/fonts
-interest /usr/share/texmf/fonts
+interest-noawait /usr/share/fonts
+interest-noawait /usr/share/ghostscript/fonts
+interest-noawait /usr/share/texmf/fonts
--
Don Armstrong http://www.donarmstrong.com
Junkies were all knitted together in a loose global macrame, the
intercontinental freemasonry of narcotics.
-- Bruce Sterling, _Holy Fire_ p257
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770003: unblock lilypond/2.18.2-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is a simple fix for the RC bug #768272:
diff -Nru lilypond-2.18.2/debian/changelog lilypond-2.18.2/debian/changelog
--- lilypond-2.18.2/debian/changelog2014-09-26 11:43:19.0 -0700
+++ lilypond-2.18.2/debian/changelog2014-11-16 17:38:32.0 -0800
@@ -1,11 +1,20 @@
+lilypond (2.18.2-4) unstable; urgency=medium
+
+ * Fix the wrong maintscript-helper invocation which was trying to
+symlink to /usr/share/doc/lilypond/Documentation/user instead of
+/usr/share/doc/lilypond/Documentation. (Closes: #768272)
+ * Add missing Pre-Depends: ${misc:Depends} for dpkg-maintscript-helper.
+
+ -- Don Armstrong d...@debian.org Sun, 16 Nov 2014 17:38:32 -0800
+
lilypond (2.18.2-3) unstable; urgency=medium
* Revert previous patch (no parallel); the issue was actually running
tests on architecture independent builds which had not built any of
the documentation. (Closes: #760794)
* Stop setting HOME to /tmp in debian/rules. (Closes: #762230)
-- Don Armstrong d...@debian.org Tue, 16 Sep 2014 14:50:14 -0700
lilypond (2.18.2-2) unstable; urgency=high
diff -Nru lilypond-2.18.2/debian/control lilypond-2.18.2/debian/control
--- lilypond-2.18.2/debian/control 2014-09-25 15:34:19.0 -0700
+++ lilypond-2.18.2/debian/control 2014-11-16 17:36:59.0 -0800
@@ -66,6 +66,7 @@
Package: lilypond-doc
Section: doc
Architecture: all
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, dpkg (= 1.15.4) | install-info
Recommends: lilypond-doc-html, lilypond-doc-pdf
Suggests: lilypond (= ${source:Version})
diff -Nru lilypond-2.18.2/debian/lilypond-doc.maintscript
lilypond-2.18.2/debian/lilypond-doc.maintscript
--- lilypond-2.18.2/debian/lilypond-doc.maintscript 2014-09-03
12:33:29.0 -0700
+++ lilypond-2.18.2/debian/lilypond-doc.maintscript 2014-11-11
14:19:22.0 -0800
@@ -1 +1 @@
-symlink_to_dir /usr/share/info/lilypond
/usr/share/doc/lilypond/html/Documentation/user 2.18.2-1~
+symlink_to_dir /usr/share/info/lilypond
/usr/share/doc/lilypond/html/Documentation 2.18.2-4~
--
Don Armstrong http://www.donarmstrong.com
I will not make any deals with you. I've resigned. I will not be
pushed, filed, stamped, indexed, briefed, debriefed or numbered. My
life is my own. I resign.
-- Patrick McGoohan as Number 6 in The Prisoner
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769747: [PATCH] debian/control: switch order of systemd-sysv|systemd-shim dependencies for libpam-systemd. (Closes: #769747)
Control: tag -1 patch
---
debian/changelog | 4
debian/control | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index cf3c3af..6fc4716 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,10 @@ systemd (215-6) UNRELEASED; urgency=medium
* debian/ifup@.service: add a ConditionPath on /run/network, to avoid
failing the unit if /etc/init.d/networking is disabled. (Closes: #769528)
+ [ Don Armstrong ]
+ * debian/control: switch order of systemd-sysv|systemd-shim dependencies
+for libpam-systemd. (Closes: #769747)
+
-- Martin Pitt mp...@debian.org Sun, 12 Oct 2014 17:29:00 +0200
systemd (215-5) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 75986c1..cbd2d6a 100644
--- a/debian/control
+++ b/debian/control
@@ -112,7 +112,7 @@ Depends: ${shlibs:Depends},
systemd (= ${binary:Version}),
libpam-runtime (= 1.0.1-6),
dbus,
- systemd-sysv | systemd-shim (= 8-2)
+ systemd-shim (= 8-2) | systemd-sysv
Description: system and service manager - PAM module
systemd is a replacement for sysvinit. It is dependency-based and
able to read the LSB init script headers in addition to parsing rcN.d
--
2.1.0
--
Don Armstrong http://www.donarmstrong.com
The attackers hadn't simply robbed the bank. They had carried off
everything portable, including the security cameras, the carpets, the
chairs, and the light and plumbing fixtures. The conspirators had
deliberately punished the bank, for reasons best known to themselves,
or to their unknown controllers. They had superglued doors and
shattered windows, severed power and communications cables, poured
stinking toxins into the wallspaces, and concreted all of the sinks
and drains. In eight minutes, sixty people had ruined the building so
thoroughly that it had to be condemned and later demolished.
-- Bruce Sterling, _Distraction_ p4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769747: [PATCH] debian/control: switch order of systemd-sysv|systemd-shim dependencies for libpam-systemd. (Closes: #769747)
On November 16, 2014 10:29:21 PM PST, Martin Pitt mp...@debian.org wrote: Hey Don, Don Armstrong [2014-11-16 14:14 -0800]: Control: tag -1 patch whoops, I'm afraid I saw your patch too late, I alraedy committed http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=26a8a43 when going through my Debian mailbox this morning. But it's essentially the same (obvious) thing with just a different changelog. Cool! Thanks for taking care of that. No worries about the patch; I just wanted to make sure one was present. -- This is not a signature. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746578: Revised call for votes (was libpam-systemd to flip dependencies - proposal)
Control: clone -1 -2 Control: reassign -2 libpam-systemd Control: tag -2 -wontfix Control: found -2 215-5 Control: retitle -2 libpam-system: please switch the dependency ordering in light of the CTTE decision in #746578 Control: close -1 On Sat, 15 Nov 2014, Don Armstrong wrote: As the voting period has now expired (1 week), the results are 5 0, and Y is the winner. Reassigning a clone of this bug back to libpam-systemd. Systemd maintainers: If you'd prefer for someone else to prepare the patch to apply the CTTE ruling, please let me know, and I'll be glad to do it. -- Don Armstrong http://www.donarmstrong.com America was far better suited to be the World's Movie Star. The world's tequila-addled pro-league bowler. The world's acerbic bi-polar stand-up comedian. Anything but a somber and tedious nation of socially responsible centurions. -- Bruce Sterling, _Distraction_ p122 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746578: Revised call for votes (was libpam-systemd to flip dependencies - proposal)
On Wed, 05 Nov 2014, Ian Jackson wrote: (My previous vote of Y,FD stands.) On Wed, 05 Nov 2014, Russ Allbery wrote: I vote Y, FD on the following. On Wed, 05 Nov 2014, Don Armstrong wrote: I vote Y FD. On Mon, 10 Nov 2014, Bdale Garbee wrote: I vote Y FD. On Wed, 12 Nov 2014, Andreas Barth wrote: I vote Y, FD As the voting period has now expired (1 week), the results are 5 0, and Y is the winner. I will announce the decision to -announce shortly. -- Don Armstrong http://www.donarmstrong.com You know, said Arthur, it's at times like this, when I'm trapped in a Vogon airlock with a man from Betelgeuse, and about to die from asphyxiation in deep space that I really wish I'd listened to what my mother told me when I was young. Why, what did she tell you? I don't know, I didn't listen. –- Douglas Adams _The Hitchhikers Guide To The Galaxy_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769050: sra-toolkit should only install binaries, not symlinks to symlinks to binaries
Package: src:sra-sdk Version: 2.3.5-2+dfsg-1 Severity: minor Since sra-toolkit isn't co-installable with another version, it should just install the binaries, and not symlinks which are two levels deep. -- Don Armstrong http://www.donarmstrong.com When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. -- Edmund Burke Thoughts on the Cause of Present Discontents -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769051: fr_CA locale has wrong weekday start (should be 1, not 2)
Package: locales Version: 2.13-38 Control: found -1 2.19-12 Control: submitter -1 ste...@openmailbox.org On Mon, 10 Nov 2014, Stephane R. wrote: It's imposible include the name of the package because it's a bad locate configuration file!!! The name of the package you want is locales. dpkg -S locales/fr_CA; will give you that information Date: Mon, 10 Nov 2014 18:41:27 -0500 From: Stephane R. ste...@openmailbox.org To: sub...@bugs.debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 Subject: fr_CA locale error French Canadian locale error in Wheezy and Jessie In this file: /usr/share/i18n/locales/fr_CA Please replace first_weekday 2 by first_weekday 1. The french canadian use only a calendar begin by the Sunday, not the Monday same the european. -- . Stéphane R. -- Don Armstrong http://www.donarmstrong.com If I had a letter, sealed it in a locked vault and hid the vault somewhere in New York. Then told you to read the letter, thats not security, thats obscurity. If I made a letter, sealed it in a vault, gave you the blueprints of the vault, the combinations of 1000 other vaults, access to the best lock smiths in the world, then told you to read the letter, and you still can't, thats security. -- Bruce Schneier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746578: Revised call for votes (was libpam-systemd to flip dependencies - proposal)
On Wed, 05 Nov 2014, Ian Jackson wrote: I am calling for votes on the text below: Y (override, swap dependencies, requires 3:1) FD I vote Y FD. -- Don Armstrong http://www.donarmstrong.com Whatever you do will be insignificant, but it is very important that you do it. -- Mohandas Karamchand Gandhi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767966: init script does not handle inet sockets correctly
Control: severity -1 minor Control: retitle -1 don't require setting SOCKETOWNER and SOCKETMODE in the case of inet sockets; avoid deleting in the case of inet sockets too. On Mon, 03 Nov 2014, Kevin Niehage wrote: That happens because the checks within the init script do not handle inet sockets at all, e.g. have a look at the stop() function: Actually, it does try handle them, but it probably could do better. You can get around this particular issue just by setting SOCKETOWNER= and SOCKETMODE=, which is even documented in /usr/share/doc/spamass-milter/README.Debian as the method to use inet sockets. -- Don Armstrong http://www.donarmstrong.com I would like to be the air that inhabits you for a moment only. I would like to be that unnoticed that necessary. -- Margaret Atwood Poetry in Motion p140 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762194: Call for Votes (re automatic switching)
On Sun, 02 Nov 2014, Ian Jackson wrote: Russ Allbery writes (Bug#762194: automatic switching - two proposals): Ian Jackson ijack...@chiark.greenend.org.uk writes: I intend to call for votes later today. This looks great to me, Ian. Thank you! Thanks. I hereby call for votes on the text below. There are two options: Y. Clarify decison and invite non-auto-switching proposals FD. Further discussion I vote Y FD. Don Armstrong -- Don Armstrong http://www.donarmstrong.com If it jams, force it. If it breaks, it needed replacing anyway. -- Lowery's Law -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767152: bugs.debian.org: Graph in upper right reasonably incomprehensible
On Tue, 28 Oct 2014, Karl O. Pinc wrote: The graphic graph that appears in the upper right of the pages of individual bugs would be entirely incomprehensible were it not for the URLs that appear in the browser on mouseover. Just click on the image. The size is currently a trade off between being readable and not being in the way of everything else on the page. [These graphs get *huge*, and the shapes and colors are sometimes more informative than the actual names.] Perhaps the image could be made a svg so at least it could be read when enlarged? If you want it as an SVG, that works too; just change format=png in the url to format=svg. I don't have that as an option, because the blown up png is generally large enough. -- Don Armstrong http://www.donarmstrong.com I'm So Meta, Even This Acronym -- xkcd http://xkcd.com/917/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767152: bugs.debian.org: Graph in upper right reasonably incomprehensible
Control: retitle -1 consider expanding the version graph on mouseover Control: severity -1 wishlist On Tue, 28 Oct 2014, Karl O. Pinc wrote: I assumed that clicking on the various nodes would take me to information specific to that node. (I'm kind of leery about clicking on things when I don't know what they do.) Might be nicer if mouseover expanded the graphic... This is possible, but it would mean that mousing over did the same thing that clicking on the image did, and would require javascript to actually do the right thing and avoid downloading the image on every page view. I don't really think that's desirable, but I could be convinced otherwise. On Tue, 28 Oct 2014, Karl O. Pinc wrote: Since it's not supposed to be readable, perhaps the thing to do is to shrink it even further to make it obviously not readable. The graphic elements should be recognizable (and have whatever utility they have) at at least 1/2 the present linear dimensions. In very simple cases, it might still be readable. The maximum size of the graph is fixed; it'll handle simple cases (linear tree, one fixed version, one found version), but when the graph gets bigger, it's not readable. -- Don Armstrong http://www.donarmstrong.com To steal ideas from one person is plagiarism; to steal from many is research. -- Steven Wright -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767159: bugs.debian.org: Add debian release version info to graphic found in header
On Tue, 28 Oct 2014, Karl O. Pinc wrote: While I can imagine that package version information regards what versions the bug appears in is useful to somebody, what I would find really useful is the version of Debian (or the codename) in which the bug was found or fixed. That's why I currently include them both in the version graph. I assume that's what we're talking about here. In the interest of reducing clutter I'd be happy to see the package version information entirely replaced with Debian release version information. (Others may disagree.) The found/fixed is the values that the bug is actually set to. Whether those versions correspond to a particular version changes over time. Now, it might be nice to have a little table which told you whether a bug was was present, fixed, or absent in a suite of Debian releases... but I don't think that's what you're asking for. -- Don Armstrong http://www.donarmstrong.com Physics is like sex. Sure, it may give some practical results, but that's not why we do it. -- Richard Feynman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767159: bugs.debian.org: Add debian release version info to graphic found in header
Control: retitle -1 create table showing bug status in different Debian releases in bugreport.cgi On Wed, 29 Oct 2014, Karl O. Pinc wrote: What I'm interested in is something that stands out from the clutter and tells me if the problem is fixed in the version of Debian that I'm running. Whatever works. OK. (Are there really so many Debian versions that a table is called for?) There are five. -- Don Armstrong http://www.donarmstrong.com It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766708: Processed: Re: Bug#766708: breaks multiarch cross building
Control: clone -1 -2 Control: reassign -2 gcc-4.9 Control: found -2 gcc-4.9/4.9.1-19 Control: block -2 by -1 Control: retitle -1 Request to override gcc maintainer changes breaking multiarch cross-building I'm keeping the original bug with the CTTE, and reassinging a clone back to gcc-4.9; keeping the original bug with the CTTE. Matthias: is the primary concern of including this patch one of maintenance burden, not primarily technical? Could you provide some background for the CTTE on how much maintenance burden we're talking about, and what recent bugs have resulted from this particular patchset? -- Don Armstrong http://www.donarmstrong.com Let the victors, when they come, When the forts of folly fall Find thy body by the wall! -- Matthew Arnold -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766374: X Server not available after Sid update on 21 Oct.
Control: retitle -1 gdm3 fails to load login screen (with less-than-useful error message) Control: severity -1 important Control: tag -1 moreinfo Control: reassign -1 gdm3 Control: found -1 3.14.1-1 On Thu, 23 Oct 2014, Jürgen Kleber wrote: after updating the system on 21 Oct. the X server was no longer working. For details, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766374 . Does anybody have a Sid-System (AMD64; as a second system, not for daily use) and could post the issue of apt-get update / apt-get dist-upgrade to this list? This particular issue may be a bug in gdm3, not the X server. (If the X server wasn't starting, you generally wouldn't see any output at all.) Someone else may be able to give you more information on how you can debug this problem in gdm3. -- Don Armstrong http://www.donarmstrong.com We must realize that today's Establishment is the New George III. Whether it will continue to adhere to his tactics, we do not know. If it does, the redress, honored in tradition, is also revolution. -- William O. Douglas _Points of Rebellion_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766374: X Server not available after Sid update on 21 Oct.
On Thu, 23 Oct 2014, Jürgen Kleber wrote: I did not mention yet that I tried lightdm/xfce4 - and it failed, too. You should assign the bug additionally to lightdm. What was output to syslog when you did this? What versions of these packages did you have installed? What is output to ~/.xsession-errors for your user? Do you have anything in ~/.config/autostart/? If so, try deleting it first. -- Don Armstrong http://www.donarmstrong.com Maybe I did steal your heart and I am such a perfect criminal that you never noticed -- a softer world #481 http://www.asofterworld.com/index.php?id=481 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763434: Example: Bug #721310
On Wed, 22 Oct 2014, Andreas Glaeser wrote: https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3ADesktop;dist=testing;package=gnome-tweak-tool Result: none https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745392 is that bug. This has been resolved, but I have no idea under which number it was filed, or if it was renamed or reassigned, closed... https://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=bugs.andreas.glae...@freenet.de;archive=both the above has all of your bugs; you could use this page to narrow down to the original bug that you were looking for instead of the per-package search page. But that said, eventually I will have the bug content searching working again. -- Don Armstrong http://www.donarmstrong.com I have no use for before and after pictures. I can't remember starting, and I'm never done. -- a softer world #221 http://www.asofterworld.com/index.php?id=221 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765421: jmapviewer: Download bing logo via attribution XML at runtime?
On Mon, 20 Oct 2014, Felix Natter wrote: IMHO the question is: Under which license are we allowed to use http://dev.virtualearth.net/REST/v1/Imagery/Metadata/Aerial?include=ImageryProvidersoutput=xmlkey=... (the REST Service for Bing maps) at all? The fact that this is a restriction on use is a bit problematic, just from an end-user point of view. [I don't believe this affects its DFSG status, since it works with free data sources just fine.] It would probably be ideal if the user was warned about potentially restrictive data sources when they enabled them the first time too; this would give them a chance to do due diligence. (Or even when the program first started if the program already had some equivalent feature.) [And if it already does so, ignore my critique; I'm not familiar with this software beyond following your efforts to clean up the DFSG status with regards to the Bing logo.] At the very least, I'd stick a note in NEWS.Debian.gz. Thanks again for working on making this software DFSG free. -- Don Armstrong http://www.donarmstrong.com Whatever you do will be insignificant, but it is very important that you do it. -- Mohandas Karamchand Gandhi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765054: libapache-gallery-perl: FTBFS - undefined symbol: modperl_is_running
Control: reassign -1 libapache2-mod-perl2 Control: forcemerge 765174 -1 Control: affects -1 libapache-gallery-perl On Mon, 13 Oct 2014, Michael Tautschnig wrote: During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] debian/rules override_dh_auto_test make[1]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-libapache-gallery-perl/libapache-gallery-perl-1.0.2' MOD_PERL_API_VERSION=2 dh_auto_test; make[2]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-libapache-gallery-perl/libapache-gallery-perl-1.0.2' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -MTest::Harness -e undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch') t/*.t # Failed test 'use Apache::Gallery;' # at t/001_use.t line 3. # Tried to use 'Apache::Gallery'. # Error: Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.20/auto/APR/APR.so' for module APR: /usr/lib/x86_64-linux-gnu/perl5/5.20/auto/APR/APR.so: undefined symbol: modperl_is_running at /usr/lib/x86_64-linux-gnu/perl/5.20/DynaLoader.pm line 187. # at /usr/lib/x86_64-linux-gnu/perl5/5.20/APR/Table.pm line 23. Yeah, this looks like the same bug (now #765174) in libapache2-mod-perl2, not really a bug in Apache::Gallery. I'll just mark it as affecting libapache-gallery-perl in case someone else runs into it. Thanks for doing the rebuild and finding these bugs! -- Don Armstrong http://www.donarmstrong.com listen, what you do in the privacy of your neighbour's house while they're away is your own business -- a softer world #511 http://www.asofterworld.com/index.php?id=511 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763434: Example: Bug #721310
On Mon, 13 Oct 2014, Andreas Glaeser wrote: I searched for bugs in packages gnome-tweak-tool and audacity, then src:audacity and src:gnome-tweak-tool, but currently the search-function by subject seems to be completely disabled. Searching by subject still does what it originally did; it allows you to exclude or only include specific bugs in a set which was already returned by another selection statement. I guess this is due to maintenace work? There's no ongoing maintenance work. Please provide specific URLs that you are viewing, and specific bugs which you expected to see but which were not returned. It's very difficult for me to know precisely what is going wrong if I don't have concrete examples. -- Don Armstrong http://www.donarmstrong.com It was a very familiar voice. [...] It was a voice you could have used to open a bottle of whine. -- Terry Pratchett _The Last Continent_ p270 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760347: Looks like emails are making it into the archive but people aren't getting them.
On Sat, 11 Oct 2014, Brian Gupta wrote: Can you please double check things? People aren't getting mail but they are showing up in the archives. Mail is being sent out properly: Oct 12 05:21:48 s_local@bendel postfix/smtp[18345]: AF02B14F8: to=brian.gu...@brandorr.com, relay=aspmx.l.google.com[74.125.143.27]:25, delay=0.85, delays=0.02/0.02/0.27/0.54, dsn=2.0.0, status=sent (250 2.0.0 OK 1413091308 o1si16348789lal.39 - gsmtp) for example. -- Don Armstrong http://www.donarmstrong.com One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758787: Just like to confirm this on 14.10
On Thu, 02 Oct 2014, Akiva wrote: Did a fresh install of the latest beta, and what I did was sudo'd a bash script full of sudo apt-get install xx commands. And that is when I started noticing problems after everything was said and done. Now I can only run programs as Root, as doing otherwise gives me permission errors. Installing and uninstalling gives me that damn symlink issue, and my whole system is paralyzed. This issue has been fixed in all Debian releases. If you're not running a Debian release, then you'll either have to manually remove the symlink, or remove lilypond-doc and install the new version. -- Don Armstrong http://www.donarmstrong.com Fate and Temperament are two words for one and the same concept. -- Novalis [Hermann Hesse _Demian_] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763434: Example: Bug #721310
On Thu, 02 Oct 2014, Andreas Glaeser wrote: I searched for the term 'Futro S450' in package installation-reports: https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3AFutro+S450;dist=testing;package=installation-reports and found this archived bug only: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699691 When I search for something from the new title 'ACPI_INITRD_TABLE_OVERRIDE' instead: https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3AACPI_INITRD_TABLE_OVERRIDE;dist=testing;package=installation-reports The above looks for bugs in installation-reports which have the given subject. This actually searches for bugs in src:linux which have the given subject: https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3AACPI_INITRD_TABLE_OVERRIDE;dist=testing;package=src:linux and returns the expected result. You're right that searching by subject across all bugs would be useful; this used to be possible with the search interface, and will be possible again in the future. However, the code currently only supports limiting the bugs returned by a previous search by subject. -- Don Armstrong http://www.donarmstrong.com Them as can do has to do for them as can't. And someone has to speak up for them as have no voices. -- Grandma Aching in _The Wee Free Men_ by Terry Pratchett p227 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763434: debbugs: retitled reports are found neither by old nor by new title/subject
On Tue, 30 Sep 2014, Andreas Glaeser wrote: it is not a big issue, but maybe it is worth fixing it. You'll have to provide more information; I'm not sure what you mean. When a bug report is retitled, the title definitely changes... -- Don Armstrong http://www.donarmstrong.com 2: There is no out. There is only in. -- The Prisoner (2009 Miniseries) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762967: XSS in bugs.debian.org/cgi-bin/version.cgi
On Sat, 27 Sep 2014, Vlad Constantin wrote:
I'll add to this bug instead of making a new one.
/cgi-bin/cookies.cgi contains XSS (persistent via cookie) and Header
injection vulnerabilities in vars repeatmerged, terse, reverse, trim,
oldview
XSS PoC:
https://bugs.debian.org/cgi-bin/cookies.cgi?repeatmerged=%3Cscript%3Ealert('xss')%3B%3C/script%3E
Header injection PoC:
https://bugs.debian.org/cgi-bin/cookies.cgi?repeatmerged=%0aLocation%3A%20http%3A%2F%2Fgoogle.com%2F%0a
Thanks for reporting these; those scripts probably shouldn't even be in
use at all. I've already removed them from bugs.debian.org, and I'll
probably eliminate them from git shortly.
--
Don Armstrong http://www.donarmstrong.com
There's no problem so large it can't be solved by killing the user
off, deleting their files, closing their account and reporting their
REAL earnings to the IRS.
-- The B.O.F.H..
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594803: Patch to fix #594803 (queued noisy when removing multiple files)
Control: tag -1 patch
The attached patch fixes #594803 (queued noisy when removing multiple
files.)
--
Don Armstrong http://www.donarmstrong.com
It was said that life was cheap in Ankh-Morpork. This was, of course,
completely wrong. Life was often very expensive; you could get death
for free.
-- Terry Pratchet _Pyramids_ p25
From 5ff72213455efd17b2a228a8165851eaf8563324 Mon Sep 17 00:00:00 2001
From: Don Armstrong d...@donarmstrong.com
Date: Sat, 27 Sep 2014 17:01:24 -0700
Subject: [PATCH] Reset @files each time through the command loop to avoid
adding previously deleted files to the output message. This resolves #594803
(queue daemon noisy when removing multiple files).
---
tools/debianqueued-0.9/debianqueued | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/debianqueued-0.9/debianqueued b/tools/debianqueued-0.9/debianqueued
index 46ce787..5702e5c 100755
--- a/tools/debianqueued-0.9/debianqueued
+++ b/tools/debianqueued-0.9/debianqueued
@@ -1097,7 +1097,7 @@ sub process_commands($) {
my $commands = shift;
my ( @cmds, $cmd, $pgplines, $signator );
local (*COMMANDS);
- my ( @files, $file, @removed, $target_delay );
+ my ($file, @removed, $target_delay );
format_status_str( $main::current_changes, $commands );
$main::dstat = c;
@@ -1190,6 +1190,7 @@ outer_loop: while (COMMANDS) {
next if @word 1;
if ( $word[0] eq rm ) {
+ my @files = ();
foreach ( @word[ 1 .. $#word ] ) {
my $origword = $_;
if (m,^DELAYED/([0-9]+)-day/,) {
--
2.1.0
Bug#762502: Reply links containing non-ascii data are broken
Package: debbugs Severity: normal See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723649#15 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762310#10 for example; the mail header encoding is not reverted. -- Don Armstrong http://www.donarmstrong.com It's not Hollywood. War is real, war is primarily not about defeat or victory, it is about death. I've seen thousands and thousands of dead bodies. Do you think I want to have an academic debate on this subject? -- Robert Fisk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746005: guile-2.0 migration
On Fri, 12 Sep 2014, Rob Browning wrote: Don Armstrong d...@donarmstrong.com writes: Should have guessed as much. Upstream probably just doesn't use it. Thanks! Certainly -- shout if I can help with anything else. I finally got back into trying to make guile 2.0 work, and apparently there are a whole host of issues that need to be changed in lilypond to make it work at all. Upstream is currently working on them, but their work is also exposing bugs in guile 2.0 as well. They are not optimistic that they will be in a position to support guile 2.0 before Debian freezes, and they are also concerned about the long term stability of lilypond with guile 2.0 due to bugs being discovered in both in that short of a time frame. What are your thoughts about supporting guile 1.8 for another release? Since lilypond is going to put more work on your plate, I'm certainly willing to help out as much as I can, but in the end, it's your decision. [Obviously, I think everything that can migrate to guile 2.0 should; it would be a great thing if the only reverse dependency of guile 1.8 was lilypond.] -- Don Armstrong http://www.donarmstrong.com Sometimes I wish I could take back all my mistakes but then I think what if my mother could take back hers? -- a softer world #498 http://www.asofterworld.com/index.php?id=498 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762217: mentioning h*elp triggers a he*lp message
Control: reassign -1 lists.debian.org Control: forcemerge 712201 -1 Control: affects -1 bugs.debian.org This is 712201 which you also filed. -- Don Armstrong http://www.donarmstrong.com We were at a chinese restaurant. He was yelling at the waitress because there was a typo in his fortune cookie. -- hugh http://www.gapingvoid.com/Moveable_Type/archives/000321.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762230: lilypond: debian/rules sets HOME=/tmp
On Fri, 19 Sep 2014, Jakub Wilk wrote: This package's debian/rules sets HOME set to /tmp in debian/rules. But HOME is supposed to be writable only by trusted users, whereas /tmp is world-writable. For example, python2.7 (which debian/rules indirectly runs) loads code from $HOME/.local/lib/python2.7/site-packages/. Heh. Yeah... I should know better than to have done that. Fixed in git, and I'll upload a fixed version soonish. Hopefully fontconfig has stopped writing to home... but if it hasn't, I'll figure out a better way to work around that. -- Don Armstrong http://www.donarmstrong.com What, now? Soon equates to good, later to worse, Uagen Zlepe, scholar. Therefore, immediacy. -- Iain M. Banks _Look to Windward_ p 213 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749950: Reopen a bug
unarchive 749950 reopen 749950 thanks On Tue, 16 Sep 2014, Ernesto wrote: how can I reopen a bug? I reported https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749950 but then took too long to provide the requested info and the bug was closed. I tried replying to the last message but I got this subject on the response: Unknown problem report Bug#749950 (Bug#749950: qemu-utils: performance inferior than older version) That bug was closed, and then even more time passed, so it was archived. I've gone ahead and reopened it with this message, but please provide the additional information requested as soon as possible. [Otherwise the maintainer will close it again.] -- Don Armstrong http://www.donarmstrong.com I never until now realized that the primary job of any emoticon is to say excuse me, that didn't make any sense. ;-P -- Cory Doctorow -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761995: If there's a copy in db-h/yy/nnnnyy.log and an additional one in archive/, assume it's not archived
Package: debbugs Severity: normal If there are copies of a bug in db-h/yy/nnnyy and archive/yy/yy, use the db-h one unless the archived one is newer. 00:05:05 mjt is bts down somehow? I received an email from control@b.d.o robot telling me it successfully changed status of one bug in my pkg (#749950), that was more than 1.5 hours ago, but on the website that bug is shown with old status still, with no indication of control@ request processing 00:12:06 weasel 2014-09-17 05:21:45,324 DEBUG Syncer: rsync: spool/db-h/50/749950.log 00:12:06 weasel 2014-09-17 05:21:45,325 DEBUG Syncer: rsync: spool/db-h/50/749950.report 00:12:06 weasel 2014-09-17 05:21:45,327 DEBUG Syncer: rsync: spool/db-h/50/749950.status 00:12:06 weasel 2014-09-17 05:21:45,327 DEBUG Syncer: rsync: spool/db-h/50/749950.summary 00:14:36 weasel weasel@beach:/srv/bugs-webmirror.debian.org$ ls -l spool/db-h/50/749950.status 00:14:36 weasel -rw-rw-r-- 1 debbugs debbugs 179 Sep 17 05:21 spool/db-h/50/749950.status 00:15:01 weasel -rw-rw-r-- 1 debbugs debbugs 58969 Sep 17 05:21 spool/db-h/50/749950.log 00:15:02 weasel -rw-rw-r-- 1 debbugs debbugs 3841 May 30 22:27 spool/db-h/50/749950.report 00:15:02 weasel -rw-rw-r-- 1 debbugs debbugs 179 Sep 17 05:21 spool/db-h/50/749950.status 00:15:02 weasel -rw-rw-r-- 1 debbugs debbugs 308 Sep 17 05:21 spool/db-h/50/749950.summary 00:15:07 weasel weasel@buxtehude:/srv/bugs.debian.org$ ls -l spool/db-h/50/749950.* 00:15:07 weasel -rw-rw-r-- 1 debbugs debbugs 58969 Sep 17 05:21 spool/db-h/50/749950.log 00:15:07 weasel -rw-rw-r-- 1 debbugs debbugs 3841 May 30 22:27 spool/db-h/50/749950.report 00:15:07 weasel -rw-rw-r-- 1 debbugs debbugs 179 Sep 17 05:21 spool/db-h/50/749950.status 00:15:07 weasel -rw-rw-r-- 1 debbugs debbugs 308 Sep 17 05:21 spool/db-h/50/749950.summary -- Don Armstrong http://www.donarmstrong.com Overcast nights are beautiful; the sun, mostly set, a near full moon partially risen, light pollution from the city, and the sky delicately purpleorangegray, as if it were a livid bruise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761450: Please add a d-i.debian.org pseudo package
Package: bugs.debian.org Severity: wishlist Control: submitter -1 Cyril Brulebois k...@debian.org Control: tag -1 moreinfo On Sat, 13 Sep 2014, Cyril Brulebois wrote: Cyril Brulebois k...@debian.org (2014-09-07): Hi folks, I'm wondering whether it would make sense to ask ow...@bugs.debian.org for a d-i.debian.org pseudo package which could be used to track bugs/proposed changes for d-i's infrastructure. This includes but is not limited to: the various scripts generating reports on d-i.debian.org, scripts used to manage i18n/l10n bits, or various cross-package tasks. Dear owner, could you please introduce a d-i.debian.org pseudo package with debian-b...@lists.debian.org as its maintainer? I can; can you provide the text for this psuedopackage's description, as well as an example of a few bugs which will be filed there? [The latter is mainly so that I know that the psuedopackage will be used; they don't have to yet be filed in the BTS... a few links to messages on -boot which are bugs which would have been filed is good enough.] -- Don Armstrong http://www.donarmstrong.com Some pirates achieved immortality by great deeds of cruelty or daring-do. Some achieved immortality by amassing great wealth. But the captain had long ago decided that he would, on the whole, prefer to achieve immortality by not dying. -- Terry Pratchet _The Color of Magic_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602781: Licenses for DAISY DTDS: ANSI/NISO Z39.86 Specifications for the Digital Talking Book
On Sat, 13 Sep 2014, George Kerscher wrote: Many companies will copy and distribute these DTDs for use with their authoring or playback tools, which is perfectly fine. This may eliminate the need to go online for validation, etc. The working group may update the DTDs if errors are found and this will be announced publically. The DTDs were developed and highly influenced by HTML and Docbook. The DTDs may be modified for your use, but you may not claim that a modified version conforms to the DAISY Standard or the Niso Z39.86 Standard. It is common for XML and DTD developers to borrow from various standards, and this is expected. Thank you for your response. May the modified versions also be distributed? -- Don Armstrong http://www.donarmstrong.com Never underestimate the power of human stupidity. -- Robert Heinlein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761450: Please add a d-i.debian.org pseudo package
On Sun, 14 Sep 2014, Cyril Brulebois wrote: Looking at the existing descriptions[1], I'd go for something like: d-i.debian.org -- Issues regarding the d-i.debian.org service and general Debian Installer tasks. Cool. Sure, things like this would have been tracked there: http://anonscm.debian.org/viewvc/d-i/trunk/scripts/testing-summary/gen-summary?r1=69167r2=69316 https://lists.debian.org/debian-boot/2014/09/msg00406.html Awesome; this is exactly what I wanted to see. I'll create this package shortly. -- Don Armstrong http://www.donarmstrong.com First you take a drink, then the drink takes a drink, then the drink takes you. -- F. Scott Fitzgerald -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602781: Licenses for DAISY DTDS: ANSI/NISO Z39.86 Specifications for the Digital Talking Book
On Sat, 13 Sep 2014, George Kerscher wrote: If you create your own DTDs and you have borrowed, even heavily from these, yes, you would be able to distribute the DTDs. I think 67 of the elements from dtbook dtds came from HTML. Cool; I figured you meant that from your e-mail, but I wanted to make sure we asked you specifically. Thanks again for responding. This will enable us (Debian) to package a few packages which contain these DTDs instead of re-implementing the DTDs. -- Don Armstrong http://www.donarmstrong.com Miracles had become relative common-places since the advent of entheogens; it now took very unusual circumstances to attract public attention to sightings of supernatural entities. The latest miracle had raised the ante on the supernatural: the Virgin Mary had manifested herself to two children, a dog, and a Public Telepresence Point. -- Bruce Sterling, _Holy Fire_ p228 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746005: guile-2.0 migration
Currently guile-2.0-dev installs to /usr/include/guile/2.0, which makes the migration more difficult than merely switching guile-1.8-dev for guile-2.0-dev... is this the way it's going to stay? -- Don Armstrong http://www.donarmstrong.com There is no more concentrated form of evil than apathy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746005: guile-2.0 migration
On September 12, 2014 8:17:09 PM PDT, Rob Browning r...@defaultvalue.org wrote: Don Armstrong d...@donarmstrong.com writes: Currently guile-2.0-dev installs to /usr/include/guile/2.0, which makes the migration more difficult than merely switching guile-1.8-dev for guile-2.0-dev... is this the way it's going to stay? Would guile-config compile help? (And there's also a link.) Should have guessed as much. Upstream probably just doesn't use it. Thanks! -- This is not a signature. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734053: please remove the base pseudo package
Control: clone -1 -2 Control: retitle -2 Indicate when a psuedopackage is deprecated at submit time Control: retitle -1 Deprecate base psueodpackage On Thu, 11 Sep 2014, gregor herrmann wrote: On Thu, 11 Sep 2014 20:20:33 +0200, Tomasz Nitecki wrote: I agree with Holger here - I think it would be a good idea to remove 'base' pseudo package. Ack, I also have the impression that this pseudo-package doesn't serve any useful purpose any more. Right. I think I'm going to keep it, but I'm going to mark it deprecated in the description. I'll probably also add support for deprecated psuedopackages to include an indication when new bugs are filed that it's probably filed against the wrong package. -- Don Armstrong http://www.donarmstrong.com Rule 6: If violence wasn't your last resort, you failed to resort to enough of it. -- Howard Tayler _Schlock Mercenary_ March 13th, 2005 http://www.schlockmercenary.com/d/20050313.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760794: lilypond: FTBFS on powerpc and mips
On Mon, 08 Sep 2014, Petter Reinholdtsen wrote: [Don Armstrong] If you built it, could you please provide the log of the output for lilypond (should be in the log file listed.) The log file only had one line, the lilypond version string, so no help there. :( Ugh. That's annoying. OK. I'll upload a version which only uses parallel on amd64 to see if that fixes the build failure... but when I actually get infinite time, I should probably really check out what is causing the underlying issue. -- Don Armstrong http://www.donarmstrong.com Ban cryptography! Yes. Let's also ban pencils, pens and paper, since criminals can use them to draw plans of the joint they are casing or even, god forbid, create one time pads to pass uncrackable codes to each other. Ban open spaces since criminals could use them to converse with each other out of earshot of the police. Let's ban flags since they could be used to pass secret messages in semaphore. In fact let's just ban all forms of verbal and non-verbal communication -- let's see those criminals make plans now! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760794: lilypond: FTBFS on powerpc and mips
Control: tag -1 - patch On Sun, 07 Sep 2014, Petter Reinholdtsen wrote: It is not clear to me exactly what is failing or how, but I was able to reproduce the build failure on the porter box partch.debian.org. Running 'debian/rules build' after the failure completed the build without any errors. Perhaps there is some race in the build? I'm not sure that this is true, because I routinely build this package massively in parallel (-j8). I'd be OK with disabling parallel for particular architectures, but not completely. If you built it, could you please provide the log of the output for lilypond (should be in the log file listed.) -- Don Armstrong http://www.donarmstrong.com Those who begin coercive elimination of dissent soon find themselves exterminating dissenters. Compulsory unification of opinion achieves only the unanimity of the graveyard. -- Justice Roberts in 319 U.S. 624 (1943) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758787: lilypond-doc: Broken usage of dpkg-maintscript-helper
On Wed, 03 Sep 2014, Guillem Jover wrote: Hmm, this was supposed to be fixed with the upload that made the check coherent with the implementation, this is what the man page says for the symlink to directory switch (which is what lilypond-doc is using): [...] or is there something else I missed on the update (perhaps the omitted stuff referenced by [1]?). Sorry; 1: was supposed to indicate that I hadn't checked the your VCS repository. And now that I see, I was reading the manpage from 1.17.10 instead of 1.17.13 because I stupidly assumed that dpkg-maintscript-helper was in dpkg-dev, not dpkg... My bad. The documentation in 1.17.13 is clear enough now that I'm actually reading that version. Sorry. Sure, it seems and it is a bit backwards, but that's because the initial implementation could only handle absolute symlink targets for dir_to_symlink, so “it seemed to make more sense” to have both be symmetric. When the dir_to_symlink got fixed to also accept relative symlinks, I actually got a bit bothered by the new asymmetry, but… Ah; makes sense. I think lilypond's symlink happened by the expedient of just doing it instead of using dpkg-maintscript-helper. … neither me nor Helmut did think of this obvious solution, I don't know why!? maybe just because we had our minds elsehwere during the Bootstrap Sprint :), I'll try to recall if there was actually any problem. But otherwise, I'll just be adding relative symlink support to symlink_to_dir in dpkg 1.17.14, but be aware that previous dpkg version will either accept them but not perform the actual switch or outright refuse them. Right; I'll fix the lilypond postinst. It's sort of embarrassing too, because I thought I tested that it worked... but it's likely that I wasn't paying enough attention (or had managed to remove the older version). -- Don Armstrong http://www.donarmstrong.com Nearly all men can stand adversity, but if you really want to test his character, give him power. -- Abraham Lincoln -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758787: lilypond-doc: Broken usage of dpkg-maintscript-helper
On Thu, 21 Aug 2014, Guillem Jover wrote: The dpkg-maintscript-helper usage in this package is broken, because it's using a relative symlink target. The dpkg-maintscript-helper has been doing sanity checks to see if the canonicalized symlink targe (from «readlink -f») matches the passed symlink target argument, which will just not match, and not perform the switch. This doesn't match what the documentation still says (as of 1.17.13)[1], and also seems sort of backwards to me. The package can control the symlink's target (after all, that's what the symlink did), but has less control over the place in the filesystem that the symlink eventually points to. [In the instant case, we've previously done a /usr/doc to /usr/share/doc migration, which would have worked seamlessly if the target was checked, but would have required more changes if the cannonical target was checked. Starting with dpkg 1.17.13 the program will error out on such parameters (the documentation has been updated too now), so the package becomes uninstallable/unremovable. Please switch to use an absolute path for the symlink target. I'll do this for the time being, but either the documentation needs to be fixed, or the implementation changed. [An easy change would be to check both readlink -f or just readlink.] -- Don Armstrong http://www.donarmstrong.com Once, our bodies were bells: Simply moving in the wind We tolled our names. -- Phillis Levin Poetry in Motion p55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751659: RFS: gridlock.app/1.10-4 [ITA]
On Tue, 05 Aug 2014, Yavor Doganov wrote: Don Armstrong wrote: When working with NMUs, you can either 1) Incorporate the NMU changelog entries before your new changelog entry 2) Include a separate section in your new changelog entry which acknowledges the NMU-specific changes and the bugs that they fixed without including the NMU changelog entries. with option #1 the changelog entry Ack NMU, thanks NMUer seems to be nothing more than a simple acknowledgment that the maintainer confirms the changes made by the NMU. [...] I mean, if the maintainer is basing the new release on the NMU, there is an implicit assumption that the NMU has been ACK'ed and this changelog entry is more or less redundant. Pretty much. The only real reason to include that is the thanks NMUer part; it's a good way to show that you appreciate the work of the NMUer. -- Don Armstrong http://www.donarmstrong.com Creativity can be a social contribution, but only in so far as society is free to use the results. -- Richard M Stallman _GNU Manifesto_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681419: Alternative dependencies on non-free packages in main: Call for Votes
On Sat, 02 Aug 2014, Steve Langasek wrote: As previously agreed in the IRC meeting, I call for votes on this question with the following ballot options: A non-free packages as non-default alternatives should not be prohibited in main B non-free packages should always be prohibited in package dependencies for main FD I vote A B FD. -- Don Armstrong http://www.donarmstrong.com An elephant: A mouse built to government specifications. -- Robert Heinlein _Time Enough For Love_ p244 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751659: RFS: gridlock.app/1.10-4 [ITA]
On Mon, 04 Aug 2014, Yavor Doganov wrote: Paul Gevers wrote: Please acknowledge nmus (even if the content is nearly all yours) Fixed in Git. BTW, this Ack NMU thing doesn't seem to work as before. Previously, the maintainer would also close the bug that was fixed by the NMU, and IIRC this was the sole reason for the requirement to acknowledge NMUs. I guess it's been made redundant since debbugs has version tracking. When working with NMUs, you can either 1) Incorporate the NMU changelog entries before your new changelog entry 2) Include a separate section in your new changelog entry which acknowledges the NMU-specific changes and the bugs that they fixed without including the NMU changelog entries. Either method is acceptable as far as the BTS is concerned. #1 means that your version is based on the previous NMU version. #2 means that your version is not based on the previous NMU version, but that the bugs that the NMU fixed are also fixed in your version. -- Don Armstrong http://www.donarmstrong.com I shall require that [a scientific system's] logical form shall be such that it can be singled out, by means of empirical tests, in a negative sense: it must be possible for an empirical scientific system to be refuted by experience. -- Sir Karl Popper _Logic of Scientific Discovery_ §6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752609: r-base-dev: Please provide a method to run upstream unit tests at package build time
On Mon, 30 Jun 2014, Dirk Eddelbuettel wrote: If a CRAN package fails 'R CMD check' it will not be on CRAN, ie not be available as a source package. It would probably be good to run these at build time too, just in case a package has local tests which fail because of a dependency which changed in some incompatible way. DEB_BUILD_OPTIONS provides nocheck, which debhelper follows, so it would be easy to adapt this procedure for dh $@ style rule files, and that would enable package maintainers to easily skip the tests for local builds if they wanted/needed to. And of course, it would be possible to not run the tests for specific packages. -- Don Armstrong http://www.donarmstrong.com I'm a rational being--of a sort--rational enough, at least, to see the symptoms of insanity around me. And I'm human, the same as the people I think of as victims when my guard drops. It's at least possible I'm even crazier than my fellows, whom I'm tempted to pity. There seems only one thing to do, and that's get drunk -- Chad C. Mulligan (John Brunner _Stand On Zanzibar_ p390) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752589: scowl: Please mark packages as Multi-Arch: foreign
On Tue, 24 Jun 2014, Frédéric Brière wrote: Marking all packages providing wordlist as Multi-Arch: foreign would allow them to satisfy dependencies from packages of foreign architectures. Thanks for filing these bugs, but there are a couple of issues here: 1) This appears to be a mass bug filing; it should probably be discussed on debian-de...@lists.debian.org first. [If that happened, and I missed it, I'm sorry in advance.] 2) This particular issue in scowl itself would be trivially fixed by #666772, which has a patch, and has been open for two years with that patch... While I don't see a problem with adding this particular fix to scowl (it really is Multi-Arch: foreign), we should just fix this archive-wide once and for all. -- Don Armstrong http://www.donarmstrong.com [T]he question of whether Machines Can Think, [...] is about as relevant as the question of whether Submarines Can Swim. -- Edsger W. Dijkstra The threats to computing science -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752193: Severity of bug from Submitter's PoV in BTS
Package: debbugs Severity: wishlist On Fri, 20 Jun 2014, Paul Tagliamonte wrote: Say what you want about launchpad.net's bugtracker (I, for one, like it), it at least has the status 'opinion'. I miss that, and sometimes, I wish I could set it in the BTS. Whos' in the patching mood? On some other mailing list, Axel Beckert and Paul Tagliamonte indicated that it would be nice to have an indication of the severity of the bug from the submitter's point of view, which would be totally separate from the current bug severities. There have been multiple requests in the past for some kind of voting (or similar) to indicate how many people are affected by a bug, and how seriously they were affected as well.[1] There is also some need for maintainers to organize bugs and prioritize them as well, beyond taking ownership via owner. Some people have pointed out that the way launchpad handles these is good; I'm amenable to implementing something similar in the BTS, but I'd like to follow someone else's example which works well if at all possible. 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71879 -- Don Armstrong http://www.donarmstrong.com Have you ever noticed: the most vocal superpatriots are the old men who send young men out to die. -- Harlan Ellison Basilisk (_Deathbird Stories_ p73) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752050: upgrade-reports: Upgrade from Squeeze to Wheezy failed because of perl issues
Control: severity -1 minor Control: retitle -1 upgrade from squeeze to wheezy fails because of locally installed perl modules in @INC Can't locate feature.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl /usr/local/lib/perl/5.10.0 /usr/local/share/perl/5.10.0 .) at /usr/local/share/perl/5.10.1/Text/Wrap.pm line 13. BEGIN failed--compilation aborted at /usr/local/share/perl/5.10.1/Text/Wrap.pm line 13. BEGIN failed--compilation aborted at /usr/local/share/perl/5.10.1/Text/Wrap.pm line 13. Compilation failed in require at /usr/share/perl5/Debconf/Template.pm line 10. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 10. Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8. Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7. Compilation failed in require at /usrconfigured to not write apport reports You've installed a local copy of Text::Wrap into /usr/local/share/perl which is not compatible with perl 5.14. Either remove it, fix @INC, or otherwise move it out of the search path. [There's also little point to installing local modules like this; use the modules that Debian packages.] -- Don Armstrong http://www.donarmstrong.com If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money it values more, it will lose that, too. -- W. Somerset Maugham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752084: Debian lists need a plan to deal with messages from DMARC p=reject domains
On Fri, 20 Jun 2014, Steven Chamberlain wrote: DMARC is so obviously broken in this regard. I tried but couldn't find anyone with influence on the DMARC working group who cared about this issue. It was 'outside of scope' or something. Would you mind pointing to the mails in the archives of the DMARC IETF group where this was proposed? Want to try to address this if at all possible, but don't want to re-hash things which have been addressed. -- Don Armstrong http://www.donarmstrong.com I learned really early the difference between knowing the name of something and knowing something -- Richard Feynman What is Science Phys. Teach. 7(6) 1969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750032: Changes for the NMU
The changes for this NMU are available from http://git.donarmstrong.com/dactyl.git If a different format would be more useful, let me know. -- Don Armstrong http://www.donarmstrong.com Do you think you might be suffering from post-traumatic stress disorder? [...] Who isn't? -- Walter Jon Williams _This Is Not A Game_ p121 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750032: New version of xul-ext-pentadactyl
On Fri, 13 Jun 2014, Clint Adams wrote: On Thu, Jun 05, 2014 at 10:50:54AM -0700, Don Armstrong wrote: Just wanted to check in on this; I actively use pentadactyl, and would like to see the new version in Debian. If you'd like additional assistance, I can help upload a new version or whatever makes sense. I'd just like to avoid duplicating work or getting in your way. [I'm not sure if I have commit access to the pkg-mozext repo, either... but if I do, and I have your blessing, I can prepare an upload of the new version.] Please NMU or hijack. This delay is infuriating. Sorry, Clint. Michael approved the NMU, I'm just lagging. I'll do it today. -- Don Armstrong http://www.donarmstrong.com Clothes make the man. Naked people have little or no influence on society. -- Mark Twain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694979: debbugs: get_bugs() should allow specifying binary versions of packages
On Thu, 12 Jun 2014, Francesco Poli wrote:
The fact is that the enhanced get_bugs() I would need would anyway
have to internally map binary packages and binary versions to source
packages and source versions. During this process, it would anyway
find any non-existing binary packages among the provided arguments. If
get_bugs() also returned a list of non-existing binary packages, it
would be a great way to solve #536613.
I am therefore changing my feature request into the following one:
I would need to call get_bugs() so that it returned an array with
two elements. The first element should be an array containing
all the (unarchived) bug-numbers that apply to the specified binary
version of one of the mentioned binary packages and have one of
the mentioned severities. The second element should a possibly empty
array containing all non-existing binary packages (among the mentioned
ones).
Something like:
get_bugs('severity', [critical, grave],
'package', [pkg1/x.y-z, pkg2, pkg3/a.b.c-d])
which would request the bugs that apply to binary version x.y-z of
binary package pkg1, the bugs that apply to any version of binary
package pkg2, and the bugs that apply to binary version a.b.c-d of
binary package pkg3, and would also return an array containing the
non-existing packages among {pkg1, pkg2, pkg3}.
I really hope that this may be implemented, since it would allow me to
significantly improve apt-listbugs.
Please let me know what you think.
get_bugs returns bugs; there's currently no way for it to filter on the
basis of bug status or bug status at an arbitrary list of package
versions.
You'd have to first call get bugs with the set of packages that you were
interested in, and then call get_bugs_status() with the set of bugs that
were returned to figure out what package each bug was in, and finally
ask again whether the bug was still found in a particular source
version.
I believe the only correct way to implement this is to have a new SOAP
call which actually asked for bugs which affected a list of packages
which had particular severity; it would be totally distinct from the
current get_bugs interface.
--
Don Armstrong http://www.donarmstrong.com
A kiss was mysterious and powerful, fragile and invincible. Like any
spark, a kiss might fizzle into nothing or consume an entire forest.
[...] A kiss could change the entire world.
-- Scott Westerfeld _The Killing of Worlds_ p336
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750032: New version of xul-ext-pentadactyl
Just wanted to check in on this; I actively use pentadactyl, and would like to see the new version in Debian. If you'd like additional assistance, I can help upload a new version or whatever makes sense. I'd just like to avoid duplicating work or getting in your way. [I'm not sure if I have commit access to the pkg-mozext repo, either... but if I do, and I have your blessing, I can prepare an upload of the new version.] -- Don Armstrong http://www.donarmstrong.com PowerPoint is symptomatic of a certain type of bureaucratic environment: one typified by interminable presentations with lots of fussy little bullet-points and flashy dissolves and soundtracks masked into the background, to try to convince the audience that the goon behind the computer has something significant to say. -- Charles Stross _The Jennifer Morgue_ p33 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750587: bugs.debian.org: As my subject described, since i use the Nvidia driver on MATE 1.8; i have a bug on hardware acceleration visual. When i change the workstation, i can see the application
Control: reassign -1 mate-desktop-environment Control: retitle -1 Bleedthrough when switching workspace of applications in background when using HA Control: severity -1 normal On Wed, 04 Jun 2014, didicou wrote: I always used the Nvidia driver on Debian 7, without problem by using MATE 1.6 version and the last Nvidia driver. You've assigned a bug to bugs.debian.org, which is for bugs related to the bug tracking system, not MATE, or the non-free nvidia driver. While I have only reassigned your bug to a more appropriate package, you'll have to provide more information. Specifically: 1) reproducing this bug with nouveau 2) providing information on which versions of X, mate, nvidia, and nouveau show this bug and whether different versions do not. -- Don Armstrong http://www.donarmstrong.com Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750524: Please package LilyPond 2.18.2
On Wed, 04 Jun 2014, John Zaitseff wrote: The only thing that had to change was debian/changelog. Could you therefore update the official Debian package? Thanks! The main reason I haven't already released 2.18.2 is that lilypond doesn't work with guile 2.0, nor does it work with makeinfo --html. I think there are bugs open for both of these issues in upstream's bugtracker, but if you've got extra cycles, working on them would be awesome. [I have a super preliminary patch in my git repository, but it doesn't work at all.] I note that the current package has some lintian errors, as listed below. If I have a chance, I'll try to whip up a patch to at least turn these into warnings... These are because of bug #748167 in lintian, which will be fixed in the next release of lintian. E: lilypond-doc: info-document-not-compressed usr/share/info/lilypond/pictures/carter-brey.jpg -- Don Armstrong http://www.donarmstrong.com We have to face the fact that either all of us are going to die together or we are going to learn to live together and if we are to live together we have to talk. -- Eleanor Roosevelt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750524: Please package LilyPond 2.18.2
On Wed, 04 Jun 2014, John Zaitseff wrote: The main reason I haven't already released 2.18.2 is that lilypond doesn't work with guile 2.0, nor does it work with makeinfo --html. Thanks for the update! I'm currently working on trying to get the libgimp-perl package back into Debian, but I'll see if I can have a look at this too. Might be in a week or two, though... Cool; no rush. If I get a free moment, I may just shove 2.18.2 into the archive as it is now, but more help on the guile and makeinfo issues would definitely be appreciated. -- Don Armstrong http://www.donarmstrong.com To steal ideas from one person is plagiarism; to steal from many is research. -- Steven Wright -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750135: Request to ctte about administration of aptitude project -- was Re: [Aptitude-devel] Processed: Unmark changes that are no longer pending
was owned by Manuel A. Fernandez Montecelo manuel.montez...@gmail.com. Removed annotation that Bug was owned by Manuel A. Fernandez Montecelo manuel.montez...@gmail.com. tags 647474 - pending Bug #647474 [aptitude] aptitude: When piping, stdout doesn't include RECOMMENDED but will not be installed Bug #587676 [aptitude] --give-me-the-same-output-even-though-you-think-i-am-not-on-a-terminal Bug #720074 [aptitude] aptitude: Can not redirect part of information of aptitude Removed tag(s) pending. Removed tag(s) pending. Removed tag(s) pending. # Using XDG_CACHE_DIR is complicated by su, sudo interaction. tags 671780 - pending Bug #671780 [aptitude] Please move ~/.aptitude/cache to $XDG_CACHE_HOME (default ~/.cache) Removed tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 587676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587676 647474: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647474 671780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671780 720074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Aptitude-devel mailing list aptitude-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel -- To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140601151758.ga30...@lugh.itsari.org - End forwarded message - -- Don Armstrong http://www.donarmstrong.com I really wanted to talk to her. I just couldn't find an algorithm that fit. -- Peter Watts _Blindsight_ p294 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748167: typo in patch for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748167
You probably already noticed, but just in case, there's a typo in the patch for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748167. It should read m/^(?:png|jpe?g)$/, not m/^(?:png|jpe?g)$. Sorry about that. -- Don Armstrong http://www.donarmstrong.com I've had so much good luck recently I was getting sated with it. It's like sugar, good luck. At first it's very sweet, but after a while you start to think: any more of this and I shall be sick. -- Adam Roberts _Yellow Blue Tibia_ p301 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748167: Lintian should ignore .jpg/.jpeg in addition to .png in info directories
Package: lintian
Version: 2.5.22.1
Severity: normal
Control: tag -1 patch
Lintian wrongly complains about images being info documents:
lilypond-doc: info-document-not-compressed
usr/share/info/lilypond/pictures/darius-blasband.jpg
lilypond-doc: info-document-has-wrong-extension
usr/share/info/lilypond/pictures/darius-blasband.jpg
the following trivial patch fixes this problem:
diff --git a/checks/infofiles.pm b/checks/infofiles.pm
index 0076375..e3c36b0 100644
--- a/checks/infofiles.pm
+++ b/checks/infofiles.pm
@@ -64,7 +64,7 @@ sub run {
}
}
}
-} elsif ($ext eq 'png') {
+} elsif ($ext =~ m/^(?:png|jpe?g)$) {
next;
} else {
push(@fname_pieces, $ext);
--
Don Armstrong http://www.donarmstrong.com
Certainly the game is rigged. Don't let that stop you. If you don't
bet, you can't win.
-- Robert Heinlein _Time Enough For Love_ p240
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747239: fixed_versions format in the BTS and forcemerge
Package: debbugs Severity: normal Control: retitle -1 -done messages with only a Version pseudoheader do not get turned into fully qualified verisons; see #729576. On Tue, 06 May 2014, Vincent Lefevre wrote: I could see in a mail from control@b.d.o: [...] After four attempts, the following changes were unable to be made: fixed_versions of #731426 is 'systemd/204-9' not '204-9' fixed_versions of #726763 is 'systemd/204-9' not '204-9' Failed to forcibly merge 729576: Unable to modify bugs so they could be merged. But according to http://www.debian.org/Bugs/server-control.en.html#fixed these are two correct, equivalent ways to mark a bug as fixed in some version. Shouldn't the format be fixed (i.e. either source_package/version or just version)? The format is source_package/version; plain version is coerced into source_package/version if version corresponds to a valid source package version (or binary package version which corresponds to a valid source package version). Or shouldn't the BTS detect that and allow the forcemerge after possible conversion? Forcemerge tries to do the modification, but because #729576 is marked as fixed in 204-9 instead of systemd/204-9, it fails. For safety, forcemerge won't try to modify the first bug given, so it's going to fail. The real issue here is that 204-9 should never have been just 204-9, but should have been coerced into systemd/204-9; this is probably a bug in -done handling which is exposed when you just give a Version pseudoheader without a Source pseudoheader... and should be fixed. -- Don Armstrong http://www.donarmstrong.com We have to face the fact that either all of us are going to die together or we are going to learn to live together and if we are to live together we have to talk. -- Eleanor Roosevelt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747260: libapache-gallery-perl: cron.daily script tries and fails to remove /var/cache/www
On Tue, 06 May 2014, Andy Spiers wrote: It's trying to remove /var/cache/www when I guess it probably shouldn't. I think this is due to an error in the options to the find command in the script. The following patch resolves this: --- /etc/cron.d/libapache-gallery-perl +++ /etc/cron.d/libapache-gallery-perl @@ -17,7 +17,7 @@ # remove empty directories start-stop-daemon --start --pidfile /dev/null --startas /bin/sh \ --oknodo --chuid $user -- -c \ - find '$cachedir' -depth -type d -print0 | \ + find '$cachedir' -empty -type d -print0 | \ xargs -r0 rmdir --ignore-fail-on-non-empty fi Thanks for the report. This actually should be -mindepth 1, not -empty, and the -depth needs to be there. [It's failing to remove /var/cache/www not because it's empty, but because it doesn't have permissions to remove it.] -- Don Armstrong http://www.donarmstrong.com The solution to a problem changes the problem. -- Peer's Law -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#500965: This bug is causing real problems now
Control: retitle -1 Do not append footers to messages with DKIM headers On Fri, 02 May 2014, Santiago Vila wrote: For a lot of years this has not been a big problem, but now Yahoo and others are using a policy called DMARC (built on top of DKIM and SPF) and at least Yahoo is actually rejecting messages failing these kind of digital signatures. The solution is for people to either not sign the bodies of the messages that they are sending, or use Body Length Limits to limit the signature to only the parts of the body which they are sending. Frankly, all of these problems are known,[1] and deploying DMARC without allowing for opt-out or other mitigation practices is kind of silly. Furthermore, we already get numerous unsubscription requests from people who are unable to read the footer, and moving them into the headers would increase those requests even more. I'm not willing to do that for all mail. However, an interesting alternative possibility might be to just not attach footers to messages which contain DKIM headers, as we already do for messages which are signed. 1: https://tools.ietf.org/html/rfc6377#section-3 -- Don Armstrong http://www.donarmstrong.com But if, after all, we are on the wrong track, what then? Only disappointed human hopes, nothing more. And even if we perish, what will it matter in the endless cycles of eternity? -- Fridtjof Nansen _Farthest North_ p152 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#500965: This bug is causing real problems now
On Fri, 02 May 2014, Santiago Vila wrote: Hmm. Can you elaborate on that? Do you consider that if I sign a message and you want to modify it, am I to blame that you can't modify it? Or else: If you modify it anyway, am I to blame that the signature does not verify anymore? You're to blame if you're sending it to a mailing list, and are signing the body in such a way that footers cannot be added, and have configured your mail setup such that DKIM headers are mandatory. On the other hand, what do you mean by people here? Do you think Yahoo users are able to choose what part of their messages are signed by the SMTP server? I think they can't. No, but Yahoo is capable of using DKIM and SPF as advisory information, and ignore it for known mailing lists. If that's true, I would consider that as a proof that mail footers are useless, not that they are useful. It's just proof that some people are not observant, even when the information is clearly present. My point is that headers are hidden, and so not only would a person have to be observant, they'd have to know to look at the headers. Another idea, if you are worried that people will not know how to unsubscribe, would be to send monthly reminders a-la-mailman, to supplement lack of footers in every message. Monthly reminder e-mails are one of the worst misfeatures of mailman. We won't be doing that. [At least they're disabled by default for mailman, now.] -- Don Armstrong http://www.donarmstrong.com My spelling ability, or rather the lack thereof, is one of the wonders of the modern world. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746206: Control: psuedoheaders do not work for -done bugs; finish() called too early
Package: debbugs Severity: normal finish() is called for -done bugs before @control_bits is processed. -- Don Armstrong http://www.donarmstrong.com Tell me something interesting about yourself. Lie if you have to. -- hugh macleod http://www.gapingvoid.com/archives/batch20.php -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745042: out-of-date https://bugs.debian.org/release-critical/other/pseudo.html
On Thu, 17 Apr 2014, Jakub Wilk wrote: Apparently https://bugs.debian.org/release-critical/other/pseudo.html hasn't been updated for years. The page says it was last modified on Tue Apr 10 06:06:46 UTC 2007. Heh. Thanks for the report. I think I've fixed this now, but hard to say. Clearly no one actually cares about this page, though. ;-) -- Don Armstrong http://www.donarmstrong.com Where am I? THE VILLAGE. What do you want? INFORMATION. Which side are you on? THAT WOULD BE TELLING. WE WANT INFORMATION. INFORMATION. INFORMATION. You won't get it! BY HOOK OR BY CROOK, WE WILL. Who are you? THE NEW NUMBER 2. Who is Number 1? YOU ARE NUMBER 6. I am not a number! I am a free man! HAHAHAHAHAHA. -- Patrick McGoohan as Number 6 with Number 2 in The Prisoner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744339: bugs.debian.org: subject should always have $PACKAGE: preceded to a reply when looking in one's email
Control: tag -1 wontfix On Sun, 13 Apr 2014, shirish शिरीष wrote: It would be so much easier and saner if the subject line compulsarily adds a packagename with each and every reply so the user doesn't need to go to the web-interface to know what the bug is all about. Every message that the BTS sends has the package encoded in the X-Debian-Pr-Package: header: X-Debian-PR-Message: report 744339 X-Debian-PR-Package: bugs.debian.org X-Debian-PR-Keywords: Because bugs can be in multiple packages, and figuring out whether to strip or not strip a package from the subject is fraught with difficulties, I don't see the advantage of overloading the subject line to provide this information. -- Don Armstrong http://www.donarmstrong.com listen, what you do in the privacy of your neighbour's house while they're away is your own business -- a softer world #511 http://www.asofterworld.com/index.php?id=511 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742004: perltidy.LOG file left behind
On Tue, 18 Mar 2014, Russ Allbery wrote: I looked into this further. The problem is that Perl::Tidy now always attempts to create a log file in the current directory unless told to create it elsewhere with the logfile parameter to its constructor. (There doesn't seem to be a way to tell it not to create the thing, although maybe you can point it to /dev/null.) Perl::Critic's policy for running Perl::Tidy doesn't pass that parameter or provide any way for the caller to pass it. I've now uploaded a new version of perltidy which should not have this problem. -- Don Armstrong http://www.donarmstrong.com Where am I? THE VILLAGE. What do you want? INFORMATION. Which side are you on? THAT WOULD BE TELLING. WE WANT INFORMATION. INFORMATION. INFORMATION. You won't get it! BY HOOK OR BY CROOK, WE WILL. Who are you? THE NEW NUMBER 2. Who is Number 1? YOU ARE NUMBER 6. I am not a number! I am a free man! HAHAHAHAHAHA. -- Patrick McGoohan as Number 6 with Number 2 in The Prisoner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743407: new pseudo-package request: sso.debian.org
On Wed, 02 Apr 2014, Martin Zobel-Helas wrote: Please create a new pseudo-package for planet.debian.org (maintainer debian-...@lists.debian.org) to let us file bugs with the service. Do you mean sso.debian.org? In order to create the psuedopackage, I also need the blurb that goes on http://www.debian.org/Bugs/pseudo-packages Other than that, seems fine to me. -- Don Armstrong http://www.donarmstrong.com Sentenced to two years hard labor (for sodomy), Oscar Wilde stood handcuffed in driving rain waiting for transport to prison. If this is the way Queen Victoria treats her prisoners, he remarked, she doesn't deserve to have any. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740670: Info received (Bug#740670: possible CVE requests: perltidy insecure temporary file usage)
Control: tag -1 fixed-upstream On Fri, 28 Mar 2014, Steven Hancock wrote: This patch is in version 20140328 at CPAN. Awesome. Thanks Steven! I'll get this packaged for Debian shortly. -- Don Armstrong http://www.donarmstrong.com One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742109: Acknowledgement (Soft lookup during port scan and IPTables log enabled)
On Fri, 28 Mar 2014, daniel.gas...@basf.com wrote: any update on this bug report so far? Do you need further information from us? This looks awfully like https://bugzilla.kernel.org/show_bug.cgi?id=6816. Presumably, you're writing the LOG requests to something (serial console or similar) which cannot keep up, and the printk blocks. You should probably switch to using -j ULOG and ulogd instead of -j LOG. [As a note, you can just e-mail bug...@bugs.debian.org; sending mail to owner@ goes to the administrator of the bug tracking system, not the individual maintainers.] -- Don Armstrong http://www.donarmstrong.com I will not make any deals with you. I've resigned. I will not be pushed, filed, stamped, indexed, briefed, debriefed or numbered. My life is my own. I resign. -- Patrick McGoohan as Number 6 in The Prisoner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742004: perltidy.LOG file left behind
Steve: bringing you in on this; it appears perltidy now creates a perltidy.LOG file, which causes a few problems in Debian; see https://bugs.debian.org/742004 for the full saga. On Tue, 18 Mar 2014, Russ Allbery wrote: I looked into this further. The problem is that Perl::Tidy now always attempts to create a log file in the current directory unless told to create it elsewhere with the logfile parameter to its constructor. (There doesn't seem to be a way to tell it not to create the thing, although maybe you can point it to /dev/null.) Perl::Critic's policy for running Perl::Tidy doesn't pass that parameter or provide any way for the caller to pass it. Perltidy really shouldn't be creating a logfile unless you tell it to create a logfile. I'm OK with carrying a local patch in Debian for this in perltidy, but I'd like to propose that a logfile not be created unless logstream is passed (or some other non-default option.) Steve: would that be acceptable upstream? Or should I just prepare a Debian-local patch for that? -- Don Armstrong http://www.donarmstrong.com I would like to be the air that inhabits you for a moment only. I would like to be that unnoticed that necessary. -- Margaret Atwood Poetry in Motion p140 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742084: debbugs should look for a bug in the non-archived location first
Package: debbugs Severity: normal 17:47:59 dondelelcaro SamB: there might be a delay for the mirror to update, but the primary server is up-to-date immediately 17:48:10 SamB yeah but guess what doesn't work anymore ... 17:49:17 dondelelcaro it actually does, but it really shouldn't be used at all. what bug is this? 17:50:21 * SamB is really just grumpy that he can't use the bugs-master trick anymore ... 17:51:14 dondelelcaro it's https://bugs-bendel.debian.org/ 17:51:20 dondelelcaro but what bug is this? 17:51:40 SamB https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584672 17:53:35 dondelelcaro ah, OK 17:53:53 dondelelcaro it was actually synced almost immediately, but the sync program doesn't handle deletions immediately... 17:54:05 dondelelcaro I should probably fix the code that does that to find the non-archived bug first -- Don Armstrong http://www.donarmstrong.com Dropping non-free would set us back at least, what, 300 packages? It'd take MONTHS to make up the difference, and meanwhile Debian users will be fleeing to SLACKWARE. And what about SHAREHOLDER VALUE? -- Matt Zimmerman in 20021120225004.gx14...@mizar.alcor.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590180: possible packaging of sigil prepared
On Sun, 16 Mar 2014, Norbert Preining wrote:
On Sat, 15 Mar 2014, Don Armstrong wrote:
The problem is that flightcrew contains non-DFSG-free source files which
cannot be distributed in main. I have partially re-implemented them from
You mean src/FlightCrew/Misc/CustomAssert.{cpp,h}
No. I mean FlightCrew/Schemas/AsSources/Ncx20051Dtd.cpp and the schema
from which that was built.
I didn't find any other file.
What about contacting the original authors or Strahinja Markovic
and ask about the status. Did you have any success with that?
They're not the original author; I contacted the NCX2005 maintainers,
and while I got one response, they didn't respond with anything else useful.
--
Don Armstrong http://www.donarmstrong.com
A citizen of America will cross the ocean to fight for democracy, but
won't cross the street to vote in a national election.
-- Bill Vaughan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590180: possible packaging of sigil prepared
On Sat, 15 Mar 2014, Norbert Preining wrote: since it seems nothing is going on here, I have packaged sigil 0.7.4 and it is built with the builtin flightcrew, as long as that one is not packaged. The problem is that flightcrew contains non-DFSG-free source files which cannot be distributed in main. I have partially re-implemented them from scratch, but I haven't had a chance to finish them up. Once I finish doing that (or someone else does), flightcrew can be uploaded to Debian, and sigil can be packaged and uploaded without the embedded code copies. -- Don Armstrong http://www.donarmstrong.com The smallest quantity of bread that can be sliced and toasted has yet to be experimentally determined. In the quantum limit we must necessarily encounter fundamental toast particles which the author will unflinchingly designate here as croutons. -- Cser, Jim. Nanotechnology and the Physical Limits of Toastability. AIR 1:3, June, 1995. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707851: Please resume discussion on #707851 or defer decision to the TC.
On Thu, 13 Mar 2014, Josselin Mouette wrote: Le jeudi 13 mars 2014 à 08:36 +0900, Charles Plessy a écrit : I am therefore asking you to resume the discussion on #707851, or to defer the decision to the technical comittee. I don’t think there is anything to discuss anymore. This is not relevant for the technical committee either, since a resolution by consensus has been attempted *with success*. If everyone doesn't agree, then it's not a consensus resolution. That said, a pocket veto isn't a valid approach either; if there's no response, it should be assumed that consensus has indeed been reached. If there is an objection, then the CTTE can be invoked at that point. -- Don Armstrong http://www.donarmstrong.com I'm So Meta, Even This Acronym -- xkcd http://xkcd.com/917/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740670: possible CVE requests: perltidy insecure temporary file usage
On Fri, 07 Mar 2014, Don Armstrong wrote: On Tue, 04 Mar 2014, Murray McAllister wrote: Jakub Wilk and Don Armstrong are discussing in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740670 1) perltidy creating a temporary file with default permissions instead of 0600 2) the use of tmpnam(). The following trivial patch fixes this issue by just using File::Temp instead: http://git.donarmstrong.com/?p=perltidy.git;a=blob;f=debian/patches/fix_insecure_tmpnam_usage_740670 I'm currently preparing an upload which will resolve this issue for Debian in unstable and testing; I'm not certain if it necessitates a CVE or security update in stable, but if anyone feels that way, I don't mind preparing one. I just wanted to draw your attention to this patch; it fixes the insecure tmpnam and temporary file creation by using File::Temp::tempfile. A CVE has been given, https://security-tracker.debian.org/tracker/CVE-2014-2277 -- Don Armstrong http://www.donarmstrong.com If I had a letter, sealed it in a locked vault and hid the vault somewhere in New York. Then told you to read the letter, thats not security, thats obscurity. If I made a letter, sealed it in a vault, gave you the blueprints of the vault, the combinations of 1000 other vaults, access to the best lock smiths in the world, then told you to read the letter, and you still can't, thats security. -- Bruce Schneier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741297: Rmpi dlopen's libmpi.so.0 instead of libmpi.so.1
Package: r-cran-rmpi
Version: 0.6-3-1
Severity: serious
Control: tag -1 patch
Rmpi should dlopen libmpi.so.1 in addition to libmpi.so.0, otherwise
Rmpi is useless without having libopenmpi-dev installed (which provides
libmpi.so).
The following trivial patch fixes this:
--- rmpi-0.6-3.orig/src/Rmpi.c
+++ rmpi-0.6-3/src/Rmpi.c
@@ -69,7 +69,8 @@
#ifndef MAC
#ifdef OPENMPI
-if (!dlopen(libmpi.so.0, RTLD_GLOBAL | RTLD_LAZY)
+if (!dlopen(libmpi.so.1, RTLD_GLOBAL | RTLD_LAZY)
+ !dlopen(libmpi.so.0, RTLD_GLOBAL | RTLD_LAZY)
!dlopen(libmpi.so, RTLD_GLOBAL | RTLD_LAZY)){
// !dlopen(libmpi.dylib, RTLD_GLOBAL | RTLD_LAZY)
// !dlopen(libmpi.1.dylib, RTLD_GLOBAL | RTLD_LAZY)) {
--
Don Armstrong http://www.donarmstrong.com
Where I sleep at night, is this important compared to what I read
during the day? What do you think defines me? Where I slept or what I
did all day?
-- Thomas Van Orden of Van Orden v. Perry
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695188: Multiple Bug# references in subject
Control: retitle -1 Only add Bug# to the front if the bug# doesn't exist anywhere in the subject Control: tag -1 - moreinfo unreproducible Control: severity -1 minor Mailman mailing lists consistently add [] headers, which causes debbugs to include additional Bug#, which then get added to. Detect this, and only add bug# to Subject: if they don't exist anywhere in the subject. See http://lists.alioth.debian.org/pipermail/piuparts-devel/2014-March/thread.html#5197 for an example. -- Don Armstrong http://www.donarmstrong.com I'm wrong to criticize the valor of your brave men. It's important to die for one's country when it means being the subject of a king who wears a ruffled collar or a pleated one. -- Cyrano de Bergerac -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740670: possible CVE requests: perltidy insecure temporary file usage
On Tue, 04 Mar 2014, Murray McAllister wrote: Jakub Wilk and Don Armstrong are discussing in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740670 1) perltidy creating a temporary file with default permissions instead of 0600 2) the use of tmpnam(). The following trivial patch fixes this issue by just using File::Temp instead: http://git.donarmstrong.com/?p=perltidy.git;a=blob;f=debian/patches/fix_insecure_tmpnam_usage_740670 I'm currently preparing an upload which will resolve this issue for Debian in unstable and testing; I'm not certain if it necessitates a CVE or security update in stable, but if anyone feels that way, I don't mind preparing one. -- Don Armstrong http://www.donarmstrong.com listen, what you do in the privacy of your neighbour's house while they're away is your own business -- a softer world #511 http://www.asofterworld.com/index.php?id=511 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738712: Tracking source package renames
16:07:57 pabs dondelelcaro: does the BTS know about source package renaming? #738172 16:20:41 pabs ah, we discussed this before, I remember now 16:29:49 dondelelcaro pabs: I've actually already got some code for it 16:29:54 dondelelcaro pabs: but currently it doesn't 16:32:00 dondelelcaro (it's actually not too terribly difficult; you just walk through the changelog) 16:51:55 pabs could you mail the bug about that? -- Don Armstrong http://www.donarmstrong.com He quite enjoyed the time by himself in the mornings. The day was too early to have started going really wrong. -- Terry Pratchet _Only You Can Save Mankind_ p133 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740559: perltidy: new upstream version
On Sun, 02 Mar 2014, brian m. carlson wrote: perltidy 20130922 has been released. It would be great if you could package it. The current version is missing the -dt flag which a project I'm involved with requires. Thanks for the report; I would have missed this, as I didn't realize that upstream has switched from sourceforge to just releasing on CPAN. -- Don Armstrong http://www.donarmstrong.com Let the victors, when they come, When the forts of folly fall Find thy body by the wall! -- Matthew Arnold -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740670: perltidy: insecure permissions of temporary files
On Mon, 03 Mar 2014, Jakub Wilk wrote: perltidy creates temporary files with default permissions, potentially disclosing information that wouldn't be otherwise accessible to local users. Temporary files should be always created with mode 0600. Thanks for the report. This whole bit should probably be ripped out and replaced by File::Temp::tempfile too, as tmpnam isn't even remotely secure, either. -- Don Armstrong http://www.donarmstrong.com Creativity can be a social contribution, but only in so far as society is free to use the results. -- Richard M Stallman _GNU Manifesto_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740296: bugs.debian.org: SimpleITK package
Control: reassign -1 wnpp Control: retitle -1 RFP: SimpleITK -- cross platform image analysis toolset On Thu, 27 Feb 2014, Matt McCormick wrote: Please consider packaging SimpleITK [1]: Welcome to the National Library of Medicine Insight Segmentation and Registration Toolkit (ITK). ITK is an open-source, cross-platform system that provides developers with an extensive suite of software tools for image analysis. Among them, SimpleITK is a simplified layer built on top of ITK, intended to facilitate its use in rapid prototyping, education, interpreted languages. [1] http://www.simpleitk.org/ Just for reference, the correct package to assign Request For Packaging bugs in wnpp, not bugs.debian.org. -- Don Armstrong http://www.donarmstrong.com When bad men combine, the good must associate; else they will fall one by one, an unpitied sacrifice in a contemptible struggle. -- Edmund Burke Thoughts on the Cause of Present Discontents -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Call for Votes on init system coupling
On Mon, 24 Feb 2014, Andreas Barth wrote: * Ian Jackson (ijack...@chiark.greenend.org.uk) [140221 19:06]: The options on the ballot are: L Software may not depend on a specific init system N No TC resolution on this question at this time A Advice: sysvinit compatibility in jessie and multiple init support FD Further discussion I vote L A N FD. With this vote, the outcome is potentially in doubt; if Steve ranks L A, then Bdale has the casting vote between L and N. If Steve ranks A L, or does not vote, then N is the winner. [Presumably in the first case, Bdale will select N, but I'm not sure if that's enough to call the vote no longer in doubt.] 727708_initsystem/coupling_votes.txt has the current votes which you can run Ian's utility on. -- Don Armstrong http://www.donarmstrong.com He was wrong. Nature abhors dimensional abnormalities, and seals them neatly away so that they don't upset people. Nature, in fact, abhors a lot of things, including vacuums, ships called the Marie Celeste, and the chuck keys for electric drills. -- Terry Pratchet _Pyramids_ p166 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740030: closed by Don Armstrong d...@donarmstrong.com (Re: Bug#740030: spamass-milter: Spamassassin scans mail to localhost)
On Tue, 25 Feb 2014, Nigel Horne wrote: From the man page: -i networks Ignores messages if the originating IP is in the network(s) listed. It does not say but only if you don't change the default configuration file. According to the man page if I have -i 127.0.0.1 it should not scan from the localhost. I don't see how the fact that I've changed the configuration file would break anything. Your configuration file currently does not pass a -i option at all. -- Configuration Files: /etc/default/spamass-milter changed: OPTIONS=-u spamass-milter -i 127.0.0.1 -i 192.168.1.0/8 -i 208.113.207.5 -i 208.113.189.44 -r 8 -I SOCKET=inet:10783@127.0.0.1 SOCKETMODE= SOCKETOWNER= OPTIONS=-r 6 You want OPTIONS=$OPTIONS -r 6 or similar. [Or better, just delete this line, and change the -r 8 above it to -r 6.] I don't understand this either. How does changing the -r level prevent scanning of locally sourced e-mails? According to the man page -r is to do the the rejection level, it has nothing to do with white-listing the localhost. Currently, your configuration file is equivalent to this: SOCKET=inet:10783@127.0.0.1 SOCKETMODE= SOCKETOWNER= OPTIONS=-r 6 Presumably, you want this instead: OPTIONS=-u spamass-milter -i 127.0.0.1 -i 192.168.1.0/8 -i 208.113.207.5 -i 208.113.189.44 -r 6 -I SOCKET=inet:10783@127.0.0.1 SOCKETMODE= SOCKETOWNER= The second OPTIONS= statement overrides the first one. [The next release I make has changed the configuration file to clarify this.] -- Don Armstrong http://www.donarmstrong.com She was alot like starbucks. IE, generic and expensive. -- hugh macleod http://www.gapingvoid.com/Moveable_Type/archives/001376.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739851: lists.debian.org: Sorry is not an (un)subscription request
On Sun, 23 Feb 2014, Rebecca N. Palmer wrote: Twice, I've apologised on the BTS for my mistake in handling a bug (with no mention of any mailing lists), and got a don't send (un)subscription requests to the list autoresponse from debian-bugs-dist-request. Yeah, these really shouldn't be being sent to messages which are sent through to the mailing list from the BTS... Can you forward the message to listmas...@lists.debian.org (and probably also d...@debian.org, in case our filters intercept it) -- Don Armstrong http://www.donarmstrong.com I never meant to let you down. I thought for sure the attic lock would hold. -- a softer world #562 http://www.asofterworld.com/index.php?id=562 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739851: lists.debian.org: Sorry is not an (un)subscription request
On Sun, 23 Feb 2014, Rebecca N. Palmer wrote: If you want the full headers, see the BTS full text/mbox links. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650575#44 : I wasn't clear enough; I meant the message which was sent to you. -- Don Armstrong http://www.donarmstrong.com This isn't life in the fast lane, it's life in the oncoming traffic -- Terry Pratchett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Call for Votes on init system coupling
On Fri, 21 Feb 2014, Ian Jackson wrote: I hereby call for votes on my coupling proposal and the amendments that have been put. The options on the ballot are: L Software may not depend on a specific init system N No TC resolution on this question at this time A Advice: sysvinit compatibility in jessie and multiple init support FD Further discussion I vote A N L FD. -- Don Armstrong http://www.donarmstrong.com 6: I'm human. I have a thousand flaws. I break down. I get up or I don't get up. I get lost. I make the same mistakes over and over. I have scars and wounds. Sometimes when I can't bear them anymore, I drink. You can't fix me. You can't fix any of us. You can't make us perfect. -- The Prisoner (2009 Miniseries) _Checkmate_ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739231: ITP: cgit -- A hyperfast web frontend for git repositories written in C
Control: forcemerge -1 515793 On Mon, 17 Feb 2014, YAEGASHI Takeshi wrote: This is an attempt to create a fast web interface for the Git SCM, using a built-in cache to decrease server I/O pressure. Just FYI, there's an existing RFP which I've now merged with your ITP. [You should probably also be using libgit2-0 instead of cgit's embedded git codebase if at all possible.] -- Don Armstrong http://www.donarmstrong.com A Democracy lead by politicians and political parties, fails. -- 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 Call for Votes, Ian's drafts
On Sun, 09 Feb 2014, Ian Jackson wrote: I hereby propose the L versions from git: == dependencies rider version L (Loose coupling) == 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. as amendments to my own formal proposal, and do not accept them. I hereby call for votes on my own formal proposal. I vote FD over all other options in this CFV. -- Don Armstrong http://www.donarmstrong.com We have to face the fact that either all of us are going to die together or we are going to learn to live together and if we are to live together we have to talk. -- Eleanor Roosevelt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718267: marked as done (ITP: xidle -- run a program on X inactivity)
Control: reopen -1 On Wed, 12 Feb 2014, Andreas Cadhalpun wrote: is there any reason why you closed Bug #718267 with your message to announce the default init system for jessie? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718267#20 I didn't, actually.[1] For reasons which are unclear to me, Thorsten Glaser t...@mirbsd.de bounced my message to d-d-a to close this bug. As you're the second person who has asked me about it, and I haven't gotten a response from Thorsten when I asked him about it yesterday, I'm going to just unilaterally reopen this bug, and put this information in the bug log. Thorsten: feel free to close or whatever as appropriate. 1: You can tell if you look at the headers[2]: Received: from static-87-79-237-121.netcologne.de ([87.79.237.121] helo=herc.mirbsd.org ident=root) by buxtehude.debian.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from t...@mirbsd.org) 2: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=20;bug=718267 -- Don Armstrong http://www.donarmstrong.com A Democracy lead by politicians and political parties, fails. -- 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
On Sun, 09 Feb 2014, Ian Jackson wrote: 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. I vote FD. I think something along these lines should be done, but (as stated previously), I believe that the third paragraph places work on the maintainer which does not need to be there, and additionally does not limit this restriction to the release of jessie. -- Don Armstrong http://www.donarmstrong.com I cannot find rest Because I am powerless To amend a broken world. -- Guy Gavriel Kay _Under Heaven_ p295 -- 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
On Sun, 09 Feb 2014, Ian Jackson wrote: 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 vote FD. The current proposal already handles this case. -- Don Armstrong http://www.donarmstrong.com The terrorist's job is to terrorize the people, to interfere with freedom in such a way that disrupts ordinary life and commerce. With due respect, it is clear that the above referenced governmental agencies are aiding the terrorists' objective. -- Gary Fielder in Gary Fielder vs Janet Napolitano et al. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: call for votes on default Linux init system for jessie
On Sat, 08 Feb 2014, Bdale Garbee wrote: - - - 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. I also agree that given that while the additional questions of how packages are able to depend or rely on the default init system is important, it is not necessary to resolve that question to determine which system is going to be the default init system, as in no ballot yet has anyone changed their D/U ranking on the basis of which of the T, S, or L options were being voted for. -- Don Armstrong http://www.donarmstrong.com There is no form of lead-poisoning which more rapidly and thoroughly pervades the blood and bones and marrow than that which reaches the young author through mental contact with type metal. -- Oliver Wendell Holmes (Tilton 1947 p67) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Call for votes on init system resolution
On Thu, 06 Feb 2014, Kurt Roeckx wrote: I think there are basicly 2 ways to go about this: - You revoke your decision during the GR process so that when the GR is being voted on your decision no longer applies and the GR isn't trying to override the ctte. You could for instance do this at the call for votes point. - The GR will be with 2:1 majority and if it comes to a decision other than FD, that will be the result. If the decision of the GR is FD you could go and re-intreprete it with the 2:1 majority dropped. Either of these options will require 2:1, though. Let me quote §4.1.4: Together, the Developers may: [...] Make or override any decision authorised by the powers of the Technical Committee, provided they agree with a 2:1 majority. As you can see, there's no difference between making a decision which requires the CTTE powers (first proposed method), or overriding a decision which requires the CTTE powers (second proposed method). We want to draft language which avoids this, which is what the paragraph in question (and Ian's paragraph in [1]) attempt to do. 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708#5684 -- Don Armstrong http://www.donarmstrong.com A kiss was mysterious and powerful, fragile and invincible. Like any spark, a kiss might fizzle into nothing or consume an entire forest. [...] A kiss could change the entire world. -- Scott Westerfeld _The Killing of Worlds_ p336 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Call for votes on init system resolution
On Thu, 06 Feb 2014, Kurt Roeckx wrote: On Thu, Feb 06, 2014 at 10:22:15AM -0800, Don Armstrong wrote: Either of these options will require 2:1, though. Let me quote §4.1.4: Together, the Developers may: [...] Make or override any decision authorised by the powers of the Technical Committee, provided they agree with a 2:1 majority. As you can see, there's no difference between making a decision which requires the CTTE powers (first proposed method), or overriding a decision which requires the CTTE powers (second proposed method). It's not clear to me which powers of the the ctte they would be overriding. They would either be using the powers of the CTTE in 6.1.2, 6.1.1, or 6.1.3. My point is that there's no difference in the constitution between developers /making/ a decision that requires CTTE powers and /overriding/ a decision which requires CTTE powers. [If that was clear previously, I apologize in advance for becoming more emphatic.] I suppose there could be some draft texts which did not actually require the CTTE powers (as a position statement, say), but without language to the contrary in the CTTE's decision, the majority needed is irrelevant to whether the CTTE has vacated its decision or not. -- Don Armstrong http://www.donarmstrong.com N: Why should I believe that? B: Because it's a fact. N: Fact? B: F, A, C, T... fact N: So you're saying that I should believe it because it's true. That's your argument? B: It IS true. -- Ploy http://www.mediacampaign.org/multimedia/Ploy.MPG -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
