Hi,
2017-01-18 4:34 GMT+01:00 Guillem Jover :
> Hi!
>
> I'd like to get some feedback from porters and package maintainers,
> given that this affects at least both groups. Some background first.
>
> One of the reasons PIE has in the past not been enabled by default in
> dpkg-buildflags, is becaus
Hi!
I'd like to get some feedback from porters and package maintainers,
given that this affects at least both groups. Some background first.
One of the reasons PIE has in the past not been enabled by default in
dpkg-buildflags, is because it introduced some slowness on some arches,
although this
<<< text/html: Unrecognized >>>
On Wed, Jan 18, 2017 at 1:08 AM, Russ Allbery wrote:
> Santiago Vila writes:
>> In this context, I refer specifically to flaky tests. What I call
>> questionable is keeping a flaky test making the build to fail when the
>> test fails so much that it's clearly a wrongly designed test.
>
> Oh, sure,
Stuart Prescott writes ("Re: no-strong-digests-in-dsc MBF"):
> Given the hashes aren't used within Debian and can't be used reliably by
> external parties either, it doesn't feel like a good use of anyone's time.
dgit uses the hashes in the .dsc, both during `dgit fetch' and during
`dgit import-d
Hi Matthias,
On Wed, 18 Jan 2017 00:31:44 Matthias Klumpp wrote:
> > The hashes inside the .dsc file are not used in Debian once the package
> > has
> > been accepted by dak.
>
> I do require them in Debian derivatives (Tanglu / PureOS) and .dsc
> files without the up-to-date signatures are quite
2017-01-18 0:14 GMT+01:00 Stuart Prescott :
> Hi Adrian,
>
>> I want to do a MBF for all packages without a SHA256 checksum field
>> in the .dsc [1] - only SHA1 as hash would not be good in stretch.
>
> I missed two details here:
>
> * why is this worth going at all
>
> * why is this important enou
Hi Adrian,
> I want to do a MBF for all packages without a SHA256 checksum field
> in the .dsc [1] - only SHA1 as hash would not be good in stretch.
I missed two details here:
* why is this worth going at all
* why is this important enough for the bugs to be release-critical (which
means, afte
Adrian Bunk writes:
> I want to do a MBF for all packages without a SHA256 checksum field
> in the .dsc [1] - only SHA1 as hash would not be good in stretch.
Why? The Sources index should have a stronger hash either way.
If you care about stronger hashes in the .dsc itself, wouldn't the .dsc
its
Hi,
I want to do a MBF for all packages without a SHA256 checksum field
in the .dsc [1] - only SHA1 as hash would not be good in stretch.
This is quite easy to fix in a package - all that is required is a
sourceful upload (but a binNMU would not be sufficient).
The steps will be:
1. QA uploads
On Tue, 17 Jan 2017 13:35:14 + Ian Jackson
wrote:
> [1] AIUI this is when your laptop suspends to RAM, but after a timeout
> or when the battery is low, wakes up so that it can suspend to disk.
Linux implements hybrid sleep by going ahead and writing the hibernation
image out, then suspendin
Santiago Vila writes:
> Not exactly. I'm not advocating not failing a build if tests fail
> as a general rule.
> In this context, I refer specifically to flaky tests. What I call
> questionable is keeping a flaky test making the build to fail when the
> test fails so much that it's clearly a wro
Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things
[and 1 more messages]"):
> This seems to solve the problem for me, thank you very much! (And I hope
> you can get this in for stretch!)
Thanks to everyone for their reports. This is very helpful.
Currently experimental
Package: wnpp
Owner: Balint Reczey
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: kodi-addon-webinterface-chorus2
Version : 2.4.1
Upstream Author : Jeremy Graham
* URL : https://github.com/xbmc/chorus2
* License : GPL-2.0+
Prog
Hi Bjørn,
Am 17.01.2017 um 10:28 schrieb Bjørn Mork:
> To me it looks like a sandbox fight which started with the creative use
> of "Priority: important". Now it appears that the party starting the
> fight thinks the other party should stop throwing sand until "mommy"
> (aka CTTE) decides who is r
Andreas Tille writes:
>> Since this is still an open discussion in #846002, I would have
>> preferred if you would not try to force your own preference here before
>> the CTTE made its decision.
>
> While I'm not sure whether its a personal preference or whether some
> discussion I might have mis
On Mon, Jan 16, 2017 at 05:45:19PM -0800, Russ Allbery wrote:
> > Well, maybe what it's excessively aggressive or questionable is to run
> > the tests at build time and making the package build as a whole to fail
> > when any test fails.
>
> *blink*.
>
> I'm quite surprised that you would advoca
On So, Jan 15, 2017 at 04:43:11 +, Ian Jackson wrote:
I have just uploaded systemd-shim 10-3~exp1 to experimental. I seems
to fix the problem for me. Depending on feedback, I will upload this
to sid in the next few days.
Thank you very much. I don’t have problems either.
Stephan
Hi,
On Sun, Jan 15, 2017 at 02:24:13PM +0100, Ole Streicher wrote:
> > Important changes in this release of the installer
> > ==
> >
> > * [...]
> > * As noted in the Stretch Alpha 6 release announcement, Debian Pure
> >Blends appeared in the
19 matches
Mail list logo
