Bug#764005: targetcli: Upgrade issues from 2.1-1

[Jerome Martin]

Thanks Chris,

I'll take a look at it in the coming days!

Best,
--
Jerome

On 12/17/2014 11:03 PM, Chris Boot wrote:

On 17 Dec 2014, at 21:11, Chris Boot  wrote:


On 17 Dec 2014, at 13:56, Ritesh Raj Sarraf  wrote:


On 10/07/2014 03:54 PM, Jerome Martin wrote:



On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote:

On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote:

Okay!! Thanks to both of you. I will prepare something next week. My
only request is if (other) users can test it in time.


By the way, Jerome, do you still plan on a newer release  of the LIO
stack ? Or is this, the one I pushed to Debian, good from your point of
view ?


Yes, an update is on its way.
This should not impact the iSCSI use-case too much, the aim will be updates to 
the HW fabrics support mostly, along with a few minor bug-fixes here and there.


Jerome: Based on what we last talked, I went ahead and created tarballs 
accordingly. I now have a beter LIO stack with proper versioning. I have pushed 
it to experimental as Debian Jesssie is in freeze.

rrs@learner:/var/tmp/Debian-Build/Result$ sudo targetcli
[sudo] password for rrs:
targetcli 3.0.pre4.1~ga55d018 (rtslib 3.0.pre4.1~g1b33ceb)
Copyright (c) 2011-2014 by Datera, Inc.
All rights reserved.

/> ls
o- / 
.
 [...]
  o- backstores 
..
 [...]
  | o- fileio 
...
 [0 Storage Object]
  | o- iblock 
...
 [0 Storage Object]
  | o- pscsi 

 [0 Storage Object]
  | o- rd_mcp 
...
 [0 Storage Object]
  o- ib_srpt 
...
 [0 Targets]
  o- iscsi 
.
 [0 Targets]
  o- loopback 
..
 [0 Targets]
  o- qla2xxx 
...
 [0 Targets]
  o- tcm_fc 

 [0 Targets]
  o- vhost 
.
 [0 Targets]
/> exit
Comparing startup and running configs...
Startup config is up-to-date.
19:23 ♒♒♒  ☺
rrs@learner:/var/tmp/Debian-Build/Result$


This looks much better. Chris: If you have some time, you may want to play with 
this version, from experimental ??


Hi Ritesh,

This version is much better, but still doesn’t work with my qla2xxx targets 
unfortunately. When saving the configuration, I get:

ConfigError: Unknown value type 'qla2xxx_wwn' when validating 
21:02:00:e0:8b:d1:67:2c


Hi Ritesh, Jerome,

I wrote a patch that appears to fix this for me, through admittedly I haven’t 
tested it very extensively yet:

https://github.com/Datera/rtslib/pull/5
https://github.com/bootc/rtslib/commit/727c345bd18137c424e4fba62bfab7bcfabfc024

That allows the configuration to be saved, at least. I haven’t yet tested 
manipulating targets (creating/changing/removing them) or rebooting my server 
to see whether they get restored correctly, but targetcli appears to make the 
right noises so far.

HTH,
Chris




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

Processed: fixed 773417 in 12.4-2+deb6u1

[Debian Bug Tracking System]

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

> fixed 773417 12.4-2+deb6u1
Bug #773417 [src:heirloom-mailx] heirloom-mailx: CVE-2004-2771 CVE-2014-7844
Marked as fixed in versions heirloom-mailx/12.4-2+deb6u1.
> thanks
Stopping processing here.

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


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

Processed: heirloom-mailx: CVE-2004-2771 CVE-2014-7844

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 12.5-2+deb7u1
Bug #773417 [src:heirloom-mailx] heirloom-mailx: CVE-2004-2771 CVE-2014-7844
Marked as fixed in versions heirloom-mailx/12.5-2+deb7u1.

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


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

Bug#773417: heirloom-mailx: CVE-2004-2771 CVE-2014-7844

[Salvatore Bonaccorso]

Source: heirloom-mailx
Version: 12.4-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: fixed -1 12.5-2+deb7u1

Hi,

the following vulnerabilities were published for heirloom-mailx.

 * CVE-2004-2771[0]
 * CVE-2014-7844[1]

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2004-2771
[1] https://security-tracker.debian.org/tracker/CVE-2014-7844

Regards,
Salvatore


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

Bug#773187: remmina-plugin-rdp is not installable due to broken dependencies

[Luca Falavigna]

2014-12-15 17:26 GMT+01:00 Pirate Praveen :
> No, it is not visible in my system (see screenshot). Does it need a reboot?

Normally not, restarting remmina is usually more than enough.

Could you attach the listing of ls -l /usr/lib/*/remmina/plugins ?

Mine appears like the following:
$ ls -l /usr/lib/*/remmina/plugins
total 124
-rw-r--r-- 1 root root 78808 Nov 20 22:46 remmina-plugin-rdp.so
-rw-r--r-- 1 root root 44600 Nov 20 22:46 remmina-plugin-vnc.so
$

Cheers,
Luca


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

Processed: fix version for 772873

[Debian Bug Tracking System]

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

> # affects jessie
> found 772873 11.87-3
Bug #772873 [auctex] auctex: Trigger cycle causes dpkg to fail processing
Marked as found in versions auctex/11.87-3.
> thanks
Stopping processing here.

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


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

Processed: fix version for 772870

[Debian Bug Tracking System]

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

> # affects jessie
> found 772870 5.3.2+20141104-1
Bug #772870 {Done: Sylvain Beucler } 
[fusionforge-plugin-mediawiki] fusionforge-plugin-mediawiki: Trigger cycle 
causes dpkg to fail processing
Marked as found in versions fusionforge/5.3.2+20141104-1.
> thanks
Stopping processing here.

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


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

Processed: fix version for 772862

[Debian Bug Tracking System]

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

> # affects jessie
> found 772862 4.0.1+dfsg-1
Bug #772862 [wordpress] wordpress: Trigger cycle causes dpkg to fail processing
Marked as found in versions wordpress/4.0.1+dfsg-1.
> thanks
Stopping processing here.

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


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

Bug#773416: ettercap: CVE-2014-6395 CVE-2014-6396 CVE-2014-9376 CVE-2014-9377 CVE-2014-9378 CVE-2014-9379 CVE-2014-9380 CVE-2014-9381

[Moritz Muehlenhoff]

Package: ettercap
Severity: grave
Tags: security
Justification: user security hole

Hi,
please see
https://www.obrela.com/home/security-labs/advisories/osi-advisory-osi-1402/
for details and patches.

Cheers,
Moritz


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

Processed: tag patch

[Debian Bug Tracking System]

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

> # fix is in svn
> tags 773315 patch
Bug #773315 [subversion] subversion: CVE-2014-8108
Added tag(s) patch.
> tags 773263 patch
Bug #773263 [subversion] subversion: CVE-2014-3580
Added tag(s) patch.
> thanks
Stopping processing here.

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


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

Processed: efivar efibootmgr 32/64-bit bug

[Debian Bug Tracking System]

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

> package efivar
Limiting to bugs with field 'package' containing at least one of 'efivar'
Limit currently set to 'package':'efivar'

> found 773412 0.15-2
Bug #773412 [efivar] make efivar's vars.c interface choose between 32 and 64 
bit at runtime
Marked as found in versions efivar/0.15-2.
> fixed 773412 0.15-3
Bug #773412 [efivar] make efivar's vars.c interface choose between 32 and 64 
bit at runtime
Marked as fixed in versions efivar/0.15-3.
> severity 773412 critical
Bug #773412 [efivar] make efivar's vars.c interface choose between 32 and 64 
bit at runtime
Severity set to 'critical' from 'serious'
> affects 773412 = efibootmgr
Bug #773412 [efivar] make efivar's vars.c interface choose between 32 and 64 
bit at runtime
Added indication that 773412 affects efibootmgr
> package efibootmgr
Limiting to bugs with field 'package' containing at least one of 'efibootmgr'
Limit currently set to 'package':'efibootmgr'

> severity 773007 critical
Bug #773007 [efibootmgr] efibootmgr: make the optional_data_len size signed
Severity set to 'critical' from 'serious'
> fixed 773007 0.11.0-3
Bug #773007 [efibootmgr] efibootmgr: make the optional_data_len size signed
Marked as fixed in versions efibootmgr/0.11.0-3.
> --
Stopping processing here.

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


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

Processed: clone to efivar

[Debian Bug Tracking System]

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

> retitle 773007 efibootmgr: make the optional_data_len size signed
Bug #773007 [efibootmgr] Doesn't work on i386, crashes also
Changed Bug title to 'efibootmgr: make the optional_data_len size signed' from 
'Doesn't work on i386, crashes also'
> clone 773007 -1
Bug #773007 [efibootmgr] efibootmgr: make the optional_data_len size signed
Bug 773007 cloned as bug 773412
> reassign -1 efivar
Bug #773412 [efibootmgr] efibootmgr: make the optional_data_len size signed
Bug reassigned from package 'efibootmgr' to 'efivar'.
No longer marked as found in versions efibootmgr/0.9.0-2.
Ignoring request to alter fixed versions of bug #773412 to the same values 
previously set
> tags -1 upstream jessie sid
Bug #773412 [efivar] efibootmgr: make the optional_data_len size signed
Ignoring request to alter tags of bug #773412 to the same tags previously set
> retitle -1 make efivar's vars.c interface choose between 32 and 64 bit at 
> runtime
Bug #773412 [efivar] efibootmgr: make the optional_data_len size signed
Changed Bug title to 'make efivar's vars.c interface choose between 32 and 64 
bit at runtime' from 'efibootmgr: make the optional_data_len size signed'
>
End of message, stopping processing here.

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


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

Bug#768889: tags jessie sid

[D. Jared Dominguez]

control: tags -1 + jessie
control: tags -1 + sid

--
Jared Domínguez
Server OS Engineering
Dell | Enterprise Solutions Group


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

Processed: tags jessie sid

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + jessie
Bug #768889 {Done: Andreas Bombe } [efibootmgr] efibootmgr: 
"dpkg-buildpackage -b" installs efibootmgr in /usr/sbin
Added tag(s) jessie.
> tags -1 + sid
Bug #768889 {Done: Andreas Bombe } [efibootmgr] efibootmgr: 
"dpkg-buildpackage -b" installs efibootmgr in /usr/sbin
Added tag(s) sid.

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


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

Bug#773007: tags jessie sid

[D. Jared Dominguez]

control: tags -1 + jessie
control: tags -1 + sid

--
Jared Domínguez
Server OS Engineering
Dell | Enterprise Solutions Group


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

Processed: tags jessie sid

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + jessie
Bug #773007 [efibootmgr] Doesn't work on i386, crashes also
Added tag(s) jessie.
> tags -1 + sid
Bug #773007 [efibootmgr] Doesn't work on i386, crashes also
Added tag(s) sid.

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


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

Processed: tags jessie sid

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + jessie
Bug #768880 {Done: Daniel Jared Dominguez } 
[efibootmgr] efibootmgr: unusable if reading any boot variable fails
Added tag(s) jessie.
> tags -1 + sid
Bug #768880 {Done: Daniel Jared Dominguez } 
[efibootmgr] efibootmgr: unusable if reading any boot variable fails
Added tag(s) sid.

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


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

Bug#768880: tags jessie sid

[D. Jared Dominguez]

control: tags -1 + jessie
control: tags -1 + sid

--
Jared Domínguez
Server OS Engineering
Dell | Enterprise Solutions Group


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

Bug#768880: marked as done (efibootmgr: unusable if reading any boot variable fails)

[Debian Bug Tracking System]

Your message dated Thu, 18 Dec 2014 04:03:54 +
with message-id 
and subject line Bug#768880: fixed in efibootmgr 0.11.0-2
has caused the Debian Bug report #768880,
regarding efibootmgr: unusable if reading any boot variable fails
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.)


-- 
768880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: efibootmgr
Version: 0.11.0-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

On my system, reading Boot0005 fails with EIO:

openat(AT_FDCWD, "/sys/firmware/efi/vars/", 
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
brk(0)  = 0xfda000
brk(0x1003000)  = 0x1003000
fcntl(3, F_GETFD)   = 0x1 (flags FD_CLOEXEC)
fcntl(3, F_SETFD, FD_CLOEXEC)   = 0
getdents(3, /* 103 entries */, 32768)   = 7336
getdents(3, /* 0 entries */, 32768) = 0
close(3)= 0
open("/sys/firmware/efi/vars/Boot-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var",
 O_RDONLY) = 3
read(3, "B\0o\0o\0t\\\\\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 2084
read(3, "", 2012)   = 0
close(3)= 0
open("/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var",
 O_RDONLY) = 3
read(3, "B\0o\0o\0t\\\\0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 2084
read(3, "", 2012)   = 0
close(3)= 0
open("/sys/firmware/efi/vars/Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var",
 O_RDONLY) = 3
read(3, "B\0o\0o\0t\\\\0002\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
4096) = 2084
read(3, "", 2012)   = 0
close(3)= 0
open("/sys/firmware/efi/vars/Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var",
 O_RDONLY) = 3
read(3, 0xfdb170, 4096) = -1 EIO (Input/output error)
close(3)= 0
write(2, "efibootmgr: ", 12)= 12
write(2, "efibootmgr", 10)  = 10
write(2, ": ", 2)   = 2
write(2, "Input/output error\n", 19)= 19
exit_group(1)   = ?

Old versions of efibootmgr and libefivar0 allowed me to install the
necessary EFI boot entries. It seems that an old libefivar0 did not report
read errors.

Then libefivar0 started to crash on unreadable variables (see Debian bug
764386). Since that bug has been fixed, efibootmgr doesn't crash anymore,
but the read errors are reported and efibootmgr always fails with an
input/output error.

The following simple patch makes read_vars() skip unreadable variables. It
allows efibootmgr to create boot entries on my system again.

--- efibootmgr-0.11.0.orig/src/efibootmgr/efibootmgr.c  2014-10-21 
22:17:27.0 +0200
+++ efibootmgr-0.11.0/src/efibootmgr/efibootmgr.c   2014-11-05 
00:34:15.883935672 +0100
@@ -110,8 +110,12 @@
rc = efi_get_variable(EFI_GLOBAL_GUID, namelist[i],
   &entry->data, &entry->data_size,
   &entry->attributes);
-   if (rc < 0)
-   goto err;
+   if (rc < 0) {
+   /* skip unreadable variable */
+   warn("reading variable %s", namelist[i]);
+   free(entry);
+   continue;
+   }
 
/* latest apple firmware sets high bit which appears
 * invalid to the linux kernel if we write it back so

However, I'm not sure if this is the right way to solve the problem. It
could be the firmware that needs a fix (there are newer versions available,
but I haven't tried them yet). It could be a bug in the kernel (maybe it
shouldn't fail with EIO). Anyway, an efibootmgr that is more fault tolerant
would be helpful.

PS: When testing the patch, I got a second unreadable boot entry that seems
to have been automatically created by the BIOS. The BIOS called it
"Generic-SD/MMC" which is one of the slots of a card reader. Together with
some other anomalies in the BIOS boot configuration, I'm now pretty sure
that at least one BIOS bug is involved. Nevertheless, I think an efibootmgr
that's not so easy to scare and creates boot entries even in face of such
adversities would be nice ...

Mainboard: Asus P9D

Processed: user debian...@lists.debian.org, found 750030 in 5.5.40-1, affects 773036, usertagging 769556 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> found 750030 5.5.40-1
Bug #750030 [mysql-server-5.5] mysql-server-5.5: unowned files after purge 
(policy 6.8, 10.8): /etc/apparmor.d/local/usr.sbin.mysqld
Marked as found in versions mysql-5.5/5.5.40-1.
> affects 773036 + libetpan-dev
Bug #773036 [libetpan-dbg] libetpan-dbg: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
Added indication that 773036 affects libetpan-dev
> usertags 769556 piuparts
Usertags were: instest-20141114 instest.
Usertags are now: instest-20141114 piuparts instest.
> tags 689773 - jessie sid
Bug #689773 [elib] elib: The package elib should be rebuilt with new debhelper 
to get trigger support
Removed tag(s) sid and jessie.
> notfound 689773 jessie/None
Bug #689773 [elib] elib: The package elib should be rebuilt with new debhelper 
to get trigger support
The source jessie and version None do not appear to match any binary packages
No longer marked as found in versions jessie/None.
> tags 635711 - unreproducible
Bug #635711 {Done: Daniel Kahn Gillmor } [monkeysphere] 
error on install
Removed tag(s) unreproducible.
> close 765726 340.65-1
Bug #765726 [nvidia-driver] nvidia-driver 340.46 has problems recognizing 
connected monitor(s)
Marked as fixed in versions nvidia-graphics-drivers/340.65-1.
Bug #765726 [nvidia-driver] nvidia-driver 340.46 has problems recognizing 
connected monitor(s)
Marked Bug as done
> tags 765726 - moreinfo
Bug #765726 {Done: Andreas Beckmann } [nvidia-driver] 
nvidia-driver 340.46 has problems recognizing connected monitor(s)
Removed tag(s) moreinfo.
> found 768896 343.36-1
Bug #768896 [nvidia-driver] nvidia-driver: resume from suspend breaks GNOME 
wallpaper
Marked as found in versions nvidia-graphics-drivers/343.36-1.
> merge 761360 768896
Bug #761360 [nvidia-driver] [nvidia-driver] Garbaged screen after suspend to RAM
Bug #768896 [nvidia-driver] nvidia-driver: resume from suspend breaks GNOME 
wallpaper
There is no source info for the package 'nvidia-driver' at version '340.58-0' 
with architecture ''
Unable to make a source version for version '340.58-0'
Marked as found in versions nvidia-graphics-drivers/340.32-1, 
nvidia-graphics-drivers/340.46-1, and nvidia-graphics-drivers/343.22-1.
Bug #761360 [nvidia-driver] [nvidia-driver] Garbaged screen after suspend to RAM
There is no source info for the package 'nvidia-driver' at version '340.58-0' 
with architecture ''
Unable to make a source version for version '340.58-0'
Marked as found in versions nvidia-graphics-drivers/343.36-1, 340.58-0, 
nvidia-graphics-drivers/340.46-4, and nvidia-graphics-drivers/340.46-3.
Merged 761360 768896
> retitle 768896 nvidia-driver: resume from suspend breaks GNOME wallpaper
Bug #768896 [nvidia-driver] nvidia-driver: resume from suspend breaks GNOME 
wallpaper
Bug #761360 [nvidia-driver] [nvidia-driver] Garbaged screen after suspend to RAM
Ignoring request to change the title of bug#768896 to the same title
Changed Bug title to 'nvidia-driver: resume from suspend breaks GNOME 
wallpaper' from '[nvidia-driver] Garbaged screen after suspend to RAM'
> tags 772740 + moreinfo
Bug #772740 [xserver-xorg-video-nvidia-legacy-304xx] 
xserver-xorg-video-nvidia-legacy-304xx: No glXSwapIntervalSGI despite reported 
GLX_SGI_swap_control in socket-based connections
Added tag(s) moreinfo.
> usertags 754122 piuparts
There were no usertags set.
Usertags are now: piuparts.
> tags 766676 + unreproducible moreinfo
Bug #766676 [src:fglrx-driver] /usr/bin/Xorg: symbol lookup error: 
/usr/lib/xorg/modules/linux/libglx.so: undefined symbol: LoadExtension
Added tag(s) unreproducible and moreinfo.
> found 768397 1:14.12-1
Bug #768397 [fglrx-modules-dkms] fglrx-modules-dkms 1:14.9+ga14.201-2 don't 
build against kernel 3.17.0
There is no source info for the package 'fglrx-modules-dkms' at version 
'1:14.12-1' with architecture ''
Unable to make a source version for version '1:14.12-1'
Marked as found in versions 1:14.12-1.
> found 745901 1:14.12-1
Bug #745901 [fglrx-driver] fglrx-driver: fglrx update crashes totem, gdm, 
gnome-session and anything that uses clutter
There is no source info for the package 'fglrx-driver' at version '1:14.12-1' 
with architecture ''
Unable to make a source version for version '1:14.12-1'
Marked as found in versions 1:14.12-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
635711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635711
689773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689773
745901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745901
750030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750030
754122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754122
761360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761360
765726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765726
766676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76

Bug#741464: grub-pc-bin: hangs after displaying boot menu

[Bernhard Übelacker]

Hello,
I tried if I could reproduce this issue.
(In my setup there is a tftp delivering grub installed by grub-mknetdir)

I could not get it to hang by "terminal_input at_keyboard".
But similar to what Jeroen Dekkers described I was not able anymore to
enter sane text with the keyboard. It feels like only every ~10th key
appears in grub.
(In virtualbox, qemu and on a real machine, with grub from testing
and/or a build from upstream git.)

I could track it down to calls into the PXE stack.
By avoiding these calls normal keyboard input is then still possible
when having at_keyboard loaded. (Unfortunately being then not able to
load anything via network).

By using a test function which does only the protected to real mode
switch and back without the actual PXE call, I assume the problem is
only with the mode switch itself - somehow resetting keyboard states.



Attached patch (against upstream) should help in debugging the problem:
- if environment no_nic_poll is set to 1, avoid the problematic PXE call
- if environment no_nic_poll is set to 1 make only the switch from
  protected mode to real and back (and avoids the problematic PXE call)

That way the keyboard input stays fluid when using this sequence:
  set no_nic_poll=1
  terminal_input at_keyboard

When you now unset the environment the keyboard reacts broken again:
  unset no_nic_poll

(Booting would still be possible if the environment is reset just before
downloading any files)



Unfortunately I was not able to reproduce it on a plain from harddisk
loaded grub.

That leaves a couple of questions open:
- have the submitter and commenter also a setup involving PXE?
- or do we have 2 or 3 different problems?

Kind regards,
Bernhard
From 39a1748cd3a4ec9e7f8e6449e3fd131143b77c05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= 
Date: Thu, 18 Dec 2014 01:26:01 +0100
Subject: Help debugging debian bug #741464

---
 grub-core/kern/i386/pc/startup.S| 102 +++-
 grub-core/net/drivers/i386/pc/pxe.c |   7 +++
 include/grub/i386/pc/pxe.h  |   1 +
 3 files changed, 75 insertions(+), 35 deletions(-)

diff --git a/grub-core/kern/i386/pc/startup.S b/grub-core/kern/i386/pc/startup.S
index 6bb36c6..1fc0011 100644
--- a/grub-core/kern/i386/pc/startup.S
+++ b/grub-core/kern/i386/pc/startup.S
@@ -159,42 +159,74 @@ FUNCTION(grub_exit)
  * int grub_pxe_call (int func, void* data, grub_uint32_t pxe_rm_entry);
  */
 FUNCTION(grub_pxe_call)
-	pushl	%ebp
-	movl	%esp, %ebp
-	pushl	%esi
-	pushl	%edi
-	pushl	%ebx
-
-	movl	%ecx, %ebx
-	movl	%eax, %ecx
-	movl	%edx, %eax
-	andl	$0xF, %eax
-	shrl	$4, %edx
-	shll	$16, %edx
-	addl	%eax, %edx
+pushl	%ebp
+movl	%esp, %ebp
+pushl	%esi
+pushl	%edi
+pushl	%ebx
+
+movl	%ecx, %ebx
+movl	%eax, %ecx
+movl	%edx, %eax
+andl	$0xF, %eax
+shrl	$4, %edx
+shll	$16, %edx
+addl	%eax, %edx
+
+PROT_TO_REAL
+.code16
+
+pushl	%ebx
+pushl	%edx
+pushw	%cx
+movw	%sp, %bx
+lcall	*%ss:6(%bx)
+cld
+addw	$10, %sp
+movw	%ax, %cx
+
+REAL_TO_PROT
+.code32
+
+movzwl	%cx, %eax
+
+popl	%ebx
+popl	%edi
+popl	%esi
+popl	%ebp
+ret
 
-	PROT_TO_REAL
-	.code16
-
-	pushl	%ebx
-	pushl	%edx
-	pushw	%cx
-	movw	%sp, %bx
-	lcall	*%ss:6(%bx)
-	cld
-	addw	$10, %sp
-	movw	%ax, %cx
-
-	REAL_TO_PROT
-	.code32
-
-	movzwl	%cx, %eax
-
-	popl	%ebx
-	popl	%edi
-	popl	%esi
-	popl	%ebp
-	ret
+/*
+ * int prot_to_real_to_prot (int func, void* data, grub_uint32_t pxe_rm_entry);
+ */
+FUNCTION(prot_to_real_to_prot)
+pushl	%ebp
+movl	%esp, %ebp
+pushl	%esi
+pushl	%edi
+pushl	%ebx
+
+movl	%ecx, %ebx
+movl	%eax, %ecx
+movl	%edx, %eax
+andl	$0xF, %eax
+shrl	$4, %edx
+shll	$16, %edx
+addl	%eax, %edx
+
+PROT_TO_REAL
+.code16
+
+REAL_TO_PROT
+.code32
+
+movzwl	%cx, %eax
+
+popl	%ebx
+popl	%edi
+popl	%esi
+popl	%ebp
+ret
 
 #include "../int.S"
 
diff --git a/grub-core/net/drivers/i386/pc/pxe.c b/grub-core/net/drivers/i386/pc/pxe.c
index e8c0b22..801a34c 100644
--- a/grub-core/net/drivers/i386/pc/pxe.c
+++ b/grub-core/net/drivers/i386/pc/pxe.c
@@ -180,6 +180,13 @@ grub_pxe_recv (struct grub_net_card *dev __attribute__ ((unused)))
 {
   grub_memset (isr, 0, sizeof (*isr));
   isr->func_flag = GRUB_PXE_ISR_IN_START;
+
+  const char *debug = grub_env_get ("no_nic_poll");
+  if (debug && debug[0] >= '2')
+  prot_to_real_to_prot (GRUB_PXENV_UNDI_ISR, isr, pxe_rm_entry);
+  if (debug && debug[0] >= '1')
+  return NULL;
+
   grub_pxe_call (GRUB_PXENV_UNDI_ISR, isr, pxe_rm_entry);
   /* Normally according to the specification we should also check
 	 that isr->func_flag != 

Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup

[Arnaud Installe]

On Thu, 27 Nov 2014 10:53:35 +
Simon McVittie  wrote:

> On Sat, 01 Nov 2014 at 11:50:40 +0100, Arnaud Installe wrote:
> > After successfully unlocking and mounting root and swap devices,
> > the system hangs a while, then drops to a rescue shell,
> > with /usr, /var and /home not unlocked by cryptsetup. After
> > manually running cryptsetup for the underlying devices, and exiting
> > the rescue shell, boot proceeds normally.
> 
> I think this may be the same thing as
> . Am I right in saying that your
> system looks like this?
> 
> /dev/sda (or whatever)
>   \- /dev/sda1 (or whatever): /boot
>   \- /dev/sda2 (or whatever): LVM PV for VG "boulez"
>  \- boulez/root LV: encrypted, boulez-_root__crypt
> \- / (rootfs)
>  \- boulez/swap LV: encrypted, boulez-_swap__crypt
> \- swap
>  \- boulez/home LV: encrypted, boulez-_home__crypt
> \- /home
>  \- boulez/usr LV: encrypted, boulez-_usr__crypt
> \- /usr
>  \- boulez/var LV: encrypted, boulez-_var__crypt
> \- /var

Yes, that's about it.

[...]

> It would be great if you could try rebuilding the initramfs after
> installing a version of cryptsetup with the patch from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767832#22
> applied. I believe that should fix your situation too, but
> so far I have only tested LUKS on partitions, not LUKS on LVM.

I'm sorry for the late reply. I wanted to try out your suggestion
today, only to find that a new version of cryptsetup including your
patch had made it to unstable.

I installed that, and my problem was solved. Thank you very much, and
again, sorry for the late reply!

Arnaud

-- 
Arnaud Installe   +32 477 304199
ESAT - STADIUS, KULeuven iMinds Medical Information Technologies


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

Bug#773354: please add breaks: live-tools (<< 4.0.1-1)

[Daniel Baumann]

On 12/17/14 23:50, Andreas Henriksson wrote:
> I'd guess (without having looked) because live-tools diverts
> update-initramfs?

no, it's about uptime.

-- 
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:  daniel.baum...@progress-technologies.net
Internet:   http://people.progress-technologies.net/~daniel.baumann/


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

Processed: Re: Bug#772609: uhexen2: use autotools-dev to update config.{sub, guess} and fix ppc64el FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity 772609 normal
Bug #772609 [uhexen2] uhexen2: use autotools-dev to update config.{sub, guess} 
and fix ppc64el FTBFS
Severity set to 'normal' from 'serious'

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


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

Bug#772609: uhexen2: use autotools-dev to update config.{sub, guess} and fix ppc64el FTBFS

[Simon McVittie]

Control: severity 772609 normal

On Tue, 09 Dec 2014 at 00:52:01 -0500, Logan Rosen wrote:
> Severity: serious
> ...
> Justification: fails to build from source

FTBFS is only considered release-critical if it's a regression, i.e. the
architecture in question has ever successfully built the package;
reducing the severity accordingly.

> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * Use autotools-dev to update config.{sub,guess} for new arches.

The patch looks reasonable. Does the resulting uhexen2 engine
actually work on ppc64el?

Regards,
S


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

Bug#773354: please add breaks: live-tools (<< 4.0.1-1)

[Andreas Henriksson]

Hi.

On Wed, Dec 17, 2014 at 09:35:01AM -0500, Phillip Susi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> I don't quite understand what's happening in this bug.  How do we get
> from calling update-initramfs to an error trying to execute
> update-initramfs.orig.initramfs-tools instead?

I'd guess (without having looked) because live-tools diverts
update-initramfs?

> 
> For that matter, instead of directly executing update-initramfs,
> shouldn't we be using a dpkg trigger?

As I see it, the discussed breaks is suggested to work around
a bug in live-tools. I'm not sure packages should be used
to carry workarounds for issues in other packages because the
list will become very long very soon. (eg. see also #772846
and grml-debootstrap << 0.68 which would be the next Breaks
candidate, and so on...)

A completely alternative suggestion would be to simply drop
the update-initramfs calls from util-linux (for jessie) as
it doesn't look like the initramfs-tools in unstable/sid
will make it into jessie (which was the reason it was added)
That would side-step the entire problem I guess.

Would be very welcome if someone wants to dig deeper into this
and investigate all options. I'm not very motivated to do it.

Regards,
Andreas Henriksson


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

Processed: closing 773303

[Debian Bug Tracking System]

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

> close 773303
Bug #773303 [libgl1-mesa-dev] libgl1-mesa-dev: Symlink error for libGL.so
Marked Bug as done
> thanks
Stopping processing here.

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


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

Bug#764005: targetcli: Upgrade issues from 2.1-1

[Chris Boot]

On 17 Dec 2014, at 21:11, Chris Boot  wrote:
> 
> On 17 Dec 2014, at 13:56, Ritesh Raj Sarraf  wrote:
>> 
>> On 10/07/2014 03:54 PM, Jerome Martin wrote:
>>> 
>>> 
>>> On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote: 
 On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote: 
> Okay!! Thanks to both of you. I will prepare something next week. My 
> only request is if (other) users can test it in time. 
 
 By the way, Jerome, do you still plan on a newer release  of the LIO 
 stack ? Or is this, the one I pushed to Debian, good from your point of 
 view ? 
>>> 
>>> Yes, an update is on its way. 
>>> This should not impact the iSCSI use-case too much, the aim will be updates 
>>> to the HW fabrics support mostly, along with a few minor bug-fixes here and 
>>> there. 
>> 
>> Jerome: Based on what we last talked, I went ahead and created tarballs 
>> accordingly. I now have a beter LIO stack with proper versioning. I have 
>> pushed it to experimental as Debian Jesssie is in freeze.
>> 
>> rrs@learner:/var/tmp/Debian-Build/Result$ sudo targetcli
>> [sudo] password for rrs: 
>> targetcli 3.0.pre4.1~ga55d018 (rtslib 3.0.pre4.1~g1b33ceb)
>> Copyright (c) 2011-2014 by Datera, Inc.
>> All rights reserved.
>> 
>> /> ls
>> o- / 
>> .
>>  [...]   
>>  o- backstores 
>> ..
>>  [...]   
>>  | o- fileio 
>> ...
>>  [0 Storage Object]  
>>  
>>  | o- iblock 
>> ...
>>  [0 Storage Object]  
>>  
>>  | o- pscsi 
>> 
>>  [0 Storage Object]  
>>  
>>  | o- rd_mcp 
>> ...
>>  [0 Storage Object]  
>>  
>>  o- ib_srpt 
>> ...
>>  [0 Targets]   
>>  o- iscsi 
>> .
>>  [0 Targets]   
>>  o- loopback 
>> ..
>>  [0 Targets]   
>>  o- qla2xxx 
>> ...
>>  [0 Targets]   
>>  o- tcm_fc 
>> 
>>  [0 Targets]   
>>  o- vhost 
>> .
>>  [0 Targets]   
>> /> exit  
>>   
>> Comparing startup and running configs... 
>>   
>> Startup config is up-to-date.
>>   
>> 19:23 ♒♒♒  ☺ 
>>  
>> rrs@learner:/var/tmp/Debian-Build/Result$
>> 
>> 
>> This looks much better. Chris: If you have some time, you may want to play 
>> with this version, from experimental ??
> 
> Hi Ritesh,
> 
> This version is much better, but still doesn’t work with my qla2xxx targets 
> unfortunately. When saving the configuration, I get:
> 
> ConfigError: Unknown value type 'qla2xxx_wwn' when validating 
> 21:02:00:e0:8b:d1:67:2c

Hi Ritesh, Jerome,

I wrote a patch that appears to fix this for me, through admittedly I haven’t 
tested it very extensively yet:

https://github.com/Datera/rtslib/pull/5
https://github.com/bootc/rtslib/commit/727c345bd18137c424e4fba62bfab7bcfabfc024

That allows the configuration to be saved, at

Bug#768127: marked as done (Fails to build the index when invalid UTF-8 is met)

[Debian Bug Tracking System]

Your message dated Wed, 17 Dec 2014 21:35:10 +
with message-id 
and subject line Bug#768127: fixed in dhelp 0.6.21+nmu6
has caused the Debian Bug report #768127,
regarding Fails to build the index when invalid UTF-8 is met
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.)


-- 
768127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dhelp
Version: 0.6.21+nmu5
Severity: grave
Justification: renders package unusable

$ dhelp
Starting browser (using local filesystem) ...
w3m: Can't load /usr/share/doc/HTML/index.html.
/usr/bin/sensible-browser: Failed to open /usr/share/doc/HTML/index.html: 
Отказано свързване
$ ls /usr/share/doc/HTML/
README

$ sudo dpkg-reconfigure dhelp
Building HTML tree...ArgumentError: invalid byte sequence in UTF-8 
(/usr/lib/ruby/vendor_ruby/debian.rb:914:in `block in initialize'
/usr/lib/ruby/vendor_ruby/debian.rb:727:in `block in parse'
/usr/lib/ruby/vendor_ruby/debian.rb:726:in `each'
/usr/lib/ruby/vendor_ruby/debian.rb:726:in `parse'
/usr/lib/ruby/vendor_ruby/debian.rb:720:in `parseArchiveFile'
/usr/lib/ruby/vendor_ruby/debian.rb:913:in `initialize'
/usr/lib/ruby/vendor_ruby/debian.rb:46:in `new'
/usr/lib/ruby/vendor_ruby/debian.rb:46:in `status'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/cgimap.rb:58:in `package_status'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/cgimap.rb:71:in `installed?'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/cgimap.rb:87:in `info2www_link'
(erb):30:in `make_page'
/usr/lib/ruby/2.1.0/erb.rb:850:in `eval'
/usr/lib/ruby/2.1.0/erb.rb:850:in `result'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/html.rb:45:in `make_page'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/html.rb:100:in `export_section_page'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/html.rb:64:in `block in export'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/html.rb:62:in `each_pair'
/usr/lib/ruby/vendor_ruby/dhelp/exporter/html.rb:62:in `export'
/usr/sbin/dhelp_parse:153:in `rebuild_html_index'
/usr/sbin/dhelp_parse:210:in `main'
/usr/sbin/dhelp_parse:216:in `')
 done.
Reindexing documentation in the background

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

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

Versions of packages dhelp depends on:
ii  doc-base0.10.6
ii  libdata-page-perl   2.02-1
ii  libhtml-parser-perl 3.71-1+b2
ii  liblocale-gettext-perl  1.05-8+b1
ii  libtemplate-perl2.24-1.2+b1
ii  liburi-perl 1.64-1
ii  perl-modules5.20.1-2
ii  poppler-utils   0.26.5-2
ii  pstotext1.9-6
ii  ruby1:2.1.0.4
ii  ruby-bdb0.6.6-1+b2
ii  ruby-debian 0.3.9
ii  ruby-gettext3.1.2-1
ii  ruby2.1 [ruby-interpreter]  2.1.4-1
ii  swish++ 6.1.5-2.2
ii  ucf 3.0030

Versions of packages dhelp recommends:
ii  links [www-browser] 2.8-2+b2
ii  lynx-cur [www-browser]  2.8.9dev1-2
ii  w3m [www-browser]   0.5.3-19

Versions of packages dhelp suggests:
pn  catdvi 
pn  httpd-cgi  
pn  info2www   
pn  man2html   

-- debconf information:
* dhelp/www-browser-console: w3m
* dhelp/www-browser-x: epiphany
--- End Message ---
--- Begin Message ---
Source: dhelp
Source-Version: 0.6.21+nmu6

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated dhelp 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, 12 Dec 2014 22:02:20 +0100
Source: dhelp
Binary: dhelp
Architecture: source all
Version: 0.6.21+nmu6
Distribution: unstable
Urgency: medium
Maintainer: Georgios M. Zarkadas 
Changed-By: gregor herrmann 
Description:
 dhelp  - online help system
Closes: 768127
Changes:
 dhe

Bug#764005: targetcli: Upgrade issues from 2.1-1

[Chris Boot]

On 17 Dec 2014, at 13:56, Ritesh Raj Sarraf  wrote:
> 
> On 10/07/2014 03:54 PM, Jerome Martin wrote:
>> 
>> 
>> On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote: 
>>> On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote: 
 Okay!! Thanks to both of you. I will prepare something next week. My 
 only request is if (other) users can test it in time. 
>>> 
>>> By the way, Jerome, do you still plan on a newer release  of the LIO 
>>> stack ? Or is this, the one I pushed to Debian, good from your point of 
>>> view ? 
>> 
>> Yes, an update is on its way. 
>> This should not impact the iSCSI use-case too much, the aim will be updates 
>> to the HW fabrics support mostly, along with a few minor bug-fixes here and 
>> there. 
> 
> Jerome: Based on what we last talked, I went ahead and created tarballs 
> accordingly. I now have a beter LIO stack with proper versioning. I have 
> pushed it to experimental as Debian Jesssie is in freeze.
> 
> rrs@learner:/var/tmp/Debian-Build/Result$ sudo targetcli
> [sudo] password for rrs: 
> targetcli 3.0.pre4.1~ga55d018 (rtslib 3.0.pre4.1~g1b33ceb)
> Copyright (c) 2011-2014 by Datera, Inc.
> All rights reserved.
> 
> /> ls
> o- / 
> .
>  [...]   
>   o- backstores 
> ..
>  [...]   
>   | o- fileio 
> ...
>  [0 Storage Object]   
>   | o- iblock 
> ...
>  [0 Storage Object]   
>   | o- pscsi 
> 
>  [0 Storage Object]   
>   | o- rd_mcp 
> ...
>  [0 Storage Object]   
>   o- ib_srpt 
> ...
>  [0 Targets]   
>   o- iscsi 
> .
>  [0 Targets]   
>   o- loopback 
> ..
>  [0 Targets]   
>   o- qla2xxx 
> ...
>  [0 Targets]   
>   o- tcm_fc 
> 
>  [0 Targets]   
>   o- vhost 
> .
>  [0 Targets]   
> /> exit   
>   
>
> Comparing startup and running configs...  
>   
>
> Startup config is up-to-date. 
>   
>
> 19:23 ♒♒♒  ☺  
>   
>
> rrs@learner:/var/tmp/Debian-Build/Result$
> 
> 
> This looks much better. Chris: If you have some time, you may want to play 
> with this version, from experimental ??

Hi Ritesh,

This version is much better, but still doesn’t work with my qla2xxx targets 
unfortunately. When saving the configuration, I get:

ConfigError: Unknown value type 'qla2xxx_wwn' when validating 
21:02:00:e0:8b:d1:67:2c

The full output from my session is below:

targetcli 3.0.pre4.1~ga55d018 (rtslib 3.0.pre4.1~g1b33ceb)
Copyright (c) 2011-2014 by Datera, Inc.

Bug#772898: win32-loader testing and newer fails with TRANSLATE error

[Didier 'OdyX' Raboud]

Hi Bernhard,

Le dimanche, 14 décembre 2014, 15.47:47 Bernhard Übelacker a écrit :
> So probably the solution could be only these 2 steps?
> 
> - to rebuild package nsis-common with the current g++-mingw-w64-i686
> package
> 
> - rebuild win32-loader with the newly built nsis-common package
> installed

I could assess post-upload on a Windows 7 VM that this was the correct 
strategy; thank you very much for this thorough analysis!

Cheers,
OdyX


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

Processed: tagging 773005, fixed 773005 in 0.0~git20140314.938cf1-3

[Debian Bug Tracking System]

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

> tags 773005 - jessie
Bug #773005 [src:yowsup] yowsup: unusable after new WhatsApp version
Removed tag(s) jessie.
> fixed 773005 0.0~git20140314.938cf1-3
Bug #773005 [src:yowsup] yowsup: unusable after new WhatsApp version
Marked as fixed in versions yowsup/0.0~git20140314.938cf1-3.
> thanks
Stopping processing here.

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


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

Bug#773303: libgl1-mesa-dev: Symlink error for libGL.so

[Shan Ting]

Yeah.. After some more check I'm now sure it's a bug in driver side. Sadly 
Parallels doesn't have open source drivers so I can't patch it's installing 
behavior... (Ugly non-free software!)
Sorry for the misplaced bug report.

> 在 2014年12月17日，下午4:34，Simon McVittie  写道：
> 
>> On Wed, 17 Dec 2014 at 14:52:33 +0800, Shan Ting wrote:
>> sudo stat /usr/lib/x86_64-linux-gnu/libGL.so
>>  File: ‘/usr/lib/x86_64-linux-gnu/libGL.so’ -> ‘libGL.so.1.2.0’
> 
> OK so far...
> 
>> sudo stat /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
>> stat: cannot stat ‘/usr/lib/x86_64-linux-gnu/libGL.so.1.2.0’: No such file 
>> or directory
> 
> ... but that seems wrong for the packages you have installed. You said
> you have:
> 
>> Package: libgl1-mesa-dev
>> Version: 10.3.2-1
>> ...
>> ii  libgl1-mesa-glx 10.3.2-1
> 
> but those same packages on the same (amd64) architecture do provide
> libGL.so.1.2.0:
> 
> % dpkg -s libgl1-mesa-dev
> ...
> Version: 10.3.2-1
> Depends: ..., libgl1-mesa-glx (= 10.3.2-1), ...
> ...
> % dpkg -L libgl1-mesa-glx:amd64
> ...
> /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
> /usr/lib/x86_64-linux-gnu/libGL.so.1
> 
>> I’m not using lx-alternative-fglrx, glx-alternative-nvidia or
>> glx-diversions. The libGL.so.10.1.1.28614 is come from my graphic card
>> driver(parallels).
> 
> Then I think this is a bug in your graphics card driver: it is overwriting
> and deleting files owned by the packaging system, but not finishing the job
> by taking responsibility for setting the target of the libGL.so symlink
> (and not participating in glx-alternatives like the non-free drivers
> packaged by Debian developers do, which would be the ideal thing).
> 
>> Is there some reasons to use libGL.so.1.2.0 directly rather than
>> libGL.so.1?
> 
> That's how libraries' development symlinks normally work. For instance,
> picking a random library for which I have development files
> installed (Gtk 2):
> 
> % ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so
> lrwxrwxrwx 1 root root 27 Oct 10 18:57 
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so -> libgtk-x11-2.0.so.0.2400.25
> default|archetype% ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> lrwxrwxrwx 1 root root 27 Oct 10 18:57 
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0.2400.25
> % ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.25
> -rw-r--r-- 1 root root 4501992 Oct 10 18:57 
> /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.25
> 
> The real file is the versioned one, and the development symlink and the
> SONAME (runtime) symlink both point to it.
> 
> Regards,
>S


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

Bug#773321: [pkg-otr-team] Bug#773321: Bug#773321: Bug#773321: irssi-plugin-otr segfaults unexpectedly

[Holger Levsen]

control: severity -1 important
control: retitle -1 must depend on the same irssi version it was built against

On Mittwoch, 17. Dezember 2014, intrigeri wrote:
> So, since apparently strong
> versioned deps are needed both ways, it seems that irssi-plugin-otr
> needs a versioned binary dep on the exact version of irssi it was
> built again. Wow.

agreed :-)




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

Bug#773321: [pkg-otr-team] Bug#773321: Bug#773321: Bug#773321: irssi-plugin-otr segfaults unexpectedly

[intrigeri]

Antoine Beaupré wrote (17 Dec 2014 15:03:08 GMT) :
> interesting. it seems that the problem is that i was using irssi from
> wheezy - maybe the dependencies for irssi-plugin-otr should be tighter,
> because it doesn't work *at all* with 0.8.15-5.

Indeed, that's exactly what was discovered and lead one of us (Holger,
I think) to ask for a binNMU of irssi-plugin-otr in Jessie, in the
opposite direction though (irssi-plugin-otr needed to be recompiled
because irssi had been upgraded). So, since apparently strong
versioned deps are needed both ways, it seems that irssi-plugin-otr
needs a versioned binary dep on the exact version of irssi it was
built again. Wow.


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

Processed: Re: Bug#773321: [pkg-otr-team] Bug#773321: Bug#773321: Bug#773321: irssi-plugin-otr segfaults unexpectedly

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #773321 [irssi-plugin-otr] irssi-plugin-otr segfaults unexpectedly
Severity set to 'important' from 'critical'
> retitle -1 must depend on the same irssi version it was built against
Bug #773321 [irssi-plugin-otr] irssi-plugin-otr segfaults unexpectedly
Changed Bug title to 'must depend on the same irssi version it was built 
against' from 'irssi-plugin-otr segfaults unexpectedly'

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


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

Processed: Adjust bug severity and merge

[Debian Bug Tracking System]

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

> retitle 660197 samhain: Cannot be installed within a chroot
Bug #660197 [samhain] samhain: Cannot be installed within a chroot
Ignoring request to change the title of bug#660197 to the same title
> severity 660197 normal
Bug #660197 [samhain] samhain: Cannot be installed within a chroot
Severity set to 'normal' from 'grave'
> forcemerge 739939 660197
Bug #739939 [samhain] doesn't install in a chroot
Bug #739939 [samhain] doesn't install in a chroot
Marked as found in versions samhain/2.6.2-1.
Added tag(s) unreproducible, squeeze, and moreinfo.
Bug #660197 [samhain] samhain: Cannot be installed within a chroot
Merged 660197 739939
> thanks
Stopping processing here.

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


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

Bug#764451: libpam-mount: Fails to run mount: invalid option -- '-p'

[Philipp Huebner]

Hi

On 16/12/14 22:30, Christian Kastner wrote:
>> I attached a debdiff for an NMU which drops the -p option. I'd
>> appreciate it an affected user could test this. For convenience, you can
>> find an amd64 version of the package here:
>>
>> http://www.kvr.at/debian/pool/main/libp/libpam-mount/libpam-mount_2.14-1.1_amd64.deb
> 
> did anyone manage to get this tested? It's working fine for me, but my
> pam_mount.conf is quite trivial.

I can confirm that this new version fixes the problem.

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



signature.asc
Description: OpenPGP digital signature

Bug#767832: marked as done (cryptsetup: does not decrypt a split /usr as required by initramfs-tools >= 0.118)

[Debian Bug Tracking System]

Your message dated Wed, 17 Dec 2014 15:19:21 +
with message-id 
and subject line Bug#767832: fixed in cryptsetup 2:1.6.6-4
has caused the Debian Bug report #767832,
regarding cryptsetup: does not decrypt a split /usr as required by 
initramfs-tools >= 0.118
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.)


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

Package: initramfs-tools
Version: 0.118_all
Severity: Critical

Hi,

I lastly did a clean install of debian amd64. I used for this a SID 
mini.iso from here 
http://ftp.nl.debian.org/debian/dists/sid/main/installer-amd64/current/images/netboot/


I chose during installation luks partitioning (not lvm), and separated 
/boot (on an usb pendrive) partition from /root partition (on another 
drive with the other one).
Then, at the end of the installation, I restarted my system and was 
unable to get it working. Indeed, debian was unable to find some partitions.


After a lot of time, I find out why things gone wrong. There where 
mismatch between /etc/fstab and /etc/crypttab. UUID and devices 
combination in crypttab file were different from /etc/fstab.
For exemple, it was written an UUID for a particular /dev on crypttab 
that was different from /etc/fstab (like /dev/mapper/sda6_crypt for /usr 
in crypttab, but listed as sda7_crypt in fstab, the /var partition)


So, from initramfs, I manually mounted all drives, and then did "CTRL + 
D". The system finally boot completely. I corrected the crypttab and the 
fstab files, and chose the «file option» for unlocking each partition 
(/usr; /var; swap; /tmp; /home

But I still get some problems.


My system does not start automatically after I enter the password for 
unlocking the root partition. I have to unlock manually /usr (from 
initramfs ), and then do "CTRL + D".


Finally, I discovered that initramfs-tools_0.118_all.deb is buggy. 
Indeed, when I replaced it for initramfs-tools_0.116_all.deb, my system 
boot perfectly.


Here what I get before booting manually :
/
//
/ /Decompressiong Linux… Parsing ELF… done.//
//Booting the kernel.//
//Loading, please wait...//
//Please unlock disk sda1_crypt://
//cryptsetup: sda1_crypt set up successfully//
//fsck from util-linux 2.25.2//
///dev/mapper/sda1_crypt: clean, 7869/170688 files, 89041/682752 blocks//
//Gave up waiting for /usr device.  Common problems://
// - Boot args (cat /proc/cmdline)//
//   - Check rootdelay= (did the system wait long enough?)//
// - Missing modules (cat /proc/modules; ls /dev)//
//ALERT!  /dev/mapper/sda5_crypt does not exist.  Dropping to a shell!//
//modprobe: module ehci-orion not found in modules.dep//
//
//
//BusyBox v1.22.1 (Debian 1:1.22.0-9) built-in shell (ash)//
//Enter 'help' for a list of built-in commands./
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.6.6-4

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

Debian distribution maintenance software
pp.
Jonas Meurer  (supplier of updated cryptsetup 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: SHA1

Format: 1.8
Date: Wed, 17 Dec 2014 14:24:41 +0100
Source: cryptsetup
Binary: cryptsetup cryptsetup-bin libcryptsetup4 libcryptsetup-dev 
cryptsetup-udeb libcryptsetup4-udeb
Architecture: source amd64
Version: 2:1.6.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Cryptsetup Team 

Changed-By: Jonas Meurer 
Description:
 cryptsetup - disk encryption support - startup scripts
 cryptsetup-bin - disk encryption support - command line tools
 cryptsetup-udeb - disk encryption support - commandline tools (udeb) (udeb)
 libcryptsetup-dev - disk encryption support - development files
 libcryptsetup4 - disk encryption support - shared library
 libcryptsetup4-udeb - disk encryption support - shared library (udeb) (udeb)
Closes: 764564 767832 768407
Changes:
 cryptsetup (2:1.6.6-4) unstable; urgency=medium
 .
   [ Simon McVittie ]
   * debian/initramfs/cryptroot-script: decrypt /usr as well as / so that

Bug#773321: [pkg-otr-team] Bug#773321: Bug#773321: irssi-plugin-otr segfaults unexpectedly

[Antoine Beaupré]

On 2014-12-16 18:53:54, Holger Levsen wrote:
> On Mittwoch, 17. Dezember 2014, Antoine Beaupré wrote:
>> i can reproduce this without the xmpp warning. which versions of irssi
>> and irssi-plugin-otr do you use?
>
> ii  irssi 0.8.17-1~bpo70+1
>amd64terminal based IRC client
> ii  irssi-dev 0.8.17-1~bpo70+1
>amd64terminal based IRC client - development files
> ii  irssi-plugin-otr  1.0.0-1~bpo70+2 
>amd64Off-the-Record Messaging Plugin for Irssi
> ii  irssi-scripts 20120326
>all  collection of scripts for irssi

interesting. it seems that the problem is that i was using irssi from
wheezy - maybe the dependencies for irssi-plugin-otr should be tighter,
because it doesn't work *at all* with 0.8.15-5.

a.

-- 
À mesure que l'opression s'étend à tous les secteurs de la vie,
la révolte prend l'allure d'une guerre sociale. 
Les émeutes renaissent et annoncent la révolution à venir.
- Jean-François Brient, de la servitude moderne


signature.asc
Description: PGP signature

Bug#773354: please add breaks: live-tools (<< 4.0.1-1)

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I don't quite understand what's happening in this bug.  How do we get
from calling update-initramfs to an error trying to execute
update-initramfs.orig.initramfs-tools instead?

For that matter, instead of directly executing update-initramfs,
shouldn't we be using a dpkg trigger?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (MingW32)

iQEcBAEBAgAGBQJUkZSVAAoJENRVrw2cjl5RojMH/1lGFkCM+FdvBL+9Y77V9O+T
o+RVZitkYpBWpPGoQ4RjjY8B6YoaOl4QppvMN+1jpfV2+u3cA7Rq6+INB+RGvtD2
UN6ZmHAdpuPyTAiXERkHqfMJ0+FNHmE0RJGGkcMpuhQ4emFWfe97KNApe3MzJ+XN
evIkPi5rlM5P7fxSZunR7F9bOnZD09g34FW9Kwdhud/aIA8qdcyComW8qtGJZlse
NzO6jlH11aLcFv5d2JGJShrBKePilngeXe8RcCptueAf6ny7t0bvroLreLKPe37g
rtgF+1nyGKG3pYHwLV9dyKXp8I26iUJ1gwGQ5Qo4upBGv4+hLeg+SK9dv8IBte4=
=BMUY
-END PGP SIGNATURE-


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

Bug#764005: targetcli: Upgrade issues from 2.1-1

[Ritesh Raj Sarraf]

On 10/07/2014 03:54 PM, Jerome Martin wrote:
>
>
> On 10/07/2014 12:21 PM, Ritesh Raj Sarraf wrote:
>> On Tuesday 07 October 2014 03:49 PM, Ritesh Raj Sarraf wrote:
>>> Okay!! Thanks to both of you. I will prepare something next week. My
>>> only request is if (other) users can test it in time.
>>
>> By the way, Jerome, do you still plan on a newer release  of the LIO
>> stack ? Or is this, the one I pushed to Debian, good from your point of
>> view ?
>
> Yes, an update is on its way.
> This should not impact the iSCSI use-case too much, the aim will be
> updates to the HW fabrics support mostly, along with a few minor
> bug-fixes here and there.

Jerome: Based on what we last talked, I went ahead and created tarballs
accordingly. I now have a beter LIO stack with proper versioning. I have
pushed it to experimental as Debian Jesssie is in freeze.

rrs@learner:/var/tmp/Debian-Build/Result$ sudo targetcli
[sudo] password for rrs:
targetcli 3.0.pre4.1~ga55d018 (rtslib 3.0.pre4.1~g1b33ceb)
Copyright (c) 2011-2014 by Datera, Inc.
All rights reserved.

/> ls
o- /

.
[...]  
  o- backstores

..
[...]  
  | o- fileio

...
[0 Storage
Object]  
  | o- iblock

...
[0 Storage
Object]  
  | o- pscsi


[0 Storage
Object]  
  | o- rd_mcp

...
[0 Storage
Object]  
  o- ib_srpt

...
[0 Targets]  
  o- iscsi

.
[0 Targets]  
  o- loopback

..
[0 Targets]  
  o- qla2xxx

...
[0 Targets]  
  o- tcm_fc


[0 Targets]  
  o- vhost

.
[0 Targets]  
/>
exit

   

Comparing startup and running
configs...  



Startup config is
up-to-date. 



19:23 ♒♒♒ 
☺   

   

rrs@learner:/var/tmp/Debian-Build/Result$   




This looks much better. Chris: If you have some time, you may want to
play with this version, from experimental ??

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



signature.asc
Description: OpenPGP digital signature

Bug#773359: package tbb_4.2~20140122-4 FTBFS on mips and mipsel

[Jurica Stanojkovic]

Package: tbb
Version: 4.2~20140122-4
Severity: serious
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch

Hello,
Package tbb_4.2~20140122-4 FTBFS on mips and mipsel.

Mips platform does not have 64-bit __sync_* operations.
To resolve this issue it is needed to use corresponding
__atomic_* from libatomic library. 

https://buildd.debian.org/status/package.php?p=tbb&suite=sid

build logs:
https://buildd.debian.org/status/fetch.php?pkg=tbb&arch=mips&ver=4.2~20140122-4&stamp=1415055684
https://buildd.debian.org/status/fetch.php?pkg=tbb&arch=mipsel&ver=4.2~20140122-4&stamp=1415054347

I have attached a patch resolving this issue.

Thank you!

Regards,
Jurica--- tbb-4.2~20140122.orig/build/linux.gcc.inc
+++ tbb-4.2~20140122/build/linux.gcc.inc
@@ -80,6 +80,14 @@ endif
 TBB_ASM.OBJ=
 MALLOC_ASM.OBJ=
 
+ifeq (mips,$(arch))
+LINK_FLAGS += -latomic
+endif
+
+ifeq (mipsel,$(arch))
+LINK_FLAGS += -latomic
+endif
+
 ifeq (ia64,$(arch))
 # Position-independent code (PIC) is a must on IA-64 architecture, even for regular (not shared) executables
 CPLUS_FLAGS += $(PIC_KEY)
--- tbb-4.2~20140122.orig/build/linux.inc
+++ tbb-4.2~20140122/build/linux.inc
@@ -76,6 +76,12 @@ ifndef arch
 ifeq ($(deb_host_arch),i386)
 export arch:=ia32
 endif
+	ifeq ($(deb_host_arch),mips)
+export arch:=mips
+endif
+ifeq ($(deb_host_arch),mipsel)
+export arch:=mipsel
+endif
 ifndef arch
 export arch:=$(uname_m)
 $(warning "Unknown arch: " $(arch))
--- tbb-4.2~20140122.orig/include/tbb/machine/gcc_generic.h
+++ tbb-4.2~20140122/include/tbb/machine/gcc_generic.h
@@ -68,14 +68,27 @@
 #define __TBB_full_memory_fence()   __sync_synchronize()
 #define __TBB_control_consistency_helper()  __sync_synchronize()
 
-#define __TBB_MACHINE_DEFINE_ATOMICS(S,T) \
-inline T __TBB_machine_cmpswp##S( volatile void *ptr, T value, T comparand ) {\
-return __sync_val_compare_and_swap(reinterpret_cast(ptr),comparand,value);  \
-} \
-  \
-inline T __TBB_machine_fetchadd##S( volatile void *ptr, T value ) {   \
-return __sync_fetch_and_add(reinterpret_cast(ptr),value);   \
-} \
+#if defined (__mips) && !defined (__mips64)
+#define __TBB_MACHINE_DEFINE_ATOMICS(S,T) \
+inline T __TBB_machine_cmpswp##S( volatile void *ptr, T value, T comparand ) {\
+__atomic_compare_exchange(reinterpret_cast(ptr),&comparand,&value,  \
+false,__ATOMIC_SEQ_CST,__ATOMIC_SEQ_CST); \
+return comparand; \
+} \
+  \
+inline T __TBB_machine_fetchadd##S( volatile void *ptr, T value ) {   \
+return __atomic_fetch_add(reinterpret_cast(ptr),value,__ATOMIC_SEQ_CST);\
+}
+#else
+	#define __TBB_MACHINE_DEFINE_ATOMICS(S,T) \
+	inline T __TBB_machine_cmpswp##S( volatile void *ptr, T value, T comparand ) {\
+	return __sync_val_compare_and_swap(reinterpret_cast(ptr),comparand,value);  \
+	} \
+	  \
+	inline T __TBB_machine_fetchadd##S( volatile void *ptr, T value ) {   \
+	return __sync_fetch_and_add(reinterpret_cast(ptr),value);   \
+	} 
+#endif
 
 __TBB_MACHINE_DEFINE_ATOMICS(1,int8_t)
 __TBB_MACHINE_DEFINE_ATOMICS(2,int16_t)

Bug#729220: marked as done (pdl: problems upgrading from wheezy due to triggers)

[Debian Bug Tracking System]

Your message dated Wed, 17 Dec 2014 13:04:05 +
with message-id 
and subject line Bug#729220: fixed in pdl 1:2.007-4
has caused the Debian Bug report #729220,
regarding pdl: problems upgrading from wheezy due to triggers
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.)


-- 
729220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pdl
Version: 1:2.007-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libpdl-io-hdf5-perl

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'sid' fails.

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

  Preparing to replace perl 5.14.2-21+deb7u1 (using 
.../perl_5.18.1-4_amd64.deb) ...
  Unpacking replacement perl ...
  Preparing to replace libtext-charwidth-perl 0.04-7+b1 (using 
.../libtext-charwidth-perl_0.04-7+b2_amd64.deb) ...
  Unpacking replacement libtext-charwidth-perl ...
  Preparing to replace libpdl-io-hdf5-perl 0.63-3 (using 
.../libpdl-io-hdf5-perl_0.63-3+b1_amd64.deb) ...
  Unpacking replacement libpdl-io-hdf5-perl ...
  Preparing to replace perl-base 5.14.2-21+deb7u1 (using 
.../perl-base_5.18.1-4_amd64.deb) ...
  Unpacking replacement perl-base ...
  Processing triggers for pdl ...
  dpkg: error processing pdl (--unpack):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   pdl

At this point the old pdl (built against perl 5.14) is still installed,
but is no longer runnable, so the trigger fails.

This could be a known dpkg problem (running a trigger for a package that is
not properly configured), but this needs to be worked around as the dpkg
in wheezy is not going to be fixed.

Maybe adding libpdl-io-hdf5-perl: Breaks: pdl (<< 1:2.007) helps
(as long as this version does not go into backports at some point)

cheers,

Andreas


libpdl-io-hdf5-perl_0.63-3+b1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: pdl
Source-Version: 1:2.007-4

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

Debian distribution maintenance software
pp.
Henning Glawe  (supplier of updated pdl 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: SHA1

Format: 1.8
Date: Wed, 17 Dec 2014 10:29:01 +0100
Source: pdl
Binary: pdl
Architecture: source amd64
Version: 1:2.007-4
Distribution: unstable
Urgency: high
Maintainer: Henning Glawe 
Changed-By: Henning Glawe 
Description:
 pdl- perl data language: Perl extensions for numerics
Closes: 729220
Changes:
 pdl (1:2.007-4) unstable; urgency=high
 .
   * Fix "problems upgrading from wheezy due to triggers"; print warning
 to STDERR if doc index could not be updated instead of causing
 postinst failure. (Closes: #729220)
 This will apply only in subsequent releases, as the upgrade problem
 is caused by the pdl package in wheezy.
 Cloned bug to perl (#773323), in order to have a 'Breaks: pdl (<<1:2.007)'
 for smooth wheezy->jessie updates.
 Changes to pdl.postinst have been tested by backporting to wheezy's pdl
 version, which solved the wheezy->jessie upgrade issues.
Checksums-Sha1:
 5d73568e234ea70330c35d20ccc022752107b560 1429 pdl_2.007-4.dsc
 557c4f59da687e28253cb7c307fe9d2752bf6ecc 27116 pdl_2.007-4.debian.tar.xz
 63367d684f338f4b2d2227a421cd4715e1b336c8 3940924 pdl_2.007-4_amd64.deb
Checksums-Sha256:
 fa76c48279dfe4cb1bea8564ef79644567757f1cd315c345a1259baa9ec342ef 1429 
pdl_2.007-4.dsc
 ce411009d5091f2d78bbf4e1488c8fa301d2cd6b194f3813f3fed891f0347446 27116 
pdl_2.007-4.debian.tar.xz
 17a11c280e147291d5573730e099a0b2051e895508d2bfa9b13d26d0beaab119 3940924 
pdl_2.007-4_amd64.deb
Files:
 41b9f5e39b34787cf5a694f0d4eade4f 1429 math optional pdl_2.007-4.dsc
 fbe2070a5a6386fb9f68ef1839f4639e 27116 math optional pdl_2.007-4.debian.tar.xz
 15081ff1f90afedbe42897de8ade9270 3940924 math optional pdl_2.007-4_amd64.deb

-BEGIN PGP SI

Bug#769765: marked as done (designate-common: fails to upgrade from 'sid': Could not load 'migrate': Invalid target type: None)

[Debian Bug Tracking System]

Your message dated Wed, 17 Dec 2014 20:54:28 +0800
with message-id <54917d04.1090...@debian.org>
and subject line This bug has been fixed
has caused the Debian Bug report #769765,
regarding designate-common: fails to upgrade from 'sid': Could not load 
'migrate': Invalid target type: None
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.)


-- 
769765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: designate-common
Version: 2014.2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid'.
It installed fine in 'sid', then the upgrade to 'experimental' fails.

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

  Setting up designate-common (2014.2-2) ...
  Installing new version of config file /etc/designate/api-paste.ini ...
  Installing new version of config file /etc/designate/policy.json ...
  Installing new version of config file /etc/logrotate.d/designate-common ...
  PKG-Openstack now calling: dbc_go designate-common configure 2014.1-14
  dbconfig-common: writing config to /etc/dbconfig-common/designate-common.conf
  Now doing 'designate-manage database sync': this may take a while...
  2014-11-14 10:02:45.928 1171 ERROR stevedore.extension [designate-manage - - 
- - -] Could not load 'migrate': Invalid target type: None
  2014-11-14 10:02:45.929 1171 ERROR stevedore.extension [designate-manage - - 
- - -] Invalid target type: None
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension Traceback (most recent 
call last):
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 162, in 
_load_plugins
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension 
verify_requirements,
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/stevedore/enabled.py", line 66, in 
_load_one_plugin
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension 
verify_requirements,
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 179, in 
_load_one_plugin
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension obj = 
plugin(*invoke_args, **invoke_kwds)
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/migration_cli/ext_migrate.py",
 line 38, in __init__
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension self.engine = 
db_session.create_engine(self.db_url)
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/session.py", line 388, in 
create_engine
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension 
pool_timeout=pool_timeout
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/utils.py", line 890, in 
__call__
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension 
self._url_from_target(target), target, arg, kw)
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension   File 
"/usr/lib/python2.7/dist-packages/oslo/db/sqlalchemy/utils.py", line 904, in 
_url_from_target
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension raise 
ValueError("Invalid target type: %r" % target)
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension ValueError: Invalid 
target type: None
  2014-11-14 10:02:45.929 1171 TRACE stevedore.extension 
  2014-11-14 10:02:46.104 1171 CRITICAL designate [designate-manage - - - - -] 
ValueError: There must be at least one plugin active.
  2014-11-14 10:02:46.104 1171 TRACE designate Traceback (most recent call 
last):
  2014-11-14 10:02:46.104 1171 TRACE designate   File 
"/usr/bin/designate-manage", line 10, in 
  2014-11-14 10:02:46.104 1171 TRACE designate sys.exit(main())
  2014-11-14 10:02:46.104 1171 TRACE designate   File 
"/usr/lib/python2.7/dist-packages/designate/cmd/manage.py", line 125, in main
  2014-11-14 10:02:46.104 1171 TRACE designate fn(*fn_args)
  2014-11-14 10:02:46.104 1171 TRACE designate   File 
"/usr/lib/python2.7/dist-packages/designate/manage/database.py", line 50, in 
sync
  2014-11-14 10:02:46.104 1171 TRACE designate get_manager().upgrade(None)
  2014-11-14 10:02:46.104 1171 TRACE designate   File 
"/usr/lib/python2.7/dist-packages/designate/manage/database.py", line 40, in 
get_manager
  2014-11-14 10:02:46.104 1171 TRACE designate REPOSITORY, 
CONF[

Processed: Re: [Pkg-openssl-devel] Bug#768681: Bug#768681: nodejs: FTBFS in jessie: tests failures

[Debian Bug Tracking System]

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

> reopen 768681
Bug #768681 {Done: Kurt Roeckx } [openssl] nodejs: FTBFS in 
jessie: tests failures
Bug reopened
Ignoring request to alter fixed versions of bug #768681 to the same values 
previously set
> severity 768681 important
Bug #768681 [openssl] nodejs: FTBFS in jessie: tests failures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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


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

Bug#768681: [Pkg-openssl-devel] Bug#768681: Bug#768681: nodejs: FTBFS in jessie: tests failures

[Kurt Roeckx]

reopen 768681
severity 768681 important
thanks

On Wed, Dec 17, 2014 at 08:02:30AM +0100, Paul Gevers wrote:
> On 16-12-14 22:53, Kurt Roeckx wrote:
> > Which upstream?
> 
> I meant openssl, as I thought William was referring to that.
> 
> > Upsteam openssl is saying that this is intentional behaviour, and
> > as such I won't be fixing this.
> 
> Ok. So I suggest to tag this bug as wontfix, and depending on how you as
> a team handle wontfixes, also close the bug.

So it seems that they just decided to revert that change since
more people run into it.

But I still suggest nodejs gets fixed.


Kurt


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

Processed: Re: live-tools: causes util-linux to fail to upgrade from 'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found

[Debian Bug Tracking System]

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

> clone 767939 -1
Bug #767939 [live-tools] live-tools: causes util-linux to fail to upgrade from 
'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Bug 767939 cloned as bug 773354
> reassign -1 util-linux
Bug #773354 [live-tools] live-tools: causes util-linux to fail to upgrade from 
'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Bug reassigned from package 'live-tools' to 'util-linux'.
No longer marked as found in versions live-tools/3.0.20-1, live-tools/4.0.2-1, 
and live-tools/4.0.1-1.
Ignoring request to alter fixed versions of bug #773354 to the same values 
previously set
> retitle -1 please add breaks: live-tools (<< 4.0.1-1)
Bug #773354 [util-linux] live-tools: causes util-linux to fail to upgrade from 
'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Changed Bug title to 'please add breaks: live-tools (<< 4.0.1-1)' from 
'live-tools: causes util-linux to fail to upgrade from 'wheezy': 
/usr/sbin/update-initramfs.orig.initramfs-tools - command not found'
> close 767939 4.0.2-1
Bug #767939 [live-tools] live-tools: causes util-linux to fail to upgrade from 
'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Marked as fixed in versions live-tools/4.0.2-1.
Bug #767939 [live-tools] live-tools: causes util-linux to fail to upgrade from 
'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Marked Bug as done
> thanks
Stopping processing here.

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


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

Bug#773351: silly: Broken /usr/lib/pkgconfig/SILLY.pc makes other package FTBFS

[Roland Stigge]

Source: silly
Version: 0.1.0-3.1
Severity: serious

Hi,

looks like SILLY.pc in libsilly-dev is broken:


$ cat /usr/lib/pkgconfig/SILLY.pc
prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib
includedir=/usr/include
plugindir=/usr/lib/SILLY 0.1.0

Name: SILLY
Description: Simple Image Loading LibrarY for games and multi-media development.
Version: 0.1.0
Libs: -L${libdir} -lSILLY 
Cflags: -DUSE_SILLYOPTIONS_H -I${includedir}/SILLY 0.1.0


The latter "0.1.0" makes cegui-mk2 FTBFS like this:


libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crti.o 
/usr/lib/gcc/x86_64-linux-gnu/4.9/crtbeginS.o  
.libs/libCEGUIFreeImageImageCodec_la-CEGUIFreeImageImageCodec.o 
.libs/libCEGUIFreeImageImageCodec_la-CEGUIFreeImageImageCodecModule.o   
-Wl,-rpath -Wl,/tmp/buildd/cegui-mk2-0.7.6/cegui/src/.libs -llua5.1 -lfreeimage 
../../../../cegui/src/.libs/libCEGUIBase.so -lpthread -ldl 
-L/usr/lib/gcc/x86_64-linux-gnu/4.9 
-L/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu 
-L/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../../lib -L/lib/x86_64-linux-gnu 
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/x86_64-linux-gnu/4.9/../../.. -lstdc++ -lm -lc -lgcc_s 
/usr/lib/gcc/x86_64-linux-gnu/4.9/crtendS.o 
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crtn.o  -O2   
-Wl,-soname -Wl,libCEGUIFreeImageImageCodec-0.7.6.so -o 
.libs/libCEGUIFreeImageImageCodec-0.7.6.so
libtool: link: (cd ".libs" && rm -f "libCEGUIFreeImageImageCodec.so" && ln -s 
"libCEGUIFreeImageImageCodec-0.7.6.so" "libCEGUIFreeImageImageCodec.so")
libtool: link: ( cd ".libs" && rm -f "libCEGUIFreeImageImageCodec.la" && ln -s 
"../libCEGUIFreeImageImageCodec.la" "libCEGUIFreeImageImageCodec.la" )
make[5]: Leaving directory 
'/tmp/buildd/cegui-mk2-0.7.6/cegui/src/ImageCodecModules/FreeImageImageCodec'
Making all in SILLYImageCodec
make[5]: Entering directory 
'/tmp/buildd/cegui-mk2-0.7.6/cegui/src/ImageCodecModules/SILLYImageCodec'
/bin/bash ../../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
-I. -I../../../../cegui/include -I../../../../cegui/include 
-I../../../../cegui/include/ImageCodecModules/SILLYImageCodec 
-DUSE_SILLY_LIBRARY -DUSE_SILLYOPTIONS_H 0.1.0 -I/usr/include/SILLY   
-D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c -o 
libCEGUISILLYImageCodec_la-CEGUISILLYImageCodec.lo `test -f 
'CEGUISILLYImageCodec.cpp' || echo './'`CEGUISILLYImageCodec.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../../cegui/include 
-I../../../../cegui/include 
-I../../../../cegui/include/ImageCodecModules/SILLYImageCodec 
-DUSE_SILLY_LIBRARY -DUSE_SILLYOPTIONS_H 0.1.0 -I/usr/include/SILLY 
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c CEGUISILLYImageCodec.cpp  -fPIC -DPIC -o 
.libs/libCEGUISILLYImageCodec_la-CEGUISILLYImageCodec.o
g++: error: 0.1.0: No such file or directory
Makefile:407: recipe for target 
'libCEGUISILLYImageCodec_la-CEGUISILLYImageCodec.lo' failed
make[5]: *** [libCEGUISILLYImageCodec_la-CEGUISILLYImageCodec.lo] Error 1
make[5]: Leaving directory 
'/tmp/buildd/cegui-mk2-0.7.6/cegui/src/ImageCodecModules/SILLYImageCodec'
Makefile:336: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1


Tested on amd64 and powerpcspe.

Roland


-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)

Kernel: Linux 3.9.0-dirty (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#773348: use QUrl::toPercentEncoding for sending password to X2Go Session Broker

[Mike Gabriel]

Package: x2goclient
Version: 4.0.3.1-1
Severity: grave
Tag: upstream patch

X2Go Client fails to send passwords containing the "&" character to an  
X2Go Session Broker.


This has been reported upstream as bug #705 [1] and is fixed in  
upstream Git, as well [2].


Mike

[1] http://bugs.x2go.org/705
[2]  
http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=db7c2f3009d9f39cdf8a85327c632dcb643f631c


--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgp7xw84bWgwN.pgp
Description: Digitale PGP-Signatur

Bug#768620: [avahi-daemon] Install fails

[Trent Lloyd]

That “something” is system itself, activation via dbus as something is trying 
to use Avahi via d-bus.

See here:
Dec 16 14:27:50 Zia dbus[1350]: [system] Activating via systemd: service 
name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'

I suggest you try “disable” instead of “stop” the service to prevent it being 
re-activated.

> On 17 Dec 2014, at 3:30 am, Anthony DeRobertis  wrote:
> 
> Package: avahi-daemon
> Version: 0.6.31-4+b1
> Followup-For: Bug #768620
> 
> On my system, something is immediately restarting avahi the second it
> stops. Here is what journalctl -f shows:
> 
> Dec 16 14:27:50 Zia systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
> Dec 16 14:27:50 Zia avahi-daemon[11795]: Got SIGTERM, quitting.
> Dec 16 14:27:50 Zia avahi-daemon[11795]: Leaving mDNS multicast group on 
> interface br0.IPv4 with address 172.16.1.244.
> Dec 16 14:27:50 Zia dbus[1350]: [system] Activating via systemd: service 
> name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
> Dec 16 14:27:50 Zia systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
> Dec 16 14:27:51 Zia avahi-daemon[11795]: avahi-daemon 0.6.31 exiting.
> Dec 16 14:27:51 Zia systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
> Dec 16 14:27:51 Zia avahi-daemon[12429]: Process 11795 died: No such process; 
> trying to remove PID file. (/var/run/avahi-daemon//pid)
> Dec 16 14:27:51 Zia avahi-daemon[12429]: Found user 'avahi' (UID 109) and 
> group 'avahi' (GID 115).
> Dec 16 14:27:51 Zia avahi-daemon[12429]: Successfully dropped root privileges.
> Dec 16 14:27:51 Zia avahi-daemon[12429]: avahi-daemon 0.6.31 starting up.
> Dec 16 14:27:51 Zia dbus[1350]: [system] Successfully activated service 
> 'org.freedesktop.Avahi'
> ...
> 
> So it looks like it gets reactivated before it even fully shuts down.
> 
> -- System Information:
> Debian Release: 8.0
>  APT prefers testing
>  APT policy: (500, 'testing'), (200, 'unstable'), (150, 'stable'), (100, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.17.0-p+ (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 avahi-daemon depends on:
> ii  adduser  3.113+nmu3
> ii  bind9-host [host]1:9.9.5.dfsg-6
> ii  dbus 1.8.12-1
> ii  init-system-helpers  1.22
> ii  libavahi-common3 0.6.31-4+b2
> ii  libavahi-core7   0.6.31-4+b2
> ii  libc62.19-13
> ii  libcap2  1:2.24-6
> ii  libdaemon0   0.14-6
> ii  libdbus-1-3  1.8.12-1
> ii  libexpat12.1.0-6+b3
> ii  lsb-base 4.1+Debian13+nmu1
> 
> Versions of packages avahi-daemon recommends:
> ii  libnss-mdns  0.10-6
> 
> Versions of packages avahi-daemon suggests:
> pn  avahi-autoipd  
> 
> -- Configuration Files:
> /etc/avahi/avahi-daemon.conf changed [not included]
> 
> -- no debconf information
> 


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

Bug#773345: pdns-backend-mysql: fails to upgrade from 'wheezy': Can't DROP 'domainmetaidindex'; check that column/key exists

[Andreas Beckmann]

Package: pdns-backend-mysql
Version: 3.4.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.

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

  Setting up pdns-backend-mysql (3.4.1-3) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/pdns-backend-mysql.conf
  creating database backup in 
/var/cache/dbconfig-common/backups/pdns-backend-mysql_3.1-4.1.mysql.
  applying upgrade sql for 3.1-4.1 -> 3.3.1-4.
  applying upgrade sql for 3.1-4.1 -> 3.4.0.
  error encountered processing 
/usr/share/dbconfig-common/data/pdns-backend-mysql/upgrade/mysql/3.4.0:
  mysql said: ERROR 1091 (42000) at line 16: Can't DROP 'domainmetaidindex'; 
check that column/key exists
  dbconfig-common: pdns-backend-mysql configure: aborted.
  dbconfig-common: flushing administrative password
  dpkg: error processing package pdns-backend-mysql (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libc-bin (2.19-13) ...
  Errors were encountered while processing:
   pdns-backend-mysql


cheers,

Andreas


pdns-backend-mysql_3.4.1-3.log.gz
Description: application/gzip

Bug#768681: marked as done (nodejs: FTBFS in jessie: tests failures)

[Debian Bug Tracking System]

Your message dated Wed, 17 Dec 2014 10:37:46 +0100
with message-id <20141217093745.ga23...@roeckx.be>
and subject line Re: [Pkg-openssl-devel] Bug#768681: Bug#768681: nodejs: FTBFS 
in jessie: tests failures
has caused the Debian Bug report #768681,
regarding nodejs: FTBFS in jessie: tests failures
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.)


-- 
768681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nodejs
Version: 0.10.29~dfsg-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/out'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory '/«PKGBUILDDIR»/out'
> ln -fs out/Release/node node
> /usr/bin/python tools/test.py --arch=x64 simple
> 

[00:00|%   0|+   0|-   0]: release test-abort-fatal-error 
 
[00:00|%   0|+   1|-   0]: release test-arraybuffer-slice 
 
[00:00|%   0|+   2|-   0]: release test-assert 
  
[00:00|%   0|+   3|-   0]: release test-bad-unicode 
   
[00:00|%   0|+   4|-   0]: release test-buffer 
  
[00:00|%   0|+   5|-   0]: release test-buffer-ascii 

[00:00|%   0|+   6|-   0]: release test-buffer-concat 
 
[00:00|%   1|+   7|-   0]: release test-buffer-regress-GH-2659 
  
[00:00|%   1|+   8|-   0]: release test-c-ares 
  
[00:01|%   1|+   9|-   0]: release test-chdir 
 
[00:01|%   1|+  10|-   0]: release test-child-process-buffering 
   
[00:01|%   1|+  11|-   0]: release test-child-process-customfd-bounded 
  
[00:01|%   1|+  12|-   0]: release test-child-process-cwd 
 
[00:01|%   2|+  13|-   0]: release test-child-process-detached 
  
[00:01|%   2|+  14|-   0]: release test-child-process-disconnect 

[00:01|%   2|+  15|-   0]: release test-child-process-double-pipe 
 
[00:01|%   2|+  16|-   0]: release test-child-process-env 
 
[00:02|%   2|+  17|-   0]: release test-child-process-exec-cwd 
  
[00:02|%   2|+  18|-   0]: release test-child-process-exec-env 
  
[00:02|%   3|+  19|-   0]: release test-child-process-exec-error 

[00:02|%   3|+  20|-   0]: release test-child-process-exit-code 
   
[00:02|%   3|+  21|-   0]: release test-child-process-fork 
  
[00:02|%   3|+  22|-   0]: release test-child-process-fork-and-spawn 

[00:02|%   3|+  23|-   0]: release test-child-process-fork-close 

[00:03|%   3|+  24|-   0]: release test-child-process-fork-dgram 

[00:03|%   4|+  25|-   0]: release test-child-process-fork-exec-argv 

[00:03|%   4|+  26|-   0]: release test-child-process-fork-exec-path 

[00:04|%   4|+  27|-   0]: release test-child-process-fork-getconnections 
 
[00:04|%   4|+  28|-   0]: release test-child-process-fork-net 
 

Bug#773343: request-tracker4: fails to upgrade from 'wheezy' if rt4-extension-assettracker is installed

[Andreas Beckmann]

Package: request-tracker4
Version: 4.2.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails.

rt4-extension-assettracker is not in jessie due to
#748737: doesn't support RT 4.2

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

  Setting up request-tracker4 (4.2.8-1) ...
  **WARNING**  
  **WARNING**  If you are using mod_perl or any form of persistent perl
  **WARNING**  process such as FastCGI, you will need to restart your
  **WARNING**  web server and any persistent processes now.
  **WARNING**  
  **WARNING**  For mod_perl this means
  **WARNING**  
  **WARNING**  invoke-rc.d apache2 stop && invoke-rc.d apache2 start
  **WARNING**  
  **WARNING**  
  **WARNING**  If you are using mod_perl or any form of persistent perl
  **WARNING**  process such as FastCGI, you will need to restart your
  **WARNING**  web server and any persistent processes now.
  **WARNING**  
  **WARNING**  For mod_perl this means
  **WARNING**  
  **WARNING**  invoke-rc.d apache2 stop && invoke-rc.d apache2 start
  **WARNING**  
  dbconfig-common: writing config to /etc/dbconfig-common/request-tracker4.conf
  creating database backup in 
/var/cache/dbconfig-common/backups/request-tracker4_4.0.7-5+deb7u2.sqlite3.
  applying upgrade script for 4.0.7-5+deb7u2 -> 4.0.10.
  Working with:
  Type: SQLite
  Host: localhost
  Port: 
  Name: /var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
  User: 
  DBA:   (No DBA)
  Now inserting data.
  Done inserting data.
  Done.
  applying upgrade script for 4.0.7-5+deb7u2 -> 4.0.12.
  Working with:
  Type: SQLite
  Host: localhost
  Port: 
  Name: /var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
  User: 
  DBA:   (No DBA)
  Now populating database schema.
  Done.
  applying upgrade script for 4.0.7-5+deb7u2 -> 4.0.19.
  Working with:
  Type: SQLite
  Host: localhost
  Port: 
  Name: /var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
  User: 
  DBA:   (No DBA)
  Now inserting data.
  Done inserting data.
  Done.
  Working with:
  Type: SQLite
  Host: localhost
  Port: 
  Name: /var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
  User: 
  DBA:   (No DBA)
  Now inserting data.
  Done inserting data.
  Done.
  applying upgrade script for 4.0.7-5+deb7u2 -> 4.2.3.
  Working with:
  Type: SQLite
  Host: localhost
  Port: 
  Name: /var/lib/dbconfig-common/sqlite3/request-tracker4/rtdb
  User: 
  DBA:   (No DBA)
  Enter RT version you're upgrading from: 
  Going to apply following upgrades:
  * 4.1.0
  * 4.1.1
  * 4.1.4
  * 4.1.5
  * 4.1.6
  * 4.1.7
  * 4.1.8
  * 4.1.9
  * 4.1.10
  * 4.1.11
  * 4.1.12
  * 4.1.13
  * 4.1.14
  * 4.1.15
  * 4.1.16
  * 4.1.17
  * 4.1.18
  * 4.1.19
  * 4.1.20
  * 4.1.21
  * 4.1.22
  * 4.1.23
  * 4.2.1
  * 4.2.2
  * 4.2.4
  * 4.2.6
  * 4.2.7
  * 4.2.8
  
  Enter RT version if you want to stop upgrade at some point,
or leave it blank if you want apply above upgrades: 
  Going to apply following upgrades:
  * 4.1.0
  * 4.1.1
  * 4.1.4
  * 4.1.5
  * 4.1.6
  * 4.1.7
  * 4.1.8
  * 4.1.9
  * 4.1.10
  * 4.1.11
  * 4.1.12
  * 4.1.13
  * 4.1.14
  * 4.1.15
  * 4.1.16
  * 4.1.17
  * 4.1.18
  * 4.1.19
  * 4.1.20
  * 4.1.21
  * 4.1.22
  * 4.1.23
  * 4.2.1
  * 4.2.2
  Processing 4.1.0
  Now inserting data.
  [24429] [Mon Dec 15 12:08:07 2014] [warning]: DBD::SQLite::db do failed: 
UNIQUE constraint failed: Groups.Name, Groups.Domain, Groups.Type, 
Groups.Instance at /usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat 
line 26, <> line 1. 
(/usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat:26)
  Processing 4.1.1
  Now populating database schema.
  Now inserting data.
  [24429] [Mon Dec 15 12:08:17 2014] [warning]: DBD::SQLite::db do failed: 
UNIQUE constraint failed: Groups.Name, Groups.Domain, Groups.Type, 
Groups.Instance at /usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat 
line 26, <> line 2. 
(/usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat:26)
  Processing 4.1.4
  Now populating database schema.
  Now inserting data.
  [24429] [Mon Dec 15 12:08:23 2014] [warning]: DBD::SQLite::db do failed: 
UNIQUE constraint failed: Groups.Name, Groups.Domain, Groups.Type, 
Groups.Instance at /usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat 
line 26, <> line 3. 
(/usr/share/request-tracker4/etc/upgrade/4.1.13/backcompat:26)
  [24429] [Mon Dec 15 12:08:23 2014] [error]: Can't load role group AdminCc: 
Couldn't find row (/usr/share/request-tracker4/etc/upgrade/4.1.4/content:18)
  [24429] [Mon Dec 15 12:08:23 2014] [error]: Can't load role group Cc: 
Couldn't find row (/usr/share/request-tracker4/etc/upgrade/4.1.4/content:18)
  [24429] [Mon Dec 15 12:08:23 2014] [error]: Can't load role group Owner: 
Couldn't find row (/usr/share/request-tracker4/etc/upgrade/4.1.4/content:18)
  [24429] [Mon Dec 15 12:08:23 2014] [error]: Can't load role group Requestor: 
Couldn't find row

Bug#773342: mingw32: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Package: mingw32
Version: 4.9.1-7+14.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:


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

  MISSING COPYRIGHT FILE: /usr/share/doc/mingw32/copyright
  # ls -lad /usr/share/doc/mingw32
  drwxr-xr-x 2 root root 40 Dec 11 13:12 /usr/share/doc/mingw32
  # ls -la /usr/share/doc/mingw32/
  total 0
  drwxr-xr-x   2 root root   40 Dec 11 13:12 .
  drwxr-xr-x 114 root root 2460 Dec 11 13:12 ..


Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.2)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


cheers,

Andreas


mingw32_4.9.1-7+14.2.log.gz
Description: application/gzip

Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed"

[Sebastian Dröge]

On Mi, 2014-12-17 at 09:35 +0100, webmbackslash wrote:
> Hi, i have this bug too.
> Attached is the valgrind output and it ended for me loading iceweasel
> for a few moments and showing "killed".
> This is the command i used:
> valgrind --track-origins=yes --trace-children=yes --leak-check=full   
> iceweasel

Hi,

thanks for the valgrind log, but I can see nothing there from the actual
crash. It's just a few memory leaks and processes exiting normally.

For the actual bug here, I suspect some reference counting problem
somewhere inside iceweasel but hard to locate it like this. Especially
as this crash never happened to me so far


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

Bug#773303: libgl1-mesa-dev: Symlink error for libGL.so

[Simon McVittie]

On Wed, 17 Dec 2014 at 14:52:33 +0800, Shan Ting wrote:
> sudo stat /usr/lib/x86_64-linux-gnu/libGL.so
>   File: ‘/usr/lib/x86_64-linux-gnu/libGL.so’ -> ‘libGL.so.1.2.0’

OK so far...

> sudo stat /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
> stat: cannot stat ‘/usr/lib/x86_64-linux-gnu/libGL.so.1.2.0’: No such file or 
> directory

... but that seems wrong for the packages you have installed. You said
you have:

> Package: libgl1-mesa-dev
> Version: 10.3.2-1
> ...
> ii  libgl1-mesa-glx 10.3.2-1

but those same packages on the same (amd64) architecture do provide
libGL.so.1.2.0:

% dpkg -s libgl1-mesa-dev
...
Version: 10.3.2-1
Depends: ..., libgl1-mesa-glx (= 10.3.2-1), ...
...
% dpkg -L libgl1-mesa-glx:amd64
...
/usr/lib/x86_64-linux-gnu/libGL.so.1.2.0
/usr/lib/x86_64-linux-gnu/libGL.so.1

>  I’m not using lx-alternative-fglrx, glx-alternative-nvidia or
> glx-diversions. The libGL.so.10.1.1.28614 is come from my graphic card
> driver(parallels).

Then I think this is a bug in your graphics card driver: it is overwriting
and deleting files owned by the packaging system, but not finishing the job
by taking responsibility for setting the target of the libGL.so symlink
(and not participating in glx-alternatives like the non-free drivers
packaged by Debian developers do, which would be the ideal thing).

> Is there some reasons to use libGL.so.1.2.0 directly rather than
> libGL.so.1?

That's how libraries' development symlinks normally work. For instance,
picking a random library for which I have development files
installed (Gtk 2):

% ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so
lrwxrwxrwx 1 root root 27 Oct 10 18:57 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so -> libgtk-x11-2.0.so.0.2400.25
default|archetype% ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
lrwxrwxrwx 1 root root 27 Oct 10 18:57 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0.2400.25
% ls -l /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.25
-rw-r--r-- 1 root root 4501992 Oct 10 18:57 
/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0.2400.25

The real file is the versioned one, and the development symlink and the
SONAME (runtime) symlink both point to it.

Regards,
S


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

Bug#773170: [Pkg-sysvinit-devel] Bug#773170: insserv: refuses to start postfix at boot because dnsmasq is disabled

[Yves-Alexis Perez]

On Tue, 16 Dec 2014 09:58:09 +0100 Petter Reinholdtsen  wrote:
> 
> Control: reassign -1 postfix
> 
> [Salvo Tomaselli]
> > Dear Maintainer,
> >
> > insserv refuses to start postfix at boot, because I have configured dnsmasq
> > to be disabled.
> 
> Hi.  As insserv is not involved at all during boot, I suspect this bug
> is misfiled.  Perhaps it is a problem with postfix or dnsmasq
> dependencies (should be soft, not hard) or with systemd refusing to
> start.  My prime suspect would be postfix, so I pass this bug over to
> the postfix maintainers for a closer look.  If postfix do not require
> dnsmasq (but should be startet after it if it exist) it should only use
> should-start instead of require-start in its init.d script.
> 

Well, postfix uses Required-start: $named because it needs name
resolution. And I guess dnsmasq provides $named by default, but that's
actually not the case in Salvo system. Not sure what's the correct way
to fix this. A quick way would be to remove the "Provide: $named", when
configuring dnsmasq to not be be used as a name resolution daemon, but
that can't really be done automatically.

Regards,
-- 
Yves-Alexis


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