Am Mi., 12. Sep. 2018 um 14:33 Uhr schrieb Andreas Tille :
>
> Control: tags -1 help
>
> Sorry, I have no idea what to do. Any help is welcome.
This is a bug in LLVM that is now being tracked at
https://bugs.llvm.org/show_bug.cgi?id=38931
Cheers,
Matthias
--
I welcome VSRE emails. See http
Am Sa., 22. Sep. 2018 um 21:45 Uhr schrieb Adrian Bunk :
>
> Control: tags 906971 + pending
> Dear maintainer,
>
> I've prepared an NMU for apper (versioned as 1.0.0-1.1) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it.
It's fine, sorry for not acting on the bug
2017-11-03 11:34 GMT+01:00 Julien Cristau :
> On 11/03/2017 11:25 AM, Julien Cristau wrote:
>> Package: appstream
>> Severity: grave
>> X-Debbugs-Cc: ftpmas...@ftp-master.debian.org
>>
>> [filing this against the appstream package as a substitute for
>> appstream.debian.org, feel free to reassign i
2017-11-05 14:23 GMT+01:00 Adrian Bunk :
> Source: appstream-generator
> Version: 0.6.7-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/appstream-generator.html
This is resolved upstream, will be fixed in the next release.
See
https://github.com/ximion
60147fc04a6fee42c7a621161ff72160c435d832
Author: Matthias Klumpp
Date: Tue Mar 7 23:34:29 2017 +0100
Finalize changelog for 1.5.2-2
diff --git a/debian/changelog b/debian/changelog
index 409cbc3..5bfb235 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+terminix (1.5.2-2) unstable; urgency=medium
2018-07-21 13:32 GMT+02:00 Paul Gevers :
> Hi Peter,
>
> On 21-07-18 13:16, peter green wrote:
>>> +
>>> _Z27qRegisterNormalizedMetaTypeIP7QActionEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBuiltInEE11DefinedTypeE@Base
>>> 2.6~beta-4
>>>
>
2018-08-18 9:39 GMT+02:00 Johannes Rohr :
> Package: appstream
> Version: 0.12.2-1
> Severity: critical
> Justification: breaks unrelated software
>
> as of today, apt-get upstream fails because appstreamcli crashes as follows:
>
> sudo appstreamcli refresh-cache
>
> (appstreamcli:7230): GLib-CRITI
Am Di., 28. Aug. 2018 um 10:40 Uhr schrieb Andreas Tille :
>
> On Tue, Aug 28, 2018 at 10:12:32AM +0300, Adrian Bunk wrote:
> > Source: libbiod
> > Version: 0.1.0-5
> > Severity: serious
> > Tags: ftbfs
> >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libbiod.html
> >
> >
Am Di., 28. Aug. 2018 um 15:39 Uhr schrieb Matthias Klumpp :
>
> Am Di., 28. Aug. 2018 um 10:40 Uhr schrieb Andreas Tille :
> >
> > On Tue, Aug 28, 2018 at 10:12:32AM +0300, Adrian Bunk wrote:
> > > Source: libbiod
> > > Version: 0.1.0-5
> > > Severity
Am Di., 28. Aug. 2018 um 20:16 Uhr schrieb Andreas Tille :
>
> Control: tags -1 help
>
> Hi Matthias,
>
> do you have any idea? Its most probably connected to the
> libbiod bug.
> [...]
This appears to be a different issue to me - this one is a bit weirder
than the BioD one. You can either apply
Am Mi., 29. Aug. 2018 um 19:56 Uhr schrieb Andreas Tille :
>
> Hi Matthias,
> On Tue, Aug 28, 2018 at 03:39:56PM +0200, Matthias Klumpp wrote:
> > > > ...
> > > > [30/149] ldc2 -Ibiod@sha -I. -I.. -I -I../ -I/usr/include/d
> > > > -enable-color -
Hi!
After a conversation with upstream, this issue won't be fixed anytime soon.
So a removal request for the ppc64el binaries was filed instead.
Cheers,
Matthias
Am Do., 10. Jan. 2019 um 08:48 Uhr schrieb Andreas Tille :
>
> Control: forwarded -1 https://github.com/biod/BioD/issues/50
> Control: tags -1 help upstream
>
> Dear Matthias,
>
> unfortunately there is another issue with libbiod and as usual I need
> your help due to my total incompetence in D. :-
Hi!
I am inclined to demote the priority of this issue to "important", because:
1) The automatic download will not happen unless there is a WiFi connection
- downloading over potentially expensive connections does not happen.
2) It does not beak the system on stable machines. It might do so on
un
2015-08-28 18:30 GMT+02:00 Steve McIntyre :
> Matthias Klump wrote:
> >Hi!
> >I am inclined to demote the priority of this issue to "important",
> because:
> >
> >1) The automatic download will not happen unless there is a WiFi
> connection
> >- downloading over potentially expensive connections d
Hi Andreas!
This RC bug has nothing to do with gnome-packagekit, and
update-notifier was deleted from the archive in 2014. Was this issue
reassigned in error?
Thanks!
Matthias
--
I welcome VSRE emails. See http://vsre.info/
Am Do., 1. Aug. 2019 um 17:15 Uhr schrieb Andreas Ronnquist :
>
> severity 931825 grave
> thanks
>
> On Thu, 11 Jul 2019 00:12:56 +0300 Jussi Pakkanen
> wrote:
> > Package: dub
> > Version: 1.12.1-1
> >
> > Installing dub on Debian unstable (tested on x86 and x64) and then
> > running "dub" errors
clone 931825 -1
reassign -1 gdc-8 8.3.0-6
retitle -1 gdc-8: Unable to link D applications against runtime/stdlib
thankyou
This issue is actually bigger than I thought You currently can't
even rebuild dub with GDC, because the linking step fails when linking
against Phobos/DRuntime:
```
gdc -Wa
Hi Salvatore!
Am Di., 25. Mai 2021 um 06:51 Uhr schrieb Debian Bug Tracking System
:
>
> Processing commands for cont...@bugs.debian.org:
>
> > found 989049 0.4.2-1
> Bug #989049 {Done: Matthias Klumpp } [debspawn] debspawn:
> privilege escalation via uid reuse
> There i
Am Di., 25. Mai 2021 um 13:21 Uhr schrieb Salvatore Bonaccorso
:
> [...]
> >
> > Can you please elaborate on why you reopened this issue? I believe it
> > has indeed been addressed with version 0.4.2-1, there is no more uid
> > reuse for the build user and Debspawn will pick a free uid that is not
Hi!
This mail just touches the debspawn RC bugs to maybe prevent an early
autoremoval, if that's still a thing during soft-freeze.
I need some extra time to sort out the package's migration, as it will
not automatically migrate due to Debian's CI not having the machines
to run the autopkgtest of th
Am Mi., 6. Mai 2020 um 19:57 Uhr schrieb Markus Frosch :
>
> Package: appstream-generator
> Version: 0.8.1-1+b1
> Severity: grave
> Justification: renders package unusable
>
> Hi maintainer,
> the package possible needs rebuilding.
>
> > appstream-generator: error while loading shared libraries: li
Control: tag -1 pending
Hello,
Bug #968816 in gtk-d reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/gtk-d/-/commit/87936be72ed396cb0e9511d07ef75fb9bc
Hi Ivo!
Am Di., 23. Feb. 2021 um 00:03 Uhr schrieb Ivo De Decker :
>
> Hi Matthias,
>
> On Wed, Jan 20, 2021 at 09:48:32PM +0100, Lucas Nussbaum wrote:
> > Source: ldc
> > Version: 1:1.24.0-1
> > Severity: serious
> > Justification: FTBFS on amd64
> > Tags: bullseye sid ftbfs
> > Usertags: ftbfs-2
Am Di., 10. Nov. 2020 um 01:08 Uhr schrieb Petter Reinholdtsen
:
>
> [Gunnar Hjalmarsson]
> > On an updated Debian testing:
> >
> > $ isenkram-lookup
> > /usr/lib/python3/dist-packages/isenkram/lookup.py:85: Warning invalid
> > uninstantiatable type '(null)' in cast to 'AsProvided'
> >provided
Am Do., 28. Jan. 2021 um 00:33 Uhr schrieb Sebastian Ramacher
:
>
> Source: dub
> Version: 1.24.0-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> | autopkgtest [03:11:10]: test run: [---
> | Package dub not found for registry at https://code.dlang.org/ (fallbacks
Am Do., 12. Nov. 2020 um 22:21 Uhr schrieb Gunnar Hjalmarsson
:
>
> On 2020-11-12 21:28, Petter Reinholdtsen wrote:
> > [Gunnar Hjalmarsson]
> >> Additional observations:
> >>
> >> * The testing failure in Ubuntu started around October 31.
> >>
> >> * The test-command-line script fails on amd64 and
Am Do., 12. Nov. 2020 um 23:20 Uhr schrieb Matthias Klumpp :
> [...]
> You want this patch for AppStream:
> https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
> Basically, Python thought it could free more objects than it should
> actually have freed
Am Fr., 13. Nov. 2020 um 01:28 Uhr schrieb Gunnar Hjalmarsson
:
>
> On 2020-11-12 23:20, Matthias Klumpp wrote:
> > You want this patch for AppStream:
> > https://github.com/ximion/appstream/commit/b52858bff55d358f925b8e64bab77b953067f248
>
> But only comments are change
2017-05-22 7:17 GMT+02:00 Petter Reinholdtsen :
> I was sad to discover that ldc and all its dependencies were removed from
> testing
> today because of this issue.
>
> I guess no-one succeeded in figuring out what go wrong here?
Eww, I completely forgot to reply to the bug report yesterday to de
Regarding the issue: The cause for it remains elusive to me. There is
a bug happening on Debian's i386 buildds which apparently is the same
thing that's happening on the armhf architecture, but I failed to
reproduce it locally (built LDC 8 times in a row in a pristine Sid
chroot with no failure, wh
2017-05-22 13:32 GMT+02:00 Matthias Klumpp :
> [...]
> Sorry, I think I screwed up here (I thought the expiration date was
> 25.May for some reason).
I learned just now that jcristau force-hinted LDC out yesterday,
although he knew that I already comitted a workaround (dropping a
Cc Sylvestre Ledru as he maintains LLVM and might know best about
changes done in the LLVM toolchain in Debian.
I uploaded an LDC to unstable yesterday with no changes but it's LLVM
dependency changed to build against LLVM 4.0. With that version, the
bug did not happen at all on the buildds.
To be
2017-03-25 22:27 GMT+01:00 Rene Engelhard :
> [ I am NOT the plasma-discover maintainer ]
>
> On Sat, Mar 25, 2017 at 12:53:20PM -0400, Leand wrote:
>>There are basic functions that are bugged. For example, the search
>>function returns wrong and unrelated results too many times. If I
>>
2017-03-31 18:16 GMT+02:00 Adrian Bunk :
> If I understand the situation correctly:
>
> 1. The only known RC issue here is that terminix frequently (but not always)
>FTBFS on armhf, and
> 2. no other package or architecture is known to be affected, and
> 3. looking at the upstream bug the root
2017-03-31 18:38 GMT+02:00 Adrian Bunk :
> On Fri, Mar 31, 2017 at 06:24:46PM +0200, Matthias Klumpp wrote:
>> 2017-03-31 18:16 GMT+02:00 Adrian Bunk :
>> > If I understand the situation correctly:
>> >
>> > 1. The only known RC issue here is that termi
something good
came out of it.
Any help would be highly appreciated!
Cheers,
Matthias Klumpp
[1]:
https://buildd.debian.org/status/fetch.php?pkg=ldc&arch=i386&ver=1%3A1.1.1-3&stamp=1493055455&raw=0
2017-04-25 8:27 GMT+02:00 Iain Buclaw :
> [...]
> If running in gdb makes the problem go away, have you tried turning on
> core dumps in buildd?
Yes, without useful results:
https://github.com/ldc-developers/ldc/issues/2022#issuecomment-288481397
Okay, the actual problem here is not the shlibs file, but upstream
breaking API without bumping the SONAME of the library.
I will raise this upstream, so we can find a way to deal with this
issue for all distros and not just Debian (the result might be that we
just always bump the version each time
2017-07-11 10:46 GMT+02:00 Andreas Beckmann :
> [...]
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch' via 'buster' to 'sid'.
> It installed fine in 'stretch' and upgraded successfully to 'buster',
> then the upgrade to 'sid' fails.
>
> >From the attached log (
2017-01-25 9:30 GMT+01:00 eNovance :
> Package: terminix
> Version: 1.4.2-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Since the update to version 1.4.2, terminix fails to start with the
> following message :
>
> terminix: symbol lookup error: terminix: und
f799eaf556bcaa13ace5345e769b1c8a111cd744
Author: Matthias Klumpp
Date: Wed Jan 25 21:00:58 2017 +0100
Finalize changelog for 1.4.2-3
diff --git a/debian/changelog b/debian/changelog
index b72edc1..97699da 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+terminix (1.4.2-3) unstable; urgency=medium
2017-10-18 9:52 GMT+02:00 Andreas Tille :
> Hi Matthias,
>
> as usual I do not have the slightest idea what to do. Could I again ask
> for your kind help? Feel free to commit right to Git if you have any
> patch.
As usual, this is a LLVM/LDC bug, I will file the bugs in Debian's
bugtracker soon
Package: ldc
Version: 1:1.4.0-3
Severity: serious
When building dertain D code, LDC crashes with a "Crash via "Assertion
`decl->ir->irGlobal != NULL' failed"" message.
This affects Sambamba in Debian.
--
I welcome VSRE emails. See http://vsre.info/
Package: ldc
Version: 1:1.4.0-3
Severity: serious
Building a simple D example with an empty `void main () {}` function
makes LDC crash on ppc64el.
--
I welcome VSRE emails. See http://vsre.info/
Hi Paul!
Am Sa., 9. Apr. 2022 um 17:30 Uhr schrieb Paul Gevers :
>
> Hi,
>
> On Tue, 8 Mar 2022 21:00:25 +0100 Paul Gevers wrote:
> > Your package fails to build from
> > source on armhf and i386 while it successfully built there before.
>
> > This bug will trigger auto-removal when appropriate.
Hello!
Am Mi., 30. März 2022 um 20:21 Uhr schrieb Florian Ernst
:
>
> Source: appstream
> Version: 0.15.2-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
>
> Hello there,
>
> during a rebuild of the reverse b-d of libyaml I found that this package
> failed to build on my am
Hi Florian!
Am Mo., 11. Apr. 2022 um 09:30 Uhr schrieb Florian Ernst
:
>
> Hello Matthias,
>
> thank you for your reply and for the appstream update.
>
> On Sun, Apr 10, 2022 at 11:08:40PM +0200, Matthias Klumpp wrote:
> > Am Mi., 30. März 2022 um 20:21 U
Hi Sam!
Am Mi., 27. Okt. 2021 um 21:24 Uhr schrieb Sam Hartman :
>
> Package: debspawn
> Version: 0.5.0-1
> Severity: serious
> Justification: Significant data loss
>
> I used debspawn interact to interactively explore what I needed to do to get
> a new upstream package building.
> To make that
Am Do., 28. Nov. 2019 um 16:37 Uhr schrieb Pjotr Prins :
>
> When 1.18 arrives I think it is a good time to get sambamba and biod
> in Debian again.
They always were in Debian, just not in a release because the packages
were broken ^^
The LDC transition went really well this time, I don't think it
Am So., 15. Dez. 2019 um 10:16 Uhr schrieb Pjotr Prins :
> [...]
> > Therefore, the way of least resistance was to just use Meson for
> > building, as that does everything we need in Debian. Both BioD and
> > Sambamba build well with Meson.
>
> That is great. We can add the meson builds in the repo
Control: tag -1 pending
Hello,
Bug #946629 in tilix reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/gnome-team/tilix/commit/d4d54429efef18b0682d48feda785bf61518
Am Fr., 13. Sept. 2019 um 15:21 Uhr schrieb Andreas Tille :
>
> Hi Matthias,
>
> since a ling time libbiod does not build and it also does not
> install. Current issue when trying to build it is:
>
> ...
> ldc2 -wi -g -relocation-model=pic -unittest -main -Icontrib/undead -L-lz -O0
> -d-debug -li
Am Fr., 13. Sept. 2019 um 22:51 Uhr schrieb Andreas Tille :
>
> On Fri, Sep 13, 2019 at 03:37:32PM +0200, Matthias Klumpp wrote:
> > Am Fr., 13. Sept. 2019 um 15:21 Uhr schrieb Andreas Tille
> > :
> > > /usr/bin/ld.gold: error: bin/biod_tests.o: multiple definition o
Am Mi., 18. Sept. 2019 um 20:39 Uhr schrieb Andreas Tille :
> [...]
> > This is definitely an error in BioD itself, caused by a deprecation
> > that turned into an error in recent LDC versions.
> > So, libbiod will need to be upgraded for sure to fix this.
>
> @Pjotr: Can you comment on this?
>
> >
Am Do., 19. Sept. 2019 um 08:29 Uhr schrieb Andreas Tille
:
>
> Hi Matthias,
>
> On Thu, Sep 19, 2019 at 12:49:54AM +0200, Matthias Klumpp wrote:
> > > As I told you before: I have no idea about meson. It would be great if
> > > we could get it working but if we
Am Fr., 18. Okt. 2019 um 18:03 Uhr schrieb peter green :
>
> Package: gtk-d
> Version: 3.9.0-2
> Severity: serious
>
> The issue with gtk-d trying to build with the wrong compiler on gdc
> architectures (most notablly armhf, which until recently was an ldc
> architecture) has now been fixed, unfo
Package: gdc-9
Version: 9.2.1-17
Severity: serious
Hi!
Currently, GDC can't build package like gtk-d because it generates
duplicate non-weak symbols in object files, causing a collision when
linking. This seems to happen when using mixins / interfaces.
For more information and a workaround, please
Am Do., 28. Nov. 2019 um 15:19 Uhr schrieb Andreas Tille :
>
> Hi Pjotr,
>
> On Thu, Nov 28, 2019 at 07:50:34AM -0600, Pjotr Prins wrote:
> > Dear Andreas and Matthias,
> >
> > Good news, I think I have fixed the Sambamba bug! After a 3 day bug
> > hunt. Thanks Andreas for pushing me again. Let me
Am Sa., 6. Okt. 2018 um 14:45 Uhr schrieb Helmut Grohne :
>
> Source: gir-to-d
> Version: 0.16.1-1
> Severity: serious
> Tags: ftbfs
>
> gir-to-d fails to build from source in sbuild on unstable/amd64. A build
> log ends with:
>
> | dh build --buildsystem=meson
> |dh_update_autotools_config -O-
Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin :
>
> Package: appstream-generator
> Version: 0.7.4-1
> Severity: grave
>
> I've just installed appstream-generator and ran it:
>
> $ appstream-generator
> appstream-generator: symbol lookup error: appstream-generator: undefined
> symbol
Am So., 28. Okt. 2018 um 17:10 Uhr schrieb Andreas Tille :
>
> Control: tags -1 help
>
> Hi Matthias,
>
> seems I need your help again :-(
> [...]
> > ldc2 -I=biod@sha -I=. -I=.. -I/usr/include/d -enable-color -O -g -release
> > -wi -relocation-model=pic -of='biod@sha/bio2_bgzf.d.o' -c ../bio2/b
Hi!
The appstream-generator package has finally been rebuilt, so this
issue can be closed.
Cheers,
Matthias
Am Sa., 10. Nov. 2018 um 15:25 Uhr schrieb Julien Cristau :
>
> On Wed, Oct 24, 2018 at 12:50:28 +0200, Matthias Klumpp wrote:
>
> > Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin
> > :
> > >
> > > Package: appstream-generator
>
forcemerge 933675 935275
affects 933675 dustmite
thankyou
Am Mi., 21. Aug. 2019 um 12:45 Uhr schrieb Ivo De Decker :
>
> package: src:dustmite
> version: 0~20170126.e95dff8-3
> severity: serious
> tags: ftbfs
>
> Hi,
>
> A binnmu of dustmite in unstable fails on amd64:
>
> https://buildd.debian.or
Am Mi., 4. Sept. 2019 um 18:00 Uhr schrieb Matthias Klose :
>
> Package: src:ldc
> Version: 1:1.17.0-1
> Severity: serious
> Tags: sid bullseye
>
> looks like gdmd isn't available, and according to the changelog gdc should be
> used for the bootstrap?
Man you're quick ^^
gdmd is currently stuck in
Am Mi., 4. Sept. 2019 um 18:05 Uhr schrieb Matthias Klose :
>
> On 04.09.19 18:01, Matthias Klumpp wrote:
> > Am Mi., 4. Sept. 2019 um 18:00 Uhr schrieb Matthias Klose :
> >>
> >> Package: src:ldc
> >> Version: 1:1.17.0-1
> >> Severity: serious
&
Hi!
Am Mi., 4. Sept. 2019 um 11:17 Uhr schrieb Matthias Klose :
>
> Package: dub
> Version: 1.16.0-1
> Severity: serious
> Tags: sid bullseye
>
> dub depends on the unavailable package default-d-compiler. Maybe that one
> should
> be built from the dh-dlang source. If you touch that package, plea
reassign 939833 gdc-9
severity 939833 important
thankyou
Am Mo., 9. Sept. 2019 um 13:30 Uhr schrieb Matthias Klose :
>
> Package: default-d-compiler
> Version: 0.6.3
> Severity: serious
> Tags: sid bullseye
>
> default-d-compiler pointing to gdc doesn't understand the "-main" option,
> causing bui
Hi!
I was going to report this bug, but fortunately checked whether
someone already created it beforehand :-)
So, the culprit is highly likely
https://github.com/mesonbuild/meson/commit/0ec039d2597526c670f7e0478a7b5008e14ff474
This passes LDFLAGS from the environment to the compiler to figure out
Control: reassign -1 meson 0.63.1-1
Control: forcemerge -1 1017087
Control: affects 1017087 + mir-core
This is due to a regression in Meson itself reported as bug #1017087
Hopefully we will get a fix into Debian soon, merging this with the
original bug.
Cheers,
Matthias
--
I welcome VSRE em
Am Mi., 31. Aug. 2022 um 01:09 Uhr schrieb Steve Langasek
:
>
> Package: mir-core
> Version: 1.1.111-1
> Severity: serious
> Tags: patch
> Justification: ftbfs
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu kinetic ubuntu-patch
>
> Hi Matthias,
>
> The mir-core package is failing t
Am Mi., 31. Aug. 2022 um 03:01 Uhr schrieb Steve Langasek
:
>
> Source: stdx-allocator
> Version: 3.1.0~beta.2-3
> Severity: serious
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu kinetic
>
> Hi Matthias,
>
> After fixing up stdx-allocator build-deps so that they're installable,
>
severity 1010421 important
thankyou
Hi!
I'm reducing the severity since an easy-ish workaround is available and
keeping this at a blocking severity prevents the workaround-included
gir-to-d version to migrate.
This is still an important issue though which should be fixed for the
release, as
2017-12-15 15:05 GMT+01:00 Matthias Klose :
> Control: reopen -1
> Control: reassign -1 ldc
>
> On 15.12.2017 13:53, Matthias Klumpp wrote:
>> 2017-12-15 9:46 GMT+01:00 Matthias Klose :
>>> [...]
>
> ok, but then the issue is in ldc, so you should change the defaul
2017-12-17 21:14 GMT+01:00 Adrian Bunk :
> Source: appstream-generator
> Version: 0.6.8-2
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/appstream-generator.html
This is a regression in Meson, see the following issue reports:
https://github.com/mesonbuil
2018-04-14 13:25 GMT+02:00 Julien Cristau :
> Package: appstream-generator,ftp.debian.org
> Severity: grave
>
> dists/unstable/non-free/dep11/Components-amd64.yml.xz doesn't match
> dists/unstable/non-free/dep11/Components-amd64.yml.gz, and the former
> also doesn't match the expected hash from InR
this transition in Debian. When we binnmu'd it in raspbian the
>> dependency on libphobos2-ldc76 was replaced by libphobos2-ldc-shared78 but
>> the dependency on libphobos2-ldc-dev remained.
>
> The depencency on libphobos2-ldc-dev was explicitly added by Matthias
> Kl
2017-09-03 21:22 GMT+02:00 Pino Toscano :
> Package: libappstreamqt-dev
> Version: 0.11.4-1
> Severity: grave
> Justification: renders package unusable
> Control: affects -1 src:frameworkintegration
> Control: affects -1 src:plasma-discover
>
> Hi,
>
> in the new version 0.11.4, I guess because of
2017-09-03 21:15 GMT+02:00 Maximiliano Curia :
> [...]
> # check that the installed version has the same 32/64bit-ness as the one
> which is currently searching:
> if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8")
> math(EXPR installedBits "8 * 8")
> set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedB
Hi!
I wonder why the shlibs file is messed up, since debhelper should
actually handle it correctly...
If you have an idea, let me know, otherwise I'll investigate this next week.
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
2018-01-29 21:19 GMT+01:00 Emilio Pozuelo Monfort :
> Source: appstream-generator
> Version: 0.6.8-2
> Severity: serious
>
> Hi,
>
> On a rebuild against new libphobos, your package failed to build from source,
> see:
>
> https://buildd.debian.org/status/package.php?p=appstream-generator
This is a
2018-01-29 21:19 GMT+01:00 Emilio Pozuelo Monfort :
> Source: vibe.d
> Version: 0.8.1-2
> Severity: serious
>
> On a rebuild against new libphobos, your package failed to build from source,
> see:
>
> https://buildd.debian.org/status/package.php?p=vibe.d
This is a known regression in Meson, mergin
2018-01-31 12:33 GMT+01:00 Juhani Numminen :
> Control: tags -1 fixed-upstream
>
> On Tue, 23 Jan 2018 19:32:45 +0200 Adrian Bunk wrote:
>> Source: apper
>> ...
>> CMake Error at CMakeLists.txt:38 (find_package):
>> Could not find a configuration file for package "PackageKitQt5" that is
>> com
2018-02-07 10:05 GMT+01:00 Chris Lamb :
> Source: plasma-discover
> Version: 5.12.0-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Matthias Klumpp
>
> Hi,
>
> I just ACCEPTed plasma-discover from NEW but noticed it was missing
> attribution in deb
2017-09-20 5:28 GMT+02:00 Nobuhiro Iwamatsu :
> Hi,
>
> sambamba package has not fixed this problem with ldc 1:1.4.0-1.
> Also, I confirmed that diet-ng fixed this problem.
This is a different bug:
https://github.com/ldc-developers/ldc/issues/2300#issuecomment-330947562
--
I welcome VSRE emails.
988902ca7a0fc22e879b709a7b022db6357ee956
Author: Matthias Klumpp
Date: Sun Oct 1 18:07:24 2017 +0200
Finalize changelog for 1.6.4-2
diff --git a/debian/changelog b/debian/changelog
index 9df65f7..347720d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tilix (1.6.4-2) unstable; urgency=medium
2018-01-23 19:32 GMT+01:00 Rik Mills :
> Appstream 0.11.8-1 synced to Ubuntu some hours ago, and is now causing
> similar build failures.
>
> For example in plasma-workspace:
> https://launchpad.net/ubuntu/+source/plasma-workspace/4:5.11.5-0ubuntu2
>
> Same failures also on Kubuntu CI, if I let tha
Am Di., 4. Aug. 2020 um 11:23 Uhr schrieb Andreas Tille :
>
> Control: tags -1 help
>
> Hi,
>
> On Mon, Aug 03, 2020 at 10:06:32AM +0200, Lucas Nussbaum wrote:
> > > lto1: fatal error: bytecode stream in file
> > > ‘/usr/lib/x86_64-linux-gnu/libhts.a’ generated with GCC compiler older
> > > than
Am Di., 26. Mai 2020 um 20:24 Uhr schrieb :
>
> > -Original Message-
> > From: Ansgar
> > Sent: Tuesday, May 26, 2020 8:01 AM
> > To: Steffen Schreiber; 961...@bugs.debian.org
> > Subject: Bug#961490: fwupd: version in stable too old, no updates possible
> >
> >
> > [EXTERNAL EMAIL]
> >
>
Hi Simon!
Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> to be replaced by libgtk-3-0t64 after checking that the functions that
> interact with time_t (methods of GtkRecentInfo) are handled correctly.
Will thi
Am Di., 19. März 2024 um 22:25 Uhr schrieb Simon McVittie :
>
> On Tue, 19 Mar 2024 at 22:14:12 +0100, Matthias Klumpp wrote:
> > Am Di., 19. März 2024 um 21:42 Uhr schrieb Simon McVittie :
> > > libgtkd-3-0 has a hard-coded dependency on libgtk-3-0, which will need
> >
Am Mo., 18. Dez. 2023 um 09:09 Uhr schrieb Adrian Bunk :
> [...]
> ...
> -- The following OPTIONAL packages have not been found:
>
> * Breeze (required version >= 5.27.10)
>For setting the default window decoration plugin
> * AppStreamQt5 (required version >= 0.10.6), Access metadata for list
Control: tag -1 pending
Hello,
Bug #1058908 in plasma-workspace reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/qt-kde-team/kde/plasma-workspace/-/commit/d99f13
Am Mo., 19. Feb. 2024 um 21:45 Uhr schrieb Matthias Klose :
>
> Package: src:ldc
> Version: 1:1.36.0-1
> Severity: serious
> Tags: sid trixie
>
> Just reading the changelog:
>
> * LDC should already work fine with 64-bit time on 32-bit
> architectures, just to be on the safe side though,
Hi Julian (now CC'ed)!
Do you have any idea how this would be possible? Both PK and Synaptic
should hold the APT frontend lock, so they should never be able to run
at the same time.
I also have never once observed this behavior...
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.i
Okay, I created a patch which _may_ fix this bug. I have no SPARC
architecture here to test it :-P
I submitted this patch to upstream, he implemented it. I also created a bug
report for lazbuild, cause my patch is only a workaround, the real problem
still exists in lazbuild.
A new package which fix
Hello!
Is this a "must-be-done"-bug? Cause it can be a bug in Lazbuild, which can
only be fixed with a new version of Lazarus IDE...
I will backtrack this strange bug, but because there are no debuginfos,
this will be hard...
If it's not possible to solve this bug, can I exclude easyMp3Gain from
b
2013/2/10 Laurent Bigonville :
> [...]
> It seems that in the 0.8, the DBus API has changed in an incompatible
> way from 0.7 series.
>
> The GetTid() method has been renamed to CreateTransaction()
>
> org.freedesktop.DBus.Error.UnknownMethod: No such method `GetTid'
>
> To handle this, you should
Hi!
What exactly happened? (This bug report lacks nearly all information
needed for resolving ;-) )
Cheers,
Matthias
2012/10/26 Nikolay Bitsadze :
> Package: packagekit
> Version: 0.7.6-1
> Severity: grave
> Tags: upstream
> Justification: causes non-serious data loss
>
> Dear Maintainer,
> ***
1 - 100 of 174 matches
Mail list logo
