Bug#755094: transition: harfbuzz

2014-07-19 Thread Emilio Pozuelo Monfort
On 17/07/14 18:56, أحمد المحمودي wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
>  Transition is due to upstream API change: replacement of 
>  'hb_version_check' with 'hb_version_atleast'.

I see the package in NEW is 0.9.30 but upstream has just released 0.9.32. Can
you check if there are any other breaks in 0.9.32, and if so update to it?

Emilio


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53ca2d8b.5030...@debian.org



Bug#755212: transition: protobuf-c

2014-07-19 Thread Emilio Pozuelo Monfort
Hi Robert,

On 18/07/14 22:19, Robert Edmonds wrote:
> I am requesting an upload slot to upload protobuf-c 1.0.0-1 to unstable.
> I am hoping to accomplish a transition to protobuf-c 1.0.0 in time for
> the jessie release.  (Disclaimer: I am also one of the protobuf-c
> upstream maintainers.)  This requires an ABI bump as well as some other
> changes that affect reverse (build-) dependencies, described below.

Can you open bug reports for the rdeps that need patches and make them block
this bug? Also file bugs for your recommendations (e.g. ship .proto files) and
the code copy, though those are not blockers IIUC.

Please go ahead with this if you are ready to NMU the rdeps after the transition
starts (assuming the maintainers don't do it, of course).

Emilio


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53ca3488.1020...@debian.org



Bug#638781: marked as done (RM: libgtfb -- RoQA; broken)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:51:08 +
with message-id 
and subject line Bug#638781: Removed package(s) from oldstable
has caused the Debian Bug report #638781,
regarding RM: libgtfb -- RoQA; broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
638781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Tags: squeeze
Usertags: rm

(x-debbugs-cc libgtfb@pdo)

libgtfb0 and libgtfb-dev's symlinks point either somewhere in
/build/buildd (on !amd64) or to /home/flatmax (on amd64).  I'm guessing
this means the package is unusable on all archs and all systems, so
should be either fixed or removed from stable.  Considering no user
reported the problem since the package was uploaded and it was only
spotted by a lintian maintainer, removal seems like the better path IMO.

Cheers,
Julien


--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

   libgtfb |0.1.0-1 | source
  libgtfb0 |0.1.0-1 | amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
libgtfb0-dev |0.1.0-1 | amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
broken
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 638...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/638781

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#740546: marked as done (RM: hlbrw/0.2.4-1; removed from unstable, useless)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:51:40 +
with message-id 
and subject line Bug#740546: Removed package(s) from oldstable
has caused the Debian Bug report #740546,
regarding RM: hlbrw/0.2.4-1; removed from unstable, useless
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
740546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

This package is a specific tool for hlbr, that has an removal request
(please, see #740477).

This package was already removed from unstable/testing. I am asking for
removal from oldstable/stable. Thanks.

Regards,

Eriberto
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

 hlbrw |0.2.4-1 | source, all

--- Reason ---
depends on to-be-removed hlbr
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 740...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/740546

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#740545: marked as done (RM: hlbr/1.7.2-2; removed from unstable, critical bugs)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:52:08 +
with message-id 
and subject line Bug#740545: Removed package(s) from oldstable
has caused the Debian Bug report #740545,
regarding RM: hlbr/1.7.2-2; removed from unstable, critical bugs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
740545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

The project was abandoned and the software has several bugs. It should not be
used on current networks (upstream recommendation)[1].

The package was already removed from unstable/testing. I am asking for removal
from oldstable/stable. Thanks.

PS: I am an upstream of the HLBR.

Regards,

Eriberto

[1] http://hlbr.sourceforge.net/index.html.en
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

  hlbr |1.7.2-2 | source, amd64, armel, i386, ia64, mips, mipsel, 
powerpc, s390, sparc

--- Reason ---
broken
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 740...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/740545

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753494: marked as done (RM: gksu-polkit -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:53:36 +
with message-id 
and subject line Bug#753494: Removed package(s) from oldstable
has caused the Debian Bug report #753494,
regarding RM: gksu-polkit -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

gksu-polkit |0.0.2-2 | source, amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
libgksu-polkit-dev |0.0.2-2 | amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc
libgksu-polkit0 |0.0.2-2 | amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753494

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#752567: marked as done (RM: flashplugin-nonfree -- RoM; security issues)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:52:36 +
with message-id 
and subject line Bug#752567: Removed package(s) from oldstable
has caused the Debian Bug report #752567,
regarding RM: flashplugin-nonfree -- RoM; security issues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
752567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: rm
Tags: squeeze
X-Debbugs-CC: Bart Martens 
Control: submitter -1 Bart Martens 

On Tue, 2014-06-24 at 17:58 +, Bart Martens wrote:
> Hello,
> 
> Please remove flashplugin-nonfree 1:2.8.2+squeeze1 from oldstable. I agreed
> with the security team to not provide a fix for bug 752277 and request the
> removal of the package from oldstable instead.
> 
> Regards,
> 
> Bart Martens
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

flashplugin-nonfree | 1:2.8.2+squeeze1 | source, amd64, i386

--- Reason ---
security issues
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 752...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/752567

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#752883: marked as done (RM: whatsnewfm -- ROM; obsolete; abandoned upstream)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:53:08 +
with message-id 
and subject line Bug#752883: Removed package(s) from oldstable
has caused the Debian Bug report #752883,
regarding RM: whatsnewfm -- ROM; obsolete; abandoned upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
752883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

This package is no longer useful since the underlying service (freecode.com)
has now shut down and is no longer accepting new submissions:

"The Freecode site has been moved to a static state effective June 18, 2014
due to low traffic levels and so that folks will focus on more useful
endeavors than site upkeep."

source: http://freecode.com/about


For more info, see the unstable removal request #752560 (already closed):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752560


-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Christian.Garbs.http://www.cgarbs.de

"Es ist schon ganz gut, daß Microsoft keine Autos entwickelt. Jedes
Auto hätte ein Lenkrad, einen Joystick, eine Fernbedienung und Griffe
auf dem Heck für Leute, die es vorziehen, ihr Auto zu schieben."
 (Andy Rathbone, Windows für Dumme^H^H^H^H^HAnfänger)


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

whatsnewfm | 0.7.2-0+squeeze1 | source, all

--- Reason ---
obsolete as freecode.com is no longer accepting submissions
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 752...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/752883

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753497: marked as done (RM: couchdb -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:54:58 +
with message-id 
and subject line Bug#753497: Removed package(s) from oldstable
has caused the Debian Bug report #753497,
regarding RM: couchdb -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753497
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

   couchdb | 0.11.0-2.3 | source, amd64, armel, i386, ia64, kfreebsd-amd64, 
kfreebsd-i386, mips, mipsel, powerpc, s390, sparc

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753497

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753495: marked as done (RM: bugzilla -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:54:02 +
with message-id 
and subject line Bug#753495: Removed package(s) from oldstable
has caused the Debian Bug report #753495,
regarding RM: bugzilla -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

  bugzilla | 3.6.2.0-4.6 | source
 bugzilla3 | 3.6.2.0-4.6 | all
bugzilla3-doc | 3.6.2.0-4.6 | all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753495

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753498: marked as done (RM: mahara -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:55:33 +
with message-id 
and subject line Bug#753498: Removed package(s) from oldstable
has caused the Debian Bug report #753498,
regarding RM: mahara -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

mahara | 1.2.6-2+squeeze6 | source, all
mahara-apache2 | 1.2.6-2+squeeze6 | all
mahara-mediaplayer | 1.2.6-2+squeeze6 | all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753498

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753496: marked as done (RM: fusionforge -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:54:33 +
with message-id 
and subject line Bug#753496: Removed package(s) from oldstable
has caused the Debian Bug report #753496,
regarding RM: fusionforge -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

fusionforge | 5.0.2-5+squeeze2 | source
fusionforge-full | 5.0.2-5+squeeze2 | all
fusionforge-minimal | 5.0.2-5+squeeze2 | all
fusionforge-standard | 5.0.2-5+squeeze2 | all
gforge | 5.0.2-5+squeeze2 | all
gforge-common | 5.0.2-5+squeeze2 | all
gforge-db-postgresql | 5.0.2-5+squeeze2 | all
gforge-dns-bind9 | 5.0.2-5+squeeze2 | all
gforge-ftp-proftpd | 5.0.2-5+squeeze2 | all
gforge-lists-mailman | 5.0.2-5+squeeze2 | all
gforge-mta-courier | 5.0.2-5+squeeze2 | all
gforge-mta-exim4 | 5.0.2-5+squeeze2 | all
gforge-mta-postfix | 5.0.2-5+squeeze2 | all
gforge-plugin-contribtracker | 5.0.2-5+squeeze2 | all
gforge-plugin-extratabs | 5.0.2-5+squeeze2 | all
gforge-plugin-globalsearch | 5.0.2-5+squeeze2 | all
gforge-plugin-mediawiki | 5.0.2-5+squeeze2 | all
gforge-plugin-projectlabels | 5.0.2-5+squeeze2 | all
gforge-plugin-scmarch | 5.0.2-5+squeeze2 | all
gforge-plugin-scmbzr | 5.0.2-5+squeeze2 | all
gforge-plugin-scmcvs | 5.0.2-5+squeeze2 | all
gforge-plugin-scmdarcs | 5.0.2-5+squeeze2 | all
gforge-plugin-scmgit | 5.0.2-5+squeeze2 | all
gforge-plugin-scmhg | 5.0.2-5+squeeze2 | all
gforge-plugin-scmsvn | 5.0.2-5+squeeze2 | all
gforge-shell-postgresql | 5.0.2-5+squeeze2 | all
gforge-web-apache | 5.0.2-5+squeeze2 | all
gforge-web-apache2 | 5.0.2-5+squeeze2 | all
gforge-web-apache2-vhosts | 5.0.2-5+squeeze2 | all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753496

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753499: marked as done (RM: mantis -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:56:27 +
with message-id 
and subject line Bug#753499: Removed package(s) from oldstable
has caused the Debian Bug report #753499,
regarding RM: mantis -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

mantis | 1.1.8+dfsg-10squeeze2 | source, all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753499

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753500: marked as done (RM: movabletype-opensource -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:57:02 +
with message-id 
and subject line Bug#753500: Removed package(s) from oldstable
has caused the Debian Bug report #753500,
regarding RM: movabletype-opensource -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

movabletype-opensource | 4.3.8+dfsg-0+squeeze4 | source, all
movabletype-plugin-core | 4.3.8+dfsg-0+squeeze4 | all
movabletype-plugin-zemanta | 4.3.8+dfsg-0+squeeze4 | all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753500

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753504: marked as done (RM: openswan -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:59:38 +
with message-id 
and subject line Bug#753504: Removed package(s) from oldstable
has caused the Debian Bug report #753504,
regarding RM: openswan -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

  openswan | 1:2.6.28+dfsg-5+squeeze1 | source, amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc
openswan-dbg | 1:2.6.28+dfsg-5+squeeze1 | amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc
openswan-doc | 1:2.6.28+dfsg-5+squeeze1 | all
openswan-modules-dkms | 1:2.6.28+dfsg-5+squeeze1 | amd64, armel, i386, ia64, 
mips, mipsel, powerpc, s390, sparc
openswan-modules-source | 1:2.6.28+dfsg-5+squeeze1 | all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753504

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753502: marked as done (RM: spip -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:58:11 +
with message-id 
and subject line Bug#753502: Removed package(s) from oldstable
has caused the Debian Bug report #753502,
regarding RM: spip -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

  spip | 2.1.1-3squeeze8 | source, all
  spip | 2.1.1-3squeeze9 | source, all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753502

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753503: marked as done (RM: zabbix -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:58:57 +
with message-id 
and subject line Bug#753503: Removed package(s) from oldstable
has caused the Debian Bug report #753503,
regarding RM: zabbix -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

zabbix | 1:1.8.2-1squeeze5 | source
zabbix-agent | 1:1.8.2-1squeeze5 | amd64, armel, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
zabbix-frontend-php | 1:1.8.2-1squeeze5 | all
zabbix-proxy-mysql | 1:1.8.2-1squeeze5 | amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc
zabbix-proxy-pgsql | 1:1.8.2-1squeeze5 | amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc
zabbix-server-mysql | 1:1.8.2-1squeeze5 | amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc
zabbix-server-pgsql | 1:1.8.2-1squeeze5 | amd64, armel, i386, ia64, mips, 
mipsel, powerpc, s390, sparc

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753503

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#753501: marked as done (RM: serendipity -- RoST; security support ended)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 09:57:29 +
with message-id 
and subject line Bug#753501: Removed package(s) from oldstable
has caused the Debian Bug report #753501,
regarding RM: serendipity -- RoST; security support ended
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
753501: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,
as briefly discussed on #debian-release. Please remove this package
in the 6.0.10 point release. It's not covered by squeeze-lts support
and debian-security-support marks existing packages as deprecated.
Removing it ensures that new squeeze installations (which can still
happen in some cases) odon't install an unsupported package. It make
tracking open issues easier. And the binaries can still be fetched
from snapshot.debian.org.

I've tested the removability with "dak rm -Rn -s oldstable $PKG"

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

serendipity |1.5.3-2 | source, all

--- Reason ---
security support ended
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 753...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/753501

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#754836: marked as done (RM: libplrpc-perl/0.2020-2)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 10:00:35 +
with message-id 
and subject line Bug#754836: Removed package(s) from oldstable
has caused the Debian Bug report #754836,
regarding RM: libplrpc-perl/0.2020-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Control: blocks -1 by 754834

This is the corresponding request to remove libplrpc-perl from
squeeze, as in [1] for wheezy. Can removal for libplrpc-perl also be
scheduled for the final squeeze point release?

 [1] http://bugs.debian.org/752236

Thanks for considering at this late stage if possible,

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

libplrpc-perl |   0.2020-2 | source, all

--- Reason ---
security issues
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/754836

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Bug#754837: marked as done (RM: libplrpc-perl/0.2020-2)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 10:00:35 +
with message-id 
and subject line Bug#754836: Removed package(s) from oldstable
has caused the Debian Bug report #754836,
regarding RM: libplrpc-perl/0.2020-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
754836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi Release Team

Note, I'm not the maintainer of libplrpc-perl, but Anibal is
Debbug-CC'ed in this request.

As already done for unstable, libplrpc-perl was removed from the
archive[1]. Thanks also for accepting the update for libdbi-perl
dropping the dependency to libplrpc-perl[2].

 [1] https://bugs.debian.org/745477
 [2] https://bugs.debian.org/751527

Can you schedule a removal for libplrpc-perl from stable in the next
wheezy point release, or a later one at least?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from oldstable:

libplrpc-perl |   0.2020-2 | source, all

--- Reason ---
security issues
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 754...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/754836

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)--- End Message ---


Re: Linux kernel ABI bump

2014-07-19 Thread Ian Campbell
On Fri, 2014-07-18 at 17:48 +0100, Ben Hutchings wrote:
> A kernel ABI bump is needed to enable:
> 
> - [powerpc] CONFIG_PPC_TRANSACTIONAL_MEM
> - [powerpc/powerpc64] CONFIG_JUMP_LABEL
> - CONFIG_DYNAMIC_DEBUG
> 
> I propose to make these changes with the next upload to unstable.
> 
> If anyone else has an ABI-breaking change planned, we should try to get
> that done at the same time.

The fix for the arm64 aufs FTBFS issue looks likely to require an ABI
bump.

Ian.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1405765026.27009.3.ca...@dagon.hellion.org.uk



Processed: limit package to release.debian.org, closing 699591, closing 740241, closing 740640, closing 741684 ...

2014-07-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # The fixes discussed in these bugs were included in the 6.0.10 point release
> limit package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> close 699591 6.0.10
Bug #699591 [release.debian.org] exim4 upload to stable (dovecot stability / 
and optionally spf quoting)
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #699591 [release.debian.org] exim4 upload to stable (dovecot stability / 
and optionally spf quoting)
Marked Bug as done
> close 740241 6.0.10
Bug #740241 [release.debian.org] squeeze-pu: package 
debian-edu-archive-keyring/2010.01.05+squeeze1
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #740241 [release.debian.org] squeeze-pu: package 
debian-edu-archive-keyring/2010.01.05+squeeze1
Marked Bug as done
> close 740640 6.0.10
Bug #740640 [release.debian.org] squeeze-pu: package 
libfinance-quote-perl/1.17-1+deb6u1
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #740640 [release.debian.org] squeeze-pu: package 
libfinance-quote-perl/1.17-1+deb6u1
Marked Bug as done
> close 741684 6.0.10
Bug #741684 [release.debian.org] opu: package clamav/0.98.1+dfsg-1+deb6u2
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #741684 [release.debian.org] opu: package clamav/0.98.1+dfsg-1+deb6u2
Marked Bug as done
> close 744820 6.0.10
Bug #744820 [release.debian.org] squeeze-pu: package catfish/0.3.2-2+deb7u1
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #744820 [release.debian.org] squeeze-pu: package catfish/0.3.2-2+deb7u1
Marked Bug as done
> close 746714 6.0.10
Bug #746714 [release.debian.org] squeeze-pu: package cups/1.4.4-7+squeeze5
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #746714 [release.debian.org] squeeze-pu: package cups/1.4.4-7+squeeze5
Marked Bug as done
> close 749366 6.0.10
Bug #749366 [release.debian.org] squeeze-pu: package suds/0.3.9-1+deb6u2 
Bug#749073
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #749366 [release.debian.org] squeeze-pu: package suds/0.3.9-1+deb6u2 
Bug#749073
Marked Bug as done
> close 753310 6.0.10
Bug #753310 [release.debian.org] opu: ia32-libs/20140630 ia32-libs-gtk/20140630
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #753310 [release.debian.org] opu: ia32-libs/20140630 ia32-libs-gtk/20140630
Marked Bug as done
> close 753686 6.0.10
Bug #753686 [release.debian.org] squeeze-pu: package 
mobile-broadband-provider-info/20140317-1~deb6u1
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #753686 [release.debian.org] squeeze-pu: package 
mobile-broadband-provider-info/20140317-1~deb6u1
Marked Bug as done
> close 754834 6.0.10
Bug #754834 [release.debian.org] squeeze-pu: package libdbi-perl/1.612-1+deb6u1
There is no source info for the package 'release.debian.org' at version 
'6.0.10' with architecture ''
Unable to make a source version for version '6.0.10'
Marked as fixed in versions 6.0.10.
Bug #754834 [release.debian.org] squeeze-pu: package libdbi-perl/1.612-1+deb6u1
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
699591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699591
740241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740241
740640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740640
741684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741684
744820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744820
746714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746714
749366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749366
753310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753310
753686: http://bugs.debian.o

Bug#742637: marked as done (squeeze-pu: package spip/2.1.1-3squeeze9)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 12:29:19 +0100
with message-id <1405769359.9607.4.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#742637: squeeze-pu: package spip/2.1.1-3squeeze9
has caused the Debian Bug report #742637,
regarding squeeze-pu: package spip/2.1.1-3squeeze9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
742637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: squeeze
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

As agreed with the security team, here I am proposing another oldstable
update for fixing minor security issues in SPIP. Attached debdiff,
thanks in advance for considering.

Regards

David


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/changelog b/debian/changelog
index 0427965..25a8296 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+spip (2.1.1-3squeeze9) squeeze; urgency=medium
+
+  * Fix missing escape
+  * Fix missing escape in SQL
+  * Update security screen to 1.1.9 (Closes: #742456)
+
+ -- David Prévot   Thu, 13 Mar 2014 16:58:14 -0300
+
 spip (2.1.1-3squeeze8) squeeze; urgency=medium
 
   * Document fixed #729172
diff --git a/debian/patches/fix_missing_escape.patch b/debian/patches/fix_missing_escape.patch
new file mode 100644
index 000..7d08c36
--- /dev/null
+++ b/debian/patches/fix_missing_escape.patch
@@ -0,0 +1,19 @@
+From: Cédric Morin 
+Subject: Fix missing escape
+
+ * ecrire/inc/log.php: Always escape < in logs, unless the _LOG_BRUT
+   constant is defined to true at the end of debug.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21251
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/inc/log.php
 b/ecrire/inc/log.php
+@@ -56,7 +56,7 @@
+ 
+ 	$f = @fopen($logfile, "ab");
+ 	if ($f) {
+-		fputs($f, ($logname!==NULL) ? $m : str_replace('<','<',$m));
++		fputs($f, (defined('_LOG_BRUT') AND _LOG_BRUT) ? $m : str_replace('<','<',$m));
+ 		fclose($f);
+ 	}
+ 
diff --git a/debian/patches/fix_missing_escape_in_SQL.patch b/debian/patches/fix_missing_escape_in_SQL.patch
new file mode 100644
index 000..8024698
--- /dev/null
+++ b/debian/patches/fix_missing_escape_in_SQL.patch
@@ -0,0 +1,18 @@
+From: Cédric Morin 
+Subject: Fix missing escape in SQL
+
+ * ecrire/inc/quete.php: Fix missing escape in a SQL request.
+
+Origin: upstream, http://core.spip.org/projects/spip/repository/revisions/21247
+Bug-Debian: http://bugs.debian.org/742456
+--- a/ecrire/public/quete.php
 b/ecrire/public/quete.php
+@@ -248,7 +248,7 @@
+ $exposer[$m][$type][$principal] = true;
+ if ($type == 'id_mot'){
+ 	if (!$parent) {
+-		$parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . $principal, '','','','',$connect);
++		$parent = sql_getfetsel('id_groupe','spip_mots',"id_mot=" . intval($principal), '','','','',$connect);
+ 	}
+ 	if ($parent)
+ 		$exposer[$m]['id_groupe'][$parent] = true;
diff --git a/debian/patches/series b/debian/patches/series
index 7646257..1ec8a6c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -19,3 +19,5 @@ fix_privilege_escalation_2.1.21.patch
 fix_CSRF_on_logout.patch
 fix_XSS_on_author_page.patch
 fix_XSS_on_signature.patch
+fix_missing_escape.patch
+fix_missing_escape_in_SQL.patch
diff --git a/debian/security/ecran_securite.php b/debian/security/ecran_securite.php
index 7e6ec1c..36b0044 100644
--- a/debian/security/ecran_securite.php
+++ b/debian/security/ecran_securite.php
@@ -5,7 +5,7 @@
  * --
  */
 
-define('_ECRAN_SECURITE', '1.1.8'); // 2013-08-29
+define('_ECRAN_SECURITE', '1.1.9'); // 2014-03-13
 
 /*
  * Documentation : http://www.spip.net/fr_article4200.html
@@ -254,13 +254,12 @@ if (isset($_REQUEST['connect'])
 	AND
 	// cas qui permettent de sortir d'un commentaire PHP
 	(strpos($_REQUEST['connect'], "?")!==false
+	 OR strpos($_REQUEST['connect'], "<")!==false
 	 OR strpos($_REQUEST['connect'], ">")!==false
 	 OR strpos($_REQUEST['connect'], "\n")!==false
 	 OR strpos($_REQUEST['connect'], "\r")!==false)
 	) {
-	$_REQUEST['connect'] = str_replace(array("?", ">", "\r", "\n"), "", $_REQUEST['connect']);
-	if (isset($_GET['co

Processed: user release.debian....@packages.debian.org, usertagging 755175, tagging 755175

2014-07-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 755175 = pu
Usertags were: opu.
Usertags are now: pu.
> tags 755175 + squeeze
Bug #755175 [release.debian.org] opu: package debdelta/0.39+squeeze2
Added tag(s) squeeze.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
755175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.140576944820160.transcr...@bugs.debian.org



Bug#755175: marked as done (opu: package debdelta/0.39+squeeze2)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 12:36:17 +0100
with message-id <1405769777.9607.9.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#755175: opu: package debdelta/0.39+squeeze2
has caused the Debian Bug report #755175,
regarding opu: package debdelta/0.39+squeeze2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
755175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: opu

Dear release team,

in the version of 'debdelta' in squeeze, the PGP keys are too old,
so 'debdelta-upgrade' was useless; this new version contains new keys;

moreover, the new server that builds deltas is creating deltas for
squeeze-backports as well, this new package contains the needed
stanza in the configuration.

As you can see from the attachment, the diff is minimal.

So please approve 'debdelta' for the upcoming squeeze point release.

a.

ps:
 I think that this new package should work fine in squeeze-lts as
  well; it contains keys valid up to 2016

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
Andrea Mennucc
 "E' un mondo difficile. Che vita intensa!" (Tonino Carotone)
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Installed-Size: [-400-] {+392+}
Version: [-0.39trl-] {+0.39+squeeze2+}
diff -Nru debdelta-0.39trl/debian/changelog debdelta-0.39+squeeze2/debian/changelog
--- debdelta-0.39trl/debian/changelog	2010-06-13 16:58:19.0 +0200
+++ debdelta-0.39+squeeze2/debian/changelog	2014-07-18 15:32:22.0 +0200
@@ -1,3 +1,10 @@
+debdelta (0.39+squeeze2) oldstable-proposed-updates; urgency=low
+
+  * new GPG keys
+  * add Debian Backports to sources.conf
+
+ -- A Mennucc1   Fri, 18 Jul 2014 14:55:40 +0200
+
 debdelta (0.39trl) unstable; urgency=high
   
   * The real thing release: upload the real 0.39, not a damaged version;
diff -Nru debdelta-0.39trl/etc/sources.conf debdelta-0.39+squeeze2/etc/sources.conf
--- debdelta-0.39trl/etc/sources.conf	2010-02-27 15:23:17.0 +0100
+++ debdelta-0.39+squeeze2/etc/sources.conf	2014-07-18 15:32:22.0 +0200
@@ -23,6 +23,11 @@
 Label=Debian
 delta_uri=http://debdeltas.debian.net/debian-deltas
 
+[backports debian archive]
+Origin=Debian Backports
+Label=Debian Backports
+delta_uri=http://debdeltas.debian.net/debian-deltas
+
 
 [stable security debian archive]
 Origin=Debian
I file binari /tmp/v3ePCjcgpQ/debdelta-0.39trl/keyrings/pub.gpg e /tmp/L5pW68i948/debdelta-0.39+squeeze2/keyrings/pub.gpg sono diversi


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix

 On Fri, 2014-07-18 at 15:55 +0200, A Mennucc wrote:
> in the version of 'debdelta' in squeeze, the PGP keys are too old,
> so 'debdelta-upgrade' was useless; this new version contains new keys;
> 
> moreover, the new server that builds deltas is creating deltas for
> squeeze-backports as well, this new package contains the needed
> stanza in the configuration.
> 
> As you can see from the attachment, the diff is minimal.
> 
> So please approve 'debdelta' for the upcoming squeeze point release.

As I mentioned in
 (which was
sent before I'd seen this bug report), I'm afraid your upload was far
too late to make it in to the point release (particularly for an
arch:any package).

As this was the final point release for squeeze I'm going to close this
bug now. You may wish to discuss an update in squeeze-lts with the LTS
team.

Regards,

Adam--- End Message ---


Bug#725823: marked as done (pu: package icedove/3.0.11-1+squeeze15)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 12:41:31 +0100
with message-id <1405770091.9607.13.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#725823: pu: package icedove/3.0.11-1+squeeze15
has caused the Debian Bug report #725823,
regarding pu: package icedove/3.0.11-1+squeeze15
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
725823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu

Dear release team,

for the icedove version 3.0.x (and 3.1.x in squeeze-backport) released
with squeeze are some similar bugs opened after the release of squeeze.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626812
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659301
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659994
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660736
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691985

Those bugs are all depened on undefined symbols that all happend after
the libc version > 2.11.3-x. That relay on the order icedove is reading
the symbols from the varous libraries and theese libraries again from
other libraries.

So in the end a fix is basicly simply, icedove has to be started with
the presetted variables LD_LIBRARY_PATH and LD_PRELOAD to be shure the
symbols are readed in the correct order and icedove will start and work
correctly.

The following patch will solve the described issues from the bug reports
above.
The patched file mozilla.in will become /usr/lib/icedove/icedove
(/usr/lib/thunderbird/thunderbird in the original Thunderbird package)
while package creating and is the executable start script for icedove.
This script calls at the end /usr/lib/icedove/run-mozilla.sh that is
shipped by Mozilla.

diff --git a/mozilla/build/unix/mozilla.in b/mozilla/build/unix/mozilla.in
index 4f54e23..336737c 100644
--- a/mozilla/build/unix/mozilla.in
+++ b/mozilla/build/unix/mozilla.in
@@ -134,6 +134,8 @@ if [ $debugging = 1 ]
 then
   echo $dist_bin/run-mozilla.sh $script_args $dist_bin/$MOZILLA_BIN "$@"
 fi
+export LD_LIBRARY_PATH=/usr/lib/icedove
+export LD_PRELOAD=/usr/lib/icedove/libxpcom.so
 "$dist_bin/run-mozilla.sh" $script_args "$dist_bin/$MOZILLA_BIN" "$@"
 exitcode=$?

Any chances to get this change into the next point release for Squeeze?

Regards
Carsten
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix

On Tue, 2014-07-08 at 20:26 +0100, Adam D. Barratt wrote:
> On Tue, 2013-10-08 at 21:30 +0200, Carsten Schoenert wrote:
[...]
> > Those bugs are all depened on undefined symbols that all happend after
> > the libc version > 2.11.3-x. That relay on the order icedove is reading
> > the symbols from the varous libraries and theese libraries again from
> > other libraries.
> > 
> > So in the end a fix is basicly simply, icedove has to be started with
> > the presetted variables LD_LIBRARY_PATH and LD_PRELOAD to be shure the
> > symbols are readed in the correct order and icedove will start and work
> > correctly.
> 
> Apologies if I'm missing something, but why does this only affect the
> squeeze packages?

We don't appear to have received a follow-up there, and as today was the
final point release for squeeze I'm going to close this bug now.

Regards,

Adam--- End Message ---


Bug#687761: marked as done (pu: package lvm2/2.02.66-5+squeeze1)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 12:42:59 +0100
with message-id <1405770179.9607.15.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#687761: pu: package lvm2/2.02.66-5+squeeze1
has caused the Debian Bug report #687761,
regarding pu: package lvm2/2.02.66-5+squeeze1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
687761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I've prepared a NMU for lvm that fixes #603036: "lvm2: fails to install
due to incorrect dependencies in init.d LSB header"

The bug is tagged squeeze-ignore:
On Monday, 27. December 2010 00:06:20 Julien Cristau wrote:
> On Mon, Dec 13, 2010 at 21:35:36 +0100, Petter Reinholdtsen wrote:
> > Given that udev is installed on most Debian systems, it can be
> > argued
> > that this issue is not release critical.  I expect incorrect udev
> Agreed, I won't make this a blocker for squeeze.  A fix would still be
> welcome though.

I'm just adding the udev dependency to the lvm2 package, not touching
the initscript (which has been updated for wheezy to make udev
optional). This just makes the current situation (udev has to be
installed for lvm to work) explicit.

This bug is a bit annoying for piuparts because we need to work around
this for lvm2 and its rdepends, therefore I'd like to see this fixed.

If this request is confirmed, I'll go looking for a sponsor.


Andreas

PS: I just noticed, the version should probably be 2.02.66-5+squeeze1
diffstat for lvm2-2.02.66 lvm2-2.02.66

 changelog |   12 
 control   |2 +-
 2 files changed, 13 insertions(+), 1 deletion(-)

diff -Nru lvm2-2.02.66/debian/changelog lvm2-2.02.66/debian/changelog
--- lvm2-2.02.66/debian/changelog	2011-01-23 18:30:34.0 +0100
+++ lvm2-2.02.66/debian/changelog	2012-09-15 16:39:47.0 +0200
@@ -1,3 +1,15 @@
+lvm2 (2.02.66-5.1) stable; urgency=low
+
+  * Non-maintainer upload.
+  * lvm2: add Depends: udev.  (Closes: #603036)
+This is a workaround for the initscript depending on udev. For wheezy,
+this has been fixed by updating the initscript dependencies, but for
+squeeze let's just depend on the udev package.
+There is no need to restrict this change to [linux-any] since lvm has an
+unrestricted B-D: libudev-dev.
+
+ -- Andreas Beckmann   Sat, 15 Sep 2012 16:27:27 +0200
+
 lvm2 (2.02.66-5) unstable; urgency=low
 
   * Remove old libdevmapper1.02 init script on upgrade. (closes: #549316)
diff -Nru lvm2-2.02.66/debian/control lvm2-2.02.66/debian/control
--- lvm2-2.02.66/debian/control	2011-01-23 18:29:31.0 +0100
+++ lvm2-2.02.66/debian/control	2012-09-15 16:34:43.0 +0200
@@ -11,7 +11,7 @@
 
 Package: lvm2
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base, dmsetup (>> 2:1.02.47)
+Depends: ${shlibs:Depends}, ${misc:Depends}, lsb-base, dmsetup (>> 2:1.02.47), udev
 Breaks: grub-common (<<1.98+20100527-1)
 Conflicts: lvm-common
 Replaces: lvm-common
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix

On Tue, 2014-07-08 at 20:15 +0100, Adam D. Barratt wrote:
> On Mon, 2013-07-01 at 00:01 +0200, Andreas Beckmann wrote:
> > Maybe we can revisit this for the next oldstable update.
> > There was no feedback from the maintainers, but Pierre Ynard (the
> > reporter of #543163) confirmed (see #687761) that he once had a working
> > squeeze setup with lvm2 and no udev by removing the initscript
> > dependency. (He is tracking unstable nowadays and needs/needed some more
> > changes for getting modules loaded, but that's the price for not using
> > udev - and seems to be due to his special hardware setup.)
> > 
> > This change to the initscript won't change anything for existing squeeze
> > installations - either they already have lvm2 + udev installed or
> > manually changed the conffiles to allow lvm2 without udev.
> > But it would simplify my work running (sometimes weird :-) upgrade tests
> > to find "interesting" corner cases - lvm2 has a large rdep tree
> > requiring a lot of workarounds ...
> 
> "The next oldstable update" is now the final update for squeeze. Is this
> still an issue in practical terms?

That final update has now happened, so we can no longer update packages
in squeeze (other than via -lts); I'm going to close this bug now.

Regards,

Adam--- End Message ---


Bug#707550: marked as done (opu: package php-mdb2/2.5.0b2-1)

2014-07-19 Thread Debian Bug Tracking System
Your message dated Sat, 19 Jul 2014 12:46:09 +0100
with message-id <1405770369.9607.17.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#707550: opu: package php-mdb2/2.5.0b2-1
has caused the Debian Bug report #707550,
regarding opu: package php-mdb2/2.5.0b2-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
707550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: opu

Hi,

This is a follow up on one email thread from  list:
  http://lists.debian.org/debian-release/2012/05/msg00182.html

Please apply the attached patch to php-mdb2 package version 2.5.0b2-1
from Debian 6.0 (squeeze) in a future point release (6.0.8 or later).

Cheers

-- System Information:
Debian Release: 7.0
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- /usr/share/php/MDB2.php_2.5.0b2-1	2009-04-25 18:23:22.0 +0300
+++ /usr/share/php/MDB2.php	2012-05-03 18:14:11.451133868 +0300
@@ -390,7 +390,7 @@
 return $err;
 }
 
-$db =& new $class_name();
+$db = new $class_name();
 $db->setDSN($dsninfo);
 $err = MDB2::setOptions($db, $options);
 if (PEAR::isError($err)) {
@@ -2596,7 +2596,7 @@
 }
 
 // }}}
-// {{{ function &_wrapResult($result, $types = array(), $result_class = true, $result_wrap_class = false, $limit = null, $offset = null)
+// {{{ function &_wrapResult($result_resource, $types = array(), $result_class = true, $result_wrap_class = false, $limit = null, $offset = null)
 
 /**
  * wrap a result set into the correct class
@@ -2613,13 +2613,13 @@
  *
  * @access  protected
  */
-function &_wrapResult($result, $types = array(), $result_class = true,
+function &_wrapResult($result_resource, $types = array(), $result_class = true,
 $result_wrap_class = false, $limit = null, $offset = null)
 {
 if ($types === true) {
 if ($this->supports('result_introspection')) {
 $this->loadModule('Reverse', null, true);
-$tableInfo = $this->reverse->tableInfo($result);
+$tableInfo = $this->reverse->tableInfo($result_resource);
 if (PEAR::isError($tableInfo)) {
 return $tableInfo;
 }
@@ -2644,7 +2644,7 @@
 'result class does not exist '.$class_name, __FUNCTION__);
 return $err;
 }
-$result =& new $class_name($this, $result, $limit, $offset);
+$result = new $class_name($this, $result_resource, $limit, $offset);
 if (!MDB2::isResultCommon($result)) {
 $err =& $this->raiseError(MDB2_ERROR_NOT_FOUND, null, null,
 'result class is not extended from MDB2_Result_Common', __FUNCTION__);
@@ -2667,7 +2667,7 @@
 'result wrap class does not exist '.$result_wrap_class, __FUNCTION__);
 return $err;
 }
-$result = new $result_wrap_class($result, $this->fetchmode);
+$result = new $result_wrap_class($result_resource, $this->fetchmode);
 }
 return $result;
 }
--- End Message ---
--- Begin Message ---
Control: tags -1 + wontfix

On Wed, 2014-07-09 at 15:41 +0100, Adam D. Barratt wrote:
> On 2014-07-09 15:08, Thomas Goirand wrote:
> > On 07/09/2014 03:22 AM, Adam D. Barratt wrote:
> >> On Wed, 2014-01-22 at 14:35 +0200, Teodor MICU wrote:
> >>> I don't have the necessary experience to make this source debdiff.
> >>> Thomas, are you still interested in uploading this (simple) patch for
> >>> squeeze?
> >> 
> >> We don't appear to have seen a reply to that, and we're now only a few
> >> days away from the final point release for squeeze.
> [...]
> > Is it ok if I upload now?
> 
> Please could we have a debdiff, just to confirm?

Unfortunately we never got one and as today was the final point release
for squeeze I'm going to close this bug now.

Regards,

Adam--- End Message ---


Bug#755263: wheezy-pu: package ipython/0.13.1-2+deb7u1

2014-07-19 Thread Julian Taylor
Package: release.debian.org
Severity: normal
Tags: wheezy
User: release.debian@packages.debian.org
Usertags: pu

Hi release team

I would like to update ipython in wheezy to fix CVE-2014-3429
It is a remote execution flaw via cross origin websockets, but one
requires a uuid from the process in order to make use of it so it was
decided by the security team that its severe enough for a DSA.
But it should stil be fixed in stable just in case.

See this page for details of the issue:
http://lambdaops.com/cross-origin-websocket-hijacking-of-ipython
diff -Nru ipython-0.13.1/debian/changelog ipython-0.13.1/debian/changelog
--- ipython-0.13.1/debian/changelog	2012-11-25 20:04:22.0 +0100
+++ ipython-0.13.1/debian/changelog	2014-07-16 20:29:04.0 +0200
@@ -1,3 +1,9 @@
+ipython (0.13.1-2+deb7u1) stable-security; urgency=medium
+
+  * Fix CVE-2014-3429: remote execution via cross origin websocket
+
+ -- Julian Taylor   Wed, 16 Jul 2014 20:27:50 +0200
+
 ipython (0.13.1-2) unstable; urgency=low
 
   * update watch file to use github directly
diff -Nru ipython-0.13.1/debian/patches/CVE-2014-3429.patch ipython-0.13.1/debian/patches/CVE-2014-3429.patch
--- ipython-0.13.1/debian/patches/CVE-2014-3429.patch	1970-01-01 01:00:00.0 +0100
+++ ipython-0.13.1/debian/patches/CVE-2014-3429.patch	2014-07-16 20:27:40.0 +0200
@@ -0,0 +1,60 @@
+Description: check origin of websocket connection CVE-2014-3429
+Origin: https://github.com/ipython/ipython/pull/4845
+
+--- a/IPython/frontend/html/notebook/handlers.py
 b/IPython/frontend/html/notebook/handlers.py
+@@ -16,6 +16,11 @@ Authors:
+ # Imports
+ #-
+ 
++try:
++from urllib.parse import urlparse # Py 3
++except ImportError:
++from urlparse import urlparse # Py 2
++
+ import logging
+ import Cookie
+ import time
+@@ -368,6 +373,30 @@ class KernelActionHandler(AuthenticatedH
+ 
+ class ZMQStreamHandler(websocket.WebSocketHandler):
+ 
++def same_origin(self):
++"""Check to see that origin and host match in the headers."""
++
++# The difference between version 8 and 13 is that in 8 the
++# client sends a "Sec-Websocket-Origin" header and in 13 it's
++# simply "Origin".
++if self.request.headers.get("Sec-WebSocket-Version") in ("7", "8"):
++origin_header = self.request.headers.get("Sec-Websocket-Origin")
++else:
++origin_header = self.request.headers.get("Origin")
++
++host = self.request.headers.get("Host")
++
++# If no header is provided, assume we can't verify origin
++if(origin_header is None or host is None):
++return False
++
++parsed_origin = urlparse(origin_header)
++origin = parsed_origin.netloc
++
++# Check to see that origin matches host directly, including ports
++return origin == host
++
++
+ def _reserialize_reply(self, msg_list):
+ """Reserialize a reply message using JSON.
+ 
+@@ -409,6 +438,11 @@ class ZMQStreamHandler(websocket.WebSock
+ class AuthenticatedZMQStreamHandler(ZMQStreamHandler):
+ 
+ def open(self, kernel_id):
++# Check to see that origin matches host directly, including ports
++if not self.same_origin():
++self.log.warn("Cross Origin WebSocket Attempt.")
++raise web.HTTPError(404)
++
+ self.kernel_id = kernel_id.decode('ascii')
+ try:
+ cfg = self.application.ipython_app.config
diff -Nru ipython-0.13.1/debian/patches/series ipython-0.13.1/debian/patches/series
--- ipython-0.13.1/debian/patches/series	2012-11-25 20:04:22.0 +0100
+++ ipython-0.13.1/debian/patches/series	2014-07-16 20:26:58.0 +0200
@@ -5,3 +5,4 @@
 use-system-mathjax-if-available.patch
 parallel-2to3.patch
 shared-static-path.patch
+CVE-2014-3429.patch


NEW changes in oldstable-new

2014-07-19 Thread Debian FTP Masters
Processing changes file: davfs2_1.4.6-1.1+squeeze1_amd64.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_armel.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_i386.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_ia64.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_mips.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_mipsel.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_powerpc.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_s390.changes
  REJECT
Processing changes file: davfs2_1.4.6-1.1+squeeze1_sparc.changes
  REJECT
Processing changes file: debdelta_0.39+squeeze2_i386.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_i386.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_amd64.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_armel.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_ia64.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_mips.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_mipsel.changes
  REJECT
Processing changes file: openjdk-6_6b31-1.13.3-1~deb6u1_powerpc.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_amd64.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_armel.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_i386.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_ia64.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_mips.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_mipsel.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_powerpc.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_s390.changes
  REJECT
Processing changes file: openswan_2.6.28+dfsg-5+squeeze2_sparc.changes
  REJECT


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1x8ta8-000496...@franck.debian.org



Bug#753502: RM: spip/2.1.1-3squeeze7

2014-07-19 Thread David Prévot
Hi,

On Wed, Jul 02, 2014 at 05:01:38PM +0200, Moritz Muehlenhoff wrote:
> as briefly discussed on #debian-release. Please remove this package
> in the 6.0.10 point release. It's not covered by squeeze-lts support
> and debian-security-support marks existing packages as deprecated.

Why the maintainers of spip who cares enough about the security of this
package and have submitted all the previous updates, have not even been
informed of this request?

Continuing to update spip in squeeze-lts would have been as easy as
during squeeze lifetime, so I’m really surprised (and not amused) to
find this request now that it has been handled by the release team.

Regards

David


signature.asc
Description: Digital signature


Bug#743259: squeeze-pu: package ca-certificates/20090814+squeeze1

2014-07-19 Thread Michael Shuler

On 07/19/2014 06:45 AM, Adam D. Barratt wrote:

On Thu, 2014-07-10 at 19:30 +0100, Adam D. Barratt wrote:

On Mon, 2014-03-31 at 22:10 -0500, Michael Shuler wrote:

I would like to upload ca-certificates to oldstable to bring the Mozilla
CA bundle up to date, include one important patch to fix duplicate
CKA_LABEL certificates, and one minor additional fix in order to parse the
new certdata.txt file correctly. I also updated Maintainer/Uploaders. The
oldstable debdiff is attached.


Please go ahead, bearing in mind that the window for getting the package
in to the upcoming (and final) point release for squeeze closes over the
coming weekend.


Unfortunately no upload happened and as today was the final point
release for squeeze I'm going to close this bug now. You may wish to
discuss an update in squeeze-lts with the LTS team.


Yep, the short window did not work out for me to get the upload 
completed, after finding an upgrade issue with the proposed patch, so a 
squeeze upload will take some additional work. Thanks for the 
consideration and pointer to -lts!


--
Kind regards,
Michael


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53ca8a47.3000...@pbandjelly.org



Bug#755263: wheezy-pu: package ipython/0.13.1-2+deb7u1

2014-07-19 Thread Julien Cristau
Control: tags -1 confirmed

On Sat, Jul 19, 2014 at 13:51:46 +0200, Julian Taylor wrote:

> Package: release.debian.org
> Severity: normal
> Tags: wheezy
> User: release.debian@packages.debian.org
> Usertags: pu
> 
> Hi release team
> 
> I would like to update ipython in wheezy to fix CVE-2014-3429
> It is a remote execution flaw via cross origin websockets, but one
> requires a uuid from the process in order to make use of it so it was
> decided by the security team that its severe enough for a DSA.

Missing "not"?

> But it should stil be fixed in stable just in case.
> 
> See this page for details of the issue:
> http://lambdaops.com/cross-origin-websocket-hijacking-of-ipython

With one comment below, and assuming this has been tested in a wheezy
environment, feel free to upload.

> diff -Nru ipython-0.13.1/debian/changelog ipython-0.13.1/debian/changelog
> --- ipython-0.13.1/debian/changelog   2012-11-25 20:04:22.0 +0100
> +++ ipython-0.13.1/debian/changelog   2014-07-16 20:29:04.0 +0200
> @@ -1,3 +1,9 @@
> +ipython (0.13.1-2+deb7u1) stable-security; urgency=medium

Please make that "stable" or "wheezy".

> +
> +  * Fix CVE-2014-3429: remote execution via cross origin websocket
> +
> + -- Julian Taylor   Wed, 16 Jul 2014 20:27:50 
> +0200
> +
>  ipython (0.13.1-2) unstable; urgency=low
>  
>* update watch file to use github directly

Cheers,
Julien


signature.asc
Description: Digital signature


Processed: Re: Bug#755263: wheezy-pu: package ipython/0.13.1-2+deb7u1

2014-07-19 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 confirmed
Bug #755263 [release.debian.org] wheezy-pu: package ipython/0.13.1-2+deb7u1
Added tag(s) confirmed.

-- 
755263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b755263.140578320010523.transcr...@bugs.debian.org



Bug#755263: wheezy-pu: package ipython/0.13.1-2+deb7u1

2014-07-19 Thread Julian Taylor
On 19.07.2014 17:19, Julien Cristau wrote:
> Control: tags -1 confirmed
> 
> On Sat, Jul 19, 2014 at 13:51:46 +0200, Julian Taylor wrote:...
>> I would like to update ipython in wheezy to fix CVE-2014-3429
>> It is a remote execution flaw via cross origin websockets, but one
>> requires a uuid from the process in order to make use of it so it was
>> decided by the security team that its severe enough for a DSA.
> 
> Missing "not"?

yes, its not severe enough.

> 
>> But it should stil be fixed in stable just in case.
>>
>> See this page for details of the issue:
>> http://lambdaops.com/cross-origin-websocket-hijacking-of-ipython
> 
> With one comment below, and assuming this has been tested in a wheezy
> environment, feel free to upload.

thanks fixed and uploaded with a slightly better changelog message.


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53caaf2a.10...@ubuntu.com



Re: Linux kernel ABI bump

2014-07-19 Thread Ben Hutchings
On Sat, 2014-07-19 at 11:17 +0100, Ian Campbell wrote:
> On Fri, 2014-07-18 at 17:48 +0100, Ben Hutchings wrote:
> > A kernel ABI bump is needed to enable:
> > 
> > - [powerpc] CONFIG_PPC_TRANSACTIONAL_MEM
> > - [powerpc/powerpc64] CONFIG_JUMP_LABEL
> > - CONFIG_DYNAMIC_DEBUG
> > 
> > I propose to make these changes with the next upload to unstable.
> > 
> > If anyone else has an ABI-breaking change planned, we should try to get
> > that done at the same time.
> 
> The fix for the arm64 aufs FTBFS issue looks likely to require an ABI
> bump.

Right, good timing there. :-)

Ben.

-- 
Ben Hutchings
Kids!  Bringing about Armageddon can be dangerous.  Do not attempt it in
your own home. - Terry Pratchett and Neil Gaiman, `Good Omens'


signature.asc
Description: This is a digitally signed message part


Bug#754582: Bug#646130: Bug#754582: transition: parted

2014-07-19 Thread Colin Watson
I have now NMUed guymager with the maintainer's permission, and I've
delayed-5-NMUed partitionmanager.  parted 3.1-2 is in experimental and
has built everywhere except mips (not a build failure, it's just sitting
in Needs-Build - given that it built fine on mipsel I don't anticipate a
problem there).  No other known blockers remain.

guymager will show up on the transition tracker, but can be ignored; it
doesn't require a binNMU.

May I go ahead and start the transition in unstable?  I can wait for the
partitionmanager NMU to land if you feel that's necessary, but I don't
want to wait too long as I'm going to be travelling for a good chunk of
August and would like to get this out of the way before then if
possible.

Thanks,

-- 
Colin Watson   [cjwat...@debian.org]


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140719232909.ga1...@riva.ucam.org