These warnings are just informing you:
1) that RESUME is a user defined without an associated login (or certificate / key), and
2) that if the login that it thinks it should be associated with isn't defined in the target database then the package will create it with a default password (because we can't get its actual password out of SQL Server).
As long as you know that RESUME is a user without an associated login (i.e. you made it with CREATE USER RESUME WITHOUT LOGIN, or deleted the login it was created for), then you can ignore the first warning. (If you think it should have an associated login, you need to look at your database and reattach the appropriate login with sp_change_users_login, as the message says.)
As long as the login RESUME thinks it should be associated with is in the target database, the second warning should also be harmless. If the user RESUME's login isn't in the target database, the package will create the user and may also create a login called RESUME with the password 'p@ssw0rd' which you'll have to change manually afterwards.
(The package will create a login if the original user was once bound to a login - it shouldn't create any logins if the original user has always been without a login, i.e. it was defined WITHOUT LOGIN rather than being defined for a login which has since disappeared.)