[Touch-packages] [Bug 1840221] [NEW] libcurl built without libssh2/sftp/scp support <= 18.04
Public bug reported: Recently I found that in distributions <=18.04 libcurl is built without libssh2 and therefore does not support the sftp/scp protocols. I am not sure if this is a bug, but maybe this should be added per default as its the case on 19.10 for example. ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: curl libcurl libssh2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1840221 Title: libcurl built without libssh2/sftp/scp support <= 18.04 Status in curl package in Ubuntu: New Bug description: Recently I found that in distributions <=18.04 libcurl is built without libssh2 and therefore does not support the sftp/scp protocols. I am not sure if this is a bug, but maybe this should be added per default as its the case on 19.10 for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1840221/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
Easy workaround which does not require another apt-setup.udeb: d-i preseed/late_commandstring \ in-target wget -q -O /etc/apt/trusted.gpg.d/bla.asc http://bla.de/bla.asc ; \ in-target sed -i '/keyword to uncomment specific line in file/s/^# *//' /etc/apt/sources.list ; \ in-target apt-get update ; \ in-target apt-get -y install packages to install ; -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
I guess every sysadmin installing an agent-based configuration management system via di will experience this problem, too. Funny how there was no progress on this in half a year. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1380976] Re: Limiting queue disk space does not work, upgrade needed
I confirmed this bug as it still affects 7.4.4-1ubuntu2.7 from trusty- updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1380976 Title: Limiting queue disk space does not work, upgrade needed Status in rsyslog package in Ubuntu: Confirmed Bug description: # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy rsyslog rsyslog: Installed: 7.4.4-1ubuntu2.3 Candidate: 7.4.4-1ubuntu2.3 Version table: [...] When rsyslog is run with a config to save/cache log to disk, e.g when the host that it is forwarding log to is not responding, it fails to respect the maxdiskspace parameter. This is a known bug and 7.4.7 of v7-stable has been released to fix this, see http://www.rsyslog.com/changelog-for-7-4-7-v7-stable/ Config for testing: global( workDirectory="/tmp" ) module(load="imudp") module(load="omrelp") input(type="imudp" port="514" ) action(type="omrelp" target="localhost" port="2514" action.resumeRetryCount="-1" queue.saveonshutdown="on" queue.type="LinkedList" queue.filename="omrelp" queue.maxfilesize="100M" queue.maxdiskspace="1M" queue.checkpointinterval="100" queue.highwatermark="10" ) Then just log more than 1MB of messages to UDP to see that it doesn't stop at 1MB but just continues forever. Please upgrade the package to 7.4.7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1380976/+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 1673717] Re: rsyslog GnuTLS error -50
Test case Step 1: Create a rsyslog-config using gtls: /etc/rsyslog.d/10-tlstest.conf Step 2: To generate the needed ca-, key-, cert-files, follow the guide at http://www.rsyslog.com/doc/v8-stable/tutorials/tls.html#certificates Step 3: Setup a client, which relays logs to the server that was just set up Step 4: Check the rsyslog-log for the errors mentioned in the initial post. ** Attachment added: "10-tlstest.conf" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+attachment/4973253/+files/10-tlstest.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: Confirmed Status in rsyslog package in Debian: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+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
