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
** 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
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
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
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 ...
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
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 r
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
>
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
mo
-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.
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.
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
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
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
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
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
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
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
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
19 matches
Mail list logo
