Mattia Rizzolo wrote...
> I'd say go ahead. I'm currently at DebCamp so I can handle problems, as
> well as my collegues we are normally fairly fast in handling this kind
> of regressions. :)
Thanks for the swift response, file 1:5.45-2 was uploaded a few seconds
ago, brace for impact :=)
On Sat, Sep 02, 2023 at 08:24:29PM +0200, Christoph Biedl wrote:
> The usual autopkgtests were run as part of the the experimental pseudo-
> migration, and diffscope did not show issues.
If autopkgtest is happy, then I'd say we can be fairly confidend
everything's fine.
> I could however not test
Hello there,
it's been a while but the story hasn't changed: A new upstream release
of file/libmagic has been accepted into experimental, already a few
weeks ago, version 1:5.45-1. As your package is one of those that
somewhat suffered from surprising feature changes of libmagic in the
past, I'd l
Hi Christoph,
> there hasn't been another upstream version upload of file/libmagic for a
> while, but it was about time. Version 5.43 was released in October, I've
> uploaded it with a cumulative patch into experimental tonight, version
> 1:5.43-3. As your package is one of those that somewhat suf
Hello,
there hasn't been another upstream version upload of file/libmagic for a
while, but it was about time. Version 5.43 was released in October, I've
uploaded it with a cumulative patch into experimental tonight, version
1:5.43-3. As your package is one of those that somewhat suffered from
surp
hi,
On Sat, Oct 30, 2021 at 11:51:45AM +0100, Chris Lamb wrote:
> Neat. Okay, so I've just run the testsuite against file 1:5.41-1 in
> experimental and everything appears to pass.
while this is great, shouldn't we run these automatically? :)
https://ci.debian.net/packages/d/diffoscope/unstable/
Hi Christoph,
> A new upstream release of file/libmagic has been accepted into
> experimental yesterday, version 1:5.41-1.
Neat. Okay, so I've just run the testsuite against file 1:5.41-1 in
experimental and everything appears to pass. Thank you for sending
these notifications — we appreciate the
Hello there,
you know this game:
A new upstream release of file/libmagic has been accepted into
experimental yesterday, version 1:5.41-1. As your package is one of
those that somewhat suffered from surprising feature changes of libmagic
in the past, I'd like to give you an opportunity to test and
Hi Christoph,
> A new upstream release of file/libmagic has been accepted into
> experimental yesterday, version 1:5.39-2. As your package is one of
> those that somewhat suffered from surprising feature changes of libmagic
> in the past, I'd like to give you an opportunity to test and to prepare
Hello there,
A new upstream release of file/libmagic has been accepted into
experimental yesterday, version 1:5.39-2. As your package is one of
those that somewhat suffered from surprising feature changes of libmagic
in the past, I'd like to give you an opportunity to test and to prepare
for any c
Hi,
On Fri, Dec 27, 2019 at 11:40:57AM +0100, Christoph Biedl wrote:
> A re-build showed no errors
Perfect. Then it's most likely fine. If we really want to do the next
step it would be to run autopkgtest, which runs just a couple more tests
iirc, but just rebuilding is good enough for me.
> -
Hello there,
A new upstream release of file/libmagic has been accepted into
experimental a few days ago, version 1:5.38-1. As your package is
one of those that somewhat suffered from surprising feature changes of
libmagic in the past, I'd like to give you an opportunity to test and
to prepare for
Hi Christoph,
> > https://gist.github.com/lamby/512ae552e687475d413bced51201721d/raw
[…]
> Obviously time zone confusion which I cannot reproduce here. Do you
> still use the setup you described in #861523?
Bam, nailed it. I have a little toggle/hack to try and avoid screwing
with timezones and
Chris Lamb wrote...
[ file build errors ]
> So, it (still) fails for me here:
>
> https://gist.github.com/lamby/512ae552e687475d413bced51201721d/raw
>
> … but I haven't looked into it whatsoever. :)
Obviously time zone confusion which I cannot reproduce here. Do you
still use the setup you des
[Re-adding diffosc...@packages.debian.org to CC]
Hi Christoph,
> > … and plan to work on it today. Thanks for letting us know and giving
> > us the heads-up, very considerate of you.
FYI this is now fixed. Thanks again.
> > (I'm sure you are aware already but this version of file actually
> > F
Dear Christoph et al.,
> A new upstream release of file/libmagic has been accepted into
> experimental a few moments ago, version 1:5.37-1. As your package is
> one of those that somewhat suffered from surprising feature changes of
> libmagic in the past, I'd like to give you an opportunity to tes
Hello there,
a new Debian development cycle, time to brea^W play around :)
A new upstream release of file/libmagic has been accepted into
experimental a few moments ago, version 1:5.37-1. As your package is
one of those that somewhat suffered from surprising feature changes of
libmagic in the pas
Hi Christoph!
On Thu, Jul 26, 2018 at 08:37:58AM +0200, Christoph Biedl wrote:
> after a somewhat bumpy experience following the upload of the previous
> upstream release of file (5.33), I eventually decided to introduce a
> release procedure for src:file in Debian: New upstream release uploads
>
Hello there,
after a somewhat bumpy experience following the upload of the previous
upstream release of file (5.33), I eventually decided to introduce a
release procedure for src:file in Debian: New upstream release uploads
will go to experimental first, and package maintainers that probably
would
19 matches
Mail list logo
