Package: dovecot-core
Version: 1:2.1.7-6
Followup-For: Bug #696817
Control: tags -1 + patch
The breakage is even worse.
1. The code that causes the problem is intended to set the *new*
path to the certificates. Why the f*** does it print $OLD_SSL_CERT ??
2. NEVER EVER touch user confiuration!
Package: bpython
Version: 0.11-1
Severity: minor
Eike discovered that bpython does not cleanly pass on the script's exit status
to the parent shell in interactive mode.
Example:
1. Call bpython.
2. Type exit(120)
3. Check with echo $?
Result:
$ bpython; echo $?
# enter exit(120)
Package: alpine
Version: 2.02-3.1
Severity: normal
The tiem information in the thread index does not take into account timezone
offsets.
Example:
Current local system time is:
$ date -R
Tue, 02 Oct 2012 23:36:06 +0200
Mail header is:
Date: Wed, 3 Oct 2012 00:29:19 +0300
Thread Index shows:
To
Package: shelldap
Version: 0.5-2
Severity: normal
Deleting attributes that do not have an equality matching rule in the schema
fails.
My best guess is that, in order to cope with multi-value fields, shelldap
compares
removed values server-side befoe deleting. Honestly, I have absolutely no clue
Package: shelldap
Version: 0.5-2
Severity: normal
Having RDNs like "cn=Foo Bar" causes unexpected behaviour for some commands.
- edit cn=Foo Bar- works
- cat cn=Foo Bar - expects ""
- cd cn=Foo Bar - works
- rm cn=Foo Bar - expects ""
All commands should expect "" for RDNs with
Hi,
> The manpage should at least document that if there are RDNs with
> spaces, then they need to be quoted. I do not see an easy way (right
> now) on how the code could be changed to parse the arguments to cat
> and rm in better way.
then just invert that. Make all commands that do not take a s
severity 688197 grave
kthxbye
I encountered this on several hosts and it is clearly RC.
--
Cheers,
Nik
PGP-Fingerprint: 8BC7 ABAB C2F2 4D5E 24FC
FC1C DB0E A4BC E210 7412
Please contact me for a face-to-face meeting
if you wish to exchange signatures with me.
Signature Policy:
Package: ldap2zone
Version: 0.2-2, 0.1-7+squeeze1
Severity: important
Tags: patch
The included script ldap2bind can never work / have worked because the
ldapsearch call uses the unknown variable $LDAP_HOST_PARAM.
The author obviously meant $LDAP_URI_PARAM, which is actually set
before in the scri
Package: mistelix
Version: 0.33-3+b1
Severity: minor
Nothing more to say ...
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Package: iceweasel
Version: 16.0.1-1, 15.0.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When opening local URLs and the file is a symbolic link, iceweasel resolves
them to their target before opening. This breaks relative links in the document
and also deviates from the beha
Package: mksh
Version: 40.9.20120630-4
Severity: normal
Tags: upstream
$ cat <
mksh: here document 'EOF' unclosed
$
mksh: local: not found
mksh: local: not found
1|nik@keks: $
After CTRL+C-ing the cat command, the local alias is not resoved anymore. The
same is true for all other aliases:
$
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
jsut for the record, this issue does not seem to affect i686 hosts.
- --
Cheers,
Nik
PGP-Fingerprint: 8BC7 ABAB C2F2 4D5E 24FC
FC1C DB0E A4BC E210 7412
Please contact me for a face-to-face meeting
if you wish to exchange signa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The bug is not reproducible on a clean bind9 installation of the mentioned
package version.
None of the shipped configuration files even reference /var/log/bind, it
all goes to syslog.
If your syslog server contains rules to redirect bind messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I can not reproduce this, neither on i686 nor on amd64, but that shouldn't
matter anyway.
The .erlang.cookie file never appears on my system, not during build, not
after install and not after purging.
- --
Cheers,
Nik
PGP-Fingerprint: 8BC7 ABAB C
--- greenwich-0.8.2.orig/debian/changelog 2012-10-22 13:46:00.905218470 +0200
+++ greenwich-0.8.2/debian/changelog 2012-10-22 13:48:44.11402 +0200
@@ -1,3 +1,9 @@
+greenwich (0.8.2-6) unstable; urgency=low
+
+ * Add dependency on liblocale-gettext-perl (Closes: #690864).
+
+ -- Dominik George Mon, 22
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just blindly following automated tests and policies here might not be a
good idea.
AFAIK, these bianries are vital for distutils to build Windows packages in
setup.py bdist.
There should be a solution to ship the files in a policy-conforming w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
from your last post, I conclude that the fix is ready to be released.
Could you please upload the fixed version to unstable or, if you are not
sure of it, provide the source package here for others to test?
- --
Cheers,
Nik
PGP-Fingerprint: 8
Package: slapd
Version: 2.4.31-1
Severity: important
The slapd process hangs when sending log data to an unresponsive syslogd.
In out site setup, all servers log to a central MySQL database through rsyslog.
rsyslog becomes unresponsive when having too much data queued, which happened
when
the li
Package: slapd
Version: 2.4.31-1
Followup-For: Bug #416272
slapd does not provide any useful information at all for certificate problems.
Our TLS certificate used for slapd recently expired and slapd simply didn't
start
anymore.
Even with highest debug level it does not provide any useful inform
Package: git-annex
Version: 3.20120924
Severity: minor
The upstream-supplied .desktop files for automatic startup of the
assistant with the session and the webapp menu entry are missing from
the Debian package. It would be great to have them added!
-- System Information:
Debian Release: wheezy/si
Package: rsyslog
Version: 5.8.11-1+b1
Severity: important
We recently added the omysql backend to rsyslog to centralize all logging to a
MySQL database.
The link to the database was a bit flakey lately and a syslog client, slapd,
was producing tons
of log lines for debugging purposes. This lead
> A full GDB backtrace of all threads would be useful for examining this issue
> any further.
kI will have to build a test case for that. Obviously, I cannot break
production deliberately for that ;).
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: xfce4-mixer
Version: 4.8.0-3+b1
Severity: grave
Justification: renders package unusable
The packages xfce4-mixer and xfce4-volumed depend on
gstreamer0.10-audiosink, with gstreamer0.10-alsa preferred, because
theyneed a gstreamer plugin that provides mixer control.
However, due to other
Package: xfce4-volumed
Version: 0.1.13-3
Severity: grave
Justification: renders package unusable
The packages xfce4-mixer and xfce4-volumed depend on
gstreamer0.10-audiosink, with gstreamer0.10-alsa preferred, because
theyneed a gstreamer plugin that provides mixer control.
However, due to other
Package: gstreamer0.10-gconf
Version: 0.10.31-3
Severity: important
According to the description and teh package contents, this package only
provides a GConf configuration interface for audio and video sinks and
sources. Nonetheless, the virtual packages -audiosink, -audiosource,
-videosink, -vide
severity 689120 grave
thanks
This bug is release critical as it breaks the default desktop task used by
the installer. ALSA is the default sound system but gstreamer0.10-alsa is
never pulled in for xfce4-mixer because gstreamer0.10-gconf is selected
beforehand and fulfills dependencies on gstre
Package: gstreamer0.10-plugins-good
Version: 0.10.31-3
Severity: normal
Some packages depend on gstreamer0.10-alsa | gstreamer0.10-audiosink or
comparable because they need a gstreamer sink/source plugin of some
sort. Unfortunately, far too many packages provide the virtual
gstreamer0.10-audiosink
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thomas,
at the Debian BSP in Essen I took a look at bug #682013 in fai-server.
Apparantly, you uploaded version 4.0.4 to unstabe, which, among other
changes, fixes the bug in question. However, I can neither find a backport
of the relevant patch
compatibility
+(Closes: #687449).
+
+ -- Dominik George Sat, 24 Nov 2012 13:28:10 +0200
+
redmine (1.4.4+dfsg1-1) unstable; urgency=low
* Upstream update.
diff -Naupr redmine-1.4.4+dfsg1.old/debian/control redmine-1.4.4+dfsg1/debian/control
--- redmine-1.4.4+dfsg1.old/debian/control 2012-05-18 16
Package: ttytter
Version: 2.0.1-1
Severity: normal
The debian/control file ists a dependency on curl | lynx, essentially
stating that both provide the same functionality. While ttytter can
really be used with any of the two, the defaut OAuth authentication
mechanism is not supported with lynx.
I
severity 693147 normal
kthxbye
Basic functionality works great for me, so this is not release critical!
--
Cheers,
Nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
c
Changes since the last upload:
* NMU to fix RC bugs.
* debian/control: add dependency on rubygems or recent enough ruby
(Closes: #693994).
* debian/postinst: replace exit status -1 with 2 for shell compatibility
(Closes: #687449).
Regards,
Dominik George
--
To UNSUBSCRIBE, email
Hi,
> $ grep-excuses fai
> fai (4.0.3 to 4.0.4)
> Maintainer: Thomas Lange
> Too young, only 6 of 10 days old
> Ignoring block request by freeze, due to unblock request by adsb
Oh ok, sorry. I actually looked for fai-server.
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ.
Hi Holger,
I stumbled upon this bug report at BSP Essen today and kindy wanted to ask
you for a follow-up on the issue.
If you do not have the time to provide a reasonable solution yourself,
feel free to explain your thought on it here and I will look to fix the
issue!
Cheers,
Nik
--
To UN
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package paramiko
The unblock would fix the RC bug #668239.
diff -Nru paramiko-1.7.7.1/debian/changelog paramiko-1.7.7.1/debian/changelog
--- paramiko-1.7.7.1/debian/changelo
Hi,
> The perfect solution would be a script to migrate from sqlite to MySQL
> (or PostgreSQL). It does not have to do the actuel migration, just to
> eat an sqldump from SQLite and turn it into a dump that could be used by
> MySQL.
So you do not actually plan to have this script run automaticall
> I have asked people that did successfuly upgrade real sqlite databse to
> MySQL if they could provide directions or a script but they don't
> remember how they did it exactly. If nobody can come up with a script,
> we will just have to put a note in the release notes about this. I
> personnaly do
Hi,
I stumvled upon this bug report during the BSP in Essen.
What is the current state? I did one obvious test and found that in
testing, the example script works.
Does this issue still break other packages? Please report un an
understandable manner what is still broken and what isn't.
-nik
severity 688634 normal
kthxbye
I am downgrading the severity of this issue because it does not cause real
data loss.
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
retitle 694164 RFS: redmine/1.4.4+dfsg1-1.1 [NMU] [RC]
kthxbye
Sorry, I meant 1.1, not 2.
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I still do not see where you have data loss. Your SQLite database, including
all of which you claim is lost, is where it always was after the upgrade. If
you do not have the skills to dump or migrate it, you sure can ask for help,
but not report it as data loss ...
-nik
--
To UNSUBSCRIBE, ema
severity 692295 important
kthxbye
Hi,
we are investigating this bug at BSP Essen.
I am downgrading the severity to important as this does not directly
affect anyone using the package. Upgrade only fails when the service has
never been restarted manualy before, e.g. when immediately upgrading t
Hi,
> Please be noted that an upload is pending. Waiting for RM answer, see
> #682172 [1].
this upload does not fix the bug you are replying to.
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
Hi,
the bug is related to
https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/448682/comments/7 :
couchdb will not be killed by its init script because signal 1 is
ignored if the daemon has been started during package installation:
$ cat /proc/$(cat /var/run/couchdb/couchdb.pid)/statu
Hi,
at BSP Essen, we are currently investigating Bug #692295 [1].
The problem is that CouchDB, an erlang service, expects SIGHUP to issue a
clean shutdown. This is what the start/stop script sends to the process.
When the start script is run by dpkg after package installation, it gets
dpkg's S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 692295 erlang
retitle 692295 does not properly set up signal handling
severity 692295 important
tags 692295 + upstream
kthxbye
I am reassigning this bug report to the erlang package.
The actual problem is that the Erlang VM does not properly
Package: gobby-0.5
Version: 0.4.94-5
Followup-For: Bug #635712
I can reproduce this bug.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package klibc
The upload fixes RC bug #692951.
unblock klibc/2.0.1-3.1
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'
Hi,
> Any more detail, please? Like a backtrace from gdb? Against which
> server? Is it public?
Sure. I can *sometimes* reproduce the issue when opening /BSP/2012/Bugs on
gobby.debian.org .
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscr
Hi,
> Thank you all for this work - Dominik, would you work directly on
> the git repository of the redmine package ? That would allow much
> easier maintenance.
Currently, I do not really plan on doing more work on the package, just RC
bug fixing.
Michael, please send follow-ups directly adres
Hi,
> As I can't it would be helpful if you could install gobby-0.5-dbg,
> libglib2.0-0-dbg and libinfinity-0.5-dbg and run it under gdb:
I could certainly do that, but that'd imply having gdb running all the
time waiting for the bug to finally appear. Right now, it doesn't occur
for me either.
Hi Michael,
I incorporated the changes you requested.
Cheers,
Nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 690851 important
kthxbye
Hi,
in the ocurse of the BSP Essen I took a close look at this report and the
proposed patch.
First of all, I am downgrading the severity of the bug to important to
remove it from the RC list. The background is th
Hi,
I am currently trying to create a workaround to fix bug #692295 [1].
The problem is that CouchDB uses SIGHUP to trigger a clean shutdown (don't
ask me why ...) and this signal is ignored by apt. So, when apt runs dpkg
to install couchdb, and dpkg runs the CouchDB init script, the SigIgn mas
@@
-couchdb (1.2.0-2.1) unstable; urgency=low
-
- * Non-maintainer upload.
- * Use SIGTERM instead of SIGHUP for graceful shutdown
-(Closes: #692295) [varacanero]
-
- -- Dominik George Mon, 26 Nov 2012 12:54:05 +0100
-
couchdb (1.2.0-2) unstable; urgency=low
* Make couchdb user own its run
varacanero]
-- Dominik George Mon, 26 Nov 2012 12:54:05 +0100
The debdiff is attached.
Regards,
Dominik George
diff -Nru couchdb-1.2.0/debian/changelog couchdb-1.2.0/debian/changelog
--- couchdb-1.2.0/debian/changelog 2012-07-19 20:35:03.0 +0200
+++ couchdb-1.2.0/debian/changelog 201
Hi,
the first diff I posted was invalid. See the CCed RFS for the correct
patch.
-nik
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
severity 690851 normal
kthxbye
Michael,
first of all, you are replying to a post I made. *Please* do not remove me
from Cc, then!
Now, back on topic:
> So, if you can fix up that issue in the patch, we can do another
> upload and ask for an unblock.
I still do not think this should be done. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am currently sorting through all the patches applied against upstream in
the arpwatch package. I then plan on migrating the packaging to dh7,
because the current packaging does not look very sane and is quite
outdated.
Should I succeed, I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> On Mon, 2012-11-26 at 13:41 +0100, Dominik George wrote:
> > I am looking for a sponsor for my package "couchdb". The upload would fix
> > RC bug #692295.
> May I ask some things? How is it your package, if you ar
> I installed the sqlite version of Roundcube at work because I don't
> understand databases (we are too small to employ a sysadmin, and if we did
> we would probably end up with a Windows server). At the rate things are
> going my (20) users are going to lose data and I wish I had installed
> Squi
Package: redmine
Version: 1.4.4+dfsg1-1
Severity: important
The redmine postinst script uses a negative exit status on line 279 which is
illegal:
/var/lib/dpkg/info/redmine.postinst: 279: exit: Illegal number: -1
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT poli
Package: xul-ext-firebug
Version: 1.9.2~b2-1
Followup-For: Bug #704714
Control: severity 634161 important
I can confirm this issue and am also raising severity of bug #634161 to
important because it would prevent this issue from happening.
-- System Information:
Debian Release: 7.0
APT prefers
Package: xul-ext-certificatepatrol
Version: 2.0.14-4
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
In Iceweasel 20, the add-on is shown with name 'null' in the add-on
list. The add-on works flawlessly apart from that.
- -- System Information:
Debian Release: 7.0
APT prefers u
Package: sqlitebrowser
Version: 2.0.0~beta1+ds.1-3
Severity: wishlist
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
SQLitebrowser should really popup a dialog and ask for unsaved changes before
exiting! Don't ask how I found out ;)...
- -- System Information:
Debian Release: whee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thijs,
> > I think that the package should additionally list curl as Recommends.
>
> I don't think listing the package in both fields would do anything
> technical that would help with this issue.
I think it would. See below ...
>
> I'm happy w
Package: cmus
Version: 2.5.0-1, 2.4.3-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The remaining time of each and every track in my library is off by 24
seconds when using the ALSA output module.
Relevant parts of ~/.cmus/autosave:
set dsp.alsa.device=default
set dsp.ao.buff
Package: cmus-plugin-ffmpeg
Version: 2.4.3-2
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Suggests: on cmus should be versioned. I just upgraded to cmus
2.5.0-1 from experimental to reproduce another bug and that broke the
ffmpeg plugin.
I actually think the plugin should ha
2012-12-04 00:11:36.0 +0100
@@ -1,3 +1,10 @@
+python-webob (1.1.1-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix response header bug reported by Mehdi Abaakouk (Closes: #695050).
+
+ -- Dominik George Tue, 04 Dec 2012 00:09:48 +0100
+
python-webob (1.1.1-1) unstable
-maintainer upload.
+ * debian/control: add dependency on rubygems or recent enough ruby
+(Closes: #693994) [Axel Beckert].
+ * debian/postinst: replace exit status -1 with 2 for shell compatibility
+(e.g. ksh) (Closes: #687449).
+
+ -- Dominik George Sun, 29 Nov 2012 14:18:29 +0200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Apparently, this bug has already been reported upstream several times
before, the oldest report that was pointed out dates 4 years back.
Mozilla's BTS is a hell of a bug report collection and why this bug is
still around after 4 years is a mystery
Package: src:linux
Version: 3.6.8-1~experimental.1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Putting my wireless conneciton under load, I recently got kernel freezes with
messages like:
BUG: soft lockup - CPU#0 stuck for 22s! [irq-17:0002]
I haven't really figured ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> > BUG: soft lockup - CPU#0 stuck for 22s! [irq-17:0002]
>
> Please send the log messages that appear immediately after this.
There are no messages after this. The I/O part of the kernel goes into a
deadlock and the system becomes unresp
intainer upload.
* Fix response header bug reported by Mehdi Abaakouk (Closes: #695050).
-- Dominik George Tue, 04 Dec 2012 00:09:48 +0100
I propose uploading to DELAYED/5 to give the maintainer some more time to
respond to the bug report themselves, but to squash RC bugs I'd really
lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
severity 695239 important
reassign 695239 wine 1.4.1-1
retitle 695239 wine meta-package is not multiarch
kthxbye
Hi,
this bug is in the wine metapackage rather than in winetricks. I also
think it is not grave because what you did is not what the a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I looked at the package and am baffled by the postinst and postrm scripts.
They are (should be?) entirely useless (manually calling ldconfig ??).
I then brought up debian/rules and immediately saw what the reason for
that method is: Complete
Package: src:liblockfile
Version: 1.09-4
Severity: wishlist
Dear maintainer,
while trying to analyze and fix RC bug #695268, I noticed that your
package does not use debhelper or any other standards method understood
by a brought part of the Debian community.
Although your code sure looks correc
+1,10 @@
+ldap2zone (0.2-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Fix unbound variable in ldap2bind script (Closes: #690377).
+
+ -- Dominik George Mon, 10 Dec 2012 16:47:17 +0100
+
ldap2zone (0.2-3) unstable; urgency=low
* Fixed installation of default file
diff -Nru
/pool/main/l/ldap2zone/ldap2zone_0.2-3.1.dsc
Changes:
ldap2zone (0.2-3.1) unstable; urgency=low
* Non-maintainer upload.
* Fix unbound variable in ldap2bind script (Closes: #690377).
Regards,
Dominik George
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> On Fri, 2012-12-07 at 09:11 +0100, Helmut Grohne wrote:
> > Introducing a new binary package is a quite big change. Please contact
> > the release team on whether such a change is acceptable at this point of
> > the freeze.
>
> Apparently no-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Is there a particular use case for such support, other than "because we
> can"? If not, then not having multi-arch support in wheezy doesn't seem
> a huge issue; ymmv, obviously.
ACK.
I can prepare another version for wheezy incorporating this. W
Package: bugs.debian.org
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The BTS converts text/plain (or similar, e.g. text/x-diff) MIME
attachments to windows inebreaks (CR/LF).
Here are two examples of this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=30;filename=ldap2
/changelog
- --- ldap2zone-0.2/debian/changelog2012-07-25 08:11:24.0 +0200
+++ ldap2zone-0.2/debian/changelog 2012-12-10 23:28:13.0 +0100
@@ -1,3 +1,14 @@
+ldap2zone (0.2-3.1) unstable; urgency=low
+
+ [ Dominik George ]
+ * Non-maintainer upload.
+ * Fix unbound variable in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
unfortunately the debdiff got messed up when pasting.
Here is a correct version of the debdiff, minus the BTSs mishandling of
line breaks:
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=30;filename=ldap2zone_0.2-3.1.debdiff;att=1;bug=69037
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
severity 695505 important
kthxbye
Hi,
os-prober not working on non-Linux kernels is not a good state.
However, I chose to ower the severity to important while squashing RC
bugs. A bug qulifies for severity grave if it makes the package unusable
Package: alpine
Version: 2.02+dfsg-2
Severity: important
Alpine changes thje linebreaks of attached plaintext files to CRLF
before base64-encoding and sending them. This is particularly awesome as
it seems to be a misfeature rather than an arbitrary bug because it
actually fixes this back when asv
Hmpf. It really is pine that does the 'helpful' conversion.
Sorry for bothering you!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
discussion in #695632 has led to the following conclusion:
RFC 2046 [1] states that any line break in text/* MIME parts must be CRLF
regardless of format. Thus, alpine's way of doing things - converting line
breaks to CRLF - is correct and th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear release managers,
today, I chose to fix RC bug #694998. It is a security issue with
MediaWiki 1.19.2 currently in testing, and there are two ways of fixing
this issue. The easiest would be to get the new upstream version 1.19.3
into testing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> No, CRLF line endings will remain the same.
>
> In any event, if you read the MIME standard as specifying CRLF line
> endings in text/* MIME parts, then that's what the BTS provides, as it
> merely shoves the un-base64 encoded mime content ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> Your argument is that the BTS should send a text/plain MIME document
> with LF instead of CRLF, which conflicts with RFC 2046.
>
> Frankly, I think that's probably more sane, but that's because I think
> that the MIME standard is wrong is spe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Things are even worse. RFC 2616 part 3.7.1:
HTTP applications MUST accept CRLF, bare CR, and bare LF as being
representative of a line break in text media received via HTTP.
So your proposal that HTTP clients should re-translate the text/*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: tags -1 + patch pending
Hi fellows,
thanks to Roland for fixing my commit access!
I have now committed my changes to the team SVN and hope that they are fit
for release.
Cheers,
Nik
- --
* mirabilos is handling my post-1990 smartphone
Package: gpsdrive
Version: 2.10~pre4-6.dfsg-5.2
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Starting any application that reads freedesktop applicaiton definitions
yields, when parsing gpsdrive's .desktop file:
> Desktop file '/usr/share/applications/gpsdrive.desktop' should
Control: severity -i normal
This bug report does not qualify for severity serious as:
- it does not make any package unusable
- does not violate any policy
- might be unreproducible anyway
On a side note, GNOME is dropping GNOME classic anyway. Get used to it,
or move away from GNOME.
-nik
Package: dovecot-core
Version: 1:2.1.7-7
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The postinst script is still broken and the package is uninstallable on
a fresh minimal installation.
= snip ==
Package: release-notes
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The dovecot packages have a new major release in wheezy (Dovecot 1 vs.
Dovecot 2). Almost nothing remained the same - the maintainer as wel as
upstream have chosesn to make the two versions heavily incompatibl
Control: severity -1 normal
Hi,
you are right, I missed a detail. I copied /etc/ssl/private from another
machine before, so /etc/ssl/private/dovecot.pem existed. This is what
the postinst script checks for and the nchooses to not modify the config
file.
This is broken because it does not check t
Hi,
> Can I ask you to help test it when the time comes?
Of course.
-nik
signature.asc
Description: Digital signature
Control: retitle -1 ITP: geierlein -- Elster client to submit VAT declarations
to Germany's fiscal authorities
I jsut tested geierlein trunk on Debian jessie and it works perfectly.
I will now try and build a Debian package for it.
-nik
--
Auf welchem Server liegt das denn jetzt…?
Wenn es n
101 - 200 of 1024 matches
Mail list logo
