Bug#698946: Security update broke php-cas, wrong call to setSslCaCert()

[Thijs Kinkhorst]

On Sat, January 26, 2013 16:05, Olivier Berger wrote:
> As you can see in [0], I've integrated the full upstream commit [1] and
> not just the change on Client.php.
>
> Hope this helps.

The updated package indeed fixes the problem and works fine. Thanks!


Cheers,
Thijs


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699034: similar bug report

[Trek]

you may find interesting this bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640501

that was fixed downgrading libgcrypt11 to the 1.4.6-9 version from:

http://snapshot.debian.org/archive/debian/20110807T212024Z/pool/main/libg/libgcrypt11/

may be it is the same bug?

Ciao


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#681830: Reproduced

[Josselin Mouette]

Le dimanche 27 janvier 2013 à 19:42 +, Neil Williams a écrit : 
> gdm3 was stopped over an SSH connection using invoke-rc.d. Then I
> started gdm3 from the command line (on a directly connected keyboard)
> to generate endless lists of:
> 
> gdm3[17041]: WARNING: GdmDisplay: display lasted 1.681562 seconds
> gdm3[17041]: WARNING: GdmDisplay: display lasted 1.687131 seconds
> gdm3[17041]: WARNING: GdmDisplay: display lasted 1.693576 seconds
> 
>  daemon/gdm-display.c : 725
>g_warning ("GdmDisplay: display lasted %lf seconds",elapsed);
> 
> I changed the shell script to avoid the 3 second timeout (which makes
> this much more manageable) and gdm3 just keeps respawning using
> gdm-simple-slave, incrementing the --display-id each time.

As mentioned on IRC, there is already some code to handle GdmDisplay
respawning too fast. See on_display_status_changed() in
gdm-local-display-factory.c.

I’m interested in logs with debugging enabled, especially stuff like
“GdmLocalDisplayFactory: display status changed”.

Cheers,
-- 
 .''`.  Josselin Mouette
: :' :
`. `'
  `-


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699096: gpa: Segmentation fault in _assuan_socket due to missing assuan_sock_init() call

[Daniel Leidert]

Hi Michael,

The segfault during `gpa -d' got fixed in the recent upload of gpa/0.9.0-4.

Regards, Daniel


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#674156: glib2.0: GStaticMutex ABI change on armel, armhf, mipsel, powerpc, s390, sparc and probably mips

[Simon McVittie]

On Fri, 11 Jan 2013 at 18:39:24 +, Simon McVittie wrote:
> By making a sourceful upload
> of gstreamer0.10, together with the sourceful upload of swami that has
> already happened and a pile of 14 binNMUs (see 694525#59), we can get
> full upgrades into a consistent state.

Julien has NMU'd gstreamer0.10 and scheduled some binNMUs, and swami has
migrated, so all we're waiting for to achieve this is for gstreamer0.10
to migrate. (This can be tracked by waiting for #697025, which is also RC,
to migrate.)

So, assuming no serious problems with the NMU, it's only a matter of time
before full upgrades are OK.

Regarding the original bug, gnome-dvb-daemon was recently built on the
affected architectures; it is now built on all Linux architectures.
So, from that point of view, job done.

As for partial upgrades: Julien's NMU of gstreamer0.10 bumped the shlibs,
so if dependent packages are rebuilt (up to 22 source NMUs of Multi-arch: same
packages, and up to 38 binNMUs of other packages,
see http://bugs.debian.org/694525#59), certain broken combinations
(namely: new dependent package, old gstreamer0.10) will be prevented.
There hasn't been any systematic upload of these; it's an open question
whether it's worthwhile to do all of these, or just the binNMUs, or neither.

The other broken combination (new gstreamer0.10, old dependent package)
can only be addressed via Breaks relations. I think Julien's conclusion
was that this has an unacceptable risk of introducing weird upgrade bugs
where apt fails to find a solution, similar to
?

Regards,
S


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: scli: FTBFS due to glib changes

[Debian Bug Tracking System]

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

> retitle 690092 scli: FTBFS due to glib changes
Bug #690092 [scli] scli: fails to build in ubuntu due to glib changes
Changed Bug title to 'scli: FTBFS due to glib changes' from 'scli: fails to 
build in ubuntu due to glib changes'
> # justification: FTBFS
> severity 690092 serious
Bug #690092 [scli] scli: FTBFS due to glib changes
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Ana Guerrero]

Package: src:hdf5
Version: 1.8.8-9
Severity: serious

In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that
allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4,
libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on
libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | 
libhdf5-1.8.4)

In Wheezy those libraries are not longer ABI compatible, therefore
the serial version was renamed libhdf5-7 and also the packages of the others
versions, for example libhdf5-openmpi-7, has a provides line:
Provides: libhdf5-1.8, libhdf5-7

So you can install for example, r-cran-hdf5 and it will install by default
the serial version (libhdf5-7), but you can also install it at the
same time than libhdf5-openmpi-7 (or you might have it installed already)
and then you will get it installed with the openMPI version despite being built
against the serial version, that as said isn't ABI compatible.

Some packages, such as slepc, have their build dependencies explicitly against
the openMPI version and those are OK.

Due the ABI incompatibility we can not longer use the same scheme than in
Squeeze, but I think having the serial version named libhdf5-7 is confusing.

Possible solutions... given the proximity of the release I'm aware some of
them might not be possible but I'm listing everything for the sake of
completeness, don't jump in your chair when reading some of the possibilities
listed :-)

a) Have libhdf5-7 renamed back with the *serial* label (libhdf5-serial-1.8.4) 
and also the -dev packages. Then have the packages using hdf5 depending on 
the supported implementation(s), that is if they support several implementation
provide a binary for implementation: r-cran-hdf5-serial r-cran-hdf5-openMPI

b)  Switch all the packages to use only one of the implementation except
those that only work in of the implementations, depending explicitly in
*-serial-*  or *-openmpi-* (or mpich in those archs that don't support
openMPI).
 b.1) make this implementation by default to be the serial version
 b.2) make this implementation by default to be the openMPI version. Which 
doesn't
sound like a crazy idea if you look at the popcon [1] and think the context
hdf5 is widely used (supercomputing).

c) Remove the provides from libhdf5-openmpi-7 and libhdf5-mpich-7 and keep
the status quo. You either install libhdf5-openmpi-7 with the packages
needing this implementation or you install libhdf5-7 with the packages
depending on this one. If you go to decide for the openmpi version
and you need a package only built for the serial version, you would
need to rebuild it.
(This is somehow a variation of b.1) because all the stuff is built against
the serial version unless the maintainer explicitily puts the openmpi one )

d) ? :)

In any case, how to switch or handle the different implementation would be nice
to have documented in a README file.

Ana

[1] http://qa.debian.org/popcon.php?package=hdf5
If you look at the amout of installations of libhdf5-openmpi-dev installations
it is the same that libhdf5-dev and growing faster.
As curiosity note: after the rename of the serial version to be the *default*
version was uploaded to unstable around January 2012, you can see libhdf5-7
rocketed in the popcon graph.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#631729: irssi-plugin-xmpp: Memory corruption and crash with /xmppconnect

[Michael Stapelberg]

tags 631729 + patch
thanks

Hi,

I used “nc -4 -l -p 5222” to simulate a local jabber server, then
started irssi, used /load xmpp and /xmppconnect -h localhost f@b to
trigger the issue.

Attached you can find the patch with which I have come up. Here is the
description:

 Previously, loudmouth would set socket->watch_connect to NULL when
 encountering an error. When the connection attempt (to a different
 IPv6) succeeded later on, _lm_socket_succeeded would therefore not
 remove the socket_connect_cb watcher, leading to socket_connect_cb
 being called upon socket activity and segfaulting the program.

This patch fixes the issue for me, but I don’t use irssi-plugin-xmpp
normally, so testing/review is welcome.

-- 
Best regards,
Michael
Description: fix crash when falling back from IPv6 to IPv4
 Previously, loudmouth would set socket->watch_connect to NULL when
 encountering an error. When the connection attempt (to a different IPv6)
 succeeded later on, _lm_socket_succeeded would therefore not remove the
 socket_connect_cb watcher, leading to socket_connect_cb being called upon
 socket activity and segfaulting the program.
Author: Michael Stapelberg 
Bug-Debian: http://bugs.debian.org/631729
Last-Update: 2013-01-28

--- loudmouth-1.4.3.orig/loudmouth/lm-socket.c
+++ loudmouth-1.4.3/loudmouth/lm-socket.c
@@ -529,7 +529,6 @@ socket_connect_cb (GIOChannel   *source,
 			/* error condition, but might be possible to recover
 			 * from it (by connecting to the next host) */
 			if (!_lm_socket_failed_with_error (connect_data, err)) {
-socket->watch_connect = NULL;
 goto out;
 			}
 		}
@@ -560,7 +559,6 @@ socket_connect_cb (GIOChannel   *source,
 _lm_sock_close (connect_data->fd);
 _lm_socket_failed_with_error (connect_data, err);
 
-socket->watch_connect = NULL;
 goto out;
 			}
 		} 

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Sylvestre Ledru]

tags 699155 help
thanks

On 28/01/2013 11:04, Ana Guerrero wrote:
> 
> Package: src:hdf5
> Version: 1.8.8-9
> Severity: serious
> 
> In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that
> allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4,
> libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on
> libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | 
> libhdf5-1.8.4)
Merci Ana for this full bug.
It would be nice to have some help here. I must admit that I don't know
what would be the best solution...

Thanks,
Sylvestre


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Debian Bug Tracking System]

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

> tags 699155 help
Bug #699155 [src:hdf5] hdf5: dependencies can be satisfied interchangeably with 
libraries providing different ABIs
Added tag(s) help.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#631729: irssi-plugin-xmpp: Memory corruption and crash with /xmppconnect

[Debian Bug Tracking System]

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

> tags 631729 + patch
Bug #631729 [libloudmouth1-0] libloudmouth1-0: segfaults when connecting to a 
dual-stacked host
Added tag(s) patch.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#667526: hdf5 upgrade Squeeze-> Wheezy (#667599, #667526)

[Ana Guerrero]

Hi!

There are *two* problems with the upgrade of hdf5 from Squeeze to Wheezy
that are a consequence of the problem of the fix for #566541.
One of then, reported in (#667599, #667526), can be solved easily
as explained by marga at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667599#62
and others have hinted before. The second problem is related with this one
and more complicated to solve. I haved filed the bug report #699155 for this.

About this problem, in short, if you have installed the openmpi version,
the upgrade will install you the serial implementation,  and remove
the openmpi implementation.


E.g. minimal installation of squeeze where libhdf5-openmpi-1.8.4 and 
hdf5-tools are installed:

ii  hdf5-tools  1.8.4-patch1-2   
Hierarchical Data Format 5 (HDF5) - Runtime tools
ii  libhdf5-openmpi-1.8.4   1.8.4-patch1-2   
Hierarchical Data Format 5 (HDF5) - runtime files - OpenMPI version  

ii  libhdf5-serial-1.8.41.8.4-patch1-2   
Hierarchical Data Format 5 (HDF5) - runtime files - serial version
ii  r-cran-hdf5 1.6.9-2+b1   GNU R 
package interfacing the NCSA HDF5 library

If we update this system to Wheezy, you'll get:

# apt-get -u dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  console-terminus defoma libept1 libhdf5-openmpi-1.8.4 libpango1.0-common 
libperl5.10 portmap x-ttcidfont-conf
The following NEW packages will be installed:
 [...]
 libhdf5-7
 [...]
  hdf5-tools 
[...]
   368 upgraded, 174 newly installed, 8 to remove and 0 not upgraded.
Need to get 252 MB of archives.
After this operation, 302 MB of additional disk space will be used.
Do you want to continue [Y/n]? 

The openmpi version is upgraded with the serial version instead of being
replaced with libhdf5-openmpi-7.


In the case of dolfin-dev (#667599) in Squeeze, the package has the following 
dependency chain to hdf5 (as somebody else has analyzed already in the bug 
report):

dolfin-dev -> libdolfin1.0-dev -> libslepc3.0.0-dev -> libslepc3.0.0 -> 
libhdf5-openmpi-1.8.4 

and when upgraded, we have the reported problem.
In wheezy, libslepc3.2 depends explicitiy on the openmpi version only. 
This means if we install libslepc3.0.0 in wheezy we must switch all our system
to use the openmpi library.

For simgear-dev (#667526), the chain dependency  in Squeeze is:
simgear-dev -> simgear1.9.1 ->  libopenscenegraph65 -> libgdal1-1.6.0 -> 
libhdf5-serial-1.8.4 | libhdf5-1.8.4

Where libhdf5-1.8.4 could be provided by libhdf5-openmpi-1.8.4 and we have
the same problem that with dolfin-dev. Although in this case the dependency
can be satisfied both by the serial and the openmpi packages in Wheezy.
This is wrong because both libraries provided different ABIs as reported
in bug #699155


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Julien Cristau]

On Mon, Jan 28, 2013 at 11:04:09 +0100, Ana Guerrero wrote:

> 
> Package: src:hdf5
> Version: 1.8.8-9
> Severity: serious
> 
> In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that
> allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4,
> libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on
> libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | 
> libhdf5-1.8.4)
> 
> In Wheezy those libraries are not longer ABI compatible, therefore
> the serial version was renamed libhdf5-7 and also the packages of the others
> versions, for example libhdf5-openmpi-7, has a provides line:
> Provides: libhdf5-1.8, libhdf5-7
> 
> So you can install for example, r-cran-hdf5 and it will install by default
> the serial version (libhdf5-7), but you can also install it at the
> same time than libhdf5-openmpi-7 (or you might have it installed already)
> and then you will get it installed with the openMPI version despite being 
> built
> against the serial version, that as said isn't ABI compatible.
> 
do you have pointers/details about that ABI incompatibility?  I'm pretty
sure I looked through exported symbols and headers from hdf5 a year ago,
and didn't see anything that would break when building against the
serial version and running against openmpi, but I may have missed
something.

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#698102: eglibc: initgroups changes egid on kfreebsd

[Petr Salinger]

Unfortuantely, POSIX declined to specify setgroups() and initgroups() is
not in any standard, so it's hard to say which behavior is right and
which is wrong.  It seems possible to argue any of the following:

1. The bug is in kFreeBSD's implementation of setgroups(), which must
   be fixed so that eglibc's initgroups() implementation works as
   expected.

2. The bug is in eglibc's implementation of initgroups(), which must be
   fixed so that it works properly with kFreeBSD's setgroups().

3. Since both behaviors of setgroups() and initgroups() are seen "in
   the wild", programs that depend on the linux kernel behavior are
   broken and should be fixed as they become known.

Personally I'm leaning towards 3 here, since these are buggy not only on
debian/kFreeBSD but on real FreeBSD as well.


Even POSIX point out that egid might be somewhere in supplementary groups
http://pubs.opengroup.org/onlinepubs/9699919799/functions/getgroups.html

  The getgroups() function shall fill in the array grouplist with the
  current supplementary group IDs of the calling process. It is
  implementation-defined whether getgroups() also returns the effective
  group ID in the grouplist array.

Under FreeBSD kernel, the "egid" is groups[0], see
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_prot.c

IMO, there is no bug, the behaviour is implementation-defined.

Petr


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Julien Cristau]

On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote:

> On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> > do you have pointers/details about that ABI incompatibility?  I'm pretty
> > sure I looked through exported symbols and headers from hdf5 a year ago,
> > and didn't see anything that would break when building against the
> > serial version and running against openmpi, but I may have missed
> > something.
> 
> I didn't check further than the attached diff, there are mostly symbols
> being added in the openMPI version but also some symbols dissapearing.
> 
OK.  So you didn't get any runtime issues with this?

> -H5E_get_stack

declared in src/H5Epkg.h, which doesn't seem to be in libhdf5-dev.

> -H5TS_cancel_count_dec
> -H5TS_cancel_count_inc
> -H5TS_create_thread

declared in src/H5TSprivate.h, probably not intended to be public (and
not installed in the -dev package).

> -H5TS_mutex_lock
> -H5TS_mutex_unlock

same here.

> -H5TS_pthread_first_thread_init

and again.

Unless you have evidence of an actual problem with software using hdf5
I'm tempted to close this as a non-bug...

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Ana Guerrero]

On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> do you have pointers/details about that ABI incompatibility?  I'm pretty
> sure I looked through exported symbols and headers from hdf5 a year ago,
> and didn't see anything that would break when building against the
> serial version and running against openmpi, but I may have missed
> something.

I didn't check further than the attached diff, there are mostly symbols
being added in the openMPI version but also some symbols dissapearing.

Ana
--- libhdf5-7/libhdf5_fortran.so.7
+++ libhdf5-openmpi-7/libhdf5_fortran.so.7
@@ -395,6 +395,12 @@
 h5eset_auto_c_
 h5fclose_c_
 h5fcreate_c_
+__h5fdmpio_MOD_h5pget_dxpl_mpio_f
+__h5fdmpio_MOD_h5pget_fapl_mpio_f
+__h5fdmpio_MOD_h5pget_fapl_mpiposix_f
+__h5fdmpio_MOD_h5pset_dxpl_mpio_f
+__h5fdmpio_MOD_h5pset_fapl_mpio_f
+__h5fdmpio_MOD_h5pset_fapl_mpiposix_f
 h5fflush_c_
 h5fget_access_plist_c_
 h5fget_create_plist_c_
@@ -553,6 +559,7 @@
 h5pget_data_transform_c_
 h5pget_double_c_
 h5pget_driver_c_
+h5pget_dxpl_mpio_c_
 h5pget_edc_check_c_
 h5pget_est_link_info_c_
 h5pget_external_c_
@@ -560,6 +567,8 @@
 h5pget_fapl_core_c_
 h5pget_fapl_direct_c_
 h5pget_fapl_family_c_
+h5pget_fapl_mpio_c_
+h5pget_fapl_mpiposix_c_
 h5pget_fapl_multi_c_
 h5pget_fclose_degree_c_
 h5pget_fill_time_c_
@@ -758,6 +767,7 @@
 h5pset_data_transform_c_
 h5pset_deflate_c_
 h5pset_double_c_
+h5pset_dxpl_mpio_c_
 h5pset_edc_check_c_
 h5pset_est_link_info_c_
 h5pset_external_c_
@@ -765,6 +775,8 @@
 h5pset_fapl_core_c_
 h5pset_fapl_direct_c_
 h5pset_fapl_family_c_
+h5pset_fapl_mpio_c_
+h5pset_fapl_mpiposix_c_
 h5pset_fapl_multi_c_
 h5pset_fapl_multi_sc_
 h5pset_fapl_sec2_c_
--- libhdf5-7/libhdf5_fortran.so.7.0.2
+++ libhdf5-openmpi-7/libhdf5_fortran.so.7.0.2
@@ -395,6 +395,12 @@
 h5eset_auto_c_
 h5fclose_c_
 h5fcreate_c_
+__h5fdmpio_MOD_h5pget_dxpl_mpio_f
+__h5fdmpio_MOD_h5pget_fapl_mpio_f
+__h5fdmpio_MOD_h5pget_fapl_mpiposix_f
+__h5fdmpio_MOD_h5pset_dxpl_mpio_f
+__h5fdmpio_MOD_h5pset_fapl_mpio_f
+__h5fdmpio_MOD_h5pset_fapl_mpiposix_f
 h5fflush_c_
 h5fget_access_plist_c_
 h5fget_create_plist_c_
@@ -553,6 +559,7 @@
 h5pget_data_transform_c_
 h5pget_double_c_
 h5pget_driver_c_
+h5pget_dxpl_mpio_c_
 h5pget_edc_check_c_
 h5pget_est_link_info_c_
 h5pget_external_c_
@@ -560,6 +567,8 @@
 h5pget_fapl_core_c_
 h5pget_fapl_direct_c_
 h5pget_fapl_family_c_
+h5pget_fapl_mpio_c_
+h5pget_fapl_mpiposix_c_
 h5pget_fapl_multi_c_
 h5pget_fclose_degree_c_
 h5pget_fill_time_c_
@@ -758,6 +767,7 @@
 h5pset_data_transform_c_
 h5pset_deflate_c_
 h5pset_double_c_
+h5pset_dxpl_mpio_c_
 h5pset_edc_check_c_
 h5pset_est_link_info_c_
 h5pset_external_c_
@@ -765,6 +775,8 @@
 h5pset_fapl_core_c_
 h5pset_fapl_direct_c_
 h5pset_fapl_family_c_
+h5pset_fapl_mpio_c_
+h5pset_fapl_mpiposix_c_
 h5pset_fapl_multi_c_
 h5pset_fapl_multi_sc_
 h5pset_fapl_sec2_c_
diff -Nurd libhdf5-7/libhdf5.so.7
--- libhdf5-7/libhdf5.so.7
+++ libhdf5-openmpi-7/libhdf5.so.7
@@ -3,6 +3,7 @@
 H5A_attr_iterate_table
 H5A_attr_post_copy_file
 H5A_attr_release_table
+H5AC_add_candidate
 H5AC_close_trace_file
 H5AC_create
 H5AC_dest
@@ -30,7 +31,13 @@
 H5Acreate_by_name
 H5AC_reset_cache_hit_rate_stats
 H5AC_resize_entry
+H5AC_rsp__dist_md_write__flush
+H5AC_rsp__dist_md_write__flush_to_min_clean
+H5AC_rsp__p0_only__flush
+H5AC_rsp__p0_only__flush_to_min_clean
 H5AC_set_cache_auto_resize_config
+H5AC_set_sync_point_done_callback
+H5AC_set_write_done_callback
 H5AC_stats
 H5AC_term_interface
 H5AC_unpin_entry
@@ -153,6 +160,9 @@
 H5_buffer_dump
 H5_build_extpath
 H5B_valid
+H5C_apply_candidate_list
+H5C_construct_candidate_list__clean_cache
+H5C_construct_candidate_list__min_clean
 H5C_create
 H5C_def_auto_resize_rpt_fcn
 H5C_dest
@@ -174,6 +184,7 @@
 H5check_version
 H5C_insert_entry
 H5close
+H5C_mark_entries_as_clean
 H5C_mark_entry_dirty
 H5C_move_entry
 H5C_pin_protected_entry
@@ -192,11 +203,14 @@
 H5D_alloc_storage
 H5D_btree_debug
 H5D_check_filters
+H5D_chunk_addrmap
 H5D_chunk_allocate
 H5D_chunk_allocated
 H5D_chunk_bh_info
 H5D_chunk_cacheable
 H5D_chunk_cinfo_cache_reset
+H5D_chunk_collective_read
+H5D_chunk_collective_write
 H5D_chunk_copy
 H5D_chunk_create
 H5D_chunk_delete
@@ -216,6 +230,8 @@
 H5D_compact_copy
 H5D_compact_fill
 H5D_contig_alloc
+H5D_contig_collective_read
+H5D_contig_collective_write
 H5D_contig_copy
 H5D_contig_delete
 H5D_contig_fill
@@ -263,6 +279,9 @@
 H5D_layout_set_io_ops
 H5D_layout_version_test
 H5D_mark
+H5D_mpio_opt_possible
+H5D_mpio_select_read
+H5D_mpio_select_write
 H5D_nameof
 H5D_oloc
 H5dont_atexit
@@ -304,7 +323,6 @@
 H5E_get_msg
 H5Eget_msg
 H5Eget_num
-H5E_get_stack
 H5E_init
 H5Epop
 H5E_pop
@@ -385,6 +403,19 @@
 H5FD_init
 H5FD_log_init
 H5FD_log_term
+H5FD_mpi_comm_info_dup
+H5FD_mpi_comm_info_free
+H5FD_mpi_get_comm
+H5FD_mpi_get_rank
+H5FD_mpi_get_size
+H5FD_mpi_haddr_to_MPIOff
+H5FD_mpi_MPIOff_to_haddr
+H5FD_mpio_init
+H5FD_mpio_term
+H5FD_mpiposix_init
+H5FD_mpiposix_term
+H5FD_mpi_setup_collective
+H5FD_mpi_teardown_collective
 H5FD_multi_ini

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Ana Guerrero]

On Mon, Jan 28, 2013 at 12:26:18PM +0100, Julien Cristau wrote:
> On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote:
> 
> > On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> > > do you have pointers/details about that ABI incompatibility?  I'm pretty
> > > sure I looked through exported symbols and headers from hdf5 a year ago,
> > > and didn't see anything that would break when building against the
> > > serial version and running against openmpi, but I may have missed
> > > something.
> > 
> > I didn't check further than the attached diff, there are mostly symbols
> > being added in the openMPI version but also some symbols dissapearing.
> > 
> OK.  So you didn't get any runtime issues with this?
>
I haven't tried :) I only checked the symbols diff quickly as said.

If you're fully sure we won't run in any runtime problems, then why
hdf5 doesn't use the same scheme than in Squeeze?
The problem with the upgrades still stands.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699066: xgks: Contains code preventing commercial distribution

[Alastair McKinstry]

Ok, I am contacting the original author of this code, to see if he
is willing to make a change. The code was written in 1990 or so,
and he may not have been aware of the consequences of his actions.

Annoying that the "Small print" appeared so far down in the file and
was missed during the original licensing checks.

I will investigate if ferret-vis can be built without this, just in case.

regards
Alastair
(Maintainer of xgks and ferret).


On 2013-01-27 11:50, Francesco Poli wrote:
> On Sat, 26 Jan 2013 19:31:33 -0500 Luke Faraone wrote:
>
> [...]
>> src/port/misc/config.c:
> [...]
>>>   and cause the whole of any work that you distribute
>>>   or publish, that in whole or in part contains or is a derivative of
>>>   this program or any part thereof, to be licensed at no charge to
>>>   all third parties on terms identical to those here.
> [...]
>> The text "to be licensed at no charge" sounds like it forbids commercial
>> distribution.
> Mmmmh, I am not too convinced.
> It says "licensed at no charge", not "distributed at no charge".
>
> Please compare with clause 2b of the GNU GPL v2:
>
> |   b) You must cause any work that you distribute or publish, that in
> |   whole or in part contains or is derived from the Program or any
> |   part thereof, to be licensed as a whole at no charge to all third
> |   parties under the terms of this License.
>
> It seems to be pretty equivalent...
>
> The license of src/port/misc/config.c looks like a not-too-strong
> copyleft (GPL-incompatible) license. I haven't spotted any
> DFSG-freeness issues.
>
> As far as the other additional violations (pointed out in message #10
> [1]) are concerned, I have nothing to comment...
>
> [1] http://bugs.debian.org/699066#10
>
>
> N.B.: I am not a maintainer of this package and I know nothing about
> it; I am just a debian-legal regular who happened to notice this RC
> bug... I hope my comment helps a little.
>


-- 
Alastair McKinstry  ,  , 
http://blog.sceal.ie

Anyone who believes exponential growth can go on forever in a finite world
is either a madman or an economist - Kenneth Boulter, Economist.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699165: rsync: debian/rules using ` instead of $(shell

[StalkR]

Package: rsync
Version: 3.0.9-4
Severity: serious
Tags: patch
Justification: fails to build from source


On squeeze, I failed to compile rsync/unstable from source:
dpkg-source -x rsync_3.0.9-4.dsc
cd rsync-3.0.9
dpkg-buildpackage -rfakeroot -b
[...] errors related to compiler not found.. but after a look at
config.log it was because not expanding `dpkg-buildflags --get CFLAGS`.
I traced that back to debian/rules, where for CFLAGS/LDFLAGS:
  CFLAGS += `dpkg-buildflags --get CFLAGS`
  LDFLAGS = `dpkg-buildflags --get LDFLAGS`
while for CPPFLAGS:
  CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)

The following patch for debian/rules solved the issue:

-CFLAGS += `dpkg-buildflags --get CFLAGS`
-LDFLAGS = `dpkg-buildflags --get LDFLAGS`
+CFLAGS += $(shell dpkg-buildflags --get CFLAGS)
+LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS)

Cheers,
StalkR

-- System Information:
Debian Release: 6.0.6
  APT prefers stable
  APT policy: (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages rsync depends on:
ii  base-files  6.0squeeze6  Debian base system miscellaneous f
ii  libacl1 2.2.49-4 Access control list shared library
ii  libc6   2.11.3-4 Embedded GNU C Library: Shared lib
ii  libpopt01.16-1   lib for parsing cmdline parameters
ii  lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip

Other:
ii  gcc 4:4.4.5-1The GNU C compiler
ii  gcc-4.4 4.4.5-8  The GNU C compiler
ii  gcc-4.4-base4.4.5-8  The GNU Compiler Colle

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699155: marked as done (hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 13:26:12 +0100
with message-id <20130128122612.gb10...@crater2.logilab.fr>
and subject line Re: Bug#699155: hdf5: dependencies can be satisfied 
interchangeably with libraries providing different ABIs
has caused the Debian Bug report #699155,
regarding hdf5: dependencies can be satisfied interchangeably with libraries 
providing different ABIs
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.)


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

Package: src:hdf5
Version: 1.8.8-9
Severity: serious

In Squeeze there are two virtual packages libhdf5-1.8 and libhdf5-1.8.4, that
allow to install either libhdf5-serial-1.8.4, libhdf5-openmpi-1.8.4,
libhdf5-mpich-1.8.4 or libhdf5-lam-1.8.4 to satisfy the dependency on
libhdf5-1.8.4. (Usually packages are depending on: libhdf5-serial-1.8.4 | 
libhdf5-1.8.4)

In Wheezy those libraries are not longer ABI compatible, therefore
the serial version was renamed libhdf5-7 and also the packages of the others
versions, for example libhdf5-openmpi-7, has a provides line:
Provides: libhdf5-1.8, libhdf5-7

So you can install for example, r-cran-hdf5 and it will install by default
the serial version (libhdf5-7), but you can also install it at the
same time than libhdf5-openmpi-7 (or you might have it installed already)
and then you will get it installed with the openMPI version despite being built
against the serial version, that as said isn't ABI compatible.

Some packages, such as slepc, have their build dependencies explicitly against
the openMPI version and those are OK.

Due the ABI incompatibility we can not longer use the same scheme than in
Squeeze, but I think having the serial version named libhdf5-7 is confusing.

Possible solutions... given the proximity of the release I'm aware some of
them might not be possible but I'm listing everything for the sake of
completeness, don't jump in your chair when reading some of the possibilities
listed :-)

a) Have libhdf5-7 renamed back with the *serial* label (libhdf5-serial-1.8.4) 
and also the -dev packages. Then have the packages using hdf5 depending on 
the supported implementation(s), that is if they support several implementation
provide a binary for implementation: r-cran-hdf5-serial r-cran-hdf5-openMPI

b)  Switch all the packages to use only one of the implementation except
those that only work in of the implementations, depending explicitly in
*-serial-*  or *-openmpi-* (or mpich in those archs that don't support
openMPI).
 b.1) make this implementation by default to be the serial version
 b.2) make this implementation by default to be the openMPI version. Which 
doesn't
sound like a crazy idea if you look at the popcon [1] and think the context
hdf5 is widely used (supercomputing).

c) Remove the provides from libhdf5-openmpi-7 and libhdf5-mpich-7 and keep
the status quo. You either install libhdf5-openmpi-7 with the packages
needing this implementation or you install libhdf5-7 with the packages
depending on this one. If you go to decide for the openmpi version
and you need a package only built for the serial version, you would
need to rebuild it.
(This is somehow a variation of b.1) because all the stuff is built against
the serial version unless the maintainer explicitily puts the openmpi one )

d) ? :)

In any case, how to switch or handle the different implementation would be nice
to have documented in a README file.

Ana

[1] http://qa.debian.org/popcon.php?package=hdf5
If you look at the amout of installations of libhdf5-openmpi-dev installations
it is the same that libhdf5-dev and growing faster.
As curiosity note: after the rename of the serial version to be the *default*
version was uploaded to unstable around January 2012, you can see libhdf5-7
rocketed in the popcon graph.
--- End Message ---
--- Begin Message ---
On Mon, Jan 28, 2013 at 13:03:02 +0100, Ana Guerrero wrote:

> On Mon, Jan 28, 2013 at 12:26:18PM +0100, Julien Cristau wrote:
> > On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote:
> > 
> > > On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> > > > do you have pointers/details about that ABI incompatibility?  I'm pretty
> > > > sure I looked through exported symbols and headers from hdf5 a year ago,
> > > > and didn't see anything that would break when building against the
> > > > serial version and running against openmpi, but I may have missed
> > > > something.
> > > 
> > > I didn't check further than the attached diff, there are mostly symbols
> > > being 

Bug#699165: rsync: debian/rules using ` instead of $(shell

[StalkR]

Hi Paul,

Thanks for the quick reply. Strange then something must be wrong with my config.

$ ls -l /bin/sh
lrwxrwxrwx 1 root root 4 May 14  2010 /bin/sh -> bash*

$ dpkg -l bash
ii  bash 4.1-3
The GNU Bourne Again SHell

Attached dpkg-buildpackage stdout log and debian/buildtree/config.log

Thanks for your help,
StalkR

On Mon, Jan 28, 2013 at 1:19 PM, Paul Slootman  wrote:
> On Mon 28 Jan 2013, StalkR wrote:
>>
>> On squeeze, I failed to compile rsync/unstable from source:
>> dpkg-source -x rsync_3.0.9-4.dsc
>> cd rsync-3.0.9
>> dpkg-buildpackage -rfakeroot -b
>> [...] errors related to compiler not found.. but after a look at
>> config.log it was because not expanding `dpkg-buildflags --get CFLAGS`.
>> I traced that back to debian/rules, where for CFLAGS/LDFLAGS:
>>   CFLAGS += `dpkg-buildflags --get CFLAGS`
>>   LDFLAGS = `dpkg-buildflags --get LDFLAGS`
>> while for CPPFLAGS:
>>   CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
>
> Can you send the complete buildlog? I have no problem whatsoever with
> building on squeeze.
>
> What is your default /bin/sh ?
>
>
> Paul


config.log
Description: Binary data


dpkg-buildpackage.log
Description: Binary data

Bug#699165: rsync: debian/rules using ` instead of $(shell

[StalkR]

You can ignore the DEBUG lines in config.log, it was me trying to
trace the problem by editing configure.sh.

The issue happened here:
configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get
CFLAGS` -g -O2   conftest.c  >&5
x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory
x86_64-linux-gnu-gcc: CFLAGS`: No such file or directory
cc1: error: unrecognized command line option "-fget"

On Mon, Jan 28, 2013 at 1:26 PM, StalkR  wrote:
> Hi Paul,
>
> Thanks for the quick reply. Strange then something must be wrong with my 
> config.
>
> $ ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 May 14  2010 /bin/sh -> bash*
>
> $ dpkg -l bash
> ii  bash 4.1-3
> The GNU Bourne Again SHell
>
> Attached dpkg-buildpackage stdout log and debian/buildtree/config.log
>
> Thanks for your help,
> StalkR
>
> On Mon, Jan 28, 2013 at 1:19 PM, Paul Slootman  wrote:
>> On Mon 28 Jan 2013, StalkR wrote:
>>>
>>> On squeeze, I failed to compile rsync/unstable from source:
>>> dpkg-source -x rsync_3.0.9-4.dsc
>>> cd rsync-3.0.9
>>> dpkg-buildpackage -rfakeroot -b
>>> [...] errors related to compiler not found.. but after a look at
>>> config.log it was because not expanding `dpkg-buildflags --get CFLAGS`.
>>> I traced that back to debian/rules, where for CFLAGS/LDFLAGS:
>>>   CFLAGS += `dpkg-buildflags --get CFLAGS`
>>>   LDFLAGS = `dpkg-buildflags --get LDFLAGS`
>>> while for CPPFLAGS:
>>>   CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
>>
>> Can you send the complete buildlog? I have no problem whatsoever with
>> building on squeeze.
>>
>> What is your default /bin/sh ?
>>
>>
>> Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699165: rsync: debian/rules using ` instead of $(shell

[Paul Slootman]

On Mon 28 Jan 2013, StalkR wrote:
> 
> On squeeze, I failed to compile rsync/unstable from source:
> dpkg-source -x rsync_3.0.9-4.dsc
> cd rsync-3.0.9
> dpkg-buildpackage -rfakeroot -b
> [...] errors related to compiler not found.. but after a look at
> config.log it was because not expanding `dpkg-buildflags --get CFLAGS`.
> I traced that back to debian/rules, where for CFLAGS/LDFLAGS:
>   CFLAGS += `dpkg-buildflags --get CFLAGS`
>   LDFLAGS = `dpkg-buildflags --get LDFLAGS`
> while for CPPFLAGS:
>   CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)

Can you send the complete buildlog? I have no problem whatsoever with
building on squeeze.

What is your default /bin/sh ?


Paul


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699165: rsync: debian/rules using ` instead of $(shell

[Adam D. Barratt]

Control: severity -1 normal

On 28.01.2013 12:29, StalkR wrote:

You can ignore the DEBUG lines in config.log, it was me trying to
trace the problem by editing configure.sh.

The issue happened here:
configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get
CFLAGS` -g -O2   conftest.c  >&5
x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory


This means you don't have a sufficiently new version of dpkg-dev 
installed which supports dpkg-buildflags. Whilst rsync's 
build-dependencies should ideally reflect this via a versioned 
dependency relation, failure of a package from testing / unstable to 
build on a stable system is not release critical; I'm therefore 
downgrading the bug.


Regards,

Adam


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#699165: rsync: debian/rules using ` instead of $(shell

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #699165 [rsync] rsync: debian/rules using ` instead of $(shell
Severity set to 'normal' from 'serious'

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 698740

[Debian Bug Tracking System]

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

> tags 698740 + pending
Bug #698740 [gnome-panel] gnome-applets: Force-Quit applet freezes/crashes, 
refuses to recognize mouse clicks or escape key
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#694286: fstrcmp: missing Breaks+Replaces: libfstrcmp-dev (<< 0.4)

[Ansgar Burchardt]

Hi,

I wonder why the man pages for library functions were moved from the
-dev package to the utility package at all?  It seems stange for a
package with the description "[...] provides a command to make fuzzy
string comparisons" to include the library documentation.

Sadly the changelog isn't really informative, though #694939 suggests
the man pages were moved back and forth multiple times...

Ansgar


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699034: libwebkitgtk-1.0-0: midori and GtkLauncher crash after typing a url (cairo-surface.c assertion)

[Alberto]

On Sun, 2013-01-27 at 20:22 -0500, Michael Gilbert wrote:
> >> > Just open midori or GtkLauncher and type in the address bar
> >> > "http://www.facebook.com"; or "http://www.twitter.com"; and press Enter.
> >> > The browser automatically crashes.
> >> > This is the error shown in the terminal
> >> >
> >> > GtkLauncher: 
> >> > /build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-
> >> > surface.c:1591: cairo_surface_set_device_offset: Assertion `status ==
> >> > CAIRO_STATUS_SUCCESS' failed.
> >> > Aborted
> >>
> >> I'm not seeing this at all. Please attach a backtrace which will be
> >> far more informative:
> >> http://wiki.debian.org/bactrace
> >
> > Here it is (after installing libwebkitgtk-1.0-0-dbg).
> 
> This looks more like an issue with cairo itself.  Anyway, the traces
> would be more informative with the gtk and glib dbg packages
> installed.

Here it is after installing
  * libcairo2-dbg
  * libgtk2.0-0-dbg
  * libglib2.0-0-dbg

WARNING: gnome-keyring:: couldn't connect
to: /home/alberto/.cache/keyring-85px7d/pkcs11: No such file or
directory
[Thread 0xa9955b70 (LWP 3282) exited]
[New Thread 0xa9955b70 (LWP 3283)]
GtkLauncher: 
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-surface.c:1591: 
cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' 
failed.

Program received signal SIGABRT, Aborted.
0xb7fe1424 in __kernel_vsyscall ()
(gdb) bt
#0  0xb7fe1424 in __kernel_vsyscall ()
#1  0xb6055941 in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xb6058d72 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#3  0xb604eb58 in __assert_fail ()
from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#4  0xb581c02e in INT_cairo_surface_set_device_offset
(surface=0x82028f8, 
x_offset=3, y_offset=3)

at 
/build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-surface.c:1591
#5  0xb594b4d8 in IA__gdk_window_begin_paint_region (window=0x818aa60, 
region=0x82124c0)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:3009
#6  0xb6601030 in IA__gtk_main_do_event (event=0xbfffef4c)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gtk/gtkmain.c:1608
#7  0xb5950647 in _gdk_window_process_updates_recurse (
window=window@entry=0x818aa60,
expose_region=expose_region@entry=0x82124c0)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5429
#8  0xb59506a7 in _gdk_window_process_updates_recurse (
window=window@entry=0x818a9b0,
expose_region=expose_region@entry=0x82124a0)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5402
#9  0xb59506a7 in _gdk_window_process_updates_recurse (
window=window@entry=0x8079640,
expose_region=expose_region@entry=0x8212460)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5402
#10 0xb5982a43 in _gdk_windowing_window_process_updates_recurse (
window=window@entry=0x8079640, region=region@entry=0x8212460)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/x11/gdkwindow-x11.c:5626
#11 0xb594b0dd in gdk_window_process_updates_internal (window=)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5588
#12 0xb594d46f in IA__gdk_window_process_all_updates ()
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5696
#13 0xb594d4e8 in gdk_window_update_idle (data=0x0)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdkwindow.c:5322
#14 0xb5928584 in gdk_threads_dispatch (data=data@entry=0x812eb70)
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gdk/gdk.c:512
#15 0xb61ee190 in g_idle_dispatch (source=source@entry=0x8211888, 
callback=0xb5928530 , user_data=0x812eb70)
at /build/buildd-glib2.0_2.33.12
+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12
+really2.32.4/./glib/gmain.c:4657
#16 0xb61f06d3 in g_main_dispatch (context=0x807a3f8)
at /build/buildd-glib2.0_2.33.12
+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12
+really2.32.4/./glib/gmain.c:2539
#17 g_main_context_dispatch (context=context@entry=0x807a3f8)
at /build/buildd-glib2.0_2.33.12
+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12
+really2.32.4/./glib/gmain.c:3075
#18 0xb61f0a70 in g_main_context_iterate (context=0x807a3f8, 
block=block@entry=1, dispatch=dispatch@entry=1, 
self=)
at /build/buildd-glib2.0_2.33.12
+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12
+really2.32.4/./glib/gmain.c:3146
#19 0xb61f0ecb in g_main_loop_run (loop=loop@entry=0x81469c8)
at /build/buildd-glib2.0_2.33.12
+really2.32.4-3-i386-Z8T5T2/glib2.0-2.33.12
+really2.32.4/./glib/gmain.c:3340
#20 0xb65ffad0 in IA__gtk_main ()
at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk
+2.0-2.24.10/gtk/gtkmain.c:1256
#21 0x0804a5a7 in main ()

> >> Is there anything unique about your setup?
> >
> > I don't think so.
> > It's a plain updated wheezy i386 with nouveau and XFCE.
> 
> Huge guess her

Bug#693666: NMU diff for dahdi-linux/1:2.6.1+dfsg2-0.1

[Tzafrir Cohen]

On Sun, Jan 27, 2013 at 04:23:05PM +, Ben Hutchings wrote:
> I've uploaded the attached changes to DELAYED/5, and will follow this
> with an upload of dahdi-firmware.

Thanks for your fixes. Applied them in SVN. I don't have the hardware and
thus I'll try to get someone to test the patch.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690799: evnice crashes with a certain PDF file

[Steven Chamberlain]

Hi,

With the 1.12.2-2+deb7u2 packages, this PDF renders okay for me,
including the thumbnail in View->Side Pane, without crashing:

http://www.city.kyoto.lg.jp/kotsu/cmsfiles/contents/019/19770/rosenzurosen.pdf

These are the exact packages I have installed:

http://people.debian.org/~biebl/cairo/amd64/libcairo2_1.12.2-2+deb7u2_amd64.deb
http://people.debian.org/~biebl/cairo/amd64/libcairo-gobject2_1.12.2-2+deb7u2_amd64.deb
http://people.debian.org/~biebl/cairo/amd64/libcairo2-dbg_1.12.2-2+deb7u2_amd64.deb

If it still crashes with those, a new gdb backtrace would be helpful, in
case there is some other problem.

Thank you,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#698740: marked as done (gnome-applets: Force-Quit applet freezes/crashes, refuses to recognize mouse clicks or escape key)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 15:32:39 +
with message-id 
and subject line Bug#698740: fixed in gnome-panel 3.4.2.1-4
has caused the Debian Bug report #698740,
regarding gnome-applets: Force-Quit applet freezes/crashes, refuses to 
recognize mouse clicks or escape key
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.)


-- 
698740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-applets
Version: 3.4.1-3
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

The Force-Quit applet for Gnome 3 creates a serious usability issue.  After
attaching the applet to a panel, attempting to use it will start the applet and
show the overlay window.  The window states that the user should click on the
window they want to quit, or press escape to abort this process.  While the
pointer on the screen will change as part of this, clicking on any window does
NOT close the application.  In fact, it appears that all mouse click events are
simply "eaten" and the mouse effective does nothing from that point forward.
Just as a side note, I also attempted to click the application entry in the
bottom panel, just to be sure there wasn't some hidden UI option that might
work as well.  Pressing Escape to end the process doesn't work either.  I have
tried this option twice, and each time, the only way to "unlock" the session
was to literally abort it by restarting the display manager.  While this does
not affect the system in a critical way, it does affect the user's session, and
I can easily see where it could lead to data loss because the X session was
dumped, in turn causing all programs to be killed with it.  I have also
attempted to see if the program could be killed by switching to a console and
doing a ps aux | grep "myusername", but I have not had much luck in locating
the application - it implies that the applet may be crashing (or simply running
under a different account).

At the very least, the applet should respond to the escape key to allow the
user to exit back to their session, rather than creating a situation where the
mouse pointer is completely ineffective.  While this does not address the
primary function of the applet (to force-quit another application) it at least
functions as a fail-safe in a case where the software could fail, allowing the
user to get out of a potentially bad situation.



-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-applets depends on:
ii  gconf-service3.2.5-1+build1
ii  gconf2   3.2.5-1+build1
ii  gir1.2-gconf-2.0 3.2.5-1+build1
ii  gir1.2-gdkpixbuf-2.0 2.26.1-1
ii  gir1.2-gtk-3.0   3.4.2-5
ii  gir1.2-panelapplet-4.0   3.4.2.1-3
ii  gnome-applets-data   3.4.1-3
ii  gnome-icon-theme 3.4.0-2
ii  gnome-panel  3.4.2.1-3
ii  gvfs 1.12.3-3
ii  libatk1.0-0  2.4.0-2
ii  libc62.13-37
ii  libcairo21.12.2-2
ii  libcpufreq0  008-1
ii  libdbus-1-3  1.6.8-1
ii  libdbus-glib-1-2 0.100-1
ii  libgconf-2-4 3.2.5-1+build1
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.33.12+really2.32.4-3
ii  libgstreamer-plugins-base0.10-0  0.10.36-1
ii  libgstreamer0.10-0   0.10.36-1
ii  libgtk-3-0   3.4.2-5
ii  libgtop2-7   2.28.4-3
ii  libgucharmap-2-90-7  1:3.4.1.1-2.1
ii  libgweather-3-0  3.4.1-1+build1
ii  libnotify4   0.7.5-1
ii  libpanel-applet-4-0  3.4.2.1-3
ii  libpango1.0-01.30.0-1
ii  libpolkit-gobject-1-00.105-3
ii  libupower-glib1  0.9.17-1
ii  libwnck-3-0  3.4.2-1
ii  libx11-6 2:1.5.0-1
ii  libxml2  2.8.0+dfsg1-7
ii  python   2.7.3~rc2-1
ii  python-gi3.2.2-1
ii  upower   0.9.17-1

Versions of packages gnome-applets recommends:
ii  gnome-media   3.4.0-1
ii  gnome-system-monitor  3.4.1-2+b1
i

Bug#681830: debug logs

[Neil Williams]

On Sun, 27 Jan 2013 19:42:47 +
Neil Williams  wrote:

> I made a fresh Wheezy GNOME3 install on a desktop machine (so that the
> display could be disconnected more easily) and had the GDM3 welcome
> screen on display. 

I've now been able to reproduce this on a laptop, as long as it is the
main X session and not a virtualbox or similar, so that access is
preserved to the virtual terminals.

As requested, I've rebuilt gdm3 with the --enable-debug switch
to ./configure and repeated the test with a simple shell script
replacing /usr/bin/Xorg which is just sleep 4 ; exit 1

This should mean that anyone with an old Debian box can test this bug,
it just needs access to the virtual terminals. A simple
# mv /Xorg /usr/bin
# invoke-rc.d gdm3 start
to restore the system.

If the output in /var/log/gdm3 was more useful, it could possibly be
done inside a virtualbox instance, just by replacing /usr/bin/Xorg
with a suitable shell script which exits nonzero.

> I changed the shell script to avoid the 3 second timeout (which makes
> this much more manageable) and gdm3 just keeps respawning using
> gdm-simple-slave, incrementing the --display-id each time.

This behaviour (monitored via htop on a virtual terminal) was
reproduced - I left the test running until the ID was at least 12 or
higher before switching back to the virtual terminal which started gdm3
and killing it with Ctrl-C.

I've attached a tarball of all of the /var/log/gdm3/*greeter* log files
which were the only files in /var/log/gdm3/ which were not zero length
after the tests.

This test machine is an old laptop of mine which was upgraded to Wheezy
this morning and has a working (if clunky) X session normally.

> As mentioned on IRC, there is already some code to handle GdmDisplay
> respawning too fast. See on_display_status_changed() in
> gdm-local-display-factory.c.
> 
> I’m interested in logs with debugging enabled, especially stuff like
> “GdmLocalDisplayFactory: display status changed”.

I get no such matches in the attached logs, I'm afraid. Indeed, I don't
get any output from the logs during the re-spawning itself. Even
watching the files in /var/log/gdm3 with tail -f whilst the problem is
occurring shows no log entries being added during the restart
operations.

I have put commands into the /usr/bin/Xorg shell script replacement and
I can see that output being written to a test file, but no
corresponding entry is made either on the terminal running gdm3 or in
the files in /var/log/gdm3/

I have also tried with and without --fatal-warnings, with no effect.

This bug appears readily reproducible, assuming that
replacing /usr/bin/Xorg temporarily is a suitable mimic of the original
problem reported.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



gdm3-logs.tgz
Description: application/gtar-compressed


pgpn78efOtnFf.pgp
Description: PGP signature

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Ana Guerrero]

> On Mon, Jan 28, 2013 at 13:03:02 +0100, Ana Guerrero wrote:
> 
> > On Mon, Jan 28, 2013 at 12:26:18PM +0100, Julien Cristau wrote:
> > > On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote:
> > > 
> > > > On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> > > > > do you have pointers/details about that ABI incompatibility?  I'm 
> > > > > pretty
> > > > > sure I looked through exported symbols and headers from hdf5 a year 
> > > > > ago,
> > > > > and didn't see anything that would break when building against the
> > > > > serial version and running against openmpi, but I may have missed
> > > > > something.
> > > > 
> > > > I didn't check further than the attached diff, there are mostly symbols
> > > > being added in the openMPI version but also some symbols dissapearing.
> > > > 
> > > OK.  So you didn't get any runtime issues with this?
> > >
> > I haven't tried :) I only checked the symbols diff quickly as said.
> > 
> Alright, closing.

Fine, I can fix my issues locally without too much pain, but other
people could find the rename confusing as I did. Given that going to the
back to the scheme used in Squeeze as I pointed:

> > If you're fully sure we won't run in any runtime problems, then why
> > hdf5 doesn't use the same scheme than in Squeeze?

is *not* a solution at this stage. Could we have this bug as a wishlist
asking to add documentantion about this?
hdf5 needs another update for the bug pointed below and adding a README.Debian
with this information won't hurt.

> > The problem with the upgrades still stands.
> > 
> What problem with the upgrades?

#667599, #667526

Ana


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696066: Fwd: Re: License issues with code in xgks

[Alastair McKinstry]

On 2013-01-27 11:50, Francesco Poli wrote:
> On Sat, 26 Jan 2013 19:31:33 -0500 Luke Faraone wrote:
>
> [...]
>> src/port/misc/config.c:
> [...]
>>>   and cause the whole of any work that you distribute
>>>   or publish, that in whole or in part contains or is a derivative of
>>>   this program or any part thereof, to be licensed at no charge to
>>>   all third parties on terms identical to those here.
> [...]
>> The text "to be licensed at no charge" sounds like it forbids commercial
>> distribution.
> Mmmmh, I am not too convinced.
> It says "licensed at no charge", not "distributed at no charge".
>
> Please compare with clause 2b of the GNU GPL v2:
>
> |   b) You must cause any work that you distribute or publish, that in
> |   whole or in part contains or is derived from the Program or any
> |   part thereof, to be licensed as a whole at no charge to all third
> |   parties under the terms of this License.
>
> It seems to be pretty equivalent...
>
> The license of src/port/misc/config.c looks like a not-too-strong
> copyleft (GPL-incompatible) license. I haven't spotted any
> DFSG-freeness issues.
>
> As far as the other additional violations (pointed out in message #10
> [1]) are concerned, I have nothing to comment...
>
> [1] http://bugs.debian.org/699066#10
>
>
> N.B.: I am not a maintainer of this package and I know nothing about
> it; I am just a debian-legal regular who happened to notice this RC
> bug... I hope my comment helps a little.
>

Below is a thread with the original author of config.c


 Original Message 
Subject:Re: License issues with code in xgks
Date:   Mon, 28 Jan 2013 15:20:31 +0100
From:   Steven Pemberton 
Organisation:   CWI
To: Steven Pemberton , Alastair McKinstry




I should point out that gcc includes enquire with exactly the same
wording, so if anyone has a problem with xgks, then that is the least of
their problems :-)

I believe that this license is fine, because packaging costs (selling a
CD) are not licensing costs. It is still available for free, and so the
conditions of the license are fulfilled. This section was added because
Oracle stole the code once, modified it, added their own copyright
notice, and sold it, and the license wording is trying to prevent that
happening again. However, the wording comes from the very beginning days
of the free-software era.

If you can suggest a wording, I'd be interested to hear.

Best wishes,

Steven

On Mon, 28 Jan 2013 15:13:24 +0100, Alastair McKinstry
 wrote:

I don't believe so. The code is the xgks repository at: 
http://sourceforge.net/projects/xgks
and it was only noticed this weekend that your license on the file
did not match the
UCAR/IBM license at the top of the tree.

We are preparing the next release of Debian, and there are
additional people checking all the licenses
of new packages. In this release I have added the 'xgks' and
'ferret' packages which are available in the
current "unstable" Debian release (which is already the base for
Ubuntu, Mint, etc. releases).

If you are amenable to a change, I will include either a changed
comment by yourself,
or the new version of enquire.c (thanks for the pointer; I hadn't
seen it).
I will also document your copyright and license terms in the
debian/copyright file;
(In Debian for each package we document all copyright /license
information in
/usr/share/doc//copyright (in addition to including other
files requested by
the copyright owner).

As this is in the Debian  freeze period, no substantial changes will
be allowed by the release managers.
In this release my options are tied to (1) the documentation
described above, or
(2) pulling the packages from release. I'll investigate including
the new enquire.c for the next
release.

best regards
Alastair


On 2013-01-28 13:53, Steven Pemberton wrote:
> By the way, did you modify config.c? Because the section you are troubled 
about is only in
relation to modified copies.
>
> And did you know that (if it is called config.c) you are using a
very old version?
> The most up-to-date version is here:
http://www.cwi.nl/~steven/enquire.html
>
> Best wishes,
>
> Steven
>
>
> On Mon, 28 Jan 2013 12:55:02 +0100, Alastair McKinstry
 wrote:
>
>> Dear Steven,
>>
>> I am the maintainer in Debian for "xgks" and other meteorology
software.
>> Included in this is the file src/port/misc/config.c that you wrote.
>>
>> The overall license of "xgks" is included below, but it appears to
>> conflict with the
>> "SMALL PRINT" you included in you file, which was only just noticed:
>>
>> The difficulty is the "licensed at no charge" bit. (For a
discussion on
>> this see the DFSG FAQ
>> http://people.debian.org/~bap/dfsg-faq). It bans people selling
copies
>> of Debian for-pr

Bug#699155: hdf5: dependencies can be satisfied interchangeably with libraries providing different ABIs

[Julien Cristau]

On Mon, Jan 28, 2013 at 16:55:47 +0100, Ana Guerrero wrote:

> > On Mon, Jan 28, 2013 at 13:03:02 +0100, Ana Guerrero wrote:
> > 
> > > On Mon, Jan 28, 2013 at 12:26:18PM +0100, Julien Cristau wrote:
> > > > On Mon, Jan 28, 2013 at 12:20:36 +0100, Ana Guerrero wrote:
> > > > 
> > > > > On Mon, Jan 28, 2013 at 11:37:31AM +0100, Julien Cristau wrote:
> > > > > > do you have pointers/details about that ABI incompatibility?  I'm 
> > > > > > pretty
> > > > > > sure I looked through exported symbols and headers from hdf5 a year 
> > > > > > ago,
> > > > > > and didn't see anything that would break when building against the
> > > > > > serial version and running against openmpi, but I may have missed
> > > > > > something.
> > > > > 
> > > > > I didn't check further than the attached diff, there are mostly 
> > > > > symbols
> > > > > being added in the openMPI version but also some symbols dissapearing.
> > > > > 
> > > > OK.  So you didn't get any runtime issues with this?
> > > >
> > > I haven't tried :) I only checked the symbols diff quickly as said.
> > > 
> > Alright, closing.
> 
> Fine, I can fix my issues locally without too much pain, but other

Which issues?

> people could find the rename confusing as I did. Given that going to the
> back to the scheme used in Squeeze as I pointed:
> 
> > > If you're fully sure we won't run in any runtime problems, then why
> > > hdf5 doesn't use the same scheme than in Squeeze?
> 
> is *not* a solution at this stage. Could we have this bug as a wishlist
> asking to add documentantion about this?
> hdf5 needs another update for the bug pointed below and adding a README.Debian
> with this information won't hurt.
> 
I don't know what you find confusing...  I also don't know what the
scheme was in squeeze, or why it was changed, I only got involved after
the fact to make the current scheme work after it was already mostly
switched.

> > > The problem with the upgrades still stands.
> > > 
> > What problem with the upgrades?
> 
> #667599, #667526
> 
OK.

Cheers,
Julien
-- 
Julien Cristau  
Logilab http://www.logilab.fr/
Informatique scientifique & gestion de connaissances


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699177: Wrong sorting in pathname expansion

[Alexander Gerasiov]

Package: dash
Version: 0.5.7-3
Severity: serious

According to IEEE Std 1003.1-1996, IEEE Std 1003.2-1992, and the Base
Specifications of The Open Group Single UNIX Specification, Version 2.
Shell and Utilities volume (XCU).
2.13.3 Patterns Used for Filename Expansion

If the pattern matches any existing filenames or pathnames, the pattern
shall be replaced with those filenames and pathnames, sorted according to the
collating sequence in effect in the current locale.

Most shells follow this standard in _sorting_ part, but dash doesn't.
In my locale a < A, but dash doesn't think so.

$ mkdir /tmp/a
$ cd /tmp/a
$ touch a aa aaa A aA Aa AA
[zsh]$ echo * 
a A aa aA Aa AA aaa
[bash]$ echo *
a A aa aA Aa AA aaa
[dash]$ echo *
A AA Aa a aA aa aaa

I marked this bug as serious because it breaks POSIX in really core package.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (680, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/dash

Versions of packages dash depends on:
ii  debianutils  4.3.2
ii  dpkg 1.16.9
ii  libc62.13-37

dash recommends no packages.

dash suggests no packages.

-- debconf information:
* dash/sh: true


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Bug#698916 marked as pending

[Debian Bug Tracking System]

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

> tag 698916 pending
Bug #698916 [wordpress] wordpress: pingback port scanning issue fixed in 3.5.1
Bug #698926 [wordpress] wordpress: pingback port scanning issue fixed in 3.5.1
Bug #698928 [wordpress] wordpress: pingback port scanning issue fixed in 3.5.1
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#698916: marked as pending

[Raphaël Hertzog]

tag 698916 pending
thanks

Hello,

Bug #698916 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/wordpress.git;a=commitdiff;h=b632282

---
commit b6322823227e51fc2dbdbe509ba1777db565cbd4
Author: Raphaël Hertzog 
Date:   Mon Jan 28 17:35:57 2013 +0100

Changelog for new upstream release

diff --git a/debian/changelog b/debian/changelog
index 1326331..837e51b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+wordpress (3.5.1+dfsg-1) unstable; urgency=low
+
+  * New upstream maintenance and security release. Closes: #698916
+
+ -- Raphaël Hertzog   Mon, 28 Jan 2013 17:15:27 +0100
+
 wordpress (3.5+dfsg-1) unstable; urgency=low
 
   * New upstream release.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#698926: marked as done (wordpress: pingback port scanning issue fixed in 3.5.1)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 17:03:02 +
with message-id 
and subject line Bug#698916: fixed in wordpress 3.5.1+dfsg-1
has caused the Debian Bug report #698916,
regarding wordpress: pingback port scanning issue fixed in 3.5.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.)


-- 
698916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 3.5+dfsg-1
Severity: important

http://wordpress.org/news/2013/01/wordpress-3-5-1/

- A server-side request forgery vulnerability and remote port scanning using 
pingbacks. This vulnerability, which could potentially be used to expose 
information and compromise a site, affects all previous WordPress versions. 
This was fixed by the WordPress security team. We’d like to thank security 
researchers Gennady Kovshenin and Ryan Dewhurst for reviewing our work.
- Two instances of cross-site scripting via shortcodes and post content. These 
issues were discovered by Jon Cave of the WordPress security team.
- A cross-site scripting vulnerability in the external library Plupload. Thanks 
to the Moxiecode team for working with us on this, and for releasing Plupload 
1.5.5 to address this issue.

--
Henri Salo
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 3.5.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
wordpress, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated wordpress 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Jan 2013 17:15:27 +0100
Source: wordpress
Binary: wordpress wordpress-l10n
Architecture: source all
Version: 3.5.1+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Giuseppe Iuculano 
Changed-By: Raphaël Hertzog 
Description: 
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
Closes: 698916
Changes: 
 wordpress (3.5.1+dfsg-1) unstable; urgency=low
 .
   * New upstream maintenance and security release. Closes: #698916
Checksums-Sha1: 
 5f0996176d0cc7af9b26efc7fdc8df02d138d6f6 2332 wordpress_3.5.1+dfsg-1.dsc
 9459f34d9d67d2f519419f5c488dd124da5f56f3 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 eaac3330740fddd8071171c2211623dc3ed78b3d 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e04b2b1bea241f12fc2ecb3c109927c079d20e48 4759492 wordpress_3.5.1+dfsg-1_all.deb
 4a129892b16eee675fbcb2b2cf969be7f376e3d5 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Checksums-Sha256: 
 69f3b54fd08343cf6e3bb75bb7dc5f637c7c9ead2174a19300b928cd2ee8e86b 2332 
wordpress_3.5.1+dfsg-1.dsc
 6a898ff66e915847c65c65b3421834b77284f80c47b410fc268db910025dc404 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 ba7c3112172470a1b47d5fc3f8c3793c7daf6d105030913fc05da1787df82d16 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e7dfd7ff24c9c92f5a70b6cb90ce8638592460f68088b70d0b9df07bd8372203 4759492 
wordpress_3.5.1+dfsg-1_all.deb
 5d8fac3d64dda64715d95f32f2fd4619cd7d9139b9d890eea7537eb68007e52e 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Files: 
 53a2f5f1d3811b889c30b2ee494b365f 2332 web optional wordpress_3.5.1+dfsg-1.dsc
 c8e8f13bd9a8961541433818e36ea482 4284028 web optional 
wordpress_3.5.1+dfsg.orig.tar.xz
 ce872b65eb5dec380775c06e7c600219 3652744 web optional 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 f23d91e480546011f69aa8255fd77f4e 4759492 web optional 
wordpress_3.5.1+dfsg-1_all.deb
 e0ceab8b16b7d2f1aa7e8cd393fe3081 5539524 localization optional 
wordpress-l10n_3.5.1+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Signed by Raphael Hertzog

iQIcBAEBCAAGBQJRBquzAAoJEOYZBF3yrHKakFsP/3lkciqdXA3n4tyBcHWnwhsg
HekplQfx/ofa/E8HlCdZJKHUyETQiNUP7kW4jwvefaVs8U4EW4Pp7Gy/AAxuxB2M
DKIjuEVcEBM2X+t+wRA6LYJdqmCd2ii2MwCGXx2WfP4ultEJnPdTa35cjbWDCvd4
H7/vphoQb/d/cH2Lv5EVeqW+VwX9modODHn8ots032FjCQ5Q6u06vwWlfBYHg+fh
DJu8/I3c/4S/b/L8CVUuSnvek1kyoDRGb+hVgT96u14J1knAID4FpLMQebYqgLJN
Wb2Wc9fn0tUMhMGn8oMJAuVSBDGMoExlXE/+xYNn5RmYBIrXUeL7VG4mo1fxxL1e
+xk7aGKfcwUK9xYcp76AVa4dp5GRmklm872HZjh9ZVCs+qzYEOjs0UHrxlYRg5by
X7QMlLjb

Bug#698916: marked as done (wordpress: pingback port scanning issue fixed in 3.5.1)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 17:03:02 +
with message-id 
and subject line Bug#698916: fixed in wordpress 3.5.1+dfsg-1
has caused the Debian Bug report #698916,
regarding wordpress: pingback port scanning issue fixed in 3.5.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.)


-- 
698916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 3.5+dfsg-1
Severity: important

http://wordpress.org/news/2013/01/wordpress-3-5-1/

- A server-side request forgery vulnerability and remote port scanning using 
pingbacks. This vulnerability, which could potentially be used to expose 
information and compromise a site, affects all previous WordPress versions. 
This was fixed by the WordPress security team. We’d like to thank security 
researchers Gennady Kovshenin and Ryan Dewhurst for reviewing our work.
- Two instances of cross-site scripting via shortcodes and post content. These 
issues were discovered by Jon Cave of the WordPress security team.
- A cross-site scripting vulnerability in the external library Plupload. Thanks 
to the Moxiecode team for working with us on this, and for releasing Plupload 
1.5.5 to address this issue.

--
Henri Salo
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 3.5.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
wordpress, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated wordpress 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Jan 2013 17:15:27 +0100
Source: wordpress
Binary: wordpress wordpress-l10n
Architecture: source all
Version: 3.5.1+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Giuseppe Iuculano 
Changed-By: Raphaël Hertzog 
Description: 
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
Closes: 698916
Changes: 
 wordpress (3.5.1+dfsg-1) unstable; urgency=low
 .
   * New upstream maintenance and security release. Closes: #698916
Checksums-Sha1: 
 5f0996176d0cc7af9b26efc7fdc8df02d138d6f6 2332 wordpress_3.5.1+dfsg-1.dsc
 9459f34d9d67d2f519419f5c488dd124da5f56f3 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 eaac3330740fddd8071171c2211623dc3ed78b3d 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e04b2b1bea241f12fc2ecb3c109927c079d20e48 4759492 wordpress_3.5.1+dfsg-1_all.deb
 4a129892b16eee675fbcb2b2cf969be7f376e3d5 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Checksums-Sha256: 
 69f3b54fd08343cf6e3bb75bb7dc5f637c7c9ead2174a19300b928cd2ee8e86b 2332 
wordpress_3.5.1+dfsg-1.dsc
 6a898ff66e915847c65c65b3421834b77284f80c47b410fc268db910025dc404 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 ba7c3112172470a1b47d5fc3f8c3793c7daf6d105030913fc05da1787df82d16 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e7dfd7ff24c9c92f5a70b6cb90ce8638592460f68088b70d0b9df07bd8372203 4759492 
wordpress_3.5.1+dfsg-1_all.deb
 5d8fac3d64dda64715d95f32f2fd4619cd7d9139b9d890eea7537eb68007e52e 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Files: 
 53a2f5f1d3811b889c30b2ee494b365f 2332 web optional wordpress_3.5.1+dfsg-1.dsc
 c8e8f13bd9a8961541433818e36ea482 4284028 web optional 
wordpress_3.5.1+dfsg.orig.tar.xz
 ce872b65eb5dec380775c06e7c600219 3652744 web optional 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 f23d91e480546011f69aa8255fd77f4e 4759492 web optional 
wordpress_3.5.1+dfsg-1_all.deb
 e0ceab8b16b7d2f1aa7e8cd393fe3081 5539524 localization optional 
wordpress-l10n_3.5.1+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Signed by Raphael Hertzog

iQIcBAEBCAAGBQJRBquzAAoJEOYZBF3yrHKakFsP/3lkciqdXA3n4tyBcHWnwhsg
HekplQfx/ofa/E8HlCdZJKHUyETQiNUP7kW4jwvefaVs8U4EW4Pp7Gy/AAxuxB2M
DKIjuEVcEBM2X+t+wRA6LYJdqmCd2ii2MwCGXx2WfP4ultEJnPdTa35cjbWDCvd4
H7/vphoQb/d/cH2Lv5EVeqW+VwX9modODHn8ots032FjCQ5Q6u06vwWlfBYHg+fh
DJu8/I3c/4S/b/L8CVUuSnvek1kyoDRGb+hVgT96u14J1knAID4FpLMQebYqgLJN
Wb2Wc9fn0tUMhMGn8oMJAuVSBDGMoExlXE/+xYNn5RmYBIrXUeL7VG4mo1fxxL1e
+xk7aGKfcwUK9xYcp76AVa4dp5GRmklm872HZjh9ZVCs+qzYEOjs0UHrxlYRg5by
X7QMlLjb

Bug#698928: marked as done (wordpress: pingback port scanning issue fixed in 3.5.1)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 17:03:02 +
with message-id 
and subject line Bug#698916: fixed in wordpress 3.5.1+dfsg-1
has caused the Debian Bug report #698916,
regarding wordpress: pingback port scanning issue fixed in 3.5.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.)


-- 
698916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 3.5+dfsg-1
Severity: important

http://wordpress.org/news/2013/01/wordpress-3-5-1/

- A server-side request forgery vulnerability and remote port scanning using 
pingbacks. This vulnerability, which could potentially be used to expose 
information and compromise a site, affects all previous WordPress versions. 
This was fixed by the WordPress security team. We’d like to thank security 
researchers Gennady Kovshenin and Ryan Dewhurst for reviewing our work.
- Two instances of cross-site scripting via shortcodes and post content. These 
issues were discovered by Jon Cave of the WordPress security team.
- A cross-site scripting vulnerability in the external library Plupload. Thanks 
to the Moxiecode team for working with us on this, and for releasing Plupload 
1.5.5 to address this issue.

--
Henri Salo
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 3.5.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
wordpress, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated wordpress 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 28 Jan 2013 17:15:27 +0100
Source: wordpress
Binary: wordpress wordpress-l10n
Architecture: source all
Version: 3.5.1+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Giuseppe Iuculano 
Changed-By: Raphaël Hertzog 
Description: 
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
Closes: 698916
Changes: 
 wordpress (3.5.1+dfsg-1) unstable; urgency=low
 .
   * New upstream maintenance and security release. Closes: #698916
Checksums-Sha1: 
 5f0996176d0cc7af9b26efc7fdc8df02d138d6f6 2332 wordpress_3.5.1+dfsg-1.dsc
 9459f34d9d67d2f519419f5c488dd124da5f56f3 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 eaac3330740fddd8071171c2211623dc3ed78b3d 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e04b2b1bea241f12fc2ecb3c109927c079d20e48 4759492 wordpress_3.5.1+dfsg-1_all.deb
 4a129892b16eee675fbcb2b2cf969be7f376e3d5 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Checksums-Sha256: 
 69f3b54fd08343cf6e3bb75bb7dc5f637c7c9ead2174a19300b928cd2ee8e86b 2332 
wordpress_3.5.1+dfsg-1.dsc
 6a898ff66e915847c65c65b3421834b77284f80c47b410fc268db910025dc404 4284028 
wordpress_3.5.1+dfsg.orig.tar.xz
 ba7c3112172470a1b47d5fc3f8c3793c7daf6d105030913fc05da1787df82d16 3652744 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 e7dfd7ff24c9c92f5a70b6cb90ce8638592460f68088b70d0b9df07bd8372203 4759492 
wordpress_3.5.1+dfsg-1_all.deb
 5d8fac3d64dda64715d95f32f2fd4619cd7d9139b9d890eea7537eb68007e52e 5539524 
wordpress-l10n_3.5.1+dfsg-1_all.deb
Files: 
 53a2f5f1d3811b889c30b2ee494b365f 2332 web optional wordpress_3.5.1+dfsg-1.dsc
 c8e8f13bd9a8961541433818e36ea482 4284028 web optional 
wordpress_3.5.1+dfsg.orig.tar.xz
 ce872b65eb5dec380775c06e7c600219 3652744 web optional 
wordpress_3.5.1+dfsg-1.debian.tar.xz
 f23d91e480546011f69aa8255fd77f4e 4759492 web optional 
wordpress_3.5.1+dfsg-1_all.deb
 e0ceab8b16b7d2f1aa7e8cd393fe3081 5539524 localization optional 
wordpress-l10n_3.5.1+dfsg-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Signed by Raphael Hertzog

iQIcBAEBCAAGBQJRBquzAAoJEOYZBF3yrHKakFsP/3lkciqdXA3n4tyBcHWnwhsg
HekplQfx/ofa/E8HlCdZJKHUyETQiNUP7kW4jwvefaVs8U4EW4Pp7Gy/AAxuxB2M
DKIjuEVcEBM2X+t+wRA6LYJdqmCd2ii2MwCGXx2WfP4ultEJnPdTa35cjbWDCvd4
H7/vphoQb/d/cH2Lv5EVeqW+VwX9modODHn8ots032FjCQ5Q6u06vwWlfBYHg+fh
DJu8/I3c/4S/b/L8CVUuSnvek1kyoDRGb+hVgT96u14J1knAID4FpLMQebYqgLJN
Wb2Wc9fn0tUMhMGn8oMJAuVSBDGMoExlXE/+xYNn5RmYBIrXUeL7VG4mo1fxxL1e
+xk7aGKfcwUK9xYcp76AVa4dp5GRmklm872HZjh9ZVCs+qzYEOjs0UHrxlYRg5by
X7QMlLjb

Bug#690092: unreproproducable

[Anton Gladky]

tags 690092 + unreproproducable
severity 690092 normal
thanks

The package builds fine in both sid and wheezy clean environment.
I am reducing the severity,

Thanks,

Anton


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): unreproproducable

[Debian Bug Tracking System]

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

> tags 690092 + unreproproducable
Unknown tag/s: unreproproducable.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid 
help security upstream pending sarge sarge-ignore experimental d-i confirmed 
ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore lenny 
lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore.

Bug #690092 [scli] scli: FTBFS due to glib changes
Requested to add no tags; doing nothing.
> severity 690092 normal
Bug #690092 [scli] scli: FTBFS due to glib changes
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699188: CVE-2013-0172

[Moritz Muehlenhoff]

Package: samba4
Severity: grave
Tags: security

Hi,
as discussed on IRC last week. I'm filing a bug for proper tracking:
https://lists.samba.org/archive/samba-technical/2013-January/089911.html

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

debian-bugs-rc@lists.debian.org

[Debian Bug Tracking System]

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

> forwarded 698910 http://www.zoneminder.com/forums/viewtopic.php?f=29&t=20771
Bug #698910 [src:zoneminder] zoneminder: arbitrary command execution 
vulnerability
Set Bug forwarded-to-address to 
'http://www.zoneminder.com/forums/viewtopic.php?f=29&t=20771'.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#659994: [regression] icedove: symbol lookup error: [...]/libdbusservice.so: undefined symbol: NS_Alloc

[Carsten Schoenert]

Version: 10.0.3-2

No feedback from the reporters so assuming version 10.x in wheezy is not
affected.

Regards
Carsten


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696837: marked as done (Missing Depends on python-libtorrent, fails to start)

[Cristian Greco]

Hi all!

First of all, I apologize for not taking care of the huge amount of
bugs with deluge lately.

I tend to disagree with the proposed patch. The current situation of
deluge dependencies is *exactly* as it was intended: the reason is
clearly (IMHO) stated in packages description; and it is the result
of a discussion which also involved upstream authors and led to the
kind of fragmentation of dependencies we all see.

The patch proposed to fix this bug is a complete revert of the change at
[0], which in turn was discussed and agreed with upstream in order to
fix the bug at [1] and to make it clear the client-server model of
deluge and the role of its UIs packages.

Having said that, I'd prefer to leave package' dependencies untouched,
and instead ask you for suggestions on how to improve their descriptions
and make it clear to the final user why and when she or he should
choose to install `deluge` rather than `deluge-gtk` (maybe the name of
the package is also unfortunate here and helps causing confusion).

[0] 
http://anonscm.debian.org/gitweb/?p=collab-maint/deluge.git;a=commitdiff;h=c9647e5e55e3fa89b4b4073708b291c3c08a23f9
[1] https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/672069


Thanks,
--
Cristian Greco
GPG key ID: 0xCF4D32E4


signature.asc
Description: PGP signature

Bug#696837: marked as done (Missing Depends on python-libtorrent, fails to start)

[Andrey Rahmatullin]

On Mon, Jan 28, 2013 at 08:21:09PM +0100, Cristian Greco wrote:
> First of all, I apologize for not taking care of the huge amount of
> bugs with deluge lately.
> 
> I tend to disagree with the proposed patch. The current situation of
> deluge dependencies is *exactly* as it was intended: the reason is
> clearly (IMHO) stated in packages description; and it is the result
> of a discussion which also involved upstream authors and led to the
> kind of fragmentation of dependencies we all see.
> 
> The patch proposed to fix this bug is a complete revert of the change at
> [0], which in turn was discussed and agreed with upstream in order to
> fix the bug at [1] and to make it clear the client-server model of
> deluge and the role of its UIs packages.
> 
> Having said that, I'd prefer to leave package' dependencies untouched,
> and instead ask you for suggestions on how to improve their descriptions
> and make it clear to the final user why and when she or he should
> choose to install `deluge` rather than `deluge-gtk` (maybe the name of
> the package is also unfortunate here and helps causing confusion).
> 
> [0] 
> http://anonscm.debian.org/gitweb/?p=collab-maint/deluge.git;a=commitdiff;h=c9647e5e55e3fa89b4b4073708b291c3c08a23f9
> [1] https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/672069
There is only one change needed: if an user installs just deluge-gtk they
shouldn't get the classic mode enabled by default.
I'm not sure that this is possible at all, though.

-- 
WBR, wRAR


signature.asc
Description: Digital signature

Bug#698631: typo3-src: diff for NMU version 4.5.19+dfsg1-4.1

[gregor herrmann]

tags 698631 + patch
tags 698631 + pending
thanks

Dear maintainer,

I've prepared an NMU for typo3-src (versioned as 4.5.19+dfsg1-4.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Steppenwolf: Forty Days & Forty Nights
diff -Nru typo3-src-4.5.19+dfsg1/debian/changelog typo3-src-4.5.19+dfsg1/debian/changelog
--- typo3-src-4.5.19+dfsg1/debian/changelog	2012-11-13 11:25:03.0 +0100
+++ typo3-src-4.5.19+dfsg1/debian/changelog	2013-01-28 21:23:19.0 +0100
@@ -1,3 +1,13 @@
+typo3-src (4.5.19+dfsg1-4.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "copyright file missing after upgrade (policy 12.5)":
+replace directory with symlink in typo3.postinst.
+Thanks Andreas Beckmann for the bug report and the template for the fix.
+(Closes: #698631)
+
+ -- gregor herrmann   Mon, 28 Jan 2013 21:23:03 +0100
+
 typo3-src (4.5.19+dfsg1-4) unstable; urgency=medium
 
   * Added patch for regression introduced by TYPO3-SA-2012-5-patch.
diff -Nru typo3-src-4.5.19+dfsg1/debian/typo3.postinst typo3-src-4.5.19+dfsg1/debian/typo3.postinst
--- typo3-src-4.5.19+dfsg1/debian/typo3.postinst	1970-01-01 01:00:00.0 +0100
+++ typo3-src-4.5.19+dfsg1/debian/typo3.postinst	2013-01-28 21:18:11.0 +0100
@@ -0,0 +1,14 @@
+#!/bin/sh
+
+set -e
+
+DOCDIR=/usr/share/doc/typo3
+DOCLINK=typo3-src-4.5
+
+if [ -d $DOCDIR ] && [ ! -L $DOCDIR ] ; then
+	if rmdir $DOCDIR 2>/dev/null; then
+		ln -sf $DOCLINK $DOCDIR
+	fi
+fi
+
+#DEBHELPER#


signature.asc
Description: Digital signature

Processed: typo3-src: diff for NMU version 4.5.19+dfsg1-4.1

[Debian Bug Tracking System]

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

> tags 698631 + patch
Bug #698631 [typo3] typo3: copyright file missing after upgrade (policy 12.5)
Added tag(s) patch.
> tags 698631 + pending
Bug #698631 [typo3] typo3: copyright file missing after upgrade (policy 12.5)
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#658896: LDAP, GnuTLS/libgcrypt

[Carlos Alberto Lopez Perez]

On 25/01/13 03:00, Howard Chu wrote:
>> Hi!
>>
>>
>> I have been digging on this issue and I found the ultimate cause of this
>> problem.
>>
>>
>> When sudo/su/passwd/ on
>> a system configured with PAM/LDAPs it chains into libldap, which uses
>> GnuTLS/libgcrypt to manage the TLS channel.
>>
>>
>> The problem is that when OpenLDAP calls gnutls_global_init(), this
>> function does nothing because OpenLDAP had previously already
>> initialized libgcrypt at some point on the stack (probably by mistake).
> 
> For the record, there is no mistake in OpenLDAP. And also for the
> record, we on the OpenLDAP Project warned you guys multiple times that
> GnuTLS/libgcrypt are broken by design, and should not be used. (E.g. as
> I noted here
> https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/62)
> 
> The libgcrypt documentation states in section 2.5 that you *must* set
> the thread callbacks before calling *any* other libgcrypt functions.
> libldap's code does that. It's not our fault that libgcrypt's design is
> so broken that even when you use it as documented it doesn't work. We've
> been telling you for *years* that GnuTLS is broken by design.
> 

I agree with you.

But, keep in mind that GnuTLS not longer supports libgcrypt (they even
removed the code from their repository). They now only support libnettle.

So there is no point at all in trying to fix GnuTLS now.

The upstream OpenLDAP project should probably have to remove support for
libgcrypt from their code.

And about the idea of patching the GnuTLS version that Debian Wheezy
ships (with libgcrypt support) I'm afraid that this could break some
unrelated package that relies in this broken design of GnuTLS/libgcrypt.

And for Wheezy+1 GnuTLS will have to migrate to the new version (with
nettle), so IMHO there is no point in fixing it now.

On the other hand, I feel like this small patch for OpenLDAP is the less
intrusive approach to make things just work for Wheezy.


Regards!




signature.asc
Description: OpenPGP digital signature

Bug#699193: libahven3-dev: fails to upgrade from 'squeeze' - trying to overwrite /usr/lib/libahven.a

[Andreas Beckmann]

Package: libahven3-dev
Version: 2.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails
because it tries to overwrite files that are owned by other packages
without declaring a Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This problem is exposed during the upgrade of the 'EXPOSER'
package, not by upgrading only the buggy package itself.
In order to have piuparts automatically track this problem, I'll mark
this bug as Affects/Found in the exposing package(s), too.

>From the attached log (scroll to the bottom...):

  Selecting previously deselected package libahven3-dev.
  Unpacking libahven3-dev (from .../libahven3-dev_2.1-3_amd64.deb) ...
  dpkg: error processing /var/cache/apt/archives/libahven3-dev_2.1-3_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/libahven.a', which is also in package 
libahven1-dev 1.7-2


Package: libahven3-dev
Source: ahven
Version: 2.1-3
Replaces: libahven2-dev
Depends: libahven21.0 (= 2.1-3), gnat, gnat-4.6
Conflicts: libahven2-dev


You should probably add a
   Conflicts/Replaces: libahven1-dev
too.


cheers,

Andreas


ahven-dbg_2.1-3.log.gz
Description: GNU Zip compressed data

Bug#698231: marked as done (memcached: CVE-2013-0179)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 21:02:29 +
with message-id 
and subject line Bug#698231: fixed in memcached 1.4.13-0.2
has caused the Debian Bug report #698231,
regarding memcached: CVE-2013-0179
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.)


-- 
698231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: memcached
Severity: grave
Tags: security
Justification: user security hole

A minor security issue was found in memcached:
http://www.openwall.com/lists/oss-security/2013/01/14/6

This doesn't warrant a DSA, but you could fix it through a point update.

For Wheezy a minimal fix should be made instead of updating to a new
upstream release.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: memcached
Source-Version: 1.4.13-0.2

We believe that the bug you reported is fixed in the latest version of
memcached, 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 698...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated memcached 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Jan 2013 21:22:09 +0100
Source: memcached
Binary: memcached
Architecture: source amd64
Version: 1.4.13-0.2
Distribution: unstable
Urgency: low
Maintainer: David Martínez Moreno 
Changed-By: Salvatore Bonaccorso 
Description: 
 memcached  - A high-performance memory object caching system
Closes: 698231
Changes: 
 memcached (1.4.13-0.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Add 05_fix-buffer-overrun_when_logging_keys.patch patch
 [SECURITY] CVE-2013-0179: DoS due to buffer overrun when printing out keys
 to be deleted in verbose mode. (Closes: #698231).
Checksums-Sha1: 
 ef93dd68447305b95c54fa73df9f248ae06717e3 1528 memcached_1.4.13-0.2.dsc
 082849bf141ac23fc5dfd73acd1b18bd7acd4e88 329382 memcached_1.4.13-0.2.tar.gz
 121bf718c3329b6428b0f2e23e9bb7a572968fc9 86682 memcached_1.4.13-0.2_amd64.deb
Checksums-Sha256: 
 5ec3bf230b941cdda277c772edc2acb6121d63ee52b9eb2f934503871d7e67bc 1528 
memcached_1.4.13-0.2.dsc
 866818e7889591487012748ec978452460f92afbe14a5902d893a093279ce8a0 329382 
memcached_1.4.13-0.2.tar.gz
 efe3092e4c597b859c057b26e5a7214cfcae3f743809ec0f4c628394718bb8ae 86682 
memcached_1.4.13-0.2_amd64.deb
Files: 
 f3d6b9893f697dc36e3ff79fb8ca5cc0 1528 web optional memcached_1.4.13-0.2.dsc
 c5436366b8fba7a3f7b2e3f6683ae2b7 329382 web optional 
memcached_1.4.13-0.2.tar.gz
 3f3abe02054b0b3bf7a186be489a6812 86682 web optional 
memcached_1.4.13-0.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJRAEbUAAoJEHidbwV/2GP+q2cQANKtVZ3zFmQRmY9t0DkFHcbU
xo+z9cEG+WW68CxyZIxXsI3nAUMrwGLOTR8CEPnr8MvXMAbiVpw9Nf7kZxarw+PO
iTSLQPKzOM4ny21BNvrRzGbpaP8pJr8853khGd9GFUDiUh91MRr16yZtgX3hkkCp
hXjZCoMEp8fupehSiQga1c9KuVaEb3z3K3RqafJ/mlYKgOpCVP+EDjo7BdOe/oQ/
yABYNhwP/V9FjahmVy8uIz1Md1T8Log0pT15louMhumjBRy2Orkyn6VobOsXe6Ze
Bi+lOmcBpQR5GWv28E6W1zS5Dolsb5GGmnQoM06EIIwH7pqPT2fsQUhDwzxAY9W2
LsLiQjmzYtIb2qcOOjA4v7BQgkk+0YipZI/86+GXroab9z7mKpIRVTO2YsTgGDhL
AZQBbHMwWORXE/O2N2cEr5ZdDw/NMyamsZ9aqjzpePTOim8OuJGlck7kkCK7GgId
bHdduV5HsTsmeT6sdoUhdEMHYhijXyzgE7yb4BCmt3+2pjfR3lJm0jmycClV86Kp
jRT6QOQo31z7fJcT6S+tTnLj2JJ0/x+KDC08MbRma2OCd8hCmxbV+78K7Uy1XRxL
Zu7ElcaoWfzG4sKfAnUSSf9pT2sZsfS7XpoAMhA6vhJHIYvGYYs7iZGhEQOf5H7I
ptHTGcjIc0f/g6RAS4R6
=72gO
-END PGP SIGNATURE End Message ---

Processed: libpcscada2-dev: fails to upgrade from 'squeeze' - trying to overwrite /usr/lib/ada/adalib/pcscada/pcsc-scard-conversion.ali

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + pcscada-dbg
Bug #699194 [libpcscada2-dev] libpcscada2-dev: fails to upgrade from 'squeeze' 
- trying to overwrite /usr/lib/ada/adalib/pcscada/pcsc-scard-conversion.ali
Added indication that 699194 affects pcscada-dbg

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699194: libpcscada2-dev: fails to upgrade from 'squeeze' - trying to overwrite /usr/lib/ada/adalib/pcscada/pcsc-scard-conversion.ali

[Andreas Beckmann]

Package: libpcscada2-dev
Version: 0.7.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + pcscada-dbg

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails
because it tries to overwrite files that are owned by other packages
without declaring a Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This problem is exposed during the upgrade of the 'pcscada-dbg'
package, not by upgrading only the buggy package itself.
In order to have piuparts automatically track this problem, I'll mark
this bug as Affects/Found in the exposing package(s), too.

>From the attached log (scroll to the bottom...):

  Selecting previously deselected package libpcscada2-dev.
  Unpacking libpcscada2-dev (from .../libpcscada2-dev_0.7.1-3_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/libpcscada2-dev_0.7.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/ada/adalib/pcscada/pcsc-scard-conversion.ali', 
which is also in package libpcscada1-dev 0.6-2

Package: libpcscada2-dev
Source: pcscada
Version: 0.7.1-3
Depends: libpcscada0.7.1 (= 0.7.1-3), libpcsclite-dev (>= 1.4.0), gnat, gnat-4.6

You should probably add
  Breaks/Replaces: libpcscada1-dev
to ensure the obsolete package gets removed during the upgrade.


cheers,

Andreas


pcscada-dbg_0.7.1-3.log.gz
Description: GNU Zip compressed data

Processed: libpolyorb2-dev: fails to upgrade from 'squeeze' - trying to overwrite /usr/bin/iac

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libpolyorb-dbg
Bug #699197 [libpolyorb2-dev] libpolyorb2-dev: fails to upgrade from 'squeeze' 
- trying to overwrite /usr/bin/iac
Added indication that 699197 affects libpolyorb-dbg

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699197: libpolyorb2-dev: fails to upgrade from 'squeeze' - trying to overwrite /usr/bin/iac

[Andreas Beckmann]

Package: libpolyorb2-dev
Version: 2.8~20110207-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libpolyorb-dbg

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails
because it tries to overwrite files that are owned by other packages
without declaring a Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This problem is exposed during the upgrade of the 'libpolyorb-dbg'
package, not by upgrading only the buggy package itself.
In order to have piuparts automatically track this problem, I'll mark
this bug as Affects/Found in the exposing package(s), too.

>From the attached log (scroll to the bottom...):

  Selecting previously deselected package libpolyorb2-dev.
  Unpacking libpolyorb2-dev (from .../libpolyorb2-dev_2.8~20110207-4_amd64.deb) 
...
  dpkg: error processing 
/var/cache/apt/archives/libpolyorb2-dev_2.8~20110207-4_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/iac', which is also in package libpolyorb1-dev 
2.6.0~20090423-10


Package: libpolyorb2-dev
Source: polyorb
Version: 2.8~20110207-4
Replaces: libpolyorb2-dev
Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libgnat-4.6 (>= 4.6.3-4), 
libpolyorb3 (= 2.8~20110207-4), g++, gnat-4.6
Recommends: polyorb-servers (= 2.8~20110207-4)
Conflicts: libpolyorb2-dev


The Conflicts/Replaces on libpolyorb2-dev seems useless as this is
not a virtual package provided by any other package. That should
probably be libpolyorb1-dev instead.


cheers,

Andreas

PS: I'd really like to see this together with the cleanup of the
diversion/alternatives mess #688299 #692780, but I'm not sure the RT
will agree ...


libpolyorb-dbg_2.8~20110207-4.log.gz
Description: GNU Zip compressed data

Processed: calligrastage: fails to upgrade from 'squeeze' - trying to overwrite /usr/share/templates/Presentation.desktop

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + koffice
Bug #699200 [calligrastage] calligrastage: fails to upgrade from 'squeeze' - 
trying to overwrite /usr/share/templates/Presentation.desktop
Added indication that 699200 affects koffice

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699177: Wrong sorting in pathname expansion

[Jonathan Nieder]

retitle 699177 dash ignores locale
tags 699177 + upstream
# standards compliance, i18n
severity 699177 important
quit

Hi Alexander,

Alexander Gerasiov wrote:

> If the pattern matches any existing filenames or pathnames, the pattern
> shall be replaced with those filenames and pathnames, sorted according to the
> collating sequence in effect in the current locale.

Yes, that's true.

Actually dash doesn't respect locales at all.

Standards-compliance bugs in dash generally are important (and not
necessarily serious).  In this case it is more complicated --- calling
'setlocale(LC_ALL, "")' would require reexamining every
locale-dependent library call dash makes and would hurt
backward-compatibility.  Help analyzing calls to mitigate the damage
would be much appreciated.

In the meantime, we should at least document it better in the manpage.
Any ideas for wording?

Thanks for reporting and hope that helps,
Jonathan


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Wrong sorting in pathname expansion

[Debian Bug Tracking System]

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

> retitle 699177 dash ignores locale
Bug #699177 [dash] Wrong sorting in pathname expansion
Changed Bug title to 'dash ignores locale' from 'Wrong sorting in pathname 
expansion'
> tags 699177 + upstream
Bug #699177 [dash] dash ignores locale
Added tag(s) upstream.
> # standards compliance, i18n
> severity 699177 important
Bug #699177 [dash] dash ignores locale
Severity set to 'important' from 'serious'
> quit
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: affects 699193, found 699200 in koffice/1:2.4.3+2

[Debian Bug Tracking System]

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

> affects 699193 ahven-dbg
Bug #699193 [libahven3-dev] libahven3-dev: fails to upgrade from 'squeeze' - 
trying to overwrite /usr/lib/libahven.a
Added indication that 699193 affects ahven-dbg
> found 699200 koffice/1:2.4.3+2
Bug #699200 [calligrastage] calligrastage: fails to upgrade from 'squeeze' - 
trying to overwrite /usr/share/templates/Presentation.desktop
The source koffice and version 1:2.4.3+2 do not appear to match any binary 
packages
Marked as found in versions koffice/1:2.4.3+2.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#677054: marked as done (nut-client: prompting due to modified conffiles which were not modified by the user)

[Debian Bug Tracking System]

Your message dated Mon, 28 Jan 2013 23:32:53 +
with message-id 
and subject line Bug#677054: fixed in nut 2.6.4-2.3
has caused the Debian Bug report #677054,
regarding nut-client: prompting due to modified conffiles which were not 
modified by the user
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.)


-- 
677054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nut-client
Version: 2.6.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

http://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In http://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

  Setting up nut-client (2.6.4-1) ...
  
  Configuration file `/etc/nut/nut.conf'
   ==> Modified (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** nut.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing nut-client 
(--configure):
   EOF on stdin at conffile prompt


cheers,

Andreas


nut_2.6.4-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: nut
Source-Version: 2.6.4-2.3

We believe that the bug you reported is fixed in the latest version of
nut, 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 677...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ivo De Decker  (supplier of updated nut 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2013 20:09:48 +0100
Source: nut
Binary: nut nut-server nut-client nut-cgi nut-snmp nut-xml nut-powerman-pdu 
nut-doc libupsclient1 libupsclient1-dev python-nut nut-monitor libups-nut-perl
Architecture: source all amd64
Version: 2.6.4-2.3
Distribution: unstable
Urgency: low
Maintainer: Arnaud Quette 
Changed-By: Ivo De Decker 
Description: 
 libups-nut-perl - network UPS tools - Perl bindings for NUT server
 libupsclient1 - network UPS tools - client library
 libupsclient1-dev - network UPS tools - development files
 nut- network UPS tools - metapackage
 nut-cgi- network UPS tools - web interface
 nut-client - network UPS tools - clients
 nut-doc- network UPS tools - documentation
 nut-monitor - network UPS tools - GUI application to monitor UPS status
 nut-powerman-pdu - network UPS tools - PowerMan PDU driver
 nut-server - network UPS tools - core system
 nut-snmp   - network UPS tools - SNMP driver
 nut-xml- network UPS tools - XML/HTTP driver
 python-nut - network UPS tools - Python bindings for NUT server
Closes: 677054
Changes: 
 nut (2.6.4-2.3) unstable; urgency=low
 .
   * Non-maintainer upload with fixes for wheezy.
   * debian/nut-client.preinst: also revert /etc/nut/nut.conf mangling done
 by postinst during upgrade from lenny to squeeze (Really closes: #677054)
 Thanks to Andreas Beckmann for the review.
Checksums-Sha1: 
 6f9be47e4f51316cc257f2a1bd8af02ba0044c1c 2698 nut_2.6.4-2.3.dsc
 d00b2642580ab

Processed: Re: Bug#656090: ocsinventory-server: prompting due to modified conffiles which where not modified by the user

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #656090 [ocsinventory-server] ocsinventory-server: prompting due to 
modified conffiles which where not modified by the user
Severity set to 'serious' from 'normal'
> tags -1 - unreproducible
Bug #656090 [ocsinventory-server] ocsinventory-server: prompting due to 
modified conffiles which where not modified by the user
Removed tag(s) unreproducible.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699208: `service mpd stop` fails silently

[Christoph Egger]

Package: mpd
Version: 0.16.8-1
Severity: serious

Hi!

  The mpd initscript silently fails to stop mpd (returns with exit
status 0 but mpd is still running):

christoph@mitoraj {3} ~ 
16:44 0 % sudo service mpd stop
[ ok ] Stopping Music Player Daemon: mpd.
christoph@mitoraj {3} ~ 
16:44 0 % ps auxf | grep mpd   
mpd   1816  0.3  0.1 300796 11468 ?Ss   14:36   0:26 /usr/bin/mpd 
/etc/mpd.conf
1000 18185  0.0  0.0   9084  1540 ?S+   16:44   0:00  |   \_ grep 
mpd
christoph@mitoraj {3} ~ 
16:44 0 % sudo bash -x /etc/init.d/mpd stop
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ NAME=mpd
+ DESC='Music Player Daemon'
+ DAEMON=/usr/bin/mpd
+ MPDCONF=/etc/mpd.conf
+ START_MPD=true
+ '[' -x /usr/bin/mpd ']'
+ '[' -r /etc/default/mpd ']'
+ . /etc/default/mpd
++ START_MPD=true
+ '[' -n '' ']'
+ '[' '!' -d /var/run/mpd ']'
++ sed -n 's/^[[:space:]]*db_file[[:space:]]*"\?\([^"]*\)\"\?/\1/p' 
/etc/mpd.conf
+ DBFILE=/var/lib/mpd/tag_cache
++ sed -n 's/^[[:space:]]*pid_file[[:space:]]*"\?\([^"]*\)\"\?/\1/p' 
/etc/mpd.conf
+ PIDFILE=/var/run/mpd/pid
+ case "$1" in
+ mpd_stop
+ '[' true '!=' true ']'
+ '[' -z /var/run/mpd/pid ']'
+ log_daemon_msg 'Stopping Music Player Daemon' mpd
+ '[' -z 'Stopping Music Player Daemon' ']'
+ log_daemon_msg_pre 'Stopping Music Player Daemon' mpd
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ '[' -t 1 ']'
+ '[' xrxvt-unicode-256color '!=' x ']'
+ '[' xrxvt-unicode-256color '!=' xdumb ']'
+ '[' -x /usr/bin/tput ']'
+ '[' -x /usr/bin/expr ']'
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ '[' -z ']'
+ FANCYTTY=1
+ case "$FANCYTTY" in
+ true
+ /bin/echo -n '[] '
[] + '[' -z mpd ']'
+ /bin/echo -n 'Stopping Music Player Daemon: mpd'
Stopping Music Player Daemon: mpd+ log_daemon_msg_post 'Stopping Music Player 
Daemon' mpd
+ :
+ start-stop-daemon --stop --quiet --oknodo --retry 5 --pidfile 
/var/run/mpd/pid --exec /usr/bin/mpd
+ log_end_msg 0
+ '[' -z 0 ']'
+ local retval
+ retval=0
+ log_end_msg_pre 0
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ '[' -t 1 ']'
+ '[' xrxvt-unicode-256color '!=' x ']'
+ '[' xrxvt-unicode-256color '!=' xdumb ']'
+ '[' -x /usr/bin/tput ']'
+ '[' -x /usr/bin/expr ']'
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ '[' -z 1 ']'
+ true
+ case "$FANCYTTY" in
+ true
++ /usr/bin/tput setaf 1
+ RED=''
++ /usr/bin/tput setaf 2
+ GREEN=''
++ /usr/bin/tput setaf 3
+ YELLOW=''
++ /usr/bin/tput op
+ NORMAL=''
+ /usr/bin/tput civis
+ /usr/bin/tput sc
+ /usr/bin/tput hpa 0
+ '[' 0 -eq 0 ']'
+ /bin/echo -ne '[ ok '
[ ok + /usr/bin/tput rc
+ /usr/bin/tput cnorm
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ '[' -t 1 ']'
+ '[' xrxvt-unicode-256color '!=' x ']'
+ '[' xrxvt-unicode-256color '!=' xdumb ']'
+ '[' -x /usr/bin/tput ']'
+ '[' -x /usr/bin/expr ']'
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ '[' -z 1 ']'
+ true
+ case "$FANCYTTY" in
+ true
++ /usr/bin/tput setaf 1
+ RED=''
++ /usr/bin/tput setaf 3
+ YELLOW=''
++ /usr/bin/tput op
+ NORMAL=''
+ '[' 0 -eq 0 ']'
+ echo .
.
+ log_end_msg_post 0
+ :
+ return 0


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.0-0-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mpd depends on:
ii  adduser   3.113+nmu3
ii  libao41.1.0-2
ii  libaudiofile1 0.3.4-2
ii  libavahi-client3  0.6.31-1
ii  libavahi-common3  0.6.31-1
ii  libavahi-glib10.6.31-1
ii  libavcodec53  6:0.8.5-1
ii  libavformat53 6:0.8.5-1
ii  libavutil51   6:0.8.5-1
ii  libc0.1   2.13-37
ii  libcurl3-gnutls   7.26.0-1
ii  libfaad2  2.7-8
ii  libflac8  1.2.1-6
ii  libglib2.0-0  2.33.12+really2.32.4-3
ii  libid3tag00.15.1b-10
ii  libjack-jackd2-0 [libjack-0.116]  1.9.8~dfsg.4+20120529git007cdc37-5
ii  libmad0   0.15.1b-7
ii  libmikmod23.1.12-5
ii  libmms0   0.6.2-3
ii  libmp3lame0   3.99.5+repack1-3
ii  libmpcdec62:0.1~r459-4
ii  libogg0   1.3.0-4
ii  libpulse0 2.0-6
ii  libsamplerate00.1.8-5
ii  libshout3  

Bug#656090: ocsinventory-server: prompting due to modified conffiles which where not modified by the user

[Stuart Prescott]

control: tags -1 +patch

The attached patch reverts the change of /etc/ocsinventory/ocsinventory.conf 
from configuation file to conffile and copies the file in only on fresh 
installs of 
the package.

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
diff -u ocsinventory-server-2.0.5/debian/ocsinventory-server.install ocsinventory-server-2.0.5/debian/ocsinventory-server.install
--- ocsinventory-server-2.0.5/debian/ocsinventory-server.install
+++ ocsinventory-server-2.0.5/debian/ocsinventory-server.install
@@ -1 +1 @@
-debian/conf/ocsinventory.conf etc/ocsinventory/
+debian/conf/ocsinventory.conf usr/share/ocsinventory-server/files/
diff -u ocsinventory-server-2.0.5/debian/changelog ocsinventory-server-2.0.5/debian/changelog
--- ocsinventory-server-2.0.5/debian/changelog
+++ ocsinventory-server-2.0.5/debian/changelog
@@ -1,3 +1,11 @@
+ocsinventory-server (2.0.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Revert change of ocsinventory-server.conf to a conffile and only install
+if on new installs (Closes: #656090).
+
+ -- Stuart Prescott   Tue, 29 Jan 2013 00:52:18 +
+
 ocsinventory-server (2.0.5-1) unstable; urgency=low
 
   * Imported Upstream version 2.0.5
diff -u ocsinventory-server-2.0.5/debian/ocsinventory-server.postinst ocsinventory-server-2.0.5/debian/ocsinventory-server.postinst
--- ocsinventory-server-2.0.5/debian/ocsinventory-server.postinst
+++ ocsinventory-server-2.0.5/debian/ocsinventory-server.postinst
@@ -12,6 +12,12 @@
 chmod -R g+w $log
 
 
+if [ "$1" = "configure" -a "$#" -eq 2 ]; then
+  if [ ! -f $confpath/$conffile ]; then
+cp /usr/share/ocsinventory-server/files/$conffile $confpath/$conffile
+  fi
+fi
+
 if [ "$1" = "configure" ]; then
 
   # enable required apache modules


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

Processed: Re: Bug#656090: ocsinventory-server: prompting due to modified conffiles which where not modified by the user

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #656090 [ocsinventory-server] ocsinventory-server: prompting due to 
modified conffiles which where not modified by the user
Added tag(s) patch.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#699034: libwebkitgtk-1.0-0: midori and GtkLauncher crash after typing a url (cairo-surface.c assertion)

[Michael Gilbert]

>> Huge guess here, but can you try with vesa rather than nouveau?
>
> How? (there is no more an Xorg.conf)

That doesn't preclude creating one for testing purposes.  It will
still be used if it exists.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#606268: marked as done (Network interface used for installation is configured as unmanaged by NM)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#606268: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #606268,
regarding Network interface used for installation is configured as unmanaged by 
NM
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.)


-- 
606268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.8.1-6
Severity: serious
Tags: d-i

On upgrading to this version network manager stopped managing
my wireless interface and my laptop's network was taken down.

/etc/network/interfaces contains a standard stanza as setup by d-i
for a wireless interface:

# The primary network interface
allow-hotplug wlan0
iface wlan0 inet dhcp
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid any

/etc/NetworkManager/NetworkManager.conf contained managed=false. Setting
managed=true works around the problem.

Unfortunatly the /etc/network/interfaces munger introduced to fix
#530024 was not a sufficient fix. It doesn't munge the above stanza at all
when I run it by hand, due to the wireless-mode and wireless-essid lines.

So, bug #569215 has basically been all that has been keeping wireless
and some other networks managed by network-manager on newly installed
and upgraded systems, for the past 6+ months..

One approach would be for for /usr/lib/NetworkManager/ifblacklist_migrate.sh
to convert stanzas containing any of these lines which d-i can include:

wireless-mode managed
wireless-essid *
wireless-key1 *
hostname *

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

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

Versions of packages network-manager depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  dbus 1.2.24-3simple interprocess messaging syst
ii  isc-dhcp-client  4.1.1-P1-15 ISC DHCP client
ii  libc62.11.2-7Embedded GNU C Library: Shared lib
ii  libdbus-1-3  1.2.24-3simple interprocess messaging syst
ii  libdbus-glib-1-2 0.88-2  simple interprocess messaging syst
ii  libgcrypt11  1.4.5-2 LGPL Crypto library - runtime libr
ii  libglib2.0-0 2.24.2-1The GLib library of C routines
ii  libgnutls26  2.8.6-1 the GNU TLS library - runtime libr
ii  libgudev-1.0-0   164-2   GObject-based wrapper library for 
ii  libnl1   1.1-6   library for dealing with netlink s
ii  libnm-glib2  0.8.1-6 network management framework (GLib
ii  libnm-util1  0.8.1-6 network management framework (shar
ii  libpolkit-gobject-1-00.96-4  PolicyKit Authorization API
ii  libuuid1 2.17.2-3.3  Universally Unique ID library
ii  lsb-base 3.2-26  Linux Standard Base 3.2 init scrip
ii  udev 164-2   /dev/ and hotplug management daemo
ii  wpasupplicant0.6.10-2.1  client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  dns 2.55-2+b1A small caching DNS proxy and DHCP
ii  ipt 1.4.10-1 administration tools for packet fi
ii  mod 0.4+git.20100624t180933.6e79d15-1+b1 D-Bus service for managing modems
ii  pol 0.96-4   framework for managing administrat
ii  ppp 2.4.5-4  Point-to-Point Protocol (PPP) - da

Versions of packages network-manager suggests:
ii  avahi-autoipd 0.6.27-3   Avahi IPv4LL network address confi

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 comme

Bug#611281: marked as done (Network interface used for installation is configured as unmanaged by NM)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#606268: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #606268,
regarding Network interface used for installation is configured as unmanaged by 
NM
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.)


-- 
606268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager-gnome
Version: 0.8.1-2
Severity: normal
File: /usr/bin/nm-applet
Tags: upstream

After successul install of D-I RC2, using my D-Link (Atheros) wifi card, I
can't see any wireless network using the nm-applet.
Still, I can connect manually and I can see my wifi card as wlan0



-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (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

Versions of packages network-manager-gnome depends on:
ii  dbus-x11   1.2.24-4  simple interprocess messaging syst
ii  gconf2 2.28.1-6  GNOME configuration database syste
ii  gnome-icon-theme   2.30.3-2  GNOME Desktop icon theme
ii  libatk1.0-01.30.0-1  The ATK accessibility toolkit
ii  libc6  2.11.2-9  Embedded GNU C Library: Shared lib
ii  libcairo2  1.8.10-6  The Cairo 2D vector graphics libra
ii  libdbus-1-31.2.24-4  simple interprocess messaging syst
ii  libdbus-glib-1-2   0.88-2.1  simple interprocess messaging syst
ii  libfontconfig1 2.8.0-2.1 generic font configuration library
ii  libfreetype6   2.4.2-2.1 FreeType 2 font engine, shared lib
ii  libgconf2-42.28.1-6  GNOME configuration database syste
ii  libglade2-01:2.6.4-1 library to load .glade files at ru
ii  libglib2.0-0   2.24.2-1  The GLib library of C routines
ii  libgnome-bluetooth72.30.0-2  GNOME Bluetooth tools - support li
ii  libgnome-keyring0  2.30.1-1  GNOME keyring services library
ii  libgtk2.0-02.20.1-2  The GTK+ graphical user interface 
ii  libnm-glib-vpn10.8.1-6   network management framework (GLib
ii  libnm-glib20.8.1-6   network management framework (GLib
ii  libnm-util10.8.1-6   network management framework (shar
ii  libnotify1 [libnotify1 0.5.0-2   sends desktop notifications to a n
ii  libpango1.0-0  1.28.3-1+squeeze1 Layout and rendering of internatio
ii  libxml22.7.8.dfsg-2  GNOME XML library
ii  network-manager0.8.1-6   network management framework daemo
ii  policykit-1-gnome  0.96-3GNOME authentication agent for Pol
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

Versions of packages network-manager-gnome recommends:
ii  gnome-bluetooth   2.30.0-2   GNOME Bluetooth tools
ii  libpam-gnome-keyring [libpam- 2.30.3-5   PAM module to unlock the GNOME key
ii  mobile-broadband-provider-inf 20101106-1 database of mobile broadband servi
ii  notification-daemon   0.5.0-2daemon to displays passive pop-up 

Versions of packages network-manager-gnome suggests:
pn  network-manager-openvpn-gnome  (no description available)
pn  network-manager-pptp-gnome (no description available)
pn  network-manager-vpnc-gnome (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 606...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manag

Bug#609072: marked as done (Network interface used for installation is configured as unmanaged by NM)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#606268: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #606268,
regarding Network interface used for installation is configured as unmanaged by 
NM
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.)


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

Package: installation-reports

Boot method: CD Net Installer
Image version: 6.0 (squeeze) - installer build 20110101-03:54
Date:   a) 4-Jan-2011
   b) 4-Jan-2001
Machine:a) Laptop Packard-Bell
   b) Laptop OEM
Processor:  a) 800 MHz Celeron, 128 Kb cache
   b) 2.8 GHz Celeron, 256 Kb cache
Memory: a) 384 Kb
   b) 448 Kb
Partitions: a)
   Filesystem   1K-blocks  Used Available Use% Mounted on
   tmpfs   18856052188508   0% /dev
   /dev/sda1   964500141336774168  15% /target
   /dev/sda5  1921156192752   1630812  11% /target/home
   /dev/sda8  1004024 18364934656   2% /target/opt
   /dev/sda6  2885780   1780004959188  65% /target/usr
   /dev/sda7  1921156170400   1653164   9% /target/var
   /dev/sda1   964500141336774168  15% /dev/.static/dev
   tmpfs   18856052188508   0% /target/dev
   b)
   Filesystem   1K-blocks  Used Available Use% Mounted on
   tmpfs   22513660225076   0% /dev
   /dev/sda5   964500143604771900  16% /target
   /dev/sda6  1921156   1182596640968  65% /target/home
   /dev/sda9  7732320148472   7191064   2% /target/opt
   /dev/sda7  4806904   2620652   1942068  57% /target/usr
   /dev/sda8  2885780224016   2515176   8% /target/var
   /dev/sda5   964500143604771900  16% /dev/.static/dev
   tmpfs   22513660225076   0% /target/dev

Wireless Interface:
   a)
   Jan  4 00:19:08 kernel: [  106.649409] cfg80211: Calling CRDA for 
country: US
   Jan  4 00:19:08 kernel: [  106.772976] p54pci :02:00.0: PCI INT 
A -> Link[LNKA] -> GSI 9 (level, low) -> IRQ 9
   Jan  4 00:19:08 kernel: [  106.773115] p54pci :02:00.0: 
firmware: requesting isl3886pci
   Jan  4 00:19:08 kernel: [  106.797935] phy0: p54 detected a LM86 
firmware
   Jan  4 00:19:08 kernel: [  106.797949] p54: rx_mtu reduced from 3240 
to 2376
   Jan  4 00:19:08 kernel: [  106.797956] phy0: FW rev 2.13.1.0 - 
Softmac protocol 5.5
   Jan  4 00:19:08 kernel: [  106.797964] phy0: cryptographic 
accelerator WEP:YES, TKIP:YES, CCMP:YES
   Jan  4 00:19:09 kernel: [  107.707178] phy0: hwaddr 
00:09:5b:ee:e5:0e, MAC:isl3886 RF:Frisbee
   Jan  4 00:19:09 kernel: [  107.744275] phy0: Selected rate control 
algorithm 'minstrel'
   Jan  4 00:19:09 kernel: [  107.746572] Registered led device: 
p54-phy0::assoc
   Jan  4 00:19:09 kernel: [  107.746638] Registered led device: 
p54-phy0::tx
   Jan  4 00:19:09 kernel: [  107.746694] Registered led device: 
p54-phy0::rx
   Jan  4 00:19:09 kernel: [  107.746749] Registered led device: 
p54-phy0::radio
   Jan  4 00:19:09 kernel: [  107.746770] p54pci :02:00.0: is 
registered as 'phy0'
   Jan  4 00:19:09 net/hw-detect.hotplug: Detected hotpluggable network 
interface wlan0
   Jan  4 00:19:10 check-missing-firmware: no missing firmware in 
/dev/.udev/firmware-missing

   b)
   Jan  4 18:49:23 kernel: [   55.562608] cfg80211: Calling CRDA for 
country: US
   Jan  4 18:49:23 net/hw-detect.hotplug: Detected hotpluggable network 
interface eth0
   Jan  4 18:49:23 kernel: [   55.740026] usb 1-4: reset high speed USB 
device using ehci_hcd and address 2
   Jan  4 18:49:23 kernel: [   55.884328] phy0: Selected rate control 
algorithm 'minstrel'

   Jan  4 18:49:23 kernel: [   55.885288] zd1211rw 1-4:1.0: phy0
   Jan  4 18:49:23 kernel: [   55.885326] usbcore: registered new 
interface driver zd1211rw
   Jan  4 18:53:05 kernel: [  277.906060] usb 1-4: firmware: requesting 
zd1211/zd1211b_ub
   Jan  4 18:53:05 kernel: [  277.911132] usb 1-4: firmware: requesting 
zd1211/zd1211b_uphr
   Jan  4 18:53:05 kernel: [  277.958073] zd1211rw 1-4:1.0: firmware 
version 4725
   Jan  4 18:53:05 kernel: [  277.998073] zd1211rw 1-4:1.0: zd1211b 
chip 050d:705c v4810 high 00-11-50 AL2230_RF pa0 g--N-
   Jan  4 18:53:05 kernel: [  278.000462] cfg80211: Calling CRDA for 
country: US
   Jan

Bug#617906: marked as done (Network interface used for installation is configured as unmanaged by NM)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#606268: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #606268,
regarding Network interface used for installation is configured as unmanaged by 
NM
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.)


-- 
606268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD
Image version: http://cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/
Date: 03-2011

Machine: desktop
Processor: Intel Pentium IV 2GHz
Memory: 1GB
Partitions:
File system   Tipo blocchi di 1K   Usati   Dispon. Uso% Montato su
/dev/sda6 ext3    10886900   3285328   7048536  32% /
tmpfs    tmpfs  647260 0    647260   0% /lib/init/rw
udev tmpfs  642908   200    642708   1% /dev
tmpfs    tmpfs  647260 0    647260   0% /dev/shm
/dev/sda5 ext3    12389324    164620  11595360   2% /home

Output of lspci -knn:
00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 645xx
[1039:0648] (rev 02)
    Subsystem: Silicon Integrated Systems [SiS] 645xx [1039:0648]
    Kernel driver in use: agpgart-sis
00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] Virtual
PCI-to-PCI bridge (AGP) [1039:0001]
00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS963
[MuTIOL Media IO] [1039:0963] (rev 04)
00:02.1 SMBus [0c05]: Silicon Integrated Systems [SiS] SiS961/2 SMBus
Controller [1039:0016]
    Kernel driver in use: sis96x_smbus
00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513
[IDE] [1039:5513]
    Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE
Controller (A,B step) [1039:5513]
    Kernel driver in use: pata_sis
00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems
[SiS] AC'97 Sound Controller [1039:7012] (rev a0)
    Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:f451]
    Kernel driver in use: Intel ICH
00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB
1.1 Controller [1039:7001] (rev 0f)
    Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001]
    Kernel driver in use: ohci_hcd
00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB
1.1 Controller [1039:7001] (rev 0f)
    Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001]
    Kernel driver in use: ohci_hcd
00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB
1.1 Controller [1039:7001] (rev 0f)
    Subsystem: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001]
    Kernel driver in use: ohci_hcd
00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB
2.0 Controller [1039:7002]
    Subsystem: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002]
    Kernel driver in use: ehci_hcd
00:0c.0 Communication controller [0780]: Conexant Systems, Inc. HSF
56k HSFi Modem [14f1:2f00] (rev 01)
    Subsystem: Conexant Systems, Inc. Dynalink 56PMi [14f1:2004]
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV17
[GeForce4 MX 420] [10de:0172] (rev a3)
    Kernel driver in use: nouveau


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:    [O]
Configure network:  [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:  [O]
Install boot loader:    [O]
Overall install:    [O]

Comments/Problems:
For wlan I use NETGEAR WG111v3 (USB)
I installed Squeeze using the first two CD and wlan with no
protection; wlan worked in the installation;
after installation I was unable to setup wpa wlan connection using
Gnome; this was
my "/etc/network/interfaces" as written by the installer:
-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug wlan0
iface wlan0 inet dhcp
    # wireless-* options are implemented by the wireless-tools package
    wireless-mode managed
    wireless-essid NETGEAR
-

I found that deleting the last lines makes th

Bug#656584: marked as done (NetworkManager doesn't interact with existing ifupdown configuration properly causing mountnfs breakage)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#656584: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #656584,
regarding NetworkManager doesn't interact with existing ifupdown configuration 
properly causing mountnfs breakage
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.)


-- 
656584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-18
Severity: normal

Dear Maintainer,
after update to initscripts (version 2.88dsf-18) NetworkManager is waiting for
interface (even if interface is already up) not doing NFS mounts.
I think is related to /etc/network/if-up.d/mountnfs, that is not updated to
/run transition at row 123: "   if ! grep -q $i /etc/network/run/ifstate ;
then"
This may be now /run/network/ifstate, according to
http://wiki.debian.org/ReleaseGoals/RunDirectory
Kind regards!

Guido Audino



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  coreutils   8.13-3
ii  debianutils 4.1
ii  libc6   2.13-24
ii  lsb-base3.2-28
ii  mount   2.20.1-1.2
ii  sysv-rc 2.88dsf-18
ii  sysvinit-utils  2.88dsf-18

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42-1
ii  psmisc 22.13-1

initscripts suggests no packages.

-- Configuration Files:
/etc/init.d/bootlogd changed:
PATH=/sbin:/bin  # No remote fs at start
DAEMON=/sbin/bootlogd
[ -x "$DAEMON" ] || exit 0
NAME=bootlogd
DESC="boot logger"
BOOTLOGD_OPTS="-r -c"
.. /lib/init/vars.sh
.. /lib/lsb/init-functions
SCRIPTNAME=${0##*/}
SCRIPTNAME=${SCRIPTNAME#[SK]??}
ACTION="$1"
case "$0" in
  *stop-bootlog*)
[ "$ACTION" = start ] && ACTION=stop
;;
esac
case "$ACTION" in
  start)
# PATH is set above
[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
if [ -d /proc/1/. ]
then
umask 027
start-stop-daemon --start --quiet --exec $DAEMON -- \
$BOOTLOGD_OPTS
ES=$?
else
$DAEMON $BOOTLOGD_OPTS
ES=$?
fi
[ "$VERBOSE" != no ] && log_end_msg $ES
;;
  stop)
PATH=/bin:/sbin:/usr/bin:/usr/sbin
[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
start-stop-daemon --oknodo --stop --quiet --exec $DAEMON
ES=$?
sleep 1
[ "$VERBOSE" != no ] && log_end_msg $ES
if [ -f /var/log/boot ] && [ -f /var/log/boot~ ]
then
[ "$VERBOSE" = no ] || log_action_begin_msg "Moving boot log 
file"
# bootlogd writes to boot, making backup at boot~
cd /var/log && {
chgrp adm boot || :
savelog -q -p -c 5 boot \
&& mv boot.0 boot \
&& mv boot~ boot.0
}
ES=$?
[ "$VERBOSE" = no ] || log_action_end_msg $ES
fi
;;
  restart|force-reload)
/etc/init.d/bootlogd stop
/etc/init.d/bootlogd start
;;
  status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
;;
  *)
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 3
;;
esac
:


-- no debconf information


--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manag

Bug#674039: marked as done (/etc/network/if-up.d/mountnfs: boot stalls by 3 minutes because network is not configured yet (using network-manager))

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#656584: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #656584,
regarding /etc/network/if-up.d/mountnfs: boot stalls by 3 minutes because 
network is not configured yet (using network-manager)
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.)


-- 
656584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-22.1
Severity: normal
File: /etc/network/if-up.d/mountnfs

Hello,

I'm using network-manager and have a NFS share configured in fstab. 
After upgrading to latest ifupdown (0.7~rc3) the boot is stalling for 3 
minutes. Here is the relevant excerpt from /var/log/boot

Tue May 22 19:16:25 2012: [] Configuring network interfaces...Starting 
rpcbind daemon
Tue May 22 19:16:26 2012: Starting NFS common utilities: statd idmapd.
Tue May 22 19:19:26 2012: mount.nfs: Connection timed out

I'm guessing this is triggered by this change in ifupdown:

  * Call hook scripts when processing all interfaces:
- If ifupdown is called with the --all option, before or after doing
  anything to the interfaces, it calls all the hook scripts (pre-up or
  down) with IFACE set to "--all", LOGICAL set to the current class
  specified by the --allow option (or "auto" if it's not set),
  ADDRFAM="meta" and METHOD="none".

As far as I can tell the mount can't succeed because I'm using 
network-manager which is started only later:

Tue May 22 19:19:33 2012: [] Starting network connection manager: 
NetworkManager

Thanks for reading,
Andrei


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (x86_64)

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

Versions of packages initscripts depends on:
ii  coreutils   8.13-3.2
ii  debianutils 4.3
ii  libc6   2.13-32
ii  lsb-base4.1+Debian4
ii  mount   2.20.1-5
ii  sysv-rc 2.88dsf-22.1
ii  sysvinit-utils  2.88dsf-22.1
ii  ucf 3.0025+nmu3

Versions of packages initscripts recommends:
ii  e2fsprogs  1.42.2-2
ii  psmisc 22.16-1

initscripts suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source amd64
Version: 0.9.4.0-9
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description: 
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 network-manager - network management framework (daemon and userspace tools)
 network-manager-dbg - network management framework (debugging symbols)
 network-manager-dev - network management framework (development files)
Closes: 475188 512286 606268 656584 688355 690987
Changes: 
 network-manager (0.9.4.0-9) unstable; urgency=low
 .
   * Change the ifupdown dispatcher script an

Bug#689320: marked as done (network-manager: async nfs mounts don't work with NetworkManager)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#656584: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #656584,
regarding network-manager: async nfs mounts don't work with NetworkManager
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.)


-- 
656584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.4.0-6
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?

I have a nfs mountpoint configured in fstab:

olympic:/local  /usr/local  nfs4sec=krb50   0

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I reboot the machine.  I expect NetworkManager to call the mountnfs
script in /etc/network/if-up.d to mount the nfs filesystem when the
interface becomes available.

   * What was the outcome of this action?

The filesystem wasn't mounted

   * What outcome did you expect instead?

I expected it to be mounted.


Why it doesn't work:

/etc/NetworkManager/dispatcher.d/01ifupdown calls the scripts in
/etc/network/if-up.d with ADDRFAM="NetworkManager"

/etc/network/if-up.d/mountnfs expects ADDRFAM to be inet or inet6,
it knows nothing of this "NetworkManager" address family.

The actual code in mountnfs is:

if [ no != "$ASYNCMOUNTNFS" ]; then
# Not for loopback!
[ "$IFACE" != "lo" ] || exit 0

[ "$ADDRFAM" = "inet" ] || [ "$ADDRFAM" = "inet6" ] || exit 0

Whoops.

Either mountnfs should be changed to expect ADDRFAM "NetworkManager"
or  01ifupdown should pass the correct address family.

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

Kernel: Linux 3.2.0-3-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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.6.2-2
ii  dpkg   1.16.8
ii  isc-dhcp-client4.2.4-2
ii  libc6  2.13-35
ii  libdbus-1-31.6.8-1
ii  libdbus-glib-1-2   0.100-1
ii  libgcrypt111.5.0-3
ii  libglib2.0-0   2.33.12+really2.32.4-1
ii  libgnutls262.12.20-1
ii  libgudev-1.0-0 175-7
ii  libnl-3-2003.2.7-4
ii  libnl-genl-3-200   3.2.7-4
ii  libnl-route-3-200  3.2.7-4
ii  libnm-glib40.9.4.0-6
ii  libnm-util20.9.4.0-6
ii  libpolkit-gobject-1-0  0.105-1
ii  libuuid1   2.20.1-5.2
ii  lsb-base   4.1+Debian7
ii  udev   175-7
ii  wpasupplicant  1.0-2

Versions of packages network-manager recommends:
pn  crda  
ii  dnsmasq-base  2.63-4
ii  iptables  1.4.14-3
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-1
ii  ppp   2.4.5-5.1+b1

Versions of packages network-manager suggests:
pn  avahi-autoipd  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 656...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source amd64
Version: 0.9.4.0-9
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description: 
 gir1.2-networkmanager-1.0 - GObject introspection data f

Bug#688355: marked as done (network-manager: NM breaks /etc/network/interfaces with DHCP + manual IPv6 entries created by wheezy's debian-installer)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#688355: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #688355,
regarding network-manager: NM breaks /etc/network/interfaces with DHCP + manual 
IPv6 entries created by wheezy's debian-installer
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.)


-- 
688355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.4.0-6
Severity: grave

I just installed a new laptop using wheezy's d-i. I do have IPv6 on the
network and as a result d-i did output supplementary entries in
/etc/network/interfaces.

However NetworkManager garbled them and the result is a file that
ifup doesn't parse. The net result is that the loopback interface
is not configured... and random things that don't work with hard to
debug failures.

$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
#NetworkManager#iface eth0 inet6 manual
up ip link set eth0 up
down ip link set eth0 down

Either NM needs to learn those new entries or we need to find a
definitive solution...

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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.6.2-2
ii  dpkg   1.16.8
ii  isc-dhcp-client4.2.4-2
ii  libc6  2.13-35
ii  libdbus-1-31.6.2-2
ii  libdbus-glib-1-2   0.100-1
ii  libgcrypt111.5.0-3
ii  libglib2.0-0   2.33.12+really2.32.3-2
ii  libgnutls262.12.20-1
ii  libgudev-1.0-0 175-7
ii  libnl-3-2003.2.7-4
ii  libnl-genl-3-200   3.2.7-4
ii  libnl-route-3-200  3.2.7-4
ii  libnm-glib40.9.4.0-6
ii  libnm-util20.9.4.0-6
ii  libpolkit-gobject-1-0  0.105-1
ii  libuuid1   2.20.1-5.2
ii  lsb-base   4.1+Debian7
ii  udev   175-7
ii  wpasupplicant  1.0-2

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.63-3
ii  iptables  1.4.14-3
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-1
ii  ppp   2.4.5-5.1+b1

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 688...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source amd64
Version: 0.9.4.0-9
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description: 
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-u

Bug#682608: marked as done (installation-reports: wireless failure upon boot after install using new netinst via wifi -- wheezy 64-bit)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#606268: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #606268,
regarding installation-reports: wireless failure upon boot after install using 
new netinst via wifi -- wheezy 64-bit
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.)


-- 
606268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

wheezy install alpha 1 using netinst.  wifi interface recognized
and WPE secure network used to install wheezy alpha 1.
Upon completion without error and when reboot the wireless
interface was not completely recognized.  The dual computer
icon did not change and device not managed shown for wireless
network.

But firefox and ping worked, but evolution and other internet
programs failed due to network being shown as down.

If config -a showed wlan0 was enabled and working.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I went back and did a complete install from scratch using
CAT6 cable to router.  Installation went perfectly again.

   * What was the outcome of this action?

This time upon reboot the system worked perfectly and
the wireless network was recognized and connected to upon
entering password.

   * What outcome did you expect instead?

Hope this helps.

I tried the weekly build, but the distinst tool does not
do wireless.  eth0  did work for the install and networking
was functional.

chuck



-- Package-specific info:

Boot method: 
Image version: 
Date: 

Machine: 
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="7.0 (wheezy) - installer build 20120723-00:03"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian 3.2.0-3-amd64 #1 SMP Thu Jun 28 09:07:26 UTC 2012 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host 
Bridge [1022:9600]
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff6a]
lspci -knn: 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 
PCI to PCI bridge (int gfx) [1022:9602]
lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 
PCI to PCI bridge (PCIE port 0) [1022:9604]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 
PCI to PCI bridge (PCIE port 1) [1022:9605]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI 
to PCI bridge (PCIE port 2) [1022:9606]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:07.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI 
to PCI bridge (PCIE port 3) [1022:9607]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee 
ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff6a]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
lspci -knn: Subsystem: Toshiba America Info Systems Device [1179:ff6a]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI 
SB

Bug#690987: marked as done (network-manager: option added in /etc/network/interfaces by D-I is not commented after nm install)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 03:33:06 +
with message-id 
and subject line Bug#690987: fixed in network-manager 0.9.4.0-9
has caused the Debian Bug report #690987,
regarding network-manager: option added in /etc/network/interfaces by D-I is 
not commented after nm install
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.)


-- 
690987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.4.0-6
Severity: serious

Hi,

The new debian installer (wheezy beta 3) is now adding ipv6
configuration for the interfaces. This configuration includes
the following option: "privext 2"

After installation, /etc/network/interfaces was looking like this on my
machine:

=8<

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
# This is an autoconfigured IPv6 interface
#NetworkManager#iface eth0 inet6 auto
# Activate RFC 4941 privacy extensions for outgoing connections. The
# machine will still be reachable via its EUI-64 interface identifier.
privext 2

=8<

As you can see the "privext 2" option is not commented, this is making
the networking init script generate warnings.

Cheers

Laurent Bigonville

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

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.6.8-1
ii  dpkg   1.16.8
ii  isc-dhcp-client4.2.4-3
ii  libc6  2.13-35
ii  libdbus-1-31.6.8-1
ii  libdbus-glib-1-2   0.100-1
ii  libgcrypt111.5.0-3
ii  libglib2.0-0   2.34.0-1
ii  libgnutls262.12.20-1
ii  libgudev-1.0-0 175-7
ii  libnl-3-2003.2.7-4
ii  libnl-genl-3-200   3.2.7-4
ii  libnl-route-3-200  3.2.7-4
ii  libnm-glib40.9.4.0-6
ii  libnm-util20.9.4.0-6
ii  libpolkit-gobject-1-0  0.105-1
ii  libuuid1   2.20.1-5.2
ii  lsb-base   4.1+Debian7
ii  udev   175-7
ii  wpasupplicant  1.0-3

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.63-4
ii  iptables  1.4.14-3
ii  modemmanager  0.5.2.0-2
ii  policykit-1   0.105-1
ii  ppp   2.4.5-5.1+b1

Versions of packages network-manager suggests:
pn  avahi-autoipd  

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.9.4.0-9

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 690...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 04:10:11 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev 
network-manager-dbg gir1.2-networkmanager-1.0
Architecture: source amd64
Version: 0.9.4.0-9
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description: 
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 -

Bug#681147: marked as done (libmilter-dev: /u/s/d/libmilter-dev is a symlink to sendmail, but ships files in /u/s/d/libmilter-dev)

[Debian Bug Tracking System]

Your message dated Tue, 29 Jan 2013 04:02:58 +
with message-id 
and subject line Bug#681147: fixed in sendmail 8.14.4-3
has caused the Debian Bug report #681147,
regarding libmilter-dev: /u/s/d/libmilter-dev is a symlink to sendmail, but 
ships files in /u/s/d/libmilter-dev
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.)


-- 
681147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmilter-dev
Version: 8.14.4-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts I noticed your package causes
removal of files that also belong to another package.

libmilter-dev.preinst sets up /usr/share/doc/libmilter-dev -> sendmail
but ships the following files there, overwriting files from the sendmail
package:

/usr/share/doc/libmilter-dev/changelog.Debian.gz
/usr/share/doc/libmilter-dev/copyright
/usr/share/doc/libmilter-dev/NEWS.Debian.gz
/usr/share/doc/libmilter-dev/buildinfo.gz
/usr/share/doc/libmilter-dev/changelog.gz
/usr/share/doc/libmilter-dev/README.gz

>From the attached log (scroll to the bottom...):

0m40.1s INFO: Warning: Package purging left files on system:
  /usr/share/doc/libmilter1.0.1 -> sendmail  owned by: libmilter1.0.1

0m40.1s ERROR: FAIL: After purging files have disappeared:
  /usr/share/doc/sendmail/   not owned
  /usr/share/doc/sendmail/NEWS.Debian.gz not owned
  /usr/share/doc/sendmail/README.gz  not owned
  /usr/share/doc/sendmail/buildinfo.gz   not owned
  /usr/share/doc/sendmail/changelog.Debian.gznot owned
  /usr/share/doc/sendmail/changelog.gz   not owned
  /usr/share/doc/sendmail/copyright  not owned

libmilter1.0.1 ships the following files:
drwxr-xr-x root/root 0 2012-05-09 08:47 ./usr/share/doc/
drwxr-xr-x root/root 0 2012-05-09 08:48 ./usr/share/doc/libmilter1.0.1/
-rw-r--r-- root/root  7216 2012-05-09 08:46 
./usr/share/doc/libmilter1.0.1/changelog.Debian.gz
-rw-r--r-- root/root  4529 2012-05-09 08:46 
./usr/share/doc/libmilter1.0.1/copyright
-rw-r--r-- root/root   964 2012-05-09 08:46 
./usr/share/doc/libmilter1.0.1/NEWS.Debian.gz
-rw-r--r-- root/root  2319 2012-05-09 08:48 
./usr/share/doc/libmilter1.0.1/buildinfo.gz
-rw-r--r-- root/root188634 2009-12-23 04:43 
./usr/share/doc/libmilter1.0.1/changelog.gz
-rw-r--r-- root/root  7733 2009-04-10 17:49 
./usr/share/doc/libmilter1.0.1/README.gz
so the symlink bug seems to exist there, too

cheers,

Andreas


libmilter-dev_8.14.4-2.1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: sendmail
Source-Version: 8.14.4-3

We believe that the bug you reported is fixed in the latest version of
sendmail, 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 681...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated sendmail 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...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Jan 2013 03:37:54 +0100
Source: sendmail
Binary: sendmail-bin rmail sensible-mda libmilter1.0.1 libmilter1.0.1-dbg 
libmilter-dev sendmail-doc sendmail sendmail-base sendmail-cf
Architecture: source all amd64
Version: 8.14.4-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Description: 
 libmilter-dev - Sendmail Mail Filter API (Milter)
 libmilter1.0.1 - Sendmail Mail Filter API (Milter)
 libmilter1.0.1-dbg - Sendmail Mail Filter API (Milter)
 rmail  - MTA->UUCP remote mail handler
 sendmail   - powerful, efficient, and scalable Mail Transport Agent
 sendmail-base - powerful, efficient, and scalable Mail Transport Agent
 sendmail-bin - powerful, efficient, and scalable Mail Transport Agent
 sendmail-cf - powerful, efficient, and scalable Mail Transport Agent
 sendmail-doc - powerful, efficient, and scalable Mail Transport Agent
 sensible-mda - Mail Delivery Agent wrapper
Closes: 336391 587944 681147 689379
Changes: 
 sendmail (8.14.4-3) unstable; urgency=low
 .
   * QA upload.
   * Set maintainer to Debian QA Group.  (See: #699117)
 .
   

Processed: retitle 698910 to zoneminder: CVE-2013-0232: arbitrary command execution vulnerability

[Debian Bug Tracking System]

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

> retitle 698910 zoneminder: CVE-2013-0232: arbitrary command execution 
> vulnerability
Bug #698910 [src:zoneminder] zoneminder: arbitrary command execution 
vulnerability
Changed Bug title to 'zoneminder: CVE-2013-0232: arbitrary command execution 
vulnerability' from 'zoneminder: arbitrary command execution vulnerability'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: severity of 699034 is normal

[Debian Bug Tracking System]

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

> severity 699034 normal
Bug #699034 [src:cairo] libwebkitgtk-1.0-0: midori and GtkLauncher crash after 
typing a url (cairo-surface.c assertion)
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#694286: fstrcmp: missing Breaks+Replaces: libfstrcmp-dev (<< 0.4)

[Andreas Beckmann]

Followup-For: Bug #694286

Hi,

I'm attaching a proposed patch for a t-p-u upload.


Andreas
diff -Nru fstrcmp-0.4.D001/debian/changelog fstrcmp-0.4.D001/debian/changelog
--- fstrcmp-0.4.D001/debian/changelog	2011-10-06 01:38:39.0 +0200
+++ fstrcmp-0.4.D001/debian/changelog	2013-01-29 08:26:41.0 +0100
@@ -1,3 +1,10 @@
+fstrcmp (0.4.D001-1.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * fstrcmp: Add Breaks/Replaces: libfstrcmp-dev (<< 0.4).  (Closes: #694286)
+
+ -- Andreas Beckmann   Tue, 29 Jan 2013 08:22:38 +0100
+
 fstrcmp (0.4.D001-1) unstable; urgency=low
 
   * This change set prepares the fstrcmp project for the next public release.
diff -Nru fstrcmp-0.4.D001/debian/control fstrcmp-0.4.D001/debian/control
--- fstrcmp-0.4.D001/debian/control	2011-10-06 01:38:39.0 +0200
+++ fstrcmp-0.4.D001/debian/control	2013-01-29 08:26:39.0 +0100
@@ -12,6 +12,8 @@
 Description: fuzzy comparison of strings
  This package provides a command to make fuzzy string comparisons.
 Depends: ${misc:Depends}, ${shlibs:Depends}, libfstrcmp0
+Breaks: libfstrcmp-dev (<< 0.4)
+Replaces: libfstrcmp-dev (<< 0.4)
 
 Package: libfstrcmp0
 Section: libs