On Tue, 2023-06-20 at 22:46 +0200, Kurt Roeckx wrote:
> Can I suggest that if you file a few bugs and add some information in
> it so that maybe someone can look at it? If it only affects one
> architecture, send a mail to that list asking for help.
PS: when filing architecture-specific bugs, ple
On Mon, Sep 30, 2019 at 1:14 AM John Paul Adrian Glaubitz wrote:
> Having said that, I'm going to unsubscribe from this list now as I realize
> that what we do in Debian Ports is still not considered useful many others,
> so I think it's not possible to find an agreement.
To be clear, I think the
John Paul Adrian Glaubitz:
> Yes, the wiki is unfortunately not always the best resource to rely
> on when it comes to these things in Debian. Currently the best
> way is to ask on the appropriate mailing lists.
Uh, mailing lists are a horrible way to do documentation :)
I've updated the wiki pa
Michael Schmitz wrote:
> I don't see why a list alias can't be used to collect mail coming in on
> the old list name (or the new, more logical one if that's easier on the
> sites archiving the list).
An alias is already in place according to that wiki page.
--
bye,
pabs
https://wiki.debian.org
On Tue, 2017-12-19 at 07:33 +0100, Ingo Jürgensmann wrote:
> Haven’t looked into the details, but would changing the addresses of
> m68k-bu...@nocrew.org also change their mailing list archive links?
> Is that archive still online? If so, it would be good to have the
> links being kept, but the r
Hi folks,
I was doing some cleanup on Debian usertags and I noticed that some
8 bugs were associated with the non-existent debian-m68k mailing list
while 53 other m68k related bugs were instead associated with the
debian-68k mailing list. I then moved the 8 bugs over to debian-68k
using the comman
On Wed, 2016-06-15 at 01:37 +0300, Dimitri John Ledkov wrote:
> At the openmainframeproject EU meetup, it was indicated that SUSE
> joined with indication that Open Build Service might be able to use
> resources hosted by Marist.
>
> I wonder if it makes sense to reach out, and see if there are
>
On Thu, Jul 23, 2015 at 1:21 AM, John Paul Adrian Glaubitz wrote:
> I'm in favor of the old design because I think it's important to havw a list
> which can be used to make announcements about important issues that all
> porters should be aware of.
We have debian-devel-announce for that, the ex
Hi all,
Do any porters have any input on this page?
https://wiki.debian.org/GettingPorted
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
On Sun, Nov 24, 2013 at 5:53 AM, Don Armstrong wrote:
> These are the list of ports that I see:
I would strongly suggest not hardcoding this list and instead
harvesting the Architecture fields of the Release files for oldstable
-> experimental on ftp.d.o, ftp.d-p.o and maybe archive.d.o.
We have
On Thu, 2005-11-24 at 09:42 +1100, Finn Thain wrote:
> FIX_ENDIAN_INT32_INPLACE is inside the ifdef, and it is used by
> testFixEndian() in endian.cpp, which is why the actual = 0x12345678, and
> not 0x78563412.
I'm so blind, thanks for that.
--
bye,
pabs
http://wiki.debian.org/PaulWise
si
On Thu, 2005-11-24 at 00:21 +1100, Finn Thain wrote:
> A quick look at the rest of the code shows that util.h tests
> #ifndef __BIG_ENDIAN__
> which probably doesn't work because it needs the right header.
True, but I don't think that is relevant to SWAP_ENDIAN_INT32 because it
is outside that #i
Hi,
I recently enabled my upstream's cppunit test suite in an upload to
experimental and the endianess test failed on m68k. The test is
basically like so:
#define SWAP_ENDIAN_INT32(x) ( \
(((x)&0xFF00) >> 24) | \
(((x)&0x00FF) >> 8) | \
(((x)&0xFF00) << 8) | \
(((x)&0x00
13 matches
Mail list logo
