Processed: Re: Bug#829136: jessie-pu: package harfbuzz/0.9.35-2+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #829136 [release.debian.org] jessie-pu: package harfbuzz/0.9.35-2+deb8u1
Added tag(s) confirmed.

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

Bug#825699: jessie-pu: package glibc/2.19-18+deb8u5

[Aurelien Jarno]

On 2016-07-12 21:33, Adam D. Barratt wrote:
> On Wed, 2016-06-08 at 00:28 +0200, Aurelien Jarno wrote:
> > On 2016-05-29 17:19, Adam D. Barratt wrote:
> > > Control: tags -1 -moreinfo +confirmed
> > > 
> > > On Sun, 2016-05-29 at 17:53 +0200, Aurelien Jarno wrote:
> > > 
> > > > Can we get this into jessie-proposed-updates just after the 8.5 release,
> > > > so that it doesn't happen again for 8.6? Most of these changes were
> > > > ready in our git repository for over a month, it's just I didn't got 
> > > > time
> > > > this week to finish preparing the final upload.
> > > 
> > > That sounds like a good plan.
> > 
> > Now that the 8.5 release is out, I would like to upload glibc version
> > 2.19-18+deb8u5 to jessie-proposed-updates. You will find the diff below,
> > it only differs to the previous one by the addition of the CVE-2016-4429
> > fix.
> 
> Please go ahead; apologies for the delay.

Thanks, I have just uploaded it.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#830911: Britney git mirrors are broken by release.d.o move

[Niels Thykier]

Package: release.debian.org
Severity: important
User: release.debian@packages.debian.org
Usertags: britney

https://anonscm.debian.org/git/mirror/britney2.git (and similar) are
not being updated.  They pull from release.d.o/git/, but those links
are not functional anymore.

Bug#829136: jessie-pu: package harfbuzz/0.9.35-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2016-06-30 at 22:19 +0200, Moritz Muehlenhoff wrote:
> +harfbuzz (0.9.35-2+deb8u1) jessie; urgency=medium
> +
> +  * Backport upstream commit 613e630617074eb9b62b794cc37c9b42a7fb079b to 
> address
> +CVE-2016-2052

Please go ahead.

Regards,

Adam

Bug#829135: jessie-pu: package python2.7/2.7.9-2+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Thu, 2016-06-30 at 22:17 +0200, Moritz Muehlenhoff wrote:
> +python2.7 (2.7.9-2+deb8u1) jessie; urgency=medium
> +
> +  * Backport upstream commit b3ce713fb9beebfff9848cefa0acbd59acc68fe9
> +to address StartTLS stripping attack in smtplib (CVE-2016-0772)
> +  * Backport upstream commit 985fc64c60d6adffd1138b6cc46df388ca91ca5d
> +to address integer overflow in zipimporter (CVE-2016-5636)
> +  * Backport upstream commit 1c45047c51020d46246385949d5c02e026d47320
> +to address HTTP header injection (CVE-2016-5699)

Please go ahead.

Regards,

Adam

Processed: Re: Bug#829135: jessie-pu: package python2.7/2.7.9-2+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #829135 [release.debian.org] jessie-pu: package python2.7/2.7.9-2+deb8u1
Added tag(s) confirmed.

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

Bug#829145: marked as done (transition: glibc 2.23)

[Debian Bug Tracking System]

Your message dated Wed, 13 Jul 2016 00:51:36 +0200
with message-id <396adae9-1914-09a1-29c4-817b356e2...@debian.org>
and subject line Re: Bug#829145: transition: glibc 2.23
has caused the Debian Bug report #829145,
regarding transition: glibc 2.23
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.)


-- 
829145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829145
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: transition

Dear release team,

We would like to get a transition slot for glibc 2.23. It is currently
available in experimental and has been built successfully on all
official architectures except hurd-i386. We have fixed the hurd-i386
failure in out git, and we are working on build failures for alpha, hppa
and sparc64. There are due to testsuite issue, mostly in the math parts
and do not look very critical.

It should be noted that this upload will make a few packages to FTBFS,
mostly due to more precise checking in the floating-point classification
macros (isnan, isinf, ...). In most of the cases the changes just make
existing bugs visible. The list of affected packages is available [1]
(thanks to Martin Michlmayr), and the bugs have been opened for more
than 3 months.

As the glibc is using symbol versioning, there is no soname change. That
said a few packages are using libc internal symbols and have to be
rebuilt for this transition:
 - apitrace
 - bro
 - dante
 - libnih
 - libnss-db
 - unscd
 
Here is the corresponding ben file:
 
title = "glibc";
is_affected = .depends ~ /libc[0-9.]* \( On 04/07/16 00:48, Aurelien Jarno wrote:
>> On 2016-07-01 09:42, Emilio Pozuelo Monfort wrote:
>>> Control: tags -1 confirmed
>>>
>>> On 01/07/16 01:41, Aurelien Jarno wrote:
 Package: release.debian.org
 Severity: normal
 User: release.debian@packages.debian.org
 Usertags: transition

 Dear release team,

 We would like to get a transition slot for glibc 2.23. It is currently
 available in experimental and has been built successfully on all
 official architectures except hurd-i386. We have fixed the hurd-i386
 failure in out git, and we are working on build failures for alpha, hppa
 and sparc64. There are due to testsuite issue, mostly in the math parts
 and do not look very critical.

 It should be noted that this upload will make a few packages to FTBFS,
 mostly due to more precise checking in the floating-point classification
 macros (isnan, isinf, ...). In most of the cases the changes just make
 existing bugs visible. The list of affected packages is available [1]
 (thanks to Martin Michlmayr), and the bugs have been opened for more
 than 3 months.

 As the glibc is using symbol versioning, there is no soname change. That
 said a few packages are using libc internal symbols and have to be
 rebuilt for this transition:
  - apitrace
  - bro
  - dante
  - libnih
  - libnss-db
  - unscd
  
 Here is the corresponding ben file:
  
 title = "glibc";
 is_affected = .depends ~ /libc[0-9.]* \(<>>> is_good = .depends ~ /libc[0-9.]* \(<< 2.24\)/;
 is_bad = .depends ~ /libc[0-9.]* \(<< 2.23\)/;

 In addition to that, a few new symbols have been added that might
 prevent a few other packages to transition to testing if they pick up
 the new symbols, namely the fts64_* and the lgamma* ones. It should not
 concerns many packages.
>>>
>>> Go ahead.
>>
>> It has just been accepted by dak.
> 
> binnmus scheduled.

This just went in. Closing.

Emilio--- End Message ---

Bug#825699: jessie-pu: package glibc/2.19-18+deb8u5

[Adam D. Barratt]

On Wed, 2016-06-08 at 00:28 +0200, Aurelien Jarno wrote:
> On 2016-05-29 17:19, Adam D. Barratt wrote:
> > Control: tags -1 -moreinfo +confirmed
> > 
> > On Sun, 2016-05-29 at 17:53 +0200, Aurelien Jarno wrote:
> > 
> > > Can we get this into jessie-proposed-updates just after the 8.5 release,
> > > so that it doesn't happen again for 8.6? Most of these changes were
> > > ready in our git repository for over a month, it's just I didn't got time
> > > this week to finish preparing the final upload.
> > 
> > That sounds like a good plan.
> 
> Now that the 8.5 release is out, I would like to upload glibc version
> 2.19-18+deb8u5 to jessie-proposed-updates. You will find the diff below,
> it only differs to the previous one by the addition of the CVE-2016-4429
> fix.

Please go ahead; apologies for the delay.

Regards,

Adam

Bug#823911: jessie-pu: package debian-security-support/2016.05.09+nmu1~deb8u1

[Adam D. Barratt]

On Wed, 2016-06-29 at 16:29 +0200, Santiago Ruano Rincón wrote:
> El 27/05/16 a las 18:17, Adam D. Barratt escribió:
> > Control: tags -1 + confirmed
[...]
> > Please go ahead.
[...]
> A more recent version of debian-security-support fixes two additional
> bugs:
> 
> https://bugs.debian.org/824015
> https://bugs.debian.org/824081
> 
> This new package also updates the security support status for different
> packages, and updates several localization files. Please, find the diff
> below.

fwiw, I don't find > 1000 line inline diffs particularly pleasant to
deal with; attaching it would have been more conventional. (

> Should I go ahead with this new release?

Please feel free.

> Retitling this same bug report is enough, or a new bug is needed?

As you never actually uploaded the previous version, reusing this report
is fine. (Basically one bug per upload, with occasional exceptions for
things like FTBFS issues in uploads.)

Regards,

Adam

Processed: Re: Bug#829650: jessie-pu: package ruby-eventmachine/1.0.3-6+deb8u1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #829650 [release.debian.org] jessie-pu: package 
ruby-eventmachine/1.0.3-6+deb8u1
Added tag(s) confirmed.

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

Processed: Re: Bug#829603: jessie-pu: package conkeror/1.0~~pre-1+git141025-1+deb8u2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #829603 [release.debian.org] jessie-pu: package 
conkeror/1.0~~pre-1+git141025-1+deb8u2
Added tag(s) confirmed.

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

Bug#829603: jessie-pu: package conkeror/1.0~~pre-1+git141025-1+deb8u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-07-04 at 17:29 +0200, Axel Beckert wrote:
> With the update to Firefox 45 in Jessie, it once again caused
> regressions in depending packages due to removed features. For
> conkeror it's this time the removal of some specific syntactic sugar
> around the "let" construct.
> 
> Cherry-picking the according upstream fix solves the issue also in
> Jessie. I've prepared and tested an upload for that and would like to
> upload this to jessie-proposed-updates.

Please go ahead.

Regards,

Adam

Bug#829650: jessie-pu: package ruby-eventmachine/1.0.3-6+deb8u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2016-07-05 at 04:40 +0200, Balint Reczey wrote:
> The Security Team suggested fixing the TEMP-0678512-2E167C [1] security
> issue through a point release.
> 
> The issue is a remotely triggerable crash due to stack overflow.

Please go ahead.

Regards,

Adam

Bug#827781: jessie-pu: package lxc/1:1.0.6-6+deb8u3

[Adam D. Barratt]

On Wed, 2016-06-29 at 16:54 -0300, Antonio Terceiro wrote:
> On Tue, Jun 28, 2016 at 12:16:21PM +0200, Julien Cristau wrote:
[...]
> > Ack.  Please go ahead.
> 
> Hi, actually I was just made aware of a regression: including `init` in
> the package list breaks the creation of wheezy containers because `init`
> did not exist then. The regression was fixed in 1:2.0.1-3 just uploaded
> to unstable.
> 
> The updated diff is attached.

Please go ahead.

Regards,

Adam

Bug#830805: jessie-pu: package cacti/0.8.8b+dfsg-8+deb8u4

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2016-07-11 at 20:28 +0200, Paul Gevers wrote:
> There are currently three CVE's open against the cacti package in jessie that
> have a patch available¹. Non of the issues are severe enough to warrent a
> security upload, but I still think it is a good idea to get this fixed in
> jessie. Could you please consider the attached debdiff?

Please go ahead.

Regards,

Adam

Processed: Re: Bug#830805: jessie-pu: package cacti/0.8.8b+dfsg-8+deb8u4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #830805 [release.debian.org] jessie-pu: package cacti/0.8.8b+dfsg-8+deb8u4
Added tag(s) confirmed.

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

Bug#794194: britney: Strip off Multi-Arch qualifiers in reverse dependency calculation

[Martin Pitt]

Control: tag -1 confirmed -moreinfo

Hello Niels,

Niels Thykier [2016-01-16 14:34 +]:
> Does this issue still apply to Britney at the current master branch?  We
> have removed register_reverses in favour of a different approach for
> unrelated reasons.

Yes, it does still apply. I rebased Ubuntu's britney onto current
master, and the test_multiarch_dep() test fails. So I reopened the
bug.

Current britney uses  apt_pkg.parse_depends() which already has an
option to strip off multi-arch qualifiers. It just needs to be
enabled.

Patch attached.

Thanks,

Martin

[1] 
https://git.launchpad.net/~ubuntu-release/+git/britney2-ubuntu/tree/tests/test_autopkgtest.py#n1233


-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
From 25871d158f65be94e11d0be564f2547e03f2b113 Mon Sep 17 00:00:00 2001
From: Martin Pitt 
Date: Tue, 12 Jul 2016 09:21:15 +0200
Subject: [PATCH] Consider packages with M-A qualifiers for reverse
 dependencies

Strip of Multi-Arch qualifiers like ":any" or ":native" when building the
dependency fields, as they are not part of the package name.

This will fix cases like

  Package: ipython3
  Depends: python3:any (>= 3)

and include ipython3 in python3's reverse dependencies.

Closes: #794194
---
 britney.py | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/britney.py b/britney.py
index e62219a..02f1835 100755
--- a/britney.py
+++ b/britney.py
@@ -683,10 +683,10 @@ class Britney(object):
 
 # We do not differentiate between depends and pre-depends
 if pkgdata.depends:
-depends.extend(apt_pkg.parse_depends(pkgdata.depends, False))
+depends.extend(apt_pkg.parse_depends(pkgdata.depends, True))
 
 if pkgdata.conflicts:
-conflicts = apt_pkg.parse_depends(pkgdata.conflicts, False)
+conflicts = apt_pkg.parse_depends(pkgdata.conflicts, True)
 
 with builder.relation_builder(pkg_id) as relations:
 
@@ -806,7 +806,7 @@ class Britney(object):
 return sources
 
 def _parse_provides(self, pkg_id, provides_raw):
-parts = apt_pkg.parse_depends(provides_raw, False)
+parts = apt_pkg.parse_depends(provides_raw, True)
 nprov = []
 for or_clause in parts:
 if len(or_clause) != 1:
@@ -1149,7 +1149,7 @@ class Britney(object):
 is_all_ok = True
 
 # for every dependency block (formed as conjunction of disjunction)
-for block, block_txt in zip(parse_depends(deps, False), deps.split(',')):
+for block, block_txt in zip(parse_depends(deps, True), deps.split(',')):
 # if the block is satisfied in testing, then skip the block
 packages = get_dependency_solvers(block, package_t_a)
 if packages:
-- 
2.8.1



signature.asc
Description: PGP signature

Processed: Re: Bug#794194: britney: Strip off Multi-Arch qualifiers in reverse dependency calculation

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed -moreinfo
Bug #794194 [release.debian.org] britney: Strip off Multi-Arch qualifiers in 
reverse dependency calculation
Added tag(s) confirmed.
Bug #794194 [release.debian.org] britney: Strip off Multi-Arch qualifiers in 
reverse dependency calculation
Removed tag(s) moreinfo.

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

Bug#830846: nmu: squid3_3.4.8-6+deb8u2~bpo70+1

[Markus Koschany]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Dear release team,

the version of squid3 in wheezy-backports (amd64) is uninstallable due
to unmet dependencies. This was caused by building the binary packages
for amd64 in an unclean environment. Please schedule a rebuild for
squid3, amd64 in wheezy-backports. See #819523 for further
information.

Thank you

nmu squid3_3.4.8-6+deb8u2~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild to 
fix unmet dependencies. (Closes: #819523)"

Processed: unarchiving 794194, reopening 794194

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 794194
Bug #794194 {Done: Martin Pitt } [release.debian.org] 
britney: Strip off Multi-Arch qualifiers in reverse dependency calculation
Unarchived Bug 794194
> reopen 794194
Bug #794194 {Done: Martin Pitt } [release.debian.org] 
britney: Strip off Multi-Arch qualifiers in reverse dependency calculation
Bug reopened
Ignoring request to alter fixed versions of bug #794194 to the same values 
previously set
> thanks
Stopping processing here.

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

Re: Thinking about a "jessie and a half" release

[Nicholas D Steeves]

Hi Jeffrey,

On 12 July 2016 at 09:28, Jeffrey Walton  wrote:
>
> I think it would benefit more than Skylake users. The last few
> processors are missing support. Below is from a Core i5-5300U (5th
> gen) and a 3.19.0-64-generic kernel.
>
> **
>
> $ dmesg | egrep -i '(error|failed)'
> ...
> [35679.953137] mce: [Hardware Error]: Machine check events logged
> [35980.749723] mce: [Hardware Error]: Machine check events logged
> [36280.594838] mce: [Hardware Error]: Machine check events logged
> [36580.439940] mce: [Hardware Error]: Machine check events logged
> [37029.202190] mce: [Hardware Error]: Machine check events logged
> [37179.118743] mce: [Hardware Error]: Machine check events logged
> [37629.831878] mce: [Hardware Error]: Machine check events logged
> [37779.748453] mce: [Hardware Error]: Machine check events logged
> [38229.510127] mce: [Hardware Error]: Machine check events logged
>
> $ sudo mcelog
> mcelog: Family 6 Model 3d CPU: only decoding architectural errors
>

Out of curiosity, what does the mcelog version in jessie-backports
output when running this kernel version?

Cheers,
Nicholas

Bug#830846: marked as done (nmu: squid3_3.4.8-6+deb8u2~bpo70+1)

[Debian Bug Tracking System]

Your message dated Tue, 12 Jul 2016 15:01:31 +0200
with message-id <07fdb7f0-33df-7ab6-5ba1-ed35d6c77...@debian.org>
and subject line Re: Bug#830846: nmu: squid3_3.4.8-6+deb8u2~bpo70+1
has caused the Debian Bug report #830846,
regarding nmu: squid3_3.4.8-6+deb8u2~bpo70+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.)


-- 
830846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830846
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: binnmu

Dear release team,

the version of squid3 in wheezy-backports (amd64) is uninstallable due
to unmet dependencies. This was caused by building the binary packages
for amd64 in an unclean environment. Please schedule a rebuild for
squid3, amd64 in wheezy-backports. See #819523 for further
information.

Thank you

nmu squid3_3.4.8-6+deb8u2~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild to 
fix unmet dependencies. (Closes: #819523)"
--- End Message ---
--- Begin Message ---
On 12/07/16 10:28, Markus Koschany wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
> 
> Dear release team,
> 
> the version of squid3 in wheezy-backports (amd64) is uninstallable due
> to unmet dependencies. This was caused by building the binary packages
> for amd64 in an unclean environment. Please schedule a rebuild for
> squid3, amd64 in wheezy-backports. See #819523 for further
> information.
> 
> Thank you
> 
> nmu squid3_3.4.8-6+deb8u2~bpo70+1 . amd64 . wheezy-backports . -m "Rebuild to 
> fix unmet dependencies. (Closes: #819523)"

AFAIK backport nmus should go to the backports team.

In any case, this already got scheduled.

Cheers,
Emilio--- End Message ---

Bug#830871: release.debian.org: missing hints file 'freeze'

[Lucas Nussbaum]

Package: release.debian.org
Severity: normal

Hi,

On https://release.debian.org/britney/hints/ there's a link to a
'freeze' file, but that link doesn't work (404 error).

This breaks UDD's hints importer.

Full IRC log from #debian-release:
13:31 < lucas> hi
13:31 < lucas> on https://release.debian.org/britney/hints/ there's a link to a 
"freeze" file
13:31 < lucas> that is missing
13:31 < lucas> could you create an empty file? alternatively, I could make UDD 
ignore the failure, or ignore that file, but both seem error-prone for the 
future
13:34 < pochu> that's a symlink, which explains the 404
14:12 < jcristau> what does udd use that for?
14:14 < lucas> jcristau: UDD fetches release team hints. they are displayed, 
for example, in 
https://udd.debian.org/bugs/?release=stretch_not_sid=ign=7=1=id=asc=1=1=1=1#results
14:16 < jcristau> would excuses.yaml be enough for that?
14:18 < lucas> I don't think so. the goal was to detect missing hints, for 
example. also, it worked until recently (and still works for other hints), so 
I'd prefer to restore the old behaviour
14:19 < adsb> it worked until release became a separate machine from ftp-master 
and as a side-effect now has the web content served from static.d.o rather than 
directly from the release host. so symlinks to stuff outside of www/ don't work

- Lucas

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-updates'), (400, 'stable'), (300, 
'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#830846: nmu: squid3_3.4.8-6+deb8u2~bpo70+1

[Markus Koschany]

On 12.07.2016 15:01, Emilio Pozuelo Monfort wrote:
[...]
> AFAIK backport nmus should go to the backports team.
> 
> In any case, this already got scheduled.
> 
> Cheers,
> Emilio

Hi,

thank you for working on this issue. The reportbug template for
release.debian.org and binNMUs lists wheezy-backports as a valid suite.
Shall I file a bug report against reportbug to change that?

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Re: Thinking about a "jessie and a half" release

[Jeffrey Walton]

> There's something I've been pondering for a while, along with some
> other folks - it might be useful to do a "jessie and a half" release,
> similarly to what we did in the etch days. That's *basically* just
> like a normal jessie release, but with a few key updates:
>
>  * backports kernel
>  * rebuilt d-i to match that kernel
>  * X drivers
>  * ... (other things that might be needed for consistency)
>
> all rolled up with a small installer image build (netinst, maybe DVD#1).
>
> A lot of arm64 machine users would benefit from this, and maybe owners
> of very recent amd64 machines too, with better support for things on
> the Skylake platform. Those are the only two architectures I'm
> thinking of supporting at this point.
>
> Is anybody else interested in helping? Thoughts/comments?

I think it would benefit more than Skylake users. The last few
processors are missing support. Below is from a Core i5-5300U (5th
gen) and a 3.19.0-64-generic kernel.

**

$ dmesg | egrep -i '(error|failed)'
...
[35679.953137] mce: [Hardware Error]: Machine check events logged
[35980.749723] mce: [Hardware Error]: Machine check events logged
[36280.594838] mce: [Hardware Error]: Machine check events logged
[36580.439940] mce: [Hardware Error]: Machine check events logged
[37029.202190] mce: [Hardware Error]: Machine check events logged
[37179.118743] mce: [Hardware Error]: Machine check events logged
[37629.831878] mce: [Hardware Error]: Machine check events logged
[37779.748453] mce: [Hardware Error]: Machine check events logged
[38229.510127] mce: [Hardware Error]: Machine check events logged

$ sudo mcelog
mcelog: Family 6 Model 3d CPU: only decoding architectural errors

Bug#794194: britney: Strip off Multi-Arch qualifiers in reverse dependency calculation

[Niels Thykier]

Control: tags -1 moreinfo

Martin Pitt:
> Control: tag -1 confirmed -moreinfo
> 
> Hello Niels,
> 
> Niels Thykier [2016-01-16 14:34 +]:
>> Does this issue still apply to Britney at the current master branch?  We
>> have removed register_reverses in favour of a different approach for
>> unrelated reasons.
> 
> Yes, it does still apply. I rebased Ubuntu's britney onto current
> master, and the test_multiarch_dep() test fails. So I reopened the
> bug.
> 

Ok thanks. :)

> Current britney uses  apt_pkg.parse_depends() which already has an
> option to strip off multi-arch qualifiers. It just needs to be
> enabled.
> 
> Patch attached.
> 
> Thanks,
> 
> Martin
> 
> [1] 
> https://git.launchpad.net/~ubuntu-release/+git/britney2-ubuntu/tree/tests/test_autopkgtest.py#n1233
> 
> 

We need to handle the multi-arch dependencies explicitly as "pkg:amd64"
is *not* acceptable for an i386 packages (etc.).  Unfortunately, the
proposed patch causes exactly that behaviour[1]. :-/

[1] We have a very crude test for this in
https://anonscm.debian.org/cgit/collab-maint/britney2-tests.git/tree/t/multi-arch-depends/

It probably only covers the most straight forward case.

Processed: Re: Bug#794194: britney: Strip off Multi-Arch qualifiers in reverse dependency calculation

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #794194 [release.debian.org] britney: Strip off Multi-Arch qualifiers in 
reverse dependency calculation
Added tag(s) moreinfo.

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

Bug#830900: RM: trn/3.6-24

[Matthew Vernon]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

Hi,

I write as the trn maintainer.

trn has been removed from unstable and testing, because it is insecure
(see #830294 for the insecurity, #830296 for the removal from
unstable/testing).

I think it should also be removed from stable - people can (and
should) use trn4 instead, and in any case trn shouldn't be used with
untrusted input (e.g. usenet).

Thanks,

Matthew

-- System Information:
Debian Release: 7.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

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