Package: vtk
Severity: grave
vtk package fails to build on kfreebdsd. error is:
1 problem (1 warning)[100%] Generating ../../java/vtk/AxesActor.class
--
1. ERROR in /«PKGBUILDDIR»/Build/java/vtk/vtkJavaTesting.java (at line 108)
public void run() {
^
The method run() of t
Your message dated Sun, 11 May 2014 05:19:02 +
with message-id
and subject line Bug#746086: fixed in tiemu 3.03-nogdb+dfsg-2.1
has caused the Debian Bug report #746086,
regarding tiemu: FTBFS: configure: error: Package requirements (ticalcs2 >=
1.0.7) were not met
to be marked as done.
This
Your message dated Sun, 11 May 2014 04:33:34 +
with message-id
and subject line Bug#740602: fixed in doomsday 1.10.4-2
has caused the Debian Bug report #740602,
regarding missing license in debian/copyright
to be marked as done.
This means that you claim that the problem has been dealt with.
On Thu, May 8, 2014 at 1:13 AM, Fabian Greffrath wrote:
> Am Montag, den 05.05.2014, 23:15 -0700 schrieb Vincent Cheng:
>> Don't forget that the Debian Games team
>> has a sponsorship queue [1] that you can use if you're looking for a
>> sponsor within the team; I aim to regularly check the queue
On Wed, 2014-05-07 at 15:05 +0200, Salvatore Bonaccorso wrote:
> Hi
>
> This is the commit which is reverted in 3.2.58, which fixes these
> issue:
>
> https://git.kernel.org/cgit/linux/kernel/git/bwh/linux-3.2.y.git/commit/?id=2e59f013993a74bf31366a59bcf36be830d0f058
Thanks. This should be incl
Source: ruby-merb-haml
Version: 1.1.3-2
Severity: serious
Justification: fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.0-rm
Dear Maintainer,
During a rebuild of ruby-related packages your package failed to
build with these errors:
Running tests for ruby2.1 using d
Source: ruby-imagesize
Version: 0.1.1-5
Severity: serious
Justification: fails to build from source
User: debian-r...@lists.debian.org
Usertags: ruby2.0-rm
Dear Maintainer,
During a rebuild of ruby-related packages your package failed to
build with these errors:
1) Failure:
TestImageSize#test_
Processing commands for cont...@bugs.debian.org:
> Tags 746420 +pending
Bug #746420 [src:linux] linux: FTBFS on armhf: sun4i-a10-a1000.dtb
Bug #746636 [src:linux] linux 3.14.2-1 FTBFS on armhf
Added tag(s) pending.
Added tag(s) pending.
> Severity 746420 serious
Bug #746420 [src:linux] linux: FTBF
Processing commands for cont...@bugs.debian.org:
> notfound 747681 1.26.2-1
Bug #747681 [src:libguestfs] FTBFS: Fatal: can't open /dev/urandom: Bad address
The source 'libguestfs' and version '1.26.2-1' do not appear to match any
binary packages
No longer marked as found in versions libguestfs/1.
On Sat, May 10, 2014 at 09:56:33PM +0200, Michael Biebl wrote:
> Source: libvirt
> Version: 1.2.4-2
> Severity: serious
>
> Aside from the kfreebsd-* failure [0], libvirt now also FTBFS on at
> least mipsel and s390x with the following error:
>
> make[4]: Entering directory '/«PKGBUILDDIR»/debian
Processing commands for cont...@bugs.debian.org:
> tags 747679 + jessie sid
Bug #747679 [ruby2.0] ruby2.0: Don't ship with jessie
Added tag(s) sid and jessie.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
747679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Package: ruby2.0
Version: 2.0.0.484+really457-3
Severity: serious
ruby2.0 is not meant to be shipped with jessie.
This bug documents this and also makes sure it doesn't reenter
testing when it is finally removed.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subjec
Processing commands for cont...@bugs.debian.org:
> retitle 732916 Depends on obsolete package: ruby1.8
Bug #732916 [dhelp] Implicitly depends on Ruby 1.8 which will not be available
in Jessie
Changed Bug title to 'Depends on obsolete package: ruby1.8' from 'Implicitly
depends on Ruby 1.8 which w
Processing commands for cont...@bugs.debian.org:
> retitle 735466 glark: Please migrate to ruby2.1
Bug #735466 [glark] glark: Please migrate to Ruby 2.0
Changed Bug title to 'glark: Please migrate to ruby2.1' from 'glark: Please
migrate to Ruby 2.0'
> thanks
Stopping processing here.
Please cont
Processing commands for cont...@bugs.debian.org:
> retitle 733641 samidare: Please migrate to ruby2.1
Bug #733641 [samidare] samidare: Please migrate to Ruby 1.9 / 2.0
Changed Bug title to 'samidare: Please migrate to ruby2.1' from 'samidare:
Please migrate to Ruby 1.9 / 2.0'
> thanks
Stopping pr
Processing commands for cont...@bugs.debian.org:
> retitle 732922 ruby-nora: Please migrate to ruby2.1
Bug #732922 [src:ruby-nora] ruby-nora: Please migrate to ruby1.9 / ruby2.0
Changed Bug title to 'ruby-nora: Please migrate to ruby2.1' from 'ruby-nora:
Please migrate to ruby1.9 / ruby2.0'
> tha
Processing commands for cont...@bugs.debian.org:
> retitle 739775 root-system: Please support building with Ruby 2.1
Bug #739775 [src:root-system] root-system: Please support building with Ruby 2.0
Changed Bug title to 'root-system: Please support building with Ruby 2.1' from
'root-system: Please
Processing control commands:
> retitle 734342 "ruby-luabridge: Please migrate to ruby2.1"
Bug #734342 [ruby-luabridge] ruby-luabridge: Please migrate to Ruby 1.9/2.0
Changed Bug title to '"ruby-luabridge: Please migrate to ruby2.1"' from
'ruby-luabridge: Please migrate to Ruby 1.9/2.0'
--
73434
Control: retitle 734342 "ruby-luabridge: Please migrate to ruby2.1"
Hello,
Ruby 1.9 has been removed from testing; Ruby 2.0 is in the process
of being removed.
Please migrate to Ruby 2.1 - or the metapackages - instead.
Thank you,
--
,''`. Christian Hofstaedtler
: :' : Debian Developer
`.
Package: ejabberd
Version: 2.1.11-1
Severity: grave
Tags: security
When setting up ejabberd with a default configuration it allows only connections
with a weak SSL configuration - if this is even configured:
1. By default ejabberd allows SSLv3 which is broken in various ways
and thus should
Your message dated Sat, 10 May 2014 22:03:36 +
with message-id
and subject line Bug#746941: fixed in dnsmasq 2.70-2
has caused the Debian Bug report #746941,
regarding Initscript fails to disable itself when the dnsmasq package is removed
to be marked as done.
This means that you claim that t
Your message dated Sat, 10 May 2014 21:51:16 +
with message-id
and subject line Bug#747658: fixed in libvirt 1.2.4-3
has caused the Debian Bug report #747658,
regarding FTBFS on various architectures: missing systemtap directory
to be marked as done.
This means that you claim that the problem
Package: cryptsetup
Version: 2:1.6.4-4
Severity: critical
Justification: breaks the whole system
Because cryptoroot (form cryptsetup) now use --type option of cryptsetup,
package cryptsetup should depend on a version of cryptsetup-bin that provide a
version of cryptsetup binary that support --ty
Package: opensmtpd
Severity: serious
Tags: upstream patch
Justification: fails to build from source
When building this package a shitload of repeated warnings about a redefined
macro scroll by exhausting my precious console backlog unnecessarily.
The attached patch fixes this issue.
Kind regards
Processing commands for cont...@bugs.debian.org:
> severity 670700 serious
Bug #670700 [dirmngr] dirmngr: upgrade broken, it fails in init script if
/bin/sh is link to /bin/dash
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
-
Source: libvirt
Version: 1.2.4-2
Severity: serious
Aside from the kfreebsd-* failure [0], libvirt now also FTBFS on at
least mipsel and s390x with the following error:
make[4]: Entering directory '/«PKGBUILDDIR»/debian/build/examples/dommigrate'
make[4]: Nothing to be done for 'install-exec-am'.
Your message dated Sat, 10 May 2014 19:18:41 +
with message-id
and subject line Bug#744696: fixed in fish 2.1.0-1
has caused the Debian Bug report #744696,
regarding [fish][DFSG] missing sources
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Dear maintainer,
I agree with Maurizio and Laurent.
I tested using start-stop-daemon as in the following patch and hibernation
in KDE works nicely with it.
I used the patch of Maurizio, but splitted the call to start-stop-daemon into
mutiple lines and KMail should post this without wordwrap issu
Your message dated Sat, 10 May 2014 18:19:54 +
with message-id
and subject line Bug#747382: fixed in rails-3.2 3.2.18-1
has caused the Debian Bug report #747382,
regarding rails-3.2: CVE-2014-0130: Directory Traversal Vulnerability With
Certain Route Configurations
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> # correct forwarded address
> forwarded 747592 http://sourceforge.net/p/autogen/bugs/160/
Bug #747592 [src:autogen] autogen: build hangs on testsuite (amd64)
Changed Bug forwarded-to-address to
'http://sourceforge.net/p/autogen/bugs/160/' from
'
Processing commands for cont...@bugs.debian.org:
> tags 747558 + sid jessie
Bug #747558 [adacontrol] adacontrol: depends on conflicting gnat, gnat-4.6 and
gnat-4.9
Added tag(s) sid and jessie.
> tags 747557 + sid jessie
Bug #747557 [adabrowse] adabrowse: depends on conflicting gnat, gnat-4.6 and
Your message dated Sat, 10 May 2014 17:34:27 +
with message-id
and subject line Bug#745339: fixed in xwelltris 1.0.1-16
has caused the Debian Bug report #745339,
regarding xwelltris: Doesn't start (Loading resources..ERROR: Can't find file)
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> clone 747382 -1
Bug #747382 [src:rails-3.2] rails-3.2: CVE-2014-0130: Directory Traversal
Vulnerability With Certain Route Configurations
Bug 747382 cloned as bug 747641
> reassign -1 ruby-actionpack-3.2
Bug #747641 [src:rails-3.2] rails-3.2: CVE
Processing commands for cont...@bugs.debian.org:
> severity 747535 important
Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading
to/installing jessie
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> #dirmngr (1.1.1-1.2) unstable; urgency=medium
> #
> # * Use start-stop-daemon instead of su to start the daemon. su is actually
> #opening a PAM session which can cause several issues.
> #Thanks to Maurizio Avogadro (Closes: #717731, #670
Hi Andreas, (and others! :-) )
> Can anyone of you still reproduce the problem[1] with seahorse 3.12
> as currently available in Debian testing/unstable?
>
>
I've migrated from GNOME to Xfce. In Xfce, the program works correctly!
(...I have not installed dconf-editor).
Bye!
I. De March
On 05/10/14 03:20, Andreas Metzler wrote:
Control: forwarded 747592 http://sourceforge.net/p/autogen/bugs/161/
Control: tags 747592 confirmed upstream
Control: severity 747592 serious
On 2014-05-10 Hector Oron wrote:
Source: autogen
Version: 5.18.3~pre34
[...]
Hello,
When attempting to
Package: akonadi-server
Version: 1.11.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** After upgrade to 12-1-1 the akonadi-server can't be launch always it fails,
i make many test and it seems that they can't see the mysql akonadi base.
when akonadi-server fails ko
Your message dated Sat, 10 May 2014 16:49:22 +
with message-id
and subject line Bug#733383: fixed in xastir 2.0.0-2.2
has caused the Debian Bug report #733383,
regarding xastir: FTBFS: collect2: error: ld returned 1 exit status
to be marked as done.
This means that you claim that the problem
On 10/05/14 05:26, Josh Triplett wrote:
> If the maintainers of the packages involved have done their jobs well
> (and they have), upgrading should be an entirely smooth process. Much
> like upgrading to a new version of the Linux kernel or a new bootloader,
> you won't actually get the new versio
Your message dated Sat, 10 May 2014 16:04:09 +
with message-id
and subject line Bug#710194: fixed in gxine 0.5.908-2
has caused the Debian Bug report #710194,
regarding Uses deprecated HAL on non-Linux
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Sat, 10 May 2014 15:45:46 +
with message-id
and subject line Bug#731823: fixed in vtk 5.8.0-17
has caused the Debian Bug report #731823,
regarding major version 51 is newer than 50, the highest major version
supported by this compiler.
to be marked as done.
This means that
Your message dated Sat, 10 May 2014 15:41:02 +
with message-id
and subject line Bug#747565: fixed in libvirt 1.2.4-2
has caused the Debian Bug report #747565,
regarding FTBFS on i386: failing test-suite
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Sat, 10 May 2014 17:17:49 +0200
with message-id <20140510151749.ga14...@jadzia.comodo.priv.at>
and subject line Re: Bug#747626: FTBFS: test failures
has caused the Debian Bug report #747626,
regarding Newer version of libscalar-does-perl needed that deals with changes
in libtype
Your message dated Sat, 10 May 2014 15:37:24 +
with message-id
and subject line Bug#746094: fixed in eliom 3.0.3-5
has caused the Debian Bug report #746094,
regarding eliom: FTBFS: Error while running external preprocessor
to be marked as done.
This means that you claim that the problem has b
Your message dated Sat, 10 May 2014 15:37:31 +
with message-id
and subject line Bug#747525: fixed in equalx 0.6.0-2
has caused the Debian Bug report #747525,
regarding equalx: FTBFS: pkg-config: not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 10 May 2014 17:12:53 +0200
with message-id <20140510151253.14931.41...@bastian.jones.dk>
and subject line Fixed by release of 0.042-1
has caused the Debian Bug report #746064,
regarding libtype-tiny-perl: FTBFS: Tests failures
to be marked as done.
This means that you claim
Hi!
Steven Chamberlain writes:
> Everything can be deleted from
> ~/gcc-4.7-4.7.3/src/gcc/testsuite/gcc.c-torture/compile/ except for
> pr44686.c, which necessitates building tls_runtime, which triggers the
> bug immediately.
>
> The tls_runtime exe survives a reboot if building on ufs mounted wi
Package: alacarte
Version: 3.10.0-1
Followup-For: Bug #731458
Dear Maintainer,
I had this same issue, it was only when I was reporting this that I discovered
they were in the other section, and not just invisible in alacarte. Sometimes
they do have an icon, sometimes they don't. Jpegs and .jpg sh
Processing commands for cont...@bugs.debian.org:
> reassign 747626 libscalar-does-perl 0.200-2
Bug #747626 [libsql-abstract-more-perl] Newer version of libscalar-does-perl
needed that deals with changes in libtype-tiny-perl
Bug reassigned from package 'libsql-abstract-more-perl' to
'libscalar-do
Processing control commands:
> reassign -1 libscalar-does-perl/0.200-2
Unknown command or malformed arguments to command.
> retitle -1 Newer version of libscalar-does-perl needed that deals with
> changes in libtype-tiny-perl
Bug #747626 [libsql-abstract-more-perl] FTBFS: test failures
Changed B
Control: reassign -1 libscalar-does-perl/0.200-2
Control: retitle -1 Newer version of libscalar-does-perl needed that deals with
changes in libtype-tiny-perl
Control: affects -1 libsql-abstract-more-perl
On Sat, 10 May 2014 15:22:12 +0200, gregor herrmann wrote:
> Package: libsql-abstract-more-p
Processing control commands:
> severity -1 serious
Bug #665720 [iptables-persistent] iptables-persistent: unusable with systemd
Severity set to 'serious' from 'critical'
--
665720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665720
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Your message dated Sat, 10 May 2014 13:34:01 +
with message-id
and subject line Bug#665720: fixed in iptables-persistent 1.0.1
has caused the Debian Bug report #665720,
regarding iptables-persistent: unusable with systemd
to be marked as done.
This means that you claim that the problem has be
Control: severity -1 serious
Hi,
On Wed, May 07, 2014 at 06:20:02PM +0100, Jakub Warmuz wrote:
> Unfortunately, I'm *unable to boot* the system with
> netfilter-persistent systemd service enabled!
>
> Removing "quiet" from the kernel parameters, reveals that it hangs
> with the following message
reopen 668890
thanks
Hi,
I'm reopening this bug as I also feel that an initscript shouldn't call
su at all and use start-stop-daemon instead.
Using su is starting a PAM session which can call a bunch a modules
including modules like pam_systemd or pam_ck_connector which can cause
issues like #72
Package: libsql-abstract-more-perl
Version: 1.17-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The package doesn't build anymore (neither 1.17-2 in the archive nor
the new upstream release 1.21);
Processing commands for cont...@bugs.debian.org:
> reopen 668890
Bug #668890 {Done: Thorsten Glaser } [dirmngr] dirmngr: Init
scripts read /etc/profile
Bug #674116 {Done: Thorsten Glaser } [dirmngr] dirmngr: init
script does not write pid into the pid file
Bug #695503 {Done: Thorsten Glaser } [d
Processing commands for cont...@bugs.debian.org:
> tags 665720 + pending
Bug #665720 [iptables-persistent] iptables-persistent: unusable with systemd
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
665720: http://bugs.debian.org/cgi-bin/bugre
Your message dated Sat, 10 May 2014 12:49:24 +
with message-id
and subject line Bug#734975: fixed in ruby-libvirt 0.5.1-3
has caused the Debian Bug report #734975,
regarding ruby-libvirt: FTBFS on all buildds
to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Sat, 10 May 2014 12:49:24 +
with message-id
and subject line Bug#738383: fixed in ruby-libvirt 0.5.1-3
has caused the Debian Bug report #738383,
regarding ruby-libvirt: FTBFS: trying to access file in $HOME dir
to be marked as done.
This means that you claim that the proble
Sorry, my. I will reupload it, using your version.
Ragards
Anton
2014-05-10 13:39 GMT+02:00 Gianfranco Costamagna
:
> Hi all, I grabbed the deb from debian incoming and this bug is NOT fixed.
>
>
> Can you please upload again with the real fix from mentors?
>
>
>
> There is also a build failure
Hi all, I grabbed the deb from debian incoming and this bug is NOT fixed.
Can you please upload again with the real fix from mentors?
There is also a build failure on kfreebsd-amd64, don't know if related to this
fix
https://buildd.debian.org/status/fetch.php?pkg=vtk&arch=kfreebsd-amd64&ver=5
Processing commands for cont...@bugs.debian.org:
> notfixed 731823 5.8.0-16
Bug #731823 {Done: Anton Gladky } [libvtk-java] major version
51 is newer than 50, the highest major version supported by this compiler.
No longer marked as fixed in versions vtk/5.8.0-16.
> reopen 731823
Bug #731823 {Don
Processing commands for cont...@bugs.debian.org:
> severity 747535 serious
Bug #747535 [systemd-sysv] systemd-sysv: Ask before installing when upgrading
to/installing jessie
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Sat, 10 May 2014 11:04:39 +
with message-id
and subject line Bug#746095: fixed in oasis 0.3.0-5
has caused the Debian Bug report #746095,
regarding oasis: FTBFS: Error: Unbound module ExtString
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> found 747592 1:5.18.3~pre34-1
Bug #747592 [src:autogen] autogen: build hangs on testsuite (amd64)
Marked as found in versions autogen/1:5.18.3~pre34-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
747592: http:
Processing commands for cont...@bugs.debian.org:
> notfound 747592 5.18.3~pre34
Bug #747592 [src:autogen] autogen: build hangs on testsuite (amd64)
The source 'autogen' and version '5.18.3~pre34' do not appear to match any
binary packages
No longer marked as found in versions autogen/5.18.3~pre34
Processing control commands:
> forwarded 747592 http://sourceforge.net/p/autogen/bugs/161/
Bug #747592 [src:autogen] autogen: build hangs on testsuite (amd64)
Set Bug forwarded-to-address to 'http://sourceforge.net/p/autogen/bugs/161/'.
> tags 747592 confirmed upstream
Bug #747592 [src:autogen] au
Your message dated Sat, 10 May 2014 09:49:55 +
with message-id
and subject line Bug#722559: fixed in ocaml-estring 20130822-3
has caused the Debian Bug report #722559,
regarding libestring-ocaml{, -dev}: fails to upgrade from 'testing' - trying to
overwrite /usr/lib/ocaml/estring/META, /usr/l
Your message dated Sat, 10 May 2014 09:25:50 +
with message-id
and subject line Bug#731823: fixed in vtk 5.8.0-16
has caused the Debian Bug report #731823,
regarding major version 51 is newer than 50, the highest major version
supported by this compiler.
to be marked as done.
This means that
Hi Anton, thanks again for the upload, but are you sure my patch alone is
enough?
Because I started from Jordi's modifications, that were into the
allpatches.patch patch
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=42;bug=731823
I don't know if it works without them, did you test it?
also
Source: haskell-algebra
Version: 3.1-2
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
this package is obsolete and ought to be removed.
(This bug is an experiment to see if auto-testing-removal will allow the
Haskell transition to happen before ftp-master have removed the p
Processing commands for cont...@bugs.debian.org:
> block 747580 with 747582 744033 744812 722362 743994
Bug #747580 [ftp.debian.org] RM: ruby1.9.1 -- ROM; obsolete, replaced by
ruby2.1, unsupported
747580 was not blocked by any bugs.
747580 was not blocking any bugs.
Added blocking bug(s) of 7475
Source: htree
Version: 0.8-1
Severity: serious
Dear Maintainer,
Your package depends on an obsolete version of Ruby.
Please migrate it to use the ruby(-all)(-dev) metapackages.
Thanks,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe
Control: reopen -1
Hello,
>* Don't depend on HAL. (Closes: #710194)
But then please also drop WITH_HWINFO = --with-hal from debian/rules,
otherwise it FTBFS :)
Samuel
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Processing control commands:
> reopen -1
Bug #710194 {Done: Darren Salt } [src:gxine] Uses
deprecated HAL on non-Linux
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fix
Hi Gianfranco,
thanks for the fix! I have applied your patch and made an upload.
http://anonscm.debian.org/gitweb/?p=collab-maint/vtk.git;a=commitdiff;h=5e721d4f2721b41c528ccd5960e6196ff4a77318
Anton
2014-05-10 0:09 GMT+02:00 Gianfranco Costamagna :
> Hi Anton,
>
> Thanks to you for the uplo
Processing commands for cont...@bugs.debian.org:
> severity 745798 important
Bug #745798 {Done: Alexander Wirt } [amavisd-new] privacy
violation/ban emails reveal re-written addresses
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assi
severity 745798 important
thanks
Severity serious is for serious policy violations. As this is not a Debian
policy violation, serious is not applicable.
The bug doesn't make the package unusable, cause data loss, or introduce a
security hole on the systems where it is installed. So neither grave
Your message dated Sat, 10 May 2014 08:58:10 +0200
with message-id <20140510065808.ga18...@pi.fatal.se>
and subject line [mmyan...@gmail.com: bug already been fixed]
has caused the Debian Bug report #714585,
regarding seahorse: Seahorse consistently crashes after selecting to view by
keyring once
81 matches
Mail list logo