from:"Quanah"

Re: [Touch-packages] [Bug 1749247] Re: Spurious SEGV running inside kvm

2018-02-14 Thread Quanah

It can also die with the following backtrace:
(gdb) bt
#0  __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2331
#1  0x7f570da4a14e in ber_dupbv_x (dst=0x25f55e8, src=0x7f2ee8001200,
ctx=0x0) at
/home/build/git/sold-2445/openldap/libraries/liblber/memory.c:512
#2  0x7f570da4a19f in ber_dupbv (dst=0x25f55e8, src=0x7f2ee8001200) at
/home/build/git/sold-2445/openldap/libraries/liblber/memory.c:523
#3  0x7f57091a07b4 in accesslog_op_mod (op=0x7f2f0518e780,
rs=0x7f2f0518e030) at
/home/build/git/sold-2445/openldap/servers/slapd/overlays/accesslog.c:2031
#4  0x004d9be5 in overlay_op_walk (op=0x7f2f0518e780,
rs=0x7f2f0518e030, which=op_modify, oi=0x25eb720, on=0x25f53c0)
at /home/build/git/sold-2445/openldap/servers/slapd/backover.c:661
#5  0x004d9ee1 in over_op_func (op=0x7f2f0518e780,
rs=0x7f2f0518e030, which=op_modify) at
/home/build/git/sold-2445/openldap/servers/slapd/backover.c:730
#6  0x004da044 in over_op_modify (op=0x7f2f0518e780,
rs=0x7f2f0518e030) at
/home/build/git/sold-2445/openldap/servers/slapd/backover.c:769
#7  0x004cc061 in syncrepl_updateCookie (si=0x26499f0,
op=0x7f2f0518e780, syncCookie=0x7f2f0518e290) at
/home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:3982
#8  0x004c0bd5 in do_syncrep2 (op=0x7f2f0518e780, si=0x26499f0) at
/home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:1019
#9  0x004c2ea6 in do_syncrepl (ctx=0x7f2f0518ec30, arg=0x25ebb40)
at /home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:1567
#10 0x0043dbed in connection_read_thread (ctx=0x7f2f0518ec30,
argv=0x11) at
/home/build/git/sold-2445/openldap/servers/slapd/connection.c:1296
#11 0x7f570dc6a909 in ldap_int_thread_pool_wrapper (xpool=0x24e8500) at
/home/build/git/sold-2445/openldap/libraries/libldap_r/tpool.c:963
#12 0x7f570d8276ba in start_thread (arg=0x7f2f0518f700) at
pthread_create.c:333
#13 0x7f570c86f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

On Wed, Feb 14, 2018 at 6:45 AM, Howard Chu  wrote:

> Will try to come up with a minimal reproducer. Currently it takes
> several hours to run the complete test, and a few hours before the SEGV
> occurs. But the stack trace is always identical when it happens. In
> multiple runs, it always succeeds on the host and always fails in the
> VM.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1749247
>
> Title:
>   Spurious SEGV running inside kvm
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/
> 1749247/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1749247

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501

[Touch-packages] [Bug 1693915] [NEW] e2fsprogs: ext(2, 3, 4) manpage typo

2017-05-26 Thread Quanah

Public bug reported:

When running: man ext4

There is an obvious typo at the top:

NAME
   ext2 - the second extended file system
   ext2 - the third extended file system
   ext4 - the fourth extended file system


Clearly, the "third" extended filesystem should be "ext3" not "ext2"

** Affects: e2fsprogs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1693915

Title:
  e2fsprogs: ext(2,3,4) manpage typo

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  When running: man ext4

  There is an obvious typo at the top:

  NAME
 ext2 - the second extended file system
 ext2 - the third extended file system
 ext4 - the fourth extended file system

  
  Clearly, the "third" extended filesystem should be "ext3" not "ext2"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1693915/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1616679] [NEW] rdepends for apt-cache fails for virtual packages

2016-08-24 Thread Quanah

Public bug reported:

Example of problem:

The zimbra-mta package provides mail-transport-agent.

Packages that depend on mail-transport-agent are installed
(mailutils,logwatch).

apt-cache is unable to list either of those as depending on zimbra-mta:

root@zre-ldap004:/home/build# apt-cache rdepends --installed 
mail-transport-agent



aptitude does a little better:

root@zre-ldap004:/home/build# aptitude why zimbra-mta
iB  mailutils  Depends  default-mta | mail-transport-agent
ip  zimbra-mta Provides mail-transport-agent


so it finds mailutils (but not logwatch).  so 50% better than apt-cache

If we try to remove zimbra-mta, we find:

root@zre-ldap004:/home/build# dpkg --purge zimbra-mta
dpkg: dependency problems prevent removal of zimbra-mta:
 mailutils depends on default-mta | mail-transport-agent; however:
  Package default-mta is not installed.
  Package mail-transport-agent is not installed.
  Package zimbra-mta which provides mail-transport-agent is to be removed.
 logwatch depends on postfix | mail-transport-agent; however:
  Package postfix is not installed.
  Package mail-transport-agent is not installed.
  Package zimbra-mta which provides mail-transport-agent is to be removed.


apt-cache kind of functions with postfix as the rdepends:

root@zre-ldap004:/home/build# apt-cache rdepends --installed postfix
postfix
Reverse Depends:
 |logwatch
  libsasl2-2
 |cron


so we pick up logwatch in that case.

However, we *still* fail to find mailutils:

root@zre-ldap004:/home/build# apt-cache rdepends --installed default-mta



So the rdepends flag for apt-cache seems to be completely broken for virtual 
packages.

root@zre-ldap004:/home/build# apt-cache showpkg zimbra-mta
Package: zimbra-mta
Versions:
8.7.0.GA.1655.UBUNTU14.64 (/var/lib/dpkg/status)
 Description Language:
 File: /var/lib/dpkg/status
  MD5: b25f6328eb0ffec1cb7bcd41cb0ddc9b


Reverse Depends:
Dependencies:
8.7.0.GA.1655.UBUNTU14.64 - zimbra-core (0 (null)) zimbra-mta-components (0 
(null)) mail-transport-agent (0 (null)) mail-transport-agent:i386 (0 (null)) 
mail-transport-agent (0 (null)) mail-transport-agent:i386 (0 (null))
Provides:
8.7.0.GA.1655.UBUNTU14.64 - mail-transport-agent
Reverse Provides:


root@zre-ldap004:/home/build# apt-cache showpkg logwatch
Package: logwatch
Versions:
7.4.0+svn20130529rev144-1ubuntu1 
(/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_trusty_main_binary-amd64_Packages)
 (/var/lib/dpkg/status)
 Description Language:
 File: 
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_trusty_main_binary-amd64_Packages
  MD5: ece539a8a87c5f861d7f0b865e42a03c
 Description Language: en
 File: 
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_trusty_main_i18n_Translation-en
  MD5: ece539a8a87c5f861d7f0b865e42a03c


Reverse Depends:
Dependencies:
7.4.0+svn20130529rev144-1ubuntu1 - perl (0 (null)) postfix (16 (null)) 
mail-transport-agent (0 (null)) fortune-mod (0 (null)) libdate-manip-perl (0 
(null))
Provides:
7.4.0+svn20130529rev144-1ubuntu1 -
Reverse Provides:


root@zre-ldap004:/home/build# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.4 LTS"

root@zre-ldap004:/home/build# apt-cache policy apt
apt:
  Installed: 1.0.1ubuntu2.14
  Candidate: 1.0.1ubuntu2.14
  Version table:
 *** 1.0.1ubuntu2.14 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.1ubuntu2.13 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
 1.0.1ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1616679

Title:
  rdepends for apt-cache fails for virtual packages

Status in apt package in Ubuntu:
  New

Bug description:
  Example of problem:

  The zimbra-mta package provides mail-transport-agent.

  Packages that depend on mail-transport-agent are installed
  (mailutils,logwatch).

  apt-cache is unable to list either of those as depending on zimbra-
  mta:

  root@zre-ldap004:/home/build# apt-cache rdepends --installed 
mail-transport-agent
  

  
  aptitude does a little better:

  root@zre-ldap004:/home/build# aptitude why zimbra-mta
  iB  mailutils  Depends  default-mta | mail-transport-agent
  ip  zimbra-mta Provides mail-transport-agent

  
  so it finds mailutils (but not logwatch).  so 50% better than apt-cache

  If we try to remove zimbra-mta, we find:

  root@zre-ldap004:/home/build# dpkg --purge zimbra-mta
  dpkg: dependency problems prevent removal of zimbra-mta:
   mailutils depends on default-mta | mail-transport-agent; however:
Package default-mta is not installed.

[Touch-packages] [Bug 1574969] Re: Regression: "lxc-create -B best" stopped working

2016-05-07 Thread Quanah

This is breaking the ability to use vagrant with LXC boxes.

/opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/batch_action.rb:82:in 
`block (2 levels) in run'
 INFO interface: error: There was an error executing ["sudo", "/usr/bin/env", 
"lxc-create", "-B", "best", "--template", 
"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template", 
"--name", "u1690_default_1462660055308_76102", "--", "--tarball", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz",
 "--config", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
There was an error executing ["sudo", "/usr/bin/env", "lxc-create", "-B", 
"best", "--template", 
"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template", 
"--name", "u1690_default_1462660055308_76102", "--", "--tarball", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz",
 "--config", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO interface: Machine: error-exit ["Vagrant::LXC::Errors::ExecuteError", 
"There was an error executing [\"sudo\", \"/usr/bin/env\", \"lxc-create\", 
\"-B\", \"best\", \"--template\", 
\"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template\", 
\"--name\", \"u1690_default_1462660055308_76102\", \"--\", \"--tarball\", 
\"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz\",
 \"--config\", 
\"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config\"]\n\nFor
 more information on the failure, enable detailed logging by setting\nthe 
environment variable VAGRANT_LOG to DEBUG."]
quanah@ub16:~/vagrant/u1690$ sudo su -
root@ub16:~# lxc-create -B best --template 
/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template --name 
u1690_default_1462660055308_76102 -- --tarball 
/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz
 --config 
/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config
best is not a valid backing storage type.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1574969

Title:
  Regression: "lxc-create -B best" stopped working

Status in Auto Upgrade Testing:
  Triaged
Status in lxc:
  New
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I want to use btrfs storage if available, otherwise the plain old
  directory/copies. Until not too long ago, this worked:

$ sudo lxc-create -B best --name=adt-xenial -t ubuntu -- -r xenial

  But now in final xenial it fails with "best is not a valid backing
  storage type.".

  But the manpage still documents it:

If backingstore is 'best', then lxc will try, in order, btrfs, 
zfs, lvm, and finally a  di‐
rectory backing store.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Apr 26 08:33:14 2016
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dnsmasq.conf:
   enable-tftp
   tftp-root=/tmp/tftp
   dhcp-boot=pxelinux.0
  lxc.conf: lxc.lxcpath = /srv/lxc

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-upgrade-testing/+bug/1574969/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

2016-04-28 Thread Quanah

It is trivial to fix this by adding the following to ~/.bashrc:

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
  eval `dbus-launch --sh-syntax`
fi

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsecret in Ubuntu.
https://bugs.launchpad.net/bugs/1420914

Title:
  secret-tool does not run on headless system

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  libsecret-tools:
Installed: 0.16-0ubuntu1
Candidate: 0.16-0ubuntu1
Version table:
   *** 0.16-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  I expected to be able to run secret-tool on a headless sytem, but got
  this message after running it.

  secret-tool store ...

  (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY

  # didn't expect thisto work, but thought I'd give it a try.
  export DISPLAY=:0
  secret-tool store ...

  (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Error spawning command line 'dbus-launch 
--autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': 
Child process exited with code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1420914/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

2016-04-28 Thread Quanah

Still a problem in ubuntu14.04.3.  Command line tools should not depend
on X11.

secret-tool store
--label="blahblah/org.freedesktop.NetworkManager.vpnc/vpn" setting-name
vpn setting-key "Xauth password"

(secret-tool:6159): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsecret in Ubuntu.
https://bugs.launchpad.net/bugs/1420914

Title:
  secret-tool does not run on headless system

Status in libsecret package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  libsecret-tools:
Installed: 0.16-0ubuntu1
Candidate: 0.16-0ubuntu1
Version table:
   *** 0.16-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  I expected to be able to run secret-tool on a headless sytem, but got
  this message after running it.

  secret-tool store ...

  (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY

  # didn't expect thisto work, but thought I'd give it a try.
  export DISPLAY=:0
  secret-tool store ...

  (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  secret-tool: Error spawning command line 'dbus-launch 
--autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': 
Child process exited with code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1420914/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2

2015-11-20 Thread Quanah Gibson-Mount

Hi Sebastien,

The problem is I've found no consistent trigger for the bug.  I have 225
packages in my repository, built out for two different branches and two
oses (so 225x4).  createrepo just randomly corrupts when executing
'createrepo --update .' when adding a new source/binary rpm pair.  It is
trivially solvable (rm -rf repodata .repodata; createrepo .), but having
to briefly have a 100% repo outage is the problem.

I've not seen anything specific about the packages that would cause this
to occur.  It seems to be some type of race condition during the update
process, because of it complaining about " I/O error : No such file or
directory".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1375637

Title:
  Premature end of data in tag file line 247651 with libxml2

Status in libxml2 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm getting the following behaviour of createrepo on Ubuntu 14.04.1
  LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and
  libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main).

  createrepo -g 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml
 \
-o 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/
  I/O error : No such file or directory

  (process:29830): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag package line 246828

  
  (process:29830): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag filelists line 2

  Spawning worker 0 with 54 pkgs
  Spawning worker 1 with 54 pkgs
  Spawning worker 2 with 54 pkgs
  Spawning worker 3 with 54 pkgs
  Spawning worker 4 with 54 pkgs
  Spawning worker 5 with 54 pkgs
  Spawning worker 6 with 54 pkgs
  Spawning worker 7 with 54 pkgs
  Spawning worker 8 with 54 pkgs
  Spawning worker 9 with 54 pkgs
  Spawning worker 10 with 53 pkgs
  Spawning worker 11 with 53 pkgs
  Spawning worker 12 with 53 pkgs
  Spawning worker 13 with 53 pkgs
  Spawning worker 14 with 53 pkgs
  Spawning worker 15 with 53 pkgs
  Spawning worker 16 with 53 pkgs
  Spawning worker 17 with 53 pkgs
  Spawning worker 18 with 53 pkgs
  Spawning worker 19 with 53 pkgs
  Spawning worker 20 with 53 pkgs
  Spawning worker 21 with 53 pkgs
  Spawning worker 22 with 53 pkgs
  Spawning worker 23 with 53 pkgs
  Workers Finished
  Saving Primary metadata
  Saving file lists metadata
  Saving other metadata
  Generating sqlite DBs
  Traceback (most recent call last):
File "/usr/share/createrepo/genpkgmetadata.py", line 308, in 
  main(sys.argv[1:])
File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main
  mdgen.doRepoMetadata()
File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, 
in doRepoMetadata
  rp.getFilelists(complete_path, csum)
File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 55, in 
getFilelists
  self.repoid))
  TypeError: Parsing filelists.xml error: Premature end of data in tag file 
line 247651


  Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid.
  Comparing patchsets in debian package sources between  2.9.1+dfsg1 and 
2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one 
of them helps in my problem:

  2.9.1+dfsg1-3ubuntu4.3:

  0001-modify-xml2-config-and-pkgconfig-behaviour.patch
  0002-Fix-an-error-in-xmlCleanupParser.patch
  0003-Fix-missing-break-on-last-function-for-attributes.patch
  0004-xmllint-memory-should-fail-on-empty-files.patch
  0005-properly-quote-the-namespace-uris-written-out-during.patch
  0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch
  0006-fix-python-multiarch-includes.patch
  0007-Fix-XPath-optimization-with-predicates.patch
  CVE-2014-0191.patch
  lp1321869.patch
  xmllint_pretty.patch

  
  2.9.1+dfsg1: 

  0001-modify-xml2-config-and-pkgconfig-behaviour.patch
  0002-fix-python-multiarch-includes.patch
  0003-Fix-an-error-in-xmlCleanupParser.patch
  0004-Fix-missing-break-on-last-function-for-attributes.patch
  0005-xmllint-memory-should-fail-on-empty-files.patch
  0006-properly-quote-the-namespace-uris-written-out-during.patch
  0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch
  0008-missing-else-in-xlink.c.patch
  0009-Catch-malloc-error-and-exit-accordingly.patch
  0010-Fix-handling-of-mmap-errors.patch
  0011-Avoid-crash-if-allocation-fails.patch

[Touch-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2

2015-11-19 Thread Quanah Gibson-Mount

When will this be fixed?  I'm currently using a single server to host
both debs and rpms, and this bug triggers fairly frequently, causing me
to have to take down my repo and regenerate it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1375637

Title:
  Premature end of data in tag file line 247651 with libxml2

Status in libxml2 package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm getting the following behaviour of createrepo on Ubuntu 14.04.1
  LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and
  libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main).

  createrepo -g 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml
 \
-o 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ 
/home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/
  I/O error : No such file or directory

  (process:29830): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag package line 246828

  
  (process:29830): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Parsing filelists.xml error: Premature end 
of data in tag filelists line 2

  Spawning worker 0 with 54 pkgs
  Spawning worker 1 with 54 pkgs
  Spawning worker 2 with 54 pkgs
  Spawning worker 3 with 54 pkgs
  Spawning worker 4 with 54 pkgs
  Spawning worker 5 with 54 pkgs
  Spawning worker 6 with 54 pkgs
  Spawning worker 7 with 54 pkgs
  Spawning worker 8 with 54 pkgs
  Spawning worker 9 with 54 pkgs
  Spawning worker 10 with 53 pkgs
  Spawning worker 11 with 53 pkgs
  Spawning worker 12 with 53 pkgs
  Spawning worker 13 with 53 pkgs
  Spawning worker 14 with 53 pkgs
  Spawning worker 15 with 53 pkgs
  Spawning worker 16 with 53 pkgs
  Spawning worker 17 with 53 pkgs
  Spawning worker 18 with 53 pkgs
  Spawning worker 19 with 53 pkgs
  Spawning worker 20 with 53 pkgs
  Spawning worker 21 with 53 pkgs
  Spawning worker 22 with 53 pkgs
  Spawning worker 23 with 53 pkgs
  Workers Finished
  Saving Primary metadata
  Saving file lists metadata
  Saving other metadata
  Generating sqlite DBs
  Traceback (most recent call last):
File "/usr/share/createrepo/genpkgmetadata.py", line 308, in 
  main(sys.argv[1:])
File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main
  mdgen.doRepoMetadata()
File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, 
in doRepoMetadata
  rp.getFilelists(complete_path, csum)
File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 55, in 
getFilelists
  self.repoid))
  TypeError: Parsing filelists.xml error: Premature end of data in tag file 
line 247651


  Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid.
  Comparing patchsets in debian package sources between  2.9.1+dfsg1 and 
2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one 
of them helps in my problem:

  2.9.1+dfsg1-3ubuntu4.3:

  0001-modify-xml2-config-and-pkgconfig-behaviour.patch
  0002-Fix-an-error-in-xmlCleanupParser.patch
  0003-Fix-missing-break-on-last-function-for-attributes.patch
  0004-xmllint-memory-should-fail-on-empty-files.patch
  0005-properly-quote-the-namespace-uris-written-out-during.patch
  0006-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch
  0006-fix-python-multiarch-includes.patch
  0007-Fix-XPath-optimization-with-predicates.patch
  CVE-2014-0191.patch
  lp1321869.patch
  xmllint_pretty.patch

  
  2.9.1+dfsg1: 

  0001-modify-xml2-config-and-pkgconfig-behaviour.patch
  0002-fix-python-multiarch-includes.patch
  0003-Fix-an-error-in-xmlCleanupParser.patch
  0004-Fix-missing-break-on-last-function-for-attributes.patch
  0005-xmllint-memory-should-fail-on-empty-files.patch
  0006-properly-quote-the-namespace-uris-written-out-during.patch
  0007-Fix-a-parsing-bug-on-non-ascii-element-and-CR-LF-usa.patch
  0008-missing-else-in-xlink.c.patch
  0009-Catch-malloc-error-and-exit-accordingly.patch
  0010-Fix-handling-of-mmap-errors.patch
  0011-Avoid-crash-if-allocation-fails.patch
  0012-Fix-a-possible-NULL-dereference.patch
  0013-Clear-up-a-potential-NULL-dereference.patch
  0014-Fix-XPath-optimization-with-predicates.patch
  0015-xmllint-pretty-crashed-without-following-numeric-arg.patch
  0016-Fix-potential-NULL-pointer-dereferences-in-regexp-co.patch
  0017-Fix-a-potential-NULL-dereference-in-tree-code.patch
  0018-Fix-pointer-dereferenced-before-null-check.patch
  0019-Fix-a-bug-loading-some-compressed-files.patch

[Touch-packages] [Bug 1003633] Re: Escape plus character in apt HTTP requests to work around Amazon S3 bug

2015-11-03 Thread Quanah Gibson-Mount

I filed https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1512845 for
the https issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1003633

Title:
  Escape plus character in apt HTTP requests to work around Amazon S3
  bug

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  
  Amazon S3 performs incorrect query-string un-escaping on URLs and improperly 
converts the plus ('+') character to a space (' ') when processing incoming GET 
requests for files.  This causes apt-get to get HTTP 404 errors when 
downloading packages from S3-hosted mirrors which include a + character in the 
name of the package.

  For more background info, see:
  https://forums.aws.amazon.com/thread.jspa?threadID=55746

  One possibly solution is to change the call to QuoteString in http.cc
  to include '+' in the character set, which would escape the plus
  character to the %2B form, which will be properly processed by Amazon
  S3.

  Thanks,
  Doug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1003633/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512845] [NEW] Escape plus character in apt HTTPS requests to work around Amazon S3 bug

2015-11-03 Thread Quanah Gibson-Mount

Public bug reported:

As noted in bug#1003633, S3 is broken when a + sign exists unless it is
escaped.  This was fixed in 2013 for http based repos.  However, it is
still broken for https based repositories.

apt-get install zimbra-openssl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  zimbra-openssl-lib
The following NEW packages will be installed:
  zimbra-openssl zimbra-openssl-lib
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,324 kB of archives.
After this operation, 6,313 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl-lib amd64 
1.0.1p-1zimbra8.7b1+14.04 [828 kB]
Err https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl-lib amd64 
1.0.1p-1zimbra8.7b1+14.04
  HttpError403
Get:2 https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl amd64 
1.0.1p-1zimbra8.7b1+14.04 [497 kB]
Err https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl amd64 
1.0.1p-1zimbra8.7b1+14.04
  HttpError403
E: Failed to fetch 
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl-lib_1.0.1p-1zimbra8.7b1+14.04_amd64.deb
  HttpError403

E: Failed to fetch https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-
openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1+14.04_amd64.deb  HttpError403

E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?


Escaping the + sign fixes the issue when testing with wget:

root@zre-ldap001:/home/quanah# wget 
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1%2B14.04_amd64.deb
--2015-11-03 13:11:03--  
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1%2B14.04_amd64.deb
Resolving repo.zimbra.com (repo.zimbra.com)... 54.230.4.69, 54.230.6.152, 
54.192.4.217, ...
Connecting to repo.zimbra.com (repo.zimbra.com)|54.230.4.69|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 496784 (485K) [application/x-debian-package]
Saving to: ‘zimbra-openssl_1.0.1p-1zimbra8.7b1+14.04_amd64.deb’

100%[===>]
496,784 1.62MB/s   in 0.3s

2015-11-03 13:11:04 (1.62 MB/s) - ‘zimbra-openssl_1.0.1p-
1zimbra8.7b1+14.04_amd64.deb’ saved [496784/496784]

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1512845

Title:
  Escape plus character in apt HTTPS requests to work around Amazon S3
  bug

Status in apt package in Ubuntu:
  New

Bug description:
  As noted in bug#1003633, S3 is broken when a + sign exists unless it
  is escaped.  This was fixed in 2013 for http based repos.  However, it
  is still broken for https based repositories.

  apt-get install zimbra-openssl
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following extra packages will be installed:
zimbra-openssl-lib
  The following NEW packages will be installed:
zimbra-openssl zimbra-openssl-lib
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,324 kB of archives.
  After this operation, 6,313 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl-lib amd64 
1.0.1p-1zimbra8.7b1+14.04 [828 kB]
  Err https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl-lib amd64 
1.0.1p-1zimbra8.7b1+14.04
HttpError403
  Get:2 https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl amd64 
1.0.1p-1zimbra8.7b1+14.04 [497 kB]
  Err https://repo.zimbra.com/apt/87/ trusty/zimbra zimbra-openssl amd64 
1.0.1p-1zimbra8.7b1+14.04
HttpError403
  E: Failed to fetch 
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl-lib_1.0.1p-1zimbra8.7b1+14.04_amd64.deb
  HttpError403

  E: Failed to fetch https://repo.zimbra.com/apt/87/pool/zimbra/z
  /zimbra-openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1+14.04_amd64.deb
  HttpError403

  E: Unable to fetch some archives, maybe run apt-get update or try with
  --fix-missing?

  
  Escaping the + sign fixes the issue when testing with wget:

  root@zre-ldap001:/home/quanah# wget 
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1%2B14.04_amd64.deb
  --2015-11-03 13:11:03--  
https://repo.zimbra.com/apt/87/pool/zimbra/z/zimbra-openssl/zimbra-openssl_1.0.1p-1zimbra8.7b1%2B14.04_amd64.deb
  Resolving repo.zimbra.com (repo.zimbra.com)... 54.230.4.69, 54.230.6.152, 
54.192.4.217, ...
  Connecting to repo.zimbra.com (repo.zimbra.com)|54.230.4.69|:443... connected.
  HTTP request s

[Touch-packages] [Bug 1003633] Re: Escape plus character in apt HTTP requests to work around Amazon S3 bug

2015-11-03 Thread Quanah Gibson-Mount

I would note this is broken for https based repositories still.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1003633

Title:
  Escape plus character in apt HTTP requests to work around Amazon S3
  bug

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  
  Amazon S3 performs incorrect query-string un-escaping on URLs and improperly 
converts the plus ('+') character to a space (' ') when processing incoming GET 
requests for files.  This causes apt-get to get HTTP 404 errors when 
downloading packages from S3-hosted mirrors which include a + character in the 
name of the package.

  For more background info, see:
  https://forums.aws.amazon.com/thread.jspa?threadID=55746

  One possibly solution is to change the call to QuoteString in http.cc
  to include '+' in the character set, which would escape the plus
  character to the %2B form, which will be properly processed by Amazon
  S3.

  Thanks,
  Doug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1003633/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1442775] [NEW] apt-get --ignore-missing doesn't ignore missing packages

2015-04-10 Thread Quanah Gibson-Mount

Public bug reported:

The man page for apt-get states:

   -m, --ignore-missing, --fix-missing
   Ignore missing packages; if packages cannot be retrieved or fail the 
integrity check after retrieval (corrupted package files), hold back those 
packages and handle the
   result. Use of this option together with -f may produce an error in 
some situations. If a package is selected for installation (particularly if it 
is mentioned on the
   command line) and it could not be downloaded then it will be 
silently held back. Configuration Item: APT::Get::Fix-Missing.

However, when removing or purging packages, it does /not/ actually
ignore missing packages:

build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo apt-get purge -y 
--ignore-missing zimbra-openssl-lib
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package zimbra-openssl-lib
build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $?
100

This causes some pain when using apt-get in a Makefile and wanting to
ensure custom packages have been removed.

dpkg handles this correctly:

build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo dpkg --purge 
zimbra-openssl-lib
dpkg: warning: ignoring request to remove zimbra-openssl-lib which isn't 
installed
build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $?
0

however you then lose dependency tracking.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1442775

Title:
  apt-get --ignore-missing doesn't ignore missing packages

Status in apt package in Ubuntu:
  New

Bug description:
  The man page for apt-get states:

 -m, --ignore-missing, --fix-missing
 Ignore missing packages; if packages cannot be retrieved or fail 
the integrity check after retrieval (corrupted package files), hold back those 
packages and handle the
 result. Use of this option together with -f may produce an error 
in some situations. If a package is selected for installation (particularly if 
it is mentioned on the
 command line) and it could not be downloaded then it will be 
silently held back. Configuration Item: APT::Get::Fix-Missing.

  However, when removing or purging packages, it does /not/ actually
  ignore missing packages:

  build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo apt-get purge -y 
--ignore-missing zimbra-openssl-lib
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package zimbra-openssl-lib
  build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $?
  100

  This causes some pain when using apt-get in a Makefile and wanting to
  ensure custom packages have been removed.

  dpkg handles this correctly:

  build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ sudo dpkg --purge 
zimbra-openssl-lib
  dpkg: warning: ignoring request to remove zimbra-openssl-lib which isn't 
installed
  build@ub14test:~/p4/zimbra/main/ThirdParty/openldap$ echo $?
  0

  however you then lose dependency tracking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1442775/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1749247] Re: Spurious SEGV running inside kvm

[Touch-packages] [Bug 1693915] [NEW] e2fsprogs: ext(2, 3, 4) manpage typo

[Touch-packages] [Bug 1616679] [NEW] rdepends for apt-cache fails for virtual packages

[Touch-packages] [Bug 1574969] Re: Regression: "lxc-create -B best" stopped working

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system

[Touch-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2

[Touch-packages] [Bug 1375637] Re: Premature end of data in tag file line 247651 with libxml2

[Touch-packages] [Bug 1003633] Re: Escape plus character in apt HTTP requests to work around Amazon S3 bug

[Touch-packages] [Bug 1512845] [NEW] Escape plus character in apt HTTPS requests to work around Amazon S3 bug

[Touch-packages] [Bug 1003633] Re: Escape plus character in apt HTTP requests to work around Amazon S3 bug

[Touch-packages] [Bug 1442775] [NEW] apt-get --ignore-missing doesn't ignore missing packages

12 matches

Site Navigation

Mail list logo

Footer information