https://salsa.debian.org/debian/uim/-/merge_requests/9
This is the fix request.
Could you review the patch?
2020年12月14日(月) 18:24 :
> On Sun, Dec 13, 2020 at 02:35:58PM +0900, Takatsugu Nokubi wrote:
> > I made a simple patch to skip test-composer:
> >
> https://salsa.deb
On Sat, 31 Oct 2020 21:52:30 +0300 Dmitry Shachnev wrote:
> Control: unblock 972278 by -1
> > It built for me on abel, which is exactly the same hardware as the
> > buildds where it failed.
> >
> > This makes it feel more like a generic race condition that only happened
> > to hit here than an arm
Tue, Nov 17, 2020 at 09:11:54AM +0900, Takatsugu Nokubi wrote:
> > I need the test2/test-suite.log file, so I had tried to reproduce it
> > on abel twice, but
> > I couldn't get the error, just succeeded.
> >
> > Can I get the test2/test-suite.log file from
On Mon, 27 Jan 2020 15:18:15 +0900 NOKUBI Takatsugu wrote:
> We uim maintainers had an another probrem #945344.
> The last update registers unusable uim modules.
The last diff lacks some commits, here is a new diff.
https://salsa.debian.org/debian/uim/snippets/386
diff --git a/debian/changelog b
2020年1月29日(水) 7:37 Adam D. Barratt :
> Are all of these changes already applied to the package in unstable?
This fix is not necessary in unstable, because libuim-data is removed
on unstable.
At first, this transition had coded in buster, but it had canceled
because of postinst bug,
so the last bus
On Mon, 1 Jul 2019 15:24:05 +0200 Sylvain Beucler wrote:
> The following vulnerabilities were published for libsixel.
Finaly, I made these fix patches, but not uploaded yet.
https://salsa.debian.org/debian/libsixel/tree/master/debian/patches
> AFAICS upstream didn't act on them yet (see issues l
On Sat, 21 Sep 2019 20:47:25 +0100 "Adam D. Barratt"
wrote:
> Control: tags -1 + moreinfo
> What environment were the amd64 packages that you uploaded built in?
Sorry, I had built on a stretch environment, so I rebuild it with
git-pbuilder environment,
tested with piuparts, and had uploaded.
On Thu, 19 Sep 2019 06:12:14 +0100 "Adam D. Barratt"
wrote:
> That version is higher than the package in unstable, which is wrong.
Now newest uim package is in unstable.
> Moreover, the package obviously landed in NEW. I have asked ftp-master
> to reject it, partly due to the broken version numb
On Sat, 07 Sep 2019 01:40:06 +0900 NIDE Naoyuki wrote:
> Dear Maintainer,
>
> On a 'buster' system that is upgraded from 'stretch', uim lacks the following
> two files:
> /var/lib/uim/installed-modules.scm
> /var/lib/uim/loader.scm
> These files existed when the system was 'stretch', but after upg
On Tue, 10 Sep 2019 21:34:23 +0900 (JST) "NIDE, Naoyuki"
wrote:
> For test, I installed stretch, and upgraded it to buster. After that,
> some stretch packages which have been removed during upgrading to buster
> leaved conf files.
>
> buster$ dpkg -l | egrep -v ^ii
> Desired=Unknown/Install/Remov
On Tue, 10 Sep 2019 21:34:23 +0900 (JST) "NIDE, Naoyuki"
wrote:
> buster# apt-get purge $(dpkg -l | awk '$1=="rc"{print $2}')
>
> Then, when libuim-data is purged, /var/lib/uim/installed-modules.scm
> and /var/lib/uim/loader.scm are disappeared, since the postrm script of
> libuim-data deletes the
On Thu, 19 Sep 2019 16:34:48 +0900 (JST) "NIDE, Naoyuki"
wrote:
> Perhaps the reason is:
>
> buster$ dpkg-query -W -f='${Status}\n' uim-tcode
> dpkg-query: no packages found matching uim-tcode
You are right. I added to check dpkg-query status to the script:
https://salsa.debian.org/snippets/327
On Thu, 19 Sep 2019 09:46:30 +0900 NOKUBI Takatsugu wrote:
> I'll upload a new version of libsixel for buster.
> It contains many security fix reported by #931311
The package is insufficient, so we updated the package source.
https://salsa.debian.org/debian/uim/commit/374d44663f4c477db91ffa1dfb01
On Fri, 20 Sep 2019 11:35:55 +0900 (JST) "NIDE, Naoyuki"
wrote:
> > https://salsa.debian.org/debian/uim/blob/buster/debian/libuim-data.postinst
>
> It worked in my environment.
> However, it does not include register_module line for uim-mozc. Is it right?
Exactly.
https://salsa.debian.org/debian/
2020年1月29日(水) 8:48 Takatsugu Nokubi :
> This fix is not necessary in unstable, because libuim-data is removed
> on unstable.
It was incorrect. I'll update unstable for this issue.
2020年1月30日(木) 9:18 Takatsugu Nokubi :
> > This fix is not necessary in unstable, because libuim-data is removed
> > on unstable.
>
> It was incorrect. I'll update unstable for this issue.
I uploaded unstable.
2020年1月30日(木) 10:21 Takatsugu Nokubi :
> > > This fix is not necessary in unstable, because libuim-data is removed
> > > on unstable.
> >
> > It was incorrect. I'll update unstable for this issue.
>
> I uploaded unstable.
Sorry, it was incorrect, the firs
On Sat, 16 May 2020 18:31:50 +0900 Hideki Yamane wrote:
> It seems that chasen is failed to build with clang.
>
> https://github.com/opencollab/clang.debian.net/blob/master/logs/2020-02-24-9.0.1/chasen_2.4.5-44_unstable_clang9.0.1.log
I tried to make fix it, but still failed.
The patch is http
-01-30 at 19:24 +0900, Takatsugu Nokubi wrote:
> > 2020年1月30日(木) 10:21 Takatsugu Nokubi :
> > > > > This fix is not necessary in unstable, because libuim-data is
> > > > > removed
> > > > > on unstable.
> > > >
> > > > It was in
Package: icinga2-bin
Version: 2.31-13+deb11u3
Severity: grave
Depends: icinga2-common (= 2.13.5-1.buster), libboost-atomic1.67.0,
libboost-chrono1.67.0, libboost-context1.67.0, libboost-coroutine1.67.0,
libboost-date-time1.67.0, libboost-filesystem1.67.0,
libboost-iostreams1.67.0, libboost-program
I made a simple patch to skip test-composer:
https://salsa.debian.org/debian/uim/-/commit/3cd351b6f2b15fb3161e1d00ed4c8ba26925429b
(Oh, I forgot to fix description of the patch)
2020年12月13日(日) 10:36 :
> Control: forwarded -1 https://github.com/uim/uim/issues/167
>
> On Sat, Dec 12, 2020 at 02:50
On Wed, 7 Aug 2019 10:05:36 +0900 Takatsugu Nokubi wrote:
> Finaly, I made these fix patches, but not uploaded yet.
> https://salsa.debian.org/debian/libsixel/tree/master/debian/patches
At least, all bugs reported as important are fixed now.
I'm working to fix patches for str
On Tue, 16 Apr 2019 00:20:49 +0900 (JST) Tatsuya Kinoshita
wrote:
> On April 6, 2018 at 10:58PM +0900, tats (at debian.org) wrote:
> >> $ perl -c /usr/share/namazu/filter/hnf.pl
> >> Unescaped left brace in regex is illegal here in regex; marked by <--
HERE in m/%{ <-- HERE ?([a-z]+)}?/ at /usr/sh
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking namazu2, fixing to work with erarier perl
that include buster's perl.
Changes:
namazu2 (2.0.21-22) unstable; urgency=medium
* d/p/0002-escape-branckets.patch:
I don't know why your mailman3-web was broken, anyway I can fix the problem
with the following steps:
* add config to /etc/mailman3/mailman-web.py
```
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
Q_CLUSTER = {
'timeout': 300,
'retry': 600,
'save_limit': 100,
'orm': 'defaul
I have same problem.
I tried to downgrade old (deb7u4) package and check again, it works fine.
Currentry disabling SSLCertificateChainFile is a workaround, but
it causes failing SSL certificate verify process.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
There is a similar issue, especially systemd environment.
The wheezy installer add serial console getty section in inittab,
but jessie's systemd seems no care.
I need to execute "systemctl enable serial-getty@ttyS0.service"
manually to enable serial console login.
--
To UNSUBSCRIBE, email to de
Sorry fo late reply.
I tried it with rebuilded deb because I use i386 arch.
So it seems to work fine.
I don't need to replace mod_ssl.so in my situation.
2015-08-08 6:18 GMT+09:00 Stefan Fritsch :
> Please try the version from https://people.debian.org/~sf/794383/
> and check if it either fixes t
On Sat, 18 Mar 2017 14:46:30 +0100 Andreas Beckmann wrote:
> apt-get install libuim-data
> apt-get install uim-utils
>
> causes /var/lib/uim/* not to be generated, since uim-module-manager
> is not available at the time libuim-data gets configured.
I think there are two way to fix it:
1. add
On Sat, 13 Feb 2016 15:37:43 +0100 Andreas Beckmann wrote:
> You shouldn't use dpkg-architecture from maintainer scripts
> but resolve the architecture specific bits at package build time.
This problem was fixed in 2.4.5-24.
On Fri, 22 Sep 2017 23:20:39 +0900 Osamu Aoki wrote:
> On Fri, Sep 22, 2017 at 09:14:22AM +0200, John Paul Adrian Glaubitz wrote:
> > This FTBFS can be easily fixed with:
> >
> > --- ibus-anthy-1.5.9.orig/data/zipcode-textdic.py
> > +++ ibus-anthy-1.5.9/data/zipcode-textdic.py
> > @@ -21,7 +21,7 @
On Mon, 30 Oct 2017 21:14:18 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > checking where the gettext function comes from... libc
> > checking for GTK2... yes
> > checking for GTK2_4... yes
> > che
On Wed, 05 Feb 2014 21:14:27 + Robert Millan wrote:
> On 05/02/2014 20:50, Axel Beckert wrote:
> > Another possibility would be to make an arch:kfreebsd-any to depend on
> > (or maybe recommend) it, or make an arch:any package to depend on (or
> > maybe recommend) it only on kfreebsd-any.
>
>
On Fri, 17 Oct 2014 13:09:19 +0900 Kenshi Muto wrote:
> At Fri, 17 Oct 2014 05:57:30 +0200,
> I myself don't matter about systemd, but
> I heared there was a bootup problem when one created a root
> system for container (such as LXC) with using debootstrap.
> (though I'm not sure about this.)
I t
On Wed, 13 Mar 2024 13:03:57 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /bin/bash ../libtool --tag=CC --mode=link gcc -g -O2
> > -Werror=implicit-function-declaration -ffile-prefix-map=/<
35 matches
Mail list logo