Re: [Bug 1906946] Re: please sync rust-signal-hook 0.1.13-1 from sid
On Sun, Dec 13, 2020 at 09:02:45AM -, Hans Joachim Desserud wrote: > I've subscribed ubuntu-sponsors to take a look at this sync request. > (For more info about syncs, see > https://wiki.ubuntu.com/SyncRequestProcess) Thank you! > Note that while rust-tokio-reactor has been re-addded, it seems to have > failed to build on most architectures > https://launchpad.net/ubuntu/+source/rust-tokio-reactor/0.1.8-2 . So > while I assume rust-signal-hook can be synced, it might have problems > building if it cannot find all dependencies. Interesting. Is there a way to trigger a rebuild of rust-tokio-reactor? The build failed on 2020-11-24 because of a missing depencency: The following packages have unmet dependencies: librust-rand-chacha+std-dev : Depends: librust-ppv-lite86-0.2+std-dev (>= 0.2.6-~~) librust-rand-chacha-dev : Depends: librust-ppv-lite86-0.2+simd-dev (>= 0.2.6-~~) E: Unable to correct problems, you have held broken packages. And looking at librust-ppv-lite86-0.2, I see that it has been updated in the meantime: https://launchpad.net/ubuntu/+source/rust-ppv- lite86/0.2.6-2/+publishinghistory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906946 Title: please sync rust-signal-hook 0.1.13-1 from sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906946] Re: please sync rust-signal-hook 0.1.13-1 from sid
** Also affects: rust-condure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906946 Title: please sync rust-signal-hook 0.1.13-1 from sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906946] [NEW] please sync rust-signal-hook 0.1.13-1 from sid
Public bug reported: It seems like rust-signal-hook was removed from ubuntu on 2020-09-14 because of a missing dependency, rust-tokio-reactor. As rust-tokio-reactor 0.1.8-2 was successfully synced from debian on 2020-11-05, rust-signal-hook could be included again, as well. This would be helpful as it would fix the build of rust-condure, see https://launchpad.net/ubuntu/+source/rust- condure/1.1.0-1/+build/20367268 Thanks! ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906946 Title: please sync rust-signal-hook 0.1.13-1 from sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1906946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553376] Re: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main)
After setting up a xenial build environment, here is the build log of pushpin_1.8.0-2. ** Attachment added: "pushpin_1.8.0-2_amd64.build" https://bugs.launchpad.net/bugs/1553376/+attachment/4601023/+files/pushpin_1.8.0-2_amd64.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553376 Title: [ffe] Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1553376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553377] Build log etc.
Please find attached: - build log of zurl 1.5.1-1 on xenial - diff of upstream changelog Output during installation is: root@xenial:/tmp# dpkg -i zurl_1.5.1-1_amd64.deb (Reading database ... 12658 files and directories currently installed.) Preparing to unpack zurl_1.5.1-1_amd64.deb ... Unpacking zurl (1.5.1-1) over (1.5.1-1) ... Setting up zurl (1.5.1-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-2ubuntu1) ... root@xenial:/tmp# The service can be started and successfully forwards request on behalf of pushpin. Best regards, Jan ** Patch added: "changelog.diff" https://bugs.launchpad.net/bugs/1553377/+attachment/4601054/+files/changelog.diff ** Attachment added: "zurl_1.5.1-1_amd64.build" https://bugs.launchpad.net/bugs/1553377/+attachment/4601055/+files/zurl_1.5.1-1_amd64.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553377 Title: [ffe] Sync zurl 1.5.1-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zurl/+bug/1553377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553376] Re: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main)
On Tue, Mar 15, 2016 at 06:36:07PM -, Sebastien Bacher wrote: > see https://wiki.ubuntu.com/FreezeExceptionProcess about how to do a ffe > request As stated above in https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1553376/comments/2, I know the process, but I don't have a xenial installation at hand. If it's really necessary - and makes it likely that the package will be synced - I can setup a machine to provide the build log. An installtion on debian/sid looks quite boring: root@sid:~# dpkg -i /tmp/pushpin_1.8.0-2_amd64.deb Selecting previously unselected package pushpin. (Reading database ... 23057 files and directories currently installed.) Preparing to unpack /tmp/pushpin_1.8.0-2_amd64.deb ... Unpacking pushpin (1.8.0-2) ... Setting up pushpin (1.8.0-2) ... Processing triggers for systemd (229-1) ... Processing triggers for man-db (2.7.5-1) ... root@sid:~# Installation was also tested on older versions of debian (wheezy) and ubuntu (trusty, vivid, wily). Forwarding requests through pushpin and zurl was tested on all these distributions. changelog.diff and build log are attached. Best regards, Jan ** Attachment added: "pushpin_1.8.0-2_amd64.build" https://bugs.launchpad.net/bugs/1553376/+attachment/4600373/+files/pushpin_1.8.0-2_amd64.build ** Patch added: "changelog.diff" https://bugs.launchpad.net/bugs/1553376/+attachment/4600374/+files/changelog.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553376 Title: [ffe] Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1553376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553376] Re: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) / [Bug 1553377] [NEW] Sync zurl 1.5.1-1 (universe) from Debian unstable (main)
Hi, On Sat, Mar 12, 2016 at 11:26:42AM +0100, Jan Niehusmann wrote: > That's true, 1.8.0 isn't just a bugfix release. I still think that > syncing pushpin 1.8.0 and zurl 1.5.1 would be beneficial for 16.04 LTS: As an additional note regarding zurl: Here, the porting to qt5 was done with release 1.5.0, which is already in Xenial. The changes between 1.5.0 and 1.5.1 are really minor. (Full diff attached.) For pushpin, it's true that 1.8.0 contains the port to qt5, so there are quite some code changes. As pushpin and zurl usually go together, having one depending on qt4 and the other one depending on qt5 could needlessly bloat installations. (Probably only relevant to dedicated servers, but especially with containers this is a likely setup.) Due to the nature of the changes, I consider it highly unlikely that the update breaks something outside of the package itself. Best regards, Jan ** Patch added: "zurl_1.5.0-1_1.5.1-1.diff" https://bugs.launchpad.net/bugs/1553377/+attachment/4596877/+files/zurl_1.5.0-1_1.5.1-1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553377 Title: Sync zurl 1.5.1-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zurl/+bug/1553377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553376] Re: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) / [Bug 1553377] [NEW] Sync zurl 1.5.1-1 (universe) from Debian unstable (main)
Hi Timo, thanks for looking at the sync request, On Fri, Mar 11, 2016 at 11:29:54AM -, Timo Jyrinki wrote: > The porting work to Qt 5 is substantial and there seem to be also > internal code refactorings, as seen at the commits at > http://anonscm.debian.org/cgit/users/jan/pushpin.git/log/?h=upstream > after the (not tagged) 1.7.0 release. > > This could also be synced after 16.04 LTS is released in April, to the > next development Ubuntu version 16.10. That's true, 1.8.0 isn't just a bugfix release. I still think that syncing pushpin 1.8.0 and zurl 1.5.1 would be beneficial for 16.04 LTS: The intention of the sync request is mainly to have a consistent codebase for long term support. If 16.04 releases with a version based on Qt4, the increased effort to backport bug fixes could mean that fixes are delayed, or that less important fixes won't be backported, at all. I have built both packages for debian unstable, jessie and wheezy, as well as ubuntu trusty, vivid and wily. If you think it will help getting the newer versions into 16.04 LTS, I can install Xenial and create the logs requested in https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_Exceptions. But please note that, as a debian developer, I don't have the required ubuntu infrastructure readily available. So I'd rather not do that work if it's unlikely to get the packages synced at all. Best regards, Jan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553376 Title: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1553376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553376] [NEW] Sync pushpin 1.8.0-2 (universe) from Debian unstable (main)
Public bug reported: Please sync pushpin 1.8.0-2 (universe) from Debian unstable (main) Changelog entries since current xenial version 1.7.0-1: pushpin (1.8.0-2) unstable; urgency=medium * Remove dependency on python-tnetstring and python-zmq. They got obsolete because pushpin-publish was rewritten in C++. -- Jan Niehusmann <j...@debian.org> Thu, 03 Mar 2016 20:43:22 +0100 pushpin (1.8.0-1) unstable; urgency=medium * New upstream version * apply hardening flags via ./configure --extraconf * Remove internal.conf from /etc/pushpin/; it was never meant to be modified locally. -- Jan Niehusmann <j...@debian.org> Thu, 25 Feb 2016 16:17:33 +0100 Upstream changelog for 1.8.0: v. 1.8.0 (2016-02-22) * Fix issue proxying large responses. * Refactor README. * Port server code to Qt 5. * Rewrite pushpin-publish tool from Python to C++. * Move internal.conf into LIBDIR. ** Affects: pushpin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553376 Title: Sync pushpin 1.8.0-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1553376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553377] [NEW] Sync zurl 1.5.1-1 (universe) from Debian unstable (main)
Public bug reported: Please sync zurl 1.5.1-1 (universe) from Debian unstable (main) Changelog entries since current xenial version 1.5.0-1: zurl (1.5.1-1) unstable; urgency=medium * New upstream version * Set Standards-Version to 3.9.7 * Fix lintian warning "command-with-path-in-maintainer-script" -- Jan Niehusmann <j...@debian.org> Thu, 03 Mar 2016 23:13:20 +0100 Upstream changelog: v. 1.5.1 (2016-02-21) * Don't install tests. * Fix crash when using --version. * Output compact JSON (to match 1.4 behavior). v. 1.5.0 (2016-02-12) * Port to Qt 5. * Drop libqjson dependency since Qt 5 has JSON support built-in. ** Affects: zurl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553377 Title: Sync zurl 1.5.1-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zurl/+bug/1553377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434123] Re: please sync pushpin 1.1.0 from debian
Install log. Just boring :-) ** Attachment added: install.log https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1434123/+attachment/4350063/+files/install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434123 Title: please sync pushpin 1.1.0 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1434123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434123] Re: please sync pushpin 1.1.0 from debian
Compile log. Built on a system which was freshly installed and upgraded to vivivd. ** Attachment added: compile.log https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1434123/+attachment/4350062/+files/compile.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434123 Title: please sync pushpin 1.1.0 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1434123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434123] [NEW] please sync pushpin 1.1.0 from debian
Public bug reported: Upstream provided a new version (1.1.0) of pushpin, which I packaged for debian. Upstream asked me if it would be possible to sync this update to ubuntu, even though 15.04 is in FeatureFreeze, now. There is no changelog file, instead I attached the git log. One major feature was added, websocket support. ** Affects: pushpin (Ubuntu) Importance: Undecided Status: New ** Attachment added: Changes from git log https://bugs.launchpad.net/bugs/1434123/+attachment/4350059/+files/changes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434123 Title: please sync pushpin 1.1.0 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1434123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373128] [NEW] Sync pushpin 1.0.0-3 (universe) from Debian unstable (main)
Public bug reported: Please sync pushpin 1.0.0-3 (universe) from Debian unstable (main) Changelog entries since current utopic version 0.0~20140620-1: pushpin (1.0.0-3) unstable; urgency=low * Fix typo in debian/rules, which prevented proper use of hardening flags. -- Jan Niehusmann j...@debian.org Thu, 18 Sep 2014 20:24:58 +0200 pushpin (1.0.0-2) unstable; urgency=low * Remove dependencies on redis-server, python-redis -- Jan Niehusmann j...@debian.org Tue, 16 Sep 2014 23:51:11 +0200 pushpin (1.0.0-1) unstable; urgency=low * New upstream version 1.0.0 * Update Vcs URL * implement hardening using buildflags instead of hardening-wrapper -- Jan Niehusmann j...@debian.org Tue, 16 Sep 2014 21:51:41 +0200 ** Affects: pushpin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373128 Title: Sync pushpin 1.0.0-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1373128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373128] Re: Sync pushpin 1.0.0-3 (universe) from Debian unstable (main)
What I should have mentioned in the report: This is the first official release of pushpin, and utopic will be the first release to contain pushpin. So the number of users affected by a late sync should be close to zero. Additionally, the upstream author explicitly asked my if I could try to sync the 1.0.0 version to ubuntu, so there is a common baseline, instead of some random development snapshot. The changes were mainly bug fixes, but also some new features (websocket support). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373128 Title: Sync pushpin 1.0.0-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pushpin/+bug/1373128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212813] Re: PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.]
Ninad: The description of the psi package contains the following text: Psi relies on the qca2 library for its encryption features. Therefore, it's necessary to install libqca2-plugin-ossl for SSL (client-to-server) encryption and libqca2-plugin-gnupg for PGP (end-to-end) encryption. Isn't this exactly what you are asking for? -- PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to decrypt it.] https://bugs.launchpad.net/bugs/212813 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258434] Re: psi segfault
This looks like the same bug as debian bug #485597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485597 It's not a psi bug, but a bug in the qt4 binary, probably caused by an incompatibility with some versions of gcc. In debian, it was resolved with a more recent upload of qt4, which was compiled with a newer version of gcc. -- psi segfault https://bugs.launchpad.net/bugs/258434 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 229614] Re: psi crashes on appearance options
This bug is fixed in debian since 0.11-6: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475748 AFAICT, ubuntu upgraded to the debian 0.11-8 package by now, so this should be fixed in ubuntu, as well. -- psi crashes on appearance options https://bugs.launchpad.net/bugs/229614 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115773] Re: ipv6 disabled
There are reasons upstream is using NDns instead of QDns (mainly bad experience with QDns stability). Therefore, I won't change the debian package to use QDns. However, there are plans to replace NDns with XMPP::NameResolver, which should support IPv6 as well. -- ipv6 disabled https://bugs.launchpad.net/bugs/115773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
