>1. Submitting a BUG as a request for a package update is NOT what i thought it 
>was.
>i kinda followed this: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages ,

Ok, I see. I've probably added to the confusion and I'm sorry for that
:)

A bug report with "there's a new version 1.2.3, perhaps update?" is ok.
Ideally this will alert people to take a look at it, though it may take
a while before someone gets round to the actual update.

A sync request is a specific type of update request, so when I saw the
title I figured some details are missing, here's a link to a wiki page
with some hints. This might be me reading more into it, so I'm sorry for
dragging you into strange things you knew little about :)


> but if I had known it ALSO was my responsibility to test and maybe 
> package/upload the package aswell I would not have done it.

Well, yes and no. I'll try to decomplicate things a bit more.
* Starting with the Debian tracker page 
https://tracker.debian.org/pkg/gcc-mingw-w64
* We see in the Ubuntu box that it has a link to "patches for 22~exp1ubuntu4" 
https://patches.ubuntu.com/g/gcc-mingw-w64/gcc-mingw-w64_22~exp1ubuntu4.patch
* These changes are the main complication here. They have been added to fix 
some issue. The main question here is whether this issue is now fixed in Debian 
or if Ubuntu still needs to add the fix.
* The new version has been added to Debian, and no serious bugs seems to have 
been reported since. 

The content of a sync request here would consist of 
1. The new changelog entries in Debian
2. The changelog entries from Ubuntu
3. A short explanation of why the Ubuntu changes can be dropped.
That should be all that's needed. (Of course, it can be tricky to see whether 
the Ubuntu changes are still required or not, and it is beyond me in this case) 
Once that is put together the sponsors-team will do the actual changes, getting 
the new package built and tested before it is added to the archive. 

(I suppose during Freeze a build log is required to see that the new
version still builds ok, and testing if the program still runs and work
is nice. But no one will require you to test every single feature of
it.)

Again, I'm sorry for adding more confusion than probably needed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897394

Title:
  Please sync gcc-mingw-w64-x86-64 (10.1.0-3+23) from debian Bullseye

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-mingw-w64/+bug/1897394/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to