Bug#412171: [installation-reports] Net install doesn't seem to work with manually entered ftp mirror.

[debianbugs]

Package: installation-reports

Boot method: netinst-CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 02/23/2007

Machine: Dell PowerEdge 750
Processor:
Memory:
Partitions: 

Output of lspci -nn and lspci -vnn:

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

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

Comments/Problems:
Net install doesn't seem to work with manually entered ftp mirror.

When manually entering an archive mirror URL, installer chooses http by 
default. Entering the "ftp://"; prefix won't help either.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#693874: closed by Christian PERRIER (Bug fixed in 1.15-1)

[debianbugs]

and this ia not gonna be fixed in squeeze or wheezy? you dont want to give them 
a security fix that prevents them to unintentionally delete data?


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

Bug#674142: upstream in 2.4.3 now

[debianbugs]

as the patch will be in 2.4.3 now, maybe the changes are there now that you
will add the patch to the 2.2 debian apache package. The mentioned parameter
rename nightmare should now not be a problem.


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

Bug#722016: netdiag: FTBFS under clang: main(unsigned int, ..) illegal

[debianbugs]

Package: netdiag
Version: 1.1-1
Severity: wishlist
Tags: patch

tcpspray.c:74:3: error: first parameter of 'main' (argument count) must be of 
type 'int'
  main(argc, argv)


diff --git a/tcpspray/tcpspray.c b/tcpspray/tcpspray.c
index 80102c4..257b259 100644
--- a/tcpspray/tcpspray.c
+++ b/tcpspray/tcpspray.c
@@ -72,7 +72,7 @@ typedef int pid_t;

 int
   main(argc, argv)
-unsigned int argc;
+int argc;
 char *argv[];
 {


http://clang.debian.net/status.php?version=3.3&key=WRONG_MAIN_DECLARATION

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (700, 'stable'), (400, 'testing'), (1, 'experimental'), (1, 
'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages netdiag depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.17-92
ii  libncurses55.9-10
ii  libpcap0.8 1.3.0-1
ii  libtinfo5  5.9-10
ii  netbase5.0

netdiag recommends no packages.

netdiag suggests no packages.

-- debconf information excluded


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

Bug#724038: libapache2-mod-gnutls: sites-available/default-tls isn't enableable; wrong name

[debianbugs]

Package: libapache2-mod-gnutls
Version: 0.5.10-2
Severity: wishlist

Dear Maintainer,

/etc/apache2/sites-available/default-tls is provided as an example
config, but can't be enabled as a2ensite expects a ".conf" extension.

faux@om:/etc/apache2/sites-available% ls
000-default.conf  default-ssl.conf  default-tls

faux@om:/etc/apache2/sites-available% sudo a2ensite default-tls
ERROR: Site default-tls does not exist!

faux@om:/etc/apache2/sites-available% sudo a2ensite default-ssl
Enabling site default-ssl.
To activate the new configuration, you need to run:
  service apache2 reload

-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (700, 'stable'), (400, 'testing'), (1, 'experimental'), (1, 
'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages libapache2-mod-gnutls depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.6-3
ii  libapr-memcache00.7.0-1
ii  libc6   2.17-92+b1
ii  libgnutls26 2.12.20-7

libapache2-mod-gnutls recommends no packages.

libapache2-mod-gnutls suggests no packages.

-- no debconf information


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

Bug#765472: Additional Info

[debianbugs]

Hi.
Redhat has addressed a bug that looks quite like this one.

See BZ#772619 in this document:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.3_Technical_Notes/nfs-utils.html

Greetings,
Norbert F.


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

Bug#574003: Acknowledgement (alacarte recommends gnome-panel, should be suggests or not at all)

[debianbugs]

I've just realised that alacarte isn't actually working correctly. Prior 
to looking into it further i'm assuming this is due to some of the 
packages that would've come with gnome-panel not being installed.


Sorry for the time waster, please disregard suggestion/bug report.

Regards,

Robert McCathie


On 16/03/10 03:18, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian GNOME Maintainers

If you wish to submit further information on this problem, please
send it to 574...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

   




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

Bug#926660: webfs: "systemctl stop webfs" not working

[debianbugs]

Package: webfs
Version: 1.21+ds1-12
Severity: important

Dear Maintainer,

webfs keeps running, even though it should be stopped. After a

systemctl stop webfs

syslog shows:

Apr  8 17:27:38 hostname webfs[13111]: Stopping httpd daemon: 
webfsdstart-stop-daemon: matching only on non-root pidfile 
/var/run/webfs/webfsd.pid is insecure
Apr  8 17:27:38 hostname webfs[13111]:  failed!
Apr  8 17:27:38 hostname systemd[1]: webfs.service: Succeeded.
Apr  8 17:27:38 hostname systemd[1]: Stopped LSB: Webfs simple HTTP server.


systemd refuses to kill the webfsd pid because the PID file is owned by
non-root user. After those syslog messages, webfsd keeps running.


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

Kernel: Linux 4.9.114-vs2.3.9.7 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages webfs depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  libc6  2.28-8
ii  libgnutls303.6.6-2
ii  lsb-base   10.2019031300
ii  ucf3.0038+nmu1

webfs recommends no packages.

webfs suggests no packages.

Bug#926660: Acknowledgement (webfs: "systemctl stop webfs" not working)

[debianbugs]

the package version is not indicating this: This problem pops up on
Debian buster, it was no issue on stretch.

Bug#971630:

[debianbugs]

retitle: Imagemagick convert can't convert to PDF

Bug#963607: [Pkg-xen-devel] Bug#963607: xen-hypervisor-4.11-amd64: Xen Hypervisor kernel fails to load arcmsr module with "arcmsr0: dma_alloc_coherent got error" message.

[debianbugs]

On 1/07/2020 22:48, Hans van Kranenburg wrote:
> On 7/1/20 5:09 PM, Alex Sanderson wrote:
>> On 1/07/2020 02:05, Hans van Kranenburg wrote:
>>> To do a bug report upstream, we'll need that information.
>> Sorry, completely misunderstood.   Here is the output from the serial
>> terminal as Xen started.
> Thanks! Yes. That's the XEN part that appears first.
>
> I attached the files, AFAIK you can just send attachments to a debian
> bug report. So, you can also do that, next time.
Good to know :) Wasn't sure, I have been using debian since the late
90's and so far have always logged bugs upstream.
> The files justlinux-notime.txt and xen-dom0-notime.txt have the
> timestamps removed from the beginning of the linux part of the logging,
> so that we can diff the files.
>
> E.g. colordiff -u justlinux-notime.txt xen-dom0-notime.txt |less -r
>
> Now, here's an interesting part:
>
>  8< 
>
> @@ -973,20 +1031,15 @@
>  usb usb1: SerialNumber: :00:1a.0
>  hub 1-0:1.0: USB hub found
>  hub 1-0:1.0: 2 ports detected
> -isci :09:00.0: OEM parameter table found in OROM
> -isci :09:00.0: OEM SAS parameters (version: 1.0) loaded (platform)
> +xen: registering gsi 23 triggering 0 polarity 1
> +Already setup the GSI :23
>  ehci-pci :00:1d.0: EHCI Host Controller
>  ehci-pci :00:1d.0: new USB bus registered, assigned bus number 2
>  ehci-pci :00:1d.0: debug port 2
>  ehci-pci :00:1d.0: cache line size of 64 is not supported
>  ehci-pci :00:1d.0: irq 23, io mem 0xcfc22000
> -isci :09:00.0: SCU controller 0: phy 3-0 cables: {short, short,
> short, short}
> -scsi host1: isci
>  Areca RAID Controller0: Model ARC-1882, F/W V1.56 2019-07-30
> -scsi host0: Areca SAS/SATA RAID Controller (RAID6 capable)
> -arcmsr version v1.40.00.09-20180709
> -
> -arcmsr0: msi-x enabled
> +arcmsr0: dma_alloc_coherent got error
>  ehci-pci :00:1d.0: USB 2.0 started, EHCI 1.00
>  usb usb2: New USB device found, idVendor=1d6b, idProduct=0002,
> bcdDevice= 4.19
>  usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
>
>  >8 
>
> So, when running Linux as dom0 under Xen, you get the "arcmsr0:
> dma_alloc_coherent got error". Did you already spot this error?
>
> Just pasting it into a search engine leads me to the following page:
>
> http://faq.areca.com.tw/index.php?action=artikel&cat=16&id=387&artlang=en
>
> ...which only displays an error.
>
> There's also:
>
> https://webcache.googleusercontent.com/search?q=cache:wQHp6mpYuckJ:faq.areca.com.tw/index.php%3Faction%3Dartikel%26cat%3D16%26id%3D387%26artlang%3Den+&cd=1&hl=nl&ct=clnk&gl=nl
>
>  8< 
>
> Q10051103 - We have problems with the new Linux driver
> (arcmsr.1.20.0X.15-100729) for the raid controller ARC-1880. Our system
> is Linux debian 5.07 (lenny) amd64. Build the driver agains the XEN
> kernel (2.6.26-2-xen-amd64) we got following errors on boot time:
> arcmsr0: dma_alloc_coherent got error arcmsr0: arcmsr_alloc_ccb_pool got
> error
>
> you may get this error message when system have no enough memory space
> for driver requested please configure driver host queue to 64 or less to
> see if it helps.
>
> you can configure driver host queue parameter by typing the driver
> parameter as kernel option during system booting.
>
> arcmsr.host_can_queue=64
>
>  >8 
>
> So, you have an 1882, which is close to 1880.
>
> I'd say, try it! This arcmsr.host_can_queue=64 should go on the linux
> command line.
>
> You can use GRUB_CMDLINE_LINUX_XEN_REPLACE in
> /etc/default/grub.d/xen.cfg for that, so that it gets applied when
> booting with Xen, and not when booting standalone Linux. There's some
> documentation in that file.

Yes I have seen the error, unfortunately it was the only information I
had on the problem and I have squeezed everything I can from the net
regarding it.  I even looked at the source code.   In my original bug
report I did actually mention testing that kernel argument but it didn't
help.   I tried that arg and every related memory argument to do with
coherent memory allocation but nothing worked.  

I am about to purchase a new SAS HBA card to test as we have a number of
these servers with Areca cards that I imagine will have the same problem
on Xen 4.11.   I am leaning towards mpt3 driver cards but we have had
problems with mpt3 previously so I am hesitating there too.  mpt2 has
been rock solid. 

If you can think of anything else that I could try that would be
excellent.  

Thanks

Alex


>
> Feel free to ask more about it if it's unclear how the different options
> work together. The text in that file is part of our Xen packages, so
> feedback on it is always appreciated. We might be able to improve something.
>
> Thanks, curious to hear about the results, and otherwise we'll continue
> our searching for a solution,
>
> Hans

Bug#959733: cant update wireguard

[debianbugs]

Package: wireguard-dkms
Version: 1.0.20200429-1~bpo10+1


If i update my wireguard, i get the following error:

DKMS make.log for wireguard-1.0.20200429 for kernel 4.19.0-8-amd64 (x86_64)
Mo 4. Mai 18:42:30 CEST 2020
make: Verzeichnis „/usr/src/linux-headers-4.19.0-8-amd64“ wird betreten
/bin/sh: 1: bc: not found
/var/lib/dkms/wireguard/1.0.20200429/build/compat/Kbuild.include:58: *** 
bc(1) is required for building.  Schluss.
make[2]: *** [/usr/src/linux-headers-4.19.0-8-common/Makefile:1537: 
_module_/var/lib/dkms/wireguard/1.0.20200429/build] Fehler 2

make[1]: *** [Makefile:146: sub-make] Fehler 2
make: *** [Makefile:8: all] Fehler 2
make: Verzeichnis „/usr/src/linux-headers-4.19.0-8-amd64“ wird verlassen

If it a problem with the dependencies to the meta package wireguard?

Bug#944020: Help with this for TAILS

[debianbugs]

Hello-

I'm doing some work with the Tails team working to get Trezor python-trezor and 
python-libusb1 back-ported to Buster. These packages can then be put into 
testing for Tails to use. Currently this all hinges on getting debian bug 
944020 > fixed, as per the 
discussion over with the Tails team: 
https://redmine.tails.boum.org/code/issues/17461#change-116459 
 
> . 

I am inquiring to see if there is anything I can do to help expedite 944020 and 
get the process moving along.

Regards

Bug#959733: cant update wireguard

[debianbugs]

Hi,

on my site is the problem solved with ticket 956869. See On:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956869

Bug#387808: fails to properly handle when server-ip is included in root-path

[vagrant+debianbugs]

found 387808 0.81
thanks

ok, i've figured out the failure case from my original bug report,
though i haven't yet figured out why.

when i specify a root-path of 192.168.111.65:/opt/ltsp/i386 in my dhcpd
server, initramfs-tools adds the server-ip received from dhcp, so
NFSROOT ends up being 192.168.111.64:192.168.111.65:/opt/ltsp/i386 when
it tries to mount it.

specifying nfsroot=192.168.111.65:/opt/ltsp/i386 at the boot prompt
works fine, as well as nfsroot=/opt/ltsp/i386. specifying a root-path of
/opt/ltsp/i386 in the dhcp server works as well.

i'm at a loss as to why, but at least i figured out when it happens.

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#601733: python-moinmoin: wrong permissions on /etc/moin files

[debianbugs . boog]

I can confirm that this is a problem on a fresh Debian Lenny install
plus python-moinmoin Version: 1.7.1-3+lenny5.
It prevents a successful set up following the steps in
/usr/share/doc/python-moinmoin/README.Debian.gz.

The error displayed is a s follows:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
ImportError: No module named wikiconfig

Check that the file is in the same directory as the server script. If
it is not, you must add the path of the directory where the file is
located to the python path in the server script. See the comments at
the top of the server script.

Check that the configuration file name is either "wikiconfig.py" or
the module name specified in the wikis list in farmconfig.py. Note
that the module name does not include the ".py" suffix.

Error in your configuration file
"/var/lib/python-support/python2.5/MoinMoin/config/multiconfig.py"
around line 45.
- - - - - - - - - - - - - - - - - - - - - - - - - - -

I also can confirm that it took me way too long to find this solution
through trial and error. I really wish I would have found this bug
report *before* I "fixed" it.




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

Bug#623194: Please upgrade fvwm to version 2.6.3

[gi1242+debianbugs]

On Fri, Jan 20, 2012 at 09:31:42AM +, Michael Stevens wrote:

>> It would be great to see fvwm 2.6.3 in debian. Please Upgrade
> 
> I too would like to see this.

I'd love to see this in Debian too.

GI

-- 




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

Bug#706990: Only fixed in testing

[gi1242+debianbugs]

I noticed that the iceweasel-17.0.6esr-1~deb7u1 is now pulled through
wheezy/updates from security.debian.org.

The xul-ext-pentadactyl-1.0~rc1-1 from wheezy is incompatible with
iceweasel-17.0.6esr-1~deb7u1 (as pointed out above).

The xul-ext-pentadactyl-1.0+hg6924-1 (from testing) is compatible with
iceweasel, of course, but is not in wheezy.

Should users pull xul-ext-pentadactyl-1.0+hg6924-1 from testing? Or will
there be a compatible version released for wheezy? (I don't mind pulling
it from wheezy for now; but I'm concerned that somewhere down the road
the xul-ext-pentadactyl/testing will stop working with
iceweasel/wheezy...)

GI

PS: Sorry if I asked a "standard procedure" question, which you are
already in the process of taking care off...

-- 
'Gambling' -- The sure way of getting nothing for something.


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

Bug#568608: Regression: Slow VT switching

[gi1242+debianbugs]

On Tue, Mar 02, 2010 at 12:31:34AM +1030, Ron wrote:

> This looks like you're probably just getting bitten by the fact that
> there is no support for serial tablets yet in the udev/config server.
> That should be coming soon.  There is a patch in bug #568236 if you
> want it even sooner.

Thanks Ron. I'll have to either wait for spring break, or the next
upload (more likely the latter). Will let you know if the problem
persists or not after that.

GI

-- 
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
33. I won't require high-ranking female members of my organization to
wear a stainless-steel bustier. Morale is better with a more casual
dress-code. Similarly, outfits made entirely from black leather will be
reserved for formal occasions.



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

Bug#627482: Segmentation fault on level 1 of area 2

[gi1242+debianbugs]

I have the same issue. I've noticed the segfault usually occurs when the
ball leaves the TOP of the screen. Initially there are a bunch of thin
yellow bricks, which break after the ball hits them once. The second
time the ball goes there, it goes through the gap and off the top of the
screen, and the segfault happens.

GI

-- 
'Oregon' -- When, after two days of rain, Monday arrives.



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

Bug#661845: biff: postinst assumes existence of /etc/inetd.conf and hence prints errors

[pfx-debianbugs]

Package: biff
Version: 1:0.17.pre2412-5
Severity: minor

postinst contains:
if grep -q 'biff dgram udp wait nobody.mail /usr/sbin/in.comsat comsat' 
/etc/inetd.conf

.. which prints:
grep: /etc/inetd.conf: No such file or directory

.. as /etc/inetd.conf doesn't exist on my system.  This is scary to me.

-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (700, 'stable'), (400, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages biff depends on:
ii  libc6 2.11.3-2   Embedded GNU C Library: Shared lib
ii  netbase   4.45   Basic TCP/IP networking system

biff recommends no packages.

biff suggests no packages.

-- no debconf information



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

Bug#661846: biff: postinst assumes existence of /etc/inetd.conf and hence prints errors

[pfx-debianbugs]

Package: biff
Version: 1:0.17.pre2412-5
Severity: minor

postinst contains:
if grep -q 'biff dgram udp wait nobody.mail /usr/sbin/in.comsat comsat' 
/etc/inetd.conf

.. which prints:
grep: /etc/inetd.conf: No such file or directory

.. as /etc/inetd.conf doesn't exist on my system.  This is scary to me.

-- System Information:
Debian Release: 6.0.4
  APT prefers stable
  APT policy: (700, 'stable'), (400, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages biff depends on:
ii  libc6 2.11.3-2   Embedded GNU C Library: Shared lib
ii  netbase   4.45   Basic TCP/IP networking system

biff recommends no packages.

biff suggests no packages.

-- no debconf information



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

Bug#315142: Gtk+Perl alternative to wacomcpl

[gi1242+debianbugs]

The upgrade to xserver-xorg-input-wacom 0.12.0-1 broke everything.
Here's an update of the calibration script to work with the new
xsetwacom syntax.

I've heard there's a way to set the calibration / etc. through HAL.
However, as long as xsetwacom "Works for me (tm)", I'll follow the path
of least resistance.

GI

-- 
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
24. I will maintain a realistic assessment of my strengths and
weaknesses. Even though this takes some of the fun out of the job, at
least I will never utter the line "No, this cannot be! I AM
INVINCIBLE!!!" (After that, death is usually instantaneous.)


calibrate.pl
Description: Perl program

Bug#661171: Needs desktop-file-utils

[gi1242+debianbugs]

I had the same problem. However, I don't think there's a problem with
xdg-open. I don't think that xdg-open does any translation of %c or %i
(see the source). The translation seems to be done by mimeopen.

I installed desktop-file-utils, and did update-desktop-database. It
seems fine now,

GI

-- 
Little Johnny was a scientist. Little Johnny is no more. For what he
thought was H2O was H2SO4.



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

Bug#794372: Oh, the transition!

[solo-debianbugs]

I have been reminded that there's a nasty C++ transition going on, so
these might be transient (i.e. fixed when the upstream libraries are
done transitioning).

Feel free to close as invalid, drop priority, or whatever!


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

Bug#793319: FTBFS: ImportError: cannot import name component_re

[solo-debianbugs]

On Wed, Aug 12, 2015 at 04:31:15PM +0300, Gediminas Paulauskas wrote:
> Now that Bug#779324 is fixed, a simple rebuild would fix the problem.

Looks good, yep.

Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

[solo-debianbugs]

On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote:
> control: tags -1 + unreproducible
> 
> Chris, was this an issue on your end? Or am I misinterpreting something?
> 

The problem seems to have gone away.  I was running local builds in
response to errors on the reproducible-builds builder.  Their builder
has rebuilt sucessfully since then, and I have also just rebuilt
sucessfully.  Perhaps it was fixed by dependency changes?

Proof I'm not mad: my build log from local:
https://paste.debian.net/286717/


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

Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

[solo-debianbugs]

On Mon, Jul 27, 2015 at 10:45:17PM +0200, Michael Stapelberg wrote:
> Actually, my bad, the commit I referenced is already in the package in the
> form of a patch.
> 
> In your https://paste.debian.net/286717/, I don’t see any mention of the
> patch, though…? Does your build environment not apply patches? When running
> gbp buildpackage --git-pbuilder, I see:
> [..]

Unless I'm missing something, the patch is not in the version in
unstable/testing.  Looking at the git repo linked from tracker.d.o,
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-glacjay-goini.git/
the patch was added after the release was tagged.

The paste link is building from unstable, so (correctly) isn't seeing
the patch?


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

Bug#755132: zathura: fails to start (symbol lookup error)

[gi1242+debianbugs]

Package: zathura
Version: 0.2.9-2
Severity: grave
Justification: renders package unusable

When I run zathura it exits immediately with the message

/usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined
symbol: girara_template_add_variable

PS: Note I'm running zathura in a testing chroot.


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

Kernel: Linux 3.14-0.bpo.1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Shell: /bin/sh linked to /bin/dash

Versions of packages zathura depends on:
ii  libc6 2.19-7
ii  libcairo2 1.12.16-2
ii  libgirara-gtk3-1  0.2.2-2
ii  libglib2.0-0  2.40.0-3
ii  libgtk-3-03.12.2-1+b1
ii  libmagic1 1:5.19-1
ii  libpoppler-glib8  0.26.2-2
ii  libsqlite3-0  3.8.5-2
ii  libsynctex1   2014.20140528.34243-4

zathura recommends no packages.

Versions of packages zathura suggests:
ii  iceweasel [www-browser]  30.0-2
ii  poppler-data 0.4.6-5
pn  zathura-cb   
ii  zathura-djvu 0.2.3-5
ii  zathura-ps   0.2.2-5

-- no debconf information

-- 
Freedom of speech is wonderful - right up there with the freedom not to
listen.


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

Bug#755132: zathura: fails to start (symbol lookup error)

[gi1242+debianbugs]

On Fri, Jul 18, 2014 at 09:04:20AM +0200, Sebastian Ramacher wrote:

>> When I run zathura it exits immediately with the message
>> 
>> /usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined
>> symbol: girara_template_add_variable
> 
> Looks like you have an old copy of libgirara-gtk3.so.1 somewhere in
> library lookup path. Please attach ld -r /usr/bin/zathura.

Hmm. I'm no LD guru:

$ ld -r /usr/bin/zathura
ld: attempted static link of dynamic object `/usr/bin/zathura'

However, you are 100% right about an old copy of libgirara-gtk3.so.1 in
my library lookup path. Running

LD_LIBRARY_PATH= /usr/bin/zathura

fixes the problem.

Thanks a lot and sorry to bother you for a mistake of mine! Please close
this bug.

GI

-- 
Don't have awk? Use this simple sh emulation:
#!/bin/sh
echo 'Awk bailing out!'
exit 2


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

Bug#792064: [Pkg-javascript-devel] Bug#792064: FTBFS: tests fail with CAP_DAC_OVERRIDE and without networking

[solo-debianbugs]

On Sun, Jul 12, 2015 at 05:56:08PM +0200, Luca Bruno wrote:
> However, as this seems to be part of repro-build (which I do care about), you 
> can find a patch here that should fix it. Let me know if it works.

Woo, thanks!


> > If you have CAP_DAC_OVERRIDE (e.g. you're running the build as root),
> 
> Isn't this an incredibly bad practice?

That builder (one I'm in the middle of writing!) runs stuff as "uid 0"
inside an unprivileged LXC (i.e. in a new uid/pid/mount/... namespace),
which is (I believe) supported for security, i.e. it should be safe.
It's easy enough to flip the builder over to using a normal user
inside the container, in the future.

I was under the impression that there was a policy entry requiring stuff
to be buildable as root, so I thought I'd let it run as root for now.
Otoh, I can't actually find said policy entry, nor one for requiring
packages to build without networking; perhaps the latter covered simply
by the requirement that there's no dependency on anything outside of
main.


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

Bug#792221: libnet-frame-device-perl: FTBFS without networking: t/04-new-default and t/05-new-target fail

[solo-debianbugs]

On Mon, Jul 13, 2015 at 01:19:29AM +0200, gregor herrmann wrote:
> > Full build log:
> > https://reproducible.debian.net/rb-pkg/unstable/amd64/libnet-frame-device-perl.html
> 
> It seems to be a bit more complicated than that.
> 
> With "USENETWORK=no" I indeed see the failures:
> ...
> # Using Test.pm version 1.26
> Dubious, test returned 101 (wstat 25856, 0x6500)
> Failed 1/1 subtests 
> Possible precedence issue with control flow operator at 
> /tmp/buildd/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 
> 63.
> Net::Frame::Device: updateFromTarget: unable to get dnet
> t/05-new-target.t  
> 1..1
> # Running under perl version 5.020002 for linux
> # Current time local: Sun Jul 12 23:16:50 2015
> # Current time GMT:   Sun Jul 12 23:16:50 2015
> # Using Test.pm version 1.26
> Dubious, test returned 101 (wstat 25856, 0x6500)
> Failed 1/1 subtests 
> 
> 
> but only during the build, when cowbuilder drops me into a shell, a
> manual `prove --blib --verbose t/*.t' works fine.

I was manually re-testing things inside lxc (with eth0 down), and can
hit the failure even with `prove`:

% lxc-attach -n sid2
root@sid2:~# cd libnet-frame-device-perl-1.10/
root@sid2:~/libnet-frame-device-perl-1.10# ifdown eth0
[...]
root@sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t
t/01-use.t ...
[...]
t/04-new-default.t ... 
1..1
# Running under perl version 5.020002 for linux
# Current time local: Mon Jul 13 07:23:47 2015
# Current time GMT:   Mon Jul 13 07:23:47 2015
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at 
/home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromDefault: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 
t/05-new-target.t  
1..1
# Running under perl version 5.020002 for linux
# Current time local: Mon Jul 13 07:23:47 2015
# Current time GMT:   Mon Jul 13 07:23:47 2015
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at 
/home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromTarget: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 



Is it my imagination, or does that "unable to get dnet" message appear
in the 05 test only for me?



---

And, because I failed to send the e-mail before getting distracted, I
did some debugging:

The (apparent) error is it calling intf_get_dst('1.1.1.1') which
"retrieves the configuration for the best interface with which to
reach the specified dst.", which fails.

Indeed, I can reproduce this for 04 by blackholing 1.1.1.1 (I don't
actually know what this does, but it sounds cool):

root@sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t 
>/dev/null 2>&1 && echo passed
passed
root@sid2:~/libnet-frame-device-perl-1.10# ip r add blackhole 1.1.1.1/32
root@sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t

t/04-new-default.t ... 
1..1
[...]
Possible precedence issue with control flow operator at 
/home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromDefault: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 
t/05-new-target.t  
1..1
[...]
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at 
/home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
$VAR1 = {
  'gatewayIp' => '10.0.3.1',
[...]
root@sid2:~/libnet-frame-device-perl-1.10# ip r del 1.1.1.1


Does that help you reproduce it?  I suspect the answer is simply to disable
these tests if there isn't public connectivity (or just generally), however.


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

Bug#778421: haskell-hscurses: FTBFS haskell-devscripts (>= 0.9) isn't in unstable

[solo-debianbugs]

Package: src:haskell-hscurses
Version: 1.4.2.0-1
Severity: wishlist

Dear Maintainer,

The package depends on haskell-devscripts (>= 0.9), which is only in
experimental, not sid.

pbuilder:

The following NEW packages will be installed:
  cdbs{a} ghc{a} ghc-doc{a} ghc-haddock{a} ghc-prof{a} libbsd-dev{a} 
  libbsd0{a} libffi-dev{a} libghc-exceptions-dev{a} 
  libghc-exceptions-doc{a} libghc-exceptions-prof{a} libghc-mtl-dev{a} 
  libghc-mtl-doc{a} libghc-mtl-prof{a} libghc-transformers-dev{a} 
  libghc-transformers-prof{a} libgmp-dev{a} libgmpxx4ldbl{a} 
  libncurses5-dev{a} libtinfo-dev{a} 
0 packages upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 65.4 MB of archives. After unpacking 761 MB will be used.
The following packages have unmet dependencies:
 pbuilder-satisfydepends-dummy : Depends: haskell-devscripts (>= 0.9) but it is 
not going to be installed.
Unable to resolve dependencies!  Giving up...
[...]
Abort.


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

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

[solo-debianbugs]

Package: libmaven-archiver-java
Version: 2.5-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that many Java packages would not build reproducibly because Maven emits
a build date in the "pom.properties" file generated by maven-archiver
(as used by maven-jar-plugin) [2].

Ideally, this date would be removed.
I believe that it's there by accident:
 * it's in a comment so it's hard (but not impossible) for people to access
 * it's written by java.lang.Properties, not intentionally by Maven code
 * it's not updated by any of the code in maven-archiver to update the file

However, in order to maintain nearly total backwards compatability, the
attached patch causes the original behaviour to be maintained unless a
BUILD_DATE environment variable is set.  The plan is for this to
(eventually) be set by something like javahelper.  Patch should apply to
2.5, 2.6 and trunk at time of writing (2.7-SNAPSHOT).

Your thoughts would be appreciated.  There are some alternative
solutions being gathered on the wiki [3].

Cheers.

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: 
https://reproducible.debian.net/issues/timestamps_in_maven_pom_files_issue.html
 [3]: https://wiki.debian.org/ReproducibleBuilds/TimestampsInMavenPomProperties

>From d725546a99257c1fe6b03a7321142e6d564665d7 Mon Sep 17 00:00:00 2001
From: "Chris West (Faux)" 
Date: Fri, 9 Jan 2015 21:19:43 +
Subject: [PATCH] honour BUILD_DATE when generating pom.properties

---
 .../apache/maven/archiver/PomPropertiesUtil.java   | 88 +-
 .../maven/archiver/PomPropertiesUtilTest.java  | 34 +
 2 files changed, 121 insertions(+), 1 deletion(-)
 create mode 100644 src/test/java/org/apache/maven/archiver/PomPropertiesUtilTest.java

diff --git a/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java b/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
index 5e0a41b..605a2f1 100644
--- a/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
+++ b/src/main/java/org/apache/maven/archiver/PomPropertiesUtil.java
@@ -25,6 +25,17 @@ import java.io.FileOutputStream;
 import java.io.IOException;
 import java.io.InputStream;
 import java.io.OutputStream;
+import java.io.OutputStreamWriter;
+import java.io.Writer;
+import java.io.BufferedWriter;
+import java.text.SimpleDateFormat;
+import java.text.ParseException;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.Comparator;
+import java.util.Date;
+import java.util.List;
+import java.util.Map;
 import java.util.Properties;
 
 import org.apache.maven.project.MavenProject;
@@ -85,7 +96,7 @@ public class PomPropertiesUtil
 OutputStream os = new FileOutputStream( outputFile );
 try
 {
-properties.store( os, GENERATED_BY_MAVEN );
+storeWithCustomTimestamp(properties, os);
 os.close(); // stream is flushed but not closed by Properties.store()
 os = null;
 }
@@ -117,4 +128,79 @@ public class PomPropertiesUtil
 
 archiver.addFile( pomPropertiesFile, "META-INF/maven/" + groupId + "/" + artifactId + "/pom.properties" );
 }
+
+/**
+ * Java always writes the date in a comment.  We have to reimplement the method to change the date.
+ */
+static void storeWithCustomTimestamp(Properties properties, OutputStream os) throws IOException {
+final BufferedWriter writer = new BufferedWriter(new OutputStreamWriter(os, "8859_1"));
+try {
+writer.append("#" + GENERATED_BY_MAVEN);
+writer.newLine();
+writer.append("#" + computeBuildDate().toString());
+writer.newLine();
+final List> entries =
+new ArrayList>(properties.entrySet());
+Collections.sort(entries, new Comparator>() {
+public int compare(Map.Entry left, Map.Entry right) {
+return String.valueOf(left.getKey()).compareTo(String.valueOf(right.getKey()));
+}
+});
+for (Map.Entry property : entries) {
+writer.write(property.getKey() + "=" + escapeForProperties(String.valueOf(property.getValue(;
+writer.newLine();
+}
+} finally {
+writer.flush();
+writer.close();
+}
+}
+
+private static Date computeBuildDate() {
+final String envVariable = System.getenv("BUILD_DATE");
+if (null != envVariable) {
+try {
+return new SimpleDateFormat("EEE, dd MMM  HH:mm:ss zzz").parse(envVariable);
+} catch (ParseException e) {
+System.err.println("maven-archiver: BUILD_DATE not in recognised format");
+e.printStackTrace();
+// fall through
+}
+}
+return new Date();
+}
+
+static 

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

[solo-debianbugs]

On Sat, Jan 10, 2015 at 10:19:19PM +0100, Emmanuel Bourg wrote:
> Thank you for the update. It's safe to assume the date always follow the
> comment specified, the Javadoc for the store() method states:
> 
> "Next, a comment line is always written, consisting of an ASCII #
> character, the current date and time (as if produced by the toString
> method of Date for the current time), and a line separator as generated
> by the Writer."

Sweet.

> The call to Arrays.sort() isn't necessary but it doesn't hurt.

I couldn't see any evidence that the properties would always come out in
the same order; it looks like it defers to Hashtable, which definitely
doesn't have defined iteration order (in theory, but probably does in
practice (unless any of that security-driven randomized hashCode stuff
went in (which I can't see any evidence of))).


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

Bug#802059: Already reported against glibmm2.4

[solo-debianbugs]

Maybe this is a duplicate of:

https://bugs.debian.org/800371

..depending on the solution they arrive at.

Bug#802105: iodine: FTBFS: Assertion 'addr_len == sizeof(struct sockaddr_in)' failed

[solo-debianbugs]

On Sat, Oct 17, 2015 at 05:58:13PM +0200, gregor herrmann wrote:
> I'm lowering the severity of the bug for now, since this doesn't
> look like a bug in the code itself but like a weird interaction
> between the test suite and pbuilder's optional use of namespaces.
> 

Heh.  I try and eliminate these cases by rebuilding them on lxc (which
it also failed in the same way), but lxc /also/ has weird uses of
namespaces, so.. :)

Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64

[solo-debianbugs]

On Thu, Jun 25, 2015 at 12:03:04AM +0200, Axel Beckert wrote:
> > t/undo.t ... ok
> > t/unexpected-cases.t ... 
> > Dubious, test returned 1 (wstat 256, 0x100)
> > Failed 1/98 subtests 
> thanks for the report, but I couldn't reproduce this, neither with
> 0.3.3 nor with the HEAD of the git repository. And
> https://reproducible.debian.net/rb-pkg/unstable/amd64/unburden-home-dir.html
> shows different tests failing, but not t/unexpected-cases.t.
> 
> Can you please explain a little bit more about your setup? pbuilder or
> sbuild? On which file system where the tests run? (And if the
> reporting machine was not the same as the machine where the issue
> happend: Which locale was set? Which init system was used? Which
> kernel was running?) etc.

Hah.  After far too much staring, the test which is failing for me is:

ok 93 - Make list file t/zo4O_qcnum/list unreadable
ok 94 - Call 'perl bin/unburden-home-dir -C t/zo4O_qcnum/config -c /dev/null -L 
t/zo4O_qcnum/list -l /dev/null'
not ok 95 - Check STDERR
#   Failed test 'Check STDERR'
#   at t/lib/Test/UBH.pm line 260.
# --- Got
# +++ Expected
# @@ -1 +1,2 @@
# -''
# +'List file t/8mn4dawfHl/list isn\'t readable, skipping at
# unburden-home-dir line .
# +'
# Looks like you failed 1 test of 98.


It's running chmod  foo && cat foo, and expecting it to fail.  It
succeeds for me as I have a better simulation of root: I'm running the
build as very-nearly root on a VM.  (root in an unpriviliged LXC
container).

The full build log isn't much more useful; sorry for missing some
important parts in the initial report: https://paste.debian.net/260610/

My specific bug is probably invalid, in this case?  I don't think we
expect the builds to pass as root.  Weird test, though.


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

Bug#805249: pyparted: FTBFS: PartedException: Unknown disk flag, 1000.

[solo-debianbugs]

Hmm.

I re-test things on my local builder before reporting them, so I've
definitely been able to reproduce this failure.  My builder is much
more normal than jenkins: it uses apt to resolve packages, and things
like that.

If you don't have any ideas then I can run the build a few more times
and see if I can catch what's up.

Bug#745224: FTBFS on amd64/sid

[solo-debianbugs]

Control: severity -1 serious

The package fails to build on amd64 in sid with the same errors.

Full build log (reproduced outside of pbuilder locally):
https://reproducible.debian.net/rb-pkg/unstable/amd64/stretchplayer.html


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

Bug#776292: -Werror is on by default, so FTBFS in sid

[solo-debianbugs]

Control: severity -1 serious

The package fails to build in sid, as -Werror is on by default.

Full build log (checked locally):
https://reproducible.debian.net/rb-pkg/unstable/amd64/ffrenzy.html


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

Bug#790800: ..or maybe this is just transition noise

[solo-debianbugs]

This is happening to other packages too, and I can't find the .moc files
I thought were bundled before; maybe it's just transition related and
will go away?

See e.g. qapt:
https://reproducible.debian.net/rb-pkg/unstable/amd64/qapt.html


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

Bug#791410: m17n-db: FTBFS due to missing Build-Conflicts: locales-all

[solo-debianbugs]

On Mon, Jul 06, 2015 at 03:37:04PM +0530, Harshula wrote:
> Hi,
> 
> Could you please elaborate on what changed to cause this side-effect?

There was no change to your package or any other package; it has (as far
as I'm aware) always been legal to have locales-all instead of locales.

It's just likely that nobody has ever tried this before...

> 
> Thanks,
> #
> 
> On 04/07/15 18:47, Chris West (Faux) wrote:
> > Source: m17n-db
> > Version: 1.6.5-1
> > Severity: important
> > Tags: sid stretch
> > User: reproducible-bui...@lists.alioth.debian.org
> > Usertags: ftbfs
> > 
> > Dear Maintainer,
> > 
> > The package fails to build when locales-all is installed.
> > locales-all "provides" locales, but doesn't really have all the stuff 
> > everyone expects.
> > There is some discussion available in https://bugs.debian.org/788353
> > 
> > Please apply the recommended solution, adding:
> > Build-Conflicts: locales-all
> > 
> > 
> > Specific error:
> > 
> > config.status: creating po/Makefile
> > config.status: executing depfiles commands
> > ---ERROR---ERROR---ERROR
> > Can't find source files for generating charset maps.
> > Run the script "./get-glibc.sh", and try again.
> > Or, read the installation procedure in the file README.
> >   --with-charmaps=--DIRECTORY-OF-GLIBC-SOURCE--/localedata/charmaps
> > ---ERROR---ERROR---ERROR
> > dh_testdir
> > /usr/bin/make
> > make[1]: Entering directory '/tmp/buildd/m17n-db-1.6.5'
> > Making all in po
> > make[2]: Entering directory '/tmp/buildd/m17n-db-1.6.5/po'
> > make[2]: Nothing to be done for 'all'.
> > make[2]: Leaving directory '/tmp/buildd/m17n-db-1.6.5/po'
> > Making all in LANGDATA
> > make[2]: Entering directory '/tmp/buildd/m17n-db-1.6.5/LANGDATA'
> > (for f in [a-z][a-z].lnm [a-z][a-z][a-z].lnm; do \
> >   l=`basename $f .tbl`; \
> >   sed -n -e "/($l /s/(\([a-z]*\)[^\"]*\"\([^\"]*\)\")/\1|\2/p" < $f; \
> > done) > native.ext
> > mawk -f LANGUAGE.awk '-F|' < ISO-639-2.txt > LANGUAGE.tbl
> > make[2]: Leaving directory '/tmp/buildd/m17n-db-1.6.5/LANGDATA'
> > make[2]: Entering directory '/tmp/buildd/m17n-db-1.6.5'
> > make[2]: *** No rule to make target '8859-2.map', needed by 'all-am'.  Stop.
> > 
> > 
> > Full build log:
> > https://reproducible.debian.net/rb-pkg/unstable/amd64/m17n-db.html
> > 
> > -- System Information:
> > Debian Release: stretch/sid
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
> > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > 


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

Bug#809982: zathura: Memory leak when PDF is refreshed

[gi1242+debianbugs]

Package: zathura
Version: 0.3.1-2
Severity: normal

Dear Maintainers,

There is a memory leak in zathura. Steps to reproduce:

1. Open a PDF file (e.g. output generated by LaTeX)

2. Scroll

3. Refresh the PDF (e.g. by recompiling the LaTeX document)

(You might have to do a forward / inverse search in between to trigger
it.) I'm not "cool enough" to valgrind. But I monitored memory usage
using

ps -o pid,vsz,pmem,pcpu,tty,cmd --sort -pmem,-pcpu -C zathura

After about an hour of work (on a 2 / 3 page paper without any figures)
the memory usage of zathura rises from a footprint of about 1.5% (about
50MB) initially to 20% (about 750MB) by the end of the hour.

This is possibly fixed upstream here:


https://git.pwmt.org/pwmt/zathura/commit/876d35de943b16de7b8a218065a0a7409b383634

Thanks and best,

GI

PS: I marked severity as normal since I didn't know if the correct
section for higher severities. It does make Zathura unusable on my
system though.


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

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

Versions of packages zathura depends on:
ii  libc6 2.19-18+deb8u1
ii  libcairo2 1.14.0-2.1
ii  libgirara-gtk3-1  0.2.3-1
ii  libglib2.0-0  2.42.1-1
ii  libgtk-3-03.14.5-1+deb8u1
ii  libmagic1 1:5.22+15-2
ii  libpoppler-glib8  0.26.5-2
ii  libsqlite3-0  3.8.7.1-1+deb8u1
ii  libsynctex1   2014.20140926.35254-6

zathura recommends no packages.

Versions of packages zathura suggests:
ii  chromium [www-browser]47.0.2526.80-1~deb8u1
ii  google-chrome-beta [www-browser]  48.0.2564.48-1
ii  iceweasel [www-browser]   38.5.0esr-1~deb8u2
ii  konqueror [www-browser]   4:4.14.2-1
ii  poppler-data  0.4.7-1
ii  w3m [www-browser] 0.5.3-19
pn  zathura-cb
ii  zathura-djvu  0.2.4-6
ii  zathura-ps0.2.2-6

-- no debconf information

-- 
A program is a device used to convert data into error messages.

Bug#809982: zathura: Memory leak when PDF is refreshed

[gi1242+debianbugs]

Update: I ran valgrind. Here's the summary:

==13647== LEAK SUMMARY:
==13647==definitely lost: 274,913 bytes in 62 blocks
==13647==indirectly lost: 29,937 bytes in 1,264 blocks
==13647==  possibly lost: 71,528 bytes in 876 blocks
==13647==still reachable: 70,136,419 bytes in 31,730 blocks
==13647== suppressed: 0 bytes in 0 blocks
==13647== Reachable blocks (those to which a pointer was found) are not 
shown.
==13647== To see them, rerun with: --leak-check=full --show-leak-kinds=all

Looks like there definitely is a memory leak which leaks sizable chunks
of memory (not just a KB or two).

GI

-- 
The system requirements said 'Requires Windows 95 or better', so I
bought a Mac.

Bug#809982: zathura: Memory leak when PDF is refreshed

[gi1242+debianbugs]

On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote:

> Otherwise we need a more verbose valgrind log with the GTK+ leaks
> filtered out.

How do I get you this log? If you tell me what I should run on my system
to get you the info you need, I'm happy to do it.

I'll check out the version in testing later today.

Thanks,

GI

-- 
'Altruism' -- That occasional moment when your selfishness benefits
someone else.

Bug#809982: zathura: Memory leak when PDF is refreshed

[gi1242+debianbugs]

On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote:

> I'd recommend to try the new version available in unstable and check
> if the problem still exists.

It appears that the problem is fixed in 0.3.4-1 in testing. (If not,
I'll reopen a separate bug for 0.3.4-1).

The version 0.3.1-2 in Jessie still has the memory leak though.

Best,

Gautam

-- 
'Kleptomaniac' -- One who can't help himself from helping himself.

Bug#809982: closed by Sebastian Ramacher (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

[gi1242+debianbugs]

Please don't close this bug as long as 0.3.1-2 is still the only version
in Jessie! Some unsuspecting Jessie user will get burnt badly!

GI

-- 
One man's folly is another man's wife.

Bug#809982: closed by Sebastian Ramacher (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

[gi1242+debianbugs]

On Fri, Jan 08, 2016 at 10:44:00AM +0100, Sebastian Ramacher wrote:

> The BTS knows about versions and keeps track of them. See the graph on
> the top right of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809982.

Oh I see. Thanks.

Best,

Gautam

-- 
Mathematicians are like Frenchmen: whatever you say to them, they
translate it into their own language, and forthwith it means something
entirely different. -- Goethe

Bug#808640: [Pkg-freeipa-devel] Bug#808640: custodia: FTBFS: Could not find any downloads that satisfy the requirement sphinx<1.3.0

[solo-debianbugs]

On Tue, Dec 29, 2015 at 08:06:06AM +0200, Timo Aaltonen wrote:
> 
> So what's special about this build env compared to normal sbuild, where
> it builds just fine?
> 

The build runs without networking, like the main buildds, and the Ubuntu
buildds.

The Policy requires builds to complete without depending on external
resources, and we implement this by banning networking.  In this case,
it looks like the package is trying to use code from pypi, (i.e. the
binaries included in the package wouldn't be built from the source code
in Debian), which is a serious bug.

Ubuntu buildd:
https://launchpad.net/ubuntu/+source/custodia/0.1.0-2/+build/8184393

Bug#859542: puma: libssl-1.1 supported upstream

[solo-debianbugs]

tags -1 + fixed-upstream
thanks

This is fixed upstream by this commit:
https://github.com/puma/puma/commit/12a856ee63551809ffeb70cb8bfc405d2210febd

Please apply the fix, or package the new version.

Chris.

Bug#858931: isakmpd: Patch

[solo-debianbugs]

Control: tags -1 + patch

The attached patch moves the code over to using the appropriate
accessors for OpenSSL 1.1 in most cases. I have disabled 40-bit
DES, and not ported that code, as the crypto is comically useless
in the modern world.

Chris.
diff --git a/isakmpd-20041012/apps/certpatch/certpatch.c b/isakmpd-20041012/apps/certpatch/certpatch.c
index 0a0125a..a619db6 100644
--- a/isakmpd-20041012/apps/certpatch/certpatch.c
+++ b/isakmpd-20041012/apps/certpatch/certpatch.c
@@ -147,8 +147,6 @@ main (int argc, char **argv)
* EVP_get_digest_byname.
*/
 
-  SSLeay_add_all_algorithms ();
-
   /* Use a certificate created by ssleay and add the appr. extension */
   printf ("Reading ssleay created certificate %s and modify it\n",
 	  certin);
@@ -171,7 +169,7 @@ main (int argc, char **argv)
 }
 
   /* Get the digest for the actual signing */
-  digest = EVP_get_digestbyname (OBJ_nid2sn (OBJ_obj2nid (cert->sig_alg->algorithm)));
+  digest = EVP_get_digestbyname (OBJ_nid2sn (X509_get_signature_nid(cert)));
 
   if (!X509_set_version (cert, 2))
 {
@@ -293,7 +291,7 @@ main (int argc, char **argv)
   BIO_free (file);
 
   printf ("Creating Signature: PKEY_TYPE = %s: ",
-	  pkey_priv->type == EVP_PKEY_RSA ? "RSA" : "unknown");
+   EVP_PKEY_id(pkey_priv) == EVP_PKEY_RSA ? "RSA" : "unknown");
   err = X509_sign (cert, pkey_priv, digest);
   printf ("X509_sign: %d ", err);
   if (!err)
diff --git a/isakmpd-20041012/crypto.c b/isakmpd-20041012/crypto.c
index d74191e..2995119 100644
--- a/isakmpd-20041012/crypto.c
+++ b/isakmpd-20041012/crypto.c
@@ -105,12 +105,13 @@ struct crypto_xf transforms[] = {
 #define DC	(void *)
 #endif
 
+#ifdef USE_DES
 enum cryptoerr
 des1_init(struct keystate *ks, u_int8_t *key, u_int16_t len)
 {
-	/* des_set_key returns -1 for parity problems, and -2 for weak keys */
-	des_set_odd_parity(DC key);
-	switch (des_set_key(DC key, ks->ks_des[0])) {
+	/* DES_set_key returns -1 for parity problems, and -2 for weak keys */
+	DES_set_odd_parity(DC key);
+	switch (DES_set_key(DC key, ks->ks_des[0])) {
 	case -2:
 		return EWEAKKEY;
 	default:
@@ -131,19 +132,20 @@ des1_decrypt(struct keystate *ks, u_int8_t *d, u_int16_t len)
 	des_cbc_encrypt(DC d, DC d, len, ks->ks_des[0], DC ks->riv,
 	DES_DECRYPT);
 }
+#endif
 
 #ifdef USE_TRIPLEDES
 enum cryptoerr
 des3_init(struct keystate *ks, u_int8_t *key, u_int16_t len)
 {
-	des_set_odd_parity(DC key);
-	des_set_odd_parity(DC(key + 8));
-	des_set_odd_parity(DC(key + 16));
+	DES_set_odd_parity(DC key);
+	DES_set_odd_parity(DC(key + 8));
+	DES_set_odd_parity(DC(key + 16));
 
 	/* As of the draft Tripe-DES does not check for weak keys */
-	des_set_key(DC key, ks->ks_des[0]);
-	des_set_key(DC(key + 8), ks->ks_des[1]);
-	des_set_key(DC(key + 16), ks->ks_des[2]);
+	DES_set_key(DC key, ks->ks_des[0]);
+	DES_set_key(DC(key + 8), ks->ks_des[1]);
+	DES_set_key(DC(key + 16), ks->ks_des[2]);
 
 	return EOKAY;
 }
@@ -154,7 +156,7 @@ des3_encrypt(struct keystate *ks, u_int8_t *data, u_int16_t len)
 	u_int8_tiv[MAXBLK];
 
 	memcpy(iv, ks->riv, ks->xf->blocksize);
-	des_ede3_cbc_encrypt(DC data, DC data, len, ks->ks_des[0],
+	DES_ede3_cbc_encrypt(DC data, DC data, len, ks->ks_des[0],
 	ks->ks_des[1], ks->ks_des[2], DC iv, DES_ENCRYPT);
 }
 
@@ -164,7 +166,7 @@ des3_decrypt(struct keystate *ks, u_int8_t *data, u_int16_t len)
 	u_int8_tiv[MAXBLK];
 
 	memcpy(iv, ks->riv, ks->xf->blocksize);
-	des_ede3_cbc_encrypt(DC data, DC data, len, ks->ks_des[0],
+	DES_ede3_cbc_encrypt(DC data, DC data, len, ks->ks_des[0],
 	ks->ks_des[1], ks->ks_des[2], DC iv, DES_DECRYPT);
 }
 #undef DC
diff --git a/isakmpd-20041012/crypto.h b/isakmpd-20041012/crypto.h
index 1095c7e..902c359 100644
--- a/isakmpd-20041012/crypto.h
+++ b/isakmpd-20041012/crypto.h
@@ -108,7 +108,7 @@ struct keystate {
 	u_int8_tiv2[MAXBLK];
 	u_int8_t   *riv, *liv;
 	union {
-		des_key_schedule desks[3];
+		DES_key_schedule *desks[3];
 #ifdef USE_BLOWFISH
 		blf_ctx blfks;
 #endif
diff --git a/isakmpd-20041012/debian/control b/isakmpd-20041012/debian/control
index cc5ddfd..cf3a994 100644
--- a/isakmpd-20041012/debian/control
+++ b/isakmpd-20041012/debian/control
@@ -3,7 +3,7 @@ Maintainer: Jochen Friedrich 
 Priority: optional
 Section: net
 Standards-Version: 3.8.4
-Build-Depends: debhelper (>= 7.0.50~), libssl1.0-dev | libssl-dev (<< 1.1.0~), libgmp-dev, libpcap-dev, linux-kernel-headers
+Build-Depends: debhelper (>= 7.0.50~), libssl-dev, libgmp-dev, libpcap-dev, linux-kernel-headers
 
 Package: isakmpd
 Priority: optional
diff --git a/isakmpd-20041012/sysdep/linux/GNUmakefile.sysdep b/isakmpd-20041012/sysdep/linux/GNUmakefile.sysdep
index 32104ed..4c2edb3 100644
--- a/isakmpd-20041012/sysdep/linux/GNUmakefile.sysdep
+++ b/isakmpd-20041012/sysdep/linux/GNUmakefile.sysdep
@@ -39,7 +39,7 @@ CFLAGS+=	-DHAVE_GETNAMEINFO -DUSE_OLD_SOCKADDR -DHAVE_PCAP \
 		-I/usr/include/openssl
 
 FEATURES=	debug tripledes blowfish cast ec aggressive x509
-FEATURES+=	dpd na

Bug#859227: mixmaster: ssl 1.1 support

[solo-debianbugs]

Control: tags -1 + patch

The attached patch moves the code over to using the openssl 1.1 api. It
is entirely renames / accessors.

Chris.

diff --git a/mixmaster-3.0.0/Src/crypto.c b/mixmaster-3.0.0/Src/crypto.c
index 1025b6d..e860a67 100644
--- a/mixmaster-3.0.0/Src/crypto.c
+++ b/mixmaster-3.0.0/Src/crypto.c
@@ -82,6 +82,7 @@ static int read_seckey(BUFFER *buf, SECKEY *key, const byte id[])
   int len, plen;
   byte *ptr;
   int err = 0;
+  BIGNUM *key_n, *key_e, *key_d, *key_p, *key_q, *key_dmp1, *key_dmq1, *key_iqmp;
 
   md = buf_new();
   bits = buf->data[0] + 256 * buf->data[1];
@@ -94,32 +95,36 @@ static int read_seckey(BUFFER *buf, SECKEY *key, const byte id[])
 
   ptr = buf->data + 2;
 
-  key->n = BN_bin2bn(ptr, len, NULL);
+  key_n = BN_bin2bn(ptr, len, NULL);
   buf_append(md, ptr, len);
   ptr += len;
 
-  key->e = BN_bin2bn(ptr, len, NULL);
+  key_e = BN_bin2bn(ptr, len, NULL);
   buf_append(md, ptr, len);
   ptr += len;
 
-  key->d = BN_bin2bn(ptr, len, NULL);
+  key_d = BN_bin2bn(ptr, len, NULL);
   ptr += len;
 
-  key->p = BN_bin2bn(ptr, plen, NULL);
+  key_p = BN_bin2bn(ptr, plen, NULL);
   ptr += plen;
 
-  key->q = BN_bin2bn(ptr, plen, NULL);
+  key_q = BN_bin2bn(ptr, plen, NULL);
   ptr += plen;
 
-  key->dmp1 = BN_bin2bn(ptr, plen, NULL);
+  key_dmp1 = BN_bin2bn(ptr, plen, NULL);
   ptr += plen;
 
-  key->dmq1 = BN_bin2bn(ptr, plen, NULL);
+  key_dmq1 = BN_bin2bn(ptr, plen, NULL);
   ptr += plen;
 
-  key->iqmp = BN_bin2bn(ptr, plen, NULL);
+  key_iqmp = BN_bin2bn(ptr, plen, NULL);
   ptr += plen;
 
+  RSA_set0_key(key, key_n, key_e, key_d);
+  RSA_set0_factors(key, key_p, key_q);
+  RSA_set0_crt_params(key, key_dmp1, key_dmq1, key_iqmp);
+
   digest_md5(md, md);
   if (id)
 err = (memcmp(id, md->data, 16) == 0) ? 0 : -1;
@@ -134,6 +139,7 @@ static int read_pubkey(BUFFER *buf, PUBKEY *key, const byte id[])
   int len;
   byte *ptr;
   int err = 0;
+  BIGNUM *key_n, *key_e;
 
   md = buf_new();
   bits = buf->data[0] + 256 * buf->data[1];
@@ -144,13 +150,14 @@ static int read_pubkey(BUFFER *buf, PUBKEY *key, const byte id[])
 
   ptr = buf->data + 2;
 
-  key->n = BN_bin2bn(ptr, len, NULL);
+  key_n = BN_bin2bn(ptr, len, NULL);
   buf_append(md, ptr, len);
   ptr += len;
 
-  key->e = BN_bin2bn(ptr, len, NULL);
+  key_e = BN_bin2bn(ptr, len, NULL);
   buf_append(md, ptr, len);
   ptr += len;
+  RSA_set0_key(key, key_n, key_e, NULL);
 
   digest_md5(md, md);
   if (id)
@@ -164,17 +171,22 @@ static int write_seckey(BUFFER *sk, SECKEY *key, byte keyid[])
   byte l[128];
   int n;
   BUFFER *b, *temp;
+  const BIGNUM *key_n, *key_e, *key_d, *key_p, *key_q, *key_dmp1, *key_dmq1, *key_iqmp;
+
+  RSA_get0_key(key, &key_n, &key_e, &key_d);
+  RSA_get0_factors(key, &key_p, &key_q);
+  RSA_get0_crt_params(key, &key_dmp1, &key_dmq1, &key_iqmp);
 
   b = buf_new();
   temp = buf_new();
 
-  n = BN_bn2bin(key->n, l);
+  n = BN_bn2bin(key_n, l);
   assert(n <= 128);
   if (n < 128)
 buf_appendzero(b, 128 - n);
   buf_append(b, l, n);
 
-  n = BN_bn2bin(key->e, l);
+  n = BN_bn2bin(key_e, l);
   assert(n <= 128);
   if (n < 128)
 buf_appendzero(b, 128 - n);
@@ -187,37 +199,37 @@ static int write_seckey(BUFFER *sk, SECKEY *key, byte keyid[])
   buf_appendc(sk, 4);
   buf_cat(sk, b);
 
-  n = BN_bn2bin(key->d, l);
+  n = BN_bn2bin(key_d, l);
   assert(n <= 128);
   if (n < 128)
 buf_appendzero(sk, 128 - n);
   buf_append(sk, l, n);
 
-  n = BN_bn2bin(key->p, l);
+  n = BN_bn2bin(key_p, l);
   assert(n <= 64);
   if (n < 64)
 buf_appendzero(sk, 64 - n);
   buf_append(sk, l, n);
 
-  n = BN_bn2bin(key->q, l);
+  n = BN_bn2bin(key_q, l);
   assert(n <= 64);
   if (n < 64)
 buf_appendzero(sk, 64 - n);
   buf_append(sk, l, n);
 
-  n = BN_bn2bin(key->dmp1, l);
+  n = BN_bn2bin(key_dmp1, l);
   assert(n <= 64);
   if (n < 64)
 buf_appendzero(sk, 64 - n);
   buf_append(sk, l, n);
 
-  n = BN_bn2bin(key->dmq1, l);
+  n = BN_bn2bin(key_dmq1, l);
   assert(n <= 64);
   if (n < 64)
 buf_appendzero(sk, 64 - n);
   buf_append(sk, l, n);
 
-  n = BN_bn2bin(key->iqmp, l);
+  n = BN_bn2bin(key_iqmp, l);
   assert(n <= 64);
   if (n < 64)
 buf_appendzero(sk, 64 - n);
@@ -234,15 +246,17 @@ static int write_pubkey(BUFFER *pk, PUBKEY *key, byte keyid[])
 {
   byte l[128];
   int n;
+  const BIGNUM *key_n, *key_e, *key_d;
 
   buf_appendc(pk, 0);
   buf_appendc(pk, 4);
-  n = BN_bn2bin(key->n, l);
+  RSA_get0_key(key, &key_n, &key_e, &key_d);
+  n = BN_bn2bin(key_n, l);
   assert(n <= 128);
   if (n < 128)
 buf_appendzero(pk, 128 - n);
   buf_append(pk, l, n);
-  n = BN_bn2bin(key->e, l);
+  n = BN_bn2bin(key_e, l);
   assert(n <= 128);
   if (n < 128)
 buf_appendzero(pk, 128 - n);
@@ -383,23 +397,23 @@ int pk_encrypt(BUFFER *in, BUFFER *keybuf)
 }
 int buf_crypt(BUFFER *buf, BUFFER *key, BUFFER *iv, int enc)
 {
-  des_key_schedule ks1;
-  des_key_schedule ks2;
-  des_key_schedule ks3;
-  des_cblock i;
+  DES_key_schedule *ks1;
+  DES_key_schedule *ks2;
+  DES_key_schedule *k

Bug#859549: patch

[solo-debianbugs]

Control: tags -1 + patch

The attached patch fixes the configure script to not check for a removed
symbol. Interestingly, the symbol hasn't really existed for a long, long
time, and its removal isn't even in the changelog; I had to read the
source. `CRYPTO_lock` was its name.

Chris.

commit 324c4c7e78be0e802093294ff24e5d0865fce733
Author: Chris West (Faux) 
Date:   Thu Jun 1 16:36:59 2017 +

check for a symbol that actually exists

diff --git a/partimage-0.6.9/configure.ac b/partimage-0.6.9/configure.ac
index bb2ff61..267a140 100644
--- a/partimage-0.6.9/configure.ac
+++ b/partimage-0.6.9/configure.ac
@@ -240,7 +240,7 @@ if test "$SSL" = "yes"; then
   AC_CHECKING([ for SSL Library and Header files ... ])
   AC_SEARCH_HEADERS(rsa.h crypto.h x509.h pem.h ssl.h err.h,
 $SSL_HDR_DIR /usr/include/ssl /usr/include/openssl /usr/include,
-[  AC_CHECK_LIB(crypto, CRYPTO_lock, [LIBS="$LIBS -lcrypto"],
+[  AC_CHECK_LIB(crypto, CRYPTO_free, [LIBS="$LIBS -lcrypto"],
 AC_MSG_ERROR([ Required for SSL Crypto Library not found. ])
   )
AC_CHECK_LIB(ssl, SSL_CTX_new,
diff --git a/partimage-0.6.9/debian/control b/partimage-0.6.9/debian/control
index 928fc98..441bb9b 100644
--- a/partimage-0.6.9/debian/control
+++ b/partimage-0.6.9/debian/control
@@ -4,13 +4,14 @@ Priority: optional
 Maintainer: Debian QA Group 
 Build-Depends: cdbs,
  debhelper (>= 8),
+ dh-autoreconf,
  autotools-dev,
  libbz2-dev,
  libnewt-dev,
  zlib1g-dev,
  comerr-dev,
  e2fslibs-dev (>= 1.25),
- libssl1.0-dev | libssl-dev (<< 1.1.0~),
+ libssl-dev,
  libpam0g-dev,
  gettext
 Standards-Version: 3.9.8
diff --git a/partimage-0.6.9/debian/rules b/partimage-0.6.9/debian/rules
index bc179ba..39852f6 100755
--- a/partimage-0.6.9/debian/rules
+++ b/partimage-0.6.9/debian/rules
@@ -2,6 +2,7 @@
 
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/autotools.mk
+include /usr/share/cdbs/1/rules/autoreconf.mk
 
 DEB_CONFIGURE_EXTRA_FLAGS := --with-log-dir=/var/log/partimage \
  --with-debug-level=1 \

Bug#851092: patch

[solo-debianbugs]

Control: tags -1 + patch
Control: forwarded -1 https://github.com/boxbackup/boxbackup/issues/16

The above patch changes a single object into a pointer, and changes
init/cleanup into new/free.

Chris.

commit 9d2bf90676206957a502e9ec1c3cfe4f4b40b0cc
Author: Chris West (Faux) 
Date:   Thu Jun 1 17:01:16 2017 +

dynamically allocate EVP_CTX

diff --git a/boxbackup-0.11.1~r2837/debian/control b/boxbackup-0.11.1~r2837/debian/control
index 5cbdba6..d422125 100644
--- a/boxbackup-0.11.1~r2837/debian/control
+++ b/boxbackup-0.11.1~r2837/debian/control
@@ -12,7 +12,7 @@ Build-Depends:
  docbook-xsl,
  libdb-dev (>= 4.7),
  libedit-dev,
- libssl1.0-dev,
+ libssl-dev,
  libtest-lwp-useragent-perl,
  xsltproc,
  zlib1g-dev
diff --git a/boxbackup-0.11.1~r2837/lib/crypto/CipherContext.cpp b/boxbackup-0.11.1~r2837/lib/crypto/CipherContext.cpp
index e5cd9b0..f23317f 100644
--- a/boxbackup-0.11.1~r2837/lib/crypto/CipherContext.cpp
+++ b/boxbackup-0.11.1~r2837/lib/crypto/CipherContext.cpp
@@ -49,7 +49,7 @@ CipherContext::~CipherContext()
 	if(mInitialised)
 	{
 		// Clean up
-		EVP_CIPHER_CTX_cleanup(&ctx);
+		EVP_CIPHER_CTX_free(ctx);
 		mInitialised = false;
 	}
 #ifdef HAVE_OLD_SSL
@@ -84,9 +84,9 @@ void CipherContext::Init(CipherContext::CipherFunction Function, const CipherDes
 	
 	// Initialise the cipher
 #ifndef HAVE_OLD_SSL
-	EVP_CIPHER_CTX_init(&ctx); // no error return code, even though the docs says it does
+	ctx = EVP_CIPHER_CTX_new();
 
-	if(EVP_CipherInit_ex(&ctx, rDescription.GetCipher(), NULL, NULL, NULL, Function) != 1)
+	if(EVP_CipherInit_ex(ctx, rDescription.GetCipher(), NULL, NULL, NULL, Function) != 1)
 #else
 	// Store function for later
 	mFunction = Function;
@@ -102,19 +102,19 @@ void CipherContext::Init(CipherContext::CipherFunction Function, const CipherDes
 	{
 #ifndef HAVE_OLD_SSL
 		// Let the description set up everything else
-		rDescription.SetupParameters(&ctx);
+		rDescription.SetupParameters(ctx);
 #else
 		// With the old version, a copy needs to be taken first.
 		mpDescription = rDescription.Clone();
 		// Mark it as not a leak, otherwise static cipher contexts
 		// cause spurious memory leaks to be reported
 		MEMLEAKFINDER_NOT_A_LEAK(mpDescription);
-		mpDescription->SetupParameters(&ctx);
+		mpDescription->SetupParameters(ctx);
 #endif
 	}
 	catch(...)
 	{
-		EVP_CIPHER_CTX_cleanup(&ctx);
+		EVP_CIPHER_CTX_free(ctx);
 		throw;
 	}
 
@@ -135,7 +135,7 @@ void CipherContext::Reset()
 	if(mInitialised)
 	{
 		// Clean up
-		EVP_CIPHER_CTX_cleanup(&ctx);
+		EVP_CIPHER_CTX_cleanup(ctx);
 		mInitialised = false;
 	}
 #ifdef HAVE_OLD_SSL
@@ -172,7 +172,7 @@ void CipherContext::Begin()
 	}
 
 	// Initialise the cipher context again
-	if(EVP_CipherInit(&ctx, NULL, NULL, NULL, -1) != 1)
+	if(EVP_CipherInit(ctx, NULL, NULL, NULL, -1) != 1)
 	{
 		THROW_EXCEPTION(CipherException, EVPInitFailure)
 	}
@@ -218,14 +218,14 @@ int CipherContext::Transform(void *pOutBuffer, int OutLength, const void *pInBuf
 	}
 	
 	// Check output buffer size
-	if(OutLength < (InLength + EVP_CIPHER_CTX_block_size(&ctx)))
+	if(OutLength < (InLength + EVP_CIPHER_CTX_block_size(ctx)))
 	{
 		THROW_EXCEPTION(CipherException, OutputBufferTooSmall);
 	}
 	
 	// Do the transform
 	int outLength = OutLength;
-	if(EVP_CipherUpdate(&ctx, (unsigned char*)pOutBuffer, &outLength, (unsigned char*)pInBuffer, InLength) != 1)
+	if(EVP_CipherUpdate(ctx, (unsigned char*)pOutBuffer, &outLength, (unsigned char*)pInBuffer, InLength) != 1)
 	{
 		THROW_EXCEPTION(CipherException, EVPUpdateFailure)
 	}
@@ -265,7 +265,7 @@ int CipherContext::Final(void *pOutBuffer, int OutLength)
 	}
 
 	// Check output buffer size
-	if(OutLength < (2 * EVP_CIPHER_CTX_block_size(&ctx)))
+	if(OutLength < (2 * EVP_CIPHER_CTX_block_size(ctx)))
 	{
 		THROW_EXCEPTION(CipherException, OutputBufferTooSmall);
 	}
@@ -273,7 +273,7 @@ int CipherContext::Final(void *pOutBuffer, int OutLength)
 	// Do the transform
 	int outLength = OutLength;
 #ifndef HAVE_OLD_SSL
-	if(EVP_CipherFinal_ex(&ctx, (unsigned char*)pOutBuffer, &outLength) != 1)
+	if(EVP_CipherFinal_ex(ctx, (unsigned char*)pOutBuffer, &outLength) != 1)
 	{
 		THROW_EXCEPTION(CipherException, EVPFinalFailure)
 	}
@@ -302,11 +302,11 @@ void CipherContext::OldOpenSSLFinal(unsigned char *Buffer, int &rOutLengthOut)
 	// Old version needs to use a different form, and then set up the cipher again for next time around
 	int outLength = rOutLengthOut;
 	// Have to emulate padding off...
-	int blockSize = EVP_CIPHER_CTX_block_size(&ctx);
+	int blockSize = EVP_CIPHER_CTX_block_size(ctx);
 	if(mPaddingOn)
 	{
 		// Just use normal final call
-		if(EVP_CipherFinal(&ctx, Buffer, &outLength) != 1)
+		if(EVP_CipherFinal(ctx, Buffer, &outLength) != 1)
 		{
 			THROW_EXCEPTION(CipherException, EVPFinalFailure)
 		}
@@ -319,13 +319,13 @@ void CipherContext::OldOpenSSLFinal(unsigned char *Buffer, int &rOutLengthOut)
 		{
 			// NASTY -- fiddling around with internals like this is bad.
 			// But only way to get this w

Bug#851092: upstream

[solo-debianbugs]

Upstream have committed a better version of the patch for their latest
version, which also fixes a load of deprecation warnings:

https://github.com/boxbackup/boxbackup/commit/edd3687f067c68b131822e0064cdeff5bf7a3835

Bug#828413: fixed upstream

[solo-debianbugs]

Control: tags -1 + fixed-upstream

Upstream have resolved the issues, e.g. in
cf1e808e2ffa1f26644fb5d2cb82a919f323deba.

Packaging the newer tag (0.7.5) should pick up the fixes.

Bug#866908: doclint still haunts us

[solo-debianbugs]

Control: reopen -1
Control: found 9~b181-2

The shipped javadoc command in 9~b181-2 still complains, as this bug
report mentions; the testcase above still fails.

I believe the patch, while updated, is not being applied:
https://sources.debian.net/src/openjdk-9/9~b181-2/debian/rules/#L393

Please save us from this evil!

Chris.

Bug#872797: RM? Abandoned upstream in 2004, FTBFS with openjdk-9, few rdeps

[solo-debianbugs]

Source: avalon-framework
Priority: wishlist

Could we RM this package? It was officially abandoned by upstream in
2004[1]. There was an upload to Maven Central in 2007, but it doesn't
seem to have gone through source control: the last commit was in 2004.
It FTBFS with openjdk-9, will require the source patching.

The reverse depends (in sid, today) are:

 * libfop-java (>= 1:2.1-7)

As fop is really popular, the popcon of libavalon-framework-java is
very artificially inflated. It is in the build-deps of nearly everything.

fop depends on only the configuration parser (and, in test, logging), which
I am trying to get upstream to remove[2], and have a patch for HEAD[3].

 * jmeter (2.13-3)
 * libexcalibur-logger-java (2.1-6)

jmeter upstream (3.2) has moved off this logging framework to slf4j,
dropping the dependency on avalon-framework. The logging framework has
no other rdeps, so could also be removed.

 * libtrang-java (20131210+dfsg+1-6)

libtrang upstream have also removed references to avalon-framework.

 * libjaxe-java (3.5-8)

Part of the "jaxe" XML editor, dead upstream. I'm going to have a look
at fixing it.

 * scilab-full-bin (5.5.2-5)

Pretty sure this doesn't actually depend on avalon-framework at all;
looks like it's just trying to pull it in to fix fop? I'm not entirely
sure, hard to test without rebuilding Debian's fop without avalon.


Thanks,
Chris.

1: https://avalon.apache.org/closed.html
2: https://issues.apache.org/jira/browse/FOP-2733
3: https://github.com/apache/fop/compare/trunk...FauxFaux:trunk

Bug#872797: jaxe also seems to just be trying to fix fop

[solo-debianbugs]

jaxe also seems to just trying to fix fop problems; i.e. it has no real
dependence on avalon as far as I can see. Again, hard to test without
trying a rebuild of a fixed fop.

Chris.

Bug#872945: FTBFS with openjdk-9-jdk

[solo-debianbugs]

Source: dicomscope
Priority: normal

This package fails to build against openjdk-9, for which there should
soon be a transition.

The changes look like they should be easy to fix:

error: [options] source value 1.5 is obsolete and will be removed in a future 
release
error: [options] target value 1.5 is obsolete and will be removed in a future 
release

These are literally true; -source/-target 1.6 or higher must be passed.

And:

./processCommunication/ProcessTable.java:216: error: incompatible types: Object 
cannot be converted to Vector
dataVector.setElementAt(dummy, row2);
^
./viewer/sr/VerificationDialog.java:294: error: incompatible types: Object 
cannot be converted to Vector
dataVector.setElementAt(dummy, row2);
^

These are normally caused by swing having gained generics for
methods that previously accepted raw types, and can be fixed by
adding wildcards (in a way that doesn't break compilation on
Java 8).


Cheers,
Chris.

Bug#872946: FTBFS with openjdk-9

[solo-debianbugs]

Source: charactermanaj
Priority: normal

This package fails to build with Java 9, for which there will hopefully
soon be a transition. Please fix it.

Build log excerpt:

/build/charactermanaj-0.998+git20150728.a826ad85/src/charactermanaj/ui/util/SpinnerWheelSupportListener.java:53:
 error: incompatible types: Comparable cannot be converted to 
Comparable
Comparable max = nmodel.getMaximum();
  ^
  where CAP#1 is a fresh type-variable:
CAP#1 extends Object from capture of ?
/build/charactermanaj-0.998+git20150728.a826ad85/src/charactermanaj/ui/util/SpinnerWheelSupportListener.java:55:
 error: incompatible types: Comparable cannot be converted to 
Comparable
Comparable min = nmodel.getMinimum();
  ^
  where CAP#1 is a fresh type-variable:
CAP#1 extends Object from capture of ?

These errors are normally because javax.swing classes have gained some
generics, where previously they had raw types. Some extra  wildcards,
or generics, may be required.


Cheers,
Chris.

Bug#873021: RM? FTBFS with openjdk-9, outdated, no rdeps

[solo-debianbugs]

Source: ha-jdbc
Priority: wishlist

This library package has no rdeps, is a release-candidate version from
2009, there are new major versions upstream. The currently packaged
version fails to build with the current openjdk-9-jdk betas.

Can we remove it?

Cheers,
Chris.

Bug#873030: RM? Superseded by Java 7, abandoned upstream, FTBFS on 9, 1 rdep

[solo-debianbugs]

Source: jpathwatch
Priority: wishlist

Can we RM this package?

It fails to build on Java 9.

It has been abandoned by upstream in 2012, as Java 7 provides the
functionality without all the hacks.

It has one rdep: eclipse-pydev, which uses it only at build time, for a
single test, I believe. eclipse-pydev-data seems to be ending up with
it as an actual depends, but I hope that's a bug.

Chris.

Bug#698240: build-rdeps also fails with lz4'd sources

[solo-debianbugs]

Control: severity -1 important

build-rdeps also fails with lz4'd sources, which appears to have become
the default in sid at some point? It's the case in the "official"
debian:sid Docker images, without any config I can see set.

As the tool is broken on a default install, without me having changed
any configuration, this bug is Important.

Chris.

Bug#873249: FTBFS with Java 9: javadoc classpath with maven?

[solo-debianbugs]

On Sat, Aug 26, 2017 at 12:25:16PM +0200, Emmanuel Bourg wrote:
> With Java 8 a warning was displayed, but with Java 9 it's now
> an error. The only workaround I've found besides fixing the classpath is
>
> Do you know how many packages are affected by this issue?

I'd guess ~4 of the ~50 I looked at, so maybe 30 packages total? I can't
grep up a better answer as many packages fail their build before getting
to the javadoc generation.

This one specifically is weird as it's maven, and maven is probably
supposed to be using the same classpath for the build as for the javadoc
generation. And the main build has succeeded, or we wouldn't be here.

Bug#859784: ssl 1.1 fix

[solo-debianbugs]

Control: tags -1 + patch
Control: forwarded https://github.com/tobez/validns/pull/64

A patch to fix compilation with openssl 1.1 is attached.
The patch doesn't apply cleanly to upstream, so I sent them a different
patch.

Chris.

diff --git a/validns-0.8+git20160720/debian/control b/validns-0.8+git20160720/debian/control
index 3714846..d31cb26 100644
--- a/validns-0.8+git20160720/debian/control
+++ b/validns-0.8+git20160720/debian/control
@@ -3,7 +3,7 @@ Section: net
 Priority: extra
 Maintainer: Casper Gielen 
 Uploaders: Joost van Baal-Ilić 
-Build-Depends: debhelper (>= 9), libssl1.0-dev, libjudy-dev, libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
+Build-Depends: debhelper (>= 9), libssl-dev, libjudy-dev, libtest-command-simple-perl, dpkg-dev (>= 1.16.1~)
 Standards-Version: 3.9.8
 Homepage: http://www.validns.net/
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/validns.git
diff --git a/validns-0.8+git20160720/dnskey.c b/validns-0.8+git20160720/dnskey.c
index fecc62a..14f2cc2 100644
--- a/validns-0.8+git20160720/dnskey.c
+++ b/validns-0.8+git20160720/dnskey.c
@@ -154,6 +154,7 @@ int dnskey_build_pkey(struct rr_dnskey *rr)
unsigned int e_bytes;
unsigned char *pk;
int l;
+   BIGNUM *n, *e;
 
rsa = RSA_new();
if (!rsa)
@@ -174,11 +175,12 @@ int dnskey_build_pkey(struct rr_dnskey *rr)
if (l < e_bytes) /* public key is too short */
goto done;
 
-   rsa->e = BN_bin2bn(pk, e_bytes, NULL);
+   e = BN_bin2bn(pk, e_bytes, NULL);
pk += e_bytes;
l -= e_bytes;
 
-   rsa->n = BN_bin2bn(pk, l, NULL);
+   n = BN_bin2bn(pk, l, NULL);
+   RSA_set0_key(rsa, n, e, NULL);
 
pkey = EVP_PKEY_new();
if (!pkey)
diff --git a/validns-0.8+git20160720/nsec3checks.c b/validns-0.8+git20160720/nsec3checks.c
index 69c6553..97be1ce 100644
--- a/validns-0.8+git20160720/nsec3checks.c
+++ b/validns-0.8+git20160720/nsec3checks.c
@@ -28,7 +28,7 @@
 static struct binary_data name2hash(char *name, struct rr *param)
 {
 struct rr_nsec3param *p = (struct rr_nsec3param *)param;
-   EVP_MD_CTX ctx;
+   EVP_MD_CTX *ctx;
unsigned char md0[EVP_MAX_MD_SIZE];
unsigned char md1[EVP_MAX_MD_SIZE];
unsigned char *md[2];
@@ -45,22 +45,23 @@ static struct binary_data name2hash(char *name, struct rr *param)
 
/* XXX Maybe use Init_ex and Final_ex for speed? */
 
-   EVP_MD_CTX_init(&ctx);
-   if (EVP_DigestInit(&ctx, EVP_sha1()) != 1)
+   ctx = EVP_MD_CTX_new();
+   if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
return r;
-   digest_size = EVP_MD_CTX_size(&ctx);
-   EVP_DigestUpdate(&ctx, wire_name.data, wire_name.length);
-   EVP_DigestUpdate(&ctx, p->salt.data, p->salt.length);
-   EVP_DigestFinal(&ctx, md[mdi], NULL);
+   digest_size = EVP_MD_CTX_size(ctx);
+   EVP_DigestUpdate(ctx, wire_name.data, wire_name.length);
+   EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
+   EVP_DigestFinal(ctx, md[mdi], NULL);
 
for (i = 0; i < p->iterations; i++) {
-   if (EVP_DigestInit(&ctx, EVP_sha1()) != 1)
+   if (EVP_DigestInit(ctx, EVP_sha1()) != 1)
return r;
-   EVP_DigestUpdate(&ctx, md[mdi], digest_size);
+   EVP_DigestUpdate(ctx, md[mdi], digest_size);
mdi = (mdi + 1) % 2;
-   EVP_DigestUpdate(&ctx, p->salt.data, p->salt.length);
-   EVP_DigestFinal(&ctx, md[mdi], NULL);
+   EVP_DigestUpdate(ctx, p->salt.data, p->salt.length);
+   EVP_DigestFinal(ctx, md[mdi], NULL);
}
+   EVP_MD_CTX_free(ctx);
 
r.length = digest_size;
r.data = getmem(digest_size);
diff --git a/validns-0.8+git20160720/rrsig.c b/validns-0.8+git20160720/rrsig.c
index 81f24b4..d6ea0c5 100644
--- a/validns-0.8+git20160720/rrsig.c
+++ b/validns-0.8+git20160720/rrsig.c
@@ -26,7 +26,7 @@
 struct verification_data
 {
struct verification_data *next;
-   EVP_MD_CTX ctx;
+   EVP_MD_CTX *ctx;
struct rr_dnskey *key;
struct rr_rrsig *rr;
int ok;
@@ -180,7 +180,7 @@ void *verification_thread(void *dummy)
if (d) {
int r;
d->next = NULL;
-   r = EVP_VerifyFinal(&d->ctx, (unsigned char *)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
+   r = EVP_VerifyFinal(d->ctx, (unsigned char *)d->rr->signature.data, d->rr->signature.length, d->key->pkey);
if (r == 1) {
d->ok = 1;
} else {
@@ -232,7 +232,7 @@ static void schedule_verification(struct verification_data *d)
} else {
int r;
G.stats.signatures_verified+

Bug#859717: Skipfish uses deleted openssl functionality

[solo-debianbugs]

One of the failures here is using SSL_CIPHER->algo_strength,
which has been removed with, as far as I can see, no replacement.

I've raised a bug against OpenSSL upstream to consider exposing this:
https://github.com/openssl/openssl/issues/3795

Chris.

Bug#850890: patch

[solo-debianbugs]

Control: tags -1 + patch

Attached is a trivial patch which fixes the build on OpenSSL 1.1.

Chris.
diff --git a/opennebula-4.12.3+dfsg/debian/control b/opennebula-4.12.3+dfsg/debian/control
index 5cd7e8e..df9dc68 100644
--- a/opennebula-4.12.3+dfsg/debian/control
+++ b/opennebula-4.12.3+dfsg/debian/control
@@ -11,7 +11,7 @@ Build-Depends: debhelper (>= 9), dh-systemd, dh-linktree, javahelper
   ,flex
   ,libmysql++-dev
   ,libsqlite3-dev
-  ,libssl1.0-dev
+  ,libssl-dev
   ,libws-commons-util-java
   ,libxml2-dev
   ,libxmlrpc-c++8-dev
diff --git a/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc b/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
index 90a0a17..f528998 100644
--- a/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
+++ b/opennebula-4.12.3+dfsg/src/common/NebulaUtil.cc
@@ -154,18 +154,18 @@ string * one_util::base64_decode(const string& in)
 
 string one_util::sha1_digest(const string& in)
 {
-EVP_MD_CTX mdctx;
+EVP_MD_CTX *mdctx;
 unsigned char  md_value[EVP_MAX_MD_SIZE];
 unsigned int   md_len;
 ostringstream  oss;
 
-EVP_MD_CTX_init(&mdctx);
-EVP_DigestInit_ex(&mdctx, EVP_sha1(), NULL);
+mdctx = EVP_MD_CTX_new();
+EVP_DigestInit_ex(mdctx, EVP_sha1(), NULL);
 
-EVP_DigestUpdate(&mdctx, in.c_str(), in.length());
+EVP_DigestUpdate(mdctx, in.c_str(), in.length());
 
-EVP_DigestFinal_ex(&mdctx,md_value,&md_len);
-EVP_MD_CTX_cleanup(&mdctx);
+EVP_DigestFinal_ex(mdctx,md_value,&md_len);
+EVP_MD_CTX_free(mdctx);
 
 for(unsigned int i = 0; i

Bug#851069: Builds fine with modern libssl

[solo-debianbugs]

This package builds fine, and all the tests pass fine, with modern
libssl.

The version dependence on older versions has been there since
the package was first uploaded; I am unable to work out why it was
added: maybe a dependent library which has now been fixed?

All that's necessary to close this bug is to change the debian/control
dependence to the current version.

Chris.

Bug#863568: ..and of course I forgot the attachment

[solo-debianbugs]

diff --git a/cfengine3-3.9.1/cf-key/cf-key-functions.c b/cfengine3-3.9.1/cf-key/cf-key-functions.c
index 7c53ee5..5287b2c 100644
--- a/cfengine3-3.9.1/cf-key/cf-key-functions.c
+++ b/cfengine3-3.9.1/cf-key/cf-key-functions.c
@@ -48,6 +48,7 @@ RSA *LoadPublicKey(const char *filename)
 {
 FILE *fp;
 RSA *key;
+const BIGNUM *n, *e;
 
 fp = safe_fopen(filename, "r");
 if (fp == NULL)
@@ -69,7 +70,9 @@ RSA *LoadPublicKey(const char *filename)
 
 fclose(fp);
 
-if (BN_num_bits(key->e) < 2 || !BN_is_odd(key->e))
+RSA_get0_key(key, &n, &e, NULL);
+
+if (BN_num_bits(e) < 2 || !BN_is_odd(e))
 {
 Log(LOG_LEVEL_ERR, "Error while reading public key '%s' - RSA Exponent is too small or not odd. (BN_num_bits: %s)",
 filename, GetErrorStr());
diff --git a/cfengine3-3.9.1/cf-serverd/server_classic.c b/cfengine3-3.9.1/cf-serverd/server_classic.c
index 5e610da..f50dc01 100644
--- a/cfengine3-3.9.1/cf-serverd/server_classic.c
+++ b/cfengine3-3.9.1/cf-serverd/server_classic.c
@@ -569,6 +569,7 @@ static void SetConnectionData(ServerConnectionState *conn, char *buf)
 static int CheckStoreKey(ServerConnectionState *conn, RSA *key)
 {
 RSA *savedkey;
+const BIGNUM *key_n, *key_e, *savedkey_n, *savedkey_e;
 
 const char *udigest = KeyPrintableHash(ConnectionInfoKey(conn->conn_info));
 assert(udigest != NULL);
@@ -579,7 +580,10 @@ static int CheckStoreKey(ServerConnectionState *conn, RSA *key)
 "A public key was already known from %s/%s - no trust required",
 conn->hostname, conn->ipaddr);
 
-if ((BN_cmp(savedkey->e, key->e) == 0) && (BN_cmp(savedkey->n, key->n) == 0))
+RSA_get0_key(key, &key_n, &key_e, NULL);
+RSA_get0_key(savedkey, &savedkey_n, &savedkey_e, NULL);
+
+if ((BN_cmp(savedkey_e, key_e) == 0) && (BN_cmp(savedkey_n, key_n) == 0))
 {
 Log(LOG_LEVEL_VERBOSE,
 "The public key identity was confirmed as %s@%s",
@@ -772,6 +776,7 @@ char iscrypt, enterprise_field;
 
 /* proposition C2 - Receive client's public key modulus */
 RSA *newkey = RSA_new();
+BIGNUM *newkey_n, *newkey_e;
 {
 
 int len_n = ReceiveTransaction(conn->conn_info, recvbuffer, NULL);
@@ -783,7 +788,7 @@ RSA *newkey = RSA_new();
 return false;
 }
 
-if ((newkey->n = BN_mpi2bn(recvbuffer, len_n, NULL)) == NULL)
+if ((newkey_n = BN_mpi2bn(recvbuffer, len_n, NULL)) == NULL)
 {
 Log(LOG_LEVEL_ERR, "Authentication failure: "
 "private decrypt of received public key modulus failed "
@@ -804,16 +809,19 @@ RSA *newkey = RSA_new();
 return false;
 }
 
-if ((newkey->e = BN_mpi2bn(recvbuffer, len_e, NULL)) == NULL)
+if ((newkey_e = BN_mpi2bn(recvbuffer, len_e, NULL)) == NULL)
 {
 Log(LOG_LEVEL_ERR, "Authentication failure: "
 "private decrypt of received public key exponent failed "
 "(%s)", CryptoLastErrorString());
+BN_free(newkey_n);
 RSA_free(newkey);
 return false;
 }
 }
 
+RSA_set0_key(newkey, newkey_n, newkey_e, NULL);
+
 /* Compute and store hash of the client's public key. */
 {
 Key *key = KeyNew(newkey, CF_DEFAULT_DIGEST);
@@ -891,18 +899,21 @@ RSA *newkey = RSA_new();
 
 /* proposition S4, S5 - If the client doesn't have our public key, send it. */
 {
+const BIGNUM *n, *e;
 if (iscrypt != 'y')
 {
 Log(LOG_LEVEL_DEBUG, "Sending server's public key");
 
 char bignum_buf[CF_BUFSIZE] = { 0 };
 
+RSA_get0_key(PUBKEY, &n, &e, NULL);
+
 /* proposition S4  - conditional */
-int len_n = BN_bn2mpi(PUBKEY->n, bignum_buf);
+int len_n = BN_bn2mpi(n, bignum_buf);
 SendTransaction(conn->conn_info, bignum_buf, len_n, CF_DONE);
 
 /* proposition S5  - conditional */
-int len_e = BN_bn2mpi(PUBKEY->e, bignum_buf);
+int len_e = BN_bn2mpi(e, bignum_buf);
 SendTransaction(conn->conn_info, bignum_buf, len_e, CF_DONE);
 }
 }
diff --git a/cfengine3-3.9.1/cf-serverd/server_common.c b/cfengine3-3.9.1/cf-serverd/server_common.c
index 64e04a4..e4e01e2 100644
--- a/cfengine3-3.9.1/cf-serverd/server_common.c
+++ b/cfengine3-3.9.1/cf-serverd/server_common.c
@@ -557,7 +557,7 @@ void CfEncryptGetFile(ServerFileGetState *args)
 unsigned char iv[32] =
 { 1, 2, 3, 4, 5, 6, 7, 8, 1, 2, 3, 4, 5, 6, 7, 8, 1, 2, 3, 4, 5, 6, 7, 8, 1, 2, 3, 4, 5, 6, 7, 8 };
 int blocksize = CF_BUFSIZE - 4 * CF_INBAND_OFFSET;
-EVP_CIPHER_CTX ctx;
+EVP_CIPHER_CTX *ctx = EVP_CIPHER_CTX_new();
 char *key, enctype;
 struct stat sb;
 ConnectionInfo *conn_info = args->conn->conn_info;
@@ -581,7 +581,7 @@ void CfEncryptGetFile(ServerFileGetState *args)
 FailedTransfer(conn_info);
 }
 
-EVP_CIPHER_CTX_init(&ctx);
+EVP_CIPHER_CTX_init(ctx);
 
 if ((fd = safe_open(filename, O_RDONLY)) == -1)
 {
@@ -630,20 +630,20 @@ void CfEncryptGetFile(ServerFileGetState *args)
 
  

Bug#859053: trivial compilation fix

[solo-debianbugs]

Control: tags -1 + patch

The attached trivial patch fixes compilation in my sid chroot.

Chris.

diff --git a/libofetion-2.2.2/debian/control b/libofetion-2.2.2/debian/control
index 64a8b55..279cd46 100644
--- a/libofetion-2.2.2/debian/control
+++ b/libofetion-2.2.2/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Debian Chinese Team 
 DM-Upload-Allowed: yes
 Uploaders: Aron Xu , Asias He  
-Build-Depends: debhelper (>= 7), cmake, libxml2-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), libsqlite3-dev, pkg-config
+Build-Depends: debhelper (>= 7), cmake, libxml2-dev, libssl-dev, libsqlite3-dev, pkg-config
 Standards-Version: 3.9.2
 Homepage: http://code.google.com/p/ofetion/
 
diff --git a/libofetion-2.2.2/fetion_login.c b/libofetion-2.2.2/fetion_login.c
index 6cdcc1c..457cdc7 100644
--- a/libofetion-2.2.2/fetion_login.c
+++ b/libofetion-2.2.2/fetion_login.c
@@ -85,7 +85,7 @@ char* generate_response(const char *nouce, const char *userid,
 	bne = BN_new();
 	BN_hex2bn(&bnn, modulus);
 	BN_hex2bn(&bne, exponent);
-	r->n = bnn;	r->e = bne;	r->d = NULL;
+	RSA_set0_key(r, bnn, bne, NULL);
 //	RSA_print_fp(stdout, r, 5);
 	flen = RSA_size(r);
 	out =  (unsigned char*)malloc(flen);

Bug#858939: fixed upstream

[solo-debianbugs]

Control: tags -1 + fixed-upstream

Upstream have added support for building against either SSL api:
https://github.com/jorisvink/kore/commit/95daf3a62bef0b9c84101eecbb464fd474566f45

Chris.

Bug#859551: fixed upstream

[solo-debianbugs]

Control: tags -1 + fixed-upstream

pgbouncer contains an embedded copy of libusual, where the problems
appear to lie. Upstream have picked up an updated embedded copy of
libusual[1], and now builds fine.

The libusual fixes are pretty spread out, e.g.
https://github.com/libusual/libusual/commit/1c7798405869bb56e9c055dcf1f115b409f82ed1
https://github.com/libusual/libusual/commit/0e56f729d74e4af6c19fe60f6e2b47f5e717dcac

Doesn't seem worth trying to backport them?


Chris.

1: 
https://github.com/pgbouncer/pgbouncer/commit/2a064d04b346f3496f82682ffe997c3bca7d5f67

Bug#859960: gcj-jdk: dh_javadoc: please add -notimestamp to invocation

[solo-debianbugs]

The bug is not really in gcj, it's in a script in gcc-defaults, which
ends up in the binary named gcj-jdk for some bizarre reason.

However, I've just been looking further, and it looks like the script is
literally only used by jaminid, and that jaminid looks pretty abandoned
upstream, and has no deps or rdeps, and the maintainer is idle. So maybe
both can be removed, and the archive can be a better place.

https://codesearch.debian.net/search?q=dh_javadoc+path%3Adebian%2Frules

Bug#860098: writer2latex: please make the javadoc build reproducible

[solo-debianbugs]

Source: writer2latex
Version: 1.4-1
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
Priority: wishlist

The javadoc in writer2latex contains timestamps, which prevent the
package from building reproducibly. Please pass the -notimestamp
argument to javadoc. This can be done by adding:



..to the "javadocs" https://sources.debian.net/src/writer2latex/1.4-1/build.xml/#L298

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/writer2latex.html

Cheers.

Bug#848947: bibtool: [Regression] Empty separators cause errors

[gi1242+debianbugs]

On Wed, Dec 21, 2016 at 04:34:43AM +, Jerome BENOIT wrote:

> Can you send a minimal material (sample(s) + procedure) that reproduce
> the issue ?

Dear Jerome,

Thanks for your quick response, and apologies for not being more
explicit.

I'm attaching a minimal bib file and rsc file to reproduce the problem.
Running

bibtool -r bibtoolrsc < test.bib

produces

*** BibTool ERROR: Invalid separator specification.

@Book{Adams.Fournier,
  author= {Adams, Robert A. and Fournier, John J. F.}
}

With earlier versions it used to produce

@Book{AdamsFournier,
  author= {Adams, Robert A. and Fournier, John J. F.}
}

(i.e. the key is supposed to be "AdamsFournier" and not
"Adams.Fournier")

Best,

GI

-- 
Birthdays are good for health. Studies show that people who have more
birthdays live longer.
fmt.name.name = {}
key.format = {%2n(author)}
@Book{		  AdamsFournier03,
  author	= {Adams, Robert A. and Fournier, John J. F.},
}

Bug#842635: Incorrect output on i386 due to UB

[solo-debianbugs]

Package: docbook-to-man
User: reproducible-bui...@lists.alioth.debian.org
Usertags: toolchain
Version: 1:2.0.0-35
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

On i386 (but not armhf or amd64), docbook-to-man inserts random
characters into the output.

e.g. it will sometimes generate an "I" instead of a literal tab.

I chased the bug around the code, and it looks like /usr/bin/instant has
some UB in main.c:

https://sources.debian.net/src/docbook-to-man/1:2.0.0-35/Instant/main.c/#L799

memcpy(&buf[1], &buf[2], strlen(buf)-1);

.. for bufs like " n\\011". The resulting buf contains \111, which maps
to capital I, eventually. Cool coincidence, eh.

Patch (for this case!) is simply s/memcpy/memmove/, but I doubt this is
the only case where this can happen.

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

[gi1242+debianbugs]

Hi There,

I think this is a bug with pinentry-gtk-2. Running it almost always
results in the following warning:

$ echo getpin | pinentry-gtk-2
OK Pleased to meet you

** (pinentry-gtk-2:28067): WARNING **: it took 32 tries to grab the keyboard
D this is a test
OK

Sometimes it (erratically) fails outright as follows:

$ echo getpin | pinentry-gtk-2
OK Pleased to meet you

** (pinentry-gtk-2:28071): WARNING **: it took 38 tries to grab the keyboard

** (pinentry-gtk-2:28071): CRITICAL **: could not grab pointer: already 
grabbed (1)
ERR 83886179 Operation cancelled 

If I replace pinentry-gtk-2 with pinentry-qt or pinentry-curses I don't
get any such warning anymore. (For pinentry-curses I have to type
getpin, and redirect the stdin, of course.)

It may or may not be related to the fact that I'm running under fvwm,
and not a standard desktop environment.

GI

-- 
Did you hear about the blonde who threw away her weight loss video? She
noticed that the people on the video weren't losing weight either!

Bug#848947: closed by Jerome Benoit (Bug#848947: fixed in bibtool 2.66+ds-2)

[gi1242+debianbugs]

Thanks! I confirm it's fixed on my system with the update.

GI

-- 
File not found. Should I fake it? (Y/N)

Bug#1066957: dependency not satisfiable in bookworm-backports

[debianbugs . document346]

Same problem!

At the moment, is not possible to update to the stable-backports version of 
Grub2 for amd64 (2.12-1~bpo12+1), because APT would require removing 
grub-efi-amd64-signed (1+2.06+13+deb12u1), which would then make the system 
unbootable with Secure Boot enabled.
I suppose a backport of grub-efi-amd64-signed (1+2.12+1) from Trixie might 
solve this...

Bug#502346: virtualbox-ose-modules-* need to be rebuilt

[vagrant+debianbugs]

reopen 502539
merge 502539 502346
thanks

these bugs should have been merged (502539 was closed without
explanation).

live well,
  vagrant



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#490596: approx: cannot download Release or Packages files

[vagrant+debianbugs]

On Sat, Jul 12, 2008 at 08:33:03PM -0400, Eric Cooper wrote:
> > it's transparently being proxied through squid, and i'm wondering if
> > that's somehow messing with it, although until yesterday (the last time
> > it worked), it was working with the identical squid configuration. the
> > same mirrors are accessible if put in sources.list directly and using
> > the squid proxy.
> 
> Please try the same "curl" commands that approx is using and let me
> know if there's any more information about why they are failing.
> They're in the log:
> 
> > Jul 12 15:50:47 hobo approx: Command: /usr/bin/curl --fail --silent  
> > --include "http://debian.osuosl.org/debian/dists/lenny/Release";
> > Jul 12 15:50:48 hobo approx: Command: /usr/bin/curl --fail --silent  
> > --include 
> > "http://debian.osuosl.org/debian/dists/lenny/main/binary-i386/Packages.gz";
> > Jul 12 15:50:48 hobo approx: Command: /usr/bin/curl --fail --silent  
> > --include 
> > "http://debian.osuosl.org/debian/dists/sid/main/binary-i386/Packages.gz";
> 
> (Even if they succeed, please send me the output.  Approx expects some
> headers as a result of the "--include" option; maybe the squid setup
> is breaking its assumptions.)

all silently fail. dropping the --silent option:

 /usr/bin/curl --fail   --include 
"http://debian.osuosl.org/debian/dists/lenny/Release";
 curl: (6) Could not resolve host: debian.osuosl.org (DNS server returned 
answer with no data)

which sounds similar to debian bug #478864, possibly.

 host debian.osuosl.org
 debian.osuosl.org has address 140.211.166.134
 debian.osuosl.org is an alias for ftp.osuosl.org.
 debian.osuosl.org is an alias for ftp.osuosl.org.
 
so, i switched to ftp.osuosl.org, and it seems to work fine:

 /usr/bin/curl --fail   --include 
"http://ftp.osuosl.org/debian/dists/lenny/Release";
 HTTP/1.0 200 OK
 Date: Mon, 14 Jul 2008 00:38:57 GMT
 Server: Apache
 Last-Modified: Sun, 13 Jul 2008 20:55:59 GMT
 ETag: "7d40a7c-122d1-451ee007b75c0"
 Accept-Ranges: bytes
 Content-Length: 74449
 Content-Type: text/plain
 X-Cache: MISS from tentacle.fglan
 X-Cache-Lookup: MISS from tentacle.fglan:3128
 Via: 1.0 tentacle.fglan:3128 (squid/2.6.STABLE5)
 Connection: close
 
 Origin: Debian
 Label: Debian
 Suite: testing
 Codename: lenny
 Date: Sun, 13 Jul 2008 20:54:51 UTC
 Architectures: alpha amd64 arm armel hppa i386 ia64 mips mipsel powerpc
 s390 sparc
 Components: main contrib non-free
 Description: Debian x.y Testing distribution - Not Released
 MD5Sum:
  79fe3caaa475eace9b3a6a88319531ac 23080247 main/binary-alpha/Packages
  d58ce0efbcb976641afbcab306a2bd55  6613328 main/binary-alpha/Packages.gz
 

so maybe there's something wrong with handling of CNAMEs ?

thanks!

live well,
  vagrant 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#462292: gjdoc: fails to upgrade/remove/install when /proc is not mounted

[vagrant+debianbugs]

retitle 462292 gjdoc: fails to upgrade/remove/install when /proc is not mounted
thanks

it also fails similarly on removal or installation when /proc is not
mounted.

live well,
  vagrant



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#607603: zsh: Completion of fuser command does not detect psmisc version

[gi1242+debianbugs]

Hi Clint,

Looks like there's a typo in your patch below:

> -if _pick_variant -c $words[1] psmisc=psmisc unix -V; then
> +if _pick_variant -c $words[1] psmisc='#(i)psmisc' unix -V; then

Should be '(#i)...' not '#(i)...' right?

Thanks,

GI

PS: I started using zsh 2 weeks ago. It is *AWESOME*, thanks a TON. I'm
migrating my custom completions over from tcsh, and have a few new
zsh completions, and corrections to old completions to contribute.
What is the best way to post them? Debian bugzilla, or the mailing
list?

-- 
The short fortuneteller who escaped from prison was a small medium at
large.



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

Bug#568608: closed by Cyril Brulebois (Bug#568236: fixed in xorg-server 2:1.7.5.902-1)

[gi1242+debianbugs]

On Mon, Mar 15, 2010 at 11:51:25PM +, Debian Bug Tracking System wrote:

> We believe that the bug you reported is fixed in the latest version of
> xorg-server, which is due to be installed in the Debian FTP archive:
> 
> xdmx-tools_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xdmx-tools_1.7.5.902-1_amd64.deb
> xdmx_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xdmx_1.7.5.902-1_amd64.deb
> xnest_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xnest_1.7.5.902-1_amd64.deb
> xorg-server_1.7.5.902-1.diff.gz
>   to main/x/xorg-server/xorg-server_1.7.5.902-1.diff.gz
> xorg-server_1.7.5.902-1.dsc
>   to main/x/xorg-server/xorg-server_1.7.5.902-1.dsc
> xorg-server_1.7.5.902.orig.tar.gz
>   to main/x/xorg-server/xorg-server_1.7.5.902.orig.tar.gz
> xserver-common_1.7.5.902-1_all.deb
>   to main/x/xorg-server/xserver-common_1.7.5.902-1_all.deb
> xserver-xephyr_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xserver-xephyr_1.7.5.902-1_amd64.deb
> xserver-xfbdev_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xserver-xfbdev_1.7.5.902-1_amd64.deb
> xserver-xorg-core-dbg_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xserver-xorg-core-dbg_1.7.5.902-1_amd64.deb
> xserver-xorg-core-udeb_1.7.5.902-1_amd64.udeb
>   to main/x/xorg-server/xserver-xorg-core-udeb_1.7.5.902-1_amd64.udeb
> xserver-xorg-core_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xserver-xorg-core_1.7.5.902-1_amd64.deb
> xserver-xorg-dev_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xserver-xorg-dev_1.7.5.902-1_amd64.deb
> xvfb_1.7.5.902-1_amd64.deb
>   to main/x/xorg-server/xvfb_1.7.5.902-1_amd64.deb

I just confirmed. This does NOT fix the problem! Can you please reopen
the bug?

Amongst the above, here's what I have installed currently on my system:

xserver-common  2:1.7.6-1
xserver-xorg-core   2:1.7.6-1
xserver-xorg-dev2:1.7.6-1

The server hangs 8 seconds when I switch back to it from a console. The
problem, as pointed out before, is with the WACOM serial device. I've
heard that there is a fix upstream, but it has not propagated to testing
yet,

GI

-- 
'Shin' -- A device for finding furniture in the dark.



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

Bug#607603: zsh: Completion of fuser command does not detect psmisc version

[gi1242+debianbugs]

Package: zsh
Version: 4.3.10-14
Severity: normal
Tags: patch

The completion function for fuser tries to determine if fuser is
provided by PSmisc, or other the (less functional) generic Unix version.
It decides by checking the output of "fuser -V" for psmisc. However it
does not use case insensitive matching, so the test fails on my system
(even though my fuser is provided by psmisc).

Changing line 6 in

/usr/share/zsh/functions/Completion/Unix/_fuser

from

if _pick_variant -c $words[1] psmisc=psmisc unix -V; then

to

if _pick_variant -c $words[1] psmisc='(#i)psmisc' unix -V; then

fixes the problem.

GI


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages zsh depends on:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libcap2   1:2.19-3   support for getting/setting POSIX.
ii  libncursesw5  5.7+20100313-4 shared libraries for terminal hand

Versions of packages zsh recommends:
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libpcre3  8.02-1.1   Perl 5 Compatible Regular Expressi

Versions of packages zsh suggests:
ii  zsh-doc   4.3.10-14  zsh documentation - info/HTML form

-- no debconf information

-- 
TOP 10 NEW FEATURES OF THE NEXT VERSION OF WINDOWS
3. Start-up .wav file replaced with the "cha-ching" sound of a cash
register.



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

Bug#569500: Updated patch combining solutions for #572203 and #569500

[rafael-debianbugs]

forwarded 569500 http://dev.mutt.org/trac/ticket/3261
thanks

On Fri, Apr 02, 2010 at 09:44:57PM +, Antonio Radici wrote:
> On Fri, Apr 02, 2010 at 11:35:55AM -0400, James Vega wrote:
> > Since #572203 and #569500 are both results of #528233, I figured I would
> > send an updated patch combining the fixes from myself and Philipp.
> > 
> > Philipp or Antonio, could you forward the patch upstream?
> 
> Sure, I will do it this weekend.
> 
> It's most likely that I will do an upload for your patch and some other
> patches.

Since #528233 was closed, shouldn't this bug be closed as well? Or is it
here waiting for upstream to close the forwarded ticket?



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

Bug#568608: Please reopen. Fixed upstream, but not in Debian.

[gi1242+debianbugs]

Ok -- this problem has been fixed upstream. It's an issue with
xserver-xorg-input-wacom. It's fixed in 0.10.8, for which no Debian
package exists yet.

The bug is present in 0.10.5+20100416-1 which is the latest version
available with Debian.

GI

-- 
'Common' Proof Techniques:
23. Proof by vehement assertion -- It is useful to have some kind of
authority relation to the audience.



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

Bug#590231: improperly nested partition?

[gi1242+debianbugs]

On Mon, Oct 04, 2010 at 11:59:44AM +0800, Michael Deegan wrote:

> Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition,
> rather than swap?

I got the same set of warnings, and had the same issue (i.e. a partition
table residing in the mbr of my swap). I just recreated my swap and all
was fine:

swapoff -a
mkswap -f /dev/sda2 # WARNING: Make sure the device name is correct.
# -f means "force". Wrong name = lost data.

You have to use the "-f" flag, otherwise your old boot sector won't be
erased. On successful completion, you should get no warning message, and
mkswap should have printed a UUID. Edit your /etc/fstab and replace the
UUID of the old swap partition with the new one. Then run

swapon -a

and you're good to go.

GI

-- 
'Microsecond' -- The time it takes for your state-of-the-art computer to
become obsolete.



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

Bug#590231: improperly nested partition?

[gi1242+debianbugs]

On Sat, Oct 23, 2010 at 03:43:53PM -0400, gi1242+debianb...@gmail.com wrote:

>> Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition,
>> rather than swap?
> 
> I got the same set of warnings, and had the same issue (i.e. a partition
> table residing in the mbr of my swap). I just recreated my swap and all
> was fine:
> 
> swapoff -a
> mkswap -f /dev/sda2 # WARNING: Make sure the device name is correct.
>   # -f means "force". Wrong name = lost data.
> 
> You have to use the "-f" flag, otherwise your old boot sector won't be
> erased. On successful completion, you should get no warning message, and
> mkswap should have printed a UUID. Edit your /etc/fstab and replace the
> UUID of the old swap partition with the new one. Then run
> 
> swapon -a
> 
> and you're good to go.

Oops. If you suspend to disk, then you need to update the swap UUID in

/etc/initramfs-tools/conf.d/resume

as well. Then run

update-initramfs -k all -u
update-grub # Probably not necessary

and reboot.

GI

-- 
File not found. Should I fake it? (Y/N)



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

Bug#560244: ITP: mysql-cluster

[debianbugs . boog]

Unfortunately the Ubuntu mysql-cluster package is broken, it has been
since the release of 10.04, although there is a workaround that works.

The bug report for this issue has been open since May with no
activity, it's status is still still listed as "new":
https://bugs.launchpad.net/ubuntu/+source/mysql-cluster-7.0/+bug/579732

I was really hoping that mysql-cluster would be available in Debian 6,
but I not optimistic as there seems to be no activity, and squeeze is
now frozen.




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

Bug#560244: ITP: mysql-cluster

[debianbugs . boog]

Toni
Thanks for the update. I am really glad this being worked on. Do you
know if the plan is have 2 separate packages like in Ubuntu, one w/
cluster support and one without (mysql-cluster-server & mysql-server)?
Also, if I can be of assistance in this effort to get this into Debian
please let me know.
Thanks.
Tom




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

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

[gi1242+debianbugs]

Package: tcsh
Version: 6.17.02-3
Severity: normal

If the alias "jobcmd" contains "!#:q", then all your typed commands are
stored twice in the history. Once as typed, and once with only the first
argument (and aliases expanded).

The issue does not arise if you don't use the ":q" modifier. This bug
was not present in 6.17.02-3 and is present in 6.17.02-2.

Here's how you can reproduce this:

1. Set jobcmd to use !#:q in some way. E.g.:

alias jobcmd echo -n '"\e]0;"\!#:q"\a"'

2. Run any command. E.g.

/bin/echo a b

3. See the bottom of your history.

583  0:31/bin/echo a b
   -5000   0:31/bin/echo a
584  0:31history | tail

4. Alternately go up in the history (using the "up" key). You'll first
   see a command "/bin/echo a" (which you never typed). Pressing the
   "up" key again, you'll get the command "/bin/echo a b" which you
   typed.



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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages tcsh depends on:
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libncurses5   5.7+20100313-2 shared libraries for terminal hand

tcsh recommends no packages.

tcsh suggests no packages.

-- no debconf information

-- 
A Windows user spends 1/3 of his life sleeping, 1/3 working, 1/3
waiting.



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

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

[gi1242+debianbugs]

On Tue, Aug 24, 2010 at 07:25:54AM +0200, Lucas Nussbaum wrote:

>> The issue does not arise if you don't use the ":q" modifier. This bug
>> was not present in 6.17.02-3 and is present in 6.17.02-2.
> 
> Huh? I guess you mistyped one of the new versions. Could you check?

Yes, I swapped them apologies. (I sent a correction email, but it got
rejected by the BTS as there was no number assigned yet).

The bug is present in 6.17.02-3. The bug is not present in 6.17.02-2.

Thanks,

Gautam

-- 
'Common' Proof Techniques:
18. Proof by importance -- A large body of useful consequences all
follow from the proposition in question.



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

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

[gi1242+debianbugs]

On Tue, Aug 24, 2010 at 09:13:31PM +0200, Lucas Nussbaum wrote:

 The issue does not arise if you don't use the ":q" modifier. This bug
 was not present in 6.17.02-3 and is present in 6.17.02-2.
>>> 
>>> Huh? I guess you mistyped one of the new versions. Could you check?
>> 
>> Yes, I swapped them apologies. (I sent a correction email, but it got
>> rejected by the BTS as there was no number assigned yet).
>> 
>> The bug is present in 6.17.02-3. The bug is not present in 6.17.02-2.
> 
> That's rather strange. The only difference between the two versions is
> the re-addition of an unrelated patch. Could you maybe recheck using
> the binary packages on
> http://snapshot.debian.org/package/tcsh/ ?

Indeed. On rechecking, the bug is also present in 6.17.02-x.

The bug is however *absent* in 6.17.00-3. Check what you get on your
system with the following:

tcsh:> tcsh -f
> alias jobcmd echo -n '"\e]0;"\!#:q "($cwd)\a"'
> /bin/echo hello world
> history

On 6.17.00-3 the output of the last command is

 1  21:12   alias jobcmd echo -n '"\e]0;"\!#:q "($cwd)\a"'
 2  21:12   /bin/echo hello world
 3  21:12   history

On 6.17.02-3 the output of the last command is

 1  21:17   alias jobcmd echo -n '"\e]0;"\!#:q "($cwd)\a"'
 2  21:17   /bin/echo hello world
-5000   21:17   /bin/echo hello
 3  21:17   history

The history event with number -5000 is a bug.

Thanks,

GI

-- 
Actually officer, if you factor in the earth's rotation, we were all
speeding.



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

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

[gi1242+debianbugs]

Package: xserver-xorg-video-intel
Version: 2:2.15.0-1
Severity: important

There are various instances when the screen is not updated. Usually this
happens when repeated keyboard, or mouse input is involved at the same
time. Some examples:

xournal

When using the 2.6.38 kernel, some strokes don't show up, until
the pen/mouse leave the xournal window. When using the 2.6.32,
or 2.6.38 kernels, when the display is rotated, the strokes show
up after a delay.

I followed this upstream and the bug was traced to the video
driver:

http://sourceforge.net/mailarchive/message.php?msg_id=27467219
http://sourceforge.net/mailarchive/message.php?msg_id=27480622

frozen-bubble-2.2.0-2
pangzero-1.3-2

In both games, there are numerous times (usually when I hold
down a key) when the screen stops being updated. The bug is not
present when I use the 2.6.32 kernel.

There was a suggestion on the Xournal mailing list that this bug is
related to


http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3145530feed879082bcfab11ffc8e7fd0911c920

But I haven't mastered debian packaging enough to try integrating this
myself. (Trying to install xserver-xorg-video-intel/sid itself wanted me
to upgrade xserver-xorg-core, which I wasn't prepared to do as this is
my primary work machine).

Finally, this might be related to Debian Bug #597696, or it might not
be. I wasn't sure, so I opened a new issue.

Thanks for any help with this,

GI


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Dec 21  2009 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1926464 Mar 25 23:49 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1

Kernel version (/proc/version):
---
Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 32106 Dec 23  2009 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 22147 Feb 19 22:49 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 29733 May 10 21:43 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[59.171] 
X.Org X Server 1.9.5
Release Date: 2011-03-17
[59.171] X Protocol Version 11, Revision 0
[59.171] Build Operating System: Linux 2.6.38-1-amd64 x86_64 Debian
[59.171] Current Operating System: Linux mordor 2.6.38-2-amd64 #1 SMP Thu 
Apr 7 04:28:07 UTC 2011 x86_64
[59.171] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 
root=UUID=9f504572-3101-4f1d-9c22-08938165f79d ro quiet
[59.171] Build Date: 26 March 2011  03:32:34AM
[59.171] xorg-server 2:1.9.5-1 (Cyril Brulebois ) 
[59.171] Current version of pixman: 0.21.4
[59.171]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[59.171] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[59.172] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 10 07:43:42 
2011
[59.269] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[59.308] (==) No Layout section.  Using the first Screen section.
[59.308] (==) No screen section available. Using defaults.
[59.308] (**) |-->Screen "Default Screen Section" (0)
[59.308] (**) |   |-->Monitor ""
[59.309] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[59.309] (==) Automatically adding devices
[59.309] (==) Automatically enabling devices
[59.352] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[59.352]Entry deleted from font path.
[59.476] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[59.476] (==) ModulePath set to "/usr/lib/xorg/modules"
[59.476] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[59.476]

Bug#315142: Gtk+Perl alternative to wacomcpl

[gi1242+debianbugs]

Here's an updated version of the script. With the recent xsetwacom
upgrade, it wasn't harvesting device names correctly. Should be fixed
now,

GI

-- 
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
49. If I learn the whereabouts of the one artifact which can destroy me,
I will not send all my troops out to seize it. Instead I will send them
out to seize something else and quietly put a Want-Ad in the local
paper.


calibrate.pl
Description: Perl program

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

[gi1242+debianbugs]

On Wed, May 11, 2011 at 10:30:10AM +0200, Cyril Brulebois wrote:

>> There was a suggestion on the Xournal mailing list that this bug is
>> related to
>> 
>> 
>> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3145530feed879082bcfab11ffc8e7fd0911c920
>> 
>> But I haven't mastered debian packaging enough to try integrating
>> this myself.
> 
> something like this should do the job, or at least get you started:
> 
> sudo apt-get build-dep xserver-xorg-video-intel
> # from the devscripts package, or git clone from git.debian.org:
> debcheckout xserver-xorg-video-intel
> cd xserver-xorg-video-intel
> git remote add upstream 
> git://anongit.freedesktop.org/xorg/driver/xf86-video-intel
> git fetch upstream
> git cherry-pick 3145530feed879082bcfab11ffc8e7fd0911c920
> dch --local +yournickname "Cherry-pick 
> 3145530feed879082bcfab11ffc8e7fd0911c920 from upstream."
> debuild -b
> sudo debi

Thanks a ton! This worked. Though I presume you mean 

debuild -d (instead of -b)

Also there were two other patches in the git upstream that might have
been related; so instead of cherry picking, I did

git pull upstream HEAD

Now installing this driver solves all the problems on my system. I'll
post back confirming though. I've heard reports that this bug is
aggravated by repeated suspend / resumes. If things are working tip top
in a few days, I'll post back confirming.

Thanks a ton for the Debian package build instructions! It was exactly
what I needed,

GI

-- 
100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD
66. My security keypad will actually be a fingerprint scanner. Anyone
who watches someone press a sequence of buttons or dusts the pad for
fingerprints then subsequently tries to enter by repeating that sequence
will trigger the alarm system.



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

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

[gi1242+debianbugs]

On Fri, May 13, 2011 at 09:49:23PM -0400, gi1242+debianb...@gmail.com wrote:

> Now installing this driver solves all the problems on my system. I'll
> post back confirming though.

OK. The bug is back. It is a little more sporadic, and a lot less
severe. But the bug is certainly back. (However the system is a lot more
usable, since the bug is a lot lot less severe.

Please let me know if there is anything I can do to help fix it.


-- 
'Committee' -- A cul-de-sac down which ideas are lured and then quietly
strangled.


signature.asc
Description: Digital signature