Bug#801568: libtevent-dev and linpac: error when trying to install together

[Ralf Treinen]

Package: linpac,libtevent-dev
Version: linpac/0.23-1
Version: libtevent-dev/0.9.25-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2015-10-12
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libffi6:amd64.
(Reading database ... 10896 files and directories currently installed.)
Preparing to unpack .../libffi6_3.2.1-3_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-3) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../libc-dev-bin_2.19-22_amd64.deb ...
Unpacking libc-dev-bin (2.19-22) ...
Selecting previously unselected package linux-libc-dev:amd64.
Preparing to unpack .../linux-libc-dev_4.2.3-1_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.2.3-1) ...
Selecting previously unselected package libc6-dev:amd64.
Preparing to unpack .../libc6-dev_2.19-22_amd64.deb ...
Unpacking libc6-dev:amd64 (2.19-22) ...
Selecting previously unselected package libglib2.0-0:amd64.
Preparing to unpack .../libglib2.0-0_2.46.0-2_amd64.deb ...
Unpacking libglib2.0-0:amd64 (2.46.0-2) ...
Selecting previously unselected package libtalloc2:amd64.
Preparing to unpack .../libtalloc2_2.1.3-1_amd64.deb ...
Unpacking libtalloc2:amd64 (2.1.3-1) ...
Selecting previously unselected package pkg-config.
Preparing to unpack .../pkg-config_0.28-1_amd64.deb ...
Unpacking pkg-config (0.28-1) ...
Selecting previously unselected package libtalloc-dev.
Preparing to unpack .../libtalloc-dev_2.1.3-1_amd64.deb ...
Unpacking libtalloc-dev (2.1.3-1) ...
Selecting previously unselected package libtevent0:amd64.
Preparing to unpack .../libtevent0_0.9.25-2_amd64.deb ...
Unpacking libtevent0:amd64 (0.9.25-2) ...
Selecting previously unselected package libtevent-dev.
Preparing to unpack .../libtevent-dev_0.9.25-2_amd64.deb ...
Unpacking libtevent-dev (0.9.25-2) ...
Selecting previously unselected package linpac.
Preparing to unpack .../linpac_0.23-1_amd64.deb ...
Unpacking linpac (0.23-1) ...
dpkg: error processing archive /var/cache/apt/archives/linpac_0.23-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/include/tevent.h', which is also in package 
libtevent-dev 0.9.25-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.4-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linpac_0.23-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/include/tevent.h

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Processed: found 801410 in java-common/0.52.1

[Debian Bug Tracking System]

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

> found 801410 java-common/0.52.1
Bug #801410 [java-common,java-policy] java-policy and java-common: error when 
trying to install together
Marked as found in versions java-common/0.52.1.
> thanks
Stopping processing here.

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

Bug#801361: [systemd] attempts to unmount filesystems at end of boot, INCLUDING ROOT

[Ara Keary]

Many thanks for the very fast solution!
Updating from 227-1 to 227-2 solves
• unmounting of partitions at boot
• ssh rsa/dsa-key authentification issue that occurred if partitions were
manually mounted (with: mount -a) and gdm manually started under version
227-1

Best,
Ara



On 9 October 2015 at 14:08, Martin Pitt  wrote:

> Control: tag -1 pending
>
> I found the offending commit, reverted it, and currently run tests.
> I'll upload 227-2 within the hour.
>
> Ara Keary [2015-10-09 12:55 +0200]:
> > Other symptom, if helpful: trying to log with rsa/dsa key fails on every
> > machine i can access to.
> > Could all this mess be related to a (pam) *system-wise authentification
> > problem*?
>
> Might be #801354?
>
> > Maintainers: i really truly appreciate ∞ly your work, but do you test
> > updates before uploading? ...
>
> We do of course, with both automated and manual tests, but #801354 is
> a race condition which doesn't happen everywhere, and this bug doesn't
> actually surface at all until you look at the logs (for non-root
> logins it's just cosmetical). I added a test case for this now,
> though.
>
> Sorry, but sh** happens :-/
>
> Martin
>
> --
> Martin Pitt| http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
>

Bug#798900: [Debian-med-packaging] Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

[Paul Wise]

On Sun, 2015-10-11 at 13:38 +0100, Sascha Steinbiss wrote:

> It looks like JSHint is not a hard requirement but will just not be used if 
> it’s
> not there:
> https://github.com/DataTables/DataTablesSrc/blob/master/build/make.sh#L58
> Otherwise I wouldn't mind patching the build script to not use it.

Aha, great!

> In principle I agree here.

Good to hear :)

> Sure. Could you probably give me access to collab-maint then? As a DM I only 
> have a
> guest account on Alioth and someone has to approve me. I have sent a request 
> via
> the Alioth web interface quite some time ago but received no response.

I don't have admin access to collab-maint. 

As per the policy, you should have your sponsor or potential sponsor
advocate you in order to get access. Probably someone from debian-med.

https://lists.debian.org/debian-devel-announce/2012/01/msg6.html

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#801535: asterisk: FTBFS in sid: linker errors due to missing B-D

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2015-10-11 23:34:32)
> Quoting Andreas Beckmann (2015-10-11 22:58:11)
>> asterisk FTBFS in sid:
>> 
>> [...]
>> x86_64-linux-gnu-gcc -o pjsip/dialplan_functions.o -c 
>> pjsip/dialplan_functions.c -MD -MT pjsip/dialplan_functions.o -MF 
>> .pjsip_dialplan_functions.o.d -MP -pthread 
>> -I/tmp/buildd/asterisk-13.1.0~dfsg/include -fgnu89-inline -g -O2 -fPIE 
>> -fstack-protector-strong -Wformat -Werror=format-security 
>> -D_FORTIFY_SOURCE=2   -I/usr/include/libxml2 -pipe -Wall -Wstrict-prototypes 
>> -Wmissing-prototypes -Wmissing-declarations  -fPIC 
>> -DAST_MODULE=\"chan_pjsip\"  -DPJ_AUTOCONF=1 -DPJ_IS_BIG_ENDIAN=0 
>> -DPJ_IS_LITTLE_ENDIAN=1 -DOPENSSL_NO_SSL2=1   
>> /tmp/buildd/asterisk-13.1.0~dfsg/build_tools/make_linker_version_script 
>> chan_pjsip "" "/tmp/buildd/asterisk-13.1.0~dfsg"
>> x86_64-linux-gnu-gcc  -o chan_pjsip.so -pthread -fPIE -pie -Wl,-z,relro 
>> -Wl,-z,now-shared -Wl,--version-script,chan_pjsip.exports,--warn-common  
>> chan_pjsip.o pjsip/dialplan_functions.o  -lpjsua2 -lstdc++ -lpjsua 
>> -lpjsip-ua -lpjsip-simple -lpjsip -lpjmedia-codec -lpjmedia 
>> -lpjmedia-videodev -lpjmedia-audiodev -lpjmedia -lpjnath -lpjlib-util -lsrtp 
>> -lpj -lm -lrt -lpthread -lSDL2 -lavformat-ffmpeg -lavcodec-ffmpeg 
>> -lswscale-ffmpeg -lavutil-ffmpeg -lv4l2 -lopencore-amrnb -lopencore-amrwb 
>> /usr/bin/ld: cannot find -lSDL2
>> /usr/bin/ld: cannot find -lavformat-ffmpeg
>> /usr/bin/ld: cannot find -lavcodec-ffmpeg
>> /usr/bin/ld: cannot find -lswscale-ffmpeg
>> /usr/bin/ld: cannot find -lavutil-ffmpeg
>> /usr/bin/ld: cannot find -lv4l2
>> /usr/bin/ld: cannot find -lopencore-amrnb
>> /usr/bin/ld: cannot find -lopencore-amrwb
>> collect2: error: ld returned 1 exit status
>> 
>> These seem to be several Build-Depends missing, e.g. libsdl2-dev, 
>> libv4l-dev and the ffmpeg bits seem to have been reorganized as well.
>
> I suspect ig might be pjsip growing dependencies on those libraries 
> and injecting linkage flags into Asterisk, but instead of actively 
> avoiding those it seems more sensible to me to consider solving 
> bug#531728.

No, must be some other dependency than pjproject: I thought of 
bug#795825 that that one isn't fixed yet.

My suggestion still stand: Have asterisk build-depend these: 
libavcodec-dev libswscale-dev libsdl-image1.2-dev

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: severity of 572828 is normal, severity of 785906 is normal, severity of 572829 is normal ...

[Debian Bug Tracking System]

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

> severity 572828 normal
Bug #572828 {Done: Scott Kitterman } 
[ftp.debian.org] RM: gurlchecker -- RoQA; abandoned
Severity set to 'normal' from 'serious'
> severity 785906 normal
Bug #785906 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: gstreamer-sharp -- RoM; obsolete
Severity set to 'normal' from 'serious'
> severity 572829 normal
Bug #572829 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: gsnmp -- RoQA; abandoned
Severity set to 'normal' from 'serious'
> severity 572830 normal
Bug #572830 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: scli -- RoQA; abandoned
Severity set to 'normal' from 'serious'
> severity 801171 normal
Bug #801171 [ftp.debian.org] RM: randomize-lines -- ROM; deprecated, replaced 
by shuf
Severity set to 'normal' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

[Paul Wise]

On Sun, 2015-10-11 at 10:41 +0200, Ole Streicher wrote:

> The Readme.md states that the files in the DataTables were generated
> from the ones in DataTablesSrc, which means that DataTablesSrc contains
> the *sources*.

That is exactly my point.

> Specifically,
> https://github.com/DataTables/DataTablesSrc/blob/master/js/DataTables.js
> contains a line 25 (> 1024 characters long):
> which triggers the lintian error in the case of python-astropy. I don't
> see why this is real, since:

Yes, I hadn't seen that the line lintian was triggered on in
jquery.dataTables.js was also in one of the source files DataTables.js
so I had assumed that the build process was creating this line.

> --> lintian uses some heuristics here, which does obviously not match
> the real life. Until this is improved, I would (again) propose to use
> the "experimental" tag here; this is what this tag is for.

Agreed that the heuristics need adjusting (some changes are in git) and
that the tag should be marked as possible rather than certain. I don't
think wild-guess is appropriate though.

> I would also propose to consider removing at least the line length test
> for comments.

That seems reasonable.

> They don't; at least not in the case of python-astropy.

The do actually, astropy/extern/js/jquery.dataTables.js is an embedded
code copy of a build artefact. In other words it is from DataTables
instead of from DataTablesSrc. Personally I would repack the tarball to
remove it and package DataTablesSrc separately.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

On Mon, 2015-10-12 at 11:51 +0200, Bastian Venthur wrote:
> Hi Ritesh,
> 
> could you provide the value of `PackageName` (as in your stack trace
> line 155, in FetchBugsDebian) so I can try to reproduce this bug?
> 
> Trying it with the package you seem to query, I don't get an error:
> 
> In [2]: bts.get_bugs('package', 'libgstreamer-plugins-base1.0-0')
> Out[2]: []


Thanks for the quick reply. Please find attached the full console log.
apt-offline is multi-threaded when downloading the data. But with the
 --verbose switch used, you should be able to relate the Thread-N
number.


Also there are mulitple exceptions coming from debianbts module.
And FYI, I also bundle the debianbts module with apt-offline so that
the user can download the bug reports on a Windows box too. The
currently bundled version of debianbts module works fine.




rrs@learner:~/devel/apt-offline/apt-offline (master)$ ./apt-offline get
/var/tmp/set.uris --bug-reports --threads 5 --cache-dir
/var/cache/apt/archives/ --verbose
VERBOSE: Namespace(bundle_file=None,
cache_dir='/var/cache/apt/archives/', deb_bugs=True,
disable_md5check=False, download_dir=None, func=, get='/var/tmp/set.uris', num_of_threads=5,
proxy_host=None, proxy_port=None, simulate=False, socket_timeout=30,
verbose=True)
VERBOSE: Default timeout now is: 30.

Fetching APT Data

VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/d/dconf-edit
or/dconf-editor_3.18.0-1_amd64.deb'", 'dconf-editor_3.18.0-
1_amd64.deb', '145296', 'MD5Sum:15b56ce956d4707bad2a543d97bf6d27\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/d
/dconf-editor/dconf-editor_3.18.0-1_amd64.deb
VERBOSE: Stripped item FILE is: dconf-editor_3.18.0-1_amd64.deb
VERBOSE: Stripped item SIZE is: 145296
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:15b56ce956d4707bad2a543d97bf6d27
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/geoclue-2.
0/geoclue-2.0_2.3.0-2_amd64.deb'", 'geoclue-2.0_2.3.0-2_amd64.deb',
'82344', 'MD5Sum:c9217f9d30e8ae44fb546758a04a2b71\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/geoclue-2.0/geoclue-2.0_2.3.0-2_amd64.deb
VERBOSE: Stripped item FILE is: geoclue-2.0_2.3.0-2_amd64.deb
VERBOSE: Stripped item SIZE is: 82344
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:c9217f9d30e8ae44fb546758a04a2b71
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/gstreamer1
.0/libgstreamer1.0-0_1.6.0-1_amd64.deb'", 'libgstreamer1.0-0_1.6.0-
1_amd64.deb', '1804346', 'MD5Sum:d64ae10322697555dcc5842c8a275387\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/gstreamer1.0/libgstreamer1.0-0_1.6.0-1_amd64.deb
VERBOSE: Stripped item FILE is: libgstreamer1.0-0_1.6.0-1_amd64.deb
VERBOSE: Stripped item SIZE is: 1804346
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:d64ae10322697555dcc5842c8a275387
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/gstreamer1
.0/gir1.2-gstreamer-1.0_1.6.0-1_amd64.deb'", 'gir1.2-gstreamer-
1.0_1.6.0-1_amd64.deb', '958360',
'MD5Sum:72a963e8024d1767c19aab40750640a6\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/gstreamer1.0/gir1.2-gstreamer-1.0_1.6.0-1_amd64.deb
VERBOSE: Stripped item FILE is: gir1.2-gstreamer-1.0_1.6.0-1_amd64.deb
VERBOSE: Stripped item SIZE is: 958360
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:72a963e8024d1767c19aab40750640a6
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/gst-plugin
s-base1.0/libgstreamer-plugins-base1.0-0_1.6.0-1_amd64.deb'",
'libgstreamer-plugins-base1.0-0_1.6.0-1_amd64.deb', '1470546',
'MD5Sum:1bfc596cc2de01fa51ca0a64b61d9a0e\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/gst-plugins-base1.0/libgstreamer-plugins-base1.0-0_1.6.0-1_amd64.deb
VERBOSE: Stripped item FILE is: libgstreamer-plugins-base1.0-0_1.6.0-
1_amd64.deb
VERBOSE: Stripped item SIZE is: 1470546
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:1bfc596cc2de01fa51ca0a64b61d9a0e
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/gst-plugin
s-base1.0/gir1.2-gst-plugins-base-1.0_1.6.0-1_amd64.deb'", 'gir1.2-gst-
plugins-base-1.0_1.6.0-1_amd64.deb', '912402',
'MD5Sum:2a0637d2e32543aed3cbe0627b205538\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/gst-plugins-base1.0/gir1.2-gst-plugins-base-1.0_1.6.0-1_amd64.deb
VERBOSE: Stripped item FILE is: gir1.2-gst-plugins-base-1.0_1.6.0-
1_amd64.deb
VERBOSE: Stripped item SIZE is: 912402
VERBOSE: Stripped item CHECKSUM is:
MD5Sum:2a0637d2e32543aed3cbe0627b205538
VERBOSE: Item is ["'http://ftp.debian.org/debian/pool/main/g/gst-plugin
s-base1.0/gstreamer1.0-plugins-base_1.6.0-1_amd64.deb'", 'gstreamer1.0-
plugins-base_1.6.0-1_amd64.deb', '1345928',
'MD5Sum:bf5f101733f1a2a4f42ae8e5ed8cfff2\n']
VERBOSE: Stripped item URL is: http://ftp.debian.org/debian/pool/main/g
/gst-plugins-base1.0/gstreamer1.0-plugins-base_1.6.0-1_amd64.deb
VERBOSE: Stripped item FILE is: gstreamer1.0-plugins-base_1.6.0-
1_amd64.deb
VERBOSE: Stripped item SIZE is: 1345928

Bug#801502: apt-offline: missing dependency on python-apt in jessie

[Paul Wise]

On Mon, 2015-10-12 at 14:15 +0530, Ritesh Raj Sarraf wrote:

> There may be more bugs with that version.

I am working around two bugs but they are present in wheezy too:

https://bugs.debian.org/747064
https://bugs.debian.org/747163

It would be great if you could propose updates to fix these issues.

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable

> Does it work for you with your proposed fix ?

Yes, perfectly.

> My desire was to push 1.6.1 into Jessie.
> But I guess that won't be allowed. :-(

I don't know what changes were made but that seems unlikely to be allowed.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Processed: block 801502 with 801580

[Debian Bug Tracking System]

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

> block 801502 with 801580
Bug #801502 [apt-offline] apt-offline: missing dependency on python-apt in 
jessie
801502 was not blocked by any bugs.
801502 was not blocking any bugs.
Added blocking bug(s) of 801502: 801580
> thanks
Stopping processing here.

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

Processed: Re: Bug#801502: apt-offline: missing dependency on python-apt in jessie

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #801502 [apt-offline] apt-offline: missing dependency on python-apt in 
jessie
Bug 801502 cloned as bug 801587
801580 was not blocked by any bugs.
801580 was blocking: 801502
Added blocking bug(s) of 801580: 801587
> retitle -2 "apt-offline (old) stable fixes for Wheezy"
Bug #801587 [apt-offline] apt-offline: missing dependency on python-apt in 
jessie
Changed Bug title to '"apt-offline (old) stable fixes for Wheezy"' from 
'apt-offline: missing dependency on python-apt in jessie'

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

Bug#801502: apt-offline: missing dependency on python-apt in jessie

[Ritesh Raj Sarraf]

Control: clone -1 -2
Control: retitle -2 "apt-offline (old) stable fixes for Wheezy"

On Mon, 2015-10-12 at 17:35 +0800, Paul Wise wrote:
> On Mon, 2015-10-12 at 14:15 +0530, Ritesh Raj Sarraf wrote:
> 
> > There may be more bugs with that version.
> 
> I am working around two bugs but they are present in wheezy too:
> 
> https://bugs.debian.org/747064
> https://bugs.debian.org/747163
> 
> It would be great if you could propose updates to fix these issues.
> 

Okay!! Hopefully the above commands will clone the bugs correct. I will
look into them. Thanks.

> https://www.debian.org/doc/manuals/developers-
> reference/pkgs.html#upload-stable
> 
> > Does it work for you with your proposed fix ?
> 
> Yes, perfectly.

Great. I already have proposed a patch to release team @ #801580


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#801585: python-debianbts: get_bugs interface is broken

[Bastian Venthur]

Hi Ritesh,

could you provide the value of `PackageName` (as in your stack trace
line 155, in FetchBugsDebian) so I can try to reproduce this bug?

Trying it with the package you seem to query, I don't get an error:

In [2]: bts.get_bugs('package', 'libgstreamer-plugins-base1.0-0')
Out[2]: []


Cheers,

Bastian




-- 
Dr. Bastian Venthur  http://venthur.de
Debian Developer venthur at debian org

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

Package: python-debianbts
Version: 2.5
Severity: grave

Hello Bastian,

Both, in 2.4 and 25, the get_bugs() has been broken :-(


rrs@learner:~/devel/apt-offline/apt-offline (master)$ ./apt-offline get 
/var/tmp/set.uris --bug-reports --threads 5 --cache-dir /var/cache/apt/archives/

Fetching APT Data

WARNING: If you are on a slow connection, it is good to
WARNING: limit the number of threads to a low number like 2.
WARNING: Else higher number of threads executed could cause
WARNING: network congestion and timeouts.

Fetched bug reports for package libgstreamer-plugins-base1.0-0. 
   
libgstreamer-plugins-base1.0-0 copied from local cache directory 
/var/cache/apt/archives/.  
No handlers could be found for logger "pysimplesoap.simplexml"
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineLib.py",
 line 636, in run
self.responseQueue.put( self.WorkerFunction( item, thread_name ) )
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 638, in DataFetcher
if FetchBugReportsDebian.FetchBugsDebian(PackageName) in [1,2]:
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 155, in FetchBugsDebian
self.bugs_list = debianbts.get_bugs( 'package', PackageName )
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 409, in get_bugs
reply = soap_client.call('get_bugs', method_el)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 260, in 
call
self.xml_response = self.send(method, self.xml_request)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 317, in 
send
log.debug('\n'.join(["%s: %s" % (k, v) for k, v in response.items()]))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x90 in position 18: 
ordinal not in range(128)

Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineLib.py",
 line 636, in run
self.responseQueue.put( self.WorkerFunction( item, thread_name ) )
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 638, in DataFetcher
if FetchBugReportsDebian.FetchBugsDebian(PackageName) in [1,2]:
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 155, in FetchBugsDebian
self.bugs_list = debianbts.get_bugs( 'package', PackageName )
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 409, in get_bugs
reply = soap_client.call('get_bugs', method_el)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 262, in 
call
jetty=self.__soap_server in ('jetty',))
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/simplexml.py", line 56, 
in __init__
self.__document = xml.dom.minidom.parseString(text)
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: syntax error: line 1, column 0

Segmentation fault (core dumped)
2015-10-12 / 15:05:16 ♒♒♒☹  => 139  

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

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

Versions of packages python-debianbts depends on:
ii  python-pysimplesoap  1.16-1
pn  python:any   

python-debianbts recommends no packages.

python-debianbts suggests no packages.

-- no debconf information

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

On Mon, 2015-10-12 at 15:51 +0530, Ritesh Raj Sarraf wrote:
> Exception in thread Thread-2:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 810, in
> __bootstrap_inner
> self.run()
>   File "/usr/lib/python2.7/threading.py", line 763, in run
> self.__target(*self.__args, **self.__kwargs)
>   File "/media/SSHD/rrs-home/devel/apt-offline/apt-
> offline/apt_offline_core/AptOfflineLib.py", line 636, in run
> self.responseQueue.put( self.WorkerFunction( item, thread_name )
> )
>   File "/media/SSHD/rrs-home/devel/apt-offline/apt-
> offline/apt_offline_core/AptOfflineCoreLib.py", line 638, in
> DataFetcher
> if FetchBugReportsDebian.FetchBugsDebian(PackageName) in [1,2]:
>   File "/media/SSHD/rrs-home/devel/apt-offline/apt-
> offline/apt_offline_core/AptOfflineCoreLib.py", line 155, in
> FetchBugsDebian
> self.bugs_list = debianbts.get_bugs( 'package', PackageName )
>   File "/usr/lib/python2.7/dist-packages/debianbts.py", line 409, in
> get_bugs
> reply = soap_client.call('get_bugs', method_el)
>   File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py",
> line
> 260, in call
> self.xml_response = self.send(method, self.xml_request)
>   File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py",
> line
> 313, in send
> location, http_method, body=xml, headers=headers)
>   File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line
> 1607, in request
> (response, content) = self._request(conn, authority, uri,
> request_uri, method, body, headers, redirections, cachekey)
>   File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line
> 1349, in _request
> (response, content) = self._conn_request(conn, request_uri,
> method,
> body, headers)
>   File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line
> 1305, in _conn_request
> response = conn.getresponse()
>   File "/usr/lib/python2.7/httplib.py", line 1131, in getresponse
> response.begin()
>   File "/usr/lib/python2.7/httplib.py", line 453, in begin
> version, status, reason = self._read_status()
>   File "/usr/lib/python2.7/httplib.py", line 417, in _read_status
> raise BadStatusLine(line)
> BadStatusLine: ''
> 

This one, BadStatusLine, has been a headache for me too.
It is a Python bug. https://bugs.python.org/issue8823


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#801502: apt-offline: missing dependency on python-apt in jessie

[Ritesh Raj Sarraf]

Hello Paul,


Thank you for the bug report.

On Sun, 2015-10-11 at 19:18 +0800, Paul Wise wrote:
> apt-offline appears to unconditionally use python-apt in jessie but
> doesn't depend on it. The fix is to either depend on python-apt or:
> 
> Replace this from jessie:
> 
> #Instantiate Apt based on what we have. For now, fall to apt
> only
> AptInst = AptManip(Str_SetArg, Simulate=Bool_TestWindows,
> AptType="python-apt")
> 
> With this from stretch:
> 
>         #Instantiate Apt based on what we have. For now, fall to apt
> only
> if PythonApt is True:
> AptInst = AptManip(Str_SetArg,
> Simulate=Bool_TestWindows, AptType="python-apt")
> else:
> AptInst = AptManip(Str_SetArg,
> Simulate=Bool_TestWindows, AptType="apt")
> 

There may be more bugs with that version. Does it work for you with
your proposed fix ?

My desire was to push 1.6.1 into Jessie. But I guess that won't be
allowed. :-(


>         
-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#800689: telepathy-glib: diff for NMU version 0.24.1-1.1

[Iain Lane]

Hi,

I prepared an NMU for telepathy-glib and uploaded it without delay.
Patch attached.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
diff -Nru telepathy-glib-0.24.1/debian/changelog telepathy-glib-0.24.1/debian/changelog
--- telepathy-glib-0.24.1/debian/changelog	2014-09-16 15:49:57.0 +0100
+++ telepathy-glib-0.24.1/debian/changelog	2015-10-12 10:08:02.0 +0100
@@ -1,3 +1,12 @@
+telepathy-glib (0.24.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch:
+Take patch from upstream bug #92245 to not use the same test name more
+than once, which causes build failures with glib 2.46. (Closes: #800689)
+
+ -- Iain Lane   Mon, 12 Oct 2015 10:08:02 +0100
+
 telepathy-glib (0.24.1-1) unstable; urgency=medium
 
   * New upstream stable release
diff -Nru telepathy-glib-0.24.1/debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch telepathy-glib-0.24.1/debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch
--- telepathy-glib-0.24.1/debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch	1970-01-01 01:00:00.0 +0100
+++ telepathy-glib-0.24.1/debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch	2015-10-12 10:07:54.0 +0100
@@ -0,0 +1,93 @@
+From 838bb888d80f75fb29653656c571f9f32d0255f0 Mon Sep 17 00:00:00 2001
+From: Iain Lane 
+Date: Fri, 2 Oct 2015 15:19:23 +0100
+Subject: [PATCH] Don't use the same test name for multiple tests
+
+GLib 2.46.0 doesn't allow this any more, and so the testsuite fails.
+
+https://bugs.freedesktop.org/show_bug.cgi?id=92245
+
+---
+ tests/dbus/account.c | 10 +-
+ tests/dbus/cm.c  |  2 +-
+ tests/dbus/contact-list-client.c |  2 +-
+ tests/dbus/contact-lists.c   |  2 +-
+ 4 files changed, 8 insertions(+), 8 deletions(-)
+
+diff --git a/tests/dbus/account.c b/tests/dbus/account.c
+index 1df043a..8fa7514 100644
+--- a/tests/dbus/account.c
 b/tests/dbus/account.c
+@@ -980,7 +980,7 @@ main (int argc,
+ 
+   g_test_add ("/account/reconnect", Test, NULL, setup_service, test_reconnect,
+   teardown_service);
+-  g_test_add ("/account/reconnect", Test, "vardict", setup_service,
++  g_test_add ("/account/reconnect/vardict", Test, "vardict", setup_service,
+   test_reconnect, teardown_service);
+ 
+   g_test_add ("/account/prepare/success", Test, NULL, setup_service,
+@@ -989,17 +989,17 @@ main (int argc,
+   g_test_add ("/account/connection", Test, NULL, setup_service,
+   test_connection, teardown_service);
+ 
+-  g_test_add ("/account/storage", Test, "first", setup_service, test_storage,
++  g_test_add ("/account/storage/first", Test, "first", setup_service, test_storage,
+   teardown_service);
+-  g_test_add ("/account/storage", Test, "later", setup_service, test_storage,
++  g_test_add ("/account/storage/later", Test, "later", setup_service, test_storage,
+   teardown_service);
+ 
+   g_test_add ("/account/avatar", Test, NULL, setup_service, test_avatar,
+   teardown_service);
+ 
+-  g_test_add ("/account/addressing", Test, "first", setup_service,
++  g_test_add ("/account/addressing-first", Test, "first", setup_service,
+   test_addressing, teardown_service);
+-  g_test_add ("/account/addressing", Test, "later", setup_service,
++  g_test_add ("/account/addressing-later", Test, "later", setup_service,
+   test_addressing, teardown_service);
+ 
+   return tp_tests_run_with_bus ();
+diff --git a/tests/dbus/cm.c b/tests/dbus/cm.c
+index ad42854..c386d60 100644
+--- a/tests/dbus/cm.c
 b/tests/dbus/cm.c
+@@ -1187,7 +1187,7 @@ main (int argc,
+ 
+   g_test_add ("/cm/list", Test, GINT_TO_POINTER (0),
+   setup, test_list, teardown);
+-  g_test_add ("/cm/list", Test, GINT_TO_POINTER (USE_OLD_LIST),
++  g_test_add ("/cm/list/use-old-list", Test, GINT_TO_POINTER (USE_OLD_LIST),
+   setup, test_list, teardown);
+ 
+   return tp_tests_run_with_bus ();
+diff --git a/tests/dbus/contact-list-client.c b/tests/dbus/contact-list-client.c
+index a3f878a..bb4895d 100644
+--- a/tests/dbus/contact-list-client.c
 b/tests/dbus/contact-list-client.c
+@@ -577,7 +577,7 @@ main (int argc,
+ 
+   g_test_add ("/contact-list-client/contact-list/properties", Test,
+   GUINT_TO_POINTER (FALSE), setup, test_contact_list_properties, teardown);
+-  g_test_add ("/contact-list-client/contact-list/properties", Test,
++  g_test_add ("/contact-list-client/contact-list/properties/props-only", Test,
+   GUINT_TO_POINTER (TRUE), setup, test_contact_list_properties, teardown);
+ 
+   return tp_tests_run_with_bus ();
+diff --git a/tests/dbus/contact-lists.c b/tests/dbus/contact-lists.c
+index 

Bug#800617: marked as done (Fails to provide secrets)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 11:05:00 +
with message-id 
and subject line Bug#800617: fixed in gnome-keyring 3.18.0-3
has caused the Debian Bug report #800617,
regarding Fails to provide secrets
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.)


-- 
800617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-keyring
Version: 3.18.0-1
Severity: grave

Since upgrading gnome-keyring from 3.16.0-4 to 3.18.0-1, applications
trying to retrieve secrets from gnome-keyring no longer can.  I see log
messages like the following:

Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5801]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
Oct 01 10:36:37 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't access 
control socket: /run/user/1000/keyring/control: No such file or directory
[...]
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't register in 
session: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-keyring-daemon[5803]: couldn't communicate 
with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: ** Message: couldn't 
communicate with already running daemon: Timeout was reached
Oct 01 10:36:38 jtriplet-mobl1 gnome-session[5731]: 
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Oct 01 10:36:39 jtriplet-mobl1 gnome-keyring-daemon[5844]: couldn't register in 
session: Timeout was reached
[...]
Oct 01 10:37:03 jtriplet-mobl1 gnome-keyring-daemon[5808]: couldn't request 
name 'org.freedesktop.secrets' on session bus: Timeout was reached
[...]
Oct 01 10:48:34 jtriplet-mobl1 org.gnome.evolution.dataserver.Sources4[5783]: 
server_side_source_credentials_lookup_cb: Failed to lookup password: Error 
calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
Oct 01 10:48:35 jtriplet-mobl1 org.gnome.seahorse.Application[5783]: 
(seahorse:8293): seahorse-WARNING **: gkr-backend.vala:85: couldn't connect to 
secret service: Error calling StartServiceByName for org.freedesktop.secrets: 
Timeout was reached

In addition to that, it also looks like every time an application tries to
access the org.freedesktop.secrets service, dbus spawns an instance of
gnome-keyring with the --foreground option, likely based on
/usr/share/dbus-1/services/org.freedesktop.secrets.service ; does this conflict
with the instance already run via /etc/xdg/autostart?

- Josh Triplett

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

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

Versions of packages gnome-keyring depends on:
ii  dbus-x11 1.10.0-3
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-22
ii  libcap-ng0   0.7.7-1
ii  libcap2-bin  1:2.24-11
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.46.0-2
ii  p11-kit  0.23.1-3
ii  pinentry-gnome3  0.9.5-4

Versions of packages gnome-keyring recommends:
ii  libpam-gnome-keyring  3.18.0-1

gnome-keyring suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-keyring
Source-Version: 3.18.0-3

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

Bug#801535: asterisk: FTBFS in sid: linker errors due to missing B-D

[Tzafrir Cohen]

On Sun, Oct 11, 2015 at 11:34:32PM +0200, Jonas Smedegaard wrote:
> Quoting Andreas Beckmann (2015-10-11 22:58:11)
> > asterisk FTBFS in sid:
> > 
> > [...]
> > x86_64-linux-gnu-gcc -o pjsip/dialplan_functions.o -c 
> > pjsip/dialplan_functions.c -MD -MT pjsip/dialplan_functions.o -MF 
> > .pjsip_dialplan_functions.o.d -MP -pthread 
> > -I/tmp/buildd/asterisk-13.1.0~dfsg/include -fgnu89-inline -g -O2 -fPIE 
> > -fstack-protector-strong -Wformat -Werror=format-security 
> > -D_FORTIFY_SOURCE=2   -I/usr/include/libxml2 -pipe -Wall 
> > -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations  -fPIC 
> > -DAST_MODULE=\"chan_pjsip\"  -DPJ_AUTOCONF=1 -DPJ_IS_BIG_ENDIAN=0 
> > -DPJ_IS_LITTLE_ENDIAN=1 -DOPENSSL_NO_SSL2=1   
> > /tmp/buildd/asterisk-13.1.0~dfsg/build_tools/make_linker_version_script 
> > chan_pjsip "" "/tmp/buildd/asterisk-13.1.0~dfsg"
> > x86_64-linux-gnu-gcc  -o chan_pjsip.so -pthread -fPIE -pie -Wl,-z,relro 
> > -Wl,-z,now-shared -Wl,--version-script,chan_pjsip.exports,--warn-common 
> >  chan_pjsip.o pjsip/dialplan_functions.o  -lpjsua2 -lstdc++ -lpjsua 
> > -lpjsip-ua -lpjsip-simple -lpjsip -lpjmedia-codec -lpjmedia 
> > -lpjmedia-videodev -lpjmedia-audiodev -lpjmedia -lpjnath -lpjlib-util 
> > -lsrtp -lpj -lm -lrt -lpthread -lSDL2 -lavformat-ffmpeg -lavcodec-ffmpeg 
> > -lswscale-ffmpeg -lavutil-ffmpeg -lv4l2 -lopencore-amrnb -lopencore-amrwb 
> > /usr/bin/ld: cannot find -lSDL2
> > /usr/bin/ld: cannot find -lavformat-ffmpeg
> > /usr/bin/ld: cannot find -lavcodec-ffmpeg
> > /usr/bin/ld: cannot find -lswscale-ffmpeg
> > /usr/bin/ld: cannot find -lavutil-ffmpeg
> > /usr/bin/ld: cannot find -lv4l2
> > /usr/bin/ld: cannot find -lopencore-amrnb
> > /usr/bin/ld: cannot find -lopencore-amrwb
> > collect2: error: ld returned 1 exit status
> > 
> > These seem to be several Build-Depends missing, e.g. libsdl2-dev, libv4l-dev
> > and the ffmpeg bits seem to have been reorganized as well.
> 
> I suspect ig might be pjsip growing dependencies on those libraries and 
> injecting linkage flags into Asterisk, but instead of actively avoiding 
> those it seems more sensible to me to consider solving bug#531728.

You are right. The git version of pjsip should look better.

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

Bug#798900: lintian: false positive: source-is-missing for non-minified JS files

[Ole Streicher]

On 12.10.2015 09:58, Paul Wise wrote:
>> They don't; at least not in the case of python-astropy.
> The do actually, astropy/extern/js/jquery.dataTables.js is an embedded
> code copy of a build artefact.

How do you see this? It is well formatted, including comments etc. In
the packages I maintain I have source files which are much worse to
maintain. Again my question: for what kind of editing you would prefer a
different ("original") source? What do you miss here?

And, again: would you consider any automatically inserted line, like CVS
tags as non-source, and reject these files from Debian? What is the
difference here?

> In other words it is from DataTables instead of from DataTablesSrc. 
> Personally I would repack the tarball to remove it and package DataTablesSrc 
> separately.

How do you come to that?

$ wget
https://raw.githubusercontent.com/DataTables/DataTablesSrc/1_9/media/js/jquery.dataTables.js
\
-Ogit-jquery.dataTables.js
$ wget
https://sources.debian.net/data/main/p/python-astropy/1.0.4-1/astropy/extern/js/jquery.dataTables.js
\
-Oastropy-git-jquery.dataTables.js
$ diff -c git-jquery.dataTables.js astropy-git-jquery.dataTables.js

Files git-jquery.dataTables.js and astropy-git-jquery.dataTables.js are
identical

Don't you have the feeling that you hunt some ghosts here? Please
explain me what this error is about; I feel a bit upset now that you put
some "rules" what is a source and what not, which are nowhere defined
(the only definition I have is the one from GPL, which means "preferred
to edit"), and them randomly trigger some files without a reason, and
without any explanation.

There is no definition (at least, as I know), that requires source files
to be (completely) manually generated,
There is no proof that the file in question is manually generated.
There is nothing that I could discuss with upstream to change the file
-- actually the file was put there by upstream after I asked them to
include the source [1].

But I get a lintian complaint, and then answers like "remove this file",
or "this is a borderline case" or similar. I *am* aware of having the
sources included; however it would be really nice if you were a bit
careful here as well, and at least explain why do you think that this
file is not a source, and by which definition.

Best regards

Ole

[1] https://github.com/astropy/astropy/issues/1992

Bug#801582: grub-pc: default entry becomes Halt once (for setting alarm) => no boot

[Eric Valette]

Package: grub-pc
Version: 2.02~beta2-28
Severity: critical
Justification: breaks the whole system


Today my system did not boot because the default entry was set
to  Halt once (for setting alarm). This emans that if I upgrade
machines where I have only ssh access, no console, I'm dead.
And I have many both at work and home.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/sda6 /var ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /usr ext4 rw,relatime,data=ordered 0 0
/dev/sda8 /home ext4 rw,relatime,data=ordered 0 0
/dev/sda7 /usr/local ext4 rw,relatime,data=ordered 0 0
/dev/sda5 /tmp ext2 rw,relatime,errors=continue 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/ata-WDC_WD2500BEKT-75PVMT0_WD-WXP1AC0K6712
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
e305023c-baf2-4e52-9847-d35118d65706
else
  search --no-floppy --fs-uuid --set=root e305023c-baf2-4e52-9847-d35118d65706
fi
font="/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 
--hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 --hint='hd0,msdos2'  
e305023c-baf2-4e52-9847-d35118d65706
else
  search --no-floppy --fs-uuid --set=root e305023c-baf2-4e52-9847-d35118d65706
fi
insmod png
if background_image /share/images/desktop-base/lines-grub.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-a65a0c35-cdf7-40f5-b630-a7835e6ac24b' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'  
a65a0c35-cdf7-40f5-b630-a7835e6ac24b
else
  search --no-floppy --fs-uuid --set=root 
a65a0c35-cdf7-40f5-b630-a7835e6ac24b
fi
echo'Loading Linux 4.1.9 ...'
linux   /boot/vmlinuz-4.1.9 root=/dev/sda1 ro rootfstype=ext4 
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-a65a0c35-cdf7-40f5-b630-a7835e6ac24b' {
menuentry 'Debian GNU/Linux, with Linux 4.1.9' --class debian --class 
gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-4.1.9-advanced-a65a0c35-cdf7-40f5-b630-a7835e6ac24b' {
load_video

Bug#800689: marked as done (new glib makes it fail to build)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 09:24:36 +
with message-id 
and subject line Bug#800689: fixed in telepathy-glib 0.24.1-1.1
has caused the Debian Bug report #800689,
regarding new glib makes it fail to build
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.)


-- 
800689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: telepathy-glib
Version: 0.24.1-1

Using glib 2.46 makes telepathy-glib fails to build due to duplicated tests

FAIL: test-account
==


(telepathy-glib-0.24.1/tests/dbus/.libs/lt-test-account:1891):
GLib-ERROR **: duplicate test case path: /account/reconnect
FAIL test-account (exit status: 133)

FAIL: test-cm
=


(telepathy-glib-0.24.1/tests/dbus/.libs/lt-test-cm:2334): GLib-ERROR **:
duplicate test case path: /cm/list
FAIL test-cm (exit status: 133)

FAIL: test-contact-lists



(telepathy-glib-0.24.1/tests/dbus/.libs/lt-test-contact-lists:2819):
GLib-ERROR **: duplicate test case path:
/contact-lists/cancelled-publish-request
FAIL test-contact-lists (exit status: 133)

FAIL: test-contact-list-client
==


(telepathy-glib-0.24.1/tests/dbus/.libs/lt-test-contact-list-client:2864):
GLib-ERROR **: duplicate test case path:
/contact-list-client/contact-list/properties
FAIL test-contact-list-client (exit status: 133)
--- End Message ---
--- Begin Message ---
Source: telepathy-glib
Source-Version: 0.24.1-1.1

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

Debian distribution maintenance software
pp.
Iain Lane  (supplier of updated telepathy-glib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Oct 2015 10:08:02 +0100
Source: telepathy-glib
Binary: libtelepathy-glib0 libtelepathy-glib-dev libtelepathy-glib0-dbg 
libtelepathy-glib-doc gir1.2-telepathyglib-0.12
Architecture: source
Version: 0.24.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Telepathy maintainers 

Changed-By: Iain Lane 
Description:
 gir1.2-telepathyglib-0.12 - GLib Telepathy connection manager library 
(GObject-Introspection)
 libtelepathy-glib-dev - GLib Telepathy connection manager library (headers)
 libtelepathy-glib-doc - GLib Telepathy library (documentation)
 libtelepathy-glib0 - Telepathy framework - GLib library
 libtelepathy-glib0-dbg - GLib Telepathy library (debug symbols)
Closes: 800689
Changes:
 telepathy-glib (0.24.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/0001-Don-t-use-the-same-test-name-for-multiple-tests.patch:
 Take patch from upstream bug #92245 to not use the same test name more
 than once, which causes build failures with glib 2.46. (Closes: #800689)
Checksums-Sha1:
 4e133aa88f944d5447ebce0bd12c6e288cc5d1cb 2812 telepathy-glib_0.24.1-1.1.dsc
 56ff259fd57fcf415429a893a009f0b3cf4d32d4 30700 
telepathy-glib_0.24.1-1.1.debian.tar.xz
Checksums-Sha256:
 f60b949dd06a22837dc104b91161ae723e28f7f676f5092485d450e43d0c819c 2812 
telepathy-glib_0.24.1-1.1.dsc
 4801da1f0789b1bf82686826cf7dc2766471ef115330eedd7f4ec6f86c311f71 30700 
telepathy-glib_0.24.1-1.1.debian.tar.xz
Files:
 f1ace5cf9b8840c35633adab355a5d06 2812 libs optional 
telepathy-glib_0.24.1-1.1.dsc
 5962e0cf585e5f31e6424a3b110dbca0 30700 libs optional 
telepathy-glib_0.24.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWG3nGAAoJEONS1cUcUEHUx2EP/izbsY93dfqF0T3ikUDgWNMf
YGLHUFho5xUgRijVUWtPZHhqQXNi/Fy5BiY/vTIDun0yZdnbU+lKWkpvBRWP1AzF
17sW7z05Pzbdby83GMKhG+Gmr0zoGiGmYGNoIvsMtnKhj0vsAjFI8UgR8kUo4uAb
g1ln/9p0/pltzVdKRQXvSf64L0kC9lwmFAwHb/QIPBfwS79rukFzGygRu3cFiKYg
XnXQ1SMJO+gQn/+X67+88EED6CLs4lDMoWjcsMl4DD7GvZVWUGWfz+1GqW8JPwVj
tWdGUzBBosVLTO0AddXPnlCmFCClVtobho0Ih8Yw5NmK/1BMJYF9q0jNTqCcgfoB
h2Xhm5UYZDHbF34WzFoQ29C/43Oole1S0Oyruf4ub+UYb4cY1E+l0zvlm+qQ280Y

Bug#801582: grub-pc: default entry becomes Halt once (for setting alarm) => no boot

[Colin Watson]

Control: reassign -1 nvram-wakeup

On Mon, Oct 12, 2015 at 11:06:19AM +0200, Eric Valette wrote:
> Today my system did not boot because the default entry was set
> to  Halt once (for setting alarm). This emans that if I upgrade
> machines where I have only ssh access, no console, I'm dead.
> And I have many both at work and home.
[...]
> ### BEGIN /etc/grub.d/50_nvram_wakeup ###
> # This is an utility for the nvram-wakeup package.  nvram-wakeup
> # programs the alarm of the RTC (Real Time Clock, a clock in the
> # motherboard) so that the system will power up at a certain hour.
> # This menu method provides an easy way to halt the system at reboot,
> # once.  This is needed by nvram-wakeup on certain motherboard, where,
> # for the changes to take effect, you need to restart (not halt) the
> # computer and wait until the BIOS runs (don't need to enter the BIOS
> # setup).
> menuentry "Halt once (for setting alarm)" {
>   halt
> }
> if [ ${nvram_halt_once} ] ; then
>   set nvram_halt_once=
>   save_env nvram_halt_once
>   set default="Halt once (for setting alarm)"
> fi
> ### END /etc/grub.d/50_nvram_wakeup ###

This is provided by the nvram-wakeup package, not by grub2 itself.
Reassigning.

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

Processed: Re: Bug#801582: grub-pc: default entry becomes Halt once (for setting alarm) => no boot

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 nvram-wakeup
Bug #801582 [grub-pc] grub-pc: default entry becomes Halt once (for setting 
alarm) => no boot
Bug reassigned from package 'grub-pc' to 'nvram-wakeup'.
No longer marked as found in versions grub2/2.02~beta2-28.
Ignoring request to alter fixed versions of bug #801582 to the same values 
previously set

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

Bug#797976: Security update debian android

[Welly Ardiansyah]

Please give me security updates. To be able to install debian application
for android

Bug#801585: python-debianbts: get_bugs interface is broken

[Gaetano Guerriero]

On Mon, Oct 12, 2015 at 06:00:34PM +0530, Ritesh Raj Sarraf wrote:
> On Mon, 2015-10-12 at 13:22 +0200, Gaetano Guerriero wrote:
> > 
> > Hello,
> > 
> > is it possible to have access to /var/tmp/set.uris, so I can easily
> > recreate the
> > problem ?
> > I can't reproduce by calling get_bugs() on single packages of the
> > logs.
> > 
> >  Gaetano Guerriero
> 
> Yes. Sure. Please find the file attached.
> 

Thank you very much.

Can you reproduce the bug with version 2.5.1 from sid ?

It is working right on my side.

 Gaetano Guerriero

Bug#801284: marked as done (mlt: B-D on obsolete packages: lib{avformat,avdevice,swscale}-ffmpeg-dev)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 15:31:28 +
with message-id 
and subject line Bug#801284: fixed in mlt 0.9.8-2
has caused the Debian Bug report #801284,
regarding mlt: B-D on obsolete packages: 
lib{avformat,avdevice,swscale}-ffmpeg-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.)


-- 
801284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlt
Version: 0.9.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

mlt FTBFS in sid:

 pbuilder-satisfydepends-dummy : Depends: libavdevice-ffmpeg-dev which is a 
virtual package and is not provided by any available package.

 Depends: libavformat-ffmpeg-dev which is a 
virtual package and is not provided by any available package.

 Depends: libswscale-ffmpeg-dev which is a 
virtual package and is not provided by any available package.

Unable to resolve dependencies!  Giving up...


Andreas
--- End Message ---
--- Begin Message ---
Source: mlt
Source-Version: 0.9.8-2

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated mlt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Oct 2015 15:54:01 +0200
Source: mlt
Binary: libmlt-dev libmlt6 libmlt-data libmlt++-dev libmlt++3 libmlt-dbg melt 
python-mlt
Architecture: source amd64 all
Version: 0.9.8-2
Distribution: unstable
Urgency: medium
Maintainer: Fathi Boudra 
Changed-By: Patrick Matthäi 
Description:
 libmlt++-dev - MLT multimedia framework C++ wrapper (development)
 libmlt++3  - MLT multimedia framework C++ wrapper (runtime)
 libmlt-data - multimedia framework (data)
 libmlt-dbg - multimedia framework (debugging symbols)
 libmlt-dev - multimedia framework (development)
 libmlt6- multimedia framework (runtime)
 melt   - command line media player and video editor
 python-mlt - multimedia framework (Python bindings)
Closes: 801284
Changes:
 mlt (0.9.8-2) unstable; urgency=medium
 .
   * Correct build dependencies.
 Closes: #801284
Checksums-Sha1:
 f9490671ecbe7bd09a9ca4ba437205fadb1c09f7 2420 mlt_0.9.8-2.dsc
 eefdfa920437e9c9d76efb82ea16602f1709f17f 12180 mlt_0.9.8-2.debian.tar.xz
 6eed70af699a03c588c88f66de9effb23d54293c 112204 libmlt++-dev_0.9.8-2_amd64.deb
 7e502a1fab3291084ae23ed63f8b9af7ec81fd91 135756 libmlt++3_0.9.8-2_amd64.deb
 afcf1d9dd0db9e492c35521d05f49da81d968c25 1296934 libmlt-data_0.9.8-2_all.deb
 ef2abfac0682f8825a2c982dcfd0a068c3367e48 2417664 libmlt-dbg_0.9.8-2_amd64.deb
 288d594fc6c9d24a0f3b5034b66148d897687668 141352 libmlt-dev_0.9.8-2_amd64.deb
 f4168677b53aed0147bdaf1473b68a46a67260ad 525552 libmlt6_0.9.8-2_amd64.deb
 a3a5b504789c12e7da03de30e6e1795f828ea7a0 114856 melt_0.9.8-2_amd64.deb
 a0333e1ba5ea2d874f98eaf7d55ced4a19ccc6b2 191164 python-mlt_0.9.8-2_amd64.deb
Checksums-Sha256:
 645d2be3764310c07901c1ed55c31a12dcafafd51ea87a1241a79b5aed17e91d 2420 
mlt_0.9.8-2.dsc
 57a081cbd2318b2b7fdd7add546fa4af37756ccd6148ea86f63fecd75ac288c1 12180 
mlt_0.9.8-2.debian.tar.xz
 fc22658347ce3e38c312d4eaf63ca66ae89baf97160ed6e4c83593f6a6794c6e 112204 
libmlt++-dev_0.9.8-2_amd64.deb
 f43b6ff9c318f55bf5f19ee5ced2bb595265ff1f153066508322141e0c6d6c53 135756 
libmlt++3_0.9.8-2_amd64.deb
 803e28c8539941641b93f0d3d32428083a1fcf39d703618513bf38902a441e2f 1296934 
libmlt-data_0.9.8-2_all.deb
 03725e2c0a558c0c20b0c35c6b315010817b7f6e5b6819acf266ed84aefbfc72 2417664 
libmlt-dbg_0.9.8-2_amd64.deb
 1904453ad9875daa1554af068bf0839eeb22a44cda4ba0cb37c5a950fcc148f0 141352 
libmlt-dev_0.9.8-2_amd64.deb
 161e8cb184e945a4fc7914df7c91a6477748c2b8c5eef62dc9d261d74540652e 525552 
libmlt6_0.9.8-2_amd64.deb
 5fc0d6868d5f18ba54f09342cc0ab841802941f0162dbd9a987321cb1b35a708 114856 
melt_0.9.8-2_amd64.deb
 b00b44b9eefb96c6427116f02b4e08398ea9453527e6571e231575d82cb5ba0d 

Bug#801564: squid: prompting due to modified conffiles which were not modified by the user: /etc/squid/squid.conf

[Amos Jeffries]

We have the problem that the Squid-2.7 configuration settings which are
always present in 2.7 configs, will not run in squid-3.5. In fact will
cause the 3.5 process to halt with a fatal error. So we have a mandatory
automated edit by during the upgrade.

How does one avoid or suppress the dpkg query in this situation?

We are already using the dpkg-maintenance-helper to do all other config
file shuffling. AFAIK that is correctly done.

Amos

Bug#801477: [Ceph-maintainers] Bug#801477: ceph: FTBFS on armel: common/RWLock.h:29:11: error: 'atomic_t' does not name a type

[Gaudenz Steinlin]

Hi

Emilio Pozuelo Monfort  writes:

> Source: ceph
> Version: 0.80.10-1
> Severity: serious
>
> Hi,
>
> Thanks for the upload to fix the FTBFS in sid. Unfortunately this still failed
> on armel:
>
> Excerpt from the log:
>
> In file included from common/HeartbeatMap.h:26:0,
>  from common/HeartbeatMap.cc:21:
> common/RWLock.h:29:11: error: 'atomic_t' does not name a type
>
> See the full log at:
>
> https://buildd.debian.org/status/fetch.php?pkg=ceph=armel=0.80.10-1=1444230749

I hope this is fixed by upstream commit
https://github.com/ceph/ceph/commit/2e09a2c22ab885f8ec81dbc55f2c8fc0f2984543

I'm doing a test build on a porter box right now and will upload a new
revision if this succeeds.

Gaudenz


signature.asc
Description: PGP signature

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

On Mon, 2015-10-12 at 13:22 +0200, Gaetano Guerriero wrote:
> 
> Hello,
> 
> is it possible to have access to /var/tmp/set.uris, so I can easily
> recreate the
> problem ?
> I can't reproduce by calling get_bugs() on single packages of the
> logs.
> 
>  Gaetano Guerriero

Yes. Sure. Please find the file attached.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
'http://ftp.debian.org/debian/pool/main/d/dconf-editor/dconf-editor_3.18.0-1_amd64.deb'
 dconf-editor_3.18.0-1_amd64.deb 145296 MD5Sum:15b56ce956d4707bad2a543d97bf6d27
'http://ftp.debian.org/debian/pool/main/g/geoclue-2.0/geoclue-2.0_2.3.0-2_amd64.deb'
 geoclue-2.0_2.3.0-2_amd64.deb 82344 MD5Sum:c9217f9d30e8ae44fb546758a04a2b71
'http://ftp.debian.org/debian/pool/main/g/gstreamer1.0/libgstreamer1.0-0_1.6.0-1_amd64.deb'
 libgstreamer1.0-0_1.6.0-1_amd64.deb 1804346 
MD5Sum:d64ae10322697555dcc5842c8a275387
'http://ftp.debian.org/debian/pool/main/g/gstreamer1.0/gir1.2-gstreamer-1.0_1.6.0-1_amd64.deb'
 gir1.2-gstreamer-1.0_1.6.0-1_amd64.deb 958360 
MD5Sum:72a963e8024d1767c19aab40750640a6
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-base1.0/libgstreamer-plugins-base1.0-0_1.6.0-1_amd64.deb'
 libgstreamer-plugins-base1.0-0_1.6.0-1_amd64.deb 1470546 
MD5Sum:1bfc596cc2de01fa51ca0a64b61d9a0e
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-base1.0/gir1.2-gst-plugins-base-1.0_1.6.0-1_amd64.deb'
 gir1.2-gst-plugins-base-1.0_1.6.0-1_amd64.deb 912402 
MD5Sum:2a0637d2e32543aed3cbe0627b205538
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-base1.0/gstreamer1.0-plugins-base_1.6.0-1_amd64.deb'
 gstreamer1.0-plugins-base_1.6.0-1_amd64.deb 1345928 
MD5Sum:bf5f101733f1a2a4f42ae8e5ed8cfff2
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-base1.0/gstreamer1.0-x_1.6.0-1_amd64.deb'
 gstreamer1.0-x_1.6.0-1_amd64.deb 921904 MD5Sum:138a180d43449133bf8f15c45a6badf2
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-good1.0/gstreamer1.0-plugins-good_1.6.0-1_amd64.deb'
 gstreamer1.0-plugins-good_1.6.0-1_amd64.deb 2525862 
MD5Sum:2366a26384265f3535a005cfd2570975
'http://ftp.debian.org/debian/pool/main/g/gstreamer-editing-services1.0/libges-1.0-0_1.6.0-1_amd64.deb'
 libges-1.0-0_1.6.0-1_amd64.deb 327686 MD5Sum:f8c1b1063cc60af9f4b11f8abf716dbc
'http://ftp.debian.org/debian/pool/main/g/gstreamer-editing-services1.0/gir1.2-ges-1.0_1.6.0-1_amd64.deb'
 gir1.2-ges-1.0_1.6.0-1_amd64.deb 129890 MD5Sum:24ce9225f37a7e52f209e831adf4fdc6
'http://ftp.debian.org/debian/pool/main/t/totem/totem-plugins_3.18.0-1_amd64.deb'
 totem-plugins_3.18.0-1_amd64.deb 509422 MD5Sum:5bd0900e0fb4395233244ce36cec08b6
'http://ftp.debian.org/debian/pool/main/t/totem/totem_3.18.0-1_amd64.deb' 
totem_3.18.0-1_amd64.deb 438288 MD5Sum:da605ab86770c10e024cde3af1bfbe69
'http://ftp.debian.org/debian/pool/main/t/totem/totem-common_3.18.0-1_all.deb' 
totem-common_3.18.0-1_all.deb 2162578 MD5Sum:89cd0d43fec2b625f07ecc07d877db6d
'http://ftp.debian.org/debian/pool/main/t/totem/gir1.2-totem-1.0_3.18.0-1_amd64.deb'
 gir1.2-totem-1.0_3.18.0-1_amd64.deb 395692 
MD5Sum:40dbe51291c4dfeed3f9c33b32d4e16a
'http://ftp.debian.org/debian/pool/main/t/totem/libtotem0_3.18.0-1_amd64.deb' 
libtotem0_3.18.0-1_amd64.deb 542388 MD5Sum:7ecf9923d577f887b20e58493555d074
'http://ftp.debian.org/debian/pool/main/g/gnome-getting-started-docs/gnome-getting-started-docs_3.18.0-1_all.deb'
 gnome-getting-started-docs_3.18.0-1_all.deb 118846848 
MD5Sum:16db5ca77992c3dc29cff31da6b2c9ee
'http://ftp.debian.org/debian/pool/main/g/gnome-user-share/gnome-user-share_3.18.0-1_amd64.deb'
 gnome-user-share_3.18.0-1_amd64.deb 129008 
MD5Sum:546beebdfbdcdde563dfc17f9cf7ba75
'http://ftp.debian.org/debian/pool/main/g/gst-libav1.0/gstreamer1.0-libav_1.6.0-1_amd64.deb'
 gstreamer1.0-libav_1.6.0-1_amd64.deb 185186 
MD5Sum:dc462b7d4742bbcd15be701ebf34ffea
'http://ftp.debian.org/debian/pool/main/g/gst-plugins-ugly1.0/gstreamer1.0-plugins-ugly_1.6.0-1_amd64.deb'
 gstreamer1.0-plugins-ugly_1.6.0-1_amd64.deb 383042 
MD5Sum:c92dc4107d44b9037d142a23d8a019b0
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/pulseaudio-module-gconf_7.0-1_amd64.deb'
 pulseaudio-module-gconf_7.0-1_amd64.deb 31398 
MD5Sum:d31af6982c263935445d373f5fdca2f1
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/pulseaudio-module-bluetooth_7.0-1_amd64.deb'
 pulseaudio-module-bluetooth_7.0-1_amd64.deb 72038 
MD5Sum:176d45e7378bad2b9ed1134397cdc40f
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/pulseaudio-module-x11_7.0-1_amd64.deb'
 pulseaudio-module-x11_7.0-1_amd64.deb 35630 
MD5Sum:f52025ad81a7bec0f9bd54bbcbc2
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/pulseaudio-utils_7.0-1_amd64.deb'
 pulseaudio-utils_7.0-1_amd64.deb 70146 MD5Sum:458cf6eb7ce43274bd9209f4e3bf7dda
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/libpulsedsp_7.0-1_amd64.deb'
 libpulsedsp_7.0-1_amd64.deb 40524 MD5Sum:c8d44176afb82755afca54690fb25123
'http://ftp.debian.org/debian/pool/main/p/pulseaudio/libpulse-mainloop-glib0_7.0-1_amd64.deb'
 

Bug#801598: nvidia-graphics-drivers: nvidia devices created with permissions 0666 on boot

[Andreas Beckmann]

Source: nvidia-graphics-drivers
Version: 304.125-1
Severity: serious
Tags: security jessie sid stretch experimental

Even though /etc/modprobe.d/nvidia-kernel-common.conf sets the
permissions and owner to root:video 0660, the devices are created
acessible by all local users: root:root 0666.


Andreas

Bug#785782:

[Dan Griswold]

I am now having this same problem. Gdm3 greeter shows no login prompt, no
users.

It happens on two different computers.

gdm3: 3.14.2-2, amd64

The op's workaround doesn't work for me.

Dan

Bug#785915: marked as done (yauap: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:26:51 +
with message-id 
and subject line Bug#801076: Removed package(s) from unstable
has caused the Debian Bug report #785915,
regarding yauap: Please update to GStreamer 1.x
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.)


-- 
785915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yauap
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package yauap currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 0.2.4-3+rm

Dear submitter,

as the package yauap has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/801076

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#785890: marked as done (minirok: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:25:38 +
with message-id 
and subject line Bug#801071: Removed package(s) from unstable
has caused the Debian Bug report #785890,
regarding minirok: Please update to GStreamer 1.x
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.)


-- 
785890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minirok
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package minirok currently still depends on GStreamer 0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 2.1-1+rm

Dear submitter,

as the package minirok has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/801071

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: found 801568 in 0.23-1, found 801568 in 0.9.25-2

[Debian Bug Tracking System]

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

> found 801568 0.23-1
Bug #801568 [linpac,libtevent-dev] libtevent-dev and linpac: error when trying 
to install together
There is no source info for the package 'libtevent-dev' at version '0.23-1' 
with architecture ''
Marked as found in versions linpac/0.23-1.
> found 801568 0.9.25-2
Bug #801568 [linpac,libtevent-dev] libtevent-dev and linpac: error when trying 
to install together
There is no source info for the package 'linpac' at version '0.9.25-2' with 
architecture ''
Marked as found in versions tevent/0.9.25-2.
> thanks
Stopping processing here.

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

Bug#799430: marked as done (libkf5texteditor5: libgit2 upgrade pulls in OpenSSL, conflicting with the GPL)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:50:16 +
with message-id 
and subject line Bug#799430: fixed in ktexteditor 5.15.0-1
has caused the Debian Bug report #799430,
regarding libkf5texteditor5: libgit2 upgrade pulls in OpenSSL, conflicting with 
the GPL
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.)


-- 
799430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkf5texteditor5
Version: 5.13.0-1+b1
Severity: serious
Justification: license violation

Dear Maintainer,

libgit2-23 now links to OpenSSL, which conflicts with the GPL license
used by this package.

See #798421 for more information.


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

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

Versions of packages libkf5texteditor5 depends on:
ii  ktexteditor-data   5.13.0-1
ii  libc6  2.19-20
ii  libgit2-23 0.23.1-1
ii  libjs-underscore   1.7.0~dfsg-1
ii  libkf5archive5 5.13.0-1
ii  libkf5codecs5  5.13.0-1
ii  libkf5completion5  5.13.0-1
ii  libkf5configcore5  5.13.0-1
ii  libkf5configgui5   5.13.0-1
ii  libkf5configwidgets5   5.13.0-2
ii  libkf5coreaddons5  5.13.0-1
ii  libkf5guiaddons5   5.13.0-1
ii  libkf5i18n55.13.0-1
ii  libkf5iconthemes5  5.13.0-1
ii  libkf5itemviews5   5.13.0-1
ii  libkf5jobwidgets5  5.13.0-1
ii  libkf5kiocore5 5.13.0-1
ii  libkf5kiofilewidgets5  5.13.0-1
ii  libkf5kiowidgets5  5.13.0-1
ii  libkf5parts5   5.13.0-1
ii  libkf5sonnetcore5  5.13.0-1
ii  libkf5sonnetui55.13.0-1
ii  libkf5textwidgets5 5.13.0-1
ii  libkf5widgetsaddons5   5.13.0-1
ii  libkf5xmlgui5  5.13.0-1
ii  libqt5core5a   5.4.2+dfsg-9
ii  libqt5gui5 5.4.2+dfsg-9
ii  libqt5printsupport55.4.2+dfsg-9
ii  libqt5script5  5.4.2+dfsg-4
ii  libqt5widgets5 5.4.2+dfsg-9
ii  libqt5xml5 5.4.2+dfsg-9
ii  libstdc++6 5.2.1-17

Versions of packages libkf5texteditor5 recommends:
ii  ktexteditor-katepart  5.13.0-1+b1

libkf5texteditor5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ktexteditor
Source-Version: 5.15.0-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated ktexteditor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Oct 2015 19:16:48 +0200
Source: ktexteditor
Binary: libkf5texteditor-dev libkf5texteditor5 ktexteditor-data 
ktexteditor-katepart libkf5texteditor5-dbg
Architecture: source
Version: 5.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 ktexteditor-data - provide advanced plain text editing services
 ktexteditor-katepart - provide advanced plain text editing services
 libkf5texteditor-dev - provide advanced plain text editing services
 libkf5texteditor5 - provide advanced plain text editing services
 libkf5texteditor5-dbg - provide advanced plain text editing services
Closes: 799430
Changes:
 ktexteditor (5.15.0-1) unstable; urgency=medium
 .
   * Add copyright information about the current license of the linkable
 code.
   * Drop libgit2-dev build dep. (Closes: #799430)
   * New upstream release (5.15.0).
Checksums-Sha1:
 c146bef0d4d1d812164eedc6a0f1b32e5ae6c80c 2731 ktexteditor_5.15.0-1.dsc
 7be09fda5b43d3ceebe2b614c8f2e62f81d0944d 2857676 ktexteditor_5.15.0.orig.tar.xz
 33fbbf89e1351d9d79b654d7241ec70d9ee21a18 10420 

Bug#801415: ejabberd: maintainer is not maintainer

[Dominik George]

Am Montag, 12. Oktober 2015, 15:54:45 schrieb Konstantin Khomoutov:
> While I'm dissatisfied, to put it mildly, with what the submitter wrote
> in this bug report regarding me being «unable to respond to any
> requests», 

Quoting, to make it clearer what I mean:

> unfortunately I'm not familiar with
> these new line of ejabberd development (AB.CD version numbering).

> I can only google for the error string.

> Another room of interest is pkg-ejabb...@deb.at
> which is dedicated to packaging ejabberd for Debian.

That means, that the person listed as maintainer is, in fact, unable to 
respond to any requests, because he did not follow upstream development for at 
least three years.

Of course, pointing to online resources or other packagers is, technically, a 
response, but I think using Google is something that many people can do and 
not something that makes a person maintainer of a software package.

There should be no bad feelings here, it's simply a fact.

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-151-61623918

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)

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

Bug#801585: python-debianbts: get_bugs interface is broken

[Gaetano Guerriero]

On Mon, Oct 12, 2015 at 03:51:53PM +0530, Ritesh Raj Sarraf wrote:
> Thanks for the quick reply. Please find attached the full console log.
> apt-offline is multi-threaded when downloading the data. But with the
>  --verbose switch used, you should be able to relate the Thread-N
> number.
> 
> 
> Also there are mulitple exceptions coming from debianbts module.
> And FYI, I also bundle the debianbts module with apt-offline so that
> the user can download the bug reports on a Windows box too. The
> currently bundled version of debianbts module works fine.
> 
> 
> 
> 
> rrs@learner:~/devel/apt-offline/apt-offline (master)$ ./apt-offline get
> /var/tmp/set.uris --bug-reports --threads 5 --cache-dir
> /var/cache/apt/archives/ --verbose


Hello,

is it possible to have access to /var/tmp/set.uris, so I can easily recreate the
problem ?
I can't reproduce by calling get_bugs() on single packages of the logs.

 Gaetano Guerriero

Bug#785928: marked as done (gst-chromaprint: Please update to GStreamer 1.x)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:26:15 +
with message-id 
and subject line Bug#801075: Removed package(s) from unstable
has caused the Debian Bug report #785928,
regarding gst-chromaprint: Please update to GStreamer 1.x
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.)


-- 
785928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-chromaprint
Severity: important
User: sl...@debian.org
Usertags: gstreamer0.10-removal

Hi maintainer,

your package gst-chromaprint currently still depends on GStreamer
0.10.

GStreamer 0.10 is no longer maintained and supported by the upstream
project since almost 3 years, and contains many known bugs that are
fixed in the new 1.x release series of GStreamer. Next to many bug
fixes, the new release series also contains many other improvements,
new features and a more streamlined API.

For the next Debian release GStreamer 0.10 is planned to be removed,
and if your package is not updated it might not be included in the
release. Please update your package to use the new version as soon as
possible.

If you need any help with porting or have further questions, please
feel free to also contact me privately.

Best regards, Sebastian

PS: See https://bugs.debian.org/785198 and
https://lists.debian.org/debian-devel/2015/05/msg00335.html for some
further discussion.
--- End Message ---
--- Begin Message ---
Version: 0.1-3+rm

Dear submitter,

as the package gst-chromaprint has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/801075

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#801071: marked as done (RM: minirok -- ROM; dead upstream; low popcpn; alternatives available)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:25:26 +
with message-id 
and subject line Bug#801071: Removed package(s) from unstable
has caused the Debian Bug report #801071,
regarding RM: minirok -- ROM; dead upstream; low popcpn; alternatives available
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.)


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

Should minirok be removed? It hasn't seen an upload
since 2009, it's dead upstream (Debian maintainer is also
upstream), popcon usage is marginal and it relies on
obsolete gstreamer 0.10. Plus, there's plenty of alternatives
in the archive.

Please address the outstanding bugs or reassign this to
ftp.debian.org for removal.

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

   minirok |  2.1-1 | source, all

--- Reason ---
ROM; dead upstream; low popcpn; alternatives available
--

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

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

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#800508: marked as done (iceweasel-vimperator: does not work anymore)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 12:34:10 +
with message-id 
and subject line Bug#801473: Removed package(s) from unstable
has caused the Debian Bug report #800508,
regarding iceweasel-vimperator: does not work anymore
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.)


-- 
800508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iceweasel-vimperator
Version: 3.8.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

possibly caused by the recent iceweasel update, vimperator 3.8.2-2
stopped working on jessie.
The browser behaves exactly as if vimperator was not installed or not
active.
Purge/re-install does not help.

Workaround: Installing vimperator 3.10.1-1 from testing works for me.


-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages iceweasel-vimperator depends on:
ii  iceweasel  38.3.0esr-1~deb8u1

iceweasel-vimperator recommends no packages.

iceweasel-vimperator suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.10.1-1+rm

Dear submitter,

as the package vimperator has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/801473

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#801415: ejabberd: maintainer is not maintainer

[Konstantin Khomoutov]

On Fri, 09 Oct 2015 22:33:59 +0200
Dominik George  wrote:

> Package: ejabberd
> Severity: serious
> Justification: Policy 3.3
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I contacted the maintainer as listed in the package, and was informed
> that he is not the current maintainer in reality and is unable to
> respond to any requests.
> 
> Please update the maintainer field or orphan the package.

While I'm dissatisfied, to put it mildly, with what the submitter wrote
in this bug report regarding me being «unable to respond to any
requests», the crux of their report -- that I'm not really packaging
ejabberd for some time -- is true, and I'm of course fine with
officially resigning if it's deemed the right thing to do with those
doing actual packaging.

Hence I'd like to hear opinions from Philipp and Rhonda about what
should I do next (if I should).

Bug#801535: asterisk: FTBFS in sid: linker errors due to missing B-D

[Jonas Smedegaard]

Quoting Tzafrir Cohen (2015-10-12 10:15:30)
> On Sun, Oct 11, 2015 at 11:34:32PM +0200, Jonas Smedegaard wrote:
> > Quoting Andreas Beckmann (2015-10-11 22:58:11)
> > > asterisk FTBFS in sid:
> > > 
> > > [...]
> > > x86_64-linux-gnu-gcc -o pjsip/dialplan_functions.o -c 
> > > pjsip/dialplan_functions.c -MD -MT pjsip/dialplan_functions.o -MF 
> > > .pjsip_dialplan_functions.o.d -MP -pthread 
> > > -I/tmp/buildd/asterisk-13.1.0~dfsg/include -fgnu89-inline -g -O2 -fPIE 
> > > -fstack-protector-strong -Wformat -Werror=format-security 
> > > -D_FORTIFY_SOURCE=2   -I/usr/include/libxml2 -pipe -Wall 
> > > -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations  
> > > -fPIC -DAST_MODULE=\"chan_pjsip\"  -DPJ_AUTOCONF=1 -DPJ_IS_BIG_ENDIAN=0 
> > > -DPJ_IS_LITTLE_ENDIAN=1 -DOPENSSL_NO_SSL2=1   
> > > /tmp/buildd/asterisk-13.1.0~dfsg/build_tools/make_linker_version_script 
> > > chan_pjsip "" "/tmp/buildd/asterisk-13.1.0~dfsg"
> > > x86_64-linux-gnu-gcc  -o chan_pjsip.so -pthread -fPIE -pie -Wl,-z,relro 
> > > -Wl,-z,now-shared 
> > > -Wl,--version-script,chan_pjsip.exports,--warn-common  chan_pjsip.o 
> > > pjsip/dialplan_functions.o  -lpjsua2 -lstdc++ -lpjsua -lpjsip-ua 
> > > -lpjsip-simple -lpjsip -lpjmedia-codec -lpjmedia -lpjmedia-videodev 
> > > -lpjmedia-audiodev -lpjmedia -lpjnath -lpjlib-util -lsrtp -lpj -lm -lrt 
> > > -lpthread -lSDL2 -lavformat-ffmpeg -lavcodec-ffmpeg -lswscale-ffmpeg 
> > > -lavutil-ffmpeg -lv4l2 -lopencore-amrnb -lopencore-amrwb 
> > > /usr/bin/ld: cannot find -lSDL2
> > > /usr/bin/ld: cannot find -lavformat-ffmpeg
> > > /usr/bin/ld: cannot find -lavcodec-ffmpeg
> > > /usr/bin/ld: cannot find -lswscale-ffmpeg
> > > /usr/bin/ld: cannot find -lavutil-ffmpeg
> > > /usr/bin/ld: cannot find -lv4l2
> > > /usr/bin/ld: cannot find -lopencore-amrnb
> > > /usr/bin/ld: cannot find -lopencore-amrwb
> > > collect2: error: ld returned 1 exit status
> > > 
> > > These seem to be several Build-Depends missing, e.g. libsdl2-dev, 
> > > libv4l-dev
> > > and the ffmpeg bits seem to have been reorganized as well.
> > 
> > I suspect ig might be pjsip growing dependencies on those libraries and 
> > injecting linkage flags into Asterisk, but instead of actively avoiding 
> > those it seems more sensible to me to consider solving bug#531728.
> 
> You are right. The git version of pjsip should look better.

Right - fails even when explicitly adding those build-dependencies, so 
something seems broken in pjproject and/or its relationship with ffmpeg 
- the former hasn't changed since August, but the latter was updated
from 2.7 to 2.8 on September 22.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: Bug#795178 tagged as pending

[Debian Bug Tracking System]

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

> tag 795178 pending
Bug #795178 {Done: Gaudenz Steinlin } [src:ceph] ceph FTBFS 
with boost1.58
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#795178: tagged as pending

[Gaudenz Steinlin]

tag 795178 pending
--

We believe that the bug #795178 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/pkg-ceph/ceph.git/diff/?id=c8b478a

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit c8b478a038cd879f0088a5a462d98495f9257c2e
Author: Gaudenz Steinlin 
Date:   Tue Oct 6 14:37:06 2015 +0200

Add upstream patch to fix compiling with boost 1.58

Closes: #795178

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

[gregor herrmann]

On Mon, 12 Oct 2015 16:49:29 +0300, Niko Tyni wrote:

> Package: license-reconcile
> Version: 0.7
> Severity: serious
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> 
> As noticed by the reproducible.debian.net CI setup, this package
> fails to build on current sid:
> 
>   #   Failed test at t/09-licensecheck.t line 20.
>   # Compared $data->[0]{"file"}
>   #got : 'base'
>   # expect : 'base.h'
>   /usr/bin/licensecheck warning: cannot parse file 
> 't/data/example/sample.png' with mime type 'image/png; charset=binary'
>   
>   #   Failed test at t/09-licensecheck.t line 37.
>   # Compared $data->[0]{"file"}
>   #got : 'base'
>   # expect : 'base.h'
>   # Looks like you failed 2 tests of 7.
>   [...]
>   /usr/bin/licensecheck warning: cannot parse file 
> 't/data/example/sample.png' with mime type 'image/png; charset=binary'
>   /usr/bin/licensecheck warning: cannot parse file 
> 't/data/example/sample.png' with mime type 'image/png; charset=binary'
>   
>   #   Failed test at t/18-app.t line 159.
>   # Comparing $data as a Bag
>   # Missing: 2 references
>   # Extra: 2 references
>   # Looks like you failed 1 test of 41.
>   
>   Test Summary Report
>   ---
>   t/09-licensecheck.t (Wstat: 512 Tests: 7 Failed: 2)
> Failed tests:  3, 6
> Non-zero exit status: 2
>   t/18-app.t  (Wstat: 256 Tests: 41 Failed: 1)
> Failed test:  40
> Non-zero exit status: 1

Hm, maybe related to recent changes in licensecheck (I only remember
seeing it in devscript's changelog). Dominique, do you have an idea?


Cheers,
gregor  

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Ludwig Hirsch: Der Turm


signature.asc
Description: Digital Signature

Bug#801610: libogg-vorbis-decoder-perl: FTBFS: Failed test 'raw_total'

[Niko Tyni]

Package: libogg-vorbis-decoder-perl
Version: 0.9-2
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

As noticed by the reproducible.debian.net CI setup, this package
fails to build on current sid:

  #   Failed test 'raw_total'
  #   at t/basic.t line 20.
  #  got: '4414398'
  # expected: '4418594'
  # Looks like you failed 1 test of 20.
  [...]
  Test Summary Report
  ---
  t/basic.t   (Wstat: 256 Tests: 20 Failed: 1)
Failed test:  9
Non-zero exit status: 1

-- 
Niko Tyni   nt...@debian.org

Bug#801608: ntop: build-depends on non-existent librrd2-dev

[Michael Tautschnig]

Package: ntop
Version: 3:5.0.1+dfsg1-2.1
Usertags: goto-cc
Severity: serious
Justification: FTBFS

As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ntop. Changing the build-dependency to
librrd-dev should fix the problem.

Best,
Michael



pgpSuO0vM6CpP.pgp
Description: PGP signature

Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'

[Niko Tyni]

Package: license-reconcile
Version: 0.7
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

As noticed by the reproducible.debian.net CI setup, this package
fails to build on current sid:

  #   Failed test at t/09-licensecheck.t line 20.
  # Compared $data->[0]{"file"}
  #got : 'base'
  # expect : 'base.h'
  /usr/bin/licensecheck warning: cannot parse file 't/data/example/sample.png' 
with mime type 'image/png; charset=binary'
  
  #   Failed test at t/09-licensecheck.t line 37.
  # Compared $data->[0]{"file"}
  #got : 'base'
  # expect : 'base.h'
  # Looks like you failed 2 tests of 7.
  [...]
  /usr/bin/licensecheck warning: cannot parse file 't/data/example/sample.png' 
with mime type 'image/png; charset=binary'
  /usr/bin/licensecheck warning: cannot parse file 't/data/example/sample.png' 
with mime type 'image/png; charset=binary'
  
  #   Failed test at t/18-app.t line 159.
  # Comparing $data as a Bag
  # Missing: 2 references
  # Extra: 2 references
  # Looks like you failed 1 test of 41.
  
  Test Summary Report
  ---
  t/09-licensecheck.t (Wstat: 512 Tests: 7 Failed: 2)
Failed tests:  3, 6
Non-zero exit status: 2
  t/18-app.t  (Wstat: 256 Tests: 41 Failed: 1)
Failed test:  40
Non-zero exit status: 1
 
-- 
Niko Tyni   nt...@debian.org

Processed: tagging 801610

[Debian Bug Tracking System]

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

> tags 801610 + stretch sid
Bug #801610 [libogg-vorbis-decoder-perl] libogg-vorbis-decoder-perl: FTBFS: 
Failed test 'raw_total'
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#794817: Should mplayer2 be removed from unstable?

[Sebastian Ramacher]

Control: reassign -1 ftp.debian.org
Control: severity -1 normal
Control: retile -1 RM: mplayer2 -- ROM; dead upstream, replacement exists

On 2015-08-13 21:24:56, Andreas Cadhalpun wrote:
> On 07.08.2015 03:19, Sebastian Ramacher wrote:
> > On 2015-08-06 23:05:58, Andreas Cadhalpun wrote:
> >> Unless someone objects, I'll reassign this bug to ftp.debian.org for
> >> removal soon.
> > 
> > Before doing so, please file bugs against packages (Build-)Depending on
> > mplayer2 to switch back to mplayer:
> > 
> > Checking reverse dependencies...
> > # Broken Depends:
> > jajuk: jajuk
> > kphotoalbum: kphotoalbum
> > 
> > # Broken Build-Depends:
> > jajuk: mplayer2
> 
> I've filed #795418 for jajuk and #795419 for kphotoalbum and made them block
> this bug.

I've uploaded NMUs based on your patches. They will hit unstable in 5 days. So
let's ressign this bug to ftp.debian.org.

Dear FTP masters, please remove mplayer2 from the archive. It's dead upstream
and replacement exists (mplayer, mpv).

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed (with 1 error): Re: Bug#794817: Should mplayer2 be removed from unstable?

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #794817 [mplayer2] Should mplayer2 be removed from unstable?
Bug reassigned from package 'mplayer2' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #794817 to the same values 
previously set
Ignoring request to alter fixed versions of bug #794817 to the same values 
previously set
> severity -1 normal
Bug #794817 [ftp.debian.org] Should mplayer2 be removed from unstable?
Severity set to 'normal' from 'serious'
> retile -1 RM: mplayer2 -- ROM; dead upstream, replacement exists
Unknown command or malformed arguments to command.


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

Bug#801585: python-debianbts: get_bugs interface is broken

[Ritesh Raj Sarraf]

On Mon, 2015-10-12 at 18:21 +0200, Gaetano Guerriero wrote:
> Thank you very much.
> 
> Can you reproduce the bug with version 2.5.1 from sid ?
> 
> It is working right on my side.
> 
>  Gaetano Guerriero

Nope. did not help much. Please find the logs below.

Apart from the ExpatError exception, all others looks like generic issues. Like 
the SSLv3 is a common problem but you'll have to decide on how you want to 
handle it in your module. Same goes for BadStatusLine exception.
As for ExpatError, I'm not sure if it is specific to debianbts or python in 
general.



rrs@learner:~/devel/apt-offline/apt-offline (jessie)$ ./apt-offline get 
/var/tmp/set.uris --bug-reports --threads 5 --cache-dir 
/var/cache/apt/archives/ 

Fetching APT Data

WARNING: If you are on a slow connection, it is good to
WARNING: limit the number of threads to a low number like 2.
WARNING: Else higher number of threads executed could cause
WARNING: network congestion and timeouts.

libgstreamer1.0-0 copied from local cache directory /var/cache/apt/archives/.   
   
gir1.2-gstreamer-1.0 copied from local cache directory 
/var/cache/apt/archives/.  
gstreamer1.0-plugins-base copied from local cache directory 
/var/cache/apt/archives/.  
No handlers could be found for logger "pysimplesoap.simplexml"
No handlers could be found for logger "pysimplesoap.simplexml"
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineLib.py",
 line 624, in run
self.responseQueue.put( self.WorkerFunction( item, thread_name ) )
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 633, in DataFetcher
if FetchBugReportsDebian.FetchBugsDebian(PackageName) in [1,2]:
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 151, in FetchBugsDebian
self.bugs_list = debianbts.get_bugs( 'package', PackageName )
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 413, in get_bugs
reply = soap_client.call('get_bugs', method_el)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 262, in 
call
jetty=self.__soap_server in ('jetty',))
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/simplexml.py", line 56, 
in __init__
self.__document = xml.dom.minidom.parseString(text)
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: not well-formed (invalid token): line 1, column 4
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineLib.py",
 line 624, in run
self.responseQueue.put( self.WorkerFunction( item, thread_name ) )
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 633, in DataFetcher
if FetchBugReportsDebian.FetchBugsDebian(PackageName) in [1,2]:
  File 
"/media/SSHD/rrs-home/devel/apt-offline/apt-offline/apt_offline_core/AptOfflineCoreLib.py",
 line 151, in FetchBugsDebian
self.bugs_list = debianbts.get_bugs( 'package', PackageName )
  File "/usr/lib/python2.7/dist-packages/debianbts.py", line 413, in get_bugs
reply = soap_client.call('get_bugs', method_el)
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/client.py", line 262, in 
call
jetty=self.__soap_server in ('jetty',))
  File "/usr/lib/python2.7/dist-packages/pysimplesoap/simplexml.py", line 56, 
in __init__
self.__document = xml.dom.minidom.parseString(text)
  File "/usr/lib/python2.7/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
  File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: not well-formed (invalid token): line 1, column 1


gstreamer1.0-x copied from local cache directory /var/cache/apt/archives/.  

gstreamer1.0-plugins-good copied from local cache directory 
/var/cache/apt/archives/.  
libges-1.0-0 copied from local cache directory 

Bug#801558: [pkg-go] Bug#801558: Bug#801558: golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go

[Tianon Gravi]

On 12 October 2015 at 10:20, Tianon Gravi  wrote:
> | Replaces: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~)
> | Breaks: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~)
> | Provides: golang-codegangsta-cli-dev
>
> Are the version numbers wrong or something similarly simple I've overlooked?

Doh, that's exactly it -- these should've been "(<<
0.0~git20150117-2~)" (not "-1").

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed: Re: kadu: FTBFS with gcc5

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #795488 {Done: Patryk Cisek } [kadu] kadu: FTBFS with 
gcc5
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions kadu/2.1-1.
> severity -1 serious
Bug #795488 [kadu] kadu: FTBFS with gcc5
Severity set to 'serious' from 'important'

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

Bug#796306: marked as done (pyoperators: FTBFS: plugin distutils failed with: exit code=1)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 13:58:24 -0400
with message-id <5354.dX4uIu5vf2@kitterma-e6430>
and subject line Builds now
has caused the Debian Bug report #796306,
regarding pyoperators: FTBFS: plugin distutils failed with: exit code=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.)


-- 
796306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyoperators
Version: 0.13.6-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

pyoperators fails to build from source on unstable/amd64:

  [..]

  print(rule_manager['none'])
  Expected nothing
  Got:
  False
  --
  File
  
"/home/lamby/temp/cdt.20150821101010.z8E8Urm7PB/pyoperators-0.13.6/.pybuild/pythonX.Y_2.7/build/pyoperators/rules.py",
  line 280, in pyoperators.rules.RuleManager
  Failed example:
  with rule_manager(none=True) as new_rule_manager:
  print(rule_manager['none'])
  with new_rule_manager(none=False):
  print(rule_manager['none'])
  print(rule_manager['none'])
  Expected nothing
  Got:
  True
  False
  True
  --
  File
  
"/home/lamby/temp/cdt.20150821101010.z8E8Urm7PB/pyoperators-0.13.6/.pybuild/pythonX.Y_2.7/build/pyoperators/rules.py",
  line 285, in pyoperators.rules.RuleManager
  Failed example:
  print(rule_manager['none'])
  Expected:
  False
  True
  False
  True
  False
  Got:
  False
  
  
  --
  Ran 37 tests in 0.970s
  
  FAILED (errors=2, failures=8)
  E: pybuild pybuild:262: test: plugin distutils failed with: exit
  code=1: cd
  
/home/lamby/temp/cdt.20150821101010.z8E8Urm7PB/pyoperators-0.13.6/.pybuild/pythonX.Y_2.7/build;
  python2.7 -m nose --with-doctest 
  dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7
  --dir . returned exit code 13
  debian/rules:10: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
 dpkg-buildpackage -rfakeroot -D -us -uc -b
dpkg-buildpackage: source package pyoperators
dpkg-buildpackage: source version 0.13.6-1
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Ghislain Antony Vaillant 

 dpkg-source --before-build pyoperators-0.13.6
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python2,python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
pybuild --clean --test-nose -i python{version} -p 2.7 --dir .
pybuild --clean --test-nose -i python{version} -p 3.4 --dir .
rm -rf .pybuild/
find . -name \*.pyc -exec rm {} \;
   dh_clean -O--buildsystem=pybuild
rm -f debian/python-pyoperators.substvars
rm -f debian/python-pyoperators.*.debhelper
rm -rf debian/python-pyoperators/
rm -f debian/python3-pyoperators.substvars
rm -f debian/python3-pyoperators.*.debhelper
rm -rf debian/python3-pyoperators/
rm -rf debian/.debhelper/
rm -f debian/*.debhelper.log
rm -f debian/files
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS \) -prune -o -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
rm -f *-stamp
 debian/rules build
dh build --with python2,python3 --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
pybuild --configure --test-nose -i python{version} -p 2.7 --dir .
I: pybuild base:170: python2.7 setup.py config 
running config
pybuild --configure --test-nose -i python{version} -p 3.4 --dir .
I: pybuild base:170: python3.4 

Bug#801558: [pkg-go] Bug#801558: golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go

[Tianon Gravi]

On 11 October 2015 at 21:56, Andreas Beckmann  wrote:
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

Hmm, this seems strange, because "golang-github-codegangsta-cli-dev"
does have a Replaces/Breaks/Provides combo:

| Replaces: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~)
| Breaks: golang-codegangsta-cli-dev (<< 0.0~git20150117-1~)
| Provides: golang-codegangsta-cli-dev

Are the version numbers wrong or something similarly simple I've overlooked?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#801610: libogg-vorbis-decoder-perl: FTBFS: Failed test 'raw_total'

[Niko Tyni]

On Mon, Oct 12, 2015 at 04:52:37PM +0300, Niko Tyni wrote:
> Package: libogg-vorbis-decoder-perl
> Version: 0.9-2
> Severity: serious
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs

>   #   Failed test 'raw_total'
>   #   at t/basic.t line 20.
>   #  got: '4414398'
>   # expected: '4418594'

This test was broken by src:libvorbis (binary:libvorbisfile3 to be exact)
upgrade from 1.3.4-2 to 1.3.4-3.

I have no idea if it's an intended change or an accidental
side effect. Copying the libvorbis maintainers, could you please
comment on that?

It looks like the raw_total() method in Decoder.xs just calls
ov_raw_total() with i==-1. The test file is data/test.ogg in the
libogg-vorbis-decoder-perl source package, and I see the expected value
4418594 is also the full size of the file.
-- 
Niko Tyni   nt...@debian.org

Bug#798079: utopia-documents: diff for NMU version 2.4.4-2.1

[Sebastian Ramacher]

Control: tags 798079 + patch
Control: tags 798079 + pending

Dear maintainer,

I've prepared an NMU for utopia-documents (versioned as 2.4.4-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru utopia-documents-2.4.4/debian/changelog utopia-documents-2.4.4/debian/changelog
--- utopia-documents-2.4.4/debian/changelog	2014-10-24 14:39:17.0 +0200
+++ utopia-documents-2.4.4/debian/changelog	2015-10-12 20:45:41.0 +0200
@@ -1,3 +1,14 @@
+utopia-documents (2.4.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Steve Langasek ]
+  * debian/patches/boost1.58-qt4moc-compatibility.patch: compatibility
+with boost 1.58.
+  * Add missing build-dependency on libqt4-opengl-dev. (Closes: #798079)
+
+ -- Sebastian Ramacher   Mon, 12 Oct 2015 20:45:40 +0200
+
 utopia-documents (2.4.4-2) unstable; urgency=medium
 
   * Updated copyright file to include additional licenses.
diff -Nru utopia-documents-2.4.4/debian/control utopia-documents-2.4.4/debian/control
--- utopia-documents-2.4.4/debian/control	2014-10-23 12:34:54.0 +0200
+++ utopia-documents-2.4.4/debian/control	2015-10-12 21:08:51.0 +0200
@@ -18,6 +18,7 @@
libqglviewer-dev | libqglviewer-qt4-dev,
libqjson-dev,
libqt4-dev,
+   libqt4-opengl-dev,
libqtwebkit-dev | libqt4-dev (<< 4:4.7),
libraptor-dev,
libssl-dev,
diff -Nru utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch
--- utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch	1970-01-01 01:00:00.0 +0100
+++ utopia-documents-2.4.4/debian/patches/boost1.58-qt4moc-compatibility.patch	2015-10-12 20:44:31.0 +0200
@@ -0,0 +1,527 @@
+Author: Steve Langasek 
+Description: compatibility with boost 1.58
+ Newer versions of boost break compatibility with previous workarounds for
+ qt4 moc's inability to parse boost headers.  Add a new workaround here.
+Index: utopia-documents-2.4.4/libutopia2/utopia2/extension.h
+===
+--- utopia-documents-2.4.4.orig/libutopia2/utopia2/extension.h
 utopia-documents-2.4.4/libutopia2/utopia2/extension.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ #include 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/annotationprocessoraction.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/annotationprocessoraction.h
 utopia-documents-2.4.4/libpapyro/papyro/annotationprocessoraction.h
+@@ -35,7 +35,9 @@
+ #include 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/annotatorrunnable.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/annotatorrunnable.h
 utopia-documents-2.4.4/libpapyro/papyro/annotatorrunnable.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/capabilities.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/capabilities.h
 utopia-documents-2.4.4/libpapyro/papyro/capabilities.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ #include 
+ #include 
+ 
+Index: utopia-documents-2.4.4/libpapyro/papyro/cslengine.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/cslengine.h
 utopia-documents-2.4.4/libpapyro/papyro/cslengine.h
+@@ -35,7 +35,9 @@
+ #include 
+ #include 
+ #include 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ namespace Papyro
+ {
+Index: utopia-documents-2.4.4/libpapyro/papyro/decorator.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/decorator.h
 utopia-documents-2.4.4/libpapyro/papyro/decorator.h
+@@ -34,7 +34,9 @@
+ 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ #include 
+ 
+ namespace Spine
+Index: utopia-documents-2.4.4/libpapyro/papyro/dispatcher.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/dispatcher.h
 utopia-documents-2.4.4/libpapyro/papyro/dispatcher.h
+@@ -37,7 +37,9 @@
+ #include 
+ #include 
+ 
++#ifndef Q_MOC_RUN
+ #include 
++#endif
+ 
+ #include 
+ #include 
+Index: utopia-documents-2.4.4/libpapyro/papyro/dispatcher_p.h
+===
+--- utopia-documents-2.4.4.orig/libpapyro/papyro/dispatcher_p.h

Bug#801046: git: "Out of memory, malloc failed" cloning certain repos

[Jonathan Nieder]

tags 801046 + moreinfo
quit

Hi Lenz,

PICCORO McKAY Lenz wrote:

> Version: 1:1.7.10.4-1+wheezy1
> Severity: grave

I am able to use git.  Are you sure the package is actually unusable?
For example, do commands like "git init" work?

[...]
> Current version of git for wheeze and squeeze are unusable, does not
> work as normal user for make it work user must know the root
> password and swicht, sudo does not work!

Thanks for reporting.  I'm having some trouble understanding the exact
problem.

Does version 2.x have this problem as well?  There was a change
upstream mentioning http.pushbuffer but I am not sure if it is
related.

commit c80d96ca0c3cf948c5062bf6591a46c625620b6d (tags/v1.9-rc0~97^2)
Author: Brian M. Carlson 
Date:   Thu Oct 31 02:36:51 2013 -0400

remote-curl: fix large pushes with GSSAPI

Due to an interaction between the way libcurl handles GSSAPI
authentication over HTTP and the way git uses libcurl, large
pushes (those over http.postBuffer bytes) would fail due to
an authentication failure requiring a rewind of the curl
buffer.  Such a rewind was not possible because the data did
not fit into the entire buffer.

Enable the use of the Expect: 100-continue header for large
requests where the server offers GSSAPI authentication to
avoid this issue, since the request would otherwise fail.
This allows git to get the authentication data right before
sending the pack contents.  Existing cases where pushes
would succeed, including small requests using GSSAPI, still
disable the use of 100 Continue, as it causes problems for
some remote HTTP implementations (servers and proxies).

Signed-off-by: Brian M. Carlson 
Signed-off-by: Jeff King 

Thanks and hope that helps,
Jonathan

Processed: Re: git: "Out of memory, malloc failed" cloning certain repos

[Debian Bug Tracking System]

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

> tags 801046 + moreinfo
Bug #801046 [git] fatal: Out of memory, malloc failed (tried to allocate 
524288000 bytes)
Added tag(s) moreinfo.
> quit
Stopping processing here.

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

Processed: utopia-documents: diff for NMU version 2.4.4-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 798079 + patch
Bug #798079 [utopia-documents] FTBFS: QGLWidget: No such file or directory
Added tag(s) patch.
> tags 798079 + pending
Bug #798079 [utopia-documents] FTBFS: QGLWidget: No such file or directory
Added tag(s) pending.

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

Bug#801558: marked as done (golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 18:18:50 +
with message-id 
and subject line Bug#801558: fixed in golang-codegangsta-cli 0.0~git20150117-3
has caused the Debian Bug report #801558,
regarding golang-codegangsta-cli-dev: fails to upgrade from 'testing' - trying 
to overwrite /usr/share/gocode/src/github.com/codegangsta/cli/command.go
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.)


-- 
801558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-codegangsta-cli-dev
Version: 0.0~git20150117-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package golang-github-codegangsta-cli-dev.
  Preparing to unpack 
.../golang-github-codegangsta-cli-dev_0.0~git20150117-2_all.deb ...
  Unpacking golang-github-codegangsta-cli-dev (0.0~git20150117-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-codegangsta-cli-dev_0.0~git20150117-2_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/gocode/src/github.com/codegangsta/cli/command.go', which is also in 
package golang-codegangsta-cli-dev 0.0~git20150117-1
  Preparing to unpack .../golang-codegangsta-cli-dev_0.0~git20150117-2_all.deb 
...
  Unpacking golang-codegangsta-cli-dev (0.0~git20150117-2) over 
(0.0~git20150117-1) ...
  Errors were encountered while processing:
   
/var/cache/apt/archives/golang-github-codegangsta-cli-dev_0.0~git20150117-2_all.deb


cheers,

Andreas


golang-codegangsta-cli-dev_0.0~git20150117-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: golang-codegangsta-cli
Source-Version: 0.0~git20150117-3

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

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated golang-codegangsta-cli 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Oct 2015 10:50:21 -0700
Source: golang-codegangsta-cli
Binary: golang-github-codegangsta-cli-dev golang-codegangsta-cli-dev
Architecture: source all
Version: 0.0~git20150117-3
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Tianon Gravi 
Description:
 golang-codegangsta-cli-dev - Transitional package for 
golang-github-codegangsta-cli-dev
 golang-github-codegangsta-cli-dev - simple library for building command line 
apps in Go
Closes: 801558
Changes:
 golang-codegangsta-cli (0.0~git20150117-3) unstable; urgency=medium
 .
   * Team upload.
   * Fix Breaks/Replaces version number so upgrades work. (Closes: #801558)
Checksums-Sha1:
 52e2b78effd05feb15748ac23b1597704bd344bb 2283 
golang-codegangsta-cli_0.0~git20150117-3.dsc
 9854720a91ac29170075039c0415836149e2f8db 2272 
golang-codegangsta-cli_0.0~git20150117-3.debian.tar.xz
 e67ff770ae22307dda8d919dec838a0b90c4d610 2332 
golang-codegangsta-cli-dev_0.0~git20150117-3_all.deb
 e6845ba78e7eb8357023296c2b8ef046185905a5 14424 
golang-github-codegangsta-cli-dev_0.0~git20150117-3_all.deb
Checksums-Sha256:
 ec7912cedaf4e390b4e7634259362c340d6bede2997ff127d2762db9c75511c5 2283 
golang-codegangsta-cli_0.0~git20150117-3.dsc
 49dde93c2cb91138451d2f0063cdf1b7032d36057b698bfd890c73a2e60a1889 2272 
golang-codegangsta-cli_0.0~git20150117-3.debian.tar.xz
 9f38c1ba93d757ad6c54c964547aeeb74347a12adc33e1fe001e607d587a5a9d 2332 
golang-codegangsta-cli-dev_0.0~git20150117-3_all.deb
 40a821fe27ae4790c584cce6cb905e4a7f1833bc6d1e3b1e8925f37d28e64ada 14424 

Processed: merging 799694 800672

[Debian Bug Tracking System]

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

> merge 799694 800672
Bug #799694 [src:healpy] healpy: FTBFS on ppc64(el): No module named _tkinter
Bug #800672 [src:healpy] healpy: FTBFS: Tests require X environment
Merged 799694 800672
> thanks
Stopping processing here.

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

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Manuel A. Fernandez Montecelo]

2015-10-12 22:35 GMT+01:00 Nick Black :
> As a datum (I reported a duplicate of this bug as 801488), I removed both
> libxmlrpc-lite-perl and libsoap-lite-perl, and still see the crash. So I
> don't think they're to blame, as asserted earlier on this bug. They also
> would seem unlikely causes for the gdb/valgrind output I reported in that
> bug.

I tried to replicate it and I could not yet with the different
scenarios in these bug reports.  I think that I have a fix for this,
but since I couldn't test it I am not 100% sure and I am waiting --
but hopefully it will be fixed soon and will appear in the next
release after that.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Nick Black]

if you want me to pull something and test it, i ought be able to within a
day or so.

-- 
nick black -=- http://www.nick-black.com
to make an apple pie from scratch, you need first invent a universe.

Processed (with 1 error): Re: Bug#801497: docdiff: non-free file "devutil/JIS0208.TXT"

[Debian Bug Tracking System]

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

> tag 801497 fixed-in-upstream pending
Unknown tag/s: fixed-in-upstream.
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 newcomer etch etch-ignore 
lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie 
jessie-ignore stretch stretch-ignore buster buster-ignore.

Bug #801497 [src:docdiff] docdiff: non-free file "devutil/JIS0208.TXT"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#754803: marked as done (healpy: out-of-date binaries)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 17:42:51 -0400
with message-id <43780856.MLm11FyEe7@kitterma-e6430>
and subject line Re: healpy: out-of-date binaries
has caused the Debian Bug report #754803,
regarding healpy: out-of-date binaries
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.)


-- 
754803: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1
Severity: serious
Justification: ood binaries

Hi,

your package can no longer migrate to testing since it has out-of-date
binaries on various architectures (armel armhf i386 kfreebsd-i386 mips
mipsel powerpc s390x).

Please investigate whether restricting to *amd64 was the proper thing to
do, and request the removal of the old binaries from unstable if that is
the case. Documentation is available here:
  https://wiki.debian.org/ftpmaster_Removals

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
On Mon, 14 Jul 2014 15:09:26 +0200 Cyril Brulebois  wrote:
> Source: healpy
> Version: 1.8.1-1
> Severity: serious
> Justification: ood binaries
> 
> Hi,
> 
> your package can no longer migrate to testing since it has out-of-date
> binaries on various architectures (armel armhf i386 kfreebsd-i386 mips
> mipsel powerpc s390x).
> 
> Please investigate whether restricting to *amd64 was the proper thing to
> do, and request the removal of the old binaries from unstable if that is
> the case. Documentation is available here:
>   https://wiki.debian.org/ftpmaster_Removals

At some point this was resolved as the unbuildable binaries are no longer 
around.

Scott K--- End Message ---

Bug#799694: marked as done (healpy: FTBFS on ppc64(el): No module named _tkinter)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 21:51:56 +
with message-id 
and subject line Bug#799694: fixed in healpy 1.8.1-1.1
has caused the Debian Bug report #799694,
regarding healpy: FTBFS on ppc64(el): No module named _tkinter
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.)


-- 
799694: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.8.1-1
Severity: important
Justification: fails to build from source

Builds of healpy for ppc64 and ppc64el have been failing because
python-matplotlab tries to use the tkagg backend, which requires the
python-tk package.  A typical backtrace is

  self = 
  
  def test_cartview_ma_nocrash(self):
  >   cartview(self.ma)
  
  healpy/test/test_visufunc.py:33: 
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  healpy/visufunc.py:482: in cartview
  import pylab
  /usr/lib/python2.7/dist-packages/pylab.py:1: in 
  from matplotlib.pylab import *
  /usr/lib/python2.7/dist-packages/matplotlib/pylab.py:274: in 
  from matplotlib.pyplot import *
  /usr/lib/python2.7/dist-packages/matplotlib/pyplot.py:109: in 
  _backend_mod, new_figure_manager, draw_if_interactive, _show = 
pylab_setup()
  /usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py:32: in 
pylab_setup
  globals(),locals(),[backend_name],0)
  /usr/lib/python2.7/dist-packages/matplotlib/backends/backend_tkagg.py:6: in 

  from six.moves import tkinter as Tk
  /usr/lib/python2.7/dist-packages/six.py:199: in load_module
  mod = mod._resolve()
  /usr/lib/python2.7/dist-packages/six.py:113: in _resolve
  return _import_module(self.mod)
  /usr/lib/python2.7/dist-packages/six.py:80: in _import_module
  __import__(name)
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
  
  """
  
  __version__ = "$Revision: 81008 $"
  
  import sys
  if sys.platform == "win32":
  # Attempt to configure Tcl/Tk without requiring PATH
  import FixTk
  try:
  import _tkinter
  except ImportError, msg:
  >   raise ImportError, str(msg) + ', please install the python-tk package'
  E   ImportError: No module named _tkinter, please install the python-tk 
package
  
  /usr/lib/python2.7/lib-tk/Tkinter.py:42: ImportError

I'm not sure why this issue has only come up on those particular
architectures, so you might want to consider declaring an
unconditional build dependency on python-tk to be safe.

Anyway, please do take a look.

Thanks!
--- End Message ---
--- Begin Message ---
Source: healpy
Source-Version: 1.8.1-1.1

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated healpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Oct 2015 17:21:20 -0400
Source: healpy
Binary: python-healpy python3-healpy
Architecture: source amd64
Version: 1.8.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Scott Kitterman 
Description:
 python-healpy - HEALPix representation of spherical data - Python interface
 python3-healpy - HEALPix representation of spherical data - Python interface
Closes: 799694
Changes:
 healpy (1.8.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Install matplotlibrc file that sets the matplotlib backend to Agg for
 tests in the new pybuild location for running tests (Closes: #799694)
Checksums-Sha1:
 550603c1fa34962f14f382119eb6b6e8f7b89db0 2512 healpy_1.8.1-1.1.dsc
 bf403f907c1fcc000a4d1af31eeba3ebb020089e 4208 healpy_1.8.1-1.1.debian.tar.xz
 18d2a3675b95b74ef7ece7cc43ad4af9790a820f 1850894 
python-healpy_1.8.1-1.1_amd64.deb
 65b9f55d1a2ff644caf5da6ebc21dac9010bd80b 1874108 
python3-healpy_1.8.1-1.1_amd64.deb

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Nick Black]

As a datum (I reported a duplicate of this bug as 801488), I removed both
libxmlrpc-lite-perl and libsoap-lite-perl, and still see the crash. So I
don't think they're to blame, as asserted earlier on this bug. They also
would seem unlikely causes for the gdb/valgrind output I reported in that
bug.

-- 
nick black -=- http://www.nick-black.com
to make an apple pie from scratch, you need first invent a universe.

Bug#801477: marked as done (ceph: FTBFS on armel: common/RWLock.h:29:11: error: 'atomic_t' does not name a type)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 22:23:55 +
with message-id 
and subject line Bug#801477: fixed in ceph 0.80.10-2
has caused the Debian Bug report #801477,
regarding ceph: FTBFS on armel: common/RWLock.h:29:11: error: 'atomic_t' does 
not name a type
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.)


-- 
801477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 0.80.10-1
Severity: serious

Hi,

Thanks for the upload to fix the FTBFS in sid. Unfortunately this still failed
on armel:

Excerpt from the log:

In file included from common/HeartbeatMap.h:26:0,
 from common/HeartbeatMap.cc:21:
common/RWLock.h:29:11: error: 'atomic_t' does not name a type

See the full log at:

https://buildd.debian.org/status/fetch.php?pkg=ceph=armel=0.80.10-1=1444230749

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 0.80.10-2

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

Debian distribution maintenance software
pp.
Gaudenz Steinlin  (supplier of updated ceph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Oct 2015 18:47:17 +0200
Source: ceph
Binary: ceph ceph-dbg ceph-common ceph-common-dbg ceph-mds ceph-mds-dbg 
ceph-fuse ceph-fuse-dbg rbd-fuse rbd-fuse-dbg ceph-fs-common ceph-fs-common-dbg 
ceph-resource-agents librados2 librados2-dbg librados-dev librbd1 librbd1-dbg 
librbd-dev libcephfs1 libcephfs1-dbg libcephfs-dev radosgw radosgw-dbg 
rest-bench rest-bench-dbg ceph-test ceph-test-dbg python-ceph libcephfs-java 
libcephfs-jni libcephfs-jni-dbg
Architecture: source amd64 all
Version: 0.80.10-2
Distribution: unstable
Urgency: medium
Maintainer: Ceph Maintainers 
Changed-By: Gaudenz Steinlin 
Description:
 ceph   - distributed storage and file system
 ceph-common - common utilities to mount and interact with a ceph storage cluste
 ceph-common-dbg - debugging symbols for ceph-common
 ceph-dbg   - debugging symbols for ceph
 ceph-fs-common - common utilities to mount and interact with a ceph file system
 ceph-fs-common-dbg - debugging symbols for ceph-fs-common
 ceph-fuse  - FUSE-based client for the Ceph distributed file system
 ceph-fuse-dbg - debugging symbols for ceph-fuse
 ceph-mds   - metadata server for the ceph distributed file system
 ceph-mds-dbg - debugging symbols for ceph-mds
 ceph-resource-agents - OCF-compliant resource agents for Ceph
 ceph-test  - Ceph test and benchmarking tools
 ceph-test-dbg - debugging symbols for ceph-test
 libcephfs-dev - Ceph distributed file system client library (development files)
 libcephfs-java - Java library for the Ceph File System
 libcephfs-jni - Java Native Interface library for CephFS Java bindings
 libcephfs-jni-dbg - debugging symbols for libcephfs-jni
 libcephfs1 - Ceph distributed file system client library
 libcephfs1-dbg - debugging symbols for libcephfs1
 librados-dev - RADOS distributed object store client library (development 
files)
 librados2  - RADOS distributed object store client library
 librados2-dbg - debugging symbols for librados2
 librbd-dev - RADOS block device client library (development files)
 librbd1- RADOS block device client library
 librbd1-dbg - debugging symbols for librbd1
 python-ceph - Python libraries for the Ceph distributed filesystem
 radosgw- REST gateway for RADOS distributed object store
 radosgw-dbg - debugging symbols for radosgw
 rbd-fuse   - FUSE-based rbd client for the Ceph distributed file system
 rbd-fuse-dbg - debugging symbols for rbd-fuse
 rest-bench - RESTful bencher that can be used to benchmark radosgw performance
 rest-bench-dbg - debugging symbols for rest-bench
Closes: 801477
Changes:
 ceph (0.80.10-2) unstable; urgency=medium
 .
   * [2d1482] Add upstream patch to fix building without libatomic-ops
 (Closes: #801477)
   * [4d408f] Remove build dependency on 

Bug#801640: FTBFS: cffi library '_openssl' has no function, constant or global variable named '__class__'

[Brian May]

Source: celery
Version: 3.1.18-2
Severity: serious
Justification: Does not build from source

==
ERROR: test_read_configuration_importerror 
(celery.tests.app.test_loaders.test_DefaultLoader)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "/«PKGBUILDDIR»/celery/tests/app/test_loaders.py", line 172, in 
test_read_configuration_importerror
with self.assertWarnsRegex(NotConfigured, r'make sure it exists'):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 253, in __enter__
if v and not _is_magic_module(v):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 237, in _is_magic_module
cls, modtype = m.__class__, types.ModuleType
AttributeError: cffi library '_openssl' has no function, constant or global 
variable named '__class__'

==
ERROR: test_mail_admins_errors (celery.tests.app.test_loaders.test_LoaderBase)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
  File "/«PKGBUILDDIR»/celery/tests/app/test_loaders.py", line 123, in 
test_mail_admins_errors
with self.assertWarnsRegex(SendmailWarning, r'KeyError'):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 253, in __enter__
if v and not _is_magic_module(v):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 237, in _is_magic_module
cls, modtype = m.__class__, types.ModuleType
AttributeError: cffi library '_openssl' has no function, constant or global 
variable named '__class__'

==
ERROR: test_current_loader (celery.tests.app.test_loaders.test_loaders)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 385, in __inner
return fun(self, *args, **kwargs)
  File "/«PKGBUILDDIR»/celery/tests/app/test_loaders.py", line 36, in 
test_current_loader
with self.assertPendingDeprecation():
  File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 321, in 
assertPendingDeprecation
r'scheduled for deprecation'):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 253, in __enter__
if v and not _is_magic_module(v):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 237, in _is_magic_module
cls, modtype = m.__class__, types.ModuleType
AttributeError: cffi library '_openssl' has no function, constant or global 
variable named '__class__'

==
ERROR: test_load_settings (celery.tests.app.test_loaders.test_loaders)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 385, in __inner
return fun(self, *args, **kwargs)
  File "/«PKGBUILDDIR»/celery/tests/app/test_loaders.py", line 41, in 
test_load_settings
with self.assertPendingDeprecation():
  File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 321, in 
assertPendingDeprecation
r'scheduled for deprecation'):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 253, in __enter__
if v and not _is_magic_module(v):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 237, in _is_magic_module
cls, modtype = m.__class__, types.ModuleType
AttributeError: cffi library '_openssl' has no function, constant or global 
variable named '__class__'

==
ERROR: test_compat_propertie 
(celery.tests.backends.test_redis.test_RedisBackend)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/celery/tests/backends/test_redis.py", line 166, in 
test_compat_propertie
with self.assertPendingDeprecation():
  File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 321, in 
assertPendingDeprecation
r'scheduled for deprecation'):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 253, in __enter__
if v and not _is_magic_module(v):
  File "/«PKGBUILDDIR»/celery/tests/case.py", line 237, in _is_magic_module
cls, modtype = m.__class__, types.ModuleType
AttributeError: cffi library '_openssl' has no function, constant or global 
variable named '__class__'

==
ERROR: test_warns_if_running_as_privileged_user 

Bug#783390: marked as done (pymodbus: Debian/copyright has wrong license)

[Debian Bug Tracking System]

Your message dated Mon, 12 Oct 2015 23:36:21 +
with message-id 
and subject line Bug#783390: fixed in pymodbus 1.2.0+git20150925-1
has caused the Debian Bug report #783390,
regarding pymodbus: Debian/copyright has wrong license
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.)


-- 
783390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymodbus
Version: 1.2.0-2
Severity: serious
Justification: Policy 4.5

Dear Maintainer,

The debian/copyright file lists MIT as the upstream license, but the only
references in the code are to BSD.  From setup.py in 1.2.0-2:

License :: OSI Approved :: BSD License

In the version in New that I'm reviewing for experimental, there are
additional references to BSD as well as the full text in doc/LICENSE.

Since this is a pre-existing issue with the package, I'm not rejecting due to
the issue, but it should be fixed ASAP.  Additionally, pymodbus/__init__.py
says:

TwistedModbus is built on top of the code developed by:

Copyright (c) 2001-2005 S.W.A.C. GmbH, Germany.
Copyright (c) 2001-2005 S.W.A.C. Bohemia s.r.o., Czech Republic.
Hynek Petrak 

Released under the the BSD license

These should probably be mentioned in debian/copyright as well.
--- End Message ---
--- Begin Message ---
Source: pymodbus
Source-Version: 1.2.0+git20150925-1

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

Debian distribution maintenance software
pp.
W. Martin Borgert  (supplier of updated pymodbus package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Oct 2015 22:16:13 +
Source: pymodbus
Binary: python-pymodbus
Architecture: source all
Version: 1.2.0+git20150925-1
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 

Changed-By: W. Martin Borgert 
Description:
 python-pymodbus - full Modbus protocol implementation
Closes: 783390
Changes:
 pymodbus (1.2.0+git20150925-1) unstable; urgency=low
 .
   * Use latest git from upstream, fixing some issues.
   * Use git-dpm instead of gbp for packaging.
   * Drop Python 3 patch, because upstream does not support it.
 Need to reopen #774741.
   * Correct license: BSD, not MIT (Closes: #783390).
 Thanks to Scott Kitterman!
Checksums-Sha1:
 916b3a5a587332114294d44b740994525a027ca5 2210 pymodbus_1.2.0+git20150925-1.dsc
 5feae02502eeaf5ba4753a6fc188b23e0ba3a3ab 501714 
pymodbus_1.2.0+git20150925.orig.tar.gz
 e59f8d36f9b97955e1f8f1a3c8a5e21911acb60d 4216 
pymodbus_1.2.0+git20150925-1.debian.tar.xz
 973a4c7c779994ae62471c379efcfd0d8b108252 126354 
python-pymodbus_1.2.0+git20150925-1_all.deb
Checksums-Sha256:
 280165ba8fc2c5cf22bae44af24598bfeeea7f0a1eac06bfc0a66b9be928b4d7 2210 
pymodbus_1.2.0+git20150925-1.dsc
 ca9f039aaf423225485f9c64d8de66d83c551948c1d9de41e4c424c32f77bd9a 501714 
pymodbus_1.2.0+git20150925.orig.tar.gz
 e5f0cf18b75fbb7e9b27e6d1ebd4f9a63a21d48b7399b7defea313d8702de0c3 4216 
pymodbus_1.2.0+git20150925-1.debian.tar.xz
 d5a7de95495fdc1b565b1630ebf6c01add4043fed7acf4bc24f6fd474ee496de 126354 
python-pymodbus_1.2.0+git20150925-1_all.deb
Files:
 03dad82eff4c021e9cd779a900cbee74 2210 python optional 
pymodbus_1.2.0+git20150925-1.dsc
 b095259e94a98b859d975d1109118948 501714 python optional 
pymodbus_1.2.0+git20150925.orig.tar.gz
 a6787fea30c3474401d52d2656b768d8 4216 python optional 
pymodbus_1.2.0+git20150925-1.debian.tar.xz
 2f6a567663f40f79a12e1cb5809a0475 126354 python optional 
python-pymodbus_1.2.0+git20150925-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIbBAEBCAAGBQJWHD/vAAoJEOPgocKGuWPqwyoP91tWtFIkuSrlTsVDqjAYbn6y
Nil9eRwyxfYNt2BDJvfAW4TUCtNsV/SKEu0nevY9p1SHXkfo5yAiRxrsCxCm97+S
IvL+8pT/rqonyZhAe4WT3T1jXbH8u370rMMVw8cBbf0bHwxHnNyBeOWdCtrEXZrM
U+zGApHbm1k/2BKPzrWoMpwoplqtwFpuRscfFR0BKB5x6V+7tZhQiKz6yaBSu4kM
ssx/xDOejg8LQm3jH8DJSAdA54/7FdgG29b5Ag5jgn2HDVM8Bei0Ci1zDXXi/f96

Processed: tagging 799694

[Debian Bug Tracking System]

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

> tags 799694 + pending
Bug #799694 [src:healpy] healpy: FTBFS on ppc64(el): No module named _tkinter
Bug #800672 [src:healpy] healpy: FTBFS: Tests require X environment
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#796466: pepper: FTBFS: error: ‘svn_sort__hash’ was not declared in this scope

[Jonas Gehring]

Sorry for the huge delay here, and thanks for the report!. I could
reproduce the issue and fixed it by simply re-implementing the extract
keys + sort logic of svn_sort__hash()
(https://github.com/jgehring/pepper/commit/8b67dbf). I'll prepare a new
release soon.

Bug#799694: Not just ppc64

[Scott Kitterman]

On Tue, 06 Oct 2015 12:58:23 + Tristan Seligmann  
wrote:
> Control: severity -1 serious
> 
> This appears to be happening on all arches, not just ppc64. See, for
> example:
> 
> 
https://buildd.debian.org/status/fetch.php?pkg=healpy=amd64=1.8.1-1%2Bb2=1444131922

NMU diff attached.  The issue here is that pybuild changed where it runs its 
tests and so the matplotlibrc that's generated to support tests was no longer 
in the right location.

This is blocking completion of the python3.5 transition, so I'll upload 
shortly.

Scott Kdiff -Nru healpy-1.8.1/debian/changelog healpy-1.8.1/debian/changelog
--- healpy-1.8.1/debian/changelog	2014-06-29 20:12:07.0 -0400
+++ healpy-1.8.1/debian/changelog	2015-10-12 17:26:27.0 -0400
@@ -1,3 +1,11 @@
+healpy (1.8.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Install matplotlibrc file that sets the matplotlib backend to Agg for
+tests in the new pybuild location for running tests (Closes: #799694)
+
+ -- Scott Kitterman   Mon, 12 Oct 2015 17:21:20 -0400
+
 healpy (1.8.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru healpy-1.8.1/debian/rules healpy-1.8.1/debian/rules
--- healpy-1.8.1/debian/rules	2014-06-24 22:04:32.0 -0400
+++ healpy-1.8.1/debian/rules	2015-10-12 17:28:22.0 -0400
@@ -14,4 +14,8 @@
 	echo backend: agg > $@
 
 override_dh_auto_test: matplotlibrc
+	cp matplotlibrc .pybuild/pythonX.Y_2.7/build/
+	for pv in $(shell (py3versions -vr)); do \
+		cp matplotlibrc .pybuild/pythonX.Y_$$pv/build/ ; \
+	done
 	dh_auto_test

Bug#801430: aptitude: segfault maybe casued by package dependency loop aptitudeDepCache::internal_mark_delete loop here

[Nick Black]

As a datum (I reported a duplicate of this bug as 801488), I removed both
libxmlrpc-lite-perl and libsoap-lite-perl, and still see the crash. So I
don't think they're to blame, as asserted earlier on this bug. They also
would seem unlikely causes for the gdb/valgrind output I reported in that
bug.

-- 
nick black -=- http://www.nick-black.com
to make an apple pie from scratch, you need first invent a universe.

Bug#754803: healpy: out-of-date binaries

[Scott Kitterman]

On Monday, October 12, 2015 05:42:51 PM Scott Kitterman wrote:
> On Mon, 14 Jul 2014 15:09:26 +0200 Cyril Brulebois  wrote:
> > Source: healpy
> > Version: 1.8.1-1
> > Severity: serious
> > Justification: ood binaries
> > 
> > Hi,
> > 
> > your package can no longer migrate to testing since it has out-of-date
> > binaries on various architectures (armel armhf i386 kfreebsd-i386 mips
> > mipsel powerpc s390x).
> > 
> > Please investigate whether restricting to *amd64 was the proper thing to
> > do, and request the removal of the old binaries from unstable if that is
> > 
> > the case. Documentation is available here:
> >   https://wiki.debian.org/ftpmaster_Removals
> 
> At some point this was resolved as the unbuildable binaries are no longer
> around.
> 
> Scott K

Meh.  I'm wrong.  As penance, I'll file the rm bug to clean this up.

Scott K

Bug#801415: ejabberd: maintainer is not maintainer

[Philipp Huebner]

Hi

On 12.10.2015 14:54, Konstantin Khomoutov wrote:
> On Fri, 09 Oct 2015 22:33:59 +0200 Dominik George
>  wrote:
>> Please update the maintainer field or orphan the package.
> 
> While I'm dissatisfied, to put it mildly, with what the submitter 
> wrote in this bug report regarding me being «unable to respond to any
> requests», the crux of their report -- that I'm not really packaging
> ejabberd for some time -- is true, and I'm of course fine with
> officially resigning if it's deemed the right thing to do with those
> doing actual packaging.
> 
> Hence I'd like to hear opinions from Philipp and Rhonda about what 
> should I do next (if I should).

Personally I don't mind in this case who is listed as maintainer and who
is listed as uploader, anybody who looks into the changelog or the PTS
can see at once who the most active uploader recently is and direct
questions accordingly.

What annoys me more is that this bug will block the migration to testing
soon and hence delay the availabilty of ejabberd 15.09 in Jessie Backports.


Back in March 2014 I actually e-mailed Konstantin with a request similar
to this bug report:
[...]
>> If you're too busy, that's okay, but if this isn't going to change
>> in the near future it would be very nice of you to orphan the
>> package so other's can take over.
> 
> Before I comment on this please understand that I'm not about
> offending you. I'm not the native speaker so what I intend to write
> might not sound quite polite but I don't really want to insult you!
> 
> The problem with your statement is that while I understand it's
> really bad for the community that I'm abstraining from doing my
> maintainership work (and I do feel guilty for this, honest!), so far
> other people did little but prodding me about this.  Prodding *is*
> good but talk is cheap while finding time to do quality packaging
> work is hard. Hence currently I'm quite confident that merely
> orphaning the package will do nothing to it because the only active
> community member -- my uploader Rhonda -- has no time either to do
> packaging work for ejabberd.
> 
> Another contributing factor for me not resigning is that before I
> even embarked on maintaining ejabberd in Debian I made friends with
> three of ejabberd's core developers (one of them, its initial author,
> resigned since then) and with jabber.ru staff (jabber.ru is arguably
> the largest public XMPP server running ejabberd), and with Erlang
> maintainer (with him I even periodically meet face-to-face) [*].
> This places me in a somewhat unique position which many times proved
> its usefulness: it allows me to solve various problems quickly
> because I'm typically able to ask the relevant persons for help
> directly rather than spending time in bug trackers etc.  I mean, this
> makes me useful exactly for maintaining ejabberd and tkabber -- my
> two source packages in Debian. The fact I'm Erlang-literate also
> helped several times.
> 
>> Please get back to me about this.
> 
> Sure.  The bottom line of my thoughts is that if you feel like
> really do the packaging work and not merely hand-waving (like did
> most who contacted me about the stagnation of my work) I'll hand it
> over to you and will try to help you solve problems should they
> arise.
> 
> Otherwise let's see if I will find time to get things done myself as
> I did not yet abandon this hope. ;-)
> 
> [*] That's because I helped develop the Tkabber XMPP client which has
> been concieved by the same gang of folks back then.

I then actually did step in and began to help ;)

Anyway, Konstantin's reasoning appeared and still appears very sound to
me and he still checks in at the Packaging MUC from time to time and is
still reachable, so I am fine with him staying listed as the maintainer.
He has done a great job maintaining ejabberd for quite some time.

Just as well I wouldn't mind switching places (Uploader vs. Maintainer)
with Konstantin. The idea of orphaning the package however is pure
nonsense, as it is currently well-maintained.

Another option would be to create some kind of team address and put that
in the maintainer field.

I'd like to hear Rhonda's opinion on this as well.



On 12.10.2015 15:03, Dominik George wrote:
> Am Montag, 12. Oktober 2015, 15:54:45 schrieb Konstantin Khomoutov:
>> Another room of interest is pkg-ejabb...@deb.at which is dedicated 
>> to packaging ejabberd for Debian.

Maybe this quote is incomplete, but I wonder why you didn't point him to
ejabb...@chat.deb.at instead, that being Rhonda's channel for the
official ejabberd packaging for Debian.


Regards,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Bug#801203: marked as done (kazam: Fails to start, throws a trace)

[Debian Bug Tracking System]

Your message dated Tue, 13 Oct 2015 03:56:06 +
with message-id 
and subject line Bug#801203: fixed in kazam 1.4.5-2
has caused the Debian Bug report #801203,
regarding kazam: Fails to start, throws a trace
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.)


-- 
801203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801203
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kazam
Version: 1.4.5-1
Severity: grave
Justification: renders package unusable

Hello,

Kazam no longer starts - the following trace is shown instead:

```
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version 
first. Use gi.require_version('Gtk', '3.0') before import to ensure that the 
right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/kazam/backend/prefs.py:28: PyGIWarning: GdkX11 
was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gdk, GdkX11
Traceback (most recent call last):
  File "/usr/bin/kazam", line 146, in 
from kazam.app import KazamApp
  File "/usr/lib/python3/dist-packages/kazam/app.py", line 35, in 
from kazam.backend.prefs import *
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 478, in 

prefs = Prefs()
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 121, in 
__init__
self.read_config()
  File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 199, in 
read_config
self.audio_source = int(self.config.get("main", "audio_source"))
  File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 103, in 
get
return ConfigParser.get(self, section, key)
  File "/usr/lib/python3.4/configparser.py", line 772, in get
d)
  File "/usr/lib/python3.4/configparser.py", line 371, in before_get
self._interpolate_some(parser, option, L, value, section, defaults, 1)
  File "/usr/lib/python3.4/configparser.py", line 384, in _interpolate_some
rawval = parser.get(section, option, raw=True, fallback=rest)
TypeError: get() got an unexpected keyword argument 'raw'
```


Best regards,

George

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

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

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.6.0-1
ii  gir1.2-gstreamer-1.0 1.6.0-1
ii  gir1.2-keybinder-3.0 0.3.0-1
ii  gir1.2-wnck-3.0  3.14.0-2
ii  gnome-session-canberra   0.30-2.1
ii  gstreamer1.0-plugins-base1.6.0-1
ii  gstreamer1.0-plugins-good1.6.0-1
ii  gstreamer1.0-plugins-ugly1.6.0-1
ii  gstreamer1.0-pulseaudio  1.6.0-1
ii  python3  3.4.3-6
ii  python3-cairo1.10.0+dfsg-5
ii  python3-dbus 1.2.0-2+b4
ii  python3-gi   3.18.0-1
ii  python3-gi-cairo 3.18.0-1
ii  python3-xdg  0.25-4
pn  python3:any  

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.6.0-1

kazam suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: kazam
Source-Version: 1.4.5-2

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated kazam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 12 Oct 2015 21:33:25 -0400
Source: kazam
Binary: kazam
Architecture: source all
Version: 1.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Andrew Starr-Bochicchio 
Description:
 kazam  

Processed: Re: Bug#801497: docdiff: non-free file "devutil/JIS0208.TXT"

[Debian Bug Tracking System]

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

> tag 801497 fixed-upstream pending
Bug #801497 [src:docdiff] docdiff: non-free file "devutil/JIS0208.TXT"
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 784839 + pending
Bug #784839 [mayavi2] mayavi2: please package new upstream version
Added tag(s) pending.
> tag 798169 + pending
Bug #798169 [src:mayavi2] mayavi2: depends on vtk 5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#798169: marked as done (mayavi2: depends on vtk 5)

[Debian Bug Tracking System]

Your message dated Tue, 13 Oct 2015 04:36:55 +
with message-id 
and subject line Bug#798169: fixed in mayavi2 4.4.3-1
has caused the Debian Bug report #798169,
regarding mayavi2: depends on vtk 5
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.)


-- 
798169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mayavi2
Version: 4.3.1-4.1
Severity: serious
Tags: sid stretch
Control: block 798164 with -1

Hi,

your package depends on vtk 5.x, which should not be in stretch.  Please
switch to vtk 6.x or drop the dependency.

Thanks,
Julien


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: mayavi2
Source-Version: 4.4.3-1

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

Debian distribution maintenance software
pp.
Varun Hiremath  (supplier of updated mayavi2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 12 Oct 2015 21:52:54 -0400
Source: mayavi2
Binary: mayavi2
Architecture: source amd64
Version: 4.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Varun Hiremath 
Description:
 mayavi2- scientific visualization package for 2-D and 3-D data
Closes: 784839 798169
Changes:
 mayavi2 (4.4.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #784839)
   * Bump Standards-Version to 3.9.6
   * d/control: BD on python-vtk6 (Closes: #798169)
   * Fix d/watch file
Checksums-Sha1:
 6d49bae02548e6b31e01754f86de4afe8968edf6 2057 mayavi2_4.4.3-1.dsc
 1e3bf4642958c134c287392dd97e49ba95cb219a 6556983 mayavi2_4.4.3.orig.tar.gz
 844c135529ca376cbdeadb98aa99748351cb3efa 12768 mayavi2_4.4.3-1.debian.tar.xz
 9c0ef81750f4332fefbc5307034c22af88135c59 21856496 mayavi2_4.4.3-1_amd64.deb
Checksums-Sha256:
 02d1c247d59f506f1fe374a1cbc9cb5296d5b9aff6dead9a677a5a4104daedd3 2057 
mayavi2_4.4.3-1.dsc
 2d1005421c1357ff9942372870787a48c86da51cfff40c92ae36c7f681db03e8 6556983 
mayavi2_4.4.3.orig.tar.gz
 b8fe4b0742602e502e3a29874703f692c0a8a0449e7f880a7931440d3271c5e3 12768 
mayavi2_4.4.3-1.debian.tar.xz
 00de90e2a71cb6217e15b45d4b76e84e959ae97ce3a272ef60f04d06dc98bd36 21856496 
mayavi2_4.4.3-1_amd64.deb
Files:
 c30c7e7977803320ccb81f5ff743d32f 2057 science optional mayavi2_4.4.3-1.dsc
 8ad9aa94ed425697f0d1969822b17005 6556983 science optional 
mayavi2_4.4.3.orig.tar.gz
 e8aaa6ac6f067e25d031aec2f575b8a3 12768 science optional 
mayavi2_4.4.3-1.debian.tar.xz
 07ba279d55d0c02f29cf06841fa19508 21856496 science optional 
mayavi2_4.4.3-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWHIBHAAoJEHA3PPEpDbnOE3UP/1LE4uqX3F7/rvdNVjddiNjK
BlD4t1zjCD3k/gToOB3bZP9iOIe6e7/PdYEdviF4Q8lUPFZF2mHbX/fjEvhM2UEa
Z5E/ZPbYeHoHlWbtDHEDLVCa7i7ly4T0jAvy0+AFOa/OtYjwx8tMmbFKjnkyUQG7
WOwyOfPsbohX07cOU3qIRZxeb3vYybXAc7sgkYwPj59X1fp/OYX8u9SbAwNZqyPi
knZ7KYsZQSGWTFvd4eCJvvypf7as2XTTbUaDcs55HGxoDQo2WfUkAUBYhUlIIboG
KEZbhfXhmbeDvFp+S2V96+fh9iesi7eUySlO1/4+ubk3ohbqaH6D4AZgqU6YXe21
6yX5WyVCUE5f58UjPAvqGWXx+xcMSJtGibuIWwOTHfyvgfDDCvNshrMzX9fdr2EB
JOVsDAyZiEej81prAuxTjvklfeXUsnQUbRCcpKPtKLEo6yazozYQ52sr7WqrGYr7
G9+wOxYdiJY04vcOqV7m+/OD2QP1dHeAPcmav2y9fH7ybFb+Ybxufhlv6MFglIgT
TVfWjeO0b8TPBwU5LZ2xXiTMtN/l1nuGRdZdntkt9a6joT9B/rYTYAK32wrmJ32F
Np0DRa9+2Y1VQrX1hEopfLU1vfbQWDmZWGCzsqgFM8FaXzHJ+iOarmrEAjCxIc96
mV1rKTenjMl7gWjoEnka
=DLCa
-END PGP SIGNATURE End Message ---

Bug#775554: marked as done (Please update dependency python-aptdaemon-gtk)

[Debian Bug Tracking System]

Your message dated Tue, 13 Oct 2015 04:36:36 +
with message-id 
and subject line Bug#775554: fixed in isenkram 0.19
has caused the Debian Bug report #775554,
regarding Please update dependency python-aptdaemon-gtk
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.)


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

python-aptdaemon-gtk is now a transitional package. It could probably
be replaced by python-aptdaemon.gtk3widgets.

This probably made the package disappear from recent Ubuntu versions,
as the transitional package is not available there.

--

Marius
--- End Message ---
--- Begin Message ---
Source: isenkram
Source-Version: 0.19

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen  (supplier of updated isenkram package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 13 Oct 2015 06:09:25 +0200
Source: isenkram
Binary: isenkram isenkram-cli
Architecture: source all
Version: 0.19
Distribution: unstable
Urgency: low
Maintainer: Petter Reinholdtsen 
Changed-By: Petter Reinholdtsen 
Description:
 isenkram   - Suggest packages to install when inserting new hardware (GUI popu
 isenkram-cli - Suggest packages to install when inserting new hardware (CLI 
tool
Closes: 769664 775554 783831
Changes:
 isenkram (0.19) unstable; urgency=low
 .
   [ Petter Reinholdtsen ]
   * Add forgotten file tasksel/packages/for-current-hardware-firmware
 to isenkram-cli (Closes: #783831).
   * Add missing Settings category to desktop file.
   * Fix python space/formatting issues reported by 'pep8 --ignore W191'.
   * Updated generated firmware lists.
   * Modify text of button showed in event to fit it smaller screen estate.
   * Remove obsolete conflicts/replaces on hw-support-handler.
   * Reduce isenkram-cli deb size. (Closes: #769664)
   * Updated standards-version from 3.9.5 to 3.9.6.  No changes needed.
   * Move from debhelper 8 to 9.
 .
   [ Julian Andres Klode ]
   * Port to GObject introspection (Closes: #775554)
Checksums-Sha1:
 2b6c7360acc98dfdb386fda151c44bfe737c869c 1780 isenkram_0.19.dsc
 2b9b7336b5ecb4be6407b9aa8696192bfdaf1acc 157872 isenkram_0.19.tar.gz
 cdc1acb8d120a4961b3ff352bd45fe4c40e08d61 22050 isenkram-cli_0.19_all.deb
 dca298d1793d23b7527beae9fbf5d758c7d07b12 7992 isenkram_0.19_all.deb
Checksums-Sha256:
 a728d602bc70a2f8326bd0a3c7804ff925ba45ff2bba9bc0dee7216436643ede 1780 
isenkram_0.19.dsc
 7f25963806616a8054d6bb760c27222e694f7edc0bf84f040333f9cd29d18f60 157872 
isenkram_0.19.tar.gz
 52236d35dfce1170b2e22bc54a8600be4a73347672f78fcc97208c29a1cd2bee 22050 
isenkram-cli_0.19_all.deb
 8b3bc77703f166d8abb557e20ea2ccb586065daca3c48156a6bd84f1f60adc41 7992 
isenkram_0.19_all.deb
Files:
 b7369f324b4272d1b14c9a7983b1e981 1780 misc optional isenkram_0.19.dsc
 b8a8118142f2dd5ab9dffe1e6b5b391a 157872 misc optional isenkram_0.19.tar.gz
 b3aff94bff1307144bc055b07d21cc5e 22050 misc optional isenkram-cli_0.19_all.deb
 88bb2224a8f9988067b889d6b10978ec 7992 misc extra isenkram_0.19_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWHIS8AAoJEJr0azAldxsxaOoP+wQ0HscZq8sQaexuwhmlEPJr
Bg4CzC5HYK+glNwv5kBO9zS78Nu0fge0rgjhMXTA04bQM4EY2n8ufDSsRYA/hKpW
NsxzFr5kBrVAhv33P01ETW0SAZhDXz4Aogg67mx5Pwd7uOTe55n47m5VNxAvLa2e
F74bAu58E3crkoSiKUcrP8rfhZ/hcueWOBGAUg/f2jO+gZGxtHju1Sxsnn2e8uVv
PcDF/c3+ahPeC+vKhmgXZ7XcW7sYU65/uTpEGY5/C32Tkdm63CrV1rm3Y7YWk0vc
jUq7aI3aclBZt630Un2a6erkoECJFWf8AfzvCQAEwTEorz0gGKCPvDk3aHPOzK79
sujnh7Tut9Td9yKxlrM3s+4TWQK5EgHhf4unqkjn0Xwi8tw1bl9ogVYi9QTwfWP/
J8ozhRc0+RBiL0taoGM0RdLlNZ5IQbtOdKp1hROFiISivjqlW9EDLh3Fc/Xo1GNf
E/BQn+AGKjnkxEPwmtzPOnzLu3ZCUgi8IkxQZKDSjg62VKRCAzXZ1A+absnZfSXh
P7SlKO5PRuV6f8vOiDwy7g72lcFLk6GRfPNJTeJw+xobC9UjhwDbOIdCWEfp2XsV
J/smDPHSvdTlBW7sM09mTFHzxxY51ddBNAvcMebJweZX7Iw19PtrSKmD1nUYFrKE
8ZHBLaLksEnAP9FbrHgD
=8inO

Bug#799449: marked as done (apparmor: FTBFS: test suite segfaults on mips and mipsel)

[Debian Bug Tracking System]

Your message dated Tue, 13 Oct 2015 07:47:20 +0200
with message-id <561c9ae8.2040...@debian.org>
and subject line Re: [pkg-apparmor] Processed: severity of 799449 is serious
has caused the Debian Bug report #799449,
regarding apparmor: FTBFS: test suite segfaults on mips and mipsel
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.)


-- 
799449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apparmor
Version: 2.10-2
Severity: important

https://buildd.debian.org/status/fetch.php?pkg=apparmor=mips=2.10-2=1442250379
https://buildd.debian.org/status/fetch.php?pkg=apparmor=mipsel=2.10-2=1442250826

I've reproduced these segfaults on the minkus.debian.org (mips) and
eder.debian.org (mipsel) porterboxes.

Note that:

 * 2.10-1 built just fine on those architectures' buildds when that
   package was uploaded to experimental.
 * I tried building 2.9.2-3 on these two porterboxes => I see the same
   segfault and FTBFS, and running ./parser/tst_regex by hand indeed
   tells me: "zsh: segmentation fault  ./parser/tst_regex"

=> so this looks like the breakage was triggered by some change in the
build environment, rather than in the source package itself. (Which
doesn't necessarily mean that the source package is innocent,
though :)

Could it be that there's some inconsistency between the version of
libapparmor we're building/linking the test programs against, and the
version we're running them with? The system's libapparmor1 (2.9.2-3),
has been built before the GCC-5 transition.

Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
On 06.10.2015 21:40, Felix Geyer wrote:
> Control: tags -1 - help
> 
> This issue is most likely caused by g++ bug #799811.

AppArmor built fine now on mips*, closing.

Felix--- End Message ---