date:20140928

* Andreas Cadhalpun (andreas.cadhal...@googlemail.com) [140928 11:27]:
 On 28.09.2014 10:24, Moritz Muehlenhoff wrote:
 Package: ffmpeg
 Severity: serious

 As written before we can have only libav or ffmpeg in jessie.
 I'm filing this blocker bug to prevent testing migration until
 this is sorted out.

 As I have explained [1], I see no security problem with having FFmpeg  
 and Libav in Jessie, in particular because this is already the case for  
 Wheezy, as chromium embeds a copy of FFmpeg.

First of all, I think it is very good news that we now have FFmpeg
available in Debian. Thank you for your work on it, it's appreciated.

However, the open question is (especially with the upcoming release),
do we want to have it in jessie? (That we probably want FFmpeg in
testing in the long run is something else, but the current discussion
is especially about jessie.)

I also think it's good that you actively raised this discussion, even
if it is perhaps not working as you would have like it. Please
continue this good style.


Another remark, we are already quite late in the cycle. At this point
it is too late to have greater changes to jessie. So even if jessie is
not officially frozen, larger changes are not possible anymore
(without disturbing the time plan).


 So would you please explain why you see a problem?

I hope we end this discussion on an agreement about the jessie plans.

However, to avoid misunderstandings at a later moment, I need to point
out that the final decision of what is part of jessie is taken by the
release team (or ultimatly the release managers). All of RC-bugs,
testing migration scripts etc are very valuable helpers because it
wouldn't be possible to manage it otherwise, but in the end they are
helpers.

The release policy does say Packages must be security-supportable. I
would be surprised if a statement from the security team (assuming
that Moritz raised that bug report with his security team-hat on and
not privately) that they would like to have only one of libav and
ffmpeg in jessie would be overruled by the release team.

Now seeing the statements from the libav maintainers (which of course,
as this is an overlaping jurisdiction, could be escalated to the tech
ctte), that we already have transition freeze and the time planings
for jessie, makes it quite unlikely (or rather: impossible) to switch
from libav to FFmpeg in time for jessie. (Of course, for jessie+1
there is enough time for the transition. And for jessie+1 we will have
enough experience with FFmpeg in Debian to perhaps see things in a
different light.)


So from my experience I assume the final answer would look similar to
It's too late for jessie, sorry. Which might be a pity but, well,
that's how it is.




Andi


-- 
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/20140928104705.gn20...@mails.so.argh.org

Bug#760343: transition: protobuf 2.6.0

2014-09-28 Thread Jonathan Wiltshire


On 2014-09-27 18:49, Robert Edmonds wrote:

Robert Edmonds wrote:

Robert Edmonds wrote:
 node-mapnik
 ---

 This package Build-Depends against mapnik-vector-tile, which ships a
 .pb.h file in /usr/include (a bad upstream practice).
 mapnik-vector-tile needs to be binNMU'd first before node-mapnik can
 be binNMU'd.

It turns out node-mapnik FTBFS (#759843) due to a problem with
mapnik-vector-tile (#762643) unrelated to the protobuf transition.  
I've

uploaded a fix for this to DELAYED, so once mapnik-vector-tile
0.5.1+dfsg-1.3 is in the archive, node-mapnik can be binNMU'd.  (And I
think that will complete the transition?)


Hi,

mapnik-vector-tile 0.5.1+dfsg-1.3 is in unstable and I've confirmed 
that

it fixes #759843, so node-mapnik can be binNMU'd now.


Thanks, scheduled. I also fixed up the found/fixed versions for #759843, 
or various tools will believe it still affects node-mapnik in sid and 
jessie.


--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

directhex i have six years of solaris sysadmin experience, from
8-10. i am well qualified to say it is made from bonghits
layered on top of bonghits


--
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/0c243990e86b53e75425d6e1ce63c...@hogwarts.powdarrmonkey.net

Bug#763058: nmu: doxygen_1.8.7-3

2014-09-28 Thread Sylvestre Ledru

On 27/09/2014 18:54, Andreas Barth wrote:
 * Sylvestre Ledru (sylves...@debian.org) [140927 16:51]:
 nmu doxygen_1.8.7-3 . ALL . -m binMNU because of the libclang change of 
 soname

 I updated the soname as part of the coordination to switch to llvm 3.5.
 https://release.debian.org/transitions/html/llvm-defaults-3.html
 Did you also switch the binary package name? For any soname change you
 need to have the package name to follow.

 See e.g. https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
 | Every time the shared library ABI changes in a way that may break
 | binaries linked against older versions of the shared library, the
 | SONAME of the library and the corresponding name for the binary
 | package containing the runtime shared library should change.

 Can you please do that so that we could schedule the binNMUs after
 this is done?

The package name is libclang1-3.5
and the soname is libclang-3.5.so.1

Initially, I uploaded with libclang-3.5.so as soname since the ABI remains
the same over a version of libclang but dpkg-shlibdeps complained about
the missing .1 even
if it seems valid in the policy
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
The soname may instead be of the form name-major-version.so, such as
libdb-5.1.so, in which case the name would be libdb and the version
would be 5.1. 

What would you want in term of package naming ? I don't know what would
work best here
libclang-3.5.1 is kind of a bad name.

If possible, I would prefer to keep the following naming and fix the
doxygen breakage by the
binNMU.

Sylvestre

Re: Bug#763148: Prevent migration to jessie

* Andreas Cadhalpun (andreas.cadhal...@googlemail.com) [140928 14:36]:
 On 28.09.2014 12:47, Andreas Barth wrote:

 The release policy does say Packages must be security-supportable. I
 would be surprised if a statement from the security team (assuming
 that Moritz raised that bug report with his security team-hat on and
 not privately) that they would like to have only one of libav and
 ffmpeg in jessie would be overruled by the release team.

 Nonetheless both are in wheezy and will be in jessie, unless chromium  
 gets removed from testing.

There is a distinction between an old and a new package.

However (and please note that I'm not a member of the security team
and just speak for myself here as always when not otherwise marked) if
it would be possible to replace the internal code copy in chromium
by a reference to ffmpeg (but it's not possible with libav), that will
probably lead to a re-evalutation. (That doesn't necessarily mean
sucess guranteed, but it looks to me as it will not make things
worse.)

Perhaps you always intended that, but at least I didn't understand it
that way yet.


 I absolutely cannot understand why the security team would prefer to  
 have an embedded code copy instead of a properly packaged library.

I don't think they do that. However, I can understand why one embedded
code copy is better than one embedded code copy plus a library in
addition to it.




Andi


-- 
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/20140928124440.gt3...@mails.so.argh.org

Bug#763058: nmu: doxygen_1.8.7-3

* Sylvestre Ledru (sylves...@debian.org) [140928 14:15]:
On 27/09/2014 18:54, Andreas Barth wrote:

 See e.g. [3]https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
 | Every time the shared library ABI changes in a way that may break
 | binaries linked against older versions of the shared library, the
 | SONAME of the library and the corresponding name for the binary
 | package containing the runtime shared library should change.
 
 Can you please do that so that we could schedule the binNMUs after
 this is done?


The package name is libclang1-3.5
and the soname is libclang-3.5.so.1
Initially, I uploaded with libclang-3.5.so as soname since the ABI
remains
the same over a version of libclang but dpkg-shlibdeps complained about
the missing .1 even
if it seems valid in the policy
[4]https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
The soname may instead be of the form name-major-version.so, such as
libdb-5.1.so, in which case the name would be libdb and the version
would be 5.1. 
What would you want in term of package naming ? I don't know what would
work best here
libclang-3.5.1 is kind of a bad name.

Basically there is no really nice solution there because the
packagename libclang1-3.5 was already used for the soname libclang.so.1.

The two major options are:

1. Change back the soname (which is of course wrong otherwise)
2. Change the package name to something like libclang1-3.5a.

I also have an idea for an ugly hack but I need to think a bit more
about it. From package POV it might be the niciest, but I'm not sure
if it works (which is a precondition for everything). I'll update this
mail tonight.


Andi


-- 
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/20140928123259.gs3...@mails.so.argh.org

Bug#745541: Any news?

2014-09-28 Thread Guido Günther

On Wed, Sep 24, 2014 at 11:29:10AM +0100, Adam D. Barratt wrote:
 [Context considered helpful...]
 
 On 2014-09-24 10:30, martin f krafft wrote:
 Any news on this bug?
 
 The package in unstable still hasn't been fixed and the maintainer never
 replied to my mail about that.

This is fixed in unstable with the last virt-manager upload 1.0.1-2
(which now contains virtisnt). Sorry for not getting around to it
earlier.
Cheers,
 -- Guido


-- 
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/20140928122403.ga12...@bogon.m.sigxcpu.org

Re: Bug#763148: Prevent migration to jessie

2014-09-28 Thread Andreas Cadhalpun

Hi,

On 28.09.2014 12:47, Andreas Barth wrote:

* Andreas Cadhalpun (andreas.cadhal...@googlemail.com) [140928 11:27]:

On 28.09.2014 10:24, Moritz Muehlenhoff wrote:

Package: ffmpeg
Severity: serious

As written before we can have only libav or ffmpeg in jessie.
I'm filing this blocker bug to prevent testing migration until
this is sorted out.

As I have explained [1], I see no security problem with having FFmpeg
and Libav in Jessie, in particular because this is already the case for
Wheezy, as chromium embeds a copy of FFmpeg.

First of all, I think it is very good news that we now have FFmpeg
available in Debian. Thank you for your work on it, it's appreciated.

Thank you for your kind words.

However, the open question is (especially with the upcoming release),
do we want to have it in jessie? (That we probably want FFmpeg in
testing in the long run is something else, but the current discussion
is especially about jessie.)

Yes, this is the open question. As you know, I would like to see FFmpeg
in jessie. Many users want this as well [1]. It would also be good for
XBMC and it would make it possible to have MPlayer in jessie.

I also think it's good that you actively raised this discussion, even
if it is perhaps not working as you would have like it. Please
continue this good style.

It would indeed be nice if others would also follow this good style and
participate constructively in the discussion instead of just blocking
FFmpeg.

Another remark, we are already quite late in the cycle. At this point
it is too late to have greater changes to jessie. So even if jessie is
not officially frozen, larger changes are not possible anymore
(without disturbing the time plan).

This is nothing new for me, but letting FFmpeg migrate to jessie is no
large change. It does not involve a transition of any kind.

So would you please explain why you see a problem?

I hope we end this discussion on an agreement about the jessie plans.

That was my hope, when I started this discussion.

However, to avoid misunderstandings at a later moment, I need to point
out that the final decision of what is part of jessie is taken by the
release team (or ultimatly the release managers). All of RC-bugs,
testing migration scripts etc are very valuable helpers because it
wouldn't be possible to manage it otherwise, but in the end they are
helpers.

This is the reason why I contacted the release team.

The release policy does say Packages must be security-supportable. I
would be surprised if a statement from the security team (assuming
that Moritz raised that bug report with his security team-hat on and
not privately) that they would like to have only one of libav and
ffmpeg in jessie would be overruled by the release team.

Nonetheless both are in wheezy and will be in jessie, unless chromium
gets removed from testing.

Debian policy § 4.13 [2] contains:
Debian packages should not make use of these convenience copies unless
the included package is explicitly intended to be used in this way.
If the included code is already in the Debian archive in the form of a
library, the Debian packaging should ensure that binary packages
reference the libraries already in Debian and the convenience copy is
not used. If the included code is not already in Debian, it should be
packaged separately as a prerequisite if possible.

FFmpeg is not intended to be used as embedded code copy, yet chromium
uses it that way. It should instead use the system libraries, which are
now available.
I absolutely cannot understand why the security team would prefer to
have an embedded code copy instead of a properly packaged library.

Now seeing the statements from the libav maintainers (which of course,
as this is an overlaping jurisdiction, could be escalated to the tech
ctte), that we already have transition freeze and the time planings
for jessie, makes it quite unlikely (or rather: impossible) to switch
from libav to FFmpeg in time for jessie. (Of course, for jessie+1
there is enough time for the transition. And for jessie+1 we will have
enough experience with FFmpeg in Debian to perhaps see things in a
different light.)

As I have made clear from the beginning [3], I see no need for a
transition as long as Libav is maintained.
The purpose of having FFmpeg is that users can use the binary tools and
that developers can use the libraries, if they want to.

So from my experience I assume the final answer would look similar to
It's too late for jessie, sorry. Which might be a pity but, well,
that's how it is.

It is too late for a transition, but it is not too late for letting
FFmpeg migrate into testing.

Best regards,
Andreas

1:
https://qa.debian.org/popcon-graph.php?packages=libavutil-ffmpeg54show_installed=onwant_legend=onwant_ticks=onfrom_date=to_date=hlght_date=date_fmt=%25m-%25dbeenhere=1

2: https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
3:

Bug#745541: Any news?

2014-09-28 Thread martin f krafft

also sprach Guido Günther a...@sigxcpu.org [2014-09-28 14:24 +0200]:
 This is fixed in unstable with the last virt-manager upload 1.0.1-2
 (which now contains virtisnt). Sorry for not getting around to it
 earlier.

So this should also fix #745537 in combination with libvirt from
backports, eh?

Thank you!

-- 
 .''`.   martin f. krafft madduck@d.o @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
there's an old proverb that says just about whatever you want it to.


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#763182: nmu: libdevel-cover-perl_1.17-1

2014-09-28 Thread Niko Tyni

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

A newer upstream version of libdevel-cover-perl was recently uploaded
(after perl 5.20.1-1 had migrated to testing), but unfortunately quite
a few buildds hadn't been updated from 5.20.0 yet so those binaries are
now uninstallable.

nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64 kfreebsd-i386 
powerpc s390x . --extra-depends 'perl-base (= 5.20.1)' -m rebuild for Perl 
5.20.1

amd64, mips, mipsel, ppc64el, and arm64 seem to be OK.

To prevent this occurring again on the next upload, should I mail the
relevant a...@buildd.debian.org addresses to get the chroots updated
or do you have a process for that?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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


-- 
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/20140928133131.6170.45929.reportbug@estella.local.invalid

Bug#763188: pu: package iso-scan/1.43+deb7u2

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

Hi,

I'd like to get the following one-liner into wheezy. It's been reported
a very long while ago, and the patch has waited way too long already
before getting applied. (Low on manpower, etc., you know the drill.)

| iso-scan (1.43+deb7u2) wheezy; urgency=low
| 
|   * Do not error out when searching in folders with shell-special
| characters in their name (Closes: #640789). Thanks, Modestas Vainius!
|   * It should be noted that ISO files located in paths containing special
| characters might still lead to some problems (See: #759174). Thanks,
| Stephen Kitt, for the analysis!
| 
|  -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:12:51 +0200

OK to upload?

Mraw,
KiBi.
diff -Nru iso-scan-1.43+deb7u1/debian/changelog iso-scan-1.43+deb7u2/debian/changelog
--- iso-scan-1.43+deb7u1/debian/changelog	2013-10-08 01:30:40.0 +0200
+++ iso-scan-1.43+deb7u2/debian/changelog	2014-09-28 17:12:54.0 +0200
@@ -1,3 +1,13 @@
+iso-scan (1.43+deb7u2) wheezy; urgency=low
+
+  * Do not error out when searching in folders with shell-special
+characters in their name (Closes: #640789). Thanks, Modestas Vainius!
+  * It should be noted that ISO files located in paths containing special
+characters might still lead to some problems (See: #759174). Thanks,
+Stephen Kitt, for the analysis!
+
+ -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:12:51 +0200
+
 iso-scan (1.43+deb7u1) wheezy; urgency=low
 
   [ Joey Hess ]
diff -Nru iso-scan-1.43+deb7u1/debian/iso-scan.postinst iso-scan-1.43+deb7u2/debian/iso-scan.postinst
--- iso-scan-1.43+deb7u1/debian/iso-scan.postinst	2013-10-08 01:28:02.0 +0200
+++ iso-scan-1.43+deb7u2/debian/iso-scan.postinst	2014-09-28 17:12:40.0 +0200
@@ -162,7 +162,7 @@
 			elif [ $look_subdirs = 1 ]; then
 opt=-type f
 			fi
-			isolist=$(find $dir $opt -name *.iso -o -name *.ISO 2/dev/null)
+			isolist=$(find $dir $opt -name *.iso -o -name *.ISO 2/dev/null)
 			TOPLEVEL_DIRS_COUNT=$(($TOPLEVEL_DIRS_COUNT + 1))
 
 			for iso in $isolist; do

Bug#763189: pu: package netcfg/1.108+deb7u2

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

Hi,

please review the following one-liner against netcfg. That's another
long standing bug and it's easy to fix. :)

| netcfg (1.108+deb7u2) wheezy; urgency=low
| 
|   * Fix support for entering an ESSID manually, it was previously
| getting ignored (Closes: #757478). Thanks to James Cowgill for the
| report and the patch!
| 
|  -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:11:31 +0200

OK to upload?

Mraw,
KiBi.
diff -Nru netcfg-1.108+deb7u1/debian/changelog netcfg-1.108+deb7u2/debian/changelog
--- netcfg-1.108+deb7u1/debian/changelog	2013-10-08 01:04:57.0 +0200
+++ netcfg-1.108+deb7u2/debian/changelog	2014-09-28 17:11:32.0 +0200
@@ -1,3 +1,11 @@
+netcfg (1.108+deb7u2) wheezy; urgency=low
+
+  * Fix support for entering an ESSID manually, it was previously
+getting ignored (Closes: #757478). Thanks to James Cowgill for the
+report and the patch!
+
+ -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:11:31 +0200
+
 netcfg (1.108+deb7u1) wheezy; urgency=low
 
   [ Philipp Kern ]
diff -Nru netcfg-1.108+deb7u1/wireless.c netcfg-1.108+deb7u2/wireless.c
--- netcfg-1.108+deb7u1/wireless.c	2012-09-22 19:38:28.0 +0200
+++ netcfg-1.108+deb7u2/wireless.c	2014-09-28 17:11:21.0 +0200
@@ -86,7 +86,7 @@
 goto get_essid;
 }
 
-strdup(client-value);
+interface-essid = strdup(client-value);
 
 memset(wconf.essid, 0, IW_ESSID_MAX_SIZE + 1);
 snprintf(wconf.essid, IW_ESSID_MAX_SIZE + 1, %s, interface-essid);

Re: FFmpeg in Jessie

2014-09-28 Thread Alessio Treglia

On Sun, Sep 28, 2014 at 9:27 AM, Moritz Mühlenhoff j...@inutil.org wrote:
 I've filed a blocker bug to prevent testing migration of ffmpeg.

Great, thanks!

 We can sort this out at the beginning of the jessie+1 development
 cycle.

Sure I know we'll do it.
Cheers!

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer|  quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A


--
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/CAMHuwozZ+saR91cyt7VVK_fXkCO+NaFrwBvOBCW+�26ea...@mail.gmail.com

Bug#745541: Any news?

Control: tags -1 + confirmed

On Sun, 2014-09-28 at 14:24 +0200, Guido Günther wrote:
 On Wed, Sep 24, 2014 at 11:29:10AM +0100, Adam D. Barratt wrote:
  [Context considered helpful...]
  
  On 2014-09-24 10:30, martin f krafft wrote:
  Any news on this bug?
  
  The package in unstable still hasn't been fixed and the maintainer never
  replied to my mail about that.
 
 This is fixed in unstable with the last virt-manager upload 1.0.1-2
 (which now contains virtisnt). Sorry for not getting around to it
 earlier.

Thanks. Please feel free to go ahead with the upload to p-u.

Regards,

Adam


-- 
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/1411924454.25283.6.ca...@jacala.jungle.funky-badger.org

Bug#762144: pu: package perl/5.14.2-21+deb7u1

Control: tags -1 + confirmed

On Sat, 2014-09-27 at 23:54 +0100, Dominic Hargreaves wrote:
 On Sat, Sep 27, 2014 at 07:57:39PM +0100, Adam D. Barratt wrote:
  On Thu, 2014-09-18 at 23:00 +0100, Dominic Hargreaves wrote:
   As announced in
   http://www.nntp.perl.org/group/perl.perl5.porters/2014/09/msg220118.html
   there is a probably-hard-to-exploit bug in the Data::Dumper module in
   perl. Updates are being prepared at
   
   https://anonscm.debian.org/cgit/perl/perl.git/log/?h=wheezy-data-dumper-fix
   
   The security team have called this one a no-dsa issue. Please let us know
   if it's okay to upload the fix to stable.
  
  From the current state of the above, it looks like it should be fine.
  Please could we have a debdiff of the proposed upload attached to this
  bug for a final confirmation? (For one thing it keeps the bug
  self-contained; there's also no guarantee that the branch will still
  exist in its current state for anyone looking in the future.)
 
 Sure, here goes.

Thanks. Please go ahead.

Regards,

Adam


-- 
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/1411924604.25283.7.ca...@jacala.jungle.funky-badger.org

Bug#763189: pu: package netcfg/1.108+deb7u2

Control: tags -1 + confirmed wheezy

On Sun, 2014-09-28 at 17:23 +0200, Cyril Brulebois wrote:
 please review the following one-liner against netcfg. That's another
 long standing bug and it's easy to fix. :)
 
 | netcfg (1.108+deb7u2) wheezy; urgency=low
 | 
 |   * Fix support for entering an ESSID manually, it was previously
 | getting ignored (Closes: #757478). Thanks to James Cowgill for the
 | report and the patch!
 | 
 |  -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:11:31 +0200
 
 OK to upload?

Please go ahead; thanks.

Regards,

Adam


-- 
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/1411924749.25283.9.ca...@jacala.jungle.funky-badger.org

Bug#763188: pu: package iso-scan/1.43+deb7u2

Control: tags -1 + confirmed wheezy

On Sun, 2014-09-28 at 17:21 +0200, Cyril Brulebois wrote:
 I'd like to get the following one-liner into wheezy. It's been reported
 a very long while ago, and the patch has waited way too long already
 before getting applied. (Low on manpower, etc., you know the drill.)
 
 | iso-scan (1.43+deb7u2) wheezy; urgency=low
 | 
 |   * Do not error out when searching in folders with shell-special
 | characters in their name (Closes: #640789). Thanks, Modestas Vainius!
 |   * It should be noted that ISO files located in paths containing special
 | characters might still lead to some problems (See: #759174). Thanks,
 | Stephen Kitt, for the analysis!
 | 
 |  -- Cyril Brulebois k...@debian.org  Sun, 28 Sep 2014 17:12:51 +0200
 
 OK to upload?

Please go ahead; thanks.

Regards,

Adam


-- 
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/1411924720.25283.8.ca...@jacala.jungle.funky-badger.org

Processed: Re: Bug#745541: Any news?

Processing control commands:

 tags -1 + confirmed
Bug #745541 [release.debian.org] wheezy-pu: package virtinst/0.600.1-3+deb7u2
Added tag(s) confirmed.

-- 
745541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745541
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.b745541.141192446323074.transcr...@bugs.debian.org

Processed: Re: Bug#762144: pu: package perl/5.14.2-21+deb7u1

Processing control commands:

 tags -1 + confirmed
Bug #762144 [release.debian.org] pu: package perl/5.14.2-21+deb7u1
Added tag(s) confirmed.

-- 
762144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762144
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.b762144.141192461324450.transcr...@bugs.debian.org

Processed: Re: Bug#763189: pu: package netcfg/1.108+deb7u2

Processing control commands:

 tags -1 + confirmed wheezy
Bug #763189 [release.debian.org] pu: package netcfg/1.108+deb7u2
Added tag(s) wheezy and confirmed.

-- 
763189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763189
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.b763189.141192475725073.transcr...@bugs.debian.org

Processed: Re: Bug#763188: pu: package iso-scan/1.43+deb7u2

Processing control commands:

 tags -1 + confirmed wheezy
Bug #763188 [release.debian.org] pu: package iso-scan/1.43+deb7u2
Added tag(s) wheezy and confirmed.

-- 
763188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763188
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.b763188.141192472724982.transcr...@bugs.debian.org

Re: Uploading linux (3.2.63-1)

On Wed, 2014-09-24 at 03:54 +0100, Ben Hutchings wrote:
 I intend to upload linux version 3.2.63-1 to stable-proposed-updates
 later this week.  This will include all the fixes that went into stable
 updates 3.2.61-63 inclusive, including fixes for these security issues:
[...]

Flagged for acceptance in to p-u; thanks.

Regards,

Adam


-- 
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/1411926130.25283.10.ca...@jacala.jungle.funky-badger.org

Bug#735020: pu: package nana/2.5-12+deb7u1

Control: tags -1 + pending

On Sat, 2014-09-06 at 16:25 +0100, Jonathan Wiltshire wrote:
 Doesn't sound like nana can get much worse. Please check the build as 
 best you can, and upload.

That happened, and I've just flagged the package for acceptance.

Regards,

Adam


-- 
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/1411926177.25283.11.ca...@jacala.jungle.funky-badger.org

Processed: Re: Bug#735020: pu: package nana/2.5-12+deb7u1

Processing control commands:

 tags -1 + pending
Bug #735020 [release.debian.org] pu: package nana/2.5-12+deb7u1
Added tag(s) pending.

-- 
735020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735020
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.b735020.14119261851490.transcr...@bugs.debian.org

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_multi.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_amd64.changes
  ACCEPT


-- 
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/e1xyiyx-sw...@franck.debian.org

Bug#763182: marked as done (nmu: libdevel-cover-perl_1.17-1)

Your message dated Sun, 28 Sep 2014 19:21:03 +0100
with message-id 620b0101620737d5ae2097263cc42...@hogwarts.powdarrmonkey.net
and subject line Re: Bug#763182: nmu: libdevel-cover-perl_1.17-1
has caused the Debian Bug report #763182,
regarding nmu: libdevel-cover-perl_1.17-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.)


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

A newer upstream version of libdevel-cover-perl was recently uploaded
(after perl 5.20.1-1 had migrated to testing), but unfortunately quite
a few buildds hadn't been updated from 5.20.0 yet so those binaries are
now uninstallable.

nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64 kfreebsd-i386 
powerpc s390x . --extra-depends 'perl-base (= 5.20.1)' -m rebuild for Perl 
5.20.1

amd64, mips, mipsel, ppc64el, and arm64 seem to be OK.

To prevent this occurring again on the next upload, should I mail the
relevant a...@buildd.debian.org addresses to get the chroots updated
or do you have a process for that?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---

On 2014-09-28 14:31, Niko Tyni wrote:

A newer upstream version of libdevel-cover-perl was recently uploaded
(after perl 5.20.1-1 had migrated to testing), but unfortunately quite
a few buildds hadn't been updated from 5.20.0 yet so those binaries are
now uninstallable.

nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64
kfreebsd-i386 powerpc s390x . --extra-depends 'perl-base (= 5.20.1)'
-m rebuild for Perl 5.20.1

amd64, mips, mipsel, ppc64el, and arm64 seem to be OK.


Scheduled.


To prevent this occurring again on the next upload, should I mail the
relevant a...@buildd.debian.org addresses to get the chroots updated
or do you have a process for that?


I don't believe we do, so please mail the arch address. That's unless
someone has a s3kr1t process I'm not aware of :)

Thanks,

--
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

directhex i have six years of solaris sysadmin experience, from
8-10. i am well qualified to say it is made from bonghits
layered on top of bonghits---End Message---

Bug#763182: nmu: libdevel-cover-perl_1.17-1

2014-09-28 Thread Niko Tyni

On Sun, Sep 28, 2014 at 07:21:03PM +0100, Jonathan Wiltshire wrote:
 On 2014-09-28 14:31, Niko Tyni wrote:

 nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64
 kfreebsd-i386 powerpc s390x . --extra-depends 'perl-base (= 5.20.1)'
 -m rebuild for Perl 5.20.1

 Scheduled.

Thanks!

 To prevent this occurring again on the next upload, should I mail the
 relevant a...@buildd.debian.org addresses to get the chroots updated
 or do you have a process for that?
 
 I don't believe we do, so please mail the arch address. That's unless
 someone has a s3kr1t process I'm not aware of :)

Email sent.

Thanks for your work,
-- 
Niko Tyni   nt...@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/20140928185308.GB1302@estella.local.invalid

Bug#763058: nmu: doxygen_1.8.7-3

* Andreas Barth (a...@ayous.org) [140928 14:32]:
 I also have an idea for an ugly hack but I need to think a bit more
 about it. From package POV it might be the niciest, but I'm not sure
 if it works (which is a precondition for everything). I'll update this
 mail tonight.

What works in practice, and seems to be ok-ish from a theoretical POV
is to create a symlink from libclang-3.5.so.1 to
/usr/lib/`dpkg-architecture -qDEB_BUILD_MULTIARCH`/libclang.so.1
during build time (as part of the deb file). This allows doxygen to
work again.

(Also, all previous packages were broken according to policy because
that symlink was created only at configure time by ldconfig.  However
the symlink needs to be part of the package so that the lib is
available before configure. Just a notice, there doesn't seem to be a
fallout from that, but should be kept in mind for future packages.)


Andi


-- 
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/20140928192507.ga...@mails.so.argh.org

Bug#760050: transition: llvm-toolchain-3.5

Sylvestre Ledru sylves...@debian.org (2014-08-31):
 To make sure Jessie gets ship with a recent version of llvm, I would
 like to transit llvm from version 3.4 to 3.5.
 I am also planning to update llvm-defaults to make sure that llvm, clang
 and lldb tools are proposing version 3.5.

I'm not sure why shipping something recent enough (llvm 3.5) in jessie
should mean switching the default to that version.

 However, I am planning to keep llvm 3.4 in the archive.  So, packages
 not supporting 3.5 won't be deleted. We will just have to force the
 version 3.4.

Moreover, switching toolchain defaults while we're trying to freeze
library transitions doesn't look like a good idea; especially since
3.5 packages aren't exactly bug free.

(Granted, it's easy to say that once breakages have been noted. But
I would have expected such things to be detected and fixed before a
transition is proposed!)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#763278: wheezy-pu: gcc-4.9/4.9.1-14~deb7u1

2014-09-28 Thread Michael Gilbert

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Severity: normal
Tags: security

chromium 38 is currently planning to drop support for all compilers
less than gcc 4.8 (and all clang not built against = gcc 4.8).  So
wheezy will soon have no way to compile an up to date chromium.

In order to continue providing security updates for chromium in
wheezy, I would like to propose a gcc wheezy-pu.  I haven't tried to
get this working yet, and am sending this to see whether the release
team would even consider this.

The alternative is to drop chromium security support for wheezy way too soon.

I'm proposing gcc 4.9 to hedge against future upstream compiler
requirements, but gcc 4.8 would also be an option.

Best wishes,
Mike


-- 
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/CANTw=MMZ=5frqktmpdjnfz9wv45jy0nh+dm8mzwp-gns955...@mail.gmail.com

Bug#760050: transition: llvm-toolchain-3.5

2014-09-28 Thread Steven Chamberlain

Hi,

On 21:44, Cyril Brulebois wrote:
 Sylvestre Ledru sylves...@debian.org (2014-08-31):
  However, I am planning to keep llvm 3.4 in the archive.  So, packages
  not supporting 3.5 won't be deleted. We will just have to force the
  version 3.4.
 
 Moreover, switching toolchain defaults while we're trying to freeze
 library transitions doesn't look like a good idea; especially since
 3.5 packages aren't exactly bug free.

FWIW when building kfreebsd (kernel package) we already explicitly
depend on clang-3.4, in order to be not impacted by a change of default
such as this.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.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/20140928200657.gc26...@squeeze.pyro.eu.org

Bug#760050: transition: llvm-toolchain-3.5

Steven Chamberlain ste...@pyro.eu.org (2014-09-28):
 On 21:44, Cyril Brulebois wrote:
  Sylvestre Ledru sylves...@debian.org (2014-08-31):
   However, I am planning to keep llvm 3.4 in the archive.  So, packages
   not supporting 3.5 won't be deleted. We will just have to force the
   version 3.4.
  
  Moreover, switching toolchain defaults while we're trying to freeze
  library transitions doesn't look like a good idea; especially since
  3.5 packages aren't exactly bug free.
 
 FWIW when building kfreebsd (kernel package) we already explicitly
 depend on clang-3.4, in order to be not impacted by a change of default
 such as this.

Well I either knew or suspected that. That's what linux does as well. I
was more rather referring to doxygen's being broken and hundreds of rc
bugs as a consequence; some of which affecting packages I'm interested
in (new brltty for example).

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: your mail

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

 tag 763278 wheezy
Bug #763278 [release.debian.org] wheezy-pu: gcc-4.9/4.9.1-14~deb7u1
Added tag(s) wheezy.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763278
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.14119361711576.transcr...@bugs.debian.org

Bug#762644: wheezy-pu: package php-getid3/1.9.3-1+deb7u2

Control: tags -1 + pending

On Sat, 2014-09-27 at 15:31 -0400, David Prévot wrote:
 Hi,
 
  Please go ahead; thanks.
 
 Thanks Adam, uploaded

Flagged for acceptance.

Regards,

Adam


-- 
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/1411940285.25283.13.ca...@jacala.jungle.funky-badger.org

Processed: Re: Bug#762644: wheezy-pu: package php-getid3/1.9.3-1+deb7u2

Processing control commands:

 tags -1 + pending
Bug #762644 [release.debian.org] wheezy-pu: package php-getid3/1.9.3-1+deb7u2
Added tag(s) pending.

-- 
762644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762644
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.b762644.141194029531074.transcr...@bugs.debian.org

NEW changes in stable-new

Processing changes file: php-getid3_1.9.3-1+deb7u2_amd64.changes
  ACCEPT


-- 
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/e1xymj7-m0...@franck.debian.org

Bug#763058: marked as done (nmu: doxygen_1.8.7-3)

Your message dated Sun, 28 Sep 2014 21:59:24 +
with message-id e1xymv2-0002oq...@franck.debian.org
and subject line Bug#763058: fixed in llvm-toolchain-3.5 1:3.5-4
has caused the Debian Bug report #763058,
regarding nmu: doxygen_1.8.7-3
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.)


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

nmu doxygen_1.8.7-3 . ALL . -m binMNU because of the libclang change of soname

I updated the soname as part of the coordination to switch to llvm 3.5.
https://release.debian.org/transitions/html/llvm-defaults-3.html

I updated the soname to fix the bug #759538 and make sure that libclang can be 
co instalable for its various version.

I should have coordinated better and I haven't noticed that doxygen was 
impacted  (my bad).

So, we just need a binNMU of doxygen and it should fix the problem.

The rest of impacted packages are leaf packages and I warned the maintainers.

Cheers  sorry again,
Sylvestre
---End Message---
---BeginMessage---
Source: llvm-toolchain-3.5
Source-Version: 1:3.5-4

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-3.5, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 763...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru sylves...@debian.org (supplier of updated llvm-toolchain-3.5 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 28 Sep 2014 10:13:22 +0200
Source: llvm-toolchain-3.5
Binary: clang-3.5 clang-format-3.5 cpp11-migrate-3.5 clang-modernize-3.5 
clang-3.5-doc libclang1-3.5 libclang1-3.5-dbg libclang-3.5-dev 
libclang-common-3.5-dev python-clang-3.5 clang-3.5-examples libllvm3.5 
libllvm3.5-dbg llvm-3.5 llvm-3.5-runtime llvm-3.5-dev llvm-3.5-tools 
libllvm-3.5-ocaml-dev llvm-3.5-doc llvm-3.5-examples lldb-3.5 liblldb-3.5 
python-lldb-3.5 liblldb-3.5-dev lldb-3.5-dev
Architecture: source amd64 all
Version: 1:3.5-4
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
Changed-By: Sylvestre Ledru sylves...@debian.org
Description:
 clang-3.5  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.5-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.5-examples - Clang examples
 clang-format-3.5 - Tool to format C/C++/Obj-C code
 clang-modernize-3.5 - Tool to convert C++98 and C++03 code to C++11
 cpp11-migrate-3.5 - Tool to convert C++98 and C++03 code to C++11
 libclang-3.5-dev - clang library - Development package
 libclang-common-3.5-dev - clang library - Common development package
 libclang1-3.5 - C interface to the clang library
 libclang1-3.5-dbg - clang library
 liblldb-3.5 - Next generation, high-performance debugger, library
 liblldb-3.5-dev - Next generation, high-performance debugger - Header files
 libllvm-3.5-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm3.5 - Modular compiler and toolchain technologies, runtime library
 libllvm3.5-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lldb-3.5   - Next generation, high-performance debugger
 lldb-3.5-dev - transitional dummy package to liblldb-3.5-dev
 llvm-3.5   - Modular compiler and toolchain technologies
 llvm-3.5-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-3.5-doc - Modular compiler and toolchain technologies, documentation
 llvm-3.5-examples - Modular compiler and toolchain technologies, examples
 llvm-3.5-runtime - Modular compiler and toolchain technologies, IR interpreter
 llvm-3.5-tools - Modular compiler and toolchain technologies, tools
 python-clang-3.5 - Clang Python Bindings
 python-lldb-3.5 - Next generation, high-performance debugger, python lib
Closes: 758998 762959 763058
Changes:
 llvm-toolchain-3.5 (1:3.5-4) unstable; urgency=medium
 .
   * scan-build could not find clang binary (Closes: #758998)
   * Fix the ABI issues by installing a symlink (Closes: #762959,

NEW changes in stable-new

Processing changes file: nana_2.5-12+deb7u1_armhf.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_i386.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_kfreebsd-amd64.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_kfreebsd-i386.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_mipsel.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_powerpc.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_s390.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_s390x.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_sparc.changes
  ACCEPT


-- 
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/e1xymme-0005gz...@franck.debian.org

Bug#763297: transition: libsystemd

2014-09-28 Thread Michael Biebl

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

Hi,

in systemd v209, the various libsystemd-* libraries were merged into a
single libsystemd0 library. We still build the old libraries to not
break existing packages, though.
The libsystemd-(daemon|journal|login|id128)-dev package now point to
-lsystemd0, i.e. packages once rebuilt will link against libsystemd0 not
the old library names and we want all packages to link against the new
libsysemd0 library so we can eventually drop the compat library
packages.

Please schedule a round of binNMUs so affected packages will be rebuilt
against libsystemd0. Afaics this doesn't qualify as library transition
but it's probably easiest to find affected packages via a transition
tracker.

The ben file for it should look something like this:

title = libsystemd;
is_affected = .depends ~ libsystemd-(daemon|journal|login|id128-)0, | 
.depends ~ libsystemd0;
is_good = .depends ~ libsystemd0;
is_bad = .depends ~ libsystemd-(daemon|journal|login|id128-)0,;


The binNMU could be something like Rebuild against libsystemd0

Thanks for considering,

Michael

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

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


-- 
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/20140928222332.27507.68731.report...@pluto.milchstrasse.xx

Re: Time for Jessie Beta 2?

[ debian-release@: see last paragraph. ]

Cyril Brulebois k...@debian.org (2014-09-26):
 Cyril Brulebois k...@debian.org (2014-09-10):
  as you might have seen, a number of uploads happened lately and the
  d-i BoF notes from DebConf kindly provided by Steve (thanks!)
  reminded me about uploading d-i more often. So I think I'll try and
  achieve that as soon as linux 3.16 reaches testing (it was just
  uploaded to unstable, and FTBFSes on several architectures, so not
  this week ;)).
 
 linux/linux-latest are now ready, baring nvidida (#762977).

It migrated in the meanwhile.

  Some things got set into motion, like syslinux menu overhaul (mainly
  discussion around the switch to graphical by default, didn't see any
  patch yet) or tasksel changes (alternative desktops, blends support).
  I'm unsure they're going to be ready at that point, so I guess it would
  make sense not to wait for them and publish another release in the
  meanwhile. I'll probably gather opinions when linux is ready, this mail
  is mainly meant to be a heads-up.
 
 I'll probably skip syslinux vs. multi-arch this time, mostly due to
 lack of time and other large ongoing changes: let's see if we can get
 debian-cd to cope with latest tasksel changes soon.

Steve managed to fix debian-cd in a few minutes/hours, so that shouldn't
be a blocker. Latest tasksel reached testing, too. I've also removed
desktop preseeding as pointed out by Joey some minutes ago.

  → I'd like to know whether some bugs need special attention/fixes
(besides what's in unstable already).
  
  I haven't looked at recent bugs lately but I think we might be missing
  at least a ttf-cjk-compact-udeb upload (which might explain some issues
  reported against debian-edu IIRC), and I failed to upload choose-mirror
  for the past release (Aurelien uploaded it 10 days ago though, to get
  updated arch lists).
 
 Since the kernel is now a candidate for migration, I'll probably start
 urgenting more packages into testing during the weekend (all l10n-only
 updates, for a start), try to figure out which packages to additionally
 migrate, and freeze udeb-producing packages.

Besides partman-efi (uploaded today to drop armhf), brltty (stuck
because of llvm/clang issues), and the CJK issue (#762057), I don't
think I'm going to merge more things, so I've just frozen udebs.

Mraw,
KiBi.


signature.asc
Description: Digital signature

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_powerpc.changes
  ACCEPT


-- 
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/e1xynfm-0003du...@franck.debian.org

NEW changes in stable-new

Processing changes file: nana_2.5-12+deb7u1_mips.changes
  ACCEPT


-- 
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/e1xynth-0005py...@franck.debian.org

Bug#763058: nmu: doxygen_1.8.7-3

2014-09-28 Thread Julien Cristau

On Sun, Sep 28, 2014 at 21:25:07 +0200, Andreas Barth wrote:

 * Andreas Barth (a...@ayous.org) [140928 14:32]:
  I also have an idea for an ugly hack but I need to think a bit more
  about it. From package POV it might be the niciest, but I'm not sure
  if it works (which is a precondition for everything). I'll update this
  mail tonight.
 
 What works in practice, and seems to be ok-ish from a theoretical POV
 is to create a symlink from libclang-3.5.so.1 to
 /usr/lib/`dpkg-architecture -qDEB_BUILD_MULTIARCH`/libclang.so.1
 during build time (as part of the deb file). This allows doxygen to
 work again.
 
That seems wrong.  If wheezy's libclang1 and jessie's libclang1-3.5
aren't binary-compatible, the latter shouldn't provide a libclang.so.1.
And if they are, then there shouldn't be two different package names.
I fear we're just adding hacks on top of hacks here, somebody please
clarify.

Cheers,
Julien


signature.asc
Description: Digital signature

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_i386.changes
  ACCEPT


-- 
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/e1xynwy-0001tu...@franck.debian.org

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_armhf.changes
  ACCEPT


-- 
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/e1xyobl-0003ze...@franck.debian.org

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_amd64.changes
  ACCEPT


-- 
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/e1xyp7s-0004yz...@franck.debian.org

Bug#763058: nmu: doxygen_1.8.7-3

2014-09-28 Thread Steven Chamberlain

Hi,

[I'm trying to learn to understand this kind of thing, as well try to
elaborate on what Julien said, so please correct me if I'm wrong].

On 01:19, Julien Cristau wrote:
 On Sun, Sep 28, 2014 at 21:25:07 +0200, Andreas Barth wrote:
 
  * Andreas Barth (a...@ayous.org) [140928 14:32]:
  What works in practice, and seems to be ok-ish from a theoretical POV
  is to create a symlink from libclang-3.5.so.1 to
  /usr/lib/`dpkg-architecture -qDEB_BUILD_MULTIARCH`/libclang.so.1
  during build time (as part of the deb file). This allows doxygen to
  work again.
  
 That seems wrong.  If wheezy's libclang1 and jessie's libclang1-3.5
 aren't binary-compatible, the latter shouldn't provide a libclang.so.1.

Assuming they're not meant to be binary-compatible:

It looks like libclang.so.1 has been provided by different versions of
the LLVM toolchain since wheezy, and that was wrong.

I don't think the LLVM 'default version' transition itself caused this,
but merely exposed an existing problem, one that can't be reverted.
Already some packages were built with libclang-3.4-dev (e.g. mesa,
vim-youcompleteme) or libclang-3.5-dev (e.g. doxygen).

So doxygen for example expects libclang.so.1 to be provided by
libclang1-3.5.  When that file was (rightly) removed from libclang1-3.5
it was left broken.  Restoring a symlink from libclang.so.1 may fix it
temporarily but is not a correct thing to do;  some other package (now,
or in the future) may expect libclang.so.1 to come from a different LLVM
version and may have been subtly broken for some time already.

So AIUI Sylvestre needs to remove that symlink in a new upload, but
all reverse-deps must be NMUd to use the new, versioned library name
e.g. libclang-3.5.so.1.  Except I think the package name needs to be
changed in order to do that, so perhaps a soname bump to
libclang-3.5.so.2 provided by libclang2-3.5?

The existing transition bug and tracker could possibly be repurposed
for this?
https://release.debian.org/transitions/html/llvm-defaults-3.html

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.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/20140929012610.gh26...@squeeze.pyro.eu.org

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_sparc.changes
  ACCEPT


-- 
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/e1xyq3r-0003cn...@franck.debian.org

packages.debian.org По поводу сайта

2014-09-28 Thread Служба рассылок

Добрый день!

Я наткнулся случайно на Ваш web сайт и обратил внимание - что на нем низкая 
посещаемость.

Я занимаюсь профессионально продвижение товаров и услуг в интернете.

Предлагаю осуществить email рассылку Вашей информации.

Пожалуйста сообщите - было бы Вам интересно воспользоваться моими услугами?

Если интересно - пожалуйста пришлите Ваше коммерческое предложение - я сверстаю 
из него макет для рассылки.

Заранее благодарен за ответ Вячеслав.
7(  Ч9 5 ) 5  1О ~ 7 5   -  2З


-- 
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/0854278...@hch.philb.info

NEW changes in stable-new

Processing changes file: linux_3.2.63-1_armel.changes
  ACCEPT
Processing changes file: linux_3.2.63-1_ia64.changes
  ACCEPT
Processing changes file: nana_2.5-12+deb7u1_ia64.changes
  ACCEPT


-- 
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/e1xysan-0004zx...@franck.debian.org

NEW changes in stable-new