On 29.01.2017 13:13, Alexey Pavlov wrote:
> Well you can try then update PKGBUILD to use latest debian release sources
So the curious case is that this package (which is just by chance the
first one I tried to build) seems to be broken in multiple ways. First
the download is offline. But I found the archive on launchpad with the
correct checksum. After fixing the link it does not compile because a
directory name doesn't match. After fixing the directory name, it does
not compile because a patch fails. I stopped there.
The strange thing: the sources all have matching checksums. So either
the package would have failed to build in a very long time, or maybe I'm
completely on the wrong track? Does the current CI ever try to build the
full set of packages, for example after a major system update or gcc
update or something?
I'm just trying to help here, in the sense that I'd like MSYS2 to have
a more "stable" state. I'll try to compile further packages and fix
issues as I find them. It would be super awesome to have a (large) set
of packages that compile 100% out of the box against each other.
Can someone give me a hint how I would bootstrap the full system? Can
I just go alphabetically and build all packages twice, or does one need
to cleverly order packages to first get gcc and base, and then the rest?
Cheers and thanks for all the great work(!!!!!),
Mario
>> 29 янв. 2017 г., в 15:02, Mario Emmenlauer <[email protected]
>> <mailto:[email protected]>> написал(а):
>>
>>
>> Hi Alexey,
>>
>> On 29.01.2017 12:58, Alexey Pavlov wrote:
>>>
>>>> 29 янв. 2017 г., в 14:55, Mario Emmenlauer <[email protected]
>>>> <mailto:[email protected]>> написал(а):
>>>>
>>>>
>>>> Dear All,
>>>>
>>>> I'm trying to compile the current HEAD of Alexpux/MINGW-packages
>>>> against itself. My mileage is not super great. The first problem is
>>>> that ca-certificates references a debian download package that is
>>>> no longer available. What is the cleanest way to fix this? Would it
>>>> be sensible to have a fallback mirror of source archives referenced
>>>> in Alexpux/MINGW-packages? It makes a bit of extra work to push the
>>>> sources there when updating a package, but it would make the repo
>>>> much more long-lived (and help in regression testing).
>>>>
>>>> What do others think?
>>>
>>> You can manually download package with sources and place source archive in
>>> folder with PKGBUILD
>>
>> Thanks for the super quick response! That's a good idea, but it does
>> not really solve the problem in the long run... for example in my
>> case I'm aiming for a "stable release" series, so it would be great
>> if the packages just compile, no questions asked :-) Do you know if
>> makepkg has a concept of fallback servers? Then we could maybe put
>> fallback copies on sourceforge or somewhere...
>>
>> Cheers,
>>
>> Mario Emmenlauer
Viele Gruesse,
Mario Emmenlauer
--
BioDataAnalysis GmbH, Mario Emmenlauer Tel. Buero: +49-89-74677203
Balanstr. 43 mailto: memmenlauer * biodataanalysis.de
D-81669 München http://www.biodataanalysis.de/
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
